Network Working Group L. Daigle, Ed.
Request for Comments: 4845
Category: Informational Internet Architecture Board
(IAB)
July 2007
Network Working Group L. Daigle, Ed.
Request for Comments: 4845
Category: Informational Internet Architecture Board
(IAB)
July 2007
Process for Publication of IAB RFCs
IAB RFC的发布流程
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
From time to time, the Internet Architecture Board (IAB) publishes documents as Requests for Comments (RFCs). This document defines the process by which those documents are produced, reviewed, and published in the RFC Series.
互联网体系结构委员会（IAB）不时以征求意见（RFC）的形式发布文件。本文档定义了在RFC系列中生成、审查和发布这些文档的过程。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Review and Approval . . . . . . . . . . . . . . . . . . . . . . 2
3. IAB RFC Publication Process . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
5. IAB Members at the Time of Approval . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Review and Approval . . . . . . . . . . . . . . . . . . . . . . 2
3. IAB RFC Publication Process . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
5. IAB Members at the Time of Approval . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
From time to time, the IAB has cause to publish documents as Requests for Comments (RFCs). These occasions include the following:
IAB不时有理由将文件发布为征求意见书（RFC）。这些情况包括：
o documents that arise from consideration of an issue by the IAB and are authored by the IAB through a nominated editor.
o IAB考虑某一问题后产生的文件，由IAB通过指定编辑编写。
o documents that report on IAB activities, such as workshop reports, and are authored by a nominated editor, generally from among the activity participants.
o 报告IAB活动的文件，如研讨会报告，通常由活动参与者中指定的编辑撰写。
o documents that are not the outcome of an Internet Engineering Task Force (IETF) Working Group effort but that the IAB has determined would be of benefit to the IETF community to publish. Such documents need not necessarily be authored or revised by the IAB.
o 不是互联网工程任务组（IETF）工作组工作成果，但IAB已确定将有利于IETF社区发布的文件。此类文件无需由IAB编写或修订。
The majority of documents published by the IAB will be classified as Informational RFCs (see [RFC2026]). Generally speaking, the IAB does not publish Standards-Track or Experimental RFCs. If the IAB has cause to publish a document as a Best Current Practice (BCP), it would fall under the approval process of the IETF standards stream of RFCs (see [RFC4844]).
IAB发布的大多数文件将被归类为信息性RFC（见[RFC2026]）。一般来说，IAB不发布标准跟踪或实验RFC。如果IAB有理由将文件发布为最佳现行做法（BCP），则该文件将属于IETF RFC标准流的审批流程（见[RFC4844]）。
In many cases, the IAB publishes documents to provide a permanent record of an IAB statement or position. In such cases, the IAB uses its internal discussion processes to refine the expression and technical content of the document, and the document is approved for publication if, and only if, the IAB is in agreement on its substantive content.
在许多情况下，IAB发布文件以提供IAB声明或立场的永久记录。在这种情况下，IAB使用其内部讨论流程来完善文件的表述和技术内容，并且只有在IAB同意其实质性内容的情况下，才批准发布该文件。
For certain documents, it may not be appropriate for the IAB to take responsibility for technical correctness. For example, where the IAB has sponsored a workshop in which not all the participants were members of the IAB and/or not all the members of the IAB were present, approval by the IAB of a report of the workshop is used only to assert that the report is a faithful report of the proceedings of the workshop and that the matter is of interest to the community.
对于某些文件，IAB可能不适合对技术正确性负责。例如，如果IAB赞助了一个研讨会，其中并非所有参与者都是IAB成员和/或并非所有IAB成员都在场，IAB对研讨会报告的批准仅用于声明该报告是研讨会过程的真实报告，且该事项与社区利益相关。
Documents for which the IAB takes responsibility for technical correctness (the most usual case) will be indicated by noting the IAB as an author of the document, with individuals noted as editors or text authors. Other documents, such as workshop reports, will not specify the IAB as an author (although this does not preclude individual IAB members from being authors or editors).
IAB负责技术正确性的文件（最常见的情况）将通过注明IAB为文件作者、注明个人为编辑或文本作者来表示。其他文件，如研讨会报告，将不会指定IAB为作者（尽管这并不排除IAB成员个人成为作者或编辑）。
In general, the document (introductory) text should make plain the role of the IAB in publishing and supporting the text. Should the IAB have significant issues with any individual item in the document, a note may be included in the document explaining the issue.
一般而言，文件（介绍性）文本应明确IAB在发布和支持文本方面的作用。如果IAB对文件中的任何单个项目有重大问题，可在文件中加入注释，解释该问题。
The following is a description of the process used by the IAB to publish IAB documents as RFCs.
以下是IAB将IAB文档发布为RFC的过程描述。
1. The document is determined to be an IAB document by the IAB, as described in Section 1.
1. 如第1节所述，IAB确定该文件为IAB文件。
2. The IAB publishes an IAB draft (draft-iab-*). Comments on the draft are reviewed and may be integrated into successive iterations of the draft. In addition to considering comments received on the draft, the IAB may elect to refer the document to individuals or groups and explicitly solicit comments as appropriate.
2. IAB发布IAB草案（草案IAB-*）。审查对草案的评论，并将其纳入草案的后续迭代中。除了考虑收到的对草案的意见外，IAB还可以选择将文件提交给个人或团体，并在适当时明确征求意见。
3. For documents intended to be published as BCPs, the document is passed to the Internet Engineering Steering Group (IESG) with a sponsoring Area Director (AD), and follows the process outlined in [SPONSOR].
3. 对于拟作为BCP发布的文件，该文件将与赞助区域总监（AD）一起传递给互联网工程指导小组（IESG），并遵循[赞助商]中概述的流程。
4. For documents intended to be Informational RFCs, the remainder of this process is followed.
4. 对于拟作为信息性RFC的文档，遵循此过程的其余部分。
5. The chair of the IAB issues an IETF-wide Call for Comment on the IETF Announce mailing list. The comment period is normally no shorter than four weeks.
5. IAB主席在IETF范围内发出呼吁，征求对IETF公告邮件列表的意见。评论期通常不少于四周。
6. Comments received are considered for integration into the document. The IAB shall determine whether the document is ready for publication based on the comments received, or whether another round of document editing and, optionally, a further call for input is required.
6. 收到的意见将纳入文件。IAB应根据收到的评论确定文件是否已准备好发布，或是否需要进行另一轮文件编辑，以及（可选）进一步要求输入。
7. The document is passed to the RFC Editor for publication as an IAB document Informational RFC.
7. 该文档被传递到RFC编辑器，作为IAB文档信息RFC发布。
This document does not discuss matters with any particular security implications.
本文件不讨论具有任何特定安全影响的事项。
Bernard Aboba Loa Andersson Brian Carpenter Leslie Daigle Elwyn Davies Kevin Fall Olaf Kolkman Kurtis Lindqvist David Meyer David Oran Eric Rescorla Dave Thaler Lixia Zhang
Bernard Aboba Loa Andersson Brian Carpenter Leslie Daigle Elwyn Davies Kevin Fall Olaf Kolkman Kurtis Lindqvist David Meyer David Oran Eric Rescorla Dave Thaler Lixia Zhang
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", RFC 2026, BCP 9, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，RFC 2026，BCP 9，1996年10月。
[RFC4844] Daigle, L., Ed., "The RFC Series and RFC Editor", RFC 4844, July 2007.
[RFC4844]Daigle，L.，编辑，“RFC系列和RFC编辑器”，RFC 48442007年7月。
[SPONSOR] Arkko, J., Ed., "Guidance on Area Director Sponsoring of Documents", ION, May 2007.
[发起人]Arkko，J.，Ed.，“关于区域主管赞助文件的指导”，ION，2007年5月。
Authors' Addresses
作者地址
Leslie L. Daigle (editor)
莱斯利·戴格尔（编辑）
EMail: ledaigle@cisco.com, leslie@thinkingcat.com
EMail: ledaigle@cisco.com, leslie@thinkingcat.com
(IAB)
（IAB）
EMail: iab@iab.org
URI: http://www.iab.org/
EMail: iab@iab.org
URI: http://www.iab.org/
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。