Internet Architecture Board (IAB) O. Kolkman, Ed.
Request for Comments: 6635
Obsoletes: 5620 J. Halpern, Ed.
Category: Informational Ericsson
ISSN: 2070-1721 IAB
June 2012
Internet Architecture Board (IAB) O. Kolkman, Ed.
Request for Comments: 6635
Obsoletes: 5620 J. Halpern, Ed.
Category: Informational Ericsson
ISSN: 2070-1721 IAB
June 2012
RFC Editor Model (Version 2)
RFC编辑器模型（版本2）
Abstract
摘要
The RFC Editor model described in this document divides the responsibilities for the RFC Series into three functions: the RFC Series Editor, the RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described, as is the relationship between the IETF Administrative Oversight Committee (IAOC) and the RSOC. This document reflects the experience gained with "RFC Editor Model (Version 1)", documented in RFC 5620, and obsoletes that document.
本文档中描述的RFC编辑器模型将RFC系列的职责划分为三个功能：RFC系列编辑器、RFC生产中心和RFC发布者。描述了互联网体系结构委员会（IAB）通过RFC系列监督委员会（RSOC）的监督，以及IETF管理监督委员会（IAOC）和RSOC之间的关系。本文档反映了在RFC 5620中记录的“RFC编辑器模型（版本1）”中获得的经验，并废弃了该文档。
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. 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批准发布的文件不适用于任何级别的互联网标准；见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/rfc6635.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6635.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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 ....................................................3
1.1. The RFC Editor Function ....................................3
2. RFC Editor Model ................................................4
2.1. RFC Series Editor ..........................................7
2.1.1. Strategic Leadership and Management of the
Publication and Production Functions ................8
2.1.2. Representation of the RFC Series ....................8
2.1.2.1. Representation to the IETF .................8
2.1.2.1.1. Volunteerism ....................9
2.1.2.1.2. Policy Authority ................9
2.1.2.2. External Representation ....................9
2.1.3. Development of RFC Production and Publication ......10
2.1.4. Development of the RFC Series ......................10
2.1.5. Workload ...........................................11
2.1.6. Qualifications .....................................11
2.1.7. Conflict of Interest ...............................12
2.2. RFC Production Center .....................................12
2.3. RFC Publisher .............................................13
3. Committees .....................................................14
3.1. RFC Series Oversight Committee (RSOC) .....................14
3.1.1. RSOC Composition ...................................15
4. Administrative Implementation ..................................16
4.1. Vendor Selection for the Production and Publisher
Functions .................................................17
4.2. Budget ....................................................17
4.3. Disagreements among Entities Related to the RFC Editor ....18
4.4. Issues with Contractual Impact ............................19
5. IANA Considerations ............................................19
6. Security Considerations ........................................19
7. Acknowledgments ................................................20
8. References .....................................................21
8.1. Normative References ......................................21
8.2. Informative References ....................................21
1. Introduction ....................................................3
1.1. The RFC Editor Function ....................................3
2. RFC Editor Model ................................................4
2.1. RFC Series Editor ..........................................7
2.1.1. Strategic Leadership and Management of the
Publication and Production Functions ................8
2.1.2. Representation of the RFC Series ....................8
2.1.2.1. Representation to the IETF .................8
2.1.2.1.1. Volunteerism ....................9
2.1.2.1.2. Policy Authority ................9
2.1.2.2. External Representation ....................9
2.1.3. Development of RFC Production and Publication ......10
2.1.4. Development of the RFC Series ......................10
2.1.5. Workload ...........................................11
2.1.6. Qualifications .....................................11
2.1.7. Conflict of Interest ...............................12
2.2. RFC Production Center .....................................12
2.3. RFC Publisher .............................................13
3. Committees .....................................................14
3.1. RFC Series Oversight Committee (RSOC) .....................14
3.1.1. RSOC Composition ...................................15
4. Administrative Implementation ..................................16
4.1. Vendor Selection for the Production and Publisher
Functions .................................................17
4.2. Budget ....................................................17
4.3. Disagreements among Entities Related to the RFC Editor ....18
4.4. Issues with Contractual Impact ............................19
5. IANA Considerations ............................................19
6. Security Considerations ........................................19
7. Acknowledgments ................................................20
8. References .....................................................21
8.1. Normative References ......................................21
8.2. Informative References ....................................21
The IAB, on behalf of the Internet technical community, is concerned with ensuring the continuity of the RFC Series, orderly RFC Editor succession, RFC quality, and RFC document accessibility. The IAB is also sensitive to the concerns of the IETF Administrative Oversight Committee (IAOC) about providing the necessary services in a cost-effective and efficient manner.
IAB代表互联网技术界，致力于确保RFC系列的连续性、有序的RFC编辑顺序、RFC质量和RFC文档的可访问性。IAB还对IETF行政监督委员会（IAOC）关于以成本效益和效率高的方式提供必要服务的关注非常敏感。
The contemporary RFC Editor model [RFC5620] was first approved in October 2008, and our understanding of the model has evolved with our experience since. During the implementation of version 1 of the model [RFC5620], it was quickly realized that the role of the RFC Series Editor (RSE) and the oversight responsibilities needed to be structured differently. In order to gain experience with "running code", a transitional RSE was hired who analyzed the managerial environment and provided recommendations. This was followed by the appointment of an acting RSE, who ably managed the series while work was undertaken to select and hire a permanent RSE. This version of the model is based on the recommendations of both temporary RFC Series Editors and the extensive discussion in the IETF community, on the rfc-interest list, and within the IAB. As such, this document obsoletes [RFC5620].
当代RFC编辑器模型[RFC5620]于2008年10月首次获得批准，此后，我们对该模型的理解随着我们的经验而不断发展。在模型[RFC5620]第1版的实施过程中，人们很快意识到，RFC系列编辑器（RSE）的角色和监督职责需要以不同的结构进行组织。为了获得“运行代码”方面的经验，聘请了一名过渡性RSE，负责分析管理环境并提供建议。随后任命了一名代理RSE，他在挑选和聘用永久RSE的同时，出色地管理了该系列节目。该模型版本基于临时RFC系列编辑的建议以及IETF社区、RFC兴趣列表和IAB内的广泛讨论。因此，本文件废除了[RFC5620]。
This document, and the resulting structures, will be modified as needed through normal procedures. The RSE, and the IAB, through the RFC Oversight Committee (see Section 3.1), will continue to monitor discussions within the community about potential adjustments to the RFC Editor model and recognize that the process described in this document may need to be adjusted to align with any changes that result from such discussions; hence, the version number in the title.
本文件以及由此产生的结构将根据需要通过正常程序进行修改。RSE和IAB将通过RFC监督委员会（见第3.1节）继续监督社区内关于RFC编辑器模型潜在调整的讨论，并认识到可能需要调整本文件中描述的流程，以与此类讨论产生的任何变化保持一致；因此，标题中的版本号为。
The IAB and IAOC maintain their chartered responsibility as defined in [RFC2850] and [RFC4071].
IAB和IAOC保留[RFC2850]和[RFC4071]中定义的特许责任。
The RFC Series is described in [RFC4844]. Its Section 3.1 defines "RFC Editor":
[RFC4844]中描述了RFC系列。其第3.1节定义了“RFC编辑器”：
Originally, there was a single person acting as editor of the RFC Series (the RFC Editor). The task has grown, and the work now requires the organized activity of several experts, so there are RFC Editors, or an RFC Editor organization. In time, there may be multiple organizations working together to undertake the work required by the RFC Series. For simplicity's sake, and without
最初，只有一个人担任RFC系列的编辑（RFC编辑）。这项任务已经增加，现在这项工作需要几位专家的有组织的活动，因此有了RFC编辑器或RFC编辑器组织。随着时间的推移，可能会有多个组织共同承担RFC系列所需的工作。为了简单起见，没有
attempting to predict how the role might be subdivided among them, this document refers to this collection of experts and organizations as the "RFC Editor".
为了预测角色如何在他们之间细分，本文件将专家和组织的集合称为“RFC编辑器”。
The RFC Editor is an expert technical editor and series editor, acting to support the mission of the RFC Series. As such, the RFC Editor is the implementer handling the editorial management of the RFC Series, in accordance with the defined processes. In addition, the RFC Editor is expected to be the expert and prime mover in discussions about policies for editing, publishing, and archiving RFCs.
RFC编辑器是一名专家技术编辑器和系列编辑器，负责支持RFC系列的任务。因此，RFC编辑器是根据定义的流程处理RFC系列编辑管理的实现者。此外，RFC编辑有望成为有关RFC编辑、发布和归档政策讨论的专家和主要推动者。
RFC 4844 does not explore the internal organization of the RFC Editor. However, RFC 4844 envisions changes in the RFC Editor organizational structure. There have been several iterations on efforts to improve and clarify this structure. These have been led by the IAB, in consultation with the community and many leadership bodies within the community. This first resulted in the publication of [RFC5620] and then in further discussions leading to this document. Some of the details on this evolution can be found below. In undertaking this evolution, the IAB considered changes that increase flexibility and operational support options, provide for the orderly succession of the RFC Editor, and ensure the continuity of the RFC Series, while maintaining RFC quality, maintaining timely processing, ensuring document accessibility, reducing costs, and increasing cost transparency. The model set forth below describes the internal organization of the RFC Editor, while remaining consistent with RFC 4844.
RFC 4844不研究RFC编辑器的内部组织。然而，RFC4844设想了RFC编辑器组织结构的变化。为了改进和澄清这种结构，已经进行了多次迭代。这些活动由IAB领导，并与社区和社区内的许多领导机构协商。这首先导致了[RFC5620]的出版，然后导致了本文件的进一步讨论。关于这一演变的一些细节可以在下面找到。在进行这一演变过程中，IAB考虑了一些变化，这些变化增加了灵活性和操作支持选项，提供了RFC编辑器的有序继承，并确保RFC系列的连续性，同时保持RFC质量，保持及时处理，确保文档可访问性，降低成本，以及提高成本透明度。下面列出的模型描述了RFC编辑器的内部组织，同时与RFC 4844保持一致。
Note that RFC 4844 uses the term "RFC Editor function" or "RFC Editor" as the collective set of responsibilities for which this memo provides a model for internal organization. This memo defines the term "RFC Series Editor" or "Series Editor" for one of the organizational components.
请注意，RFC 4844使用术语“RFC编辑器功能”或“RFC编辑器”作为集体责任集，本备忘录为内部组织提供了一个模型。本备忘录为其中一个组织组件定义了术语“RFC系列编辑器”或“系列编辑器”。
The RFC Editor model divides the responsibilities for the RFC Series into the following components:
RFC编辑器模型将RFC系列的职责划分为以下组件：
o RFC Series Editor (RSE)
o RFC系列编辑器（RSE）
o RFC Production Center
o RFC生产中心
o RFC Publisher
o RFC出版商
The structure and relationship of the components of the RFC Series production and process is schematically represented by the figure below. The picture does not depict oversight and escalation relations. It does include the streams and their managers (which are not part of the RFC Series Editor, the RFC Production Center, or Publisher facilities) in order to more fully show the context in which the RFC Series Editor operates.
RFC系列生产和工艺组件的结构和关系如下图所示。图中没有描述监督和升级关系。它确实包括流及其管理器（不属于RFC系列编辑器、RFC生产中心或发行商设施的一部分），以便更全面地显示RFC系列编辑器操作的上下文。
+-------------+
| |
+--------------+ IAB <------------+
| | | |
| |=============| |
| | | |
| | RSOC <------------+
| | | |
| +-------+-----+ +-----+-----+
| | | |
| +...........|.........+ | Community |
| . | . | at |
| . +-------V-----+ . | Large |
| . | | . | |
| . | RFC | . +-----+-----+
| . | Series | . |
| . | Editor <------------+
| . | | .
| . +-+---------+-+ .
| . | | .
+-------------+ +-----V-------+ . +--V--+ +--V--+ . +-----+
| | | | . | | | | . | |
| Independent | | Independent | . | RFC | | | . | E |
| Authors +--> Submission +-----> | | | . | n |
| | | Editor | . | P | | | . | d |
| | | | . | r | | RFC | . | |
+-------------+ +-------------+ . | o | | | . | U |
+-------------+ +-------------+ . | d | | P | . | s |
| | | | . | u | | u | . | e |
| IAB +--> IAB +-----> c | | b | . | r |
| | | | . | t | | l | . | s |
+-------------+ +-------------+ . | i +---> i +--------> |
+-------------+ +-------------+ . | o | | s | . | & |
| | | | . | n | | h | . | |
| IRTF +--> IRSG +---->| | | e | . | R |
| | | | . | C | | r | . | e |
+-------------+ +-------------+ . | e | | | . | a |
+-------------+ +-------------+ . | n | | | . | d |
| | | | . | t | | | . | e |
| IETF +--> IESG +-----> e | | | . | r |
| | | | . | r | | | . | s |
+-------------+ +-------------+ . +-----+ +-----+ . +-----+
. .
+..... RFC Editor ....+
+-------------+
| |
+--------------+ IAB <------------+
| | | |
| |=============| |
| | | |
| | RSOC <------------+
| | | |
| +-------+-----+ +-----+-----+
| | | |
| +...........|.........+ | Community |
| . | . | at |
| . +-------V-----+ . | Large |
| . | | . | |
| . | RFC | . +-----+-----+
| . | Series | . |
| . | Editor <------------+
| . | | .
| . +-+---------+-+ .
| . | | .
+-------------+ +-----V-------+ . +--V--+ +--V--+ . +-----+
| | | | . | | | | . | |
| Independent | | Independent | . | RFC | | | . | E |
| Authors +--> Submission +-----> | | | . | n |
| | | Editor | . | P | | | . | d |
| | | | . | r | | RFC | . | |
+-------------+ +-------------+ . | o | | | . | U |
+-------------+ +-------------+ . | d | | P | . | s |
| | | | . | u | | u | . | e |
| IAB +--> IAB +-----> c | | b | . | r |
| | | | . | t | | l | . | s |
+-------------+ +-------------+ . | i +---> i +--------> |
+-------------+ +-------------+ . | o | | s | . | & |
| | | | . | n | | h | . | |
| IRTF +--> IRSG +---->| | | e | . | R |
| | | | . | C | | r | . | e |
+-------------+ +-------------+ . | e | | | . | a |
+-------------+ +-------------+ . | n | | | . | d |
| | | | . | t | | | . | e |
| IETF +--> IESG +-----> e | | | . | r |
| | | | . | r | | | . | s |
+-------------+ +-------------+ . +-----+ +-----+ . +-----+
. .
+..... RFC Editor ....+
Structure of RFC Series Production and Process
RFC系列产品和工艺的结构
Figure 1
图1
In this model, documents are produced and approved through multiple document streams. The stream manager for each stream is responsible for the content of that stream. The four streams that now exist are described in [RFC4844]. The RFC Editor function is responsible for the packaging and distribution of the documents. As such, documents from these streams are edited and processed by the Production Center and published by the Publisher. The RFC Series Editor will exercise strategic leadership and management over the activities of the RFC Publisher and the RFC Production Center (both of which can be seen as back-office functions) and will be the entity that:
在此模型中，通过多个文档流生成和批准文档。每个流的流管理器负责该流的内容。[RFC4844]中描述了目前存在的四个流。RFC编辑器功能负责文档的打包和分发。因此，这些流中的文档由生产中心编辑和处理，并由发布者发布。RFC系列编辑将对RFC出版商和RFC制作中心的活动行使战略领导和管理权（两者都可以视为后台职能），并将成为以下实体：
o Represents the RFC Series and the RFC Editor Function within the IETF and externally.
o 表示IETF内部和外部的RFC系列和RFC编辑器功能。
o Leads the community in the design of improvements to the RFC Series.
o 领导社区对RFC系列进行改进设计。
o Is responsible for planning and seeing to the execution of improvements in the RFC Editor production and access processes.
o 负责规划并确保RFC编辑器生产和访问流程的改进执行。
o Is responsible for the content of the rfc-editor.org web site, which is operated and maintained by the RFC Publisher.
o 负责rfc-editor.org网站的内容，该网站由rfc出版商运营和维护。
o Is responsible for developing consensus versions of vision and policy documents. These documents will be reviewed by the RFC Series Oversight Committee (Section 3.1) and subject to its approval before final publication.
o 负责制定愿景和政策文件的共识版本。这些文件将由RFC系列监督委员会（第3.1节）审查，并在最终出版前获得批准。
These responsibilities are defined below, although the specific work items under them are a matter for the actual employment contract and its Statement of Work (SOW).
这些责任定义如下，尽管其下的具体工作项目与实际雇佣合同及其工作说明书（SOW）有关。
The IAB and IAOC maintain their chartered responsibility as defined in [RFC2850] and [RFC4071]. More details on the oversight by the IAB via the RFC Series Oversight Committee (RSOC) can be found in Section 3.1. For example, the RSE does not have the direct authority to hire or fire RFC Editor contractors or personnel.
IAB和IAOC保留[RFC2850]和[RFC4071]中定义的特许责任。关于IAB通过RFC系列监督委员会（RSOC）进行监督的更多详情，请参见第3.1节。例如，RSE没有雇用或解雇RFC编辑承包商或人员的直接权力。
The RFC Series Editor is the individual with overall responsibility for the quality, continuity, and evolution of the RFC Series.
RFC系列编辑是全面负责RFC系列的质量、连续性和发展的个人。
The RSE is appointed by the IAB, but formally hired by the IAOC. The IAB delegates the direct oversight over the RSE to the RSOC, which it appoints.
RSE由IAB任命，但由IAOC正式聘用。IAB将RSE的直接监督权委托给RSOC，RSOC由IAB任命。
The RSE is expected to cooperate closely with the IAOC and the stream managers.
RSE预计将与IAOC和流管理者密切合作。
2.1.1. Strategic Leadership and Management of the Publication and Production Functions
2.1.1. 对出版和制作职能的战略领导和管理
With respect to the RFC Publisher and Production Center functions, the RSE provides input to the IASA budget, SOWs, and manages vendor selection processes. The RSE performs annual reviews of the RFC Production Center and Publisher function, which are then provided to the RSOC, the IASA, and the community. Normally, private financial details would not be included in a public version unless the IAOC concludes it is necessary to make such information public.
关于RFC发布者和生产中心职能，RSE向IASA预算、SOW和管理供应商选择流程提供输入。RSE对RFC生产中心和出版商职能部门进行年度审查，然后提供给RSOC、IASA和社区。通常情况下，除非IAOC认为有必要公开此类信息，否则公开版本中不会包含私人财务详细信息。
The RSE is responsible for the performance of the RFC Production Center and Publisher. The RSE is responsible for issues that go beyond the RFC Production Center or Publisher functions, such as cross-stream coordination of priorities. Issues that require changes to the budget or contracts shall be brought to the attention of the IAD by the RSE.
RSE负责RFC生产中心和发行商的绩效。RSE负责RFC生产中心或发布者职能以外的问题，如优先权的跨流协调。RSE应提请IAD注意需要更改预算或合同的问题。
The RSE is also responsible for creating documentation and structures that will allow for continuity of the RFC Series in the face of changes in contracts and personnel.
RSE还负责创建文档和结构，以便在合同和人员发生变化时保持RFC系列的连续性。
Vendor selection for the RFC Production Center and Publisher functions is done in cooperation with the streams and under final authority of the IASA. Details on this process can be found in Section 4.1.
RFC生产中心和发行商职能的供应商选择是与streams合作并在IASA的最终授权下完成的。有关此过程的详细信息，请参见第4.1节。
The RSE is the primary representative of the RFC Series. This representation is important both internally, relative to the IETF, and externally.
RSE是RFC系列的主要代表。这种表示在内部（相对于IETF）和外部都很重要。
The RSE is the primary point of contact to the IETF on matters relating to the RFC Series in general, or policy matters relating to specific documents. Issues of practical details in the processing of specific documents are generally worked through directly with the RFC Production Center staff.
RSE是IETF的主要联络点，负责与RFC系列相关的一般事宜，或与特定文件相关的政策事宜。具体文件处理过程中的实际细节问题通常由RFC生产中心员工直接解决。
This includes providing suitable reports to the community at large, providing email contact for policy questions and inputs, and enabling and participating in suitable on-line forums for discussion of issues related to the RFC Series.
这包括向整个社区提供适当的报告，为政策问题和投入提供电子邮件联系，并支持和参与适当的在线论坛，以讨论与RFC系列相关的问题。
Due to the history and nature of the interaction between the RSE and the IETF, certain principles, described in the following subsections, must be understood and adhered to by the RSE in his or her interactions with the community. These apply to the representation function, as well as to the leadership the RSE provides for production and series development.
由于RSE和IETF之间互动的历史和性质，RSE在与社区互动时必须理解并遵守以下小节中描述的某些原则。这些适用于代表职能，以及RSE为生产和系列开发提供的领导。
The vast majority of Internet technical community work is led, initiated, and done by community volunteers, including oversight, policy making, and direct production of, for example, many software tools. The RSE, while not a volunteer, is dependent upon these volunteer participants. Also, the spirit of the community is heavily focused on and draws from these volunteers. As such, the RSE needs to support the vitality and effectiveness of volunteer participation.
绝大多数互联网技术社区工作都是由社区志愿者领导、发起和完成的，包括监督、决策和直接制作，例如许多软件工具。RSE虽然不是志愿者，但依赖于这些志愿者参与者。此外，社区的精神高度集中在这些志愿者身上，并从他们身上汲取。因此，RSE需要支持志愿者参与的活力和有效性。
All decisions are to be made in the overall interest of the broader Internet community. The RSE is responsible for identifying materially concerned interest groups within the Internet community and reaching out to them. Those interest groups include at least the IETF community, the IRTF community, the network research community, and the network operations community. Other interest groups might also be materially interested.
所有决策都将以更广泛的互联网社区的整体利益为出发点。RSE负责识别互联网社区内的重大利益集团，并与他们联系。这些利益集团至少包括IETF社区、IRTF社区、网络研究社区和网络运营社区。其他利益集团也可能有重大利益。
The RSE must consult with the community on policy issues. The RSE works with the community to achieve policy that meets the overall quality, continuity, and evolution goals the RSE is charged with meeting. As described in Section 3.1, the RSE reports the results of such interactions to the RSOC, including a description of the outreach efforts and the specific recommendations on policy. This enables the RSOC to provide the oversight the IAB is required to apply, as well as to confirm that the Internet community has been properly consulted and considered in making policy.
RSE必须就政策问题与社区协商。RSE与社区合作，实现符合RSE负责实现的总体质量、连续性和发展目标的政策。如第3.1节所述，RSE向RSOC报告此类互动的结果，包括外联工作的说明和政策方面的具体建议。这使RSOC能够提供IAB所需的监督，并确认在制定政策时已适当咨询和考虑了互联网社区。
From time to time, individuals or organizations external to the IETF need a contact person to talk to about the RFC Series. The RSE, or the RSE's designate, serves this role.
IETF外部的个人或组织不时需要一名联系人来谈论RFC系列。RSE或RSE的指定人员担任此角色。
Over time, the RSE should determine what, if any, means should be employed to increase end-user awareness of the series, to reinforce the stature of the series, and to provide the contact point for outside parties seeking information on the series or the Editor.
随着时间的推移，RSE应确定应采用何种方式（如有），以提高最终用户对该系列的认识，增强该系列的知名度，并为寻求该系列或编辑信息的外部各方提供联络点。
Closely related to providing strategic leadership and management to the RFC Production Center and Publisher functions is the need to develop and improve those functions. The RSE is responsible for ensuring that such ongoing development takes place.
与为RFC生产中心和出版商职能提供战略领导和管理密切相关的是需要开发和改进这些职能。RSE负责确保进行此类持续发展。
This effort must include the dimensions of document quality, timeliness of production, and accessibility of results. It must also specifically take into account issues raised by the IETF community, including all the streams feeding into the RFC Editor function.
这项工作必须包括文件质量、制作的及时性和结果的可访问性等方面。它还必须特别考虑IETF社区提出的问题，包括提供给RFC编辑器功能的所有流。
In order to develop the RFC Series, the RSE is expected to develop a relationship with the Internet technical community. The Editor is expected to engage with the Internet technical community in a process of articulating and refining a vision for the series and its continuous evolution. The RSE is also expected to engage other users of the RFC Series, in particular, the consumers of these documents, such as those people who use them to specify products, write code, test behaviors, or other related activities.
为了开发RFC系列，RSE预计将与互联网技术社区建立关系。预计编者将与互联网技术界合作，为该系列及其持续发展阐明和完善愿景。RSE还将吸引RFC系列的其他用户，特别是这些文档的使用者，例如使用它们指定产品、编写代码、测试行为或其他相关活动的人。
Concretely:
具体地说：
The RSE is responsible for the coordination of discussion on series evolution among the series' stream participants and the broader Internet technical community.
RSE负责协调系列流参与者和更广泛的互联网技术社区之间关于系列演进的讨论。
In time, the RSE is expected to develop and refine a vision for the RFC Series, including examining:
预计RSE将及时制定和完善RFC系列的愿景，包括检查：
* The RFC Series, as it continues to evolve. The RSE is expected to take a broad view and look for the best ways to evolve the series for the benefit of the entire Internet community. As such, the RSE may even consider evolution beyond the historical 'by engineers for engineers' emphasis; and
* RFC系列，随着它的不断发展。RSE将以更广阔的视野，寻找最佳的方式，为整个互联网社区的利益发展该系列。因此，RSE甚至可以考虑超越工程师的“工程师”强调的历史；和
* Its publication-technical environment, by looking at whether it should be slowly changing in terms of publishing and archiving techniques -- particularly to better serve the communities that produce and depend on the RFC Series. For example, all of those communities have been slowly changing to include a significant population of multi-lingual individuals or non-native speakers of English. Another example is that some of these constituencies also have shifted to include significant
* 它的出版技术环境，通过研究它是否应该在出版和归档技术方面慢慢改变——特别是为了更好地为制作和依赖RFC系列的社区服务。例如，所有这些社区都在缓慢变化，包括大量多语种个人或非英语母语人士。另一个例子是，这些选区中的一些选区也已转变为包括重要选区
groups whose primary focus is on the constraints and consequences of network engineering, rather than a primary interest in the engineering issues themselves.
主要关注网络工程的约束和后果，而不是工程问题本身的主要兴趣的小组。
For this type of responsibility, the RSE cooperates closely with the community, and operates under oversight of the RSOC: thus, ultimately, under oversight of the IAB.
对于这类责任，RSE与社区密切合作，并在RSOC的监督下运作：因此，最终在IAB的监督下运作。
On average, the job is expected to take half of a full-time equivalent position (FTE, thus approx 20 hrs per week), with the workload per week nearing full time during IETF weeks. In addition, the job is expected to take more than 20 hours per week in the first few months of the engagement and when involved in special projects.
平均而言，该工作预计将占据相当于全职职位的一半（FTE，因此每周约20小时），IETF周内每周工作量接近全职。此外，在聘用的头几个月以及参与特殊项目时，该工作预计每周需要20多个小时。
The RFC Series Editor is a senior technology professional. The following qualifications are desired:
RFC系列编辑是一位高级技术专业人士。需要具备以下资格：
1. Strategic leadership and management experience fulfilling the requirements outlined in this document, the many aspects of this role, and the coordination of the overall RFC Editor process.
1. 满足本文件所述要求的战略领导和管理经验、该角色的许多方面以及整个RFC编辑流程的协调。
2. Good understanding of the English language and technical terminology related to the Internet.
2. 对互联网相关的英语和技术术语有良好的理解。
3. Good communication skills.
3. 良好的沟通技巧。
4. Experience with editorial processes.
4. 有编辑经验。
5. Ability to develop strong understanding of the IETF and RFC process.
5. 能够深入理解IETF和RFC流程。
6. Independent worker.
6. 独立工作者。
7. Willingness to, and availability for, travel.
7. 愿意并有机会出差。
8. The ability to work effectively in a multi-actor and matrixed environment with divided authority and responsibility similar to that described in this document.
8. 在多参与者和矩阵环境中有效工作的能力，具有类似于本文件所述的划分权限和责任的能力。
9. Experience with and ability to participate in, and manage, activities by email and teleconferences, not just face-to-face interactions.
9. 通过电子邮件和电话会议参与和管理活动的经验和能力，而不仅仅是面对面交流。
10. Demonstrated experience in strategic planning and the management of entire operations.
10. 在战略规划和整个运营管理方面具有丰富经验。
11. Experience as an RFC author.
11. 作为RFC作者的经验。
The RSE is expected to avoid even the appearance of conflict of interest or judgment in performing these roles. As such, the RSE is barred from having any ownership, advisory, or other relationship to the vendors executing the RFC Publisher or Production Center functions except as specified elsewhere in this document. If necessary, an exception can be made after public disclosure of those relationships and with the explicit permission of the IAB and IAOC.
RSE在履行这些职责时甚至可以避免出现利益冲突或判断冲突。因此，RSE不得与执行RFC发布者或生产中心职能的供应商有任何所有权、咨询或其他关系，除非本文件中另有规定。如有必要，在公开披露这些关系后，并经IAB和IAOC明确许可，可作出例外。
The RFC Production Center function is performed by a paid contractor, and the contractor's responsibilities include the following:
RFC生产中心功能由付费承包商执行，承包商的责任包括：
1. Editing inputs from all RFC streams to comply with the RFC Style Manual, under the direction of the RSE;
1. 在RSE的指导下，编辑所有RFC流的输入，以符合RFC样式手册；
2. Creating records of edits performed on documents;
2. 创建对文档进行编辑的记录；
3. Identifying where editorial changes might have technical impact and seeking necessary clarification;
3. 确定编辑变更可能产生技术影响的地方，并寻求必要的澄清；
4. Engaging in dialog with authors, document shepherds, IANA, and/or stream-dependent contacts when clarification is needed;
4. 当需要澄清时，与作者、文档管理员、IANA和/或依赖流的联系人进行对话；
5. Creating records of dialog with document authors;
5. 创建与文档作者的对话记录；
6. Requesting advice from the RFC Series Editor as needed;
6. 根据需要向RFC系列编辑征求建议；
7. Providing suggestions to the RFC Series Editor as needed;
7. 根据需要向RFC系列编辑提供建议；
8. Providing sufficient resources to support reviews of RFC Publisher performance by the RFC Series Editor and external reviews of the RFC Editor function initiated by the IAB or IAOC;
8. 提供足够的资源，以支持RFC系列编辑器对RFC出版商绩效的审查，以及IAB或IAOC发起的对RFC编辑器功能的外部审查；
9. Coordinating with IANA to ensure correct documentation of IANA-performed protocol registry actions;
9. 与IANA协调，确保正确记录IANA执行的协议注册行动；
10. Assigning RFC numbers;
10. 分配RFC编号；
11. Establishing publication readiness of each document through communication with the authors, document shepherds, IANA, and/or stream-dependent contacts, and, if needed, with the RFC Series Editor;
11. 通过与作者、文档管理员、IANA和/或流相关联系人以及RFC系列编辑器（如需要）的沟通，确定每个文档的出版准备状态；
12. Forwarding documents that are ready for publication to the RFC Publisher;
12. 将准备发布的文档转发给RFC发布者；
13. Forwarding records of edits and author dialog to the RFC Publisher so these can be preserved;
13. 将编辑和作者对话框的记录转发给RFC发布者，以便保存这些记录；
14. Liaising with the streams as needed.
14. 根据需要与溪流联络。
All these activities will be done under the general direction, but not day-to-day management, of the RSE and need some level of coordination with various submission streams and the RSE.
所有这些活动都将在RSE的总体指导下进行，但不是日常管理，并且需要与各种提交流和RSE进行一定程度的协调。
The RFC Production Center contractor is to be selected through an IASA Request for Proposal (RFP) process as described in Section 4.1.
RFC生产中心承包商将通过第4.1节所述的IASA招标（RFP）流程进行选择。
The RFC Publisher responsibilities include the following:
RFC发布者的职责包括：
1. Announcing and providing on-line access to RFCs.
1. 宣布并提供对RFC的在线访问。
2. Providing an on-line system to submit RFC Errata.
2. 提供在线系统以提交RFC勘误表。
3. Providing on-line access to approved RFC Errata.
3. 提供对经批准的RFC勘误表的在线访问。
4. Providing backups.
4. 提供备份。
5. Providing storage and preservation of records.
5. 提供记录的存储和保存。
6. Authenticating RFCs for legal proceedings.
6. 为法律程序认证RFC。
All these activities will be done under the general direction, but not day-to-day management, of the RSE and need some level of coordination with various submission streams and the RSE.
所有这些活动都将在RSE的总体指导下进行，但不是日常管理，并且需要与各种提交流和RSE进行一定程度的协调。
The RFC Publisher contractor is to be selected through an IASA RFP process as described in Section 4.1.
RFC出版商承包商将通过第4.1节所述的IASA RFP流程进行选择。
The IAB is responsible for the oversight of the RFC Series and acts as a body for final conflict resolution, including the process described in Section 4.3.
IAB负责监督RFC系列，并作为最终冲突解决机构，包括第4.3节所述的流程。
In order to provide continuity over periods longer than the NomCom appointment cycle [RFC3777] and assure that oversight includes suitable subject matter expertise, the IAB will establish a group that implements oversight for the IAB, the RFC Series Oversight Committee (RSOC).
为了在超过NomCom任命周期[RFC3777]的时间段内提供连续性，并确保监督包括适当的主题专业知识，IAB将成立一个小组，对IAB实施监督，即RFC系列监督委员会（RSOC）。
The RSOC will act with authority delegated from the IAB: in general, it will be the RSOC that will approve consensus policy and vision documents as developed by the RSE in collaboration with the community. While it is expected that the IAB will exercise due diligence in its supervision of the RSOC, the RSOC should be allowed the latitude to do its job without undue interference from the IAB. Therefore, it is expected that the IAB will accord RSOC reports and recommendations the benefit of the doubt.
RSOC将根据IAB授予的权限行事：通常，RSOC将批准RSE与社区合作制定的共识政策和愿景文件。虽然预计IAB将对RSOC的监管进行尽职调查，但应允许RSOC在不受IAB不当干扰的情况下开展工作。因此，预计IAB将对RSOC报告和建议给予质疑。
For all decisions that affect the RSE individually (e.g., hiring and firing), the RSOC prepares recommendations for the IAB, but the final decision is the responsibility of the IAB. For instance the RSOC would do the following:
对于单独影响RSE的所有决策（如雇佣和解雇），RSOC为IAB准备建议，但最终决策由IAB负责。例如，RSOC将执行以下操作：
o perform annual reviews of the RSE and report the result of these reviews to the IAB.
o 对RSE进行年度审查，并向IAB报告审查结果。
o manage RSE candidate selection and advise the IAB on candidate appointment (in other words, select the RSE subject to IAB approval).
o 管理RSE候选人的选择，并就候选人任命向IAB提供建议（换句话说，选择需要IAB批准的RSE）。
RSOC members are expected to recognize potential conflicts of interest and behave accordingly.
RSOC成员应认识到潜在的利益冲突，并采取相应的行动。
For the actual recruitment and selection of the RSE, the RSOC will propose a budget for the search process. It will work with IASA to refine that budget and develop remuneration criteria and an employment agreement or contracting plans, as appropriate.
对于RSE的实际招聘和选择，RSOC将为搜索过程提出预算。它将与IASA合作完善预算，并酌情制定薪酬标准和雇佣协议或合同计划。
The RSOC will be responsible for ensuring that the RFC Series is run in a transparent and accountable manner.
RSOC将负责确保RFC系列以透明和负责的方式运行。
The RSOC shall develop and publish its own rules of order.
RSOC应制定并公布自己的秩序规则。
The initial RSOC was charged with designing and executing a solicitation, search, and selection process for the first actual (not transitional or "acting") RSE appointment. That process involved iteration on this and related documents and evaluation of various strategies and options. During the creation of this document, it was expected that the RSOC would describe the process it ultimately selected to the community. The RSOC did involve the community in interim considerations when that was likely to be of value. Following completion of the selection process, the RSOC will determine the best way to share information learned and experience gained with the community and determine how to best preserve that information for future use.
最初的RSOC负责设计和执行第一次实际（非过渡或“代理”）RSE任命的征集、搜索和选择流程。这一过程涉及对本文件和相关文件的迭代以及对各种战略和选择的评估。在创建本文件期间，预计RSOC将向社区描述其最终选择的流程。RSOC确实让社区参与了可能有价值的临时考虑。选择过程完成后，RSOC将确定与社区分享所学信息和经验的最佳方式，并确定如何最好地保存这些信息以备将来使用。
The RSOC will operate under the authority of the IAB, with the IAB retaining final responsibility. The IAB will delegate authority and responsibility to the RSOC as appropriate and as RSOC and RSE relationships evolve. The RSOC will include people who are not current IAB members. Currently, this is aligned with the IAB program structure. The IAB will designate the membership of the RSOC with the following goals: preserving effective stability; keeping it small enough to be effective, and keeping it large enough to provide general Internet community expertise, specific IETF expertise, publication expertise, and stream expertise. Members serve at the pleasure of the IAB and are expected to bring a balance between short- and long-term perspectives. Specific input about, and recommendations of, members will be sought from the streams, the IASA, and the RSE.
RSOC将在IAB的授权下运作，IAB保留最终责任。IAB将视情况以及RSOC和RSE关系的发展，将权力和责任委托给RSOC。RSOC将包括非当前IAB成员的人员。目前，这与IAB计划结构一致。IAB将指定RSOC的成员，目标如下：保持有效的稳定性；保持其足够小以使其有效，并保持其足够大以提供一般互联网社区专业知识、特定IETF专业知识、出版物专业知识和流专业知识。会员服务于IAB，并有望在短期和长期观点之间取得平衡。将从streams、IASA和RSE寻求成员的具体意见和建议。
In addition to the members from outside of the IAB appointed to the RSOC, IAB members may participate as full members of the RSOC. Under most circumstances, there will be a specific individual IAB member appointed by the IAB as the program lead, who will be a full member of the RSOC. This member's role is distinct from any RSOC-internal organizational roles, such as would be created by the RSOC choosing to appoint a chair from among its members. Other IAB members may choose to be full members of the RSOC, with the consent of the IAB. This consent is primarily concerned with avoiding overpopulating the RSOC and providing it with relatively stable membership, which will work best if it is not too large a committee.
除被任命为RSOC的IAB以外的成员外，IAB成员可作为RSOC的正式成员参与。在大多数情况下，IAB将指定一名具体的IAB成员作为项目负责人，该成员将是RSOC的正式成员。该成员的角色不同于任何RSOC内部组织角色，如RSOC选择从其成员中任命主席所产生的角色。经IAB同意，其他IAB成员可选择成为RSOC的正式成员。这一同意主要是为了避免RSOC人口过多，并为其提供相对稳定的成员资格，如果RSOC不是一个太大的委员会，这将是最有效的。
The IAOC will appoint an individual to serve as its liaison to the RSOC. The RSE and the IAOC Liaison will serve as non-voting ex officio members of the RSOC. Either or both can be excluded from its discussions if necessary.
IAOC将任命一名个人作为其与RSOC的联络人。RSE和IAOC联络人将作为RSOC的无投票权当然成员。如有必要，可将其中一方或双方排除在讨论之外。
The exact implementation of the administrative and contractual activities described here are a responsibility of the IETF Administrative Oversight Committee (IAOC, [RFC4071]) in cooperation with the RFC Series Editor. The authority structure is described in Figure 2 below.
IETF行政监督委员会（IAOC，[RFC4071]）与RFC系列编辑合作，负责此处所述行政和合同活动的准确实施。下面的图2描述了权限结构。
+----------------+ +----------------+
| | | |
| IAB | | IAOC |
| | | |
+==========+-----+ +-+--------------+
| | .
| RSOC | .
| | .
+----+-----+ .
| .
| .
| ...................
| . .
+--------V---V----+ .
| | .
| RFC | .
| Series | .
| Editor | .
| | .
+--------+--------+ .
| .
| .................
| . .
+--+----------------+ .
| . | .
| . | .
+---V-----V--+ +--V----V---+
| RFC | | RFC |
| Production | | Publisher |
| Center | | |
+------------+ +-----------+
+----------------+ +----------------+
| | | |
| IAB | | IAOC |
| | | |
+==========+-----+ +-+--------------+
| | .
| RSOC | .
| | .
+----+-----+ .
| .
| .
| ...................
| . .
+--------V---V----+ .
| | .
| RFC | .
| Series | .
| Editor | .
| | .
+--------+--------+ .
| .
| .................
| . .
+--+----------------+ .
| . | .
| . | .
+---V-----V--+ +--V----V---+
| RFC | | RFC |
| Production | | Publisher |
| Center | | |
+------------+ +-----------+
Authority Structure of the RFC Series
RFC系列的权限结构
Legend:
------- IAB RFC Series Oversight
....... IAOC Contract/Budget Oversight
Legend:
------- IAB RFC Series Oversight
....... IAOC Contract/Budget Oversight
Figure 2
图2
As stated earlier, vendor selection is done in cooperation with the streams and under the final authority of the IAOC.
如前所述，供应商选择是在IAOC的最终授权下与streams合作完成的。
The RSE owns and develops the work definition (the SOW) and participates in the IASA vendor selection process. The work definition is created within the IASA budget and takes into account the stream managers and community input.
RSE拥有并制定工作定义（SOW），并参与IASA供应商选择流程。工作定义在IASA预算中创建，并考虑了流程经理和社区投入。
The process to select and contract for an RFC Production Center, RFC Publisher, and other RFC-related services, is as follows:
选择RFC生产中心、RFC发布者和其他RFC相关服务并签订合同的过程如下：
o The IAOC establishes the contract process, including the steps necessary to issue an RFP when necessary, the timing, and the contracting procedures.
o IAOC制定合同流程，包括必要时发布RFP所需的步骤、时间安排和合同程序。
o The IAOC establishes the Selection Committee, which will consist of the RSE, the IAD, and other members selected by the RSOC and the IAOC. The Committee shall be chaired by the RSE.
o IAOC成立了遴选委员会，由RSE、IAD以及RSOC和IAOC选出的其他成员组成。委员会由注册会计师担任主席。
o The Selection Committee selects the vendor, subject to the successful negotiation of a contract approved by the IAOC. In the event that a contract cannot be reached, the matter shall be referred to the Selection Committee for further action.
o 遴选委员会在IAOC批准的合同谈判成功后选择供应商。如果无法达成合同，则应将此事提交遴选委员会采取进一步行动。
o The Selection Committee may select an RFC Publisher either through the IASA RFP process or, at the Committee's option, the Committee may select the IETF Secretariat to provide RFC Publisher services, subject to negotiations in accordance with the IASA procedures.
o 遴选委员会可以通过IASA RFP流程选择RFC出版商，或者根据委员会的选择，委员会可以选择IETF秘书处提供RFC出版商服务，但需根据IASA程序进行协商。
The expenses discussed in this document are not new expenses. They have been and remain part of the IETF Administrative Support Activity (IASA, [RFC4071]) budget.
本文件中讨论的费用不是新的费用。它们一直是并且仍然是IETF行政支持活动（IASA，[RFC4071]）预算的一部分。
The RFC Series portion of the IASA budget shall include entries for the RSOC, RSE, RFC Production Center, and the RFC Publisher. The IASA budget shall also include entries for the streams, including the independent stream.
IASA预算的RFC系列部分应包括RSOC、RSE、RFC生产中心和RFC出版商的条目。IASA预算还应包括流的条目，包括独立流。
The IAOC has the responsibility to approve the total RFC Editor budget (and the authority to deny it). The RSE must work within the IAOC budgetary process.
IAOC有责任批准RFC编辑总预算（并有权拒绝）。RSE必须在IAOC预算流程内工作。
The RSE is responsible for managing the RFC Editor function to operate within those budgets. If production needs change, the RSE is responsible for working with the Production Center, and where appropriate, other RFC Editor component institutions, relevant streams, and/or the RSOC to determine what the correct response should be. If they agree that a budgetary change is needed, that decision needs to be taken to the IAD and the IAOC.
RSE负责管理RFC编辑器功能，以便在这些预算范围内运行。如果生产需要更改，RSE负责与生产中心以及其他RFC编辑器组件机构、相关流和/或RSOC（如适用）合作，以确定正确的响应。如果他们同意需要改变预算，则需要向国际审计署和国际审计委员会作出决定。
The RFC Series Editor and the RFC Production Center and Publisher facilities work with the various streams to produce RFCs. Disagreements may arise between these entities during the execution of the RFC Editor operations. In particular, different streams may disagree with each other, or disagree with the RFC Editor function. Potentially, even the RSOC or the IAOC could find themselves in disagreement with some aspect of the RFC Editor operations. Note that disagreements between an author and the RFC Production Center are not cross-entity issues, and they are to be resolved by the RSE, in accordance with the rest of this document.
RFC系列编辑器、RFC生产中心和发行商设施与各种流一起工作以生成RFC。在执行RFC编辑器操作期间，这些实体之间可能会出现分歧。特别是，不同的流可能彼此不一致，或者与RFC编辑器功能不一致。甚至RSOC或IAOC也可能发现自己对RFC编辑器操作的某些方面存在分歧。请注意，作者和RFC制作中心之间的分歧不是跨实体问题，应由RSE根据本文件的其余部分解决。
If such cross-entity disagreements arise, the community would generally hope that they can be resolved politely and directly. However, this is not always possible. At that point, any relevant party would first formally request a review and reconsideration of the decision. If the party still disagrees after the reconsideration, that party may ask the RSE to decide or, especially if the RSE is involved, the party may ask the IAB Chair (for a technical or procedural matter) to mediate or appoint a mediator to aid in the discussions, although he or she not is obligated to do so. All parties should work informally and in good faith to reach a mutually agreeable conclusion. As noted below, any such issues that involve contractual matters must be brought to the attention of the IAOC. If the IAB Chair is asked to assist in resolving the matter, the Chair may ask for advice or seek assistance from anyone the Chair deems helpful. The Chair may also alert any appropriate individuals or organizations to the existence of the issue.
如果出现这种跨实体的分歧，社区通常希望能够礼貌和直接地解决这些分歧。然而，这并不总是可能的。届时，任何相关方都将首先正式要求对该决定进行审查和重新审议。如果一方在重新审议后仍不同意，该方可要求RSE作出决定，尤其是如果涉及RSE，该方可要求IAB主席（就技术或程序问题）进行调解或指定调解人协助讨论，尽管他或她没有义务这样做。各方应非正式地、真诚地开展工作，以达成双方都同意的结论。如下文所述，涉及合同事项的任何此类问题必须提请IAOC注意。如果IAB主席被要求协助解决问题，主席可向其认为有帮助的任何人寻求建议或帮助。主席还可提醒任何适当的个人或组织注意该问题的存在。
If such a conclusion is not possible through the above less formal processes, then the matter must be registered with the RFC Series Oversight Committee. The RSOC may choose to offer advice to the RSE or more general advice to the parties involved and may ask the RSE to defer a decision until it formulates its advice. However, if a timely decision cannot be reached through discussion, mediation, and mutual agreement, the RSE is expected to make whatever decisions are needed to ensure the smooth operation of the RFC Editor function; those decisions are final.
如果通过上述不太正式的程序无法得出这样的结论，则该事项必须向RFC系列监督委员会登记。RSOC可选择向RSE提供建议或向相关方提供更一般性的建议，并可要求RSE推迟做出决定，直到其制定建议。但是，如果无法通过讨论、调解和相互协商达成及时决定，则RSE应做出任何必要的决定，以确保RFC编辑器功能的顺利运行；这些决定是最终决定。
The RSE may make final decisions unilaterally only to assure the functioning of the process, and only while there is an evaluation of current policies to determine whether they are appropriately implemented in the decision or need adjustment. In particular, it should be noted that final decisions about the technical content of individual documents are the exclusive responsibility of the stream approvers from which those documents originate, as shown in the illustration in Figure 1.
RSE可以单方面做出最终决定，以确保流程的运作，并且只有在对当前政策进行评估以确定其是否在决策中得到适当实施或需要调整时才能做出最终决定。特别值得注意的是，如图1所示，有关单个文档技术内容的最终决定是这些文档来源的流审批人的专属责任。
If informal agreements cannot be reached, then formal RSOC review and decision making may be required. If so, the RSE must present the issues involved to the community so that the community is aware of the situation. The RSE will then report the issue to the RSOC for formal resolution by the RSOC with confirmation by the IAB in its oversight capacity.
如果无法达成非正式协议，则可能需要正式的RSOC审查和决策。如果是这样，RSE必须向社区提出相关问题，以便社区了解情况。RSE随后将向RSOC报告该问题，由RSOC正式解决，并由IAB以其监督能力确认。
IAB and community discussion of any patterns of disputes are expected to inform future changes to RFC Series policies, including possible updates to this document.
IAB和社区对任何争议模式的讨论预计将通知RFC系列政策的未来变化，包括本文件的可能更新。
If a disagreement or decision has immediate or future contractual consequences, it falls under BCP 101 [RFC4071] and IASA; thus, the RSE must identify the issue and provide his or her advice to the IAOC; additionally, if the RSOC has provided advice, forward that advice as well. The IAOC must notify the RSOC and IAB regarding the action it concludes is required to resolve the issue based on its applicable procedures and provisions in the relevant contracts.
如果分歧或决定具有即时或未来的合同后果，则属于BCP 101[RFC4071]和IASA的范畴；因此，RSE必须识别问题并向IAOC提供建议；此外，如果RSOC提供了建议，也应转发该建议。IAOC必须通知RSOC和IAB其根据相关合同中的适用程序和规定得出的解决问题所需采取的行动。
This document defines several functions within the overall RFC Editor structure, and it places the responsibility for coordination of registry value assignments with the RFC Production Center. The IAOC will facilitate the establishment of the relationship between the RFC Production Center and IANA.
本文档在整个RFC编辑器结构中定义了几个功能，并负责与RFC生产中心协调注册表值分配。IAOC将促进RFC生产中心与IANA之间建立关系。
This document does not create a new registry nor does it register any values in existing registries, and no IANA action is required.
本文档不创建新注册表，也不在现有注册表中注册任何值，并且不需要IANA操作。
The same security considerations as those in [RFC4844] apply. The processes for the publication of documents must prevent the introduction of unapproved changes. Since the RFC Editor maintains the index of publications, sufficient security must be in place to prevent these published documents from being changed by external
与[RFC4844]中的安全注意事项相同。文件发布流程必须防止引入未经批准的更改。由于RFC编辑器维护出版物索引，因此必须具有足够的安全性，以防止外部用户更改这些已发布的文档
parties. The archive of RFC documents, any source documents needed to recreate the RFC documents, and any associated original documents (such as lists of errata, tools, and, for some early items, originals that are not machine readable) need to be secured against any kind of data storage failure.
派对。RFC文档的存档、重新创建RFC文档所需的任何源文档以及任何相关的原始文档（例如勘误表、工具列表，以及对于某些早期项目，不可由机器读取的原始文档）都需要进行保护，以防出现任何类型的数据存储故障。
The IAOC should take these security considerations into account during the implementation and enforcement of the RFC Editor component contracts.
IAOC应在实施和执行RFC编辑器组件合同期间考虑这些安全因素。
The RFC Editor model was conceived and discussed in hallways and on mailing lists. The first iteration of the text on which this document is based was first written by Leslie Daigle, Russ Housley, and Ray Pelletier. In addition to the members of the IAOC and IAB in conjunction with those roles, major and minor contributions were made by (in alphabetical order): Bob Braden, Brian Carpenter, Sandy Ginoza, Alice Russo, Joel M. Halpern, Alfred Hoenes, Paul Hoffman, John Klensin, Subramanian Moonesamy, and Jim Schaad.
RFC编辑器模型是在走廊和邮件列表中构思和讨论的。本文档所基于的文本的第一次迭代是由Leslie Daigle、Russ Housley和Ray Pelletier首先编写的。除了IAOC和IAB的成员以及这些角色外，主要和次要贡献由以下人员（按字母顺序排列）：鲍勃·布拉登、布赖恩·卡彭特、桑迪·吉诺萨、爱丽丝·鲁索、乔尔·M·哈尔伯恩、阿尔弗雷德·霍恩斯、保罗·霍夫曼、约翰·克莱辛、Subramanian Moonesamy和吉姆·沙德。
The IAOC members at the time this RFC Editor model was approved were (in alphabetical order): Bernard Aboba (ex officio), Eric Burger, Dave Crocker, Marshall Eubanks, Bob Hinden, Russ Housley (ex officio), Ole Jacobsen, Ray Pelletier (non-voting), and Lynn St. Amour (ex officio).
在该RFC编辑模式获得批准时，IAOC成员（按字母顺序排列）：伯纳德·阿博巴（当然）、埃里克·伯格、戴夫·克罗克、马歇尔·尤班克斯、鲍勃·辛登、罗斯·霍斯利（当然）、奥勒·雅各布森、雷·佩莱蒂埃（无投票权）和林恩·圣·阿穆尔（当然）。
The IAB members at the time the initial RFC Editor model was approved were (in alphabetical order): Loa Andersson, Gonzalo Camarillo, Stuart Cheshire, Russ Housley, Olaf Kolkman, Gregory Lebovitz, Barry Leiba, Kurtis Lindqvist, Andrew Malis, Danny McPherson, David Oran, Dave Thaler, and Lixia Zhang. In addition, the IAB included two ex officio members: Dow Street, who was serving as the IAB Executive Director, and Aaron Falk, who was serving as the IRTF Chair.
在最初的RFC编辑模式获得批准时，IAB的成员是（按字母顺序排列）：Loa Andersson、Gonzalo Camarillo、Stuart Cheshire、Russ Housley、Olaf Kolkman、Gregory Lebovitz、Barry Leiba、Kurtis Lindqvist、Andrew Malis、Danny McPherson、David Oran、Dave Thaler和Lixia Zhang。此外，IAB还包括两名当然成员：担任IAB执行董事的陶氏街和担任IRTF主席的亚伦·福克。
The IAB members at the time the this RFC was approved were (in alphabetical order): Bernard Aboba, Ross Callon, Alissa Cooper, Spencer Dawkins, Joel Halpern, Russ Housley, David Kessens, Olaf Kolkman, Danny McPherson, Jon Peterson, Andrei Robachevsky, Dave Thaler, and Hannes Tschofenig. In addition, at the time of approval, the IAB included two ex officio members: Mary Barnes who was serving as the IAB Executive Director, and Lars Eggert, who was serving as the IRTF Chair.
本RFC批准时的IAB成员（按字母顺序排列）：伯纳德·阿博巴、罗斯·卡隆、艾莉莎·库珀、斯宾塞·道金斯、乔尔·哈尔佩恩、罗斯·霍斯利、大卫·凯森斯、奥拉夫·科尔克曼、丹尼·麦克弗森、乔恩·彼得森、安德烈·罗巴切夫斯基、戴夫·泰勒和汉内斯·茨霍芬尼。此外，在批准时，IAB包括两名当然成员：担任IAB执行董事的Mary Barnes和担任IRTF主席的Lars Eggert。
[RFC4844] Daigle, L. and Internet Architecture Board, "The RFC Series and RFC Editor", RFC 4844, July 2007.
[RFC4844]Daigle，L.和互联网架构委员会，“RFC系列和RFC编辑器”，RFC 48442007年7月。
[RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF Administrative Support Activity (IASA)", BCP 101, RFC 4071, April 2005.
[RFC4071]Austein，R.和B.Wijnen，“IETF行政支持活动（IASA）的结构”，BCP 101，RFC 4071，2005年4月。
[RFC2850] Internet Architecture Board and B. Carpenter, "Charter of the Internet Architecture Board (IAB)", BCP 39, RFC 2850, May 2000.
[RFC2850]互联网架构委员会和B.Carpenter，“互联网架构委员会（IAB）章程”，BCP 39，RFC 2850，2000年5月。
[RFC5620] Kolkman, O. and IAB, "RFC Editor Model (Version 1)", RFC 5620, August 2009.
[RFC5620]Kolkman，O.和IAB，“RFC编辑器模型（版本1）”，RFC562009年8月。
[RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", BCP 10, RFC 3777, June 2004.
[RFC3777]Galvin，J.，“IAB和IESG选择、确认和召回流程：提名和召回委员会的运作”，BCP 10，RFC 3777，2004年6月。
Authors' Addresses
作者地址
Olaf M. Kolkman (editor)
奥拉夫·科尔克曼（编辑）
EMail: olaf@nlnetlabs.nl
EMail: olaf@nlnetlabs.nl
Joel M. Halpern (editor) Ericsson
乔尔·哈尔佩恩（编辑）爱立信
EMail: joel.halpern@ericsson.com
EMail: joel.halpern@ericsson.com
Internet Architecture Board
互联网架构委员会
EMail: iab@iab.org
EMail: iab@iab.org