draft-ietf-mile-enum-reference-format-14.txt   rfc7495.txt 
INTERNET-DRAFT Adam W. Montville Internet Engineering Task Force (IETF) A. Montville
Intended Status: Standards Track (CIS) Request for Comments: 7495 CIS
Expires: August 3, 2015 David Black Category: Standards Track D. Black
(EMC) ISSN: 2070-1721 EMC
March 2015
January 30, 2015
IODEF Enumeration Reference Format Enumeration Reference Format
draft-ietf-mile-enum-reference-format-14 for the Incident Object Description Exchange Format (IODEF)
Abstract Abstract
The Incident Object Description Exchange Format (IODEF) is an XML The Incident Object Description Exchange Format (IODEF) is an XML
data representation framework for sharing information about computer data representation framework for sharing information about computer
security incidents. In IODEF, the Reference class provides security incidents. In IODEF, the Reference class provides
references to externally specified information such as a references to externally specified information such as a
vulnerability, Intrusion Detection System (IDS) alert, malware vulnerability, Intrusion Detection System (IDS) alert, malware
sample, advisory, or attack technique. In practice, these references sample, advisory, or attack technique. In practice, these references
are based on external enumeration specifications that define both the are based on external enumeration specifications that define both the
skipping to change at page 1, line 35 skipping to change at page 1, line 34
information. information.
This document establishes a stand-alone data format to include both This document establishes a stand-alone data format to include both
the external specification and specific enumeration identification the external specification and specific enumeration identification
value, and establishes an IANA registry to manage external value, and establishes an IANA registry to manage external
enumeration specifications. While this document does not update enumeration specifications. While this document does not update
IODEF v1, this enumeration reference format is used in IODEF v2 and IODEF v1, this enumeration reference format is used in IODEF v2 and
is applicable to other formats that support this class of enumeration is applicable to other formats that support this class of enumeration
references. references.
Status of this Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months This is an Internet Standards Track document.
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/1id-abstracts.html (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.
The list of Internet-Draft Shadow Directories can be accessed at Information about the current status of this document, any errata,
http://www.ietf.org/shadow.html and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7495.
Copyright and License Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
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 . . . . . . . . . . . . . . . . . . . . 6 2.1. Reference Name Format ......................................4
4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 2.2. Reference Method Applicability .............................5
5 The ReferenceName Schema . . . . . . . . . . . . . . . . . . . . 8 3. Security Considerations .........................................5
6 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations .............................................6
7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. The ReferenceName Schema ........................................8
7.1 Normative References . . . . . . . . . . . . . . . . . . . 9 6. References ......................................................9
7.2 Informative References . . . . . . . . . . . . . . . . . . 10 6.1. Normative References .......................................9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 6.2. Informative References .....................................9
Acknowledgements ..................................................10
Authors' Addresses ................................................10
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 from other data representation formats in an IODEF enumeration values from other data representation formats in an IODEF
document. It is anticipated that this requirement will exist in other document. It is anticipated that this requirement will exist in
standardization efforts within several IETF Working Groups, but the other standardization efforts within several IETF Working Groups, but
scope of this document pertains solely to IODEF. This format is used the scope of this document pertains solely to IODEF. This format is
in IODEF v2 [I-D.draft-ietf-mile-rfc5070-bis] which replaces the used in IODEF v2 [IODEFv2], which will replace the original IODEF v1
original IODEF v1 [IODEF] specification; this document does not [IODEF] specification; this document does not specify use of this
specify use of this format in IODEF v1 [IODEF]. format in IODEF v1 [IODEF].
1.1 Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Referencing External Enumerations 2. Referencing External Enumerations
The need is to place enumeration identifiers and their enumeration The need is to place enumeration identifiers and their enumeration
format references in IODEF's Reference class. There are several ways format references in IODEF's Reference class. There are several ways
to accomplish this goal, but the most appropriate at this point is to to accomplish this goal, but the most appropriate at this point is to
require a specific structure for the ReferenceName string of the require a specific structure for the ReferenceName string of the
IODEF Reference class, and use an IANA registry to manage references IODEF Reference class, and use an IANA registry to manage references
to specific enumeration reference formats. to specific enumeration reference formats.
Per IODEF [IODEF] the ReferenceName is of type ML_STRING. This Per IODEF [IODEF], the ReferenceName is of type ML_STRING. This
becomes problematic when specific references, especially enumeration becomes problematic when specific references, especially enumeration
formats such as Common Vulnerability Enumeration [CVE], Common formats such as Common Vulnerability Enumeration [CVE], Common
Configuration Enumeration [CCE], Common Platform Enumeration [CPE] Configuration Enumeration [CCE], Common Platform Enumeration [CPE],
and so on, are referenced - how is an implementer to know which type and so on, are referenced -- how is an implementer to know which type
of reference this is, and thus how to parse it? One solution, of reference this is, and thus how to parse it? One solution,
presented here, is to require that ReferenceName follow a particular presented here, is to require that ReferenceName follow a particular
format. format.
Inclusion of such enumeration values, especially those related to Inclusion of such enumeration values, especially those related to
security automation, is important to incident communication and security automation, is important to incident communication and
investigation. Typically, an enumeration identifier is simply an investigation. Typically, an enumeration identifier is simply an
identifier with a specific format as defined by an external party. identifier with a specific format as defined by an external party.
Further, that enumeration identifier is itself a reference to Further, that enumeration identifier is itself a reference to
specific information associated with the identifier. Thus, the specific information associated with the identifier. Thus, the
ReferenceName is an identifier that is formatted in a specific ReferenceName is an identifier that is formatted in a specific manner
manner, and which identifies some set of associated information. and that identifies some set of associated information.
For example, a vulnerability identifier following the CVE [CVE] For example, a vulnerability identifier following the CVE [CVE]
formatting specification may be: CVE-2014-0001. That identifier is formatting specification may be CVE-2014-0001. That identifier is
formatted in a specific manner and relates to information about a formatted in a specific manner and relates to information about a
specific vulnerability. Communicating the format for the identifier specific vulnerability. Communicating the format for the identifier
is the subject of this document. is the subject of this document.
2.1 Reference Name Format 2.1. Reference Name Format
The ReferenceName class provides the XML representation for The ReferenceName class provides the XML representation for
identifying an enumeration and specifying a value from it. A given identifying an enumeration and specifying a value from it. A given
enumeration is uniquely identified by the specIndex attribute. Each enumeration is uniquely identified by the specIndex attribute. Each
specIndex value corresponds to an entry in the "Enumeration Reference specIndex value corresponds to an entry in the "Enumeration Reference
Type Identifiers" IANA registry (see Section 4). The child ID Type Identifiers" IANA registry (see Section 4). The child ID
element represents a particular value from the corresponding element represents a particular value from the corresponding
enumeration identified by the specIndex attribute. The format of the enumeration identified by the specIndex attribute. The format of the
ID element is described in the IANA registry entry of the ID element is described in the IANA registry entry of the
enumeration. enumeration.
+-------------------------+ +-------------------------+
| ReferenceName | | ReferenceName |
+-------------------------+ +-------------------------+
| INTEGER specIndex |<>----------[ ID ] | INTEGER specIndex |<>----------[ ID ]
+-------------------------+ +-------------------------+
Figure 1: The ReferenceName Class Figure 1: The ReferenceName Class
The aggregate classes that constitute ReferenceName: The aggregate class that constitutes ReferenceName is:
ID ID
One. The identifier assigned to represent the particular One. The identifier assigned to represent the particular
enumeration object being referenced. enumeration object being referenced.
The ReferenceName class has one attribute. The ReferenceName class has one attribute.
specIndex specIndex
Required. INTEGER. Enumeration identifier. This value Required. INTEGER. Enumeration identifier. This value
corresponds to an entry in the "Enumeration Reference Type corresponds to an entry in the "Enumeration Reference Type
Identifiers" IANA registry with an identical SpecIndex value. Identifiers" IANA registry with an identical SpecIndex value.
An example of such a reference is as follows: An example of such a reference is as follows:
<iodef:Reference> <iodef:Reference>
<enum:ReferenceName specIndex="1"> <enum:ReferenceName specIndex="1">
<enum:ID>CXI-1234-XYZ</enum:ID> <enum:ID>CXI-1234-XYZ</enum:ID>
</enum:ReferenceName> </enum:ReferenceName>
<iodef:URL>http://cxi.example.com</iodef:URL> <iodef:URL>http://cxi.example.com</iodef:URL>
<iodef:Description>Foo</iodef:Description> <iodef:Description>Foo</iodef:Description>
</iodef:Reference> </iodef:Reference>
Information in the IANA table (see Section 4) would include: Information in the IANA table (see Section 4) would include:
Full Name: Concept X Identifier Full Name: Concept X Identifier
SpecIndex: 1 SpecIndex: 1
Version: any Version: any
Specification URI: http://cxi.example.com/spec_url Specification URI: http://cxi.example.com/spec_url
2.2 Reference Method Applicability 2.2. Reference Method Applicability
While the scope of this document pertains to IODEF, any standard While the scope of this document pertains to IODEF, any standard
needing to reference an enumeration identified by a specially needing to reference an enumeration identified by a specially
formatted string can use this method of providing structure after formatted string can use this method of providing structure after the
the standard has been published. In effect, this method provides standard has been published. In effect, this method provides a
a standardized interface for enumeration formats, thus allowing a standardized interface for enumeration formats, thus allowing a loose
loose coupling between a given standard and the enumeration coupling between a given standard and the enumeration identifiers it
identifiers it needs to reference now and in the future. needs to reference now and in the future.
3 Security Considerations 3. Security Considerations
Ensuring a proper mapping of enumeration reference ID elements to Ensuring a proper mapping of enumeration reference ID elements to the
the correct SpecIndex is important. Potential consequences of not correct SpecIndex is important. Potential consequences of not
mapping correctly include inaccurate information references and mapping correctly include inaccurate information in references and
similar distribution of misinformation. similar distribution of misinformation.
Use of enumeration reference IDs from trusted sources are Use of enumeration reference IDs from trusted sources is preferred to
preferred to mitigate the risk of receiving and/or providing mitigate the risk of receiving and/or providing misinformation.
misinformation. Trust decisions with respect to enumeration Trust decisions with respect to enumeration reference providers are
reference providers are beyond the scope of this document. beyond the scope of this document. However, receiving an IODEF
However, receiving an IODEF [IODEF] document containing an unknown [IODEF] document containing an unknown ReferenceName (i.e., the
ReferenceName (i.e. the SpecIndex does not exist in the IANA SpecIndex does not exist in the IANA table) may indicate a misled or
table) may indicate a misled or malicious source. malicious source.
This document is establishing a container for publicly available This document establishes a container for publicly available
enumeration values to be included in an IODEF [IODEF] document, enumeration values to be included in an IODEF [IODEF] document, and
and it is important to note the distinction between the it is important to note the distinction between the enumeration
enumeration value's format and the information conveyed by the value's format and the information conveyed by the value itself.
value itself. While the enumeration value may hold information While the enumeration value may hold information deemed to be private
deemed to be private by relying parties, the enumeration format is by relying parties, the enumeration format is likely not subject to
likely not subject to privacy concerns. privacy concerns.
However, if the Reference class includes an enumeration value in However, if the Reference class includes an enumeration value in
combination with other data in an IODEF [IODEF] document, the combination with other data in an IODEF [IODEF] document, the
resulting combination could expose information. An example might resulting combination could expose information. An example might
include attack vectors or system descriptions used in a privacy- include attack vectors or system descriptions used in a privacy-
related incident. As such, the reader is referred to the IODEF related incident. As such, the reader is referred to the IODEF
[IODEF] Security Considerations section, which explicitly covers [IODEF] Security Considerations section, which explicitly covers
protecting IODEF [IODEF] documents in transit and at rest, protecting IODEF [IODEF] documents in transit and at rest, ensuring
ensuring proper recipient authentication, data confidence levels, proper recipient authentication, data confidence levels, underlying
underlying transport security characteristics, and proper use of transport security characteristics, and proper use of IODEF's
IODEF's restriction attribute. restriction attribute.
4 IANA Considerations 4. IANA Considerations
This document specifies an enumeration reference identifier This document specifies an enumeration reference identifier format.
format. All fields, including abbreviation, are mandatory. All fields, including abbreviation, are mandatory.
This document creates the following registry for IANA to manage: Per this document, IANA has created and maintains the following
registry:
Name of the Registry: "Security External Enumeration Registry" Name of the Registry: "Security External Enumeration Registry"
Location of Registry: https://www.iana.org/assignments/sec-ext- Location of Registry: http://www.iana.org/assignments/sec-ext-enum
enum
Fields to record in the registry: Fields to record in the registry:
Full Name: The full name of the enumeration (i.e. the Full Name: The full name of the enumeration (i.e., the
referenced specification) as a string from the printable ASCII referenced specification) as a string from the printable ASCII
character set [RFC0020] with individual embedded spaces character set [RFC20] with individual embedded spaces allowed.
allowed. The ABNF [RFC5234] syntax for this field is: The ABNF [RFC5234] syntax for this field is:
1*VCHAR *(SP 1*VCHAR) FULL-NAME = 1*VCHAR *(SP 1*VCHAR)
Abbreviation: An abbreviation may be an acronym - it consists Abbreviation: An abbreviation may be an acronym -- it consists
of upper-case characters (at least two, upper-case is used to of uppercase characters (at least two). Uppercase is used to
avoid mismatches due to case differences), as specified by this avoid mismatches due to case differences. It is specified by
ABNF [RFC5234] syntax: this ABNF [RFC5234] syntax:
ABBREVIATION = 2*UC-ALPHA ; At least two ABBREVIATION = 2*UC-ALPHA ; At least two
UC-ALPHA = %x41-5A ; A-Z UC-ALPHA = %x41-5A ; A-Z
Multiple registrations MAY use the same Abbreviation but Multiple registrations MAY use the same Abbreviation but
MUST have different Versions. MUST have different Versions.
SpecIndex: This is an IANA-assigned positive integer that SpecIndex: This is an IANA-assigned positive integer that
identifies the registration. The first entry added to this identifies the registration. The first entry added to this
registry uses the value 1, and this value is incremented for registry uses the value 1, and this value is incremented for
each subsequent entry added to the registry. each subsequent entry added to the registry.
Version: The version of the enumeration (i.e. the referenced Version: The version of the enumeration (i.e., the referenced
specification) as a free-form string from the printable ASCII specification) as a free-form string from the printable ASCII
character set [RFC0020] excepting white space, i.e., from VCHAR character set [RFC20] excepting white space, i.e., from VCHAR
as defined in [RFC5234]. Some of the characters allowed in the as defined in [RFC5234]. Some of the characters allowed in the
version string are escaped when that string is used in XML version string are escaped when that string is used in XML
documents (e.g., '<' is represented as &lt;); the registered documents (e.g., '<' is represented as &lt;); the registered
version string contains the unescaped ASCII character in all version string contains the unescaped ASCII character in all
such cases. such cases.
Specification URI/Reference: A list of one or more URIs Specification URI/Reference: A list of one or more URIs
[RFC3986] from which the registered specification can be [RFC3986] from which the registered specification can be
obtained. The registered specification MUST be readily and obtained. The registered specification MUST be readily and
publicly available from that URI. The URI SHOULD be a stable publicly available from that URI. The URI SHOULD be a stable
skipping to change at page 8, line 21 skipping to change at page 7, line 41
The Designated Expert is expected to consult with the MILE (Managed The Designated Expert is expected to consult with the MILE (Managed
Incident Lightweight Exchange) working group or its successor if any Incident Lightweight Exchange) working group or its successor if any
such WG exists (e.g., via email to the working group's mailing list). such WG exists (e.g., via email to the working group's mailing list).
The Designated Expert is expected to review the request and validate The Designated Expert is expected to review the request and validate
the appropriateness of the enumeration for the attribute. This the appropriateness of the enumeration for the attribute. This
review includes review of the specification associated with the review includes review of the specification associated with the
request. request.
The Designated Expert is expected to ensure that the Full Name, The Designated Expert is expected to ensure that the Full Name,
Abbreviation and Version are appropriate and that the information at Abbreviation, and Version are appropriate and that the information at
the Specification URI is sufficient to unambiguously parse the Specification URI is sufficient to unambiguously parse
identifiers based on that specification. Additionally, the Designated identifiers based on that specification. Additionally, the
Expert should prefer short Abbreviations over long ones. Designated Expert should prefer short Abbreviations over long ones.
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. conforming to a registry mechanism described in [RFC3688].
Registration request for the IODEF enumeration reference format Registration for the IODEF enumeration reference format namespace:
namespace:
URI : urn:ietf:params:xml:ns:iodef-enum-1.0 URI: urn:ietf:params:xml:ns:iodef-enum-1.0
Registrant Contact : See the "Authors' Addresses" section of this Registrant Contact: See the "Authors' Addresses" section of this
document. document.
XML : None. XML: None.
Registration request for the IODEF enumeration reference format XML Registration for the IODEF enumeration reference format XML schema:
schema:
URI : urn:ietf:params:xml:schema:iodef-enum-1.0 URI: urn:ietf:params:xml:schema:iodef-enum-1.0
Registrant Contact See the "Authors' Addresses" section of this Registrant Contact: See the "Authors' Addresses" section of this
document. document.
XML : See Section 5, "The ReferenceName Schema", of this document. XML: See Section 5, "The ReferenceName Schema", of this document.
5. The ReferenceName Schema
5 The ReferenceName Schema
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema attributeFormDefault="unqualified" <xs:schema attributeFormDefault="unqualified"
elementFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="urn:ietf:params:xml:ns:iodef-enum-1.0" targetNamespace="urn:ietf:params:xml:ns:iodef-enum-1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:enum="urn:ietf:params:xml:ns:iodef-enum-1.0"> xmlns:enum="urn:ietf:params:xml:ns:iodef-enum-1.0">
<!-- <!--
========================================================== ==========================================================
=== ReferenceName === === ReferenceName ===
skipping to change at page 9, line 27 skipping to change at page 9, line 5
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="ID" type="xs:NCName"/> <xs:element name="ID" type="xs:NCName"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="specIndex" <xs:attribute name="specIndex"
type="xs:integer" use="required"/> type="xs:integer" use="required"/>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
6 Acknowledgements 6. References
The authors would like to thank Eric Burger for the recommendation
to rely on XML, Roman D. Danyliw for his schema contribution and
insight, and Tim Bray, Panos Kampanakis, Barry Leiba, Ted Lemon,
Alexey Melnikov, Kathleen Moriarty, Takeshi Takahashi, Henry S.
Thompson, and David Waltermire for their contributions and
reviews.
7 References
7.1 Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[IODEF] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident [IODEF] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident
Object Description Exchange Format", RFC 5070, December Object Description Exchange Format", RFC 5070, December
2007. 2007, <http://www.rfc-editor.org/info/rfc5070>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66, RFC
RFC 3986, January 2005. 3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>.
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, RFC 5234, January Syntax Specifications: ABNF", STD 68, RFC 5234, January
2008. 2008, <http://www.rfc-editor.org/info/rfc5234>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004, <http://www.rfc-editor.org/info/rfc3688>.
7.2 Informative References 6.2. Informative References
[RFC0020] Cerf, V., "ASCII format for network interchange", RFC 20, [RFC20] Cerf, V., "ASCII format for network interchange", STD 80,
October 1969. RFC 20, October 1969,
<http://www.rfc-editor.org/info/rfc20>.
[I-D.draft-ietf-mile-rfc5070-bis] Danyliw, R., and Stoecker, P., "The [IODEFv2] Danyliw, R. and P. Stoecker, "The Incident Object
Incident Object Description Exchange Format v2", draft- Description Exchange Format v2", Work in Progress,
ietf-mile-rfc5070-bis-10 (work in progress), November draft-ietf-mile-rfc5070-bis-11, March 2015.
2014.
[CCE] http://cce.mitre.org [CCE] The MITRE Corporation, "Common Configuration Enumeration
(CCE): Unique Identifiers for Common System Configuration
Issues", website in "Archive" status,
<http://cce.mitre.org>.
[CPE] http://cpe.mitre.org [CPE] The MITRE Corporation, "CPE - Common Platform
Enumeration", website in "Archive" status,
<http://cpe.mitre.org>.
[CVE] http://cve.mitre.org [CVE] The MITRE Corporation, "CVE - Common Vulnerabilities and
Exposures", <http://cve.mitre.org>.
Acknowledgements
The authors would like to thank Eric Burger for the recommendation to
rely on XML, Roman D. Danyliw for his schema contribution and
insight, and Tim Bray, Panos Kampanakis, Barry Leiba, Ted Lemon,
Alexey Melnikov, Kathleen Moriarty, Takeshi Takahashi, Henry S.
Thompson, and David Waltermire for their contributions and reviews.
Authors' Addresses Authors' Addresses
Adam W. Montville Adam W. Montville
EMail: adam.w.montville@gmail.com EMail: adam.w.montville@gmail.com
David Black David Black
EMC Corporation EMC Corporation
 End of changes. 65 change blocks. 
160 lines changed or deleted 160 lines changed or added

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