draft-ietf-mile-rfc5070-bis-23.txt   draft-ietf-mile-rfc5070-bis-24.txt 
MILE Working Group R. Danyliw MILE Working Group R. Danyliw
Internet-Draft CERT Internet-Draft CERT
Obsoletes: 5070, 6685 (if approved) June 20, 2016 Obsoletes: 5070, 6685 (if approved) June 20, 2016
Intended status: Standards Track Intended status: Standards Track
Expires: December 22, 2016 Expires: December 22, 2016
The Incident Object Description Exchange Format v2 The Incident Object Description Exchange Format v2
draft-ietf-mile-rfc5070-bis-23 draft-ietf-mile-rfc5070-bis-24
Abstract Abstract
The Incident Object Description Exchange Format (IODEF) defines a The Incident Object Description Exchange Format (IODEF) defines a
data representation for security incident reports and indicators data representation for security incident reports and indicators
commonly exchanged by operational security teams for mitigation and commonly exchanged by operational security teams for mitigation and
watch and warning. This document describes an updated information watch and warning. This document describes an updated information
model for the IODEF and provides an associated data model specified model for the IODEF and provides an associated data model specified
with XML Schema. This new information and data model obsoletes with XML Schema. This new information and data model obsoletes
Request for Comment (RFC) 5070 and 6685. Request for Comment (RFC) 5070 and 6685.
skipping to change at page 110, line 43 skipping to change at page 110, line 43
xmlns:iodef="urn:ietf:params:xml:ns:iodef-2.0" xmlns:iodef="urn:ietf:params:xml:ns:iodef-2.0"
xsi:schemaLocation="urn:ietf:params:xmls:schema:iodef-2.0" ...> xsi:schemaLocation="urn:ietf:params:xmls:schema:iodef-2.0" ...>
4.3. Validation 4.3. Validation
IODEF documents MUST be well-formed XML. It is RECOMMENDED that IODEF documents MUST be well-formed XML. It is RECOMMENDED that
recipients validate the document against the schema described in recipients validate the document against the schema described in
Section 8. However, mere conformance to this schema is not Section 8. However, mere conformance to this schema is not
sufficient for a semantically valid IODEF document. The text of sufficient for a semantically valid IODEF document. The text of
Section 3 describes further formatting and constraints; some that Section 3 describes further formatting and constraints; some that
cannot be conveniently encoded in the schema. These MUST must also cannot be conveniently encoded in the schema. These MUST also be
be considered by an IODEF implementation. Furthermore, the considered by an IODEF implementation. Furthermore, the enumerated
enumerated values present in this document are a static list that values present in this document are a static list that will be
will be incomplete over time as select attributes can be extended by incomplete over time as select attributes can be extended by a
a corresponding IANA registry per Section 10.2. Therefore, IODEF corresponding IANA registry per Section 10.2. Therefore, IODEF
implementations MUST periodically update their schema and MAY need to implementations MUST periodically update their schema and MAY need to
update their parsing algorithms to incorporate newly registered update their parsing algorithms to incorporate newly registered
values. values.
4.4. Incompatibilities with v1 4.4. Incompatibilities with v1
The IODEF data model in this document makes a number of changes to The IODEF data model in this document makes a number of changes to
[RFC5070]. These changes were largely additive -- classes and [RFC5070]. These changes were largely additive -- classes and
enumerated values were added. However, some incompatibilities enumerated values were added. However, some incompatibilities
between [RFC5070] and this new specification were introduced. These between [RFC5070] and this new specification were introduced. These
 End of changes. 2 change blocks. 
6 lines changed or deleted 6 lines changed or added

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