draft-ietf-mile-enum-reference-format-02.txt   draft-ietf-mile-enum-reference-format-03.txt 
INTERNET-DRAFT Adam W. Montville INTERNET-DRAFT Adam W. Montville
Intended Status: Standards Track (CIS) Intended Status: Standards Track (CIS)
Expires: May 2, 2014 David Black Expires: May 11, 2014 David Black
(EMC) (EMC)
November 4, 2013 November 7, 2013
IODEF Enumeration Reference Format IODEF Enumeration Reference Format
draft-ietf-mile-enum-reference-format-02 draft-ietf-mile-enum-reference-format-03
Abstract Abstract
The Incident Object Description Exchange Format [IODEF] provides a The Incident Object Description Exchange Format [IODEF] provides a
Reference class used to reference external entities (such as Reference class used to reference external entities (such as
enumeration identifiers). However, the method of external entity enumeration identifiers). However, the method of external entity
identification has been left unstructured. This document describes a identification has been left unstructured. This document describes a
method to provide structure for referencing external entities for the method to provide structure for referencing external entities for the
[IODEF] Reference class. [IODEF] Reference class.
skipping to change at page 2, line 23 skipping to change at page 2, line 23
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Referencing External Enumerations . . . . . . . . . . . . . . 3 2. Referencing External Enumerations . . . . . . . . . . . . . . 3
3 Security Considerations . . . . . . . . . . . . . . . . . . . . 5 3 Security Considerations . . . . . . . . . . . . . . . . . . . . 5
4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
5 XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5 XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1 Normative References . . . . . . . . . . . . . . . . . . . 6 6.1 Normative References . . . . . . . . . . . . . . . . . . . 7
6.2 Informative References . . . . . . . . . . . . . . . . . . 7 6.2 Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Introduction 1 Introduction
There is an identified need to specify a format to include relevant There is an identified need to specify a format to include relevant
enumeration values in an IODEF document. It is anticipated that this enumeration values in an IODEF document. It is anticipated that this
requirement will exist in other standardization efforts within requirement will exist in other standardization efforts within
several IETF Working Groups, but the scope of this document pertains several IETF Working Groups, but the scope of this document pertains
solely to [IODEF]. solely to [IODEF].
skipping to change at page 4, line 7 skipping to change at page 4, line 7
automation, is important to incident communication and investigation. automation, is important to incident communication and investigation.
Typically, an enumeration identifier is simply an identifier with a Typically, an enumeration identifier is simply an identifier with a
specific format as defined by an external party. specific format as defined by an external party.
2.1 Reference Name Format 2.1 Reference Name Format
The Reference Name Format uses XML to provide the structure for The Reference Name Format uses XML to provide the structure for
enumeration identification, and requires that a specific Abbreviation enumeration identification, and requires that a specific Abbreviation
and RegistryVersion be associated with the ID. An implementer can and RegistryVersion be associated with the ID. An implementer can
look up the ID type (as referenced by the logical tuple of look up the ID type (as referenced by the logical tuple of
Abbreviation and Version) in the IANA table (see Section 4) to Abbreviation and Index) in the IANA table (see Section 4) to
understand how the ID is structured. Multiple registry entries may understand how the ID is structured. Multiple registry entries may
use the same abbreviation. The Index field in the XML unambiguously use the same abbreviation. The Index field in the XML unambiguously
indicates which version of the referenced specification is intended indicates which IANA registry entry is to be used to correctly
without requiring interpretation of version strings that may have reference the enumeration specification, which avoids interpretation
specification-specific formats. of version strings that may have specification-specific formats.
<Reference> <Reference>
<ReferenceName> <ReferenceName>
<EnumRef> <EnumRef>
<Abbreviation>CXI</Abbreviation> <Abbreviation>CXI</Abbreviation>
<Index>1</Index> <Index>1</Index>
<ID>CXI-1234-XYZ</ID> <ID>CXI-1234-XYZ</ID>
</EnumRef> </EnumRef>
</ReferenceName> </ReferenceName>
<URL>http://cxi.example.com</URL> <URL>http://cxi.example.com</URL>
skipping to change at page 5, line 7 skipping to change at page 5, line 7
readily apparent that any standard needing to reference an readily apparent that any standard needing to reference an
enumeration identified by a specially formatted string can use enumeration identified by a specially formatted string can use
this method of providing structure after the standard has been this method of providing structure after the standard has been
published. In effect, this method provides a standardized published. In effect, this method provides a standardized
interface for enumerations, thus allowing a loose coupling between interface for enumerations, thus allowing a loose coupling between
a given standard and the enumeration identifiers it needs to a given standard and the enumeration identifiers it needs to
reference now and in the future. reference now and in the future.
3 Security Considerations 3 Security Considerations
None. Producers of [IODEF] content SHOULD be careful to ensure a proper
mapping of EnumRef ID elements to the correct Index. Potential
consequences of not mapping correctly include inaccurate
information references and similar distribution of misinformation.
Use of EnumRef IDs from trusted sources SHOULD be preferred by
implementers to mitigate the risk of receiving and/or providing
misinformation. Trust decisions with respect to enumeration
reference providers is beyond the scope of this document.
In some cases it might be possible for a third-party to host
content associated with an EnumRef ID. In such a circumstance,
trust SHOULD extend from the origin of the EnumRef ID to the
third-party, effectively making the third-party a trusted third-
party in the context of providing a particular set of EnumRef IDs.
4 IANA Considerations 4 IANA Considerations
This document specifies an identifier format for the [IODEF] This document specifies an identifier format for the [IODEF]
ReferenceName string of the Reference class. ReferenceName string of the Reference class.
This memo creates the following registry for IANA to manage: This memo creates the following registry for IANA to manage:
Name of the Registry: "Enumeration Reference Type Identifiers" Name of the Registry: "Enumeration Reference Type Identifiers"
skipping to change at page 6, line 39 skipping to change at page 7, line 5
<xs:element name="EnumRef"> <xs:element name="EnumRef">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element ref="Abbreviation"/> <xs:element ref="Abbreviation"/>
<xs:element ref="Index"/> <xs:element ref="Index"/>
<xs:element ref="ID"/> <xs:element ref="ID"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:element name="Abbreviation" type="xs:NCName"/> <xs:element name="Abbreviation" type="xs:NCName"/>
<xs:element name="Version" type="xs:integer"/> <xs:element name="Index" type="xs:integer"/>
<xs:element name="ID" type="xs:NCName"/> <xs:element name="ID" type="xs:NCName"/>
</xs:schema> </xs:schema>
LISTING 2: IODEF Enumeration Reference Format Schema LISTING 2: IODEF Enumeration Reference Format Schema
The root element of the XML schema listed here can be contained The root element of the XML schema listed here can be contained
within the IODEF XML as showin in Listing 1 of Section 2.1. within the IODEF XML as showin in Listing 1 of Section 2.1.
6 References 6 References
 End of changes. 8 change blocks. 
11 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/