draft-reschke-xml2rfc-14.txt   draft-reschke-xml2rfc-latest.txt 
Network Working Group J. Reschke Network Working Group J. Reschke
Internet-Draft greenbytes Internet-Draft greenbytes
Obsoletes: 2629 (if approved) January 7, 2015 Obsoletes: 2629 (if approved) April 11, 2024
Intended status: Informational Intended status: Informational
Expires: July 11, 2015 Expires: October 13, 2024
The 'XML2RFC' version 2 Vocabulary The 'XML2RFC' version 2 Vocabulary
draft-reschke-xml2rfc-14 draft-reschke-xml2rfc-latest
Abstract Abstract
This document defines the 'XML2RFC' version 2 vocabulary; an XML- This document defines the 'XML2RFC' version 2 vocabulary; an XML-
based language used for writing RFCs and Internet-Drafts. based language used for writing RFCs and Internet-Drafts.
Version 2 represents the current state of the vocabulary (as Version 2 represents the current state of the vocabulary (as
implemented by several tools and as used by the RFC Editor) around implemented by several tools and as used by the RFC Editor) around
2014. 2014.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
<https://www.ietf.org/mailman/listinfo/xml2rfc>. <https://www.ietf.org/mailman/listinfo/xml2rfc>.
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 https://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 July 11, 2015. This Internet-Draft will expire on October 13, 2024.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2024 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 (https://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. to this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 4 1.1. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 4
2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. <abstract> . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. <abstract> . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. <address> . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. <address> . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. <annotation> . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. <annotation> . . . . . . . . . . . . . . . . . . . . . . 5
2.4. <area> . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.4. <area> . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5. <artwork> . . . . . . . . . . . . . . . . . . . . . . . . 6 2.5. <artwork> . . . . . . . . . . . . . . . . . . . . . . . . 6
2.6. <author> . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.6. <author> . . . . . . . . . . . . . . . . . . . . . . . . 8
2.7. <back> . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.7. <back> . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.8. <c> . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.8. <c> . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.9. <city> . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.9. <city> . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.10. <code> . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.10. <code> . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.11. <country> . . . . . . . . . . . . . . . . . . . . . . . . 11 2.11. <country> . . . . . . . . . . . . . . . . . . . . . . . . 11
2.12. <cref> . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.12. <cref> . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.13. <date> . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.13. <date> . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.14. <email> . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.14. <email> . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.15. <eref> . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.15. <eref> . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.16. <facsimile> . . . . . . . . . . . . . . . . . . . . . . . 13 2.16. <facsimile> . . . . . . . . . . . . . . . . . . . . . . . 13
2.17. <figure> . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.17. <figure> . . . . . . . . . . . . . . . . . . . . . . . . 14
2.18. <format> . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.18. <format> . . . . . . . . . . . . . . . . . . . . . . . . 15
2.19. <front> . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.19. <front> . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.20. <iref> . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.20. <iref> . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.21. <keyword> . . . . . . . . . . . . . . . . . . . . . . . . 17 2.21. <keyword> . . . . . . . . . . . . . . . . . . . . . . . . 17
2.22. <list> . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.22. <list> . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.23. <middle> . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.23. <middle> . . . . . . . . . . . . . . . . . . . . . . . . 20
2.24. <note> . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.24. <note> . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.25. <organization> . . . . . . . . . . . . . . . . . . . . . . 20 2.25. <organization> . . . . . . . . . . . . . . . . . . . . . 20
2.26. <phone> . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.26. <phone> . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.27. <postal> . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.27. <postal> . . . . . . . . . . . . . . . . . . . . . . . . 21
2.28. <postamble> . . . . . . . . . . . . . . . . . . . . . . . 22 2.28. <postamble> . . . . . . . . . . . . . . . . . . . . . . . 22
2.29. <preamble> . . . . . . . . . . . . . . . . . . . . . . . . 22 2.29. <preamble> . . . . . . . . . . . . . . . . . . . . . . . 22
2.30. <reference> . . . . . . . . . . . . . . . . . . . . . . . 23 2.30. <reference> . . . . . . . . . . . . . . . . . . . . . . . 23
2.31. <references> . . . . . . . . . . . . . . . . . . . . . . . 23 2.31. <references> . . . . . . . . . . . . . . . . . . . . . . 23
2.32. <region> . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.32. <region> . . . . . . . . . . . . . . . . . . . . . . . . 24
2.33. <rfc> . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.33. <rfc> . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.34. <section> . . . . . . . . . . . . . . . . . . . . . . . . 28 2.34. <section> . . . . . . . . . . . . . . . . . . . . . . . . 28
2.35. <seriesInfo> . . . . . . . . . . . . . . . . . . . . . . . 29 2.35. <seriesInfo> . . . . . . . . . . . . . . . . . . . . . . 29
2.36. <spanx> . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.36. <spanx> . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.37. <street> . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.37. <street> . . . . . . . . . . . . . . . . . . . . . . . . 31
2.38. <t> . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.38. <t> . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.39. <texttable> . . . . . . . . . . . . . . . . . . . . . . . 31 2.39. <texttable> . . . . . . . . . . . . . . . . . . . . . . . 32
2.40. <title> . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.40. <title> . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.41. <ttcol> . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.41. <ttcol> . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.42. <uri> . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.42. <uri> . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.43. <vspace> . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.43. <vspace> . . . . . . . . . . . . . . . . . . . . . . . . 35
2.44. <workgroup> . . . . . . . . . . . . . . . . . . . . . . . 35 2.44. <workgroup> . . . . . . . . . . . . . . . . . . . . . . . 35
2.45. <xref> . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.45. <xref> . . . . . . . . . . . . . . . . . . . . . . . . . 35
3. Escaping for Use in XML . . . . . . . . . . . . . . . . . . . 37 3. Escaping for Use in XML . . . . . . . . . . . . . . . . . . . 37
4. Special Unicode Code Points . . . . . . . . . . . . . . . . . 37 4. Special Unicode Code Points . . . . . . . . . . . . . . . . . 37
5. Including Files . . . . . . . . . . . . . . . . . . . . . . . 38 5. Including Files . . . . . . . . . . . . . . . . . . . . . . . 38
6. Internationalization Considerations . . . . . . . . . . . . . 39 6. Internationalization Considerations . . . . . . . . . . . . . 39
7. Security Considerations . . . . . . . . . . . . . . . . . . . 39 7. Security Considerations . . . . . . . . . . . . . . . . . . . 39
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40
8.1. Internet Media Type Registration . . . . . . . . . . . . . 39 8.1. Internet Media Type Registration . . . . . . . . . . . . 40
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.1. Normative References . . . . . . . . . . . . . . . . . . . 41 10.1. Normative References . . . . . . . . . . . . . . . . . . 41
10.2. Informative References . . . . . . . . . . . . . . . . . . 41 10.2. Informative References . . . . . . . . . . . . . . . . . 41
Appendix A. Front Page ('Boilerplate') Generation . . . . . . . . 43 Appendix A. Front Page ('Boilerplate') Generation . . . . . . . 45
A.1. The /rfc/@category Attribute . . . . . . . . . . . . . . . 44 A.1. The /rfc/@category Attribute . . . . . . . . . . . . . . 45
A.2. The /rfc/@ipr Attribute . . . . . . . . . . . . . . . . . 44 A.2. The /rfc/@ipr Attribute . . . . . . . . . . . . . . . . . 45
A.2.1. Current Values: '*trust200902' . . . . . . . . . . . . 44 A.2.1. Current Values: '*trust200902' . . . . . . . . . . . 45
A.2.2. Historic Values . . . . . . . . . . . . . . . . . . . 46 A.2.2. Historic Values . . . . . . . . . . . . . . . . . . . 47
A.3. The /rfc/@submissionType Attribute . . . . . . . . . . . . 47 A.3. The /rfc/@submissionType Attribute . . . . . . . . . . . 48
A.4. The /rfc/@consensus Attribute . . . . . . . . . . . . . . 47 A.4. The /rfc/@consensus Attribute . . . . . . . . . . . . . . 48
Appendix B. Changes from RFC 2629 ('v1') . . . . . . . . . . . . 48 Appendix B. Changes from RFC 2629 ('v1') . . . . . . . . . . . . 49
B.1. RNC Schema Differences . . . . . . . . . . . . . . . . . . 48 B.1. RNC Schema Differences . . . . . . . . . . . . . . . . . 49
B.2. Removed Elements . . . . . . . . . . . . . . . . . . . . . 48 B.2. Removed Elements . . . . . . . . . . . . . . . . . . . . 49
B.3. Changed Defaults . . . . . . . . . . . . . . . . . . . . . 48 B.3. Changed Defaults . . . . . . . . . . . . . . . . . . . . 49
B.4. Changed Elements . . . . . . . . . . . . . . . . . . . . . 48 B.4. Changed Elements . . . . . . . . . . . . . . . . . . . . 49
B.5. New Elements . . . . . . . . . . . . . . . . . . . . . . . 49 B.5. New Elements . . . . . . . . . . . . . . . . . . . . . . 50
Appendix C. Relax NG Schema . . . . . . . . . . . . . . . . . . . 49 Appendix C. Relax NG Schema . . . . . . . . . . . . . . . . . . 50
C.1. Checking Validity . . . . . . . . . . . . . . . . . . . . 55 C.1. Checking Validity . . . . . . . . . . . . . . . . . . . . 56
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 67
1. Introduction 1. Introduction
This document describes version 2 ("v2") of the 'XML2RFC' vocabulary; This document describes version 2 ("v2") of the 'XML2RFC' vocabulary;
an XML-based language ('Extensible Markup Language', [XML]) used for an XML-based language ('Extensible Markup Language', [XML]) used for
writing RFCs ([RFC7322]) and Internet-Drafts ([IDGUIDE]). writing RFCs ([RFC7322]) and Internet-Drafts ([IDGUIDE]).
Version 2 represents the current state of the vocabulary (as Version 2 represents the current state of the vocabulary (as
implemented by several tools and as used by the RFC Editor) around implemented by several tools and as used by the RFC Editor) around
2014. 2014.
skipping to change at page 5, line 11 skipping to change at page 4, line 48
Except inside <artwork>, horizontal whitespace and linebreaks are Except inside <artwork>, horizontal whitespace and linebreaks are
collapsed into a single whitespace, and leading and trailing collapsed into a single whitespace, and leading and trailing
whitespace are trimmed off. whitespace are trimmed off.
2.1. <abstract> 2.1. <abstract>
Contains the abstract of the document. The abstract ought to be Contains the abstract of the document. The abstract ought to be
self-contained and thus should not contain references or unexpanded self-contained and thus should not contain references or unexpanded
abbreviations. See Section 4.3 of [RFC7322] for more information. abbreviations. See Section 4.3 of [RFC7322] for more information.
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: Content model:
One or more <t> elements (Section 2.38) One or more <t> elements (Section 2.38)
2.2. <address> 2.2. <address>
Provides address information for the author. Provides address information for the author.
This element appears as a child element of: <author> (Section 2.6). This element appears as a child element of <author> (Section 2.6).
Content model: Content model:
In this order: In this order:
1. One optional <postal> element (Section 2.27) 1. One optional <postal> element (Section 2.27)
2. One optional <phone> element (Section 2.26) 2. One optional <phone> element (Section 2.26)
3. One optional <facsimile> element (Section 2.16) 3. One optional <facsimile> element (Section 2.16)
4. One optional <email> element (Section 2.14) 4. One optional <email> element (Section 2.14)
5. One optional <uri> element (Section 2.42) 5. One optional <uri> element (Section 2.42)
2.3. <annotation> 2.3. <annotation>
Provides additional prose augmenting a bibliographical reference. Provides additional prose augmenting a bibliographical reference.
This element appears as a child element of: <reference> This element appears as a child element of <reference>
(Section 2.30). (Section 2.30).
Content model: Content model:
In any order: In any order:
o Text o Text
o <xref> elements (Section 2.45) o <xref> elements (Section 2.45)
o <eref> elements (Section 2.15) o <eref> elements (Section 2.15)
o <iref> elements (Section 2.20) o <iref> elements (Section 2.20)
o <cref> elements (Section 2.12) o <cref> elements (Section 2.12)
o <spanx> elements (Section 2.36) o <spanx> elements (Section 2.36)
2.4. <area> 2.4. <area>
skipping to change at page 6, line 25 skipping to change at page 6, line 13
relates (currently not used when generating documents). relates (currently not used when generating documents).
The value ought to be either the full name or the abbreviation of one The value ought to be either the full name or the abbreviation of one
of the IETF areas as listed on <http://www.ietf.org/iesg/area.html>. of the IETF areas as listed on <http://www.ietf.org/iesg/area.html>.
The list at the time that this document is being published is: The list at the time that this document is being published is:
"Applications", "app", "General", "gen", "Internet", "int", "Applications", "app", "General", "gen", "Internet", "int",
"Operations and Management", "ops", "Real-time Applications and "Operations and Management", "ops", "Real-time Applications and
Infrastructure", "rai", "Routing", "rtg", "Security", "sec", Infrastructure", "rai", "Routing", "rtg", "Security", "sec",
"Transport", "tsv". "Transport", "tsv".
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: only text content. Content model: only text content.
2.5. <artwork> 2.5. <artwork>
This element allows the inclusion of "artwork" into the document. This element allows the inclusion of "artwork" into the document.
<artwork> is the only element in the vocabulary that provides full <artwork> is the only element in the vocabulary that provides full
control of horizontal whitespace and line breaks, and thus is used control of horizontal whitespace and line breaks, and thus is used
for a variety of things, such as: for a variety of things, such as:
skipping to change at page 7, line 15 skipping to change at page 6, line 51
Alternatively, the "src" attribute allows referencing an external Alternatively, the "src" attribute allows referencing an external
graphics file, such as a bitmap or a vector drawing, using a URI graphics file, such as a bitmap or a vector drawing, using a URI
("Uniform Resource Identifier", [RFC3986]). In this case, the ("Uniform Resource Identifier", [RFC3986]). In this case, the
textual content acts as fallback for output formats that do not textual content acts as fallback for output formats that do not
support graphics, and thus ought to contain either a "line art" support graphics, and thus ought to contain either a "line art"
variant of the graphics, or otherwise prose that describes the variant of the graphics, or otherwise prose that describes the
included image in sufficient detail. Note that RFCs occasionally are included image in sufficient detail. Note that RFCs occasionally are
published with enhanced diagrams; a recent example is [RFC5598]. published with enhanced diagrams; a recent example is [RFC5598].
This element appears as a child element of: <figure> (Section 2.17). This element appears as a child element of <figure> (Section 2.17).
Content model: Content model:
Text Text
2.5.1. 'align' attribute 2.5.1. "align" Attribute
Controls whether the artwork appears left justified (default), Controls whether the artwork appears left justified (default),
centered, or right justified. centered, or right justified.
Allowed values: Allowed values:
o "left" (default) o "left" (default)
o "center" o "center"
o "right" o "right"
2.5.2. 'alt' attribute 2.5.2. "alt" Attribute
Alternative text description of the artwork (not just the caption). Alternative text description of the artwork (not just the caption).
2.5.3. 'height' attribute 2.5.3. "height" Attribute
The suggested height of the graphics included using the "src" The suggested height of the graphics included using the "src"
attribute. attribute.
This attribute is format-dependent and ought to be avoided. This attribute is format-dependent and ought to be avoided.
When generating HTML output, current implementations copy the When generating HTML output, current implementations copy the
attribute "as is". For other output formats it is usually ignored. attribute "as is". For other output formats it is usually ignored.
2.5.4. 'name' attribute 2.5.4. "name" Attribute
A filename suitable for the contents (such as for extraction to a A filename suitable for the contents (such as for extraction to a
local file). local file).
This attribute generally isn't used for document generation, but it This attribute generally isn't used for document generation, but it
can be helpful for other kinds of tools (such as automated syntax can be helpful for other kinds of tools (such as automated syntax
checkers which work by extracting the source code). checkers which work by extracting the source code).
2.5.5. 'src' attribute 2.5.5. "src" Attribute
The URI reference of a graphics file ([RFC3986], Section 4.1). The URI reference of a graphics file ([RFC3986], Section 4.1).
Note that this can be a "data" URI ([RFC2397]) as well; in which case Note that this can be a "data" URI ([RFC2397]) as well; in which case
the graphics file is wholly part of the XML file. the graphics file is wholly part of the XML file.
2.5.6. 'type' attribute 2.5.6. "type" Attribute
Specifies the type of the artwork. Specifies the type of the artwork.
The value either is an Internet Media Type (see [RFC2046]) or a The value either is an Internet Media Type (see [RFC2046]) or a
keyword (such as "abnf"). The set of recognized keywords varies keyword (such as "abnf"). The set of recognized keywords varies
across implementations. across implementations.
How it is used depends on context and application. For instance, a How it is used depends on context and application. For instance, a
formatter can attempt to syntax-highlight code in certain known formatter can attempt to syntax-highlight code in certain known
languages. languages.
2.5.7. 'width' attribute 2.5.7. "width" Attribute
The suggested width of the graphics included using the "src" The suggested width of the graphics included using the "src"
attribute. attribute.
This attribute is format-dependent and ought to be avoided. This attribute is format-dependent and ought to be avoided.
When generating HTML output, current implementations copy the When generating HTML output, current implementations copy the
attribute "as is". For other output formats it is usually ignored. attribute "as is". For other output formats it is usually ignored.
2.5.8. 'xml:space' attribute 2.5.8. "xml:space" Attribute
Determines whitespace handling. Determines whitespace handling.
"preserve" is both the default value and the only meaningful setting "preserve" is both the default value and the only meaningful setting
anyway (because that's what the <artwork> element is for). anyway (because that's what the <artwork> element is for).
See also Section 2.10 of [XML]. See also Section 2.10 of [XML].
Allowed values: Allowed values:
skipping to change at page 9, line 27 skipping to change at page 9, line 17
child element). child element).
Furthermore, the "role" attribute can be used to mark an author as Furthermore, the "role" attribute can be used to mark an author as
"editor". This is reflected both on the front page and in "editor". This is reflected both on the front page and in
bibliographical references. Note that this specification does not bibliographical references. Note that this specification does not
define a precise meaning for the term "editor". define a precise meaning for the term "editor".
See Section "Authors vs. Contributors" of [RFCPOLICY] for more See Section "Authors vs. Contributors" of [RFCPOLICY] for more
information. information.
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: Content model:
In this order: In this order:
1. One optional <organization> element (Section 2.25) 1. One optional <organization> element (Section 2.25)
2. One optional <address> element (Section 2.2) 2. One optional <address> element (Section 2.2)
2.6.1. 'fullname' attribute 2.6.1. "fullname" Attribute
The full name (used in the automatically generated "Author's Address" The full name (used in the automatically generated "Author's Address"
section). section).
2.6.2. 'initials' attribute 2.6.2. "initials" Attribute
Author initials (used on the front page and in references). Author initials (used on the front page and in references).
Initials should be provided as a whitespace separated list of pairs Initials should be provided as a whitespace separated list of pairs
of a letter and a dot. of a letter and a dot.
2.6.3. 'role' attribute 2.6.3. "role" Attribute
Specifies the role the author had in creating the document. Specifies the role the author had in creating the document.
Allowed values: Allowed values:
o "editor" o "editor"
2.6.4. 'surname' attribute 2.6.4. "surname" Attribute
The author's surname (used on the front page and in references). The author's surname (used on the front page and in references).
2.7. <back> 2.7. <back>
Contains the "back" part of the document: the references and Contains the "back" part of the document: the references and
appendices. In <back>, <section> elements indicate appendices. appendices. In <back>, <section> elements indicate appendices.
This element appears as a child element of: <rfc> (Section 2.33). This element appears as a child element of <rfc> (Section 2.33).
Content model: Content model:
In this order: In this order:
1. Optional <references> elements (Section 2.31) 1. Optional <references> elements (Section 2.31)
2. Optional <section> elements (Section 2.34) 2. Optional <section> elements (Section 2.34)
2.8. <c> 2.8. <c>
Provides the content of a cell in a table. Provides the content of a cell in a table.
This element appears as a child element of: <texttable> This element appears as a child element of <texttable>
(Section 2.39). (Section 2.39).
Content model: Content model:
In any order: In any order:
o Text o Text
o <xref> elements (Section 2.45) o <xref> elements (Section 2.45)
skipping to change at page 11, line 9 skipping to change at page 10, line 47
o <iref> elements (Section 2.20) o <iref> elements (Section 2.20)
o <cref> elements (Section 2.12) o <cref> elements (Section 2.12)
o <spanx> elements (Section 2.36) o <spanx> elements (Section 2.36)
2.9. <city> 2.9. <city>
Gives the city name in a postal address. Gives the city name in a postal address.
This element appears as a child element of: <postal> (Section 2.27). This element appears as a child element of <postal> (Section 2.27).
Content model: only text content. Content model: only text content.
2.10. <code> 2.10. <code>
Gives the postal region code. Gives the postal region code.
This element appears as a child element of: <postal> (Section 2.27). This element appears as a child element of <postal> (Section 2.27).
Content model: only text content. Content model: only text content.
2.11. <country> 2.11. <country>
Gives the country in a postal address. Gives the country in a postal address.
This element appears as a child element of: <postal> (Section 2.27). This element appears as a child element of <postal> (Section 2.27).
Content model: only text content. Content model: only text content.
2.12. <cref> 2.12. <cref>
Represents a comment. Represents a comment.
Comments can be used in a document while it is work-in-progress. Comments can be used in a document while it is work-in-progress.
They usually appear either inline and visually highlighted, at the They usually appear either inline and visually highlighted, at the
end of the document (depending on file format and settings of the end of the document (depending on file format and settings of the
formatter), or not at all (when generating an RFC). formatter), or not at all (when generating an RFC).
This element appears as a child element of: <annotation> This element appears as a child element of <annotation>
(Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28),
<preamble> (Section 2.29), and <t> (Section 2.38). <preamble> (Section 2.29), and <t> (Section 2.38).
Content model: only text content. Content model: only text content.
2.12.1. 'anchor' attribute 2.12.1. "anchor" Attribute
Document-wide unique identifier for this comment. The processor will Document-wide unique identifier for this comment. The processor will
auto-generate an identifier when none is given. auto-generate an identifier when none is given.
The value needs to be a valid XML "Name" (Section 2.3 of [XML]), The value needs to be a valid XML "Name" (Section 2.3 of [XML]),
additionally constrained to US-ASCII characters ([USASCII]). additionally constrained to US-ASCII characters ([USASCII]).
2.12.2. 'source' attribute 2.12.2. "source" Attribute
Holds the "source" of a comment, such as the name or the initials of Holds the "source" of a comment, such as the name or the initials of
the person who made the comment. the person who made the comment.
2.13. <date> 2.13. <date>
Provides information about the publication date. Provides information about the publication date.
Note that this element is used both for the boilerplate of the Note that this element is used both for the boilerplate of the
document being produced, and also inside bibliographic references. document being produced, and also inside bibliographic references.
skipping to change at page 12, line 35 skipping to change at page 12, line 30
month name ("January", "February", "March", "April", "May, "June", month name ("January", "February", "March", "April", "May, "June",
"July", "August", "September", "October", "November", or "December") "July", "August", "September", "October", "November", or "December")
in order for expiration calculations to work (some implementations in order for expiration calculations to work (some implementations
might support additional formats, though). might support additional formats, though).
In the case of bibliographic references, the date information can In the case of bibliographic references, the date information can
have prose text for the month or year. For example, vague dates have prose text for the month or year. For example, vague dates
(year="ca. 2000"), date ranges (year="2012-2013"), non-specific (year="ca. 2000"), date ranges (year="2012-2013"), non-specific
months (month="Second quarter") and so on, are allowed. months (month="Second quarter") and so on, are allowed.
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: this element does not have any contents. Content model: this element does not have any contents.
2.13.1. 'day' attribute 2.13.1. "day" Attribute
In the "boilerplate" case: the day of publication; this is a number. In the "boilerplate" case: the day of publication; this is a number.
Otherwise: an indication of the publication day, with the format not Otherwise: an indication of the publication day, with the format not
being restricted. being restricted.
2.13.2. 'month' attribute 2.13.2. "month" Attribute
In the "boilerplate" case: the month of publication; this is the In the "boilerplate" case: the month of publication; this is the
English name of the month. Otherwise: an indication of the English name of the month. Otherwise: an indication of the
publication month, with the format not being restricted. publication month, with the format not being restricted.
2.13.3. 'year' attribute 2.13.3. "year" Attribute
In the "boilerplate" case: the year of publication; this is a number In the "boilerplate" case: the year of publication; this is a number
(usually four-digit). Otherwise: an indication of the publication (usually four-digit). Otherwise: an indication of the publication
year, with the format not being restricted. year, with the format not being restricted.
2.14. <email> 2.14. <email>
Provides an email address. Provides an email address.
The value is expected to be the scheme-specific part of a "mailto" The value is expected to be the scheme-specific part of a "mailto"
URI (so does not include the prefix "mailto:"). See Section 2 of URI (so does not include the prefix "mailto:"). See Section 2 of
[RFC6068] for details. [RFC6068] for details.
This element appears as a child element of: <address> (Section 2.2). This element appears as a child element of <address> (Section 2.2).
Content model: only text content. Content model: only text content.
2.15. <eref> 2.15. <eref>
Represents an "external" link (as specified in the "target" Represents an "external" link (as specified in the "target"
attribute). attribute).
If the element has text content, that content will be used. If the element has text content, that content will be used.
Otherwise, the value of the target attribute will be inserted in Otherwise, the value of the target attribute will be inserted in
angle brackets ([RFC3986], Appendix C). angle brackets ([RFC3986], Appendix C).
[[oi-eref: Need to discuss what we can say for non-empty erefs (also [[oi-eref: Need to discuss what we can say for non-empty erefs (also
whether requesting angle brackets is ok for all output formats)]] whether requesting angle brackets is ok for all output formats)]]
This element appears as a child element of: <annotation> This element appears as a child element of <annotation>
(Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28),
<preamble> (Section 2.29), and <t> (Section 2.38). <preamble> (Section 2.29), and <t> (Section 2.38).
Content model: only text content. Content model: only text content.
2.15.1. 'target' attribute (mandatory) 2.15.1. "target" Attribute (Mandatory)
URI of the link target (see Section 3 of [RFC3986]). URI of the link target (see Section 3 of [RFC3986]).
2.16. <facsimile> 2.16. <facsimile>
Represents the phone number of a fax machine. Represents the phone number of a fax machine.
The value is expected to be the scheme-specific part of a "tel" URI The value is expected to be the scheme-specific part of a "tel" URI
(so does not include the prefix "tel:"), using the "global numbers" (so does not include the prefix "tel:"), using the "global numbers"
syntax. See Section 3 of [RFC3966] for details. syntax. See Section 3 of [RFC3966] for details.
This element appears as a child element of: <address> (Section 2.2). This element appears as a child element of <address> (Section 2.2).
Content model: only text content. Content model: only text content.
2.17. <figure> 2.17. <figure>
This element is used to represent a figure, consisting of an optional This element is used to represent a figure, consisting of an optional
preamble, the actual figure, an optional postamble, and an optional preamble, the actual figure, an optional postamble, and an optional
title. title.
This element appears as a child element of: <section> (Section 2.34), This element appears as a child element of <section> (Section 2.34)
and <t> (Section 2.38). and <t> (Section 2.38).
Content model: Content model:
In this order: In this order:
1. Optional <iref> elements (Section 2.20) 1. Optional <iref> elements (Section 2.20)
2. One optional <preamble> element (Section 2.29) 2. One optional <preamble> element (Section 2.29)
3. One <artwork> element (Section 2.5) 3. One <artwork> element (Section 2.5)
4. One optional <postamble> element (Section 2.28) 4. One optional <postamble> element (Section 2.28)
2.17.1. 'align' attribute 2.17.1. "align" Attribute
Used to change the alignment of <preamble> and <postamble>. Used to change the alignment of <preamble> and <postamble>.
Note: does not affect title or <artwork> alignment. Note: does not affect title or <artwork> alignment.
Allowed values: Allowed values:
o "left" (default) o "left" (default)
o "center" o "center"
o "right" o "right"
2.17.2. 'alt' attribute 2.17.2. "alt" Attribute
Duplicates functionality available on <artwork>; avoid it. Duplicates functionality available on <artwork>; avoid it.
2.17.3. 'anchor' attribute 2.17.3. "anchor" Attribute
Document-wide unique identifier for this figure. Document-wide unique identifier for this figure.
Furthermore, the presence of this attribute causes the figure to be Furthermore, the presence of this attribute causes the figure to be
numbered. numbered.
The value needs to be a valid XML "Name" (Section 2.3 of [XML]). The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
2.17.4. 'height' attribute 2.17.4. "height" Attribute
Duplicates functionality available on <artwork>; avoid it. Duplicates functionality available on <artwork>; avoid it.
2.17.5. 'src' attribute 2.17.5. "src" Attribute
Duplicates functionality available on <artwork>; avoid it. Duplicates functionality available on <artwork>; avoid it.
2.17.6. 'suppress-title' attribute 2.17.6. "suppress-title" Attribute
Figures that have an "anchor" attribute will automatically get an Figures that have an "anchor" attribute will automatically get an
autogenerated title (such as "Figure 1"), even if the "title" autogenerated title (such as "Figure 1"), even if the "title"
attribute is absent. Setting this attribute to "true" will prevent attribute is absent. Setting this attribute to "true" will prevent
this. this.
Allowed values: Allowed values:
o "true" o "true"
o "false" (default) o "false" (default)
2.17.7. 'title' attribute 2.17.7. "title" Attribute
The title for the figure; this usually appears on a line after the The title for the figure; this usually appears on a line after the
figure. figure.
2.17.8. 'width' attribute 2.17.8. "width" Attribute
Duplicates functionality available on <artwork>; avoid it. Duplicates functionality available on <artwork>; avoid it.
2.18. <format> 2.18. <format>
Provides a link to an additional format variant for a reference. Provides a link to an additional format variant for a reference.
Note that these additional links are neither used in published RFCs, Note that these additional links are neither used in published RFCs,
nor supported by all tools. If the goal is to provide a single URI nor supported by all tools. If the goal is to provide a single URI
for a reference, the "target" attribute on <reference> can be used for a reference, the "target" attribute on <reference> can be used
instead. instead.
This element appears as a child element of: <reference> This element appears as a child element of <reference>
(Section 2.30). (Section 2.30).
Content model: this element does not have any contents. Content model: this element does not have any contents.
2.18.1. 'octets' attribute 2.18.1. "octets" Attribute
Octet length of linked-to document. Octet length of linked-to document.
2.18.2. 'target' attribute 2.18.2. "target" Attribute
URI of document. URI of document.
2.18.3. 'type' attribute (mandatory) 2.18.3. "type" Attribute (Mandatory)
The type of the linked-to document, such as "TXT", "HTML", or "PDF". The type of the linked-to document, such as "TXT", "HTML", or "PDF".
2.19. <front> 2.19. <front>
Represent the "front matter": metadata (such as author information), Represent the "front matter": metadata (such as author information),
abstract, and additional notes. abstract, and additional notes.
This element appears as a child element of: <reference> This element appears as a child element of <reference> (Section 2.30)
(Section 2.30), and <rfc> (Section 2.33). and <rfc> (Section 2.33).
Content model: Content model:
In this order: In this order:
1. One <title> element (Section 2.40) 1. One <title> element (Section 2.40)
2. One or more <author> elements (Section 2.6) 2. One or more <author> elements (Section 2.6)
3. One <date> element (Section 2.13) 3. One <date> element (Section 2.13)
skipping to change at page 17, line 16 skipping to change at page 17, line 16
regular index entry ("iref element 2.20"). In addition, for each use regular index entry ("iref element 2.20"). In addition, for each use
of that element inside another parent element, a nested entry was of that element inside another parent element, a nested entry was
added ("iref element 2.20, ... inside annotation 2.3"). added ("iref element 2.20, ... inside annotation 2.3").
Index entries generally refer to the exact place where the <iref> Index entries generally refer to the exact place where the <iref>
element occured. An exception is the occurence as a child element of element occured. An exception is the occurence as a child element of
<section>, in which case the whole section is considered to be <section>, in which case the whole section is considered to be
relevant for that index entry. In some formats, index entries of relevant for that index entry. In some formats, index entries of
this type might be displayed as range. this type might be displayed as range.
This element appears as a child element of: <annotation> This element appears as a child element of <annotation>
(Section 2.3), <c> (Section 2.8), <figure> (Section 2.17), (Section 2.3), <c> (Section 2.8), <figure> (Section 2.17),
<postamble> (Section 2.28), <preamble> (Section 2.29), <section> <postamble> (Section 2.28), <preamble> (Section 2.29), <section>
(Section 2.34), and <t> (Section 2.38). (Section 2.34), and <t> (Section 2.38).
Content model: this element does not have any contents. Content model: this element does not have any contents.
2.20.1. 'item' attribute (mandatory) 2.20.1. "item" Attribute (Mandatory)
The item to include. The item to include.
2.20.2. 'primary' attribute 2.20.2. "primary" Attribute
Setting this to "true" declares the occurrence as "primary", which Setting this to "true" declares the occurrence as "primary", which
might cause it to be highlighted in the index. might cause it to be highlighted in the index.
Allowed values: Allowed values:
o "true" o "true"
o "false" (default) o "false" (default)
2.20.3. 'subitem' attribute 2.20.3. "subitem" Attribute
The subitem to include. The subitem to include.
2.21. <keyword> 2.21. <keyword>
Specifies a keyword applicable to the document. Specifies a keyword applicable to the document.
Note that each element should only contain a single keyword; for Note that each element should only contain a single keyword; for
multiple keywords, the element can simply be repeated. multiple keywords, the element can simply be repeated.
Keywords are used both in the RFC Index and in the metadata of Keywords are used both in the RFC Index and in the metadata of
generated documents. generated documents.
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: only text content. Content model: only text content.
2.22. <list> 2.22. <list>
Delineates a text list. Delineates a text list.
Each list item is represented by a <t> element. The vocabulary Each list item is represented by a <t> element. The vocabulary
currently does not directly support list items consisting of multiple currently does not directly support list items consisting of multiple
paragraphs; if this is needed, <vspace> (Section 2.43) can be used as paragraphs; if this is needed, <vspace> (Section 2.43) can be used as
a workaround. a workaround.
This element appears as a child element of: <t> (Section 2.38). This element appears as a child element of <t> (Section 2.38).
Content model: Content model:
One or more <t> elements (Section 2.38) One or more <t> elements (Section 2.38)
2.22.1. 'counter' attribute 2.22.1. "counter" Attribute
This attribute holds a token that serves as an identifier for a This attribute holds a token that serves as an identifier for a
counter. The intended use is continuation of lists, where the counter. The intended use is continuation of lists, where the
counter will be incremented for every list item, and there is no way counter will be incremented for every list item, and there is no way
to reset the counter. to reset the counter.
Note that this attribute functions only when the style attribute is Note that this attribute functions only when the style attribute is
using the "format..." syntax (Section 2.22.3); otherwise, it is using the "format..." syntax (Section 2.22.3); otherwise, it is
ignored. ignored.
2.22.2. 'hangIndent' attribute 2.22.2. "hangIndent" Attribute
For list styles with potentially wide labels, this attribute can For list styles with potentially wide labels, this attribute can
override the default indentation level, measured in number of override the default indentation level, measured in number of
characters. characters.
Note that it only affects style with variable-width labels Note that it only affects style with variable-width labels
("format..." and "hanging", see below), and it may not affect formats ("format..." and "hanging", see below), and it may not affect formats
in which the list item text appears _below_ the label. in which the list item text appears _below_ the label.
2.22.3. 'style' attribute 2.22.3. "style" Attribute
This attribute is used to control the display of a list. This attribute is used to control the display of a list.
The value of this attribute is inherited by any nested lists that do The value of this attribute is inherited by any nested lists that do
not have this attribute set. It may be set to: not have this attribute set. It may be set to:
"empty" "empty"
For unlabeled list items; it can also be used for indentation For unlabeled list items; it can also be used for indentation
purposes (this is the default value when there is an enclosing purposes (this is the default value when there is an enclosing
list where the style is specified). list where the style is specified).
skipping to change at page 20, line 4 skipping to change at page 19, line 49
item counter in various formats. item counter in various formats.
The value is a free-form text that allows counter values to be The value is a free-form text that allows counter values to be
inserted using a "percent-letter" format. For instance, "[REQ%d]" inserted using a "percent-letter" format. For instance, "[REQ%d]"
generates labels of the form "[REQ1]", where "%d" inserts the item generates labels of the form "[REQ1]", where "%d" inserts the item
number as decimal number. number as decimal number.
The following formats are supported: The following formats are supported:
%c lowercase letters (a, b, c, etc.) %c lowercase letters (a, b, c, etc.)
%C uppercase letters (A, B, C, etc.)
%C uppercase letters (A, B, C, etc.)
%d decimal numbers (1, 2, 3, etc.) %d decimal numbers (1, 2, 3, etc.)
%i lowercase Roman numerals (i, ii, iii, etc.) %i lowercase Roman numerals (i, ii, iii, etc.)
%I uppercase Roman numerals (I, II, III, etc.) %I uppercase Roman numerals (I, II, III, etc.)
%% represents a percent sign %% represents a percent sign
Other formats are reserved for future use. Other formats are reserved for future use.
2.23. <middle> 2.23. <middle>
Represents the main content of the document. Represents the main content of the document.
This element appears as a child element of: <rfc> (Section 2.33). This element appears as a child element of <rfc> (Section 2.33).
Content model: Content model:
One or more <section> elements (Section 2.34) One or more <section> elements (Section 2.34)
2.24. <note> 2.24. <note>
Creates an unnumbered section that appears after the abstract. Creates an unnumbered section that appears after the abstract.
It is usually used for additional information to reviewers (working It is usually used for additional information to reviewers (working
group information, mailing list, ...), or for additional publication group information, mailing list, ...), or for additional publication
information such as "IESG Notes". information such as "IESG Notes".
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: Content model:
One or more <t> elements (Section 2.38) One or more <t> elements (Section 2.38)
2.24.1. 'title' attribute (mandatory) 2.24.1. "title" Attribute (Mandatory)
The title of the note. The title of the note.
2.25. <organization> 2.25. <organization>
Specifies the affiliation of an author. Specifies the affiliation of an author.
This information appears in both the "Author's Address" section and This information appears in both the "Author's Address" section and
on the front page (see [RFC7322], Section 4.1.1 for more on the front page (see [RFC7322], Section 4.1.1 for more
information). If the value is long, an abbreviated variant can be information). If the value is long, an abbreviated variant can be
specified in the "abbrev" attribute. specified in the "abbrev" attribute.
This element appears as a child element of: <author> (Section 2.6). This element appears as a child element of <author> (Section 2.6).
Content model: only text content. Content model: only text content.
2.25.1. 'abbrev' attribute 2.25.1. "abbrev" Attribute
Abbreviated variant. Abbreviated variant.
2.26. <phone> 2.26. <phone>
Represents a phone number. Represents a phone number.
The value is expected to be the scheme-specific part of a "tel" URI The value is expected to be the scheme-specific part of a "tel" URI
(so does not include the prefix "tel:"), using the "global numbers" (so does not include the prefix "tel:"), using the "global numbers"
syntax. See Section 3 of [RFC3966] for details. syntax. See Section 3 of [RFC3966] for details.
This element appears as a child element of: <address> (Section 2.2). This element appears as a child element of <address> (Section 2.2).
Content model: only text content. Content model: only text content.
2.27. <postal> 2.27. <postal>
Contains child elements providing postal information. Contains child elements providing postal information.
Note that at least one <street> element needs to be present; however Note that at least one <street> element needs to be present; however
formatters will handle empty values just fine. formatters will handle empty values just fine.
This element appears as a child element of: <address> (Section 2.2). This element appears as a child element of <address> (Section 2.2).
Content model: Content model:
In this order: In this order:
1. One or more <street> elements (Section 2.37) 1. One or more <street> elements (Section 2.37)
2. In any order: 2. In any order:
* <city> elements (Section 2.9) * <city> elements (Section 2.9)
skipping to change at page 22, line 9 skipping to change at page 22, line 9
* <region> elements (Section 2.32) * <region> elements (Section 2.32)
* <code> elements (Section 2.10) * <code> elements (Section 2.10)
* <country> elements (Section 2.11) * <country> elements (Section 2.11)
2.28. <postamble> 2.28. <postamble>
Gives text that appears at the bottom of a figure or table. Gives text that appears at the bottom of a figure or table.
This element appears as a child element of: <figure> (Section 2.17), This element appears as a child element of <figure> (Section 2.17)
and <texttable> (Section 2.39). and <texttable> (Section 2.39).
Content model: Content model:
In any order: In any order:
o Text o Text
o <xref> elements (Section 2.45) o <xref> elements (Section 2.45)
skipping to change at page 22, line 32 skipping to change at page 22, line 32
o <iref> elements (Section 2.20) o <iref> elements (Section 2.20)
o <cref> elements (Section 2.12) o <cref> elements (Section 2.12)
o <spanx> elements (Section 2.36) o <spanx> elements (Section 2.36)
2.29. <preamble> 2.29. <preamble>
Gives text that appears at the top of a figure or table. Gives text that appears at the top of a figure or table.
This element appears as a child element of: <figure> (Section 2.17), This element appears as a child element of <figure> (Section 2.17)
and <texttable> (Section 2.39). and <texttable> (Section 2.39).
Content model: Content model:
In any order: In any order:
o Text o Text
o <xref> elements (Section 2.45) o <xref> elements (Section 2.45)
skipping to change at page 23, line 9 skipping to change at page 23, line 9
o <iref> elements (Section 2.20) o <iref> elements (Section 2.20)
o <cref> elements (Section 2.12) o <cref> elements (Section 2.12)
o <spanx> elements (Section 2.36) o <spanx> elements (Section 2.36)
2.30. <reference> 2.30. <reference>
Represents a bibliographical reference. Represents a bibliographical reference.
This element appears as a child element of: <references> This element appears as a child element of <references>
(Section 2.31). (Section 2.31).
Content model: Content model:
In this order: In this order:
1. One <front> element (Section 2.19) 1. One <front> element (Section 2.19)
2. Optional <seriesInfo> elements (Section 2.35) 2. Optional <seriesInfo> elements (Section 2.35)
3. Optional <format> elements (Section 2.18) 3. Optional <format> elements (Section 2.18)
4. Optional <annotation> elements (Section 2.3) 4. Optional <annotation> elements (Section 2.3)
2.30.1. 'anchor' attribute (mandatory) 2.30.1. "anchor" Attribute
Document-wide unique identifier for this reference. Usually, this Document-wide unique identifier for this reference. Usually, this
will be used both to "label" the reference in the references section, will be used both to "label" the reference in the references section,
and as an identifier in links to this reference entry. and as an identifier in links to this reference entry.
The value needs to be a valid XML "Name" (Section 2.3 of [XML]), The value needs to be a valid XML "Name" (Section 2.3 of [XML]),
additionally constrained to US-ASCII characters ([USASCII]). Thus, additionally constrained to US-ASCII characters ([USASCII]). Thus,
the character repertoire consists of "A-Z", "a-z", "0-9", "_", "-", the character repertoire consists of "A-Z", "a-z", "0-9", "_", "-",
".", and ":", where "0-9", ".", and "-" are disallowed as start ".", and ":", where "0-9", ".", and "-" are disallowed as start
character. character.
2.30.2. 'target' attribute 2.30.2. "target" Attribute
Holds the URI for the reference. Holds the URI for the reference.
Note that depending on the <seriesInfo> element, a URI might not be Note that depending on the <seriesInfo> element, a URI might not be
needed, nor desirable, as it can be automatically generated (for needed, nor desirable, as it can be automatically generated (for
instance, for RFCs). instance, for RFCs).
2.31. <references> 2.31. <references>
Contains a set of bibliographical references. Contains a set of bibliographical references.
In the early days of the RFC series, there was only one "References" In the early days of the RFC series, there was only one "References"
section per RFC. This convention was later changed to group section per RFC. This convention was later changed to group
references into two sets, "Normative" and "Informative" as described references into two sets, "Normative" and "Informative" as described
in Section 4.8.6 of [RFC7322]). This vocabulary supports the split in Section 4.8.6 of [RFC7322]). This vocabulary supports the split
with the "title" attribute. with the "title" attribute.
By default, the order of references is significant. Processors By default, the order of references is significant. Processors
however can be instructed to sort them based on their anchor names. however can be instructed to sort them based on their anchor names.
This element appears as a child element of: <back> (Section 2.7). This element appears as a child element of <back> (Section 2.7).
Content model: Content model:
One or more <reference> elements (Section 2.30) One or more <reference> elements (Section 2.30)
2.31.1. 'title' attribute 2.31.1. "title" Attribute
Provides the title for the References section (defaulting to Provides the title for the References section (defaulting to
"References"). "References").
In general, the title should be either "Normative References" or In general, the title should be either "Normative References" or
"Informative References". "Informative References".
2.32. <region> 2.32. <region>
Provides the region name in a postal address. Provides the region name in a postal address.
This element appears as a child element of: <postal> (Section 2.27). This element appears as a child element of <postal> (Section 2.27).
Content model: only text content. Content model: only text content.
2.33. <rfc> 2.33. <rfc>
This is the root element of the xml2rfc vocabulary. This is the root element of the xml2rfc vocabulary.
Processors distinguish between RFC mode ("number" attribute being Processors distinguish between RFC mode ("number" attribute being
present) and Internet-Draft mode ("docName" attribute being present): present) and Internet-Draft mode ("docName" attribute being present):
it is invalid to specify both. Setting neither "number" nor it is invalid to specify both. Setting neither "number" nor
skipping to change at page 25, line 5 skipping to change at page 25, line 5
Content model: Content model:
In this order: In this order:
1. One <front> element (Section 2.19) 1. One <front> element (Section 2.19)
2. One <middle> element (Section 2.23) 2. One <middle> element (Section 2.23)
3. One optional <back> element (Section 2.7) 3. One optional <back> element (Section 2.7)
2.33.1. 'category' attribute 2.33.1. "category" Attribute
Document category (see Appendix A.1). Document category (see Appendix A.1).
Allowed values: Allowed values:
o "std" o "std"
o "bcp" o "bcp"
o "info" o "info"
o "exp" o "exp"
o "historic" o "historic"
2.33.2. 'consensus' attribute 2.33.2. "consensus" Attribute
Affects the generated boilerplate. Affects the generated boilerplate.
See [RFC5741] for more information. See [RFC5741] for more information.
Allowed values: Allowed values:
o "no" o "no"
o "yes" o "yes"
2.33.3. 'docName' attribute 2.33.3. "docName" Attribute
For Internet-Drafts, this specifies the draft name (which appears For Internet-Drafts, this specifies the draft name (which appears
below the title). below the title).
A processor should give an error if both the "docName" and "number" A processor should give an error if both the "docName" and "number"
attributes are given in the <rfc> element. attributes are given in the <rfc> element.
Note that the file extension is not part of the draft, so in general Note that the file extension is not part of the draft, so in general
it should end with the current draft number ("-", plus two digits). it should end with the current draft number ("-", plus two digits).
Furthermore, it is good practice to disambiguate current editor Furthermore, it is good practice to disambiguate current editor
copies from submitted drafts (for instance, by replacing the draft copies from submitted drafts (for instance, by replacing the draft
number with the string "latest"). number with the string "latest").
See Section 7 of [IDGUIDE] for further information. See Section 7 of [IDGUIDE] for further information.
2.33.4. 'ipr' attribute 2.33.4. "ipr" Attribute
Represents the Intellectual Property status of the document. See Represents the Intellectual Property status of the document. See
Appendix A.2 for details. Appendix A.2 for details.
Allowed values: Allowed values:
o "full2026" o "full2026"
o "noDerivativeWorks2026" o "noDerivativeWorks2026"
skipping to change at page 26, line 44 skipping to change at page 26, line 44
o "noDerivativesTrust200811" o "noDerivativesTrust200811"
o "trust200902" o "trust200902"
o "noModificationTrust200902" o "noModificationTrust200902"
o "noDerivativesTrust200902" o "noDerivativesTrust200902"
o "pre5378Trust200902" o "pre5378Trust200902"
2.33.5. 'iprExtract' attribute 2.33.5. "iprExtract" Attribute
Identifies a single section within the document (by its 'anchor' Identifies a single section within the document (by its 'anchor'
attribute) for which extraction "as-is" is explicitly allowed (this attribute) for which extraction "as-is" is explicitly allowed (this
is only relevant for historic values of the "ipr" attribute). is only relevant for historic values of the "ipr" attribute).
2.33.6. 'number' attribute 2.33.6. "number" Attribute
The number of the RFC to be produced. The number of the RFC to be produced.
A processor should give an error if both the "docName" and "number" A processor should give an error if both the "docName" and "number"
attributes are given in the <rfc> element. attributes are given in the <rfc> element.
2.33.7. 'obsoletes' attribute 2.33.7. "obsoletes" Attribute
A comma-separated list of RFC _numbers_ or Internet-Draft names. A comma-separated list of RFC _numbers_ or Internet-Draft names.
Processors ought to parse the attribute value, so that incorrect Processors ought to parse the attribute value, so that incorrect
references can be detected and, depending on output format, references can be detected and, depending on output format,
hyperlinks can be generated. Also, the value ought to be reformatted hyperlinks can be generated. Also, the value ought to be reformatted
to insert whitespace after each comma if not already present. to insert whitespace after each comma if not already present.
2.33.8. 'seriesNo' attribute 2.33.8. "seriesNo" Attribute
Number within a document series. Number within a document series.
The document series is defined by the "category" attribute; The document series is defined by the "category" attribute;
"seriesNo" is only applicable to the values "info" ("FYI" series), "seriesNo" is only applicable to the values "info" ("FYI" series),
"std" ("STD" series), and "bcp" ("BCP" series). "std" ("STD" series), and "bcp" ("BCP" series).
2.33.9. 'submissionType' attribute 2.33.9. "submissionType" Attribute
The document stream. The document stream.
See Section 2 of [RFC5741] for details. See Section 2 of [RFC5741] for details.
Allowed values: Allowed values:
o "IETF" (default) o "IETF" (default)
o "IAB" o "IAB"
o "IRTF" o "IRTF"
o "independent" o "independent"
2.33.10. 'updates' attribute 2.33.10. "updates" Attribute
A comma-separated list of RFC _numbers_ or Internet-Draft names. A comma-separated list of RFC _numbers_ or Internet-Draft names.
Processors ought to parse the attribute value, so that incorrect Processors ought to parse the attribute value, so that incorrect
references can be detected and, depending on output format, references can be detected and, depending on output format,
hyperlinks can be generated. Also, the value ought to be reformatted hyperlinks can be generated. Also, the value ought to be reformatted
to insert whitespace after each comma if not already present. to insert whitespace after each comma if not already present.
2.33.11. 'xml:lang' attribute 2.33.11. "xml:lang" Attribute
The natural language used in the document (defaults to "en"). The natural language used in the document (defaults to "en").
See Section 2.12 of [XML] for more information. See Section 2.12 of [XML] for more information.
2.34. <section> 2.34. <section>
Represents a section (when inside a <middle> element) or an appendix Represents a section (when inside a <middle> element) or an appendix
(when inside a <back> element). (when inside a <back> element).
Sub-sections are created by nesting <section> elements inside Sub-sections are created by nesting <section> elements inside
<section> elements. <section> elements.
This element appears as a child element of: <back> (Section 2.7), This element appears as a child element of <back> (Section 2.7),
<middle> (Section 2.23), and <section> (Section 2.34). <middle> (Section 2.23), and <section> (Section 2.34).
Content model: Content model:
In this order: In this order:
1. In any order: 1. In any order:
* <t> elements (Section 2.38) * <t> elements (Section 2.38)
* <figure> elements (Section 2.17) * <figure> elements (Section 2.17)
* <texttable> elements (Section 2.39) * <texttable> elements (Section 2.39)
* <iref> elements (Section 2.20) * <iref> elements (Section 2.20)
2. Optional <section> elements (Section 2.34) 2. Optional <section> elements (Section 2.34)
2.34.1. 'anchor' attribute 2.34.1. "anchor" Attribute
Document-wide unique identifier for this section. Document-wide unique identifier for this section.
The value needs to be a valid XML "Name" (Section 2.3 of [XML]). The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
2.34.2. 'title' attribute (mandatory) 2.34.2. "title" Attribute (Mandatory)
The title of the section. The title of the section.
2.34.3. 'toc' attribute 2.34.3. "toc" Attribute
Determines whether the section is included in the Table Of Contents. Determines whether the section is included in the Table Of Contents.
The processor usually has defaults for whether a Table Of Contents The processor usually has defaults for whether a Table Of Contents
will be produced at all, and sections of which maximal depth will be will be produced at all, and sections of which maximal depth will be
included (frequently: 3). "include" and "exclude" allow overriding included (frequently: 3). "include" and "exclude" allow overriding
the processor's default behavior for the element they are specified the processor's default behavior for the element they are specified
on (they do not affect either nested or parent elements). on (they do not affect either nested or parent elements).
Allowed values: Allowed values:
skipping to change at page 29, line 22 skipping to change at page 29, line 28
o "exclude" o "exclude"
o "default" (default) o "default" (default)
2.35. <seriesInfo> 2.35. <seriesInfo>
Specifies the document series in which this document appears, and Specifies the document series in which this document appears, and
also specifies an identifier within that series. also specifies an identifier within that series.
This element appears as a child element of: <reference> This element appears as a child element of <reference>
(Section 2.30). (Section 2.30).
Content model: this element does not have any contents. Content model: this element does not have any contents.
2.35.1. 'name' attribute (mandatory) 2.35.1. "name" Attribute (Mandatory)
The name of the series. The name of the series.
The following names trigger specific processing (such as for auto- The following names trigger specific processing (such as for auto-
generating links, and adding descriptions such as "work in generating links, and adding descriptions such as "work in
progress"): "BCP", "FYI", "Internet-Draft", "RFC", and "STD". progress"): "BCP", "FYI", "Internet-Draft", "RFC", and "STD".
2.35.2. 'value' attribute (mandatory) 2.35.2. "value" Attribute (Mandatory)
The identifier within the series specified by the "name" attribute. The identifier within the series specified by the "name" attribute.
For BCPs, FYIs, RFCs, and STDs this is the number within the series. For BCPs, FYIs, RFCs, and STDs this is the number within the series.
For Internet-Drafts, it is the full draft name (ending with the two- For Internet-Drafts, it is the full draft name (ending with the two-
digit version number). digit version number).
2.36. <spanx> 2.36. <spanx>
Wraps a piece of text, indicating special formatting styles. Wraps a piece of text, indicating special formatting styles.
skipping to change at page 30, line 14 skipping to change at page 30, line 23
emph emph
Simple emphasis (this is the default). Simple emphasis (this is the default).
strong strong
Strong emphasis. Strong emphasis.
verb verb
"Verbatim" text (usually displayed using a monospaced font face). "Verbatim" text (usually displayed using a monospaced font face).
This element appears as a child element of: <annotation> This element appears as a child element of <annotation>
(Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28),
<preamble> (Section 2.29), and <t> (Section 2.38). <preamble> (Section 2.29), and <t> (Section 2.38).
Content model: only text content. Content model: only text content.
2.36.1. 'style' attribute 2.36.1. "style" Attribute
The style to be used (defaults to "emph"). The style to be used (defaults to "emph").
2.36.2. 'xml:space' attribute 2.36.2. "xml:space" Attribute
Determines whitespace handling. Determines whitespace handling.
According to the DTD, the default value is "preserve". Tests however According to the DTD, the default value is "preserve". Tests however
show that it doesn't have any effect on processing; thus this show that it doesn't have any effect on processing; thus this
attribute will be removed in future versions of the vocabulary. attribute will be removed in future versions of the vocabulary.
See also Section 2.10 of [XML]. See also Section 2.10 of [XML].
Allowed values: Allowed values:
o "default" o "default"
o "preserve" (default) o "preserve" (default)
2.37. <street> 2.37. <street>
Provides a street address. Provides a street address.
This element appears as a child element of: <postal> (Section 2.27). This element appears as a child element of <postal> (Section 2.27).
Content model: only text content. Content model: only text content.
2.38. <t> 2.38. <t>
Contains a paragraph of text. Contains a paragraph of text.
This element appears as a child element of: <abstract> (Section 2.1), This element appears as a child element of <abstract> (Section 2.1),
<list> (Section 2.22), <note> (Section 2.24), and <section> <list> (Section 2.22), <note> (Section 2.24), and <section>
(Section 2.34). (Section 2.34).
Content model: Content model:
In any order: In any order:
o Text o Text
o <list> elements (Section 2.22) o <list> elements (Section 2.22)
skipping to change at page 31, line 29 skipping to change at page 31, line 43
o <eref> elements (Section 2.15) o <eref> elements (Section 2.15)
o <iref> elements (Section 2.20) o <iref> elements (Section 2.20)
o <cref> elements (Section 2.12) o <cref> elements (Section 2.12)
o <spanx> elements (Section 2.36) o <spanx> elements (Section 2.36)
o <vspace> elements (Section 2.43) o <vspace> elements (Section 2.43)
2.38.1. 'anchor' attribute 2.38.1. "anchor" Attribute
Document-wide unique identifier for this paragraph. Document-wide unique identifier for this paragraph.
The value needs to be a valid XML "Name" (Section 2.3 of [XML]). The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
2.38.2. 'hangText' attribute 2.38.2. "hangText" Attribute
Holds the label ("hanging text") for items in lists using the Holds the label ("hanging text") for items in lists using the
"hanging" style (see Section 2.22.3). "hanging" style (see Section 2.22.3).
2.39. <texttable> 2.39. <texttable>
Contains a table, consisting of an optional preamble, a header line, Contains a table, consisting of an optional preamble, a header line,
rows, an optional postamble, and an optional title. rows, an optional postamble, and an optional title.
The number of columns in the table is determined by the number of The number of columns in the table is determined by the number of
<ttcol> elements. The number of rows in the table is determined by <ttcol> elements. The number of rows in the table is determined by
the number of <c> elements divided by the number of columns. There the number of <c> elements divided by the number of columns. There
is no requirement that the number of <c> elements be evenly divisible is no requirement that the number of <c> elements be evenly divisible
by the number of columns. by the number of columns.
This element appears as a child element of: <section> (Section 2.34). This element appears as a child element of <section> (Section 2.34).
Content model: Content model:
In this order: In this order:
1. One optional <preamble> element (Section 2.29) 1. One optional <preamble> element (Section 2.29)
2. One or more <ttcol> elements (Section 2.41) 2. One or more <ttcol> elements (Section 2.41)
3. Optional <c> elements (Section 2.8) 3. Optional <c> elements (Section 2.8)
4. One optional <postamble> element (Section 2.28) 4. One optional <postamble> element (Section 2.28)
2.39.1. 'align' attribute 2.39.1. "align" Attribute
Determines the horizontal alignment of the table. Determines the horizontal alignment of the table.
Allowed values: Allowed values:
o "left" o "left"
o "center" (default) o "center" (default)
o "right" o "right"
2.39.2. 'anchor' attribute 2.39.2. "anchor" Attribute
Document-wide unique identifier for this table. Document-wide unique identifier for this table.
Furthermore, the presence of this attribute causes the table to be Furthermore, the presence of this attribute causes the table to be
numbered. numbered.
The value needs to be a valid XML "Name" (Section 2.3 of [XML]). The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
2.39.3. 'style' attribute 2.39.3. "style" Attribute
Selects which borders should be drawn, where Selects which borders should be drawn, where
o "all" means borders around all table cells, o "all" means borders around all table cells,
o "full" is like "all" except no horizontal lines between table rows o "full" is like "all" except no horizontal lines between table rows
(except below the column titles), (except below the column titles),
o "headers" adds just a separator between column titles and rows, o "headers" adds just a separator between column titles and rows,
and and
skipping to change at page 33, line 13 skipping to change at page 33, line 31
Allowed values: Allowed values:
o "all" o "all"
o "none" o "none"
o "headers" o "headers"
o "full" (default) o "full" (default)
2.39.4. 'suppress-title' attribute 2.39.4. "suppress-title" Attribute
Tables that have an "anchor" attribute will automatically get an Tables that have an "anchor" attribute will automatically get an
autogenerated title (such as "Table 1"), even if the "title" autogenerated title (such as "Table 1"), even if the "title"
attribute is absent. Setting this attribute to "true" will prevent attribute is absent. Setting this attribute to "true" will prevent
this. this.
Allowed values: Allowed values:
o "true" o "true"
o "false" (default) o "false" (default)
2.39.5. 'title' attribute 2.39.5. "title" Attribute
The title for the table; this usually appears on a line below the The title for the table; this usually appears on a line below the
table body. table body.
2.40. <title> 2.40. <title>
Represents the document title. Represents the document title.
When this element appears in the <front> element of the current When this element appears in the <front> element of the current
document, the title might also appear in page headers or footers. If document, the title might also appear in page headers or footers. If
it's long (~40 characters), the "abbrev" attribute is used to specify it's long (~40 characters), the "abbrev" attribute is used to specify
an abbreviated variant. an abbreviated variant.
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: only text content. Content model: only text content.
2.40.1. 'abbrev' attribute 2.40.1. "abbrev" Attribute
Specifies an abbreviated variant of the document title. Specifies an abbreviated variant of the document title.
2.41. <ttcol> 2.41. <ttcol>
Contains a column heading in a table. Contains a column heading in a table.
This element appears as a child element of: <texttable> This element appears as a child element of <texttable>
(Section 2.39). (Section 2.39).
Content model: only text content. Content model: only text content.
2.41.1. 'align' attribute 2.41.1. "align" Attribute
Determines the horizontal alignment within the table column. Determines the horizontal alignment within the table column.
Allowed values: Allowed values:
o "left" (default) o "left" (default)
o "center" o "center"
o "right" o "right"
2.41.2. 'width' attribute 2.41.2. "width" Attribute
The desired column width (as integer 0..100 followed by "%"). The desired column width (as integer 0..100 followed by "%").
2.42. <uri> 2.42. <uri>
Contains a web address associated with the author. Contains a web address associated with the author.
The contents should be a valid URI (see Section 3 of [RFC3986]). The contents should be a valid URI (see Section 3 of [RFC3986]).
This element appears as a child element of: <address> (Section 2.2). This element appears as a child element of <address> (Section 2.2).
Content model: only text content. Content model: only text content.
2.43. <vspace> 2.43. <vspace>
This element can be used to force the inclusion of a single line This element can be used to force the inclusion of a single line
break or multiple blank lines. break or multiple blank lines.
Note that this is a purely presentational element and thus its use Note that this is a purely presentational element and thus its use
ought to be avoided. ought to be avoided.
This element appears as a child element of: <t> (Section 2.38). This element appears as a child element of <t> (Section 2.38).
Content model: this element does not have any contents. Content model: this element does not have any contents.
2.43.1. 'blankLines' attribute 2.43.1. "blankLines" Attribute
Number of blank lines to be inserted, where "0" indicates a single Number of blank lines to be inserted, where "0" indicates a single
line break (defaults to "0"). line break (defaults to "0").
For paged output formats, no additional blank lines should be For paged output formats, no additional blank lines should be
generated after a page break. generated after a page break.
2.44. <workgroup> 2.44. <workgroup>
This element is used to specify the Working Group (IETF) or Research This element is used to specify the Working Group (IETF) or Research
Group (IRTF) from which the document originates, if any. The Group (IRTF) from which the document originates, if any. The
recommended format is the official name of the Working Group (with recommended format is the official name of the Working Group (with
some capitalization). some capitalization).
In Internet-Drafts, this is used in the upper left corner of the In Internet-Drafts, this is used in the upper left corner of the
boilerplate, replacing the "Network Working Group" string. boilerplate, replacing the "Network Working Group" string.
Formatting software can append the words "Working Group" or "Research Formatting software can append the words "Working Group" or "Research
Group", depending on the "submissionType" property on the <rfc> Group", depending on the "submissionType" property on the <rfc>
element (Section 2.33.9). element (Section 2.33.9).
This element appears as a child element of: <front> (Section 2.19). This element appears as a child element of <front> (Section 2.19).
Content model: only text content. Content model: only text content.
2.45. <xref> 2.45. <xref>
Inserts a reference to a different part of a document. Inserts a reference to a different part of a document.
The generated text depends on whether the <xref> is empty (in which The generated text depends on whether the <xref> is empty (in which
case the processor will try to generate a meaningful text fragment), case the processor will try to generate a meaningful text fragment),
and the nature of the referenced document part. and the nature of the referenced document part.
skipping to change at page 35, line 42 skipping to change at page 36, line 16
however there are restrictions with respect to the text content being however there are restrictions with respect to the text content being
generated. For instance, a <t> can be a reference target, however, generated. For instance, a <t> can be a reference target, however,
because paragraphs are not (visibly) numbered, the author will have because paragraphs are not (visibly) numbered, the author will have
to make sure that the prose is sufficient for a reader to understand to make sure that the prose is sufficient for a reader to understand
what is being referred to. what is being referred to.
[[oi-xref: This needs to be expanded with examples and with a [[oi-xref: This needs to be expanded with examples and with a
discussion how the autogenerated text differs when <xref> is not discussion how the autogenerated text differs when <xref> is not
empty]] empty]]
This element appears as a child element of: <annotation> This element appears as a child element of <annotation>
(Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28),
<preamble> (Section 2.29), and <t> (Section 2.38). <preamble> (Section 2.29), and <t> (Section 2.38).
Content model: only text content. Content model: only text content.
2.45.1. 'format' attribute 2.45.1. "format" Attribute
This attribute is used to control the format of the generated This attribute is used to control the format of the generated
reference text. reference text.
"counter" "counter"
Inserts a counter, such as the number of a section, figure, or Inserts a counter, such as the number of a section, figure, or
table. table.
For targets that are not inherently numbered, such as references For targets that are not inherently numbered, such as references
skipping to change at page 36, line 31 skipping to change at page 37, line 4
"title" "title"
Inserts a title for the referenced element (usually obtained from Inserts a title for the referenced element (usually obtained from
the referenced element's "title" attribute; some processors also the referenced element's "title" attribute; some processors also
use the <title> child element or a <reference> target). use the <title> child element or a <reference> target).
Allowed values: Allowed values:
o "counter" o "counter"
o "title" o "title"
o "none" o "none"
o "default" (default) o "default" (default)
2.45.2. 'pageno' attribute 2.45.2. "pageno" Attribute
Unused. Unused.
It's unclear what the purpose of this attribute is; processors seem It's unclear what the purpose of this attribute is; processors seem
to ignore it and it never was documented. to ignore it and it never was documented.
Allowed values: Allowed values:
o "true" o "true"
o "false" (default) o "false" (default)
2.45.3. 'target' attribute (mandatory) 2.45.3. "target" Attribute (Mandatory)
Identifies the document component being referenced. Identifies the document component being referenced.
The value needs to match the value of the "anchor" attribute of The value needs to match the value of the "anchor" attribute of
another element in the document. another element in the document.
3. Escaping for Use in XML 3. Escaping for Use in XML
Text in XML cannot use the literal characters "<" and "&", as they Text in XML cannot use the literal characters "<" and "&", as they
have special meaning to the XML processor (starting entities, have special meaning to the XML processor (starting entities,
skipping to change at page 38, line 6 skipping to change at page 38, line 25
Similarly, this represents a hyphen character where nevertheless Similarly, this represents a hyphen character where nevertheless
no line breaking ought to occur. no line breaking ought to occur.
word joiner (U+2060) word joiner (U+2060)
Also called "zero width non-breaking space" -- can be used to Also called "zero width non-breaking space" -- can be used to
disallow line breaking between two non-whitespace characters. disallow line breaking between two non-whitespace characters.
Note that in order to use these characters by name, they need to be Note that in order to use these characters by name, they need to be
declared either in the Document Type Definition (DTD, [XML], Section declared either in the Document Type Definition (DTD, [XML],
2.9), or in the "internal subset" ([XML], Section 2.8), like this: Section 2.9), or in the "internal subset" ([XML], Section 2.8), like
this:
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!-- declare nbsp and friends --> <!-- declare nbsp and friends -->
<!ENTITY nbsp "&#xa0;"> <!ENTITY nbsp "&#xa0;">
<!ENTITY nbhy "&#x2011;"> <!ENTITY nbhy "&#x2011;">
<!ENTITY wj "&#x2060;"> <!ENTITY wj "&#x2060;">
]> ]>
skipping to change at page 40, line 33 skipping to change at page 40, line 51
additional analysis tools. additional analysis tools.
Fragment identifier considerations: The "anchor" attribute is used Fragment identifier considerations: The "anchor" attribute is used
for assigning document-wide unique identifiers that can be used as for assigning document-wide unique identifiers that can be used as
shorthand pointers, as described in Section 2.8 of [XPOINTER]. shorthand pointers, as described in Section 2.8 of [XPOINTER].
Additional information: Additional information:
Deprecated alias names for this type: None. Deprecated alias names for this type: None.
Magic number(s): As specified for "application/xml" in Section Magic number(s): As specified for "application/xml" in
9.1 of [RFC7303]. Section 9.1 of [RFC7303].
File extension(s): .xml or .rfcxml when disambiguation from other File extension(s): .xml or .rfcxml when disambiguation from other
XML files is needed XML files is needed
Macintosh file type code(s): TEXT Macintosh file type code(s): TEXT
Person & email address to contact for further information: See Person & email address to contact for further information: See
Authors Section. Authors Section.
Intended usage: COMMON Intended usage: COMMON
skipping to change at page 41, line 14 skipping to change at page 41, line 28
Change controller: RFC Series Editor (rse@rfc-editor.org) Change controller: RFC Series Editor (rse@rfc-editor.org)
9. Acknowledgments 9. Acknowledgments
Thanks to everybody who reviewed this document and provided feedback Thanks to everybody who reviewed this document and provided feedback
and/or specification text, in particular Brian Carpenter, Elwyn and/or specification text, in particular Brian Carpenter, Elwyn
Davies, Tony Hansen, Paul Hoffman, Henrik Levkowetz, Alice Russo, Tom Davies, Tony Hansen, Paul Hoffman, Henrik Levkowetz, Alice Russo, Tom
Taylor, Jim Schaad, and Nico Williams. Taylor, Jim Schaad, and Nico Williams.
We also thank Marshall T. Rose for both the original design and the We also thank Marshall T. Rose for both the original design and the
reference implementation of the "xml2rfc" formatter. reference implementation of the "xml2rfc" formatter.
10. References 10. References
10.1. Normative References 10.1. Normative References
[XML] Maler, E., Yergeau, F., Paoli, J., Sperberg-McQueen, M., [XML] Maler, E., Yergeau, F., Paoli, J., Sperberg-McQueen, M.,
and T. Bray, "Extensible Markup Language (XML) 1.0 and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth
(Fifth Edition)", W3C Recommendation REC-xml-20081126, Edition)", W3C Recommendation REC-xml-20081126, November
November 2008, 2008, <http://www.w3.org/TR/2008/REC-xml-20081126/>.
<http://www.w3.org/TR/2008/REC-xml-20081126/>.
Latest version available at <http://www.w3.org/TR/xml>. Latest version available at <http://www.w3.org/TR/xml>.
10.2. Informative References 10.2. Informative References
[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type [BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, Specifications and Registration Procedures", BCP 13,
RFC 6838, January 2013. RFC 6838, January 2013,
<https://www.rfc-editor.org/info/bcp13>.
[IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts", [IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts",
December 2010, December 2010,
<http://www.ietf.org/id-info/guidelines.html>. <http://www.ietf.org/id-info/guidelines.html>.
[JING] Thai Open Source Software Center Ltd, "Jing - A RELAX NG [JING] Thai Open Source Software Center Ltd, "Jing - A RELAX NG
validator in Java", 2008, validator in Java", 2008,
<http://www.thaiopensource.com/relaxng/jing.html>. <http://www.thaiopensource.com/relaxng/jing.html>.
Downloads: Downloads: <https://code.google.com/p/jing-
<https://code.google.com/p/jing-trang/downloads/list>. trang/downloads/list>.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<https://www.rfc-editor.org/info/rfc2026>.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996. DOI 10.17487/RFC2046, November 1996,
<https://www.rfc-editor.org/info/rfc2046>.
[RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors",
Authors", RFC 2223, October 1997. RFC 2223, DOI 10.17487/RFC2223, October 1997,
<https://www.rfc-editor.org/info/rfc2223>.
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397,
August 1998. DOI 10.17487/RFC2397, August 1998,
<https://www.rfc-editor.org/info/rfc2397>.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999. DOI 10.17487/RFC2629, June 1999,
<https://www.rfc-editor.org/info/rfc2629>.
[RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for
for the Use of Extensible Markup Language (XML) within the Use of Extensible Markup Language (XML) within IETF
IETF Protocols", BCP 70, RFC 3470, January 2003. Protocols", BCP 70, RFC 3470, DOI 10.17487/RFC3470,
January 2003, <https://www.rfc-editor.org/info/rfc3470>.
[RFC3667] Bradner, S., "IETF Rights in Contributions", RFC 3667, [RFC3667] Bradner, S., "IETF Rights in Contributions", RFC 3667,
February 2004. DOI 10.17487/RFC3667, February 2004,
<https://www.rfc-editor.org/info/rfc3667>.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers",
RFC 3966, December 2004. RFC 3966, DOI 10.17487/RFC3966, December 2004,
<https://www.rfc-editor.org/info/rfc3966>.
[RFC3978] Bradner, S., "IETF Rights in Contributions", RFC 3978, [RFC3978] Bradner, S., "IETF Rights in Contributions", RFC 3978,
March 2005. DOI 10.17487/RFC3978, March 2005,
<https://www.rfc-editor.org/info/rfc3978>.
[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, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
[RFC5598] Crocker, D., "Internet Mail Architecture", RFC 5598, [RFC5598] Crocker, D., "Internet Mail Architecture", RFC 5598,
July 2009. DOI 10.17487/RFC5598, July 2009,
<https://www.rfc-editor.org/info/rfc5598>.
PDF version: <http://www.rfc-editor.org/rfc/rfc5598.pdf> PDF version: <http://www.rfc-editor.org/rfc/rfc5598.pdf>
[RFC5741] Daigle, L. and O. Kolkman, "RFC Streams, Headers, and [RFC5741] Daigle, L. and O. Kolkman, "RFC Streams, Headers, and
Boilerplates", RFC 5741, December 2009. Boilerplates", RFC 5741, DOI 10.17487/RFC5741, December
2009, <https://www.rfc-editor.org/info/rfc5741>.
[RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' [RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto'
URI Scheme", RFC 6068, October 2010. URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010,
<https://www.rfc-editor.org/info/rfc6068>.
[RFC6266] Reschke, J., "Use of the Content-Disposition Header [RFC6266] Reschke, J., "Use of the Content-Disposition Header Field
Field in the Hypertext Transfer Protocol (HTTP)", in the Hypertext Transfer Protocol (HTTP)", RFC 6266,
RFC 6266, June 2011. DOI 10.17487/RFC6266, June 2011,
<https://www.rfc-editor.org/info/rfc6266>.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
July 2014. DOI 10.17487/RFC7303, July 2014,
<https://www.rfc-editor.org/info/rfc7303>.
[RFC7322] Heather, H. and S. Ginoza, "RFC Style Guide", RFC 7322, [RFC7322] Heather, H. and S. Ginoza, "RFC Style Guide", RFC 7322,
September 2014. DOI 10.17487/RFC7322, September 2014,
<https://www.rfc-editor.org/info/rfc7322>.
[RFCPOLICY] RFC Editor, "RFC Editorial Guidelines and Procedures", [RFCPOLICY]
February 2012, <http://www.rfc-editor.org/policy.html>. RFC Editor, "RFC Editorial Guidelines and Procedures",
February 2012, <http://www.rfc-editor.org/policy.html>.
[RNC] Clark, J., "RELAX NG Compact Syntax", OASIS , [RNC] Clark, J., "RELAX NG Compact Syntax", OASIS , November
November 2002, <http://www.oasis-open.org/committees/ 2002, <http://www.oasis-open.org/committees/relax-ng/
relax-ng/compact-20021121.html>. compact-20021121.html>.
[TCLReadme] Rose, M., Fenner, B., and C. Levert, "xml2rfc [TCLReadme]
v1.35pre1", October 2009, <http://svn.tools.ietf.org/ Rose, M., Fenner, B., and C. Levert, "xml2rfc v1.35pre1",
svn/tools/xml2rfc/archive/README.html>. October 2009,
<http://svn.tools.ietf.org/svn/tools/xml2rfc/archive/
README.html>.
[TLP2.0] IETF Trust, "Legal Provisions Relating to IETF [TLP2.0] IETF Trust, "Legal Provisions Relating to IETF Documents",
Documents", February 2009, February 2009,
<http://trustee.ietf.org/license-info/IETF-TLP-2.htm>. <http://trustee.ietf.org/license-info/IETF-TLP-2.htm>.
[TLP3.0] IETF Trust, "Legal Provisions Relating to IETF [TLP3.0] IETF Trust, "Legal Provisions Relating to IETF Documents",
Documents", September 2009, September 2009,
<http://trustee.ietf.org/license-info/IETF-TLP-3.htm>. <http://trustee.ietf.org/license-info/IETF-TLP-3.htm>.
[TLP4.0] IETF Trust, "Legal Provisions Relating to IETF [TLP4.0] IETF Trust, "Legal Provisions Relating to IETF Documents",
Documents", December 2009, December 2009,
<http://trustee.ietf.org/license-info/IETF-TLP-4.htm>. <http://trustee.ietf.org/license-info/IETF-TLP-4.htm>.
[UNICODE] The Unicode Consortium, "The Unicode Standard, Version [UNICODE] The Unicode Consortium, "The Unicode Standard, Version
6.3.0", September 2013, 6.3.0", September 2013,
<http://www.unicode.org/versions/Unicode6.3.0/>. <http://www.unicode.org/versions/Unicode6.3.0/>.
[USASCII] American National Standards Institute, "Coded Character [USASCII] American National Standards Institute, "Coded Character
Set -- 7-bit American Standard Code for Information Set -- 7-bit American Standard Code for Information
Interchange", ANSI X3.4, 1986. Interchange", ANSI X3.4, 1986.
[V1rev] Rose, M., "Writing I-Ds and RFCs using XML (revised)", [V1rev] Rose, M., "Writing I-Ds and RFCs using XML (revised)",
February 2008, <http://svn.tools.ietf.org/svn/tools/ February 2008,
xml2rfc/archive/draft-mrose-writing-rfcs.html>. <http://svn.tools.ietf.org/svn/tools/xml2rfc/archive/
draft-mrose-writing-rfcs.html>.
[XPOINTER] Grosso, P., Maler, E., Marsh, J., and N. Walsh, [XPOINTER]
"XPointer Framework", W3C Recommendation REC-xptr- Grosso, P., Maler, E., Marsh, J., and N. Walsh, "XPointer
framework-20030325, March 2003, Framework", W3C Recommendation REC-xptr-framework-
<http://www.w3.org/TR/2003/ 20030325, March 2003,
REC-xptr-framework-20030325/>. <http://www.w3.org/TR/2003/REC-xptr-framework-20030325/>.
Latest version available at Latest version available at <http://www.w3.org/TR/xptr-
<http://www.w3.org/TR/xptr-framework/>. framework/>.
Appendix A. Front Page ('Boilerplate') Generation Appendix A. Front Page ('Boilerplate') Generation
A.1. The /rfc/@category Attribute A.1. The /rfc/@category Attribute
For RFCs, the category attribute (Section 2.33.1) determines the For RFCs, the category attribute (Section 2.33.1) determines the
"maturity level" (see Section 4 of [RFC2026]). The allowed values "maturity level" (see Section 4 of [RFC2026]). The allowed values
are "std" for "Standards Track", "bcp" for "BCP", "info" for are "std" for "Standards Track", "bcp" for "BCP", "info" for
"Informational", "exp" for "Experimental", and "historic" for "Informational", "exp" for "Experimental", and "historic" for
"Historic". "Historic".
For Internet-Drafts, the category attribute is not needed, but will For Internet-Drafts, the category attribute is not needed, but will
appear on the front page as "Intended Status". Supplying this appear on the front page as "Intended Status". Supplying this
skipping to change at page 46, line 10 skipping to change at page 47, line 13
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) Without obtaining an adequate license from the person(s)
controlling the copyright in such materials, this document may not controlling the copyright in such materials, this document may not
be modified outside the IETF Standards Process, and derivative be modified outside the IETF Standards Process, and derivative
works of it may not be created outside the IETF Standards Process, works of it may not be created outside the IETF Standards Process,
except to format it for publication as an RFC or to translate it except to format it for publication as an RFC or to translate it
into languages other than English. into languages other than English.
See Section 4 of See Section 4 of <http://trustee.ietf.org/docs/IETF-Copyright-
<http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf> for further FAQ.pdf> for further information about when to use this value.
information about when to use this value.
*Note:* this text appears under "Copyright Notice", unless the *Note:* this text appears under "Copyright Notice", unless the
document was published before November 2009, in which case it document was published before November 2009, in which case it
appears under "Status Of This Memo". appears under "Status Of This Memo".
A.2.2. Historic Values A.2.2. Historic Values
A.2.2.1. Historic Values: '*trust200811' A.2.2.1. Historic Values: '*trust200811'
The attribute values "trust200811", "noModificationTrust200811" and The attribute values "trust200811", "noModificationTrust200811" and
"noDerivativesTrust200811" are similar to their "trust200902" "noDerivativesTrust200811" are similar to their "trust200902"
counterparts, except that they use text specified in <http:// counterparts, except that they use text specified in
trustee.ietf.org/license-info/archive/ <http://trustee.ietf.org/license-info/archive/IETF-Trust-License-
IETF-Trust-License-Policy_11-10-08.pdf>. Policy_11-10-08.pdf>.
A.2.2.2. Historic Values: '*3978' A.2.2.2. Historic Values: '*3978'
The attribute values "full3978", "noModification3978" and The attribute values "full3978", "noModification3978" and
"noDerivatives3978" are similar to their counterparts above, except "noDerivatives3978" are similar to their counterparts above, except
that they use text specified in Section 5 of [RFC3978]. that they use text specified in Section 5 of [RFC3978].
A.2.2.3. Historic Values: '*3667' A.2.2.3. Historic Values: '*3667'
The attribute values "full3667", "noModification3667" and The attribute values "full3667", "noModification3667" and
skipping to change at page 48, line 9 skipping to change at page 49, line 9
o "IETF": mention that there was an IETF consensus. o "IETF": mention that there was an IETF consensus.
o "IRTF": mention that there was a research group consensus (where o "IRTF": mention that there was a research group consensus (where
the name of the research group is extracted from the <workgroup> the name of the research group is extracted from the <workgroup>
element). element).
Appendix B. Changes from RFC 2629 ('v1') Appendix B. Changes from RFC 2629 ('v1')
B.1. RNC Schema Differences B.1. RNC Schema Differences
See <http://greenbytes.de/tech/webdav/ This section is to be removed before publishing as an RFC.
draft-reschke-xml2rfc-02.html#rfc.section.E> for a comparison of the
schemata. See <http://greenbytes.de/tech/webdav/draft-reschke-xml2rfc-
02.html#rfc.section.E> for a comparison of the schemata.
B.2. Removed Elements B.2. Removed Elements
The <appendix> element has been removed; to generate an appendix, The <appendix> element has been removed; to generate an appendix,
place a <section> inside <back>. place a <section> inside <back>.
B.3. Changed Defaults B.3. Changed Defaults
Many attributes have lost their "default" value; this is to avoid Many attributes have lost their "default" value; this is to avoid
having document semantics differ based on whether a DTD was specified having document semantics differ based on whether a DTD was specified
skipping to change at page 48, line 49 skipping to change at page 50, line 4
"align", "alt", "width", and "height". (Section 2.17) "align", "alt", "width", and "height". (Section 2.17)
<iref>: Has a new "primary" attribute. (Section 2.20) <iref>: Has a new "primary" attribute. (Section 2.20)
<list>: The "style" attribute isn't restricted to a set of enumerated <list>: The "style" attribute isn't restricted to a set of enumerated
values anymore. The "hangIndent" and "counter" attributes have been values anymore. The "hangIndent" and "counter" attributes have been
added. (Section 2.22) added. (Section 2.22)
<reference>: <annotation> allows adding prose to a reference. The <reference>: <annotation> allows adding prose to a reference. The
"anchor" attribute has been made mandatory. (Section 2.30) "anchor" attribute has been made mandatory. (Section 2.30)
<references>: Can now appear multiple times, and carry a "title" <references>: Can now appear multiple times, and carry a "title"
attribute (so that normative and informative references can be attribute (so that normative and informative references can be
split). (Section 2.31) split). (Section 2.31)
<rfc>: The "ipr" attribute has gained additional values. The <rfc>: The "ipr" attribute has gained additional values. The
attributes "consensus", "iprExtract", "submissionType", and "xml: attributes "consensus", "iprExtract", "submissionType", and
lang" have been added. (Section 2.33) "xml:lang" have been added. (Section 2.33)
<section>: The new "toc" attribute controls whether it will appear in <section>: The new "toc" attribute controls whether it will appear in
the Table Of Contents. <iref> can now appear as direct child element. the Table Of Contents. <iref> can now appear as direct child element.
(Section 2.34) (Section 2.34)
<t>: The "anchor" attribute can now be used as well, however there <t>: The "anchor" attribute can now be used as well, however there
are restrictions on how they can be referred to. (Section 2.38) are restrictions on how they can be referred to. (Section 2.38)
B.5. New Elements B.5. New Elements
The following elements have been added: <annotation> (Section 2.3), The following elements have been added: <annotation> (Section 2.3),
<c> (Section 2.8), <cref> (Section 2.12), <format> (Section 2.18), <c> (Section 2.8), <cref> (Section 2.12), <format> (Section 2.18),
<spanx> (Section 2.36), <texttable> (Section 2.39), <ttcol> <spanx> (Section 2.36), <texttable> (Section 2.39), <ttcol>
(Section 2.41). (Section 2.41).
Appendix C. Relax NG Schema Appendix C. Relax NG Schema
namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0" namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
rfc =
element rfc {
attribute number { text }?,
[ a:defaultValue = "" ] attribute obsoletes { text }?,
[ a:defaultValue = "" ] attribute updates { text }?,
attribute category { "std" | "bcp" | "info" | "exp" | "historic"
}?,
attribute consensus { "no" | "yes" }?,
attribute seriesNo { text }?,
attribute ipr {
"full2026"
| "noDerivativeWorks2026"
| "none"
| "full3667"
| "noModification3667"
| "noDerivatives3667"
| "full3978"
| "noModification3978"
| "noDerivatives3978"
| "trust200811"
| "noModificationTrust200811"
| "noDerivativesTrust200811"
| "trust200902"
| "noModificationTrust200902"
| "noDerivativesTrust200902"
| "pre5378Trust200902"
}?,
attribute iprExtract { xsd:IDREF }?,
[ a:defaultValue = "IETF" ]
attribute submissionType {
"IETF" | "IAB" | "IRTF" | "independent"
}?,
attribute docName { text }?,
[ a:defaultValue = "en" ] attribute xml:lang { text }?,
front,
middle,
back?
}
front = <b>grammar.rfcrfc</b> =
element front { element rfc {
title, author+, date, area*, workgroup*, keyword*, abstract?, attribute number { text }?,
note* [ a:defaultValue = "" ] attribute obsoletes { text }?,
} [ a:defaultValue = "" ] attribute updates { text }?,
attribute category { "std" | "bcp" | "info" | "exp" | "historic"
}?,
attribute consensus { "no" | "yes" }?,
attribute seriesNo { text }?,
attribute ipr {
"full2026"
| "noDerivativeWorks2026"
| "none"
| "full3667"
| "noModification3667"
| "noDerivatives3667"
| "full3978"
| "noModification3978"
| "noDerivatives3978"
| "trust200811"
| "noModificationTrust200811"
| "noDerivativesTrust200811"
| "trust200902"
| "noModificationTrust200902"
| "noDerivativesTrust200902"
| "pre5378Trust200902"
}?,
attribute iprExtract { xsd:IDREF }?,
[ a:defaultValue = "IETF" ]
attribute submissionType {
"IETF" | "IAB" | "IRTF" | "independent"
}?,
attribute docName { text }?,
[ a:defaultValue = "en" ] attribute xml:lang { text }?,
front,
middle,
back?
}
title = <b>grammar.frontfront</b> =
element title { element front {
attribute abbrev { text }?, title, author+, date, area*, workgroup*, keyword*, abstract?,
text note*
} }
author = <b>grammar.titletitle</b> =
element author { element title {
attribute initials { text }?, attribute abbrev { text }?,
attribute surname { text }?, text
attribute fullname { text }?, }
attribute role { "editor" }?,
organization?,
address?
}
organization = <b>grammar.authorauthor</b> =
element organization { element author {
attribute abbrev { text }?, attribute initials { text }?,
text attribute surname { text }?,
} attribute fullname { text }?,
attribute role { "editor" }?,
organization?,
address?
}
address = element address { postal?, phone?, facsimile?, email?, <b>grammar.organizationorganization</b> =
uri? } element organization {
attribute abbrev { text }?,
text
}
postal = element postal { street+, (city | region | code | country)* <b>grammar.addressaddress</b> = element address { postal?, phone?, facsimile?, email?,
} uri? }
street = element street { text } <b>grammar.postalpostal</b> = element postal { street+, (city | region | code | country)*
}
city = element city { text } <b>grammar.streetstreet</b> = element street { text }
region = element region { text } <b>grammar.citycity</b> = element city { text }
code = element code { text } <b>grammar.regionregion</b> = element region { text }
country = element country { text } <b>grammar.codecode</b> = element code { text }
phone = element phone { text } <b>grammar.countrycountry</b> = element country { text }
facsimile = element facsimile { text } <b>grammar.phonephone</b> = element phone { text }
email = element email { text } <b>grammar.facsimilefacsimile</b> = element facsimile { text }
uri = element uri { text } <b>grammar.emailemail</b> = element email { text }
date = <b>grammar.uriuri</b> = element uri { text }
element date {
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
area = element area { text } <b>grammar.datedate</b> =
element date {
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
workgroup = element workgroup { text } <b>grammar.areaarea</b> = element area { text }
keyword = element keyword { text } <b>grammar.workgroupworkgroup</b> = element workgroup { text }
abstract = element abstract { t+ } <b>grammar.keywordkeyword</b> = element keyword { text }
note = <b>grammar.abstractabstract</b> = element abstract { t+ }
element note {
attribute title { text },
t+
}
middle = element middle { section+ } <b>grammar.notenote</b> =
element note {
attribute title { text },
t+
}
section = <b>grammar.middlemiddle</b> = element middle { section+ }
element section {
attribute anchor { xsd:ID }?,
attribute title { text },
[ a:defaultValue = "default" ]
attribute toc { "include" | "exclude" | "default" }?,
(t | figure | texttable | iref)*,
section*
}
t = <b>grammar.sectionsection</b> =
element t { element section {
attribute anchor { xsd:ID }?, attribute anchor { xsd:ID }?,
attribute hangText { text }?, attribute title { text },
(text [ a:defaultValue = "default" ]
| \list attribute toc { "include" | "exclude" | "default" }?,
| figure (t | figure | texttable | iref)*,
| xref section*
| eref }
| iref
| cref
| spanx
| vspace)*
}
\list = <b>grammar.tt</b> =
element list { element t {
attribute style { text }?, attribute anchor { xsd:ID }?,
attribute hangIndent { text }?, attribute hangText { text }?,
attribute counter { text }?, (text
t+ | \list
} | figure
| xref
| eref
| iref
| cref
| spanx
| vspace)*
}
xref = <b>grammar.list\list</b> =
element xref { element list {
attribute target { xsd:IDREF }, attribute style { text }?,
[ a:defaultValue = "false" ] attribute pageno { "true" | "false" attribute hangIndent { text }?,
}?, attribute counter { text }?,
[ a:defaultValue = "default" ] t+
attribute format { "counter" | "title" | "none" | "default" }?, }
text
}
eref = <b>grammar.xrefxref</b> =
element eref { element xref {
attribute target { text }, attribute target { xsd:IDREF },
text [ a:defaultValue = "false" ] attribute pageno { "true" | "false"
} }?,
[ a:defaultValue = "default" ]
attribute format { "counter" | "title" | "none" | "default" }?,
text
}
iref = <b>grammar.ereferef</b> =
element iref { element eref {
attribute item { text }, attribute target { text },
[ a:defaultValue = "" ] attribute subitem { text }?, text
[ a:defaultValue = "false" ] }
attribute primary { "true" | "false" }?,
empty
}
cref = <b>grammar.irefiref</b> =
element cref { element iref {
attribute anchor { xsd:ID }?, attribute item { text },
attribute source { text }?, [ a:defaultValue = "" ] attribute subitem { text }?,
text [ a:defaultValue = "false" ]
} attribute primary { "true" | "false" }?,
empty
}
spanx = <b>grammar.crefcref</b> =
element spanx { element cref {
[ a:defaultValue = "preserve" ] attribute anchor { xsd:ID }?,
attribute xml:space { "default" | "preserve" }?, attribute source { text }?,
[ a:defaultValue = "emph" ] attribute style { text }?, text
text }
}
vspace = <b>grammar.spanxspanx</b> =
element vspace { element spanx {
[ a:defaultValue = "0" ] attribute blankLines { text }?, [ a:defaultValue = "preserve" ]
empty attribute xml:space { "default" | "preserve" }?,
} [ a:defaultValue = "emph" ] attribute style { text }?,
text
}
figure = <b>grammar.vspacevspace</b> =
element figure { element vspace {
attribute anchor { xsd:ID }?, [ a:defaultValue = "0" ] attribute blankLines { text }?,
[ a:defaultValue = "" ] attribute title { text }?, empty
[ a:defaultValue = "false" ] }
attribute suppress-title { "true" | "false" }?,
attribute src { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
iref*,
preamble?,
artwork,
postamble?
}
preamble = <b>grammar.figurefigure</b> =
element preamble { (text | xref | eref | iref | cref | spanx)* } element figure {
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
attribute src { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
iref*,
preamble?,
artwork,
postamble?
}
artwork = <b>grammar.preamblepreamble</b> =
element artwork { element preamble { (text | xref | eref | iref | cref | spanx)* }
[ a:defaultValue = "preserve" ] <b>grammar.artworkartwork</b> =
attribute xml:space { "default" | "preserve" }?, element artwork {
[ a:defaultValue = "" ] attribute name { text }?, [ a:defaultValue = "preserve" ]
[ a:defaultValue = "" ] attribute type { text }?, attribute xml:space { "default" | "preserve" }?,
attribute src { text }?, [ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "left" ] [ a:defaultValue = "" ] attribute type { text }?,
attribute align { "left" | "center" | "right" }?, attribute src { text }?,
[ a:defaultValue = "" ] attribute alt { text }?, [ a:defaultValue = "left" ]
[ a:defaultValue = "" ] attribute width { text }?, attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute height { text }?, [ a:defaultValue = "" ] attribute alt { text }?,
text* [ a:defaultValue = "" ] attribute width { text }?,
} [ a:defaultValue = "" ] attribute height { text }?,
text*
}
postamble = <b>grammar.postamblepostamble</b> =
element postamble { (text | xref | eref | iref | cref | spanx)* } element postamble { (text | xref | eref | iref | cref | spanx)* }
texttable = <b>grammar.texttabletexttable</b> =
element texttable { element texttable {
attribute anchor { xsd:ID }?, attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?, [ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ] [ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?, attribute suppress-title { "true" | "false" }?,
[ a:defaultValue = "center" ] [ a:defaultValue = "center" ]
attribute align { "left" | "center" | "right" }?, attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "full" ] [ a:defaultValue = "full" ]
attribute style { "all" | "none" | "headers" | "full" }?, attribute style { "all" | "none" | "headers" | "full" }?,
preamble?, preamble?,
ttcol+, ttcol+,
c*, c*,
postamble? postamble?
} }
ttcol = <b>grammar.ttcolttcol</b> =
element ttcol { element ttcol {
attribute width { text }?, attribute width { text }?,
[ a:defaultValue = "left" ] [ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?, attribute align { "left" | "center" | "right" }?,
text text
} }
c = element c { (text | xref | eref | iref | cref | spanx)* } <b>grammar.cc</b> = element c { (text | xref | eref | iref | cref | spanx)* }
back = element back { references*, section* } <b>grammar.backback</b> = element back { references*, section* }
references = <b>grammar.referencesreferences</b> =
element references { element references {
[ a:defaultValue = "References" ] attribute title { text }?,
reference+
} [ a:defaultValue = "References" ] attribute title { text }?,
reference+
}
reference = <b>grammar.referencereference</b> =
element reference { element reference {
attribute anchor { xsd:ID }, attribute anchor { xsd:ID }?,
attribute target { text }?, attribute target { text }?,
front, front,
seriesInfo*, seriesInfo*,
format*, format*,
annotation* annotation*
} }
seriesInfo = <b>grammar.seriesInfoseriesInfo</b> =
element seriesInfo { element seriesInfo {
attribute name { text }, attribute name { text },
attribute value { text }, attribute value { text },
empty empty
} }
format = <b>grammar.formatformat</b> =
element format { element format {
attribute target { text }?, attribute target { text }?,
attribute type { text }, attribute type { text },
attribute octets { text }?, attribute octets { text }?,
empty empty
} }
annotation = <b>grammar.annotationannotation</b> =
element annotation { (text | xref | eref | iref | cref | spanx)* } element annotation { (text | xref | eref | iref | cref | spanx)* }
start = rfc <b>grammar.startstart</b> = rfc
(This schema was derived from version 1.3.6 of the xml2rfc DTD (This schema was derived from version 1.3.6 of the xml2rfc DTD
('Document Type Definition', [XML], Section 2.8), available from <htt ('Document Type Definition', [XML], Section 2.8), available from
p://svn.tools.ietf.org/svn/tools/xml2rfc/vocabulary/v2/03/ <http://svn.tools.ietf.org/svn/tools/xml2rfc/vocabulary/v2/03/
xml2rfcv2.dtd>). xml2rfcv2.dtd>).
C.1. Checking Validity C.1. Checking Validity
The validity of XML files can be checked with any tool that supports The validity of XML files can be checked with any tool that supports
Relax NG ([RNC]). The reference implementation is the Java-based, Relax NG ([RNC]). The reference implementation is the Java-based,
open sourced "JING" ([JING]). open sourced "JING" ([JING]).
To use JING, download the latest ZIP file from the "downloads" page To use JING, download the latest ZIP file from the "downloads" page
(currently <https://code.google.com/p/jing-trang/downloads/ (currently <https://code.google.com/p/jing-trang/downloads/
skipping to change at page 56, line 15 skipping to change at page 57, line 17
To check a file "test.xml" using the RNC file "schema.rnc", run (from To check a file "test.xml" using the RNC file "schema.rnc", run (from
a command line prompt): a command line prompt):
java -jar jing.jar -c schema.rnc test.xml java -jar jing.jar -c schema.rnc test.xml
In good Unix tradition, no output means the file is valid. In good Unix tradition, no output means the file is valid.
Index Index
A A
abbrev attribute
in organization element 21
in title element 33
abstract element 5, 49
inside front 16
address element 5, 49
inside author 9
align attribute
in artwork element 7
in figure element 14
in texttable element 32
in ttcol element 34
alt attribute
in artwork element 7
in figure element 14
anchor attribute
in cref element 11
in figure element 14
in reference element 23
in section element 28
in t element 31
in texttable element 32
annotation element 5, 49
inside reference 23
application/rfc+xml Media Type 39
area element 6, 49
inside front 16
artwork element 6, 49
align attribute 7
alt attribute 7
height attribute 7
inside figure 14
name attribute 7
src attribute 8
type attribute 8
width attribute 8
xml:space attribute 8
Attributes Attributes
abbrev 21, 33 abbrev 21, 34
align 7, 14, 32, 34 align 7, 14, 32, 34
alt 7, 14 alt 7, 14
anchor 11, 14, 23, 28, 31-32 anchor 11, 14, 23, 28, 31-32
blankLines 34 blankLines 35
category 25 category 25
consensus 25 consensus 25
counter 18 counter 18
day 12 day 12
docName 25 docName 25
format 35 format 36
fullname 9 fullname 9
hangIndent 18 hangIndent 18
hangText 31 hangText 32
height 7, 15 height 7, 15
initials 9 initials 9
ipr 26 ipr 26
iprExtract 26 iprExtract 26
item 17 item 17
month 12 month 12
name 7, 29 name 7, 29
number 27 number 27
obsoletes 27 obsoletes 27
octets 16 octets 16
pageno 36 pageno 37
primary 17 primary 17
role 9 role 9
seriesNo 27 seriesNo 27
source 12 source 11
src 8, 15 src 7, 15
style 18, 30, 32 style 18, 30, 33
subitem 17 subitem 17
submissionType 27 submissionType 27
suppress-title 15, 33 suppress-title 15, 33
surname 10 surname 9
target 13, 16, 23, 37 target 13, 16, 23, 37
title 15, 20, 24, 28, 33 title 15, 20, 24, 28, 33
toc 28 toc 29
type 8, 16 type 8, 16
updates 27 updates 27
value 29 value 29
width 8, 15, 34 width 8, 15, 34
xml:lang 28 xml:lang 28
xml:space 8, 30 xml:space 8, 30
year 13 year 12
author element 9, 49 abbrev attribute
in organization element 21
in title element 34
abstract element 4, 50
inside front 16
address element 5, 50
inside author 9
align attribute
in artwork element 7
in figure element 14
in texttable element 32
in ttcol element 34
alt attribute
in artwork element 7
in figure element 14
anchor attribute
in cref element 11
in figure element 14
in reference element 23
in section element 28
in t element 31
in texttable element 32
annotation element 5, 50
inside reference 23
application/rfc+xml Media Type 40
area element 5, 50
inside front 16
artwork element 6, 50
align attribute 7
alt attribute 7
height attribute 7
inside figure 14
name attribute 7
src attribute 7
type attribute 8
width attribute 8
xml:space attribute 8
author element 8, 50
fullname attribute 9 fullname attribute 9
initials attribute 9 initials attribute 9
inside front 16 inside front 16
role attribute 9 role attribute 9
surname attribute 10 surname attribute 9
B B
back element 10, 49 back element 10, 50
inside rfc 24 inside rfc 24
blankLines attribute blankLines attribute
in vspace element 34 in vspace element 35
C C
c element 10, 49 c element 10, 50
inside texttable 32 inside texttable 32
category attribute category attribute
in rfc element 25 in rfc element 25
city element 11, 49 city element 10, 50
inside postal 21 inside postal 21
code element 11, 49 code element 11, 50
inside postal 21 inside postal 21
consensus attribute consensus attribute
in rfc element 25 in rfc element 25
counter attribute counter attribute
in list element 18 in list element 18
country element 11, 49 country element 11, 50
inside postal 21 inside postal 21
cref element 11, 49 cref element 11, 50
anchor attribute 11 anchor attribute 11
inside annotation 6 inside annotation 5
inside c 10 inside c 10
inside postamble 22 inside postamble 22
inside preamble 22 inside preamble 22
inside t 31 inside t 31
source attribute 12 source attribute 11
D D
date element 12, 49 date element 12, 50
day attribute 12 day attribute 12
inside front 16 inside front 16
month attribute 12 month attribute 12
year attribute 13 year attribute 12
day attribute day attribute
in date element 12 in date element 12
docName attribute docName attribute
in rfc element 25 in rfc element 25
E E
Elements Elements
abstract 5, 16 abstract 4, 16
address 5, 9 address 5, 9
annotation 5, 23 annotation 5, 23
area 6, 16 area 5, 16
artwork 6, 14 artwork 6, 14
author 9, 16 author 8, 16
back 10, 24 back 10, 24
c 10, 32 c 10, 32
city 11, 21 city 10, 21
code 11, 21 code 11, 21
country 11, 21 country 11, 21
cref 6, 10-11, 22, 31 cref 5, 10-11, 22, 31
date 12, 16 date 12, 16
email 5, 13 email 5, 13
eref 6, 10, 13, 22, 31 eref 5, 10, 13, 22, 31
facsimile 5, 13 facsimile 5, 13
figure 14, 28, 31 figure 14, 28, 31
format 15, 23 format 15, 23
front 16, 23-24 front 16, 23-24
iref 6, 10, 14, 16, 22, 28, 31 iref 5, 10, 14, 16, 22, 28, 31
keyword 16-17 keyword 16-17
list 18, 31 list 18, 31
middle 20, 24 middle 20, 24
note 16, 20 note 16, 20
organization 9, 20 organization 9, 20
phone 5, 21 phone 5, 21
postal 5, 21 postal 5, 21
postamble 14, 22, 32 postamble 14, 22, 32
preamble 14, 22, 32 preamble 14, 22, 32
reference 23-24 reference 23-24
references 10, 23 references 10, 23
region 21, 24 region 21, 24
rfc 24 rfc 24
section 10, 20, 28 section 10, 20, 28
seriesInfo 23, 29 seriesInfo 23, 29
spanx 6, 10, 22, 29, 31 spanx 5, 10, 22, 30-31
street 21, 30 street 21, 31
t 5, 18, 20, 28, 30 t 4, 18, 20, 28, 31
texttable 28, 31 texttable 28, 32
title 16, 33 title 16, 34
ttcol 32-33 ttcol 32, 34
uri 5, 34 uri 5, 34
vspace 31, 34 vspace 31, 35
workgroup 16, 35 workgroup 16, 35
xref 5, 10, 22, 31, 35 xref 5, 10, 22, 31, 35
email element 13, 49 email element 13, 50
inside address 5 inside address 5
eref element 13, 49 eref element 13, 50
inside annotation 6 inside annotation 5
inside c 10 inside c 10
inside postamble 22 inside postamble 22
inside preamble 22 inside preamble 22
inside t 31 inside t 31
target attribute 13 target attribute 13
F F
facsimile element 13, 49 facsimile element 13, 50
inside address 5 inside address 5
figure element 14, 49 figure element 14, 50
align attribute 14 align attribute 14
alt attribute 14 alt attribute 14
anchor attribute 14 anchor attribute 14
height attribute 15 height attribute 15
inside section 28 inside section 28
inside t 31 inside t 31
src attribute 15 src attribute 15
suppress-title attribute 15 suppress-title attribute 15
title attribute 15 title attribute 15
width attribute 15 width attribute 15
format attribute format attribute
in xref element 35 in xref element 36
format element 15, 49 format element 15, 50
inside reference 23 inside reference 23
octets attribute 16 octets attribute 16
target attribute 16 target attribute 16
type attribute 16 type attribute 16
front element 16, 49 front element 16, 50
inside reference 23 inside reference 23
inside rfc 24 inside rfc 24
fullname attribute fullname attribute
in author element 9 in author element 9
H H
hangIndent attribute hangIndent attribute
in list element 18 in list element 18
hangText attribute hangText attribute
in t element 31 in t element 32
height attribute height attribute
in artwork element 7 in artwork element 7
in figure element 15 in figure element 15
I I
initials attribute initials attribute
in author element 9 in author element 9
ipr attribute ipr attribute
'*2026' 46 '*2026' 47
'*3667' 46 '*3667' 47
'*3978' 46 '*3978' 47
'*trust200811' 46 '*trust200811' 47
'*trust200902' 44 '*trust200902' 45
'noDerivativesTrust200902' 45 'noDerivativesTrust200902' 46
'noModificationTrust200902' 45 'noModificationTrust200902' 46
'pre5378Trust200902' 45 'pre5378Trust200902' 46
'trust200902' 45 'trust200902' 46
in rfc element 26 in rfc element 26
iprExtract attribute iprExtract attribute
in rfc element 26 in rfc element 26
iref element 16, 49 iref element 16, 50
inside annotation 6 inside annotation 5
inside c 10 inside c 10
inside figure 14 inside figure 14
inside postamble 22 inside postamble 22
inside preamble 22 inside preamble 22
inside section 28 inside section 28
inside t 31 inside t 31
item attribute 17 item attribute 17
primary attribute 17 primary attribute 17
subitem attribute 17 subitem attribute 17
item attribute item attribute
in iref element 17 in iref element 17
K K
keyword element 17, 49 keyword element 17, 50
inside front 16 inside front 16
L L
list element 18, 49 list element 18, 50
counter attribute 18 counter attribute 18
hangIndent attribute 18 hangIndent attribute 18
inside t 31 inside t 31
style attribute 18 style attribute 18
list styles list styles
empty 18 empty 18
format ... 19 format ... 19
hanging 19 hanging 19
letters 19 letters 19
numbers 19 numbers 19
symbols 19 symbols 19
M M
Media Type Media Type
application/rfc+xml 39 application/rfc+xml 40
middle element 20, 49
middle element 20, 50
inside rfc 24 inside rfc 24
month attribute month attribute
in date element 12 in date element 12
N N
name attribute name attribute
in artwork element 7 in artwork element 7
in seriesInfo element 29 in seriesInfo element 29
note element 20, 49 note element 20, 50
inside front 16 inside front 16
title attribute 20 title attribute 20
number attribute number attribute
in rfc element 27 in rfc element 27
O O
obsoletes attribute obsoletes attribute
in rfc element 27 in rfc element 27
octets attribute octets attribute
in format element 16 in format element 16
organization element 20, 49 organization element 20, 50
abbrev attribute 21 abbrev attribute 21
inside author 9 inside author 9
P P
pageno attribute pageno attribute
in xref element 36 in xref element 37
phone element 21, 49 phone element 21, 50
inside address 5 inside address 5
postal element 21, 49 postal element 21, 50
inside address 5 inside address 5
postamble element 22, 49 postamble element 22, 50
inside figure 14 inside figure 14
inside texttable 32 inside texttable 32
preamble element 22, 49 preamble element 22, 50
inside figure 14 inside figure 14
inside texttable 32 inside texttable 32
primary attribute primary attribute
in iref element 17 in iref element 17
R R
reference element 23, 49 reference element 23, 50
anchor attribute 23 anchor attribute 23
inside references 24 inside references 24
target attribute 23 target attribute 23
references element 23, 49 references element 23, 50
inside back 10 inside back 10
title attribute 24 title attribute 24
region element 24, 49
region element 24, 50
inside postal 21 inside postal 21
rfc element 24, 49 rfc element 24, 50
category attribute 25 category attribute 25
consensus attribute 25 consensus attribute 25
docName attribute 25 docName attribute 25
ipr attribute 26 ipr attribute 26
iprExtract attribute 26 iprExtract attribute 26
number attribute 27 number attribute 27
obsoletes attribute 27 obsoletes attribute 27
seriesNo attribute 27 seriesNo attribute 27
submissionType attribute 27 submissionType attribute 27
updates attribute 27 updates attribute 27
xml:lang attribute 28 xml:lang attribute 28
role attribute role attribute
in author element 9 in author element 9
S S
section element 28, 49 section element 28, 50
anchor attribute 28 anchor attribute 28
inside back 10 inside back 10
inside middle 20 inside middle 20
inside section 28 inside section 28
title attribute 28 title attribute 28
toc attribute 28 toc attribute 29
seriesInfo element 29, 49 seriesInfo element 29, 50
inside reference 23 inside reference 23
name attribute 29 name attribute 29
value attribute 29 value attribute 29
seriesNo attribute seriesNo attribute
in rfc element 27 in rfc element 27
source attribute source attribute
in cref element 12 in cref element 11
spanx element 29, 49 spanx element 30, 50
inside annotation 6 inside annotation 5
inside c 10 inside c 10
inside postamble 22 inside postamble 22
inside preamble 22 inside preamble 22
inside t 31 inside t 31
style attribute 30 style attribute 30
xml:space attribute 30 xml:space attribute 30
src attribute src attribute
in artwork element 8 in artwork element 7
in figure element 15 in figure element 15
street element 30, 49 start element 50
street element 31, 50
inside postal 21 inside postal 21
style attribute style attribute
in list element 18 in list element 18
in spanx element 30 in spanx element 30
in texttable element 32 in texttable element 33
subitem attribute subitem attribute
in iref element 17 in iref element 17
submissionType attribute submissionType attribute
in rfc element 27 in rfc element 27
suppress-title attribute suppress-title attribute
in figure element 15 in figure element 15
in texttable element 33 in texttable element 33
surname attribute surname attribute
in author element 10 in author element 9
T T
t element 30, 49 t element 31, 50
anchor attribute 31 anchor attribute 31
hangText attribute 31 hangText attribute 32
inside abstract 5 inside abstract 4
inside list 18 inside list 18
inside note 20 inside note 20
inside section 28 inside section 28
target attribute target attribute
in eref element 13 in eref element 13
in format element 16 in format element 16
in reference element 23 in reference element 23
in xref element 37 in xref element 37
texttable element 31, 49 texttable element 32, 50
align attribute 32 align attribute 32
anchor attribute 32 anchor attribute 32
inside section 28 inside section 28
style attribute 32 style attribute 33
suppress-title attribute 33 suppress-title attribute 33
title attribute 33 title attribute 33
title attribute title attribute
in figure element 15 in figure element 15
in note element 20 in note element 20
in references element 24 in references element 24
in section element 28 in section element 28
in texttable element 33 in texttable element 33
title element 33, 49 title element 34, 50
abbrev attribute 33 abbrev attribute 34
inside front 16 inside front 16
toc attribute toc attribute
in section element 28 in section element 29
ttcol element 33, 49 ttcol element 34, 50
align attribute 34 align attribute 34
inside texttable 32 inside texttable 32
width attribute 34 width attribute 34
type attribute type attribute
in artwork element 8 in artwork element 8
in format element 16 in format element 16
U U
updates attribute updates attribute
in rfc element 27 in rfc element 27
uri element 34, 49 uri element 34, 50
inside address 5 inside address 5
V V
value attribute value attribute
in seriesInfo element 29 in seriesInfo element 29
vspace element 34, 49 vspace element 35, 50
blankLines attribute 34 blankLines attribute 35
inside t 31 inside t 31
W W
width attribute width attribute
in artwork element 8 in artwork element 8
in figure element 15 in figure element 15
in ttcol element 34 in ttcol element 34
workgroup element 35, 49 workgroup element 35, 50
inside front 16 inside front 16
X X
xml:lang attribute xml:lang attribute
in rfc element 28 in rfc element 28
xml:space attribute xml:space attribute
in artwork element 8 in artwork element 8
in spanx element 30 in spanx element 30
xref element 35, 49 xref element 35, 50
format attribute 35 format attribute 36
inside annotation 5 inside annotation 5
inside c 10 inside c 10
inside postamble 22 inside postamble 22
inside preamble 22 inside preamble 22
inside t 31 inside t 31
pageno attribute 36 pageno attribute 37
target attribute 37 target attribute 37
xref formats xref formats
counter 36 counter 36
default 36 default 36
none 36 none 36
title 36 title 36
Y Y
year attribute year attribute
in date element 13 in date element 12
Author's Address Author's Address
Julian F. Reschke Julian F. Reschke
greenbytes GmbH greenbytes GmbH
Hafenweg 16 Hafenweg 16
Muenster, NW 48155 Muenster, NW 48155
Germany Germany
EMail: julian.reschke@greenbytes.de EMail: julian.reschke@greenbytes.de
 End of changes. 294 change blocks. 
697 lines changed or deleted 725 lines changed or added

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