Internet Architecture Board (IAB) J. Reschke
Request for Comments: 7749 greenbytes
Obsoletes: 2629 February 2016
Category: Informational
ISSN: 2070-1721
Internet Architecture Board (IAB) J. Reschke
Request for Comments: 7749 greenbytes
Obsoletes: 2629 February 2016
Category: Informational
ISSN: 2070-1721
The "xml2rfc" Version 2 Vocabulary
“xml2rfc”版本2词汇表
Abstract
摘要
This document defines the "xml2rfc" version 2 vocabulary: an XML-based language used for writing RFCs and Internet-Drafts.
本文档定义了“xml2rfc”版本2词汇表：一种用于编写RFC和Internet草稿的基于XML的语言。
Version 2 represents the state of the vocabulary (as implemented by several tools and as used by the RFC Editor) around 2014.
版本2表示2014年前后词汇表的状态（由多个工具实现并由RFC编辑器使用）。
This document obsoletes RFC 2629.
本文件废除了RFC 2629。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Architecture Board (IAB) and represents information that the IAB has deemed valuable to provide for permanent record. It represents the consensus of the Internet Architecture Board (IAB). Documents approved for publication by the IAB are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网体系结构委员会（IAB）的产品，代表IAB认为有价值提供永久记录的信息。它代表了互联网体系结构委员会（IAB）的共识。IAB批准发布的文件不适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7749.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7749.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction ....................................................4
1.1. Syntax Notation ............................................4
2. Elements ........................................................5
2.1. <abstract> .................................................5
2.2. <address> ..................................................5
2.3. <annotation> ...............................................6
2.4. <area> .....................................................6
2.5. <artwork> ..................................................7
2.6. <author> ..................................................10
2.7. <back> ....................................................11
2.8. <c> .......................................................12
2.9. <city> ....................................................12
2.10. <code> ...................................................12
2.11. <country> ................................................12
2.12. <cref> ...................................................13
2.13. <date> ...................................................14
2.14. <email> ..................................................15
2.15. <eref> ...................................................15
2.16. <facsimile> ..............................................16
2.17. <figure> .................................................16
2.18. <format> .................................................18
2.19. <front> ..................................................19
2.20. <iref> ...................................................20
2.21. <keyword> ................................................21
2.22. <list> ...................................................21
2.23. <middle> .................................................23
2.24. <note> ...................................................24
2.25. <organization> ...........................................24
2.26. <phone> ..................................................24
2.27. <postal> .................................................25
2.28. <postamble> ..............................................25
2.29. <preamble> ...............................................26
2.30. <reference> ..............................................26
2.31. <references> .............................................27
2.32. <region> .................................................28
2.33. <rfc> ....................................................28
2.34. <section> ................................................32
2.35. <seriesInfo> .............................................33
2.36. <spanx> ..................................................34
2.37. <street> .................................................35
2.38. <t> ......................................................35
2.39. <texttable> ..............................................36
2.40. <title> ..................................................38
2.41. <ttcol> ..................................................38
2.42. <uri> ....................................................39
1. Introduction ....................................................4
1.1. Syntax Notation ............................................4
2. Elements ........................................................5
2.1. <abstract> .................................................5
2.2. <address> ..................................................5
2.3. <annotation> ...............................................6
2.4. <area> .....................................................6
2.5. <artwork> ..................................................7
2.6. <author> ..................................................10
2.7. <back> ....................................................11
2.8. <c> .......................................................12
2.9. <city> ....................................................12
2.10. <code> ...................................................12
2.11. <country> ................................................12
2.12. <cref> ...................................................13
2.13. <date> ...................................................14
2.14. <email> ..................................................15
2.15. <eref> ...................................................15
2.16. <facsimile> ..............................................16
2.17. <figure> .................................................16
2.18. <format> .................................................18
2.19. <front> ..................................................19
2.20. <iref> ...................................................20
2.21. <keyword> ................................................21
2.22. <list> ...................................................21
2.23. <middle> .................................................23
2.24. <note> ...................................................24
2.25. <organization> ...........................................24
2.26. <phone> ..................................................24
2.27. <postal> .................................................25
2.28. <postamble> ..............................................25
2.29. <preamble> ...............................................26
2.30. <reference> ..............................................26
2.31. <references> .............................................27
2.32. <region> .................................................28
2.33. <rfc> ....................................................28
2.34. <section> ................................................32
2.35. <seriesInfo> .............................................33
2.36. <spanx> ..................................................34
2.37. <street> .................................................35
2.38. <t> ......................................................35
2.39. <texttable> ..............................................36
2.40. <title> ..................................................38
2.41. <ttcol> ..................................................38
2.42. <uri> ....................................................39
2.43. <vspace> .................................................39
2.44. <workgroup> ..............................................39
2.45. <xref> ...................................................40
3. Escaping for Use in XML ........................................42
4. Special Unicode Code Points ....................................42
5. Including Files ................................................43
6. Internationalization Considerations ............................44
7. Security Considerations ........................................44
8. IANA Considerations ............................................44
8.1. Internet Media Type Registration ..........................44
9. References .....................................................46
9.1. Normative References ......................................46
9.2. Informative References ....................................46
Appendix A. Front-Page ("Boilerplate") Generation .................50
A.1. The "category" Attribute ...................................50
A.2. The "ipr" Attribute ........................................50
A.2.1. Current Values: "*trust200902" .........................51
A.2.2. Historic Values ........................................52
A.3. The "submissionType" Attribute .............................54
A.4. The "consensus" Attribute ..................................55
Appendix B. Changes from RFC 2629 ("v1") ..........................56
B.1. Removed Elements ...........................................56
B.2. Changed Defaults ...........................................56
B.3. Changed Elements ...........................................57
B.4. New Elements ...............................................57
Appendix C. RELAX NG Schema .......................................58
C.1. Checking Validity ..........................................65
IAB Members at the Time of Approval ...............................66
Acknowledgments ...................................................66
Index .............................................................67
Author's Address ..................................................76
2.43. <vspace> .................................................39
2.44. <workgroup> ..............................................39
2.45. <xref> ...................................................40
3. Escaping for Use in XML ........................................42
4. Special Unicode Code Points ....................................42
5. Including Files ................................................43
6. Internationalization Considerations ............................44
7. Security Considerations ........................................44
8. IANA Considerations ............................................44
8.1. Internet Media Type Registration ..........................44
9. References .....................................................46
9.1. Normative References ......................................46
9.2. Informative References ....................................46
Appendix A. Front-Page ("Boilerplate") Generation .................50
A.1. The "category" Attribute ...................................50
A.2. The "ipr" Attribute ........................................50
A.2.1. Current Values: "*trust200902" .........................51
A.2.2. Historic Values ........................................52
A.3. The "submissionType" Attribute .............................54
A.4. The "consensus" Attribute ..................................55
Appendix B. Changes from RFC 2629 ("v1") ..........................56
B.1. Removed Elements ...........................................56
B.2. Changed Defaults ...........................................56
B.3. Changed Elements ...........................................57
B.4. New Elements ...............................................57
Appendix C. RELAX NG Schema .......................................58
C.1. Checking Validity ..........................................65
IAB Members at the Time of Approval ...............................66
Acknowledgments ...................................................66
Index .............................................................67
Author's Address ..................................................76
This document describes version 2 ("v2") of the "xml2rfc" vocabulary: an XML-based language ("Extensible Markup Language" [XML]) used for writing RFCs [RFC7322] and Internet-Drafts [IDGUIDE].
本文档描述了“xml2rfc”词汇表的第2版（“v2”）：一种基于XML的语言（“可扩展标记语言”[XML]），用于编写RFC[RFC7322]和Internet草稿[IDGUIDE]。
Version 2 represents the state of the vocabulary (as implemented by several tools and as used by the RFC Editor) around 2014.
版本2表示2014年前后词汇表的状态（由多个工具实现并由RFC编辑器使用）。
It obsoletes the original version ("v1") [RFC2629], which contained the original language definition and which was subsequently extended. Many of the changes leading to version 2 have been described in "Writing I-Ds and RFCs using XML (revised)" [V1rev], but that document has not been updated since 2008.
它废弃了原始版本（“v1”）[RFC2629]，该版本包含原始语言定义，并随后进行了扩展。导致版本2的许多更改已在“使用XML编写I-D和RFC（修订版）”[V1rev]中描述，但该文档自2008年以来一直未更新。
Processing Instructions (Section 2.6 of [XML]) generally are specific to a given processor and thus are not considered to be part of the vocabulary. See Section 4.1 of [TCLReadme] for a list of the Processing Instructions supported by the first implementation of an xml2rfc processor.
处理指令（XML第2.6节）通常特定于给定的处理器，因此不被视为词汇表的一部分。有关xml2rfc处理器的第一个实现所支持的处理指令的列表，请参见[TCLReadme]的第4.1节。
Note that the vocabulary contains certain constructs that might not be used when generating the final text; however, they can provide useful data for other uses (such as index generation, populating a keyword database, or syntax checks).
请注意，词汇表包含某些在生成最终文本时可能不会使用的结构；但是，它们可以为其他用途（如索引生成、填充关键字数据库或语法检查）提供有用的数据。
The XML vocabulary here is defined in prose, based on the RELAX NG schema [RNC] contained in Appendix C (specified in RELAX NG Compact Notation (RNC)).
这里的XML词汇表是以散文形式定义的，基于附录C中包含的RELAXNG模式[RNC]（在RELAXNG紧凑表示法（RNC）中指定）。
Note that the schema can be used for automated validity checks, but certain constraints are only described in prose (example: the conditionally required presence of the "abbrev" attribute).
请注意，该模式可用于自动有效性检查，但某些约束仅以散文形式描述（例如：有条件地要求存在“abbrev”属性）。
The sections below describe all elements and their attributes.
以下各节描述了所有元素及其属性。
Note that attributes not labeled "mandatory" are optional.
请注意，未标记为“强制”的属性是可选的。
Except inside <artwork>, horizontal whitespace and line breaks are collapsed into a single whitespace, and leading and trailing whitespace is trimmed off.
除了内部的<artwork>，水平空白和换行符被折叠成单个空白，并且前导和尾随空白被修剪掉。
Contains the Abstract of the document. The Abstract ought to be self-contained and thus should not contain references or unexpanded abbreviations. See Section 4.3 of [RFC7322] for more information.
包含文档的摘要。摘要应该是独立的，因此不应该包含参考文献或未展开的缩写。详见[RFC7322]第4.3节。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model:
内容模型：
One or more <t> elements (Section 2.38)
一个或多个<t>元件（第2.38节）
Provides address information for the author.
为作者提供地址信息。
This element appears as a child element of <author> (Section 2.6).
此元素显示为<author>的子元素（第2.6节）。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <postal> element (Section 2.27)
1. 一个可选的<postal>元素（第2.27节）
2. One optional <phone> element (Section 2.26)
2. 一个可选的<phone>元件（第2.26节）
3. One optional <facsimile> element (Section 2.16)
3. 一个可选<传真>元件（第2.16节）
4. One optional <email> element (Section 2.14)
4. 一个可选的<email>元素（第2.14节）
5. One optional <uri> element (Section 2.42)
5. 一个可选的<uri>元素（第2.42节）
Provides additional prose augmenting a bibliographical reference.
提供补充书目参考的附加散文。
This element appears as a child element of <reference> (Section 2.30).
此元素显示为<reference>的子元素（第2.30节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <xref> elements (Section 2.45)
o <xref>元素（第2.45节）
o <eref> elements (Section 2.15)
o <eref>元件（第2.15节）
o <iref> elements (Section 2.20)
o <iref>要素（第2.20节）
o <cref> elements (Section 2.12)
o <cref>要素（第2.12节）
o <spanx> elements (Section 2.36)
o <spanx>元件（第2.36节）
Provides information about the IETF area to which this document relates (currently not used when generating documents).
提供与本文档相关的IETF区域的相关信息（当前在生成文档时未使用）。
The value ought to be either the full name or the abbreviation of one of the IETF areas as listed on <https://www.ietf.org/iesg/area.html>. The list at the time that this document is being published is "Applications and Real-Time" ("art"), "General" ("gen"), "Internet" ("int"), "Operations and Management" ("ops"), "Routing" ("rtg"), "Security" ("sec"), and "Transport" ("tsv").
该值应为上所列IETF区域之一的全名或缩写<https://www.ietf.org/iesg/area.html>. 本文件发布时的列表为“应用与实时”（“art”）、“通用”（“gen”）、“互联网”（“int”）、“运营与管理”（“ops”）、“路由”（“rtg”）、“安全”（“sec”）和“传输”（“tsv”）。
Note that the set of IETF areas can change over time; for instance, "Applications and Real-Time" ("art") replaced "Applications" ("app") and "Real-time Applications and Infrastructure" ("rai") in 2015.
请注意，IETF区域集可以随时间而变化；例如，2015年，“应用程序和实时”（“art”）取代了“应用程序”（“app”）和“实时应用程序和基础设施”（“rai”）。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model: only text content.
内容模型：仅文本内容。
This element allows the inclusion of "artwork" in the document.
此元素允许在文档中包含“艺术品”。
<artwork> is the only element in the vocabulary that provides full control of horizontal whitespace and line breaks; thus, it is used for a variety of things, such as:
<artwork>是词汇表中唯一能够完全控制水平空白和换行符的元素；因此，它可用于多种用途，例如：
o diagrams ("line art"),
o 图表（“线条艺术”），
o source code,
o 源代码，
o formal languages (such as ABNF [RFC5234] or the RNC notation used in this document),
o 正式语言（如ABNF[RFC5234]或本文件中使用的RNC符号），
o message flow diagrams,
o 消息流图，
o complex tables, or
o 复杂表，或
o protocol unit diagrams.
o 协议单元图。
Note that processors differ in the handling of horizontal TAB characters (some expand them, some treat them as single spaces), and thus these ought to be avoided.
请注意，处理器在处理水平制表符方面有所不同（一些处理器将其展开，一些处理器将其视为单个空格），因此应避免使用这些字符。
Alternatively, the "src" attribute allows referencing an external graphics file, such as a bitmap or a vector drawing, using a URI ("Uniform Resource Identifier") [RFC3986]. In this case, the textual content acts as a fallback for output formats that do not support graphics; thus, it ought to contain either (1) a "line art" variant of the graphics or (2) prose that describes the included image in sufficient detail. Note that RFCs occasionally are published with enhanced diagrams; [RFC5598] is a recent example of an RFC that was published along with a PDF with images.
或者，“src”属性允许使用URI（“统一资源标识符”）[RFC3986]引用外部图形文件，例如位图或矢量图形。在这种情况下，文本内容充当不支持图形的输出格式的后备；因此，它应该包含（1）图形的“线条艺术”变体或（2）足够详细地描述所包含图像的散文。请注意，RFC偶尔会发布增强图；[RFC5598]是一个最近发布的RFC示例，它与带有图像的PDF一起发布。
This element appears as a child element of <figure> (Section 2.17).
此元素显示为<figure>的子元素（第2.17节）。
Content model:
内容模型：
Text
文本
Controls whether the artwork appears left justified (default), centered, or right justified.
控制艺术品是左对齐（默认）、居中还是右对齐。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
Alternative text description of the artwork (not just the caption).
艺术品的备选文本描述（不仅仅是标题）。
The suggested height of the graphics (when it was included using the "src" attribute).
图形的建议高度（当使用“src”属性包含时）。
This attribute is format dependent and ought to be avoided.
此属性依赖于格式，应该避免使用。
When generating HTML output [HTML], current implementations copy the attribute "as is", thus effectively treating it as CSS (Cascading Style Sheets) pixels (see Section 4.3.2 of [CSS]). For other output formats, it is usually ignored.
当生成HTML输出[HTML]时，当前的实现复制属性“原样”，从而有效地将其视为CSS（层叠样式表）像素（参见[CSS]的第4.3.2节）。对于其他输出格式，它通常被忽略。
A filename suitable for the contents (such as for extraction to a local file).
适合于内容的文件名（例如用于提取到本地文件）。
This attribute generally isn't used for document generation, but it can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code).
此属性通常不用于文档生成，但它对其他类型的工具（例如自动语法检查器，它通过提取源代码来工作）很有帮助。
The URI reference of a graphics file (Section 4.1 of [RFC3986]).
图形文件的URI参考（RFC3986第4.1节）。
Note that this can be a "data" URI [RFC2397] as well, in which case the graphics file is wholly part of the XML file.
请注意，这也可以是“数据”URI[RFC2397]，在这种情况下，图形文件完全是XML文件的一部分。
Specifies the type of the artwork.
指定艺术品的类型。
The value is either an Internet Media Type (see [RFC2046]) or a keyword (such as "abnf"). The set of recognized keywords varies across implementations.
该值是Internet媒体类型（请参见[RFC2046]）或关键字（如“abnf”）。可识别的关键字集因实现而异。
How it is used depends on context and application. For instance, a formatter can attempt to syntax-highlight code in certain known languages.
如何使用它取决于上下文和应用程序。例如，格式化程序可以尝试对某些已知语言中的代码进行语法高亮显示。
The suggested width of the graphics (when it was included using the "src" attribute).
建议的图形宽度（当使用“src”属性包含时）。
This attribute is format dependent and ought to be avoided.
此属性依赖于格式，应该避免使用。
When generating HTML output [HTML], current implementations copy the attribute "as is", thus effectively treating it as CSS pixels (see Section 4.3.2 of [CSS]). For other output formats, it is usually ignored.
在生成HTML输出[HTML]时，当前的实现复制属性“原样”，从而有效地将其视为CSS像素（请参见[CSS]的第4.3.2节）。对于其他输出格式，它通常被忽略。
Determines whitespace handling.
确定空格处理。
"preserve" is both the default value and the only meaningful setting (because that's what the <artwork> element is for).
“preserve”既是默认值，也是唯一有意义的设置（因为<artwork>元素就是用于此目的的）。
See also Section 2.10 of [XML].
另请参见[XML]第2.10节。
Allowed values:
允许值：
o "default"
o “默认值”
o "preserve" (default)
o “保留”（默认值）
Provides information about a document's author. This is used both for the document itself (at the beginning of the document) and for referenced documents (inside of <reference>).
提供有关文档作者的信息。这既用于文档本身（在文档开头）也用于引用文档（在<reference>内部）。
The <author> elements contained within the document's <front> element are used to fill the boilerplate, and also to generate the "Author's Address" section (see Section 4.12 of [RFC7322]).
文档的<front>元素中包含的<author>元素用于填充样板文件，还用于生成“作者地址”部分（参见[RFC7322]的第4.12节）。
Note that an "author" can also be just an organization (by not specifying any of the name attributes, but adding the <organization> child element).
注意，“author”也可以只是一个组织（通过不指定任何name属性，而是添加<organization>子元素）。
Furthermore, the "role" attribute can be used to mark an author as "editor". This is reflected on the front page and in the "Author's Address" section, as well as in bibliographical references. Note that this specification does not define a precise meaning for the term "editor".
此外，“role”属性可用于将作者标记为“editor”。这反映在头版和“作者地址”部分，以及参考书目中。请注意，本规范并未定义术语“编辑器”的确切含义。
See Sections 4.10 and 4.11 of [RFC7322] for more information.
更多信息，请参见[RFC7322]第4.10节和第4.11节。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <organization> element (Section 2.25)
1. 一个可选的<organization>元素（第2.25节）
2. One optional <address> element (Section 2.2)
2. 一个可选的<address>元素（第2.2节）
The full name (used in the automatically generated "Author's Address" section).
全名（用于自动生成的“作者地址”部分）。
An abbreviated variant of the given name(s), to be used in conjunction with the separately specified surname. It usually appears on the front page, in footers, and in references.
姓名的缩写变体，与单独指定的姓氏结合使用。它通常出现在首页、页脚和参考资料中。
Some processors will post-process the value -- for instance, when it only contains a single letter (in which case they might add a trailing dot). Relying on this kind of post-processing can lead to results varying across formatters and thus ought to be avoided.
一些处理器会对值进行后期处理——例如，当它只包含一个字母时（在这种情况下，他们可能会添加一个尾随点）。依赖这种后处理可能导致不同格式化程序的结果不同，因此应该避免。
Specifies the role the author had in creating the document.
指定作者在创建文档时的角色。
Allowed values:
允许值：
o "editor"
o “编辑”
The author's surname, to be used in conjunction with the separately specified initials. It usually appears on the front page, in footers, and in references.
作者的姓氏，与单独指定的首字母一起使用。它通常出现在首页、页脚和参考资料中。
Contains the "back" part of the document: the references and appendices. In <back>, <section> elements indicate appendices.
包含文件的“背面”部分：参考文件和附录。在<back>中，<section>元素表示附录。
This element appears as a child element of <rfc> (Section 2.33).
此元素显示为<rfc>的子元素（第2.33节）。
Content model:
内容模型：
In this order:
按此顺序：
1. Optional <references> elements (Section 2.31)
1. 可选<references>元素（第2.31节）
2. Optional <section> elements (Section 2.34)
2. 可选<section>元素（第2.34节）
Provides the content of a cell in a table.
提供表中单元格的内容。
This element appears as a child element of <texttable> (Section 2.39).
此元素显示为<texttable>（第2.39节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <xref> elements (Section 2.45)
o <xref>元素（第2.45节）
o <eref> elements (Section 2.15)
o <eref>元件（第2.15节）
o <iref> elements (Section 2.20)
o <iref>要素（第2.20节）
o <cref> elements (Section 2.12)
o <cref>要素（第2.12节）
o <spanx> elements (Section 2.36)
o <spanx>元件（第2.36节）
Gives the city name in a postal address.
在邮政地址中提供城市名称。
This element appears as a child element of <postal> (Section 2.27).
此元素显示为<postal>的子元素（第2.27节）。
Content model: only text content.
内容模型：仅文本内容。
Gives the postal region code.
提供邮政区域代码。
This element appears as a child element of <postal> (Section 2.27).
此元素显示为<postal>的子元素（第2.27节）。
Content model: only text content.
内容模型：仅文本内容。
Gives the country in a postal address.
在邮政地址中给出国家。
This element appears as a child element of <postal> (Section 2.27).
此元素显示为<postal>的子元素（第2.27节）。
Content model: only text content.
内容模型：仅文本内容。
Represents a comment.
表示注释。
Comments can be used in a document while it is a work in progress. They usually appear (1) inline and visually highlighted, (2) at the end of the document (depending on file format and settings of the formatter), or (3) not at all (when generating an RFC).
当文档是正在进行的工作时，可以在文档中使用注释。它们通常显示为（1）内联并以视觉方式突出显示，（2）在文档末尾（取决于文件格式和格式化程序的设置），或（3）根本不显示（生成RFC时）。
This element appears as a child element of <annotation> (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), <preamble> (Section 2.29), and <t> (Section 2.38).
此元素显示为<annotation>（第2.3节）、<c>（第2.8节）、<postamble>（第2.28节）、<preamble>（第2.29节）和<t>（第2.38节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
Document-wide unique identifier for this comment. The processor will autogenerate an identifier when none is given.
此注释的文档范围唯一标识符。当没有给出标识符时，处理器将自动生成标识符。
The value needs to be a valid XML "Name" (Section 2.3 of [XML]), additionally constrained to US-ASCII characters [USASCII].
该值必须是有效的XML“名称”（[XML]的第2.3节），另外还必须限制为US-ASCII字符[USASCII]。
Holds the "source" of a comment, such as the name or the initials of the person who made the comment.
保留评论的“来源”，例如发表评论的人的姓名或首字母缩写。
Provides information about the publication date.
提供有关发布日期的信息。
Note that this element is used for the boilerplate of the document being produced, and also inside bibliographic references.
请注意，此元素用于生成的文档的样板文件，也用于参考书目中。
In the "boilerplate" case, it defines the publication date, which, when producing Internet-Drafts, will be used for computing the expiration date (see Section 8 of [IDGUIDE]). When one or more of "year", "month", or "day" are left out, the processor will attempt to use the current system date if the attributes that are present are consistent with that date.
在“样板”案例中，它定义了发布日期，在生成互联网草稿时，将使用该日期计算到期日期（请参见[IDGUIDE]第8节）。当漏掉一个或多个“年”、“月”或“日”时，如果存在的属性与当前系统日期一致，处理器将尝试使用当前系统日期。
Note that in this case, month names need to match the full (English) month name ("January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", or "December") in order for expiration calculations to work (some implementations might support additional formats, though).
请注意，在这种情况下，月份名称需要与完整（英文）月份名称（“一月”、“二月”、“三月”、“四月”、“五月”、“六月”、“七月”、“八月”、“九月”、“十月”、“十一月”或“十二月”）匹配，以使到期计算工作正常（尽管某些实现可能支持其他格式）。
In the case of bibliographic references, the date information can have prose text for the month or year. For example, vague dates (year="ca. 2000"), date ranges (year="2012-2013"), non-specific months (month="Second quarter") and so on are allowed.
在参考书目的情况下，日期信息可以包含月份或年份的散文文本。例如，允许使用模糊日期（year=“ca.2000”）、日期范围（year=“2012-2013”）、非特定月份（month=“Second quarter”）等。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
In the "boilerplate" case, the day of publication; this is a number. Otherwise, an indication of the publication day, with the format not being restricted.
在“样板”案例中，发布日期；这是一个数字。否则，注明出版日期，格式不受限制。
In the "boilerplate" case, the month of publication; this is the English name of the month. Otherwise, an indication of the publication month, with the format not being restricted.
在“样板”案例中，指出版月份；这是这个月的英文名字。否则，注明出版月份，格式不受限制。
In the "boilerplate" case, the year of publication; this is a number (usually four-digit). Otherwise, an indication of the publication year, with the format not being restricted.
在“样板”案例中，出版年份；这是一个数字（通常是四位数）。否则，应注明出版年份，格式不受限制。
Provides an email address.
提供电子邮件地址。
The value is expected to be an email address conforming to the addr-spec definition in Section 2 of [RFC6068] (so does not include the prefix "mailto:").
该值应为符合[RFC6068]第2节中addr规范定义的电子邮件地址（因此不包括前缀“mailto:”）。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
Represents an "external" link (as specified in the "target" attribute).
表示“外部”链接（在“目标”属性中指定）。
If the element has no text content, the value of the "target" attribute will be inserted in angle brackets (as described in Appendix C of [RFC3986]) and, depending on the capabilities of the output format, hyperlinked.
如果元素没有文本内容，“target”属性的值将插入尖括号中（如[RFC3986]附录C所述），并根据输出格式的功能进行超链接。
Otherwise, the text content will be used (and potentially hyperlinked). Depending on output format and formatter, additional text might be inserted (such as a "URI" counter, and a "URIs" section in the back of the document). Avoid this variant when consistent rendering across formats and formatters is desired.
否则，将使用文本内容（并可能进行超链接）。根据输出格式和格式化程序，可能会插入其他文本（例如“URI”计数器和文档后面的“URI”部分）。当需要跨格式和格式化程序进行一致渲染时，请避免此变体。
This element appears as a child element of <annotation> (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), <preamble> (Section 2.29), and <t> (Section 2.38).
此元素显示为<annotation>（第2.3节）、<c>（第2.8节）、<postamble>（第2.28节）、<preamble>（第2.29节）和<t>（第2.38节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
URI of the link target (see Section 3 of [RFC3986]).
链接目标的URI（参见[RFC3986]第3节）。
Represents the phone number of a fax machine.
表示传真机的电话号码。
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" syntax. See Section 3 of [RFC3966] for details.
该值应该是“tel”URI中特定于方案的部分（因此不包括前缀“tel:”），使用“全局数字”语法。详见[RFC3966]第3节。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
This element is used to represent a figure, consisting of an optional preamble, the actual figure, an optional postamble, and an optional title.
此元素用于表示图形，由可选的前序、实际图形、可选的后序和可选的标题组成。
This element appears as a child element of <section> (Section 2.34) and <t> (Section 2.38).
此元素显示为<section>（第2.34节）和<t>（第2.38节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. Optional <iref> elements (Section 2.20)
1. 可选<iref>元件（第2.20节）
2. One optional <preamble> element (Section 2.29)
2. 一个可选的<preamble>元素（第2.29节）
3. One <artwork> element (Section 2.5)
3. 一个<artwork>元素（第2.5节）
4. One optional <postamble> element (Section 2.28)
4. 一个可选的<postamble>元素（第2.28节）
Used to change the alignment of <preamble> and <postamble>.
用于更改<preamble>和<postmble>的对齐方式。
Note: does not affect title or <artwork> alignment.
注意：不影响标题或对齐。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
Duplicates functionality available on <artwork>; avoid it.
复制<artwork>上可用的功能；避免它。
Document-wide unique identifier for this figure.
此图的文档范围唯一标识符。
Furthermore, the presence of this attribute causes the figure to be numbered.
此外，此属性的存在会导致对图形进行编号。
The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
该值必须是有效的XML“名称”（[XML]第2.3节）。
Duplicates functionality available on <artwork>; avoid it.
复制<artwork>上可用的功能；避免它。
Duplicates functionality available on <artwork>; avoid it.
复制<artwork>上可用的功能；避免它。
Figures that have an "anchor" attribute will automatically get an autogenerated title (such as "Figure 1"), even if the "title" attribute is absent. Setting this attribute to "true" will prevent this.
具有“锚定”属性的人物将自动获得自动生成的标题（如“图1”），即使“标题”属性不存在。将此属性设置为“true”将防止出现这种情况。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
The title for the figure; this usually appears on a line after the figure.
图的标题；这通常出现在图形后面的一行上。
Duplicates functionality available on <artwork>; avoid it.
复制<artwork>上可用的功能；避免它。
Provides a link to an additional format variant for a reference.
提供指向附加格式变量的链接以供参考。
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 for a reference, the "target" attribute on <reference> can be used instead.
请注意，这些附加链接既不在已发布的RFC中使用，也不受所有工具的支持。如果目标是为引用提供单个URI，则可以使用<reference>上的“target”属性。
This element appears as a child element of <reference> (Section 2.30).
此元素显示为<reference>的子元素（第2.30节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
Octet length of linked-to document.
链接到文档的八位字节长度。
URI of document.
文档的URI。
The type of the linked-to document, such as "TXT", "HTML", or "PDF".
链接到文档的类型，如“TXT”、“HTML”或“PDF”。
Represents the "front matter": metadata (such as author information), the Abstract, and additional notes.
表示“前端内容”：元数据（如作者信息）、摘要和附加注释。
This element appears as a child element of <reference> (Section 2.30) and <rfc> (Section 2.33).
此元素显示为<reference>（第2.30节）和<rfc>（第2.33节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One <title> element (Section 2.40)
1. 一个<title>元素（第2.40节）
2. One or more <author> elements (Section 2.6)
2. 一个或多个<author>元素（第2.6节）
3. One <date> element (Section 2.13)
3. 一个<日期>元素（第2.13节）
4. Optional <area> elements (Section 2.4)
4. 可选<area>元件（第2.4节）
5. Optional <workgroup> elements (Section 2.44)
5. 可选<工作组>元素（第2.44节）
6. Optional <keyword> elements (Section 2.21)
6. 可选<keyword>元素（第2.21节）
7. One optional <abstract> element (Section 2.1)
7. 一个可选的<abstract>元素（第2.1节）
8. Optional <note> elements (Section 2.24)
8. 可选<note>元件（第2.24节）
Provides terms for the document's index.
提供文档索引的术语。
Index entries can be either regular entries (when just the "item" attribute is given) or nested entries (by specifying "subitem" as well), grouped under a regular entry.
索引项可以是常规项（当只给出“item”属性时）或嵌套项（通过指定“subitem”也可以），分组在常规项下。
In this document, for instance, every element definition appears as a regular index entry ("iref element 2.20"). In addition, for each use of that element inside another parent element, a nested entry was added ("iref element 2.20, ... inside annotation 2.3").
例如，在本文档中，每个元素定义都显示为常规索引项（“iref元素2.20”）。此外，对于该元素在另一个父元素中的每次使用，都会添加一个嵌套条目（“iref元素2.20，…内部注释2.3”）。
Index entries generally refer to the exact place where the <iref> element occurred. An exception is the occurrence as a child element of <section>, in which case the whole section is considered to be relevant for that index entry. In some formats, index entries of this type might be displayed as ranges.
索引项通常指<iref>元素发生的确切位置。例外情况是作为<section>的子元素出现，在这种情况下，整个节被认为与该索引条目相关。在某些格式中，此类型的索引项可能显示为范围。
This element appears as a child element of <annotation> (Section 2.3), <c> (Section 2.8), <figure> (Section 2.17), <postamble> (Section 2.28), <preamble> (Section 2.29), <section> (Section 2.34), and <t> (Section 2.38).
此元素显示为<annotation>（第2.3节）、<c>（第2.8节）、<figure>（第2.17节）、<postamble>（第2.28节）、<preamble>（第2.29节）、<Section>（第2.34节）和<t>（第2.38节）的子元素。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
The item to include.
要包括的项目。
Setting this to "true" declares the occurrence as "primary", which might cause it to be highlighted in the index.
将其设置为“true”将事件声明为“primary”，这可能会导致它在索引中突出显示。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
The subitem to include.
要包括的子项。
Specifies a keyword applicable to the document.
指定适用于文档的关键字。
Note that each element should only contain a single keyword; for multiple keywords, the element can simply be repeated.
注意，每个元素应该只包含一个关键字；对于多个关键字，可以简单地重复元素。
Keywords are used both in the RFC Index and in the metadata of generated documents.
关键字用于RFC索引和生成文档的元数据中。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model: only text content.
内容模型：仅文本内容。
Delineates a text list.
描述一个文本列表。
Each list item is represented by a <t> element. The vocabulary currently does not directly support list items consisting of multiple paragraphs; if this is needed, <vspace> (Section 2.43) can be used as a workaround.
每个列表项由一个<t>元素表示。词汇表目前不直接支持由多个段落组成的列表项；如果需要，可以使用<vspace>（第2.43节）作为解决方法。
This element appears as a child element of <t> (Section 2.38).
此元素显示为<t>的子元素（第2.38节）。
Content model:
内容模型：
One or more <t> elements (Section 2.38)
一个或多个<t>元件（第2.38节）
This attribute holds a token that serves as an identifier for a counter. The intended use is continuation of lists, where the counter will be incremented for every list item, and there is no way to reset the counter.
此属性包含一个令牌，该令牌用作计数器的标识符。预期用途是列表的延续，其中每个列表项的计数器都将递增，并且无法重置计数器。
Note that this attribute functions only when the "style" attribute is using the "format..." syntax (Section 2.22.3); otherwise, it is ignored.
注意，只有当“样式”属性使用“格式…”语法时，该属性才起作用（第2.22.3节）；否则，它将被忽略。
For list styles with potentially wide labels, this attribute can override the default indentation level, measured in number of characters.
对于具有潜在宽标签的列表样式，此属性可以覆盖默认缩进级别（以字符数为单位）。
Note that it only affects styles with variable-width labels ("format..." and "hanging"; see below), and it may not affect formats in which the list item text appears _below_ the label.
请注意，它仅影响具有可变宽度标签的样式（“格式…”和“挂起”；请参见下文），并且可能不影响列表项文本显示在标签下方的格式。
This attribute is used to control the display of a list.
此属性用于控制列表的显示。
The value of this attribute is inherited by any nested lists that do not have this attribute set. It may be set to:
此属性的值由未设置此属性的任何嵌套列表继承。它可以设置为：
"empty"
“空的”
For unlabeled list items; it can also be used for indentation purposes (this is the default value when there is an enclosing list where the style is specified).
对于未标记的列表项；它也可用于缩进（当指定样式的封闭列表中有此样式时，这是默认值）。
"hanging"
“绞刑”
For lists where the items are labeled with a piece of text.
对于使用一段文本标记项目的列表。
The label text is specified in the "hangText" attribute of the <t> element (Section 2.38.2).
标签文本在<t>元素的“hangText”属性中指定（第2.38.2节）。
"letters"
“信件”
For ordered lists using letters as labels (lowercase letters followed by a period; after "z", it rolls over to a two-letter format). For nested lists, processors usually flip between uppercase and lowercase.
对于使用字母作为标签的有序列表（小写字母后跟句点；在“z”之后，滚动到两个字母的格式）。对于嵌套列表，处理器通常在大写和小写之间切换。
"numbers"
“数字”
For ordered lists using numbers as labels.
用于使用数字作为标签的有序列表。
"symbols"
“符号”
For unordered (bulleted) lists.
对于无序（项目符号）列表。
The style of the bullets is chosen automatically by the processor (some implementations allow overriding the default using a Processing Instruction).
项目符号的样式由处理器自动选择（某些实现允许使用处理指令覆盖默认值）。
And finally:
最后：
"format ..."
“格式…”
For lists with customized labels, consisting of fixed text and an item counter in various formats.
对于具有自定义标签的列表，由固定文本和各种格式的项目计数器组成。
The value is a free-form text that allows counter values to be inserted using a "percent-letter" format. For instance, "[REQ%d]" generates labels of the form "[REQ1]", where "%d" inserts the item number as a decimal number.
该值为自由格式文本，允许使用“百分比字母”格式插入计数器值。例如，“[REQ%d]”生成格式为“[REQ1]”的标签，其中“%d”将项目编号作为十进制数字插入。
The following formats are supported:
支持以下格式：
%c lowercase letters (a, b, c, etc.)
%c小写字母（a、b、c等）
%C uppercase letters (A, B, C, etc.)
%C大写字母（A、B、C等）
%d decimal numbers (1, 2, 3, etc.)
%d十进制数（1、2、3等）
%i lowercase Roman numerals (i, ii, iii, etc.)
%i小写罗马数字（i、ii、iii等）
%I uppercase Roman numerals (I, II, III, etc.)
%I大写罗马数字（I、II、III等）
%% represents a percent sign
%%表示百分号
Other formats are reserved for future use.
其他格式保留供将来使用。
Represents the main content of the document.
表示文档的主要内容。
This element appears as a child element of <rfc> (Section 2.33).
此元素显示为<rfc>的子元素（第2.33节）。
Content model:
内容模型：
One or more <section> elements (Section 2.34)
一个或多个<section>元素（第2.34节）
Creates an unnumbered section that appears after the Abstract.
创建出现在摘要后面的未编号部分。
It is usually used for additional information to reviewers (working group information, mailing list, ...), or for additional publication information such as "IESG Notes".
它通常用于向审阅者提供附加信息（工作组信息、邮件列表等），或用于附加出版物信息，如“IESG注释”。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model:
内容模型：
One or more <t> elements (Section 2.38)
一个或多个<t>元件（第2.38节）
The title of the note.
说明的标题。
Specifies the affiliation (Section 4.1.2 of [RFC7322]) of an author.
指定作者的从属关系（RFC7322第4.1.2节）。
This information appears both in the "Author's Address" section and on the front page (see Section 4.1.1 of [RFC7322] for more information). If the value is long, an abbreviated variant can be specified in the "abbrev" attribute.
该信息出现在“作者地址”部分和首页（更多信息请参见[RFC7322]第4.1.1节）。如果该值很长，则可以在“abbrev”属性中指定缩写变量。
This element appears as a child element of <author> (Section 2.6).
此元素显示为<author>的子元素（第2.6节）。
Content model: only text content.
内容模型：仅文本内容。
Abbreviated variant.
缩写变体。
Represents a phone number.
表示电话号码。
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" syntax. See Section 3 of [RFC3966] for details.
该值应该是“tel”URI中特定于方案的部分（因此不包括前缀“tel:”），使用“全局数字”语法。详见[RFC3966]第3节。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
Contains child elements providing postal information.
包含提供邮政信息的子元素。
Note that at least one <street> element needs to be present; however, formatters will handle empty values just fine.
请注意，至少需要存在一个<street>元素；但是，格式化程序可以很好地处理空值。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One or more <street> elements (Section 2.37)
1. 一个或多个<street>元素（第2.37节）
2. In any order:
2. 以任何顺序：
* <city> elements (Section 2.9)
* <city> elements (Section 2.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)
Gives text that appears at the bottom of a figure or table.
给出显示在图形或表格底部的文本。
This element appears as a child element of <figure> (Section 2.17) and <texttable> (Section 2.39).
此元素显示为<figure>（第2.17节）和<texttable>（第2.39节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <xref> elements (Section 2.45)
o <xref>元素（第2.45节）
o <eref> elements (Section 2.15)
o <eref>元件（第2.15节）
o <iref> elements (Section 2.20)
o <iref>要素（第2.20节）
o <cref> elements (Section 2.12)
o <cref>要素（第2.12节）
o <spanx> elements (Section 2.36)
o <spanx>元件（第2.36节）
Gives text that appears at the top of a figure or table.
给出显示在图形或表格顶部的文本。
This element appears as a child element of <figure> (Section 2.17) and <texttable> (Section 2.39).
此元素显示为<figure>（第2.17节）和<texttable>（第2.39节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <xref> elements (Section 2.45)
o <xref>元素（第2.45节）
o <eref> elements (Section 2.15)
o <eref>元件（第2.15节）
o <iref> elements (Section 2.20)
o <iref>要素（第2.20节）
o <cref> elements (Section 2.12)
o <cref>要素（第2.12节）
o <spanx> elements (Section 2.36)
o <spanx>元件（第2.36节）
Represents a bibliographical reference.
表示参考书目。
This element appears as a child element of <references> (Section 2.31).
此元素显示为<references>（第2.31节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One <front> element (Section 2.19)
1. 一个<front>元件（第2.19节）
2. Optional <seriesInfo> elements (Section 2.35)
2. 可选<serieinfo>元素（第2.35节）
3. Optional <format> elements (Section 2.18)
3. 可选<格式>元素（第2.18节）
4. Optional <annotation> elements (Section 2.3)
4. 可选<annotation>元素（第2.3节）
Document-wide unique identifier for this reference. Usually, this will be used both to "label" the reference in the "References" section, and as an identifier in links to this reference entry.
此引用的文档范围唯一标识符。通常，这将用于在“引用”部分中“标记”引用，并作为指向此引用条目的链接中的标识符。
The value needs to be a valid XML "Name" (Section 2.3 of [XML]), additionally constrained to US-ASCII characters [USASCII]. Thus, the character repertoire consists of "A-Z", "a-z", "0-9", "_", "-", ".", and ":", where "0-9", ".", and "-" are disallowed as start characters.
该值必须是有效的XML“名称”（[XML]的第2.3节），另外还必须限制为US-ASCII字符[USASCII]。因此，字符集由“A-Z”、“A-Z”、“0-9”、“_“、“-”和“：”组成，其中“0-9”、“”和“-”不允许作为起始字符。
Holds the URI for the reference.
保存引用的URI。
Note that, depending on the <seriesInfo> element, a URI might not be needed and might not be desirable, as it can be automatically generated (for instance, for RFCs).
注意，根据<serieinfo>元素的不同，可能不需要URI，也可能不需要URI，因为它可以自动生成（例如，对于RFC）。
Contains a set of bibliographical references.
包含一组参考书目。
In the early days of the RFC series, there was only one "References" section per RFC. This convention was later changed to group references into two sets -- "Normative" and "Informative" -- as described in Section 4.8.6 of [RFC7322]. This vocabulary supports the split with the "title" attribute.
在RFC系列的早期，每个RFC只有一个“参考”部分。该惯例后来更改为将参考文献分为两组——“规范性”和“信息性”——如[RFC7322]第4.8.6节所述。此词汇表支持使用“title”属性进行拆分。
By default, the order of references is significant. Processors, however, can be instructed to sort them based on their anchor names.
默认情况下，引用的顺序是重要的。但是，可以指示处理器根据其锚点名称对其进行排序。
This element appears as a child element of <back> (Section 2.7).
此元素显示为<back>的子元素（第2.7节）。
Content model:
内容模型：
One or more <reference> elements (Section 2.30)
一个或多个<参考>元件（第2.30节）
Provides the title for the "References" section (defaulting to "References").
提供“参考”部分的标题（默认为“参考”）。
In general, the title should be either "Normative References" or "Informative References".
一般而言，标题应为“规范性参考文件”或“资料性参考文件”。
Provides the region name in a postal address.
在邮政地址中提供地区名称。
This element appears as a child element of <postal> (Section 2.27).
此元素显示为<postal>的子元素（第2.27节）。
Content model: only text content.
内容模型：仅文本内容。
This is the root element of the xml2rfc vocabulary.
这是xml2rfc词汇表的根元素。
Processors distinguish between RFC mode ("number" attribute being present) and Internet-Draft mode ("docName" attribute being present): it is invalid to specify both. Setting neither "number" nor "docName" can be useful for producing other types of documents but is out of scope for this specification.
处理器区分RFC模式（“数字”属性存在）和Internet草稿模式（“docName”属性存在）：两者都指定是无效的。设置“number”和“docName”对生成其他类型的文档都不有用，但不在本规范的范围之内。
Content model:
内容模型：
In this order:
按此顺序：
1. One <front> element (Section 2.19)
1. 一个<front>元件（第2.19节）
2. One <middle> element (Section 2.23)
2. 一个<middle>元素（第2.23节）
3. One optional <back> element (Section 2.7)
3. 一个可选<back>元件（第2.7节）
Document category (see Appendix A.1).
文件类别（见附录A.1）。
Allowed values:
允许值：
o "std"
o “性病”
o "bcp"
o “bcp”
o "info"
o “信息”
o "exp"
o “经验”
o "historic"
o “历史性”
Affects the generated boilerplate.
影响生成的样板文件。
See [RFC5741] for more information.
有关更多信息，请参阅[RFC5741]。
Allowed values:
允许值：
o "no"
o “没有”
o "yes"
o “是的”
For Internet-Drafts, this specifies the draft name (which appears below the title).
对于Internet草稿，这将指定草稿名称（显示在标题下方）。
A processor should give an error if both the "docName" and "number" attributes are given in the <rfc> element.
如果<rfc>元素中同时给出了“docName”和“number”属性，则处理器应给出一个错误。
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).
请注意，文件扩展名不是草稿的一部分，因此通常应以当前草稿编号（“-”，加上两位数字）结尾。
Furthermore, it is good practice to disambiguate current editor copies from submitted drafts (for instance, by replacing the draft number with the string "latest").
此外，从提交的草稿中消除当前编辑器副本的歧义是一种很好的做法（例如，用字符串“latest”替换草稿编号）。
See Section 7 of [IDGUIDE] for further information.
有关更多信息，请参见[IDGUIDE]第7节。
Represents the Intellectual Property status of the document. See Appendix A.2 for details.
表示文档的知识产权状态。详见附录A.2。
Allowed values:
允许值：
o "full2026"
o “2026年全年”
o "noDerivativeWorks2026"
o “noDerivativeWorks2026”
o "none"
o “没有”
o "full3667"
o “满3667”
o "noModification3667"
o “编号3667”
o "noDerivatives3667"
o “noDerivatives3667”
o "full3978"
o “完整3978”
o "noModification3978"
o “编号3978”
o "noDerivatives3978"
o “noDerivatives3978”
o "trust200811"
o “信托200811”
o "noModificationTrust200811"
o “noModificationTrust200811”
o "noDerivativesTrust200811"
o “noDerivativesTrust200811”
o "trust200902"
o “信托200902”
o "noModificationTrust200902"
o “noModificationTrust200902”
o "noDerivativesTrust200902"
o “noDerivativesTrust200902”
o "pre5378Trust200902"
o “pre5378Trust200902”
Identifies a single section within the document (by its "anchor" attribute) for which extraction "as is" is explicitly allowed (this is only relevant for historic values of the "ipr" attribute).
标识文档中明确允许提取“原样”的单个节（通过其“锚定”属性）（这仅与“ipr”属性的历史值相关）。
The number of the RFC to be produced.
要生成的RFC的编号。
A processor should give an error if both the "docName" and "number" attributes are given in the <rfc> element.
如果<rfc>元素中同时给出了“docName”和“number”属性，则处理器应给出一个错误。
A comma-separated list of RFC _numbers_ or Internet-Draft names.
以逗号分隔的RFC编号或Internet草稿名称列表。
Processors ought to parse the attribute value, so that incorrect references can be detected and, depending on output format, hyperlinks can be generated. Also, the value ought to be reformatted to insert whitespace after each comma if not already present.
处理器应该解析属性值，以便检测不正确的引用，并根据输出格式生成超链接。此外，如果尚未存在，则应重新格式化该值，以便在每个逗号后插入空格。
Number within a document series.
文档系列中的编号。
The document series is defined by the "category" attribute; "seriesNo" is only applicable to the values "info" ("FYI" series), "std" ("STD" series), and "bcp" ("BCP" series).
单据系列由“类别”属性定义；“序列号”仅适用于值“信息”（“FYI”系列）、“标准”（“标准”系列）和“bcp”（“bcp”系列）。
The document stream.
文档流。
See Section 2 of [RFC5741] for details.
详见[RFC5741]第2节。
Allowed values:
允许值：
o "IETF" (default)
o “IETF”（默认值）
o "IAB"
o “IAB”
o "IRTF"
o “IRTF”
o "independent"
o “独立的”
A comma-separated list of RFC _numbers_ or Internet-Draft names.
以逗号分隔的RFC编号或Internet草稿名称列表。
Processors ought to parse the attribute value, so that incorrect references can be detected and, depending on output format, hyperlinks can be generated. Also, the value ought to be reformatted to insert whitespace after each comma if not already present.
处理器应该解析属性值，以便检测不正确的引用，并根据输出格式生成超链接。此外，如果尚未存在，则应重新格式化该值，以便在每个逗号后插入空格。
The natural language used in the document (defaults to "en").
文档中使用的自然语言（默认为“en”）。
See Section 2.12 of [XML] for more information.
有关更多信息，请参见[XML]的第2.12节。
Represents a section (when inside a <middle> element) or an appendix (when inside a <back> element).
表示节（位于<middle>元素内部时）或附录（位于<back>元素内部时）。
Subsections are created by nesting <section> elements inside <section> elements.
子部分是通过在<section>元素中嵌套<section>元素来创建的。
This element appears as a child element of <back> (Section 2.7), <middle> (Section 2.23), and <section> (Section 2.34).
此元素显示为<back>（第2.7节）、<middle>（第2.23节）和<Section>（第2.34节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. In any order:
1. 以任何顺序：
* <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. 可选<section>元素（第2.34节）
Document-wide unique identifier for this section.
此节的文档范围唯一标识符。
The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
该值必须是有效的XML“名称”（[XML]第2.3节）。
The title of the section.
本节的标题。
Determines whether the section is included in the 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 included (frequently: 3). "include" and "exclude" allow overriding the processor's default behavior for the element they are specified on (they do not affect either nested or parent elements).
处理器通常默认是否生成目录，以及包含最大深度的部分（通常为：3）。“include”和“exclude”允许覆盖处理器在其上指定的元素的默认行为（它们既不影响嵌套元素也不影响父元素）。
Allowed values:
允许值：
o "include"
o “包括”
o "exclude"
o “排除”
o "default" (default)
o “默认”（默认）
Specifies the document series in which this document appears, and also specifies an identifier within that series.
指定此文档出现的文档系列，并指定该系列中的标识符。
This element appears as a child element of <reference> (Section 2.30).
此元素显示为<reference>的子元素（第2.30节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
The name of the series.
系列的名称。
Some series names might trigger specific processing (such as for autogenerating links, inserting descriptions such as "work in progress", or additional functionality like reference diagnostics). Examples for IETF-related series names are "BCP", "FYI", "Internet-Draft", "RFC", and "STD".
某些系列名称可能会触发特定的处理（例如用于自动生成链接、插入描述（如“正在进行的工作”）或其他功能（如参考诊断）。IETF相关系列名称的示例有“BCP”、“FYI”、“互联网草案”、“RFC”和“STD”。
The identifier within the series specified by the "name" attribute.
由“name”属性指定的序列中的标识符。
For BCPs, FYIs, RFCs, and STDs, this is the number within the series.
对于BCP、FYI、RFC和STD，这是系列中的数字。
For Internet-Drafts, it is the full draft name (ending with the two-digit version number).
对于Internet草稿，它是完整的草稿名称（以两位数版本号结尾）。
Wraps a piece of text, indicating special formatting styles.
换行一段文字，表示特殊的格式样式。
When generating plain text, processors usually emulate font changes using characters such as "*" and "_".
在生成纯文本时，处理器通常使用诸如“*”和“\”等字符模拟字体更改。
The following styles are defined:
定义了以下样式：
emph Simple emphasis (this is the default).
emph简单强调（这是默认值）。
strong Strong emphasis.
非常强调。
verb "Verbatim" text (usually displayed using a monospaced font face).
动词“逐字”文本（通常使用单间距字体显示）。
This element appears as a child element of <annotation> (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), <preamble> (Section 2.29), and <t> (Section 2.38).
此元素显示为<annotation>（第2.3节）、<c>（第2.8节）、<postamble>（第2.28节）、<preamble>（第2.29节）和<t>（第2.38节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
The style to be used (defaults to "emph").
要使用的样式（默认为“emph”）。
Determines whitespace handling.
确定空格处理。
According to the DTD, the default value is "preserve". However, tests show that it doesn't have any effect on processing; thus, this attribute will be removed in future versions of the vocabulary.
根据DTD，默认值为“保留”。然而，测试表明，它对加工没有任何影响；因此，该属性将在词汇表的未来版本中删除。
See also Section 2.10 of [XML].
另请参见[XML]第2.10节。
Allowed values:
允许值：
o "default"
o “默认值”
o "preserve" (default)
o “保留”（默认值）
Provides a street address.
提供街道地址。
This element appears as a child element of <postal> (Section 2.27).
此元素显示为<postal>的子元素（第2.27节）。
Content model: only text content.
内容模型：仅文本内容。
Contains a paragraph of text.
包含一段文字。
This element appears as a child element of <abstract> (Section 2.1), <list> (Section 2.22), <note> (Section 2.24), and <section> (Section 2.34).
此元素显示为<abstract>（第2.1节）、<list>（第2.22节）、<note>（第2.24节）和<Section>（第2.34节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <list> elements (Section 2.22)
o <list>元素（第2.22节）
o <figure> elements (Section 2.17)
o <figure>元素（第2.17节）
o <xref> elements (Section 2.45)
o <xref>元素（第2.45节）
o <eref> elements (Section 2.15)
o <eref>元件（第2.15节）
o <iref> elements (Section 2.20)
o <iref>要素（第2.20节）
o <cref> elements (Section 2.12)
o <cref>要素（第2.12节）
o <spanx> elements (Section 2.36)
o <spanx>元件（第2.36节）
o <vspace> elements (Section 2.43)
o <vspace>元素（第2.43节）
Document-wide unique identifier for this paragraph.
此段落的文档范围唯一标识符。
The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
该值必须是有效的XML“名称”（[XML]第2.3节）。
Holds the label ("hanging text") for items in lists using the "hanging" style (see Section 2.22.3).
使用“悬挂”样式保存列表中项目的标签（“悬挂文本”）（见第2.22.3节）。
Contains a table, consisting of an optional preamble, a header line, rows, an optional postamble, and an optional title.
包含一个表，由可选的前言、标题行、行、可选的后前言和可选的标题组成。
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 the number of <c> elements divided by the number of columns. There is no requirement that the number of <c> elements be evenly divisible by the number of columns.
表中的列数由<ttcol>元素的数量决定。表中的行数由<c>元素数除以列数决定。不要求<c>元素的数量可以被列的数量平均整除。
This element appears as a child element of <section> (Section 2.34).
此元素显示为<section>（第2.34节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <preamble> element (Section 2.29)
1. 一个可选的<preamble>元素（第2.29节）
2. One or more <ttcol> elements (Section 2.41)
2. 一个或多个<ttcol>元件（第2.41节）
3. Optional <c> elements (Section 2.8)
3. 可选<c>元件（第2.8节）
4. One optional <postamble> element (Section 2.28)
4. 一个可选的<postamble>元素（第2.28节）
Determines the horizontal alignment of the table.
确定表格的水平对齐方式。
Allowed values:
允许值：
o "left"
o “左”
o "center" (default)
o “中心”（默认值）
o "right"
o “对”
Document-wide unique identifier for this table.
此表的文档范围唯一标识符。
Furthermore, the presence of this attribute causes the table to be numbered.
此外，此属性的存在会导致对表进行编号。
The value needs to be a valid XML "Name" (Section 2.3 of [XML]).
该值必须是有效的XML“名称”（[XML]第2.3节）。
Selects which borders should be drawn, where
选择应绘制哪些边框，其中
o "all" means borders around all table cells,
o “全部”是指所有表格单元格周围的边框，
o "full" is like "all", except no horizontal lines between table rows (except below the column titles),
o “full”与“all”类似，只是表行之间没有水平线（列标题下方除外），
o "headers" adds just a separator between column titles and rows, and
o “标题”仅在列标题和行之间添加分隔符，并且
o "none" means no borders at all.
o “无”意味着没有边界。
Allowed values:
允许值：
o "all"
o “全部”
o "none"
o “没有”
o "headers"
o “标题”
o "full" (default)
o “完整”（默认值）
Tables that have an "anchor" attribute will automatically get an autogenerated title (such as "Table 1"), even if the "title" attribute is absent. Setting this attribute to "true" will prevent this.
具有“锚定”属性的表将自动获得自动生成的标题（例如“表1”），即使“标题”属性不存在。将此属性设置为“true”将防止出现这种情况。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
The title for the table; this usually appears on a line below the table body.
表格的标题；这通常出现在表体下方的一行上。
Represents the document title.
表示文档标题。
When this element appears in the <front> element of the current document, the title might also appear in page headers or footers. If it's long (~40 characters), the "abbrev" attribute is used to specify an abbreviated variant.
当此元素出现在当前文档的<front>元素中时，标题也可能出现在页眉或页脚中。如果是长的（~40个字符），“abbrev”属性用于指定缩写变量。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model: only text content.
内容模型：仅文本内容。
Specifies an abbreviated variant of the document title.
指定文档标题的缩写变体。
Contains a column heading in a table.
包含表中的列标题。
This element appears as a child element of <texttable> (Section 2.39).
此元素显示为<texttable>（第2.39节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
Determines the horizontal alignment within the table column.
确定表格列内的水平对齐方式。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
The desired column width (as integer 0..100 followed by "%").
所需的列宽（整数0..100后跟“%”）。
Contains a web address associated with the author.
包含与作者关联的网址。
The contents should be a valid URI (see Section 3 of [RFC3986]).
内容应为有效的URI（见[RFC3986]第3节）。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
This element can be used to force the inclusion of a single line break or multiple blank lines.
此元素可用于强制包含单个换行符或多个空行。
Note that this is a purely presentational element; thus, its use ought to be avoided, except within a <list> as discussed in Section 2.22.
请注意，这是一个纯粹的表现元素；因此，除第2.22节中讨论的<list>外，应避免使用它。
This element appears as a child element of <t> (Section 2.38).
此元素显示为<t>的子元素（第2.38节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
Number of blank lines to be inserted, where "0" indicates a single line break (defaults to "0").
要插入的空行数，其中“0”表示单行中断（默认为“0”）。
For paged output formats, no additional blank lines should be generated after a page break.
对于分页输出格式，分页符后不应生成额外的空行。
This element is used to specify the Working Group (IETF) or Research Group (IRTF) from which the document originates, if any. The recommended format is the official name of the Working Group (with some capitalization).
此元素用于指定文件来源的工作组（IETF）或研究组（IRTF）（如有）。建议的格式是工作组的正式名称（略加大写）。
In Internet-Drafts, this is used in the upper left corner of the boilerplate, replacing the default "Network Working Group" string. Formatting software can append the words "Working Group" or "Research Group", depending on the "submissionType" property of the <rfc> element (Section 2.33.9).
在InternetDrafts中，这在样板文件的左上角使用，替换默认的“NetworkWorkingGroup”字符串。格式化软件可以根据<rfc>元素的“submissionType”属性（第2.33.9节）添加单词“工作组”或“研究组”。
This element appears as a child element of <front> (Section 2.19).
此元素显示为<front>的子元素（第2.19节）。
Content model: only text content.
内容模型：仅文本内容。
Inserts a cross-reference to a different part of a document.
插入对文档不同部分的交叉引用。
The generated text depends on (1) whether the <xref> is empty (in which case the processor will try to generate a meaningful text fragment), (2) the "format" attribute, and (3) the nature (XML element type) of the referenced document part.
生成的文本取决于（1）<xref>是否为空（在这种情况下，处理器将尝试生成有意义的文本片段），（2）“格式”属性，以及（3）引用文档部分的性质（XML元素类型）。
Any element that allows the "anchor" attribute can be referenced;
however, there are restrictions with respect to the text content
being generated. For instance, a <t> can be a reference target;
however, because paragraphs are not (visibly) numbered, the author
will have to make sure that the combination of prose and contained
text content is sufficient for a reader to understand what is being
referred to.
Any element that allows the "anchor" attribute can be referenced;
however, there are restrictions with respect to the text content
being generated. For instance, a <t> can be a reference target;
however, because paragraphs are not (visibly) numbered, the author
will have to make sure that the combination of prose and contained
text content is sufficient for a reader to understand what is being
referred to.
This element appears as a child element of <annotation> (Section 2.3), <c> (Section 2.8), <postamble> (Section 2.28), <preamble> (Section 2.29), and <t> (Section 2.38).
此元素显示为<annotation>（第2.3节）、<c>（第2.8节）、<postamble>（第2.28节）、<preamble>（第2.29节）和<t>（第2.38节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
This attribute is used to control the format of the generated reference text.
此属性用于控制生成的引用文本的格式。
"counter"
“柜台”
Inserts a counter, such as the number of a section, figure, table, or list item.
插入计数器，例如节、图、表或列表项的编号。
For targets that are not inherently numbered, such as references or comments, it uses the anchor name instead.
对于没有固有编号的目标，例如引用或注释，它使用锚名称。
"default"
“默认值”
Inserts a text fragment that describes the referenced part completely, such as "Section 2", "Table 4", or "[XML]".
插入完整描述引用部分的文本片段，如“第2节”、“表4”或“[XML]”。
"none"
“没有”
There will be no autogenerated text.
不会有自动生成的文本。
"title"
“标题”
Inserts a title for the referenced element (usually obtained from the referenced element's "title" attribute; some processors also use the <title> child element or a <reference> target).
插入被引用元素的标题（通常从被引用元素的“title”属性中获取；某些处理器还使用<title>子元素或<reference>目标）。
Not all combinations of text content, "format" attribute, and type of referenced part lead to predictable results across different formatters. In case this matters, the following combinations need to be avoided:
并非所有文本内容、“格式”属性和引用零件类型的组合都会在不同的格式化程序中产生可预测的结果。在这种情况下，需要避免以下组合：
o Non-empty text content with any format other than "none".
o 非空文本内容，具有除“无”以外的任何格式。
o Empty text content with format "counter" for any target that isn't inherently numbered.
o 对于任何未固有编号的目标，格式为“counter”的空文本内容。
o Empty text content with format "title" for any target that doesn't have a title.
o 任何没有标题的目标的格式为“title”的空文本内容。
Allowed values:
允许值：
o "counter"
o “柜台”
o "title"
o “标题”
o "none"
o “没有”
o "default" (default)
o “默认”（默认）
Unused.
未使用的。
It's unclear what the purpose of this attribute is; processors seem to ignore it, and it never was documented.
不清楚这个属性的用途是什么；处理器似乎忽略了它，而且它从未被记录下来。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
Identifies the document component being referenced.
标识要引用的文档组件。
The value needs to match the value of the "anchor" attribute of another element in the document.
该值需要与文档中另一个元素的“锚定”属性的值匹配。
Text in XML cannot use the literal characters "<" and "&", as they have special meaning to the XML processor (starting entities, elements, etc.). Usually, these characters will need to be substituted by "<" and "&" (see Section 4.6 of [XML]).
XML中的文本不能使用文本字符“<”和“&”，因为它们对XML处理器（起始实体、元素等）具有特殊意义。通常，这些字符需要替换为“<；”和“&；”（参见[XML]第4.6节）。
">" does not require escaping, unless it appears in the sequence "]]>" (which indicates the end of a CDATA section; see below).
“>”不需要转义，除非它出现在序列“]]>”中（表示CDATA节的结束；请参见下文）。
Escaping the individual characters can be a lot of work (when done manually) and also messes up alignment in artwork. Another approach to escaping is to use CDATA sections (Section 2.7 of [XML]). Within these, no further escaping is needed, except when the "end-of-CDATA" marker needs to be used (in that case, the CDATA section needs to be closed, and a new one needs to be started).
转义单个字符可能需要大量的工作（当手动完成时），并且还会打乱艺术品中的对齐。另一种转义方法是使用CDATA节（XML的第2.7节）。在这些情况下，不需要进一步转义，除非需要使用“结束CDATA”标记（在这种情况下，需要关闭CDATA部分，并启动一个新的部分）。
Although the current RFC format does not allow non-ASCII Unicode characters [UNICODE], some of them can be used to enforce certain behaviors of formatters.
尽管当前RFC格式不允许使用非ASCII Unicode字符[Unicode]，但其中一些字符可用于强制格式化程序的某些行为。
For instance:
例如：
non-breaking space (U+00A0)
非中断空间（U+00A0）
Represents a space character where no line break should happen. This is frequently used in titles (by excluding certain space characters from the line-breaking algorithm, the processor will use the remaining whitespace occurrences for line breaks).
表示不应发生换行的空格字符。这在标题中经常使用（通过从换行算法中排除某些空格字符，处理器将使用剩余的空格作为换行符）。
non-breaking hyphen (U+2011)
不间断连字符（U+2011）
Similarly, this represents a hyphen character where no line breaking ought to occur.
类似地，这表示不应出现断行的连字符。
word joiner (U+2060)
字接合器（U+2060）
Also called "zero width non-breaking space" -- can be used to disallow line breaking between two non-whitespace characters.
也称为“零宽度不间断空格”——可用于禁止两个非空白字符之间的换行。
Note that in order to use these characters by name, they need to be declared in either the Document Type Definition (DTD) or the "internal subset" (Section 2.8 of [XML]), like this:
请注意，为了按名称使用这些字符，需要在文档类型定义（DTD）或“内部子集”（XML第2.8节）中声明它们，如下所示：
<?xml version="1.0"?>
<?xml version="1.0"?>
<!DOCTYPE rfc [
<!DOCTYPE rfc[
<!-- declare nbsp and friends -->
<!ENTITY nbsp " ">
<!ENTITY nbhy "‑">
<!ENTITY wj "⁠">
]>
<!-- declare nbsp and friends -->
<!ENTITY nbsp " ">
<!ENTITY nbhy "‑">
<!ENTITY wj "⁠">
]>
This version of the vocabulary does not support an inclusion mechanism on its own -- thus, a document always needs to be self-contained.
这个版本的词汇表本身不支持包含机制——因此，文档始终需要是自包含的。
That being said, some processors do support file inclusion using Processing Instructions (Section 2.6 of [XML] and Section 4.1.2 of [TCLReadme]).
也就是说，一些处理器确实支持使用处理指令包含文件（XML的第2.6节和TCL自述文件的第4.1.2节）。
Furthermore, XML itself allows inclusion of external content using the "internal subset" (Section 2.8 of [XML]). Unfortunately, this requires declaring the external data in the DTD upfront.
此外，XML本身允许使用“内部子集”（XML的第2.8节）包含外部内容。不幸的是，这需要在DTD中预先声明外部数据。
For instance:
例如：
<?xml version="1.0"?>
<?xml version="1.0"?>
<!DOCTYPE rfc [
<!DOCTYPE rfc[
<!-- allow later RFC 2629 reference using "&rfc2629;" -->
<!-- the data will be fetched from xml2rfc.ietf.org -->
<!ENTITY rfc2629 PUBLIC
"http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml">
]>
<!-- allow later RFC 2629 reference using "&rfc2629;" -->
<!-- the data will be fetched from xml2rfc.ietf.org -->
<!ENTITY rfc2629 PUBLIC
"http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml">
]>
...declares the entity "rfc2629", which then can be used in the "References" section:
…声明实体“rfc2629”，然后可在“引用”部分中使用该实体：
<references>
&rfc2629;
</references>
<references>
&rfc2629;
</references>
Note that this mechanism only works for well-formed XML fragments; thus, any plain text that would need to be escaped in XML can't be included as is.
注意，这种机制只适用于格式良好的XML片段；因此，任何需要在XML中转义的纯文本都不能按原样包含。
This format is based on [XML] and thus does not have any issues representing arbitrary Unicode [UNICODE] characters in text content.
此格式基于[XML]，因此在文本内容中表示任意Unicode[Unicode]字符时没有任何问题。
However, the current canonical RFC format is restricted to US-ASCII characters (see [USASCII] and Section 3 of [RFC2223]). It is possible that this rule will be relaxed in future revisions of the RFC format (for instance, to allow non-ASCII characters in examples and contact information). In that case, it is expected that the vocabulary will be extended accordingly.
但是，当前的规范RFC格式仅限于US-ASCII字符（请参见[USASCI]和[RFC2223]第3节）。在RFC格式的未来版本中，这一规则可能会放宽（例如，允许示例和联系信息中使用非ASCII字符）。在这种情况下，预计词汇表将相应扩展。
The "name" attribute of the <artwork> element (Section 2.5.4) can be used to derive a filename for saving to a local file system. Trusting this kind of information without pre-processing is a known security risk; see Section 4.3 of [RFC6266] for more information.
<artwork>元素（第2.5.4节）的“name”属性可用于导出文件名以保存到本地文件系统。未经预处理就信任此类信息是一种已知的安全风险；详见[RFC6266]第4.3节。
Furthermore, the nature of XML, plus vocabulary features such as typed artwork, make it attractive to extract content from documents for further processing, such as for the purpose of checking syntax or computing/verifying examples. In the latter case, care needs to be taken that only trusted content is processed.
此外，XML的性质，加上词汇表功能（如键入的插图），使得从文档中提取内容以供进一步处理（如用于检查语法或计算/验证示例）更具吸引力。在后一种情况下，需要注意只处理受信任的内容。
All security considerations related to XML processing are relevant as well (see Section 7 of [RFC3470]).
与XML处理相关的所有安全注意事项也都是相关的（参见[RFC3470]第7节）。
IANA maintains the registry of Internet Media Types [BCP13] at <http://www.iana.org/assignments/media-types>.
IANA在以下位置维护互联网媒体类型注册表[BCP13]<http://www.iana.org/assignments/media-types>.
This document serves as the specification for the Internet Media Type "application/rfc+xml". The following has been registered with IANA.
本文档作为Internet媒体类型“application/rfc+xml”的规范。以下内容已在IANA注册。
Type name: application
类型名称：应用程序
Subtype name: rfc+xml
子类型名称：rfc+xml
Required parameters: There are no required parameters.
必需参数：没有必需的参数。
Optional parameters: "charset": This parameter has identical semantics to the charset parameter of the "application/xml" Media Type specified in Section 9.1 of [RFC7303].
可选参数：“字符集”：该参数与[RFC7303]第9.1节中指定的“应用程序/xml”媒体类型的字符集参数具有相同的语义。
Encoding considerations: Identical to those of "application/xml" as described in Section 9.1 of [RFC7303].
编码注意事项：与[RFC7303]第9.1节中描述的“应用程序/xml”相同。
Security considerations: As defined in Section 7. In addition, as this media type uses the "+xml" convention, it inherits the security considerations described in Section 10 of [RFC7303].
安全注意事项：如第7节所定义。此外，由于此媒体类型使用“+xml”约定，因此它继承了[RFC7303]第10节中描述的安全注意事项。
Interoperability considerations: Some aspects of this vocabulary currently cannot be used interoperably; among the reasons for this are that they weren't precisely defined in the first place, that they have been added in an ad hoc fashion later on, or that they are specific to certain output formats. This specification attempts to identify these cases in the description of the individual elements/attributes.
互操作性注意事项：该词汇表的某些方面目前无法互操作使用；其原因之一是，它们最初没有精确定义，后来以特殊方式添加，或者特定于某些输出格式。本规范试图在单个元素/属性的描述中识别这些情况。
Published specification: This specification.
已发布规范：本规范。
Applications that use this media type: Applications that transform xml2rfc to output formats such as plain text or HTML, plus additional analysis tools.
使用此媒体类型的应用程序：将xml2rfc转换为纯文本或HTML等输出格式的应用程序，以及其他分析工具。
Fragment identifier considerations: The "anchor" attribute is used for assigning document-wide unique identifiers that can be used as shorthand pointers, as described in Section 3.2 of [XPOINTER].
片段标识符注意事项：“anchor”属性用于分配可用作速记指针的文档范围的唯一标识符，如[XPOINTER]第3.2节所述。
Additional information:
其他信息：
Deprecated alias names for this type: None.
此类型的已弃用别名：无。
Magic number(s): As specified for "application/xml" in Section 9.1 of [RFC7303].
幻数：如[RFC7303]第9.1节中“应用程序/xml”所述。
File extension(s): .xml or .rfcxml when disambiguation from other XML files is needed.
文件扩展名：.xml或.rfcxml（当需要从其他xml文件中消除歧义时）。
Macintosh file type code(s): TEXT
Macintosh文件类型代码：文本
Person & email address to contact for further information: See the Author's Address section of RFC 7749.
联系人和电子邮件地址了解更多信息：请参阅RFC 7749的作者地址部分。
Intended usage: COMMON
预期用途：普通
Restrictions on usage: None.
使用限制：无。
Author: See the Author's Address section of RFC 7749.
作者：参见RFC 7749的作者地址部分。
Change controller: RFC Series Editor (rse@rfc-editor.org)
更改控制器：RFC系列编辑器(rse@rfc-（www.editor.org）
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, November 1996, <http://www.rfc-editor.org/info/rfc2046>.
[RFC2046]Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第二部分：媒体类型”，RFC 2046，DOI 10.17487/RFC2046，1996年11月<http://www.rfc-editor.org/info/rfc2046>.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, DOI 10.17487/RFC3966, December 2004, <http://www.rfc-editor.org/info/rfc3966>.
[RFC3966]Schulzrinne，H.，“电话号码的电话URI”，RFC 3966，DOI 10.17487/RFC3966，2004年12月<http://www.rfc-editor.org/info/rfc3966>.
[RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010, <http://www.rfc-editor.org/info/rfc6068>.
[RFC6068]Duerst，M.，Masinter，L.，和J.Zawinski，“mailto”URI方案”，RFC 6068，DOI 10.17487/RFC6068，2010年10月<http://www.rfc-editor.org/info/rfc6068>.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, DOI 10.17487/RFC7303, July 2014, <http://www.rfc-editor.org/info/rfc7303>.
[RFC7303]Thompson，H.和C.Lilley，“XML媒体类型”，RFC 7303，DOI 10.17487/RFC7303，2014年7月<http://www.rfc-editor.org/info/rfc7303>.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, November 2008, <http://www.w3.org/TR/2008/REC-xml-20081126/>.
[XML]Bray，T.，Paoli，J.，Sperberg McQueen，C.，Maler，E.，和F.Yergeau，“可扩展标记语言（XML）1.0（第五版）”，W3C建议REC-XML-20081126，2008年11月<http://www.w3.org/TR/2008/REC-xml-20081126/>.
Latest version available at <http://www.w3.org/TR/xml>.
最新版本可于<http://www.w3.org/TR/xml>.
[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, January 2013, <http://www.rfc-editor.org/info/bcp13>.
[BCP13]Freed，N.，Klensin，J.和T.Hansen，“媒体类型规范和注册程序”，BCP 13，RFC 6838，2013年1月<http://www.rfc-editor.org/info/bcp13>.
[CSS] Bos, B., Celic, T., Hickson, I., and H. Lie, "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification", W3C Recommendation REC-CSS2-20110607, June 2011, <http://www.w3.org/TR/2011/REC-CSS2-20110607/>.
[CSS]Bos，B.，Celic，T.，Hickson，I.，和H.Lie，“级联样式表第2级修订版1（CSS 2.1）规范”，W3C建议REC-CSS2-20110607，2011年6月<http://www.w3.org/TR/2011/REC-CSS2-20110607/>.
Latest version available at <http://www.w3.org/TR/CSS2>.
最新版本可于<http://www.w3.org/TR/CSS2>.
[HTML] Hickson, I., Berjon, R., Faulkner, S., Leithead, T., Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", W3C Recommendation REC-html5-20141028, October 2014, <http://www.w3.org/TR/2014/REC-html5-20141028/>.
[HTML]Hickson，I.，Berjon，R.，Faulkner，S.，Leithead，T.，Doyle Navara，E.，O'Connor，E.，和S.Pfeiffer，“HTML5”，W3C建议REC-HTML5-20141028，2014年10月<http://www.w3.org/TR/2014/REC-html5-20141028/>.
Latest version available at <http://www.w3.org/TR/html5/>.
最新版本可于<http://www.w3.org/TR/html5/>.
[IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts", December 2010, <http://www.ietf.org/id-info/guidelines.html>.
[IDGUIDE]Housley，R.，“互联网草稿作者指南”，2010年12月<http://www.ietf.org/id-info/guidelines.html>.
[JING] Thai Open Source Software Center Ltd, "Jing - A RELAX NG validator in Java", 2008, <http://www.thaiopensource.com/relaxng/jing.html>.
[JING]泰国开源软件中心有限公司，“JING-Java中的RELAXNG验证程序”，2008年<http://www.thaiopensource.com/relaxng/jing.html>.
Downloads: <https://code.google.com/p/jing-trang/ downloads/list>.
下载：<https://code.google.com/p/jing-trang/ 下载/列表>。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, <http://www.rfc-editor.org/info/rfc2026>.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，DOI 10.17487/RFC2026，1996年10月<http://www.rfc-editor.org/info/rfc2026>.
[RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 2223, DOI 10.17487/RFC2223, October 1997, <http://www.rfc-editor.org/info/rfc2223>.
[RFC2223]Postel，J.和J.Reynolds，“RFC作者须知”，RFC 2223，DOI 10.17487/RFC2223，1997年10月<http://www.rfc-editor.org/info/rfc2223>.
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, DOI 10.17487/RFC2397, August 1998, <http://www.rfc-editor.org/info/rfc2397>.
[RFC2397]Masinter，L.，“数据”URL方案，RFC 2397，DOI 10.17487/RFC2397，1998年8月<http://www.rfc-editor.org/info/rfc2397>.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, June 1999, <http://www.rfc-editor.org/info/rfc2629>.
[RFC2629]Rose，M.“使用XML编写I-D和RFC”，RFC 2629，DOI 10.17487/RFC2629，1999年6月<http://www.rfc-editor.org/info/rfc2629>.
[RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols", BCP 70, RFC 3470, DOI 10.17487/RFC3470, January 2003, <http://www.rfc-editor.org/info/rfc3470>.
[RFC3470]Hollenbeck，S.，Rose，M.，和L.Masinter，“IETF协议中可扩展标记语言（XML）的使用指南”，BCP 70，RFC 3470，DOI 10.17487/RFC3470，2003年1月<http://www.rfc-editor.org/info/rfc3470>.
[RFC3667] Bradner, S., "IETF Rights in Contributions", RFC 3667, DOI 10.17487/RFC3667, February 2004, <http://www.rfc-editor.org/info/rfc3667>.
[RFC3667]Bradner，S.，“IETF在贡献中的权利”，RFC 3667，DOI 10.17487/RFC3667，2004年2月<http://www.rfc-editor.org/info/rfc3667>.
[RFC3978] Bradner, S., Ed., "IETF Rights in Contributions", RFC 3978, DOI 10.17487/RFC3978, March 2005, <http://www.rfc-editor.org/info/rfc3978>.
[RFC3978]Bradner，S.，Ed.，“IETF在贡献中的权利”，RFC 3978，DOI 10.17487/RFC3978，2005年3月<http://www.rfc-editor.org/info/rfc3978>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <http://www.rfc-editor.org/info/rfc3986>.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，DOI 10.17487/RFC3986，2005年1月<http://www.rfc-editor.org/info/rfc3986>.
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <http://www.rfc-editor.org/info/rfc5234>.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，DOI 10.17487/RFC5234，2008年1月<http://www.rfc-editor.org/info/rfc5234>.
[RFC5378] Bradner, S., Ed., and J. Contreras, Ed., "Rights Contributors Provide to the IETF Trust", BCP 78, RFC 5378, DOI 10.17487/RFC5378, November 2008, <http://www.rfc-editor.org/info/rfc5378>.
[RFC5378]Bradner，S.，Ed.，和J.Contreras，Ed.，“向IETF信托提供的权利贡献者”，BCP 78，RFC 5378，DOI 10.17487/RFC5378，2008年11月<http://www.rfc-editor.org/info/rfc5378>.
[RFC5598] Crocker, D., "Internet Mail Architecture", RFC 5598, DOI 10.17487/RFC5598, July 2009, <http://www.rfc-editor.org/info/rfc5598>.
[RFC5598]Crocker，D.，“互联网邮件体系结构”，RFC 5598，DOI 10.17487/RFC5598，2009年7月<http://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., Ed., Kolkman, O., Ed., and IAB, "RFC Streams, Headers, and Boilerplates", RFC 5741, DOI 10.17487/RFC5741, December 2009, <http://www.rfc-editor.org/info/rfc5741>.
[RFC5741]Daigle，L.，Ed.，Kolkman，O.，Ed.，和IAB，“RFC流，标题和样板”，RFC 5741，DOI 10.17487/RFC57411909年12月<http://www.rfc-editor.org/info/rfc5741>.
[RFC6266] Reschke, J., "Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)", RFC 6266, DOI 10.17487/RFC6266, June 2011, <http://www.rfc-editor.org/info/rfc6266>.
[RFC6266]Reschke，J.，“超文本传输协议（HTTP）中内容处置头字段的使用”，RFC 6266，DOI 10.17487/RFC6266，2011年6月<http://www.rfc-editor.org/info/rfc6266>.
[RFC7322] Flanagan, H. and S. Ginoza, "RFC Style Guide", RFC 7322, DOI 10.17487/RFC7322, September 2014, <http://www.rfc-editor.org/info/rfc7322>.
[RFC7322]Flanagan，H.和S.Ginoza，“RFC风格指南”，RFC 7322，DOI 10.17487/RFC7322，2014年9月<http://www.rfc-editor.org/info/rfc7322>.
[RNC] Clark, J., "RELAX NG Compact Syntax", OASIS, November 2002, <http://www.oasis-open.org/committees/ relax-ng/compact-20021121.html>.
[RNC]Clark，J.，“RELAXNG紧凑语法”，OASIS，2002年11月<http://www.oasis-open.org/committees/ relax ng/compact-20021121.html>。
[TCLReadme] Rose, M., Fenner, B., and C. Levert, "xml2rfc v1.35pre1", October 2009, <http://svn.tools.ietf.org/svn/tools/ xml2rfc/archive/README.html>.
[TCLReadme]Rose，M.，Fenner，B.和C.Levert，“xml2rfc v1.35pre1”，2009年10月<http://svn.tools.ietf.org/svn/tools/ xml2rfc/archive/README.html>。
[TLP1.0] IETF Trust, "Legal Provisions Relating to IETF Documents", November 2008, <http://trustee.ietf.org/license-info/IETF-TLP-1.htm>.
[TLP1.0]IETF信托，“与IETF文件相关的法律规定”，2008年11月<http://trustee.ietf.org/license-info/IETF-TLP-1.htm>.
[TLP2.0] IETF Trust, "Legal Provisions Relating to IETF Documents", February 2009, <http://trustee.ietf.org/license-info/IETF-TLP-2.htm>.
[TLP2.0]IETF信托，“与IETF文件相关的法律规定”，2009年2月<http://trustee.ietf.org/license-info/IETF-TLP-2.htm>.
[TLP3.0] IETF Trust, "Legal Provisions Relating to IETF Documents", September 2009, <http://trustee.ietf.org/license-info/IETF-TLP-3.htm>.
[TLP3.0]IETF信托，“与IETF文件相关的法律规定”，2009年9月<http://trustee.ietf.org/license-info/IETF-TLP-3.htm>.
[TLP4.0] IETF Trust, "Legal Provisions Relating to IETF Documents", December 2009, <http://trustee.ietf.org/license-info/IETF-TLP-4.htm>.
[TLP4.0]IETF信托，“与IETF文件相关的法律规定”，2009年12月<http://trustee.ietf.org/license-info/IETF-TLP-4.htm>.
[TLP5.0] IETF Trust, "Legal Provisions Relating to IETF Documents", March 2015, <http://trustee.ietf.org/license-info/IETF-TLP-5.htm>.
[TLP5.0]IETF信托，“与IETF文件相关的法律规定”，2015年3月<http://trustee.ietf.org/license-info/IETF-TLP-5.htm>.
[UNICODE] The Unicode Consortium, "The Unicode Standard", <http://www.unicode.org/versions/latest/>.
[UNICODE]UNICODE联盟，“UNICODE标准”<http://www.unicode.org/versions/latest/>.
[USASCII] American National Standards Institute, "Coded Character Set -- 7-bit American Standard Code for Information Interchange", ANSI X3.4, 1986.
[USASCII]美国国家标准协会，“编码字符集——信息交换用7位美国标准代码”，ANSI X3.41986。
[V1rev] Rose, M., "Writing I-Ds and RFCs using XML (revised)", February 2008, <http://svn.tools.ietf.org/svn/tools/xml2rfc/archive/ draft-mrose-writing-rfcs.html>.
[V1rev]Rose，M.“使用XML编写I-D和RFC（修订版）”，2008年2月<http://svn.tools.ietf.org/svn/tools/xml2rfc/archive/ 草稿mrose正在编写rfcs.html>。
[XPOINTER] Grosso, P., Maler, E., Marsh, J., and N. Walsh, "XPointer Framework", W3C Recommendation REC-xptr-framework-20030325, March 2003, <http://www.w3.org/TR/2003/REC-xptr-framework-20030325/>.
[XPOINTER]Grosso，P.，Maler，E.，Marsh，J.，和N.Walsh，“XPOINTER框架”，W3C建议REC-xptr-Framework-200303252003年3月<http://www.w3.org/TR/2003/REC-xptr-framework-20030325/>.
Latest version available at <http://www.w3.org/TR/xptr-framework/>.
最新版本可于<http://www.w3.org/TR/xptr-framework/>.
Appendix A. Front-Page ("Boilerplate") Generation
附录A.首页（“样板文件”）生成
For RFCs, the "category" attribute (Section 2.33.1) determines the "maturity level" (see Section 4 of [RFC2026]). The allowed values are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for "Historic".
对于RFC，“类别”属性（第2.33.1节）决定“成熟度水平”（见[RFC2026]第4节）。允许值为“标准轨道”的“std”，“bcp”的“bcp”，“信息”的“info”，“实验”的“exp”和“历史”的“历史”。
For Internet-Drafts, the "category" attribute is not needed; when supplied, it will appear as "Intended Status". Supplying this information can be useful to reviewers.
对于Internet草稿，不需要“类别”属性；提供时，它将显示为“预期状态”。提供这些信息对审阅者很有用。
This attribute value can take a long list of values, each of which describes an IPR policy for the document (Section 2.33.4). The values are not the result of a grand design, but they remain simply for historic reasons. Of these values, only a few are currently in use; all others are supported by various tools for backwards compatibility with old source files.
该属性值可以包含一长串值，每个值都描述了文档的IPR策略（第2.33.4节）。这些价值观并不是宏伟设计的结果，但它们只是出于历史原因而存在。在这些值中，只有少数值目前正在使用；所有其他工具都支持与旧源文件向后兼容的各种工具。
*Note:* some variations of the boilerplate are selected based on the document's date; therefore, it is important to specify the "year", "month", and "day" attributes of the <date> element when archiving the XML source of an Internet-Draft on the day of submission.
*注：*样板文件的某些变体是根据文件日期选择的；因此，在提交当天归档Internet草稿的XML源时，指定<date>元素的“年”、“月”和“日”属性非常重要。
_Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER._ For further information, refer to <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf>.
_免责声明：这仅提供实现信息。如果您需要法律咨询，请联系律师。\有关更多信息，请参阅<http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf>.
For the current "Status of This Memo" text, the "submissionType" attribute (Section 2.33.9) determines whether a statement about "Code Components" is inserted (which is the case for the value "IETF", which is the default). Other values, such as "independent", suppress this part of the text.
对于当前的“本备忘录状态”文本，“submissionType”属性（第2.33.9节）确定是否插入了关于“代码组件”的语句（默认值为“IETF”）。其他值（如“独立”）会抑制文本的这一部分。
The name for these values refers to the IETF Trust's "Legal Provisions Relating to IETF Documents", sometimes simply called the "TLP", which went into effect on February 15, 2009 [TLP2.0]. Updates to this document were published on September 12, 2009 [TLP3.0] and on December 28, 2009 [TLP4.0], modifying the license for code components (see <http://trustee.ietf.org/license-info/> for further information). The actual text is located in Section 6 ("Text to Be Included in IETF Documents") of these documents.
这些价值的名称指IETF信托的“与IETF文件相关的法律规定”，有时简称为“TLP”，于2009年2月15日生效[TLP2.0]。本文档的更新发布于2009年9月12日[TLP3.0]和2009年12月28日[TLP4.0]，修改了代码组件的许可证（请参阅<http://trustee.ietf.org/license-info/>以获取更多信息）。实际文本位于这些文件的第6节（“IETF文件中包含的文本”）。
Formatters will automatically produce the "correct" text, depending on the document's date information (see above):
格式化程序将根据文档的日期信息自动生成“正确”文本（见上文）：
+----------+--------------------------------+
| TLP | starting with publication date |
+----------+--------------------------------+
| [TLP3.0] | 2009-11-01 |
| [TLP4.0] | 2010-04-01 |
+----------+--------------------------------+
+----------+--------------------------------+
| TLP | starting with publication date |
+----------+--------------------------------+
| [TLP3.0] | 2009-11-01 |
| [TLP4.0] | 2010-04-01 |
+----------+--------------------------------+
The TLP was again updated in March 2015 ([TLP5.0]), but the changes made in that version do not affect the boilerplate text.
TLP于2015年3月再次更新（[TLP5.0]），但该版本中所做的更改不会影响样板文本。
This value should be used unless one of the more specific "*trust200902" values is a better fit. It produces the text in Sections 6.a and 6.b of the TLP.
除非更具体的“*trust200902”值之一更适合，否则应使用此值。它产生TLP第6.a和6.b节中的文本。
This produces additional text from Section 6.c.i of the TLP:
这将产生TLP第6.c.i节的附加文本：
This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.
不得修改本文件，也不得创建其衍生作品，除非将其格式化为RFC出版或将其翻译为英语以外的其他语言。
*Note:* this clause is incompatible with RFCs that are published on the Standards Track.
*注：*本条款与标准轨道上发布的RFC不兼容。
This produces the additional text from Section 6.c.ii of the TLP:
这将产生TLP第6.c.ii节中的附加文本：
This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft.
本文件不得修改，不得创作其衍生作品，不得出版，除非作为互联网草稿。
*Note:* this clause is incompatible with RFCs.
*注：*本条款与RFC不兼容。
This produces the additional text from Section 6.c.iii of the TLP, frequently called the "pre-5378 escape clause" (referring to changes introduced in [RFC5378]):
这产生了TLP第6.c.iii节的附加文本，通常称为“5378之前的免责条款”（参考[RFC5378]中引入的变更）：
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 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 into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
See Section 4 of <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf> for further information about when to use this value.
见本报告第4节<http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf>有关何时使用此值的详细信息。
*Note:* this text appears under "Copyright Notice", unless the document was published before November 2009, in which case it appears under "Status of This Memo".
*注：*本文本出现在“版权声明”下，除非该文件在2009年11月之前发布，在这种情况下，它出现在“本备忘录的状态”下。
The attribute values "trust200811", "noModificationTrust200811", and "noDerivativesTrust200811" are similar to their "trust200902" counterparts, except that they use text specified in [TLP1.0].
属性值“trust200811”、“noModificationTrust200811”和“noDerivativesTrust200811”与其对应的“trust200902”类似，只是它们使用了[TLP1.0]中指定的文本。
The attribute values "full3978", "noModification3978", and "noDerivatives3978" are similar to their counterparts above, except that they use text specified in Section 5 of [RFC3978].
属性值“full3978”、“noModification3978”和“noDerivatives3978”与上面的对应项类似，只是它们使用了[RFC3978]第5节中规定的文本。
The attribute values "full3667", "noModification3667", and "noDerivatives3667" are similar to their counterparts above, except that they use text specified in Section 5 of [RFC3667].
属性值“full3667”、“noModification3667”和“noDerivatives3667”与其上面的对应项类似，只是它们使用了[RFC3667]第5节中指定的文本。
The attribute values "full2026" and "noDerivativeWorks2026" are similar to their counterparts above, except that they use text specified in Section 10 of [RFC2026].
属性值“full2026”和“NODERIVATIVEWORK2026”与上述对应值类似，只是它们使用了[RFC2026]第10节中指定的文本。
The special value "none" was also used back then; it denied the IETF any rights beyond publication as an Internet-Draft.
当时还使用了特殊值“无”；它否认IETF除了作为互联网草案出版之外的任何权利。
The RFC Editor publishes documents from different document streams, of which the IETF stream is the most prominent. Other streams are the independent stream (used for things such as discussion of Internet-related technologies that are not part of the IETF agenda), the IAB stream (Internet Architecture Board) and the IRTF stream (Internet Research Task Force).
RFC编辑器发布来自不同文档流的文档，其中IETF流最为突出。其他流包括独立流（用于讨论不属于IETF议程的互联网相关技术）、IAB流（互联网架构委员会）和IRTF流（互联网研究任务组）。
The values for the attribute are "IETF" (the default value), "independent", "IAB", and "IRTF".
该属性的值为“IETF”（默认值）、“independent”、“IAB”和“IRTF”。
Historically, this attribute did not affect the final appearance of RFCs, except for subtle differences in copyright notices. Nowadays (as of [RFC5741]), the stream name appears in the first line of the front page, and it also affects the text in the "Status of This Memo" section.
从历史上看，除了版权声明中的细微差异外，该属性不会影响RFC的最终外观。现在（从[RFC5741]开始），流名称出现在首页的第一行，它也影响“此备忘录的状态”部分的文本。
For current documents, setting the "submissionType" attribute will have the following effect:
对于当前文档，设置“submissionType”属性将产生以下效果：
o For RFCs, the stream name appears in the upper left corner of the first page (in Internet-Drafts, this is either "Network Working Group" or the value of the <workgroup> element).
o 对于RFC，流名称显示在第一页的左上角（在Internet草稿中，这是“网络工作组”或<workgroup>元素的值）。
o For RFCs, it affects the whole "Status of This Memo" section (see Section 3.2.2 of [RFC5741]).
o 对于RFC，它影响整个“本备忘录的状态”部分（见[RFC5741]第3.2.2节）。
o For all RFCs and Internet-Drafts, it determines whether the "Copyright Notice" mentions the copyright on Code Components (see Section 6 of the TLP ("Text to Be Included in IETF Documents")).
o 对于所有RFC和互联网草案，它确定“版权通知”是否提及代码组件的版权（见TLP第6节（“将包含在IETF文件中的文本”））。
For some of the publication streams (see Appendix A.3), the "Status of This Memo" section depends on whether there was a consensus to publish (again, see Section 3.2.2 of [RFC5741]).
对于一些发布流（见附录A.3），“本备忘录的状态”部分取决于是否达成了发布共识（同样，见[RFC5741]第3.2.2节）。
The "consensus" attribute ("yes"/"no", defaulting to "yes") can be used to supply this information. The effect for the various streams is:
“共识”属性（“是”/“否”，默认为“是”）可用于提供此信息。各种流的影响是：
o "independent" and "IAB": none.
o “独立”和“IAB”：无。
o "IETF": mention that there was an IETF consensus.
o “IETF”：提及IETF达成共识。
o "IRTF": mention that there was a research group consensus (where the name of the research group is extracted from the <workgroup> element).
o “IRTF”：提到有一个研究小组共识（其中研究小组的名称取自<workgroup>元素）。
Appendix B. Changes from RFC 2629 ("v1")
附录B.RFC 2629（“v1”）的变更
The <appendix> element has been removed; to generate an appendix, place a <section> inside <back>.
已删除<appendix>元素；要生成附录，请在<back>内放置<section>。
Many attributes have lost their "default" value; this is to avoid having document semantics differ based on whether a DTD was specified and evaluated. Processors will handle absent values the way the default value was specified before.
许多属性已失去其“默认”值；这是为了避免文档语义因是否指定和评估了DTD而有所不同。处理器将按照之前指定的默认值处理缺少的值。
<artwork>: Has a set of new attributes: "name", "type", "src",
"align", "alt", "width", and "height". (Section 2.5)
<artwork>: Has a set of new attributes: "name", "type", "src",
"align", "alt", "width", and "height". (Section 2.5)
<author>: The <organization> element is now optional. The "role"
attribute was added. (Section 2.6)
<author>: The <organization> element is now optional. The "role"
attribute was added. (Section 2.6)
<country>: The requirement to use ISO 3166 codes was removed.
(Section 2.11)
<country>: The requirement to use ISO 3166 codes was removed.
(Section 2.11)
<date>: All attributes are now optional. (Section 2.13)
<date>: All attributes are now optional. (Section 2.13)
<figure>: Has a set of new attributes: "suppress-title", "src",
"align", "alt", "width", and "height". (Section 2.17)
<figure>: Has a set of new attributes: "suppress-title", "src",
"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 values anymore. The "hangIndent" and "counter" attributes have been added. (Section 2.22)
<list>：不再将“style”属性限制为一组枚举值。添加了“hangIndent”和“counter”属性。（第2.22节）
<reference>: <annotation> allows adding prose to a reference. The
"anchor" attribute has been made mandatory. (Section 2.30)
<reference>: <annotation> allows adding prose to a reference. The
"anchor" attribute has been made mandatory. (Section 2.30)
<references>: Can now appear multiple times and can carry a "title" attribute (so that normative and informative references can be split). (Section 2.31)
<references>：现在可以多次出现，并且可以带有“title”属性（以便可以拆分规范性引用和信息性引用）。（第2.31节）
<rfc>: The "ipr" attribute has gained additional values. The attributes "consensus", "iprExtract", "submissionType", and "xml:lang" have been added. (Section 2.33)
<rfc>：“ipr”属性已获得附加值。添加了属性“共识”、“iprExtract”、“submissionType”和“xml:lang”。（第2.33节）
<section>: The new "toc" attribute controls whether it will appear in
the Table Of Contents. <iref> can now appear as a direct child
element. (Section 2.34)
<section>: The new "toc" attribute controls whether it will appear in
the Table Of Contents. <iref> can now appear as a direct child
element. (Section 2.34)
<t>: The "anchor" attribute can now be used as well; however, there
are restrictions on how they can be referred to. (Section 2.38)
<t>: The "anchor" attribute can now be used as well; however, there
are restrictions on how they can be referred to. (Section 2.38)
The following elements have been added: <annotation> (Section 2.3), <c> (Section 2.8), <cref> (Section 2.12), <format> (Section 2.18), <spanx> (Section 2.36), <texttable> (Section 2.39), and <ttcol> (Section 2.41).
添加了以下元素：<annotation>（第2.3节）、<c>（第2.8节）、<cref>（第2.12节）、<format>（第2.18节）、<spanx>（第2.36节）、<texttable>（第2.39节）和<ttcol>（第2.41节）。
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?
}
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 =
element front {
title,
author+,
date,
area*,
workgroup*,
keyword*,
abstract?,
note*
}
front =
element front {
title,
author+,
date,
area*,
workgroup*,
keyword*,
abstract?,
note*
}
title =
element title {
attribute abbrev { text }?,
text
}
title =
element title {
attribute abbrev { text }?,
text
}
author =
element author {
attribute initials { text }?,
attribute surname { text }?,
attribute fullname { text }?,
attribute role { "editor" }?,
organization?,
address?
}
author =
element author {
attribute initials { text }?,
attribute surname { text }?,
attribute fullname { text }?,
attribute role { "editor" }?,
organization?,
address?
}
organization =
element organization {
attribute abbrev { text }?,
text
}
organization =
element organization {
attribute abbrev { text }?,
text
}
address = element address { postal?, phone?, facsimile?, email?, uri? }
地址=元素地址{邮政？、电话？、传真？、电子邮件？、uri？}
postal =
element postal { street+, (city | region | code | country)* }
postal =
element postal { street+, (city | region | code | country)* }
street = element street { text }
street = element street { text }
city = element city { text }
city = element city { text }
region = element region { text }
region = element region { text }
code = element code { text }
code = element code { text }
country = element country { text }
country = element country { text }
phone = element phone { text }
phone = element phone { text }
facsimile = element facsimile { text }
facsimile = element facsimile { text }
email = element email { text }
email = element email { text }
uri = element uri { text }
uri = element uri { text }
date =
element date {
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
date =
element date {
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
area = element area { text }
area = element area { text }
workgroup = element workgroup { text }
workgroup = element workgroup { text }
keyword = element keyword { text }
keyword = element keyword { text }
abstract = element abstract { t+ }
abstract = element abstract { t+ }
note =
element note {
attribute title { text },
t+
}
note =
element note {
attribute title { text },
t+
}
middle = element middle { section+ }
middle = element middle { section+ }
section =
element section {
attribute anchor { xsd:ID }?,
attribute title { text },
[ a:defaultValue = "default" ]
attribute toc { "include" | "exclude" | "default" }?,
(t | figure | texttable | iref)*,
section*
}
section =
element section {
attribute anchor { xsd:ID }?,
attribute title { text },
[ a:defaultValue = "default" ]
attribute toc { "include" | "exclude" | "default" }?,
(t | figure | texttable | iref)*,
section*
}
t =
element t {
attribute anchor { xsd:ID }?,
attribute hangText { text }?,
(text
| \list
| figure
| xref
| eref
| iref
| cref
| spanx
| vspace)*
}
t =
element t {
attribute anchor { xsd:ID }?,
attribute hangText { text }?,
(text
| \list
| figure
| xref
| eref
| iref
| cref
| spanx
| vspace)*
}
\list =
element list {
attribute style { text }?,
attribute hangIndent { text }?,
attribute counter { text }?,
t+
}
\list =
element list {
attribute style { text }?,
attribute hangIndent { text }?,
attribute counter { text }?,
t+
}
xref =
element xref {
attribute target { xsd:IDREF },
[ a:defaultValue = "false" ]
attribute pageno { "true" | "false" }?,
[ a:defaultValue = "default" ]
attribute format { "counter" | "title" | "none" | "default" }?,
text
}
xref =
element xref {
attribute target { xsd:IDREF },
[ a:defaultValue = "false" ]
attribute pageno { "true" | "false" }?,
[ a:defaultValue = "default" ]
attribute format { "counter" | "title" | "none" | "default" }?,
text
}
eref =
element eref {
attribute target { text },
text
}
eref =
element eref {
attribute target { text },
text
}
iref =
element iref {
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
empty
}
iref =
element iref {
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
empty
}
cref =
element cref {
attribute anchor { xsd:ID }?,
attribute source { text }?,
text
}
cref =
element cref {
attribute anchor { xsd:ID }?,
attribute source { text }?,
text
}
spanx =
element spanx {
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
text
}
spanx =
element spanx {
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
text
}
vspace =
element vspace {
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
vspace =
element vspace {
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
figure =
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?
}
figure =
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?
}
preamble =
element preamble { (text | xref | eref | iref | cref | spanx)* }
preamble =
element preamble { (text | xref | eref | iref | cref | spanx)* }
artwork =
element artwork {
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "" ] attribute type { text }?,
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 }?,
text*
}
artwork =
element artwork {
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "" ] attribute type { text }?,
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 }?,
text*
}
postamble =
element postamble { (text | xref | eref | iref | cref | spanx)* }
postamble =
element postamble { (text | xref | eref | iref | cref | spanx)* }
texttable =
element texttable {
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
[ a:defaultValue = "center" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "full" ]
attribute style { "all" | "none" | "headers" | "full" }?,
preamble?,
ttcol+,
c*,
postamble?
}
texttable =
element texttable {
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
[ a:defaultValue = "center" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "full" ]
attribute style { "all" | "none" | "headers" | "full" }?,
preamble?,
ttcol+,
c*,
postamble?
}
ttcol =
element ttcol {
attribute width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
text
}
ttcol =
element ttcol {
attribute width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
text
}
c = element c { (text | xref | eref | iref | cref | spanx)* }
c = element c { (text | xref | eref | iref | cref | spanx)* }
back = element back { references*, section* }
back = element back { references*, section* }
references =
element references {
[ a:defaultValue = "References" ] attribute title { text }?,
reference+
}
references =
element references {
[ a:defaultValue = "References" ] attribute title { text }?,
reference+
}
reference =
element reference {
attribute anchor { xsd:ID },
attribute target { text }?,
front,
seriesInfo*,
format*,
annotation*
}
reference =
element reference {
attribute anchor { xsd:ID },
attribute target { text }?,
front,
seriesInfo*,
format*,
annotation*
}
seriesInfo =
element seriesInfo {
attribute name { text },
attribute value { text },
empty
}
seriesInfo =
element seriesInfo {
attribute name { text },
attribute value { text },
empty
}
format =
element format {
attribute target { text }?,
attribute type { text },
attribute octets { text }?,
empty
}
format =
element format {
attribute target { text }?,
attribute type { text },
attribute octets { text }?,
empty
}
annotation =
element annotation { (text | xref | eref | iref | cref | spanx)* }
annotation =
element annotation { (text | xref | eref | iref | cref | spanx)* }
start = rfc
start = rfc
(This schema was derived from version 1.3.6 of the xml2rfc DTD ("Document Type Definition") (Section 2.8 of [XML]), available from <http://svn.tools.ietf.org/svn/tools/xml2rfc/vocabulary/v2/03/ xml2rfcv2.dtd>.)
（此模式源自xml2rfc DTD（文档类型定义）的1.3.6版（XML的第2.8节），可从<http://svn.tools.ietf.org/svn/tools/xml2rfc/vocabulary/v2/03/ xml2rfcv2.dtd>）
The validity of XML files can be checked with any tool that supports RELAX NG [RNC]. The reference implementation is the Java-based, open-sourced "Jing" [JING].
可以使用任何支持RELAX NG[RNC]的工具检查XML文件的有效性。参考实现是基于Java的开源“Jing”[Jing]。
To use Jing, download the latest ZIP file from the "downloads" page (currently <https://code.google.com/p/jing-trang/downloads/ detail?name=jing-20091111.zip>), extract the archive, copy "jing.jar" from the "bin" folder, and make sure Java is installed.
要使用Jing，请从“下载”页面下载最新的ZIP文件（当前为<https://code.google.com/p/jing-trang/downloads/ detail？name=jing-20091111.zip>），提取归档文件，从“bin”文件夹复制“jing.jar”，并确保安装了Java。
To check a file "test.xml" using the RNC file "schema.rnc", run (from a command-line prompt):
要使用RNC文件“schema.RNC”检查文件“test.xml”，请运行（从命令行提示符）：
java -jar jing.jar -c schema.rnc test.xml
java-jar-jing.jar-cschema.rnc test.xml
In good Unix tradition, no output means the file is valid.
在良好的Unix传统中，没有输出意味着文件是有效的。
IAB Members at the Time of Approval
批准时的IAB成员
Jari Arkko (IETF Chair) Mary Barnes Marc Blanchet Ralph Droms Ted Hardie Joe Hildebrand Russ Housley Erik Nordmark Robert Sparks Andrew Sullivan Dave Thaler Brian Trammell Suzanne Woolf
Jari Arkko（IETF主席）Mary Barnes Marc Blanchet Ralph Droms Ted Hardie Joe Hildebrand Russ Housley Erik Nordmark Robert Sparks Andrew Sullivan Dave Thaler Brian Trammell Suzanne Woolf
Acknowledgments
致谢
Thanks to everybody who reviewed this document and provided feedback and/or specification text, in particular Brian Carpenter, Elwyn Davies, Tony Hansen, Joe Hildebrand, Paul Hoffman, Henrik Levkowetz, Alice Russo, Tom Taylor, Dave Thaler, Jim Schaad, and Nico Williams.
感谢审阅本文件并提供反馈和/或规范文本的所有人，特别是Brian Carpenter、Elwyn Davies、Tony Hansen、Joe Hildebrand、Paul Hoffman、Henrik Levkowetz、Alice Russo、Tom Taylor、Dave Thaler、Jim Schaad和Nico Williams。
We also thank Marshall T. Rose for both the original design and the reference implementation of the "xml2rfc" formatter.
我们还感谢Marshall T.Rose对“xml2rfc”格式化程序的原始设计和参考实现。
Index
指数
A Attributes abbrev 21, 34 align 7, 14, 32, 34 alt 7, 15 anchor 11, 15, 23, 28, 31-32 blankLines 35 category 25 consensus 25 counter 18 day 12 docName 25 format 36 fullname 9 hangIndent 18 hangText 31 height 7, 15 initials 9 ipr 26 iprExtract 26 item 17 month 12 name 7, 29 number 27 obsoletes 27 octets 16 pageno 37 primary 17 role 9 seriesNo 27 source 12 src 7, 15 style 19, 30, 32 subitem 17 submissionType 27 suppress-title 15, 33 surname 10 target 13, 16, 23, 37 title 15, 21, 24, 28, 33 toc 28 type 8, 16 updates 27 value 29 width 8, 15, 34
A属性缩写21，34对齐7，14，32，34替换7，15锚11，15，23，28，31-32空行35类别25共识25计数器18天12文件名25格式36全名9悬挂缩进18悬挂文本31高度7，15首字母9 ipr 26 iprExtract 26项目17月12名称7，29编号27废弃27八位字节16页码37主要17角色9系列编号27来源12 src 7，15样式19，30，32子项17提交类型27禁止标题15，33姓氏10目标13，16，23，37标题15，21，24，28，33 toc 28类型8，16更新27值29宽度8，15，34
xml:lang 28 xml:space 8, 30 year 13 abbrev attribute in organization element 21 in title element 34 abstract element 4, 50 inside front 16 address element 4, 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 15 anchor attribute in cref element 11 in figure element 15 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 initials attribute 9 inside front 16 role attribute 9 surname attribute 10
xml:lang 28 xml:space 8，30年13 abbrev属性在组织元素21在标题元素34抽象元素4，50在前16地址元素4，50 Inner author 9 align属性在artwork元素7中在texttable元素14中在ttcol元素32中在artwork元素7中在figure元素15中在alt属性在artwork元素7中在figure元素15中在cref元素11中在figure元素15中在reference元素23中在section元素28中在texttable元素31中在texttable元素32注释元素5中，50内部参考23应用程序/rfc+xml媒体类型40区域元素5，50内部正面16艺术品元素6，50对齐属性7高度属性7内部图14名称属性7 src属性7类型属性8宽度属性8 xml:空间属性8作者元素8，50全名属性9首字母缩写属性9内前16角色属性9姓氏属性10
B back element 10, 50 inside rfc 25 blankLines attribute in vspace element 35 C c element 10, 50 inside texttable 32 category attribute in rfc element 25 city element 11, 50 inside postal 22 code element 11, 50 inside postal 22 consensus attribute in rfc element 25 counter attribute in list element 18 country element 11, 50 inside postal 22 cref element 11, 50 anchor attribute 11 inside annotation 5 inside c 10 inside postamble 22 inside preamble 23 inside t 31 source attribute 12 D date element 12, 50 day attribute 12 inside front 16 month attribute 12 year attribute 13 day attribute in date element 12 docName attribute in rfc element 25 E Elements abstract 4, 16 address 4, 9 annotation 5, 23 area 5, 16 artwork 6, 14 author 8, 16 back 10, 25 c 10, 32
B back元素10，50 in rfc 25 blankLines属性在vspace元素35 C C元素10，50 in texttable 32类别属性在rfc元素25 city元素11，50 in posal 22 code元素11，50 in posal 22共识属性在rfc元素25 counter属性在list元素18 country元素11，50内部邮政22 cref元素11，50锚属性11内部注释5内部c 10内部邮政编码22内部序言23内部t 31源属性12 D日期元素12，50天属性12内部前16个月属性12年属性13天属性日期元素12 docName属性rfc元素25 E元素摘要4，16地址4，9注释5，23区域5，16艺术品6，14作者8，16背面10，25 c 10，32
city 11, 22 code 11, 22 country 11, 22 cref 5, 10-11, 22-23, 31 date 12, 16 email 5, 13 eref 5, 10, 13, 22-23, 31 facsimile 5, 14 figure 14, 28, 31 format 15, 23 front 16, 23, 25 iref 5, 10, 14, 17, 22-23, 28, 31 keyword 16, 18 list 18, 31 middle 20, 25 note 17, 20 organization 9, 21 phone 5, 21 postal 5, 21 postamble 14, 22, 32 preamble 14, 22, 32 reference 23-24 references 10, 24 region 22, 24 rfc 24 section 10, 20, 28 seriesInfo 23, 29 spanx 5, 10, 22-23, 29, 31 street 21, 30 t 4, 18, 20, 28, 31 texttable 28, 31 title 16, 33 ttcol 32, 34 uri 5, 34 vspace 31, 34 workgroup 16, 35 xref 5, 10, 22, 31, 35 email element 13, 50 inside address 5 eref element 13, 50 inside annotation 5 inside c 10 inside postamble 22 inside preamble 23 inside t 31 target attribute 13
城市11，22代码11，22国家11，22 cref 5，10-11，22-23，31日期12，16电子邮件5，13电子邮箱5，10，13，22-23，31传真5，14图14，28，31格式15，23前16，23，25 iref 5，10，14，17，22-23，28，31关键字16，18列表18，31中间20，25注释17，20组织9，21电话5，21邮政5，21邮戳14，22，32序言14，22，32参考23-24参考10，24区域22，24 rfc 24第10，20，28节系列信息23，29 spanx 5，10，22-23，29，31 street 21，30 t 4，18，20，28，31文本表28，31标题16，33 ttcol 32，34 uri 5，34 vspace 31，34工作组16，35外部参照5，10，22，31，35电子邮件元素13，50内部地址5 eref元素13，50内部注释5内部c 10内部邮政编码22内部前导码23内部t 31目标属性13
F facsimile element 14, 50 inside address 5 figure element 14, 50 align attribute 14 alt attribute 15 anchor attribute 15 height attribute 15 inside section 28 inside t 31 src attribute 15 suppress-title attribute 15 title attribute 15 width attribute 15 format attribute in xref element 36 format element 15, 50 inside reference 23 octets attribute 16 target attribute 16 type attribute 16 front element 16, 50 inside reference 23 inside rfc 25 fullname attribute in author element 9 H hangIndent attribute in list element 18 hangText attribute in t element 31 height attribute in artwork element 7 in figure element 15 I initials attribute in author element 9 ipr attribute "*2026" 48 "*3667" 48 "*3978" 47 "*trust200811" 47 "*trust200902" 46 "noDerivativesTrust200902" 47 "noModificationTrust200902" 46 "pre5378Trust200902" 47 "trust200902" 46 in rfc element 26
F传真元素14，50内部地址5图形元素14，50对齐属性14 alt属性15锚定属性15高度属性15内部节28内部t 31 src属性15抑制标题属性15标题属性15宽度属性15格式属性外部参照元素36格式元素15，50内部参考23八位字节属性16目标属性16类型属性16前元素16，50内部参考23内部rfc 25作者元素中的全名属性9 H列表元素中的hangIndent属性18 t元素中的hangText属性31图形元素中的高度属性7元素15 I作者元素中的首字母缩写属性9 ipr属性“*2026”48“*3667”48“*3978”47”*trust200811”47“*trust200902”46rfc要素26中的“Noderivativevestrust200902”47“noModificationTrust200902”46“pre5378Trust200902”47“trust200902”46
iprExtract attribute in rfc element 26 iref element 17, 50 inside annotation 5 inside c 10 inside figure 14 inside postamble 22 inside preamble 23 inside section 28 inside t 31 item attribute 17 primary attribute 17 subitem attribute 17 item attribute in iref element 17 K keyword element 18, 50 inside front 16 L list element 18, 50 counter attribute 18 hangIndent attribute 18 inside t 31 style attribute 19 list styles empty 19 format ... 20 hanging 19 letters 19 numbers 19 symbols 19 M Media Type application/rfc+xml 40 middle element 20, 50 inside rfc 25 month attribute in date element 12 N name attribute in artwork element 7 in seriesInfo element 29 note element 20, 50 inside front 17 title attribute 21 number attribute in rfc element 27
rfc元素26中的iprExtract属性iref元素17，50内部注释5内部c 10内部图14内部邮资22内部序言23内部部分28内部t 31项目属性17主要属性17子项目属性17 iref元素中的项目属性17 K关键字元素18，50内部前16 L列表元素18，50计数器属性18悬挂缩进属性18内t 31样式属性19列表样式空19格式。。。20悬挂19个字母19个数字19个符号19 M媒体类型应用程序/rfc+xml 40中间元素20，50内rfc 25个月属性在日期元素12N名称属性在艺术品元素7在系列信息元素29注释元素20，50内前17标题属性21数字属性在rfc元素27
O obsoletes attribute in rfc element 27 octets attribute in format element 16 organization element 21, 50 abbrev attribute 21 inside author 9 P pageno attribute in xref element 37 phone element 21, 50 inside address 5 postal element 21, 50 inside address 5 postamble element 22, 50 inside figure 14 inside texttable 32 preamble element 22, 50 inside figure 14 inside texttable 32 primary attribute in iref element 17 R reference element 23, 50 anchor attribute 23 inside references 24 target attribute 23 references element 24, 50 inside back 10 title attribute 24 region element 24, 50 inside postal 22 rfc element 24, 50 category attribute 25 consensus attribute 25 docName attribute 25 ipr attribute 26 iprExtract attribute 26 number attribute 27 obsoletes attribute 27 seriesNo attribute 27 submissionType attribute 27 updates attribute 27 xml:lang attribute 28 role attribute in author element 9
O rfc元素27中的废弃属性格式元素16中的八位字节属性组织元素21中的50 abbrev属性21中的作者9 P pageno属性外部参照元素37中的电话元素21中的50内部地址5邮政元素21中的50内部地址5邮政编码元素22中的50内部地址5邮政编码元素22中的50内部图14中的texttable 32序言元素22，50内部图14内部文本表32 iref元素中的主属性17参考元素23，50锚属性23内部参考24目标属性23参考元素24，50内部背面10标题属性24区域元素24，50内部邮政22 rfc元素24，50类别属性25共识属性25文档名属性25 ipr属性26 iprExtract属性26编号属性27废弃属性27系列否属性27 submissionType属性27更新属性27 xml:lang属性28角色属性在作者元素9中
S section element 28, 50 anchor attribute 28 inside back 10 inside middle 20 inside section 28 title attribute 28 toc attribute 28 seriesInfo element 29, 50 inside reference 23 name attribute 29 value attribute 29 seriesNo attribute in rfc element 27 source attribute in cref element 12 spanx element 29, 50 inside annotation 5 inside c 10 inside postamble 22 inside preamble 23 inside t 31 style attribute 30 xml:space attribute 30 src attribute in artwork element 7 in figure element 15 street element 30, 50 inside postal 21 style attribute in list element 19 in spanx element 30 in texttable element 32 subitem attribute in iref element 17 submissionType attribute in rfc element 27 suppress-title attribute in figure element 15 in texttable element 33 surname attribute in author element 10
S节元素28，50锚属性28后内10中20内节28标题属性28 toc属性28序列信息元素29，50内参考23名称属性29值属性29序列rfc元素中无属性27 cref元素中源属性12 spanx元素29，50内部注释5内部c 10内部邮资22内部邮资23内部t 31样式属性30 xml:space属性30艺术作品中的src属性图元素15中的元素7街道元素30，50 inside postal 21 style属性在列表元素19在spanx元素30在texttable元素32子项属性在iref元素17 submissionType属性在rfc元素27抑制标题属性在图元素15在texttable元素33在author元素10中姓氏属性
T t element 31, 50 anchor attribute 31 hangText attribute 31 inside abstract 4 inside list 18 inside note 20 inside section 28 target attribute in eref element 13 in format element 16 in reference element 23 in xref element 37 texttable element 31, 50 align attribute 32 anchor attribute 32 inside section 28 style attribute 32 suppress-title attribute 33 title attribute 33 title attribute in figure element 15 in note element 21 in references element 24 in section element 28 in texttable element 33 title element 33, 50 abbrev attribute 34 inside front 16 toc attribute in section element 28 ttcol element 34, 50 align attribute 34 inside texttable 32 width attribute 34 type attribute in artwork element 8 in format element 16 U updates attribute in rfc element 27 uri element 34, 50 inside address 5
T T元素31，50锚定属性31 hangText属性31内部摘要4内部列表18内部注释20内部第28节eref元素13中的目标属性格式元素16外部参照元素37中的参考元素23中的文本表元素31，50对齐属性32第28节内的锚定属性32样式属性32抑制标题属性33标题属性33图中的标题属性注释中的元素15中的元素21中的引用中的元素24第28节中的元素33中的元素33标题元素33，50 abbrev属性34在前面16个toc属性在section元素28 ttcol元素34中，50 align属性34在texttable中宽度属性34在artwork元素8中类型属性在format元素16中U更新rfc元素27 uri元素34中的属性，50在address 5中
V value attribute in seriesInfo element 29 vspace element 34, 50 blankLines attribute 35 inside t 31 W width attribute in artwork element 8 in figure element 15 in ttcol element 34 workgroup element 35, 50 inside front 16 X xml:lang attribute in rfc element 28 xml:space attribute in artwork element 8 in spanx element 30 xref element 35, 50 format attribute 36 inside annotation 5 inside c 10 inside postamble 22 inside preamble 22 inside t 31 pageno attribute 37 target attribute 37 xref formats counter 36 default 36 none 36 title 36 Y year attribute in date element 13
seriesInfo元素29 vspace元素34中的V值属性，ttcol元素34工作组元素35中的图形元素15中的图形元素8中的t 31 W宽度属性中的50空行属性，rfc元素28中的50内前16 X xml:lang属性xml:spanx元素30外部参照元素35中的图形元素8中的空间属性，50格式属性36内注释5内c 10内邮资22内前导22内t 31页否属性37目标属性37外部参照格式计数器36默认值36无36标题36日期元素13中的Y年属性
Author's Address
作者地址
Julian F. Reschke greenbytes GmbH Hafenweg 16 Muenster, NW 48155 Germany
Julian F.Reschke greenbytes GmbH Hafenweg 16 Muenster，西北48155德国
Email: julian.reschke@greenbytes.de
URI: http://greenbytes.de/tech/webdav/
Email: julian.reschke@greenbytes.de
URI: http://greenbytes.de/tech/webdav/