Skip to main content

Enumeration Reference Format for the Incident Object Description Exchange Format (IODEF)
RFC 7495

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The Incident Object Description Exchange Format (IODEF) is an XML data representation framework for sharing information …
Received changes through RFC Editor sync (changed abstract to 'The Incident Object Description Exchange Format (IODEF) is an XML data representation framework for sharing information about computer security incidents. In IODEF, the Reference class provides references to externally specified information such as a vulnerability, Intrusion Detection System (IDS) alert, malware sample, advisory, or attack technique. In practice, these references are based on external enumeration specifications that define both the enumeration format and the specific enumeration values, but the IODEF Reference class (as specified in IODEF v1 in RFC 5070) does not indicate how to include both of these important pieces of information.

This document establishes a stand-alone data format to include both the external specification and specific enumeration identification value, and establishes an IANA registry to manage external enumeration specifications. While this document does not update IODEF v1, this enumeration reference format is used in IODEF v2 and is applicable to other formats that support this class of enumeration references.')
2015-10-14
(System) Notify list changed from mile-chairs@ietf.org, draft-ietf-mile-enum-reference-format@ietf.org to (None)
2015-03-26
Jean Mahoney Closed request for Last Call review by GENART with state 'No Response'
2015-03-26
(System) IANA registries were updated to include RFC7495
2015-03-25
(System) RFC published