Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry (Obsoleted)

Internet Engineering Task Force (IETF)                       B. Trammell
Request for Comments: 6685                                    ETH Zurich
Updates: <a href="./rfc5070">5070</a>                                                  July 2012
Category: Standards Track
ISSN: 2070-1721


 <span class="h1">Expert Review for Incident Object Description Exchange Format (IODEF)</span>
                    <span class="h1">Extensions in IANA XML Registry</span>

Abstract

   This document specifies restrictions on additions to the subset of
   the IANA XML Namespace and Schema registries, to require Expert
   Review for extensions to Incident Object Description Exchange Format
   (IODEF).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc6685">http://www.rfc-editor.org/info/rfc6685</a>.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.






<span class="grey">Trammell                     Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc6685">RFC 6685</a>                   IODEF XML Registry                  July 2012</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   IODEF extensions via class extension through AdditionalData and
   RecordItem elements, per <a href="./rfc5070#section-5.2">Section 5.2 of [RFC5070]</a>, generally register
   their namespaces and schemas with the IANA XML Namespace registry at
   <a href="http://www.iana.org/assignments/xml-registry/ns.html">http://www.iana.org/assignments/xml-registry/ns.html</a> and the IANA XML
   Schema registry at
   <a href="http://www.iana.org/assignments/xml-registry/schema.html">http://www.iana.org/assignments/xml-registry/schema.html</a>,
   respectively [<a href="./rfc3688" title=""The IETF XML Registry"">RFC3688</a>].

   In addition to schema reviews required by IANA, these registry
   requests should be accompanied by a review by IODEF experts to ensure
   the specified AdditionalData and/or RecordItem contents are
   compatible with IODEF and with other existing IODEF extensions.  This
   document specifies that review.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Expert Review of IODEF-Related XML Registry Entries</span>

   Changes to the XML Schema registry for schema names beginning with
   "urn:ietf:params:xml:schema:iodef" are subject to an additional IODEF
   Expert Review [<a href="./rfc5226" title="">RFC5226</a>] for IODEF correctness and appropriateness.

   The IODEF expert(s) for these reviews will be designated by the IETF
   Security Area Directors.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Security Considerations</span>

   This document has no security considerations.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  IANA Considerations</span>

   This document specifies additional expert reviews for IODEF
   extensions, on the XML Schema registry
   (<a href="http://www.iana.org/assignments/xml-registry/schema.html">http://www.iana.org/assignments/xml-registry/schema.html</a>), in
   <a href="#section-2">Section 2</a>.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Normative References</span>

   [<a id="ref-RFC3688">RFC3688</a>]  Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
              January 2004.

   [<a id="ref-RFC5070">RFC5070</a>]  Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident
              Object Description Exchange Format", <a href="./rfc5070">RFC 5070</a>,
              December 2007.

   [<a id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
              May 2008.



<span class="grey">Trammell                     Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc6685">RFC 6685</a>                   IODEF XML Registry                  July 2012</span>


Author's Address

   Brian Trammell
   Swiss Federal Institute of Technology Zurich
   Gloriastrasse 35
   8092 Zurich
   Switzerland

   Phone: +41 44 632 70 13
   EMail: [email protected]









































Trammell                     Standards Track                    [Page 3]