Internet Architecture Board (IAB) J. Halpern, Ed.
Request for Comments: 7841 L. Daigle, Ed.
Obsoletes: 5741 O. Kolkman, Ed.
Category: Informational May 2016
ISSN: 2070-1721
Internet Architecture Board (IAB) J. Halpern, Ed.
Request for Comments: 7841 L. Daigle, Ed.
Obsoletes: 5741 O. Kolkman, Ed.
Category: Informational May 2016
ISSN: 2070-1721
RFC Streams, Headers, and Boilerplates
RFC流、标题和样板
Abstract
摘要
RFC documents contain a number of fixed elements such as the title page header, standard boilerplates, and copyright/IPR statements. This document describes them and introduces some updates to reflect current usage and requirements of RFC publication. In particular, this updated structure is intended to communicate clearly the source of RFC creation and review. This document obsoletes RFC 5741, moving detailed content to an IAB web page and preparing for more flexible output formats.
RFC文档包含许多固定元素，如标题页标题、标准样板和版权/知识产权声明。本文档描述了它们，并介绍了一些更新，以反映RFC出版物的当前使用情况和要求。特别是，此更新结构旨在明确传达RFC创建和审查的来源。本文档淘汰了RFC 5741，将详细内容移动到IAB网页，并准备采用更灵活的输出格式。
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/rfc7841.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7841.
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. RFC Streams and Internet Standards . . . . . . . . . . . . . 3
3. RFC Structural Elements . . . . . . . . . . . . . . . . . . . 3
3.1. The Title Page Header . . . . . . . . . . . . . . . . . . 4
3.2. The Status of This Memo . . . . . . . . . . . . . . . . . 5
3.3. Paragraph 1 . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. Paragraph 2 . . . . . . . . . . . . . . . . . . . . . . . 5
3.5. Paragraph 3 . . . . . . . . . . . . . . . . . . . . . . . 6
3.6. Noteworthy . . . . . . . . . . . . . . . . . . . . . . . 6
4. Additional Notes . . . . . . . . . . . . . . . . . . . . . . 6
5. Other Structural Information in RFCs . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. RFC Editor Considerations . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Initial Formatting Details . . . . . . . . . . . . . 10
A.1. RFC Title Page Header . . . . . . . . . . . . . . . . . . 10
A.2. Constructing a "Status of This Memo" Section . . . . . . 10
A.2.1. First Paragraph . . . . . . . . . . . . . . . . . . . 11
A.2.2. Second Paragraph . . . . . . . . . . . . . . . . . . 11
A.2.3. Third Paragraph . . . . . . . . . . . . . . . . . . . 13
IAB Members at Time of Approval . . . . . . . . . . . . . . . . . 13
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. RFC Streams and Internet Standards . . . . . . . . . . . . . 3
3. RFC Structural Elements . . . . . . . . . . . . . . . . . . . 3
3.1. The Title Page Header . . . . . . . . . . . . . . . . . . 4
3.2. The Status of This Memo . . . . . . . . . . . . . . . . . 5
3.3. Paragraph 1 . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. Paragraph 2 . . . . . . . . . . . . . . . . . . . . . . . 5
3.5. Paragraph 3 . . . . . . . . . . . . . . . . . . . . . . . 6
3.6. Noteworthy . . . . . . . . . . . . . . . . . . . . . . . 6
4. Additional Notes . . . . . . . . . . . . . . . . . . . . . . 6
5. Other Structural Information in RFCs . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. RFC Editor Considerations . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Initial Formatting Details . . . . . . . . . . . . . 10
A.1. RFC Title Page Header . . . . . . . . . . . . . . . . . . 10
A.2. Constructing a "Status of This Memo" Section . . . . . . 10
A.2.1. First Paragraph . . . . . . . . . . . . . . . . . . . 11
A.2.2. Second Paragraph . . . . . . . . . . . . . . . . . . 11
A.2.3. Third Paragraph . . . . . . . . . . . . . . . . . . . 13
IAB Members at Time of Approval . . . . . . . . . . . . . . . . . 13
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
Previously, RFCs (e.g., [RFC4844]) contained a number of elements that were there for historical, practical, and legal reasons. They also contained boilerplate material to clearly indicate the status of the document and possibly contained "Notes" to indicate how the document interacts with IETF Standards-Track documents.
在此之前，RFC（例如，[RFC4844]）包含许多出于历史、实践和法律原因而存在的元素。它们还包含样板材料，以清楚地指示文档的状态，可能还包含“注释”，以指示文档如何与IETF标准跟踪文档交互。
As the RFC Series has evolved over the years, there has been increasing concern over appropriate labeling of the publications to make clear the status of each RFC and the status of the work it describes. Chiefly, there is a requirement that RFCs published as part of the IETF's review process not be easily confused with RFCs that may have had a very different review and approval process. Various adjustments have been made over the years, including evolving text of "Notes" included in the published RFC.
随着RFC系列多年来的发展，人们越来越关注出版物的适当标签，以明确每个RFC的状态及其描述的工作状态。主要的要求是，作为IETF审查过程的一部分发布的RFC不容易与可能具有非常不同的审查和批准过程的RFC混淆。多年来进行了各种调整，包括在已发布的RFC中不断演变的“注释”文本。
With the definition of the different RFC streams [RFC4844], it is appropriate to formalize the definition of the various pieces of standard RFC boilerplate and introduce some adjustments to ensure
根据不同RFC流[RFC4844]的定义，可以将各种标准RFC样板的定义形式化，并引入一些调整以确保
better clarity of expression of document status, aligned with the review and approval processes defined for each stream.
文档状态的表达更加清晰，与为每个流定义的审核和批准流程保持一致。
This memo identifies and describes the common elements of RFC boilerplate structure. It describes the content required for each kind of information. Details of the exact textual and layout requirements are left to a web page maintained by the IAB, with due consultation with the community, for ease of maintenance. This document obsoletes [RFC5741].
本备忘录确定并描述了RFC样板结构的常见元素。它描述了每种信息所需的内容。为便于维护，IAB在与社区进行适当协商后，将详细的文字和布局要求留给其维护的网页。本文件废除了[RFC5741]。
The changes introduced by this memo should be implemented as soon as practically possible after the document has been approved for publication.
本备忘录引入的变更应在批准发布文件后尽快实施。
Users of RFCs should be aware that while all Internet Standards-related documents are published as RFCs, not all RFCs are Internet Standards-related documents.
RFC的用户应意识到，虽然所有与互联网标准相关的文件都作为RFC发布，但并非所有RFC都是与互联网标准相关的文件。
The IETF is responsible for maintaining the Internet Standards Process, which includes the requirements for developing, reviewing, and approving Standards Track and BCP RFCs. The IETF also produces non-Standards-Track documents (Informational, Experimental, and Historic). All documents published as part of the IETF Stream are reviewed by the appropriate IETF bodies.
IETF负责维护互联网标准流程，包括制定、审查和批准标准跟踪和BCP RFC的要求。IETF还生成非标准跟踪文档（信息性、实验性和历史性）。作为IETF流一部分发布的所有文件均由适当的IETF机构审查。
Documents published in streams other than the IETF stream are not generally reviewed by the IETF for such things as security, congestion control, or inappropriate interaction with deployed protocols. They have also not been subject to approval by the Internet Engineering Steering Group (IESG), including an IETF-wide last call. Therefore, the IETF disclaims, for any of the non-IETF stream documents, any knowledge of the fitness of those RFCs for any purpose.
IETF通常不会审查IETF流以外的流中发布的文档的安全性、拥塞控制或与已部署协议的不当交互。它们也没有得到互联网工程指导小组（IESG）的批准，包括IETF范围内的最后一次呼叫。因此，对于任何非IETF流文件，IETF不承认这些RFC适用于任何目的的任何知识。
Refer to [RFC2026], [RFC5742], [RFC4844], [RFC6410], and [RFC7127] and their successors for current details of the IETF process and RFC streams.
请参阅[RFC2026]、[RFC5742]、[RFC4844]、[RFC6410]和[RFC7127]及其后续文件，了解IETF流程和RFC流的当前详细信息。
This section describes the elements that are commonly found in RFCs published today. This document specifies information that is required in these publications. Exact specification of the textual values required therein are provided by an IAB web page (https://www.iab.org/documents/headers-boilerplate).
本节介绍了今天发布的RFC中常见的元素。本文件规定了这些出版物所需的信息。IAB网页提供了其中所需文本值的准确说明(https://www.iab.org/documents/headers-boilerplate).
As noted above, this web page is maintained by the IAB with due consultation with the community. Following such consultation, if the IAB decides to make any changes to this material, the changes will be announced in a similar fashion to other IAB statements. The initial text to be used in that web page is included in Appendix A.
如上所述，本网页由IAB在与社区进行适当协商后维护。在此类咨询之后，如果IAB决定对本材料进行任何更改，则将以与其他IAB声明类似的方式公布这些更改。该网页中使用的初始文本包含在附录A中。
The information at the front of the RFC includes the name and affiliation of the authors as well as the RFC publication month and year.
RFC前面的信息包括作者的姓名和联系，以及RFC出版的月份和年份。
There is a set of additional information that is needed at the front of the RFC. Historically, this has been presented with the information below in a left hand column, and the author-related information described above in the right.
RFC前端需要一组附加信息。从历史上看，这一点在左侧栏中有下面的信息，在右侧栏中有上面描述的与作者相关的信息。
<document source> This describes the area where the work originates. Historically, all RFCs were labeled "Network Working Group". Network Working Group refers to the original version of today's IETF when people from the original set of ARPANET sites and whomever else was interested -- the meetings were open -- got together to discuss, design, and document proposed protocols [RFC3]. Here, we obsolete the term "Network Working Group" in order to indicate the originating stream.
<document source>这描述了工作的起始区域。历史上，所有RFC都被标记为“网络工作组”。网络工作组指的是今天IETF的原始版本，当时来自原始ARPANET站点的人们以及其他感兴趣的人——会议是开放的——聚集在一起讨论、设计和记录提议的协议[RFC3]。在这里，我们废弃了术语“网络工作组”，以指示原始流。
The <document source> is the name of the RFC stream, as defined in [RFC4844] and its successors. At the time of this publication, the streams, and therefore the possible entries are:
<document source>是[RFC4844]及其后续文件中定义的RFC流的名称。在本出版物发布时，流以及可能的条目为：
* Internet Engineering Task Force * Internet Architecture Board * Internet Research Task Force * Independent Submission
* 互联网工程任务组*互联网架构委员会*互联网研究任务组*独立提交
Request for Comments: <RFC number> This indicates the RFC number, assigned by the RFC Editor upon publication of the document. This element is unchanged.
征求意见：<RFC编号>这表示RFC编辑器在发布文档时分配的RFC编号。这个元素没有改变。
<subseries ID> <subseries number> Some document categories are also labeled as a subseries of RFCs. These elements appear as appropriate for such categories, indicating the subseries and the documents number within that series. Currently, there are subseries for BCPs [RFC2026] and STDs [RFC1311]. These subseries numbers may appear in several RFCs. For example, when a new RFC obsoletes or updates an old one, the same subseries number is used. Also, several RFCs may be assigned the same subseries number: a single STD, for example, may be composed of several
<subseries ID><subseries number>某些文档类别也被标记为RFC的子系列。这些元素适用于此类类别，表示该系列中的子系列和文档编号。目前，有BCP[RFC2026]和STD[RFC1311]的子系列。这些子系列编号可能出现在多个RFC中。例如，当新RFC淘汰或更新旧RFC时，使用相同的子系列编号。此外，多个RFC可被分配相同的子序列号：例如，单个STD可由多个RFC组成
RFCs, each of which will bear the same STD number. This element is unchanged.
RFC，每个RFC将具有相同的STD编号。这个元素没有改变。
[<RFC relation>:<RFC number[s]>] Some relations between RFCs in the series are explicitly noted in the RFC header. For example, a new RFC may update one or more earlier RFCs. Currently two relationships are defined: "Updates" and "Obsoletes" [RFC7322]. Variants like "Obsoleted by" are also used (e.g, in [RFC5143]). Other types of relationships may be defined by the RFC Editor and may appear in future RFCs.
[<RFC relationship>：<RFC number[s]>]序列中RFC之间的一些关系在RFC标题中明确指出。例如，新的RFC可以更新一个或多个早期RFC。目前定义了两种关系：“更新”和“淘汰”[RFC7322]。还使用了类似“已淘汰”的变体（例如，在[RFC5143]中）。其他类型的关系可能由RFC编辑器定义，并可能出现在未来的RFC中。
Category: <category> This indicates the initial RFC document category of the publication. These are defined in [RFC2026]. Currently, this is always one of: Standards Track, Best Current Practice, Experimental, Informational, or Historic. This element is unchanged.
类别：<Category>表示出版物的初始RFC文档类别。这些在[RFC2026]中定义。目前，这始终是其中之一：标准跟踪、最佳当前实践、实验性、信息性或历史性。这个元素没有改变。
The "Status of This Memo" describes the category of the RFC, including the distribution statement.
“本备忘录的状态”描述了RFC的类别，包括分配声明。
The "Status of This Memo" will start with a single sentence describing the status. It will also include a statement describing the stream-specific review of the material (which is stream dependent). This is an important component of status, insofar as it clarifies the breadth and depth of review, and gives the reader an understanding of how to consider its content.
“本备忘录的状态”将以描述状态的一句话开头。它还将包括一个描述材料流特定审查的声明（与流相关）。这是状态的一个重要组成部分，它阐明了审查的广度和深度，并给读者一个如何考虑其内容的理解。
The first paragraph of the "Status of This Memo" section contains a single sentence, clearly standing out. The sentence will clearly identify the stream-specific status of the document. The text to be used is defined by the stream, with a review for clarity by the IAB and RFC Series Editor.
“本备忘录的状态”一节的第一段包含一句话，明显突出。这句话将清楚地标识文档的流特定状态。要使用的文本由流定义，并由IAB和RFC系列编辑器审查以确保清晰。
The second paragraph of the "Status of This Memo" will include a paragraph describing the type of review and exposure the document has received. This is defined on a per-stream basis, subject to general review and oversight by the RFC Editor and IAB. The IAB defines a specific structure defined to ensure there is clarity about review processes and document types.
“本备忘录的状态”的第二段将包括一段描述文件收到的审查类型和风险敞口。这是在每个流的基础上定义的，受RFC编辑和IAB的一般审查和监督。IAB定义了一个特定的结构，以确保审查流程和文件类型清晰。
The boilerplate ends with a reference to where further relevant information can be found. This information may include, subject to the RFC Editor's discretion, information about whether the RFC has been updated or obsoleted, the RFC's origin, a listing of possible errata, information about how to provide feedback and suggestion, and information on how to submit errata as described in [ERRATA]. The exact wording and URL is subject to change (at the RFC Editor's discretion), but the current text is:
样板文件结尾提到了可以找到更多相关信息的地方。根据RFC编辑的判断，该信息可能包括关于RFC是否已更新或废弃的信息、RFC的来源、可能的勘误表列表、关于如何提供反馈和建议的信息以及关于如何提交勘误表的信息，如[勘误表]所述。确切的措辞和URL可能会发生变化（由RFC编辑自行决定），但当前文本为：
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/<static-path>/rfc<rfc-no>.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/<static path>/rfc<rfc no>。
Note that the text in paragraph 1 and 2 of the boilerplate indicate the initial status of a document. During their lifetime, documents can change status to, for example, Historic. This cannot be reflected in the document itself and will need be reflected in the information referred to in Section 5.
请注意，样板第1段和第2段中的文本表示文档的初始状态。在文档的生命周期内，文档的状态可以更改为（例如）历史。这不能反映在文件本身中，需要反映在第5节提到的信息中。
Exceptionally, a review and publication process may prescribe additional notes that will appear as labeled notes after the "Abstract".
例外情况下，审查和出版过程可能会规定附加注释，这些注释将在“摘要”后显示为标签注释。
This is no longer a common feature of recent RFCs. It is the goal of this document to continue to ensure that the overall RFC structure is adequately clear so that such notes are unnecessary or (at least) truly exceptional.
这已不再是最近的RFC的共同特征。本文件的目标是继续确保整个RFC结构足够清晰，以便此类注释不必要或（至少）真正例外。
RFCs contain other structural informational elements. The RFC Editor is responsible for the positioning and layout of these structural elements. Note also that new elements may be introduced or obsoleted using a process consistent with [RFC4844]. These additions may or may not require documentation in an RFC.
RFC包含其他结构信息元素。RFC编辑器负责这些结构元素的定位和布局。还应注意，新元素可采用与[RFC4844]一致的流程引入或淘汰。这些添加可能需要也可能不需要RFC中的文档。
Currently, the following structural information is available in RFCs:
目前，RFCs中提供了以下结构信息：
Copyright Notice: A copyright notice with a reference to BCP 78 [BCP78] and an Intellectual Property statement referring to BCP 78 and BCP 79 [BCP79]. The content of these statements are defined by those BCPs.
版权声明：参考BCP 78[BCP78]的版权声明和参考BCP 78和BCP 79[BCP79]的知识产权声明。这些语句的内容由这些BCP定义。
ISSN: The International Standard Serial Number [ISO.3297.2007]: ISSN 2070-1721. The ISSN uniquely identifies the RFC series as title regardless of language or country in which it is published. The ISSN itself has no significance other than the unique identification of a serial publication.
ISSN：国际标准序列号[ISO.3297.2007]：ISSN 2070-1721。ISSN将RFC系列唯一标识为标题，而不考虑其出版的语言或国家。ISSN本身除了对系列出版物进行唯一标识外，没有其他意义。
This document tries to clarify the descriptions of the status of an RFC. Misunderstanding the status of a memo could cause interoperability problems, hence security and stability problems.
本文件试图澄清RFC状态的描述。误解备忘录的状态可能会导致互操作性问题，从而导致安全性和稳定性问题。
The RFC Editor is responsible for maintaining the consistency of the RFC series. To that end, the RFC Editor maintains an "RFC Style Guide" [RFC7322]. In this memo, we mention a few explicit structural elements that the RFC Editor needs to maintain. The conventions for the content and use of all current and future elements are documented in the style guide.
RFC编辑器负责维护RFC系列的一致性。为此，RFC编辑器维护一个“RFC样式指南”[RFC7322]。在本备忘录中，我们提到了RFC编辑器需要维护的几个明确的结构元素。样式指南中记录了所有当前和未来元素的内容和使用约定。
Adding a reference to the stream in the header of RFCs is only one method for clarifying from which stream an RFC originated. The RFC Editor is encouraged to add such indication in, for example, indices and interfaces.
在RFC头中添加对流的引用只是澄清RFC来自哪个流的一种方法。建议RFC编辑器在索引和接口中添加此类指示。
[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>.
[RFC5742] Alvestrand, H. and R. Housley, "IESG Procedures for Handling of Independent and IRTF Stream Submissions", BCP 92, RFC 5742, DOI 10.17487/RFC5742, December 2009, <http://www.rfc-editor.org/info/rfc5742>.
[RFC5742]Alvestrand，H.和R.Housley，“IESG处理独立和IRTF流提交的程序”，BCP 92，RFC 5742，DOI 10.17487/RFC5742，2009年12月<http://www.rfc-editor.org/info/rfc5742>.
[ISO.3297.2007] Technical Committee ISO/TC 46, Information and documentation, Subcommittee SC 9, Identification and description., "Information and documentation - International standard serial number (ISSN)", ISO Standard 3297, 09 2007.
[ISO.3297.2007]技术委员会ISO/TC 46，信息和文件，小组委员会SC 9，标识和说明，“信息和文件-国际标准序列号（ISSN）”，ISO标准32972007年9月。
[RFC3] Crocker, S., "Documentation conventions", RFC 3, DOI 10.17487/RFC0003, April 1969, <http://www.rfc-editor.org/info/rfc3>.
[RFC3]Crocker，S.，“文件惯例”，RFC 3，DOI 10.17487/RFC0003，1969年4月<http://www.rfc-editor.org/info/rfc3>.
[RFC1311] Postel, J., "Introduction to the STD Notes", RFC 1311, DOI 10.17487/RFC1311, March 1992, <http://www.rfc-editor.org/info/rfc1311>.
[RFC1311]Postel，J.，“标准注释介绍”，RFC 1311，DOI 10.17487/RFC1311，1992年3月<http://www.rfc-editor.org/info/rfc1311>.
[RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, July 2007, <http://www.rfc-editor.org/info/rfc4844>.
[RFC4844]Daigle，L.，Ed.和互联网架构委员会，“RFC系列和RFC编辑器”，RFC 4844，DOI 10.17487/RFC4844，2007年7月<http://www.rfc-editor.org/info/rfc4844>.
[RFC5143] Malis, A., Brayley, J., Shirron, J., Martini, L., and S. Vogelsang, "Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation Service over MPLS (CEM) Encapsulation", RFC 5143, DOI 10.17487/RFC5143, February 2008, <http://www.rfc-editor.org/info/rfc5143>.
[RFC5143]Malis，A.，Brayley，J.，Shirron，J.，Martini，L.，和S.Vogelsang，“基于MPLS（CEM）封装的同步光网络/同步数字体系（SONET/SDH）电路仿真服务”，RFC 5143，DOI 10.17487/RFC5143，2008年2月<http://www.rfc-editor.org/info/rfc5143>.
[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>.
[RFC6410] Housley, R., Crocker, D., and E. Burger, "Reducing the Standards Track to Two Maturity Levels", BCP 9, RFC 6410, DOI 10.17487/RFC6410, October 2011, <http://www.rfc-editor.org/info/rfc6410>.
[RFC6410]Housley，R.，Crocker，D.，和E.Burger，“将标准轨道降低到两个成熟度水平”，BCP 9，RFC 6410，DOI 10.17487/RFC6410，2011年10月<http://www.rfc-editor.org/info/rfc6410>.
[RFC7127] Kolkman, O., Bradner, S., and S. Turner, "Characterization of Proposed Standards", BCP 9, RFC 7127, DOI 10.17487/RFC7127, January 2014, <http://www.rfc-editor.org/info/rfc7127>.
[RFC7127]Kolkman，O.，Bradner，S.和S.Turner，“拟定标准的特征”，BCP 9，RFC 7127，DOI 10.17487/RFC7127，2014年1月<http://www.rfc-editor.org/info/rfc7127>.
[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>.
[ERRATA] Hagens, A., Ginoza, S., and R. Braden, "RFC Editor Proposal for Handling RFC Errata", Work in Progress, draft-rfc-editor-errata-process-02, May 2008.
[勘误表]Hagens，A.，Ginoza，S.，和R.Braden，“处理RFC勘误表的RFC编辑建议书”，正在进行的工作，草稿-RFC-Editor-ERRATA-process-02，2008年5月。
[BCP78] Bradner, S., Ed. and J. Contreras, Ed., "Rights Contributors Provide to the IETF Trust", BCP 78, RFC 5378, November 2008, <http://www.rfc-editor.org/info/bcp78>.
[BCP78]Bradner，S.，Ed.和J.Contreras，Ed.，“向IETF信托提供的权利出资人”，BCP 78，RFC 5378，2008年11月<http://www.rfc-editor.org/info/bcp78>.
[BCP79] Bradner, S., Ed., "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3979, DOI 10.17487/RFC3979, March 2005.
[BCP79]Bradner，S.，Ed.，“IETF技术中的知识产权”，BCP 79，RFC 3979，DOI 10.17487/RFC3979，2005年3月。
Narten, T., "Clarification of the Third Party Disclosure Procedure in RFC 3979", BCP 79, RFC 4879, DOI 10.17487/RFC4879, April 2007.
Narten，T.，“RFC 3979中第三方披露程序的澄清”，BCP 79，RFC 4879，DOI 10.17487/RFC4879，2007年4月。
<http://www.rfc-editor.org/info/bcp79>
<http://www.rfc-editor.org/info/bcp79>
This section contains the text the IAB used to initially populate the web page used to maintain the list of required verbiage.
本节包含IAB最初用于填充用于维护所需措辞列表的网页的文本。
An RFC title page header can be described as follows:
RFC标题页标题可描述如下：
------------------------------------------------------------------------
<document source> <author name>
Request for Comments: <RFC number> [<author affiliation>]
[<subseries ID> <subseries number>] [more author info as appropriate]
[<RFC relation>:<RFC number[s]>]
Category: <category>
<month year>
------------------------------------------------------------------------
<document source> <author name>
Request for Comments: <RFC number> [<author affiliation>]
[<subseries ID> <subseries number>] [more author info as appropriate]
[<RFC relation>:<RFC number[s]>]
Category: <category>
<month year>
------------------------------------------------------------------------
------------------------------------------------------------------------
For example, the header for RFC 6410 appears as follows:
例如，RFC 6410的标题显示如下：
------------------------------------------------------------------------
------------------------------------------------------------------------
Internet Engineering Task Force (IETF) R. Housley Request for Comments: 6410 Vigil Security BCP: 9 D. Crocker Updates: 2026 Brandenburg InternetWorking Category: Best Current Practice E. Burger ISSN: 2070-1721 Georgetown University October 2011
互联网工程任务组（IETF）R.Housley征求意见：6410守夜安全BCP:9 D.Crocker更新：2026年勃兰登堡互联网类别：最佳当前实践E.Burger ISSN:2070-1721乔治敦大学2011年10月
------------------------------------------------------------------------
------------------------------------------------------------------------
The following sections describe mandated text for use in specific parts of the "Status of This Memo" portion of an RFC. For convenience, the RFC Editor maintains example expansions of all permutations of the paragraphs described in this document (at the time of publication, at http://www.rfc-editor.org/materials/status-memos.txt). When in conflict, the following sections are authoritative.
以下章节描述了RFC“本备忘录状态”部分特定部分中使用的强制文本。为方便起见，RFC编辑器维护本文档中描述的段落的所有排列的示例扩展（在发布时，在http://www.rfc-editor.org/materials/status-memos.txt). 当发生冲突时，以下章节具有权威性。
The following are the approved texts for use in the first paragraph of the "Status of This Memo" portion of an RFC. See Section 3.3 of RFC 7841.
以下是RFC“本备忘录状态”部分第一段中使用的批准文本。见RFC 7841第3.3节。
For 'Standards Track' documents: "This is an Internet Standards Track document."
对于“标准跟踪”文档：“这是一个Internet标准跟踪文档。”
For 'Best Current Practices' documents: "This memo documents an Internet Best Current Practice."
对于“当前最佳实践”文档：“本备忘录记录了互联网当前最佳实践。”
For other categories "This document is not an Internet Standards Track specification; <it is published for other purposes>."
对于其他类别，“本文件不是互联网标准跟踪规范；<为其他目的发布>”
For Informational, Experimental, Historic, and future categories of RFCs, the RFC Editor will maintain an appropriate text for <it is published for other purposes>. Initial values are:
对于RFC的信息、实验、历史和未来类别，RFC编辑器将为<it is published For other purposes>维护适当的文本。初始值为：
Informational: "it is published for informational purposes."
信息性：“它是为了提供信息而发布的。”
Historic: "it is published for the historical record."
历史：“它是为了历史记录而出版的。”
Experimental: "it is published for examination, experimental implementation, and evaluation."
实验：“它是为检查、实验实施和评估而出版的。”
See Section 3.4 of RFC 7841.
见RFC 7841第3.4节。
The second paragraph may include some text that is specific to the initial document category. When a document is Experimental or Historic, the second paragraph opens with:
第二段可能包括一些特定于初始文件类别的文本。当文件是实验性的或历史性的时，第二段以以下内容开头：
Experimental: "This document defines an Experimental Protocol for the Internet community."
实验性：“本文档为互联网社区定义了一个实验性协议。”
Historic: "This document defines a Historic Document for the Internet community."
历史：“本文档定义了互联网社区的历史文档。”
The text that follows is stream dependent -- these are initial values and may be updated by stream definition document updates and recorded by the IAB on the web page.
下面的文本依赖于流——这些是初始值，可以通过流定义文档更新进行更新，并由IAB记录在网页上。
IETF Stream: "This document is a product of the Internet Engineering Task Force (IETF)."
IETF流：“本文件是互联网工程任务组（IETF）的产品。”
If there has been an IETF consensus call per IETF process, this additional text should be added: "It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG)." If there has not been such a consensus call, then this simply reads: "It has been approved for publication by the Internet Engineering Steering Group (IESG)."
如果按照IETF流程进行了IETF协商一致呼吁，则应添加此附加文本：“它代表了IETF社区的协商一致意见。它已接受公众审查，并已由互联网工程指导小组（IESG）批准发布。”如果没有这样的协商一致呼吁，则其内容如下：“它已被互联网工程指导小组（IESG）批准出版。”
IAB Stream: "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."
IAB Stream：“本文件是互联网体系结构委员会（IAB）的产品，代表IAB认为有价值提供的永久记录信息。”
If the document represents IAB consensus, this additional text should be added: "It represents the consensus of the Internet Architecture Board (IAB)."
如果该文件代表IAB的共识，则应添加此附加文本：“它代表互联网架构委员会（IAB）的共识。”
IRTF Stream: "This document is a product of the Internet Research Task Force (IRTF). The IRTF publishes the results of Internet-related research and development activities. These results might not be suitable for deployment."
IRTF Stream：“本文件是互联网研究工作组（IRTF）的产品。IRTF发布了与互联网相关的研究和开发活动的结果。这些结果可能不适合部署。”
In addition, a sentence indicating the consensus base within the IRTF may be added: "This RFC represents the consensus of the <insert_name> Research Group of the Internet Research Task Force (IRTF)." or alternatively "This RFC represents the individual opinion(s) of one or more members of the <insert_name> Research Group of the Internet Research Task Force (IRTF)".
此外，可以添加一句表明IRTF内共识基础的句子：“本RFC代表互联网研究工作队（IRTF）的<insert_name>研究小组的共识。”或者“本RFC代表个人意见”互联网研究工作队（IRTF）的<insert_name>研究小组的一名或多名成员。
Independent Submission Stream: "This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment."
独立提交流：“这是对RFC系列的贡献，独立于任何其他RFC流。RFC编辑器已选择自行发布此文档，并且未对其实现或部署价值做出任何声明。”
For non-IETF stream documents, a reference to Section 2 of this RFC is added with the following sentence: "Documents approved for publication by the [stream approver -- currently, one of: "IAB", "IRSG", or "RFC Editor"] are not a candidate for any level of Internet Standard; see Section 2 of RFC 7841."
对于非IETF流文件，参考本RFC第2节时添加以下句子：“由[流批准人批准发布的文件——目前，“IAB”、“IRSG”或“RFC编辑器”中的一个文件不适用于任何级别的互联网标准；请参阅RFC 7841第2节。”
For IETF stream documents, a similar reference is added: "Further information on (BCPs or Internet Standards) is available in Section 2 of RFC 7841." for BCP and Standard Track documents; "Not all documents approved by the IESG are a candidate for any level of Internet Standards; see Section 2 of RFC 7841." for all other categories.
对于IETF流文件，增加了类似的参考：“关于（BCP或互联网标准）的更多信息，请参见RFC 7841第2节。”对于BCP和标准跟踪文件；“并非IESG批准的所有文件都适用于任何级别的互联网标准；请参见RFC 7841第2节。”所有其他类别。
See Section 3.5 of RFC 7841.
见RFC 7841第3.5节。
IAB Members at Time of Approval
批准时的IAB成员
The IAB members at the time this memo was approved were (in alphabetical order):
本备忘录批准时，IAB成员为（按字母顺序排列）：
Jari Arkko Mary Barnes Marc Blanchet Ralph Droms Ted Hardie Joe Hildebrand Russ Housley Erik Nordmark Robert Sparks Andrew Sullivan Dave Thaler Brian Trammell Suzanne Woolf
贾里·阿克科·玛丽·巴恩斯·马克·布兰切特·拉尔夫·德罗姆斯·泰德·哈迪·乔·希尔德布兰德·罗斯·霍斯利·埃里克·诺德马克·罗伯特·斯帕克斯·安德鲁·沙利文·戴夫·泰勒·布莱恩·特拉梅尔·苏珊娜·伍尔夫
Acknowledgements
致谢
Thanks to Bob Braden, Brian Carpenter, Steve Crocker, Sandy Ginoza, and John Klensin who provided background information and inspiration.
感谢提供背景信息和灵感的鲍勃·布拉登、布赖恩·卡彭特、史蒂夫·克罗克、桑迪·吉诺萨和约翰·克伦辛。
Thanks to the members of the RFC Series Oversight Committee (RSOC) for assistance and review: Alexey Melnikov, Nevil Brownlee, Bob Hinden, Sarah Banks, Robert Sparks, Tony Hansen, and Joe Hildebrand.
感谢RFC系列监督委员会（RSOC）成员的协助和审查：阿列克谢·梅尔尼科夫、内维尔·布朗利、鲍勃·欣登、莎拉·班克斯、罗伯特·斯帕克斯、托尼·汉森和乔·希尔德布兰德。
Various people have made suggestions that improved the document. Among them are: Lars Eggert, Alfred Hoenes, and Joe Touch.
许多人提出了改进该文件的建议。其中包括：拉尔斯·艾格特、阿尔弗雷德·霍恩斯和乔·图奇。
Authors' Addresses
作者地址
Joel M. Halpern (editor)
乔尔·哈尔本（编辑）
Email: jmh@joelhalpern.com
Email: jmh@joelhalpern.com
Leslie Daigle (editor)
莱斯利·戴格尔（编辑）
Email: ldaigle@thinkingcat.com
Email: ldaigle@thinkingcat.com
Olaf M. Kolkman (editor)
奥拉夫·科尔克曼（编辑）
Email: kolkman@isoc.org
Email: kolkman@isoc.org