draft-ietf-mile-template-02.txt   draft-ietf-mile-template-03.txt 
mile Working Group B. Trammell mile Working Group B. Trammell
Internet-Draft ETH Zurich Internet-Draft ETH Zurich
Intended status: BCP February 17, 2012 Intended status: Informational March 7, 2012
Expires: August 20, 2012 Expires: September 8, 2012
Guidelines for Defining Extensions to IODEF Guidelines for Defining Extensions to IODEF
draft-ietf-mile-template-02.txt draft-ietf-mile-template-03.txt
Abstract Abstract
This document provides guidelines for extensions to IODEF [RFC5070] This document provides guidelines for extensions to IODEF [RFC5070]
for exchange of incident management data, and contains a template for for exchange of incident management data, and contains a template for
Internet-Drafts describing those extensions, in order to ease the Internet-Drafts describing those extensions, in order to ease the
work and improve the quality of extension descriptions. It also work and improve the quality of extension descriptions.
specifies additional Expert Review of XML Schemas used to describe
these extensions.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 20, 2012. This Internet-Draft will expire on September 8, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Applicability of Extensions to IODEF . . . . . . . . . . . . . 3
3. Applicability of Extensions to IODEF . . . . . . . . . . . . . 3 3. Selecting a Mechanism for IODEF Extension . . . . . . . . . . 4
4. Selecting a Mechanism for IODEF Extension . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 7 Appendix A. Document Template . . . . . . . . . . . . . . . . . . 6
Appendix A. Document Template . . . . . . . . . . . . . . . . . . 7 A.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 6
A.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 7 A.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7
A.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 8 A.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 7
A.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 8 A.4. Extension Definition . . . . . . . . . . . . . . . . . . . 7
A.4. Extension Definition . . . . . . . . . . . . . . . . . . . 8 A.4.1. IODEF Data Types . . . . . . . . . . . . . . . . . . . 8
A.4.1. IODEF Data Types . . . . . . . . . . . . . . . . . . . 9 A.5. Security Considerations . . . . . . . . . . . . . . . . . 9
A.5. Security Considerations . . . . . . . . . . . . . . . . . 10 A.6. IANA Considerations . . . . . . . . . . . . . . . . . . . 9
A.6. IANA Considerations . . . . . . . . . . . . . . . . . . . 10 A.7. References . . . . . . . . . . . . . . . . . . . . . . . . 10
A.7. Appendix A: XML Schema Definition for Extension . . . . . 11 A.8. Appendix A: XML Schema Definition for Extension . . . . . 10
A.8. Appendix B: Examples . . . . . . . . . . . . . . . . . . . 11 A.9. Appendix B: Examples . . . . . . . . . . . . . . . . . . . 10
Appendix B. Example Enumerated Type Extension Definition: Appendix B. Example Enumerated Type Extension Definition:
E.164 Address . . . . . . . . . . . . . . . . . . . . 12 E.164 Address . . . . . . . . . . . . . . . . . . . . 11
Appendix C. Example Element Definition: Test . . . . . . . . . . 12 Appendix C. Example Element Definition: Test . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
In the five years since the specification of IODEF [RFC5070], the In the five years since the specification of IODEF [RFC5070], the
threat environment has evolved, as has the practice of cooperative threat environment has evolved, as has the practice of cooperative
network defense. These trends, along with experience gained through network defense. These trends, along with experience gained through
implementation and deployment, have indicated the need to extend implementation and deployment, have indicated the need to extend
IODEF. This document provides guidelines for defining these IODEF. This document provides guidelines for defining these
extensions. It starts by describing the applicability of IODEF extensions. It starts by describing the applicability of IODEF
extensions, and the IODEF extension mechanisms, before providing a extensions, and the IODEF extension mechanisms, before providing a
section Appendix A that is itself designed to be copied out and section Appendix A that is itself designed to be copied out and
filled in as the starting point of an Internet-Draft about an IODEF filled in as the starting point of an Internet-Draft about an IODEF
extension. extension.
Additionally, IODEF extensions through AdditionalData and RecordItem 2. Applicability of Extensions to IODEF
elements, as 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 in Section 6.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. Applicability of Extensions to IODEF
Before deciding to extend IODEF, the first step is to determine Before deciding to extend IODEF, the first step is to determine
whether an IODEF extension is a good fit for a given problem. There whether an IODEF extension is a good fit for a given problem. There
are two sides to this question: are two sides to this question:
1. Does the problem involve the reporting or sharing of information 1. Does the problem involve the reporting or sharing of information
about an incident? "Incident" is not defined in the terminology about an incident? "Incident" is not defined in the terminology
for IODEF, but for purposes of IODEF can be loosely described as for IODEF, but for purposes of IODEF can be loosely described as
"something that happened that has some impact on the information "something that happened that has some impact on the information
security situation of an entity", with quite a bit of leeway for security situation of an entity", with quite a bit of leeway for
interpretation. If the answer to this question is unequivocally interpretation. If the answer to this question is unequivocally
"No", then IODEF is probably not a good choice as a base "No", then IODEF is probably not a good choice as a base
technology for the application area. technology for the application area.
2. Can IODEF adequately represent information about the incident 2. Can IODEF adequately represent information about the incident
without extension? IODEF has a reasonably rich set of incident- without extension? IODEF has a rich set of incident-relevant
relevant classes. If, after examination of the problem area and classes. If, after detailed examination of the problem area and
the IODEF specification, the answer to this question is "Yes", the IODEF specification, the answer to this question is "Yes",
then extension is not necessary. then extension is not necessary.
A non-exhaustive list of good candidate extensions to IODEF includes: A non-exhaustive list of good candidate extensions to IODEF includes:
o Leveraging existing work in describing aspects of incidents to o Leveraging existing work in describing aspects of incidents to
make IODEF more expressive, by standardized reference to external make IODEF more expressive, by standardized reference to external
information bases about incidents and incident-related information information bases about incidents and incident-related information
o Allowing the description of new types of entities (e.g., related o Allowing the description of new types of entities (e.g., related
actors) or new types of characteristics of entities (e.g., actors) or new types of characteristics of entities (e.g.,
information related to financial services) involved in an IODEF information related to financial services) involved in an IODEF
incident report incident report
o Allowing additional semantic or metadata labeling of IODEF o Allowing additional semantic or metadata labeling of IODEF
Documents (e.g., for handling or disposition instructions, or Documents (e.g., for handling or disposition instructions, or
compliance with data protection and data retention regulations) compliance with data protection and data retention regulations)
4. Selecting a Mechanism for IODEF Extension 3. Selecting a Mechanism for IODEF Extension
IODEF was designed to be extended through any combination of: IODEF was designed to be extended through any combination of:
1. extending the enumerated values of Attributes, as per section 5.1 1. extending the enumerated values of Attributes, as per section 5.1
of [RFC5070]; of [RFC5070];
2. class extension through AdditionalData and RecordItem elements, 2. class extension through AdditionalData and RecordItem elements,
as per section 5.2 of [RFC5070]; and/or as per section 5.2 of [RFC5070]; and/or
3. containment of the IODEF-Document element within an external XML 3. containment of the IODEF-Document element within an external XML
Document, itself containing extension data. Document, itself containing extension data.
Note that in this final case, the extension will not be directly Note that in this final case, the extension will not be directly
interoperable with IODEF implementations, and must "unwrap" the IODEF interoperable with IODEF implementations, and must "unwrap" the IODEF
document from its container; nevertheless, this may be appropriate document from its container; nevertheless, this may be appropriate
for certain use cases involving integration with IODEF within for certain use cases involving integration of IODEF within external
external schemas. Extensions using containment of an IODEF-Document schemas. Extensions using containment of an IODEF-Document are not
are not further treated in this document, though the document further treated in this document, though the document template in
template in Appendix A may be of some use in defining them. Appendix A may be of some use in defining them.
Certain attributes containing enumerated values within certain IODEF Certain attributes containing enumerated values within certain IODEF
elements may be extended. For an attribute named "foo", this is elements may be extended. For an attribute named "foo", this is
achieved by giving the value of "foo" as "ext-value", and adding a achieved by giving the value of "foo" as "ext-value", and adding a
new attribute named "ext-foo" containing the extended value. The new attribute named "ext-foo" containing the extended value. The
attributes which can be extended in this way are defined in Section attributes which can be extended this way are limited to the
5.1 of [RFC5070], and limited to the following: following, denoted in 'Element@attribute' format, referencing the
section in which they are defined in [RFC5070]:
o Incident@purpose
o Contact@role
o Contact@type
o RegistryHandle@registry
o Impact@type
o TimeImpact@metric
o TimeImpact@duration
o HistoryItem@action
o Expectation@action
o System@category
o Counter@type
o Counter@duration
o Address@category
o NodeRole@category
o RecordPattern@type
o RecordPattern@offsetunit
o AdditionalData@dtype
o RecordItem@dtype Incident@purpose, section 3.2
AdditionalData@dtype, section 3.6
Contact@role, section 3.7
Contact@type, section 3.7
RegistryHandle@registry, section 3.7.1
Impact@type, section 3.10.1
TimeImpact@metric, section 3.10.2
TimeImpact@duration, section 3.10.2
HistoryItem@action, section 3.11.1
Expectation@action, section 3.13
System@category, section 3.15
Counter@type, section 3.16.1
Counter@duration, section 3.16.1
Address@category, section 3.16.2
NodeRole@category, section 3.16.3
RecordPattern@type>, section 3.19.2
RecordPattern@offsetunit, section 3.19.2
RecordItem@dtype, section 3.19.3
An example definition of an attribute extension is given in An example definition of an attribute extension is given in
Appendix B. Appendix B.
IODEF documents can contain extended scalar or XML data using an IODEF documents can contain extended scalar or XML data using an
AdditionalData element or a RecordItem element. Scalar data AdditionalData element or a RecordItem element. Scalar data
extensions MUST set the "dtype" attribute of the containing element extensions must set the "dtype" attribute of the containing element
to the data type to reference one of the IODEF data types as to the data type to reference one of the IODEF data types as
enumerated in Appendix A.4.1, and SHOULD define the use the "meaning" enumerated in Appendix A.4.1, and should use the "meaning" and
and "formatid" attributes to explain the content of the element. "formatid" attributes to explain the content of the element.
XML extensions within an AdditionalData or RecordItem element use a XML extensions within an AdditionalData or RecordItem element use a
dtype of "xml", and SHOULD define a schema for the root element dtype of "xml", and should define a schema for the topmost containing
within the AdditionalData or RecordItem attribute. An example element within the AdditionalData or RecordItem element. An example
definition of an element definition is given in Appendix C. definition of an element definition is given in Appendix C.
5. Security Considerations 4. Security Considerations
This document defines a template for extensions to IODEF; the This document defines a template for extensions to IODEF; the
security considerations for IODEF [RFC5070] apply. security considerations for IODEF [RFC5070] apply.
6. IANA Considerations 5. IANA Considerations
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]. The IODEF expert(s) for these reviews will
be designated by the IETF Security Area Directors.
[IANA NOTE: The authors request that IANA include a note at the top This document contains no considerations for IANA.
of http://www.iana.org/assignments/xml-registry/schema.html, stating
"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]," and naming the designated expert.]
7. Acknowledgments 6. Acknowledgments
Thanks to David Black, Takeshi Takahashi, Tom Millar, and Kathleen Thanks to David Black, Takeshi Takahashi, Tom Millar, and Kathleen
Moriarty for their comments. This work is materially supported by Moriarty for their comments. This work is materially supported by
the European Union Seventh Framework Program under grant agreement the European Union Seventh Framework Program under grant agreement
257315 (DEMONS). 257315 (DEMONS).
8. References 7. References
8.1. Normative References 7.1. Normative References
[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.
[RFC5070] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident [RFC5070] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident
Object Description Exchange Format", RFC 5070, Object Description Exchange Format", RFC 5070,
December 2007. December 2007.
[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.
[I-D.ietf-mile-rfc6045-bis] [I-D.ietf-mile-rfc6045-bis]
Moriarty, K., "Real-time Inter-network Defense (RID)", Moriarty, K., "Real-time Inter-network Defense (RID)",
draft-ietf-mile-rfc6045-bis-11 (work in progress), draft-ietf-mile-rfc6045-bis-11 (work in progress),
January 2012. January 2012.
8.2. Informative References 7.2. Informative 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.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[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 3986, January 2005. RFC 3986, January 2005.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
October 2008. October 2008.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002. Internet: Timestamps", RFC 3339, July 2002.
skipping to change at page 8, line 19 skipping to change at page 7, line 19
should be referenced in this section, but not redefined or copied. should be referenced in this section, but not redefined or copied.
If [RFC2119] terms are used in the document, this should be noted in If [RFC2119] terms are used in the document, this should be noted in
the terminology section. the terminology section.
A.3. Applicability A.3. Applicability
The applicability section defines the use cases to which the The applicability section defines the use cases to which the
extension is applicable, and details any requirements analysis done extension is applicable, and details any requirements analysis done
during the development of the extension. The primary goal of this during the development of the extension. The primary goal of this
section is to allow readers to see if an extension is indeed intended section is to allow readers to see if an extension is indeed intended
to solve a particular problem. This should also the scope of the to solve a given problem. This should also define and restrict the
extension, as appropriate, by pointing out any non-obvious situations scope of the extension, as appropriate, by pointing out any non-
to which it is not intended to apply. obvious situations to which it is not intended to apply.
In addition to defining the applicability, this section may also In addition to defining the applicability, this section may also
present example situations, which should then be detailed in the present example situations, which should then be detailed in the
examples section, below. examples section, below.
A.4. Extension Definition A.4. Extension Definition
This section defines the extension. This section defines the extension.
Extensions to enumerated types are defined in one subsection for each Extensions to enumerated types are defined in one subsection for each
attribute to be extended, enumerating the new values with an attribute to be extended, enumerating the new values with an
explanation of the meaning of the new value. An example enumeration explanation of the meaning of each new value. An example enumeration
extension is shown in Appendix B, below. extension is shown in Appendix B, below.
Element extensions are defined in one subsection for each element, in Element extensions are defined in one subsection for each element, in
top-down order, from the element contained within AdditionalData or top-down order, from the element contained within AdditionalData or
RecordItem; an example element extension is shown in Appendix C, RecordItem; an example element extension is shown in Appendix C,
below. Each element should be described by a UML diagram as in below. Each element should be described by a UML diagram as in
Figure 1, followed by a description of each of the attributes, and a Figure 1, followed by a description of each of the attributes, and a
short description of each of the child elements. Child elements short description of each of the child elements. Child elements
should then be defined in a subsequent subsection, if not already should then be defined in a subsequent subsection, if not already
defined in the IODEF document itself, or in another referenced MILE defined in the IODEF document itself, or in another referenced IODEF
extension document. extension document.
+---------------------+ +---------------------+
| Element | | Element |
+---------------------+ +---------------------+
| TYPE attribute0 |<>----------[ChildExactlyOne] | TYPE attribute0 |<>----------[ChildExactlyOne]
| TYPE attribute1 |<>--{0..1}--[ChildZeroOrOne] | TYPE attribute1 |<>--{0..1}--[ChildZeroOrOne]
| |<>--{0..*}--[ChildZeroOrMore] | |<>--{0..*}--[ChildZeroOrMore]
| |<>--{1..*}--[ChildOneOrMore] | |<>--{1..*}--[ChildOneOrMore]
+---------------------+ +---------------------+
skipping to change at page 9, line 33 skipping to change at page 8, line 33
section 2 of [RFC5070], and consist of: section 2 of [RFC5070], and consist of:
o INTEGER o INTEGER
o REAL o REAL
o CHARACTER o CHARACTER
o STRING o STRING
o ML_STRING (for strings in encodings other than that of the
enclosing document)
o BYTE for bytes or byte vectors in Base 64 encoding o BYTE for bytes or byte vectors in Base 64 encoding
o HEXBIN for bytes in ascii-hexadecimal encoding o HEXBIN for bytes in ascii-hexadecimal encoding
o ENUM for enumerated types; allowable values of the enumeration o ENUM for enumerated types; allowable values of the enumeration
must be defined in the attribute definition must be defined in the attribute definition
o DATETIME for ISO 8601:2000 [RFC3339] encoded timestamps o DATETIME for [RFC3339]-encoded timestamps
o TIMEZONE for timezones as encoded in section 2.9 of [RFC5070]. o TIMEZONE for timezones as described in section 2.9 of [RFC5070].
o PORTLIST for port lists as encoded in section 2.10 of [RFC5070]. o PORTLIST for port lists as described in section 2.10 of [RFC5070].
o POSTAL for postal addresses as defined in section 2.23 of o POSTAL for postal addresses as described in section 2.23 of
[RFC4519]. [RFC4519].
o NAME for names of natural or legal persons as defined in section o NAME for names of natural or legal persons as defined in section
2.3 of [RFC4519]. 2.3 of [RFC4519].
o PHONE for telephone numbers as defined in section 2.35 of o PHONE for telephone numbers as defined in section 2.35 of
[RFC4519]. [RFC4519].
o EMAIL for email addresses as defined in section 3.4.1. of o EMAIL for email addresses as defined in section 3.4.1. of
[RFC5322]. [RFC5322].
o URL for URLs as in [RFC3986]. o URL for URIs as in [RFC3986].
In addition to these simple data types, IODEF provides a compound In addition to these simple data types, IODEF provides a compound
data type for representing network address information. Addresses data type for representing network address information. Addresses
included within an extension element should be represented by included within an extension element should be represented by
containing an IODEF:Address element, which supports IPv4 and containing an IODEF:Address element, which supports IPv4 and IPv6
[RFC4291] IPv6 addresses, as well as MAC, ATM, and BGP autonomous addresses, as well as MAC, ATM, and BGP autonomous system numbers.
system numbers. Application-layer addresses should be represented Application-layer addresses should be represented with the URL simple
with the URL simple attribute type, instead. attribute type, instead.
A.5. Security Considerations A.5. Security Considerations
[SECDIR and RFC-EDITOR NOTE: Despite the title, this section is NOT a [SECDIR and RFC-EDITOR NOTE: Despite the title, this section is NOT a
Security Considerations section, rather a template Security Security Considerations section, rather a template Security
Considerations section for future extension documents to be built Considerations section for future extension documents to be built
from this template. See Section 5 for Security Considerations for from this template. See Section 4 for Security Considerations for
this document.] this document.]
Any security considerations [RFC3552] raised by this extension or its Any security considerations [RFC3552] raised by this extension or its
deployment should be detailed in this section. Guidance should focus deployment should be detailed in this section. Guidance should focus
on ensuring the users of this extension do so in a secure fashion, on ensuring the users of this extension do so in a secure fashion,
with special attention to non-obvious implications of the with special attention to non-obvious implications of the
transmission of the information represented by an extension. transmission of the information represented by this extension.
It should also be noted in this section that the security It should also be noted in this section that the security
considerations for IODEF [RFC5070] apply to the extension as well. considerations for IODEF [RFC5070] apply to the extension as well.
A.6. IANA Considerations A.6. IANA Considerations
[IANA and RFC-EDITOR NOTE: Despite the title, this section is NOT an [IANA and RFC-EDITOR NOTE: Despite the title, this section is NOT an
IANA Considerations section, rather a template IANA Considerations IANA Considerations section, rather a template IANA Considerations
section for future extension documents to be built from this section for future extension documents to be built from this
template. See Section 6 for IANA Considerations for this document.] template. See Section 5 for IANA Considerations for this document.]
Any IANA considerations [RFC5226] for the document should be detailed Any IANA considerations [RFC5226] for the document should be detailed
in this section; if none, the section should exist and contain the in this section; if none, the section should exist and contain the
text "this document has no actions for IANA". text "this document has no actions for IANA".
IODEF Extensions which represent an enumeration should reference an IODEF Extensions which represent an enumeration should reference an
existing IANA registry or subregistry for the values of that existing IANA registry or subregistry for the values of that
enumeration. If no such registry exists, this section should define enumeration. If no such registry exists, this section should define
a new registry to hold the enumeration's values, and define the a new registry to hold the enumeration's values, and define the
policies by which additions may be made to the registry. policies by which additions may be made to the registry.
skipping to change at page 11, line 33 skipping to change at page 10, line 30
XML: None XML: None
Registration request for the IODEF My-Extension XML schema: Registration request for the IODEF My-Extension XML schema:
URI: urn:ietf:params:xml:schema:iodef-myextension-1.0 URI: urn:ietf:params:xml:schema:iodef-myextension-1.0
Registrant Contact: Refer here to the authors' addresses section of Registrant Contact: Refer here to the authors' addresses section of
the document, or to an organizational contact in the case of an the document, or to an organizational contact in the case of an
extension supported by an external organization. extension supported by an external organization.
XML: Refer here to the XML Schema in the appendix of the document, XML: Refer here to the XML Schema in Appendix A of the document, or
or to a well-known external reference in the case of an extension to a well-known external reference in the case of an extension with
with an externally-defined schema. an externally-defined schema.
A.7. Appendix A: XML Schema Definition for Extension A.7. References
This section lists RFCs, internet-drafts and other documents
referenced from the extension, split into normative and informative
references.
A.8. Appendix A: XML Schema Definition for Extension
The XML Schema describing the elements defined in the Extension The XML Schema describing the elements defined in the Extension
Defintion section is given here. Each of the examples in section Defintion section is given here. Each of the examples in section
Appendix A.8 should be verified to validate against this schema by Appendix A.9 should be verified to validate against this schema by
automated tools. automated tools.
A.8. Appendix B: Examples A.9. Appendix B: Examples
This section contains example IODEF-Documents illustrating the This section contains example IODEF-Documents illustrating the
extension. If example situations are outlined in the applicability extension. If example situations are outlined in the applicability
section, documents for those examples should be provided in the same section, documents for those examples should be provided in the same
order as in the applicability section. Example documents should be order as in the applicability section. Example documents should be
tested to validate against the schema given in the appendix. tested to validate against the schema given in the appendix.
Appendix B. Example Enumerated Type Extension Definition: E.164 Address Appendix B. Example Enumerated Type Extension Definition: E.164 Address
This example extends the IODEF Address element to support the This example extends the IODEF Address element to support the
 End of changes. 40 change blocks. 
142 lines changed or deleted 97 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/