IODEF Registry Review: Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry
Requiring expert review for IODEF extensions in the IANA XML registry.
Trammell, B., "Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry", RFC 6685, DOI 10.17487/RFC6685, July 2012, <https://www.rfc-editor.org/info/rfc6685>.
@misc{rfc6685,
series = {Request for Comments},
number = 6685,
howpublished = {RFC 6685},
publisher = {RFC Editor},
doi = {10.17487/RFC6685},
url = {https://www.rfc-editor.org/info/rfc6685},
author = {B. Trammell},
title = {{Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry}},
pagetotal = 3,
year = 2012,
month = jul,
} RFC text
Contents
Internet Engineering Task Force (IETF) B. Trammell
Request for Comments: 6685 ETH Zurich
Updates: 5070 July 2012
Category: Standards Track
ISSN: 2070-1721
Expert Review for Incident Object Description Exchange Format (IODEF)
Extensions in IANA XML Registry
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 Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6685.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) 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.
1. Introduction
IODEF extensions via class extension through AdditionalData and
RecordItem elements, per Section 5.2 of [RFC5070], generally register
their namespaces and schemas with the IANA XML Namespace registry at
http://www.iana.org/assignments/xml-registry/ns.html and the IANA XML
Schema registry at
http://www.iana.org/assignments/xml-registry/schema.html,
respectively [RFC3688].
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.
2. Expert Review of IODEF-Related XML Registry Entries
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 [RFC5226] for IODEF correctness and appropriateness.
The IODEF expert(s) for these reviews will be designated by the IETF
Security Area Directors.
3. Security Considerations
This document has no security considerations.
4. IANA Considerations
This document specifies additional expert reviews for IODEF
extensions, on the XML Schema registry
(http://www.iana.org/assignments/xml-registry/schema.html), in
Section 2.
5. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RFC5070] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident
Object Description Exchange Format", RFC 5070,
December 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
Author's Address
Brian Trammell
Swiss Federal Institute of Technology Zurich
Gloriastrasse 35
8092 Zurich
Switzerland
Phone: +41 44 632 70 13
EMail: trammell@tik.ee.ethz.ch
AI ELI5
On this page
§1IODEF Extensions and the Registry
The Incident Object Description Exchange Format (IODEF), defined in RFC 5070, lets incident response teams exchange information about security incidents. Extensions to IODEF can be added via class extensions in AdditionalData and RecordItem elements.
These extensions are registered in the IANA XML Namespace and Schema registries. RFC 6685 requires that in addition to IANA schema review, these registry requests must also be reviewed by IODEF experts to ensure the extensions are compatible with IODEF and existing extensions.
IODEF is a format for sharing incident details. When people add new things to it, an IODEF expert checks them first.
§2Expert Review Process
Changes to the XML Schema registry for schema names beginning with 'urn:ietf:params:xml:schema:iodef' are now subject to Expert Review. The IODEF expert or experts are designated by the IETF Security Area Directors.
The expert review ensures that new AdditionalData and RecordItem contents are correct and appropriate for IODEF. This is in addition to any schema review required by IANA for the XML registries themselves.
The IETF picks IODEF experts. They check each new extension before it goes on the official list.
§3No Direct Security Impact
The document specifies no direct security considerations. The review process itself is a quality measure to ensure extensions are appropriate and compatible, reducing the risk of incompatible or insecure extensions being registered.
The review does not directly address security, but checking extensions makes the system safer.