Internet Engineering Task Force (IETF) P. Hoffman
Request for Comments: 6322 VPN Consortium
Category: Informational July 2011
ISSN: 2070-1721
Internet Engineering Task Force (IETF) P. Hoffman
Request for Comments: 6322 VPN Consortium
Category: Informational July 2011
ISSN: 2070-1721
Datatracker States and Annotations for the IAB, IRTF, and Independent Submission Streams
IAB、IRTF和独立提交流的Datatracker状态和注释
Abstract
摘要
This document describes extending the IETF Datatracker to capture and display the progression of Internet-Drafts that are intended to be published as RFCs by the IAB, IRTF, or Independent Submissions Editor. The states and annotations that are to be added to the Datatracker will be applied to Internet-Drafts as soon as any of these streams identify the Internet-Draft as a potential eventual RFC, and will continue through the lifetime of the Internet-Draft. The goal of adding this information to the Datatracker is to give the whole Internet community more information about the status of these Internet-Drafts and the streams from which they originate.
本文档描述了如何扩展IETF数据跟踪器，以捕获和显示拟由IAB、IRTF或独立提交编辑器以RFC形式发布的互联网草案的进度。待添加到Datatracker的状态和注释将应用于互联网草稿，只要这些流中的任何流将互联网草稿识别为潜在的最终RFC，并将在互联网草稿的整个生命周期内持续。将这些信息添加到Datatracker的目的是为整个互联网社区提供更多关于这些互联网草案的状态及其来源的流的信息。
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 Engineering Task Force (IETF). 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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见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/rfc6322.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6322.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 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. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
As described in Section 5 of [RFC4844], there are currently four streams that feed into the RFC publication process: the IETF document stream, the Internet Architecture Board (IAB) document stream, the Internet Research Task Force (IRTF) document stream, and the Independent Submissions stream that is administered by the Independent Submissions Editor (ISE). Each of these streams consist of Internet-Drafts (often abbreviated "I-Ds") that have been identified by an organization or role as being part of their stream. Each stream maintainer progresses documents towards RFC publication in its own fashion. A document can only be in one stream at a time.
如[RFC4844]第5节所述，目前有四个流进入RFC发布流程：IETF文件流、互联网体系结构委员会（IAB）文件流、互联网研究任务组（IRTF）文件流，以及由独立提交编辑器（ISE）管理的独立提交流。这些流中的每一个都由互联网草稿（通常缩写为“I-D”）组成，这些草稿已被组织或角色识别为其流的一部分。每个流维护者以自己的方式向RFC发布推进文档。一个文档一次只能在一个流中。
In recent years, there has been a desire by IETF participants and others to see more of the process used by each stream. For example, some people want to know how close the IAB is to finishing a particular document; IETF participants might want to know the progress of IRTF research documents that are in areas related to their engineering work; people who have asked for the ISE to publish
近年来，IETF参与者和其他人希望看到每个流使用的更多过程。例如，有些人想知道IAB离完成一个特定文档有多近；IETF参与者可能希望了解与其工程工作相关领域的IRTF研究文件的进展情况；要求ISE出版的人
their document want to track its progress. If the IETF Datatracker ("tracker") has more information about each stream's states, this information is much more easily accessible.
他们的文档希望跟踪其进度。如果IETF数据跟踪器（“跟踪器”）有更多关于每个流状态的信息，那么这些信息就更容易访问。
In this document, the term "IETF Datatracker" is used as a generic name for the existing tool used to track state changes as Internet-Drafts are processed. The word "IETF" in the name "IETF Datatracker" is not meant to limit use of the tool to the IETF document stream; this document expands use of the tool to the other streams described in RFC 4844.
在本文件中，术语“IETF数据跟踪器”用作现有工具的通用名称，该工具用于在处理互联网草稿时跟踪状态变化。“IETF数据跟踪器”名称中的“IETF”一词并不意味着将工具的使用限制在IETF文档流中；本文档将该工具的使用扩展到RFC 4844中描述的其他流。
This document describes the additional tracker states that are specific to each of the IAB, the IRTF, and the ISE document flows. A document might also have one or more annotations assigned as well. Because each stream is controlled by a different organization, this document separates out the proposed states and annotations for each stream, and associates specific semantics stream-by-stream.
本文档描述了特定于IAB、IRTF和ISE文档流的附加跟踪状态。一个文档也可以指定一个或多个注释。因为每个流都由不同的组织控制，所以本文档分离出每个流的建议状态和注释，并逐个流关联特定的语义流。
Annotations may be applied at any time to a document that is intended for the particular stream. A document may have more than one annotation applied to it. It is likely that the comments for these annotations will supply valuable information about the annotation. Each stream owner needs to have write access to the states and annotations for all the documents in their stream. They should also be able to assign others to have the same write privileges.
注释可随时应用于针对特定流的文档。一个文档可能应用了多个注释。这些注释的注释可能会提供有关注释的有价值的信息。每个流所有者都需要对其流中所有文档的状态和注释具有写访问权。他们还应该能够分配其他人具有相同的写入权限。
This document does not describe which person in each stream might be able to edit these states and annotations; it is assumed that this is a simple enough task that it can be negotiated between each stream administrator and the tracker administrator. Also, this document assumes that whoever is making the edits to the state and annotations can enter comments that will be publicly visible.
本文档没有描述每个流中的哪个人可能能够编辑这些状态和注释；假设这是一个足够简单的任务，可以在每个流管理员和跟踪器管理员之间协商。此外，本文档假定对状态和注释进行编辑的任何人都可以输入公开可见的注释。
Some streams have comments that are very long, such as document reviews and document poll results. The tracker needs to be able to store long annotation comments.
有些流有很长的注释，例如文档评论和文档投票结果。跟踪器需要能够存储长注释注释。
Note that this document does not discuss documents in the IETF stream. The states and permissions for IETF stream documents that have been requested for publication are already implemented in the tracker. A separate set of documents, [RFC6174] and [RFC6175], describe the tracker states and associated permissions proposed for documents in the IETF stream that have been adopted, or are being considered for adoption, by IETF Working Groups.
请注意，本文档不讨论IETF流中的文档。已请求发布的IETF流文档的状态和权限已在跟踪器中实现。一组单独的文件[RFC6174]和[RFC6175]描述了针对IETF工作组已采用或正在考虑采用的IETF流中的文件提出的跟踪器状态和相关权限。
The intent of this document is to inform an initial development effort for the tool described here. It is not intended to stand as the requirements against the tool once it is deployed. That is,
本文档的目的是通知此处所述工具的初始开发工作。一旦部署了工具，它就不会成为针对该工具的需求。就是，
there is no current intention to update this document frequently as the tool evolves and small features are added and changed.
随着工具的发展以及小功能的添加和更改，目前不打算频繁更新本文档。
This document defines three state machines that fit into the IETF Datatracker. The Datatracker will have multiple state machines. This document was prepared in coordination with the IAB, IRTF, and ISE, at the request of the IETF Administrative Oversight Committee (IAOC).
本文档定义了三种适合IETF数据跟踪器的状态机。Datatracker将有多个状态机。本文件是应IETF行政监督委员会（IAOC）的要求，与IAB、IRTF和ISE协调编写的。
This section describes the desired states and annotations for the IAB stream.
本节描述IAB流所需的状态和注释。
o Candidate IAB Document -- A document being considered for the IAB stream.
o 候选IAB文档——IAB流正在考虑的文档。
o Active IAB Document -- This document has been adopted by the IAB and is being actively developed.
o 主动IAB文件——该文件已被IAB采纳，并正在积极开发中。
o Parked IAB Document -- This document has lost its author or editor, is waiting for another document to be written, or cannot currently be worked on by the IAB for some other reason. Annotations probably explain why this document is parked.
o 暂停的IAB文档--此文档已失去其作者或编辑器，正在等待编写另一个文档，或者由于其他原因，IAB当前无法处理此文档。注释可能解释了此文档被搁置的原因。
o IAB Review -- This document is awaiting the IAB itself to come to internal consensus.
o IAB审查——本文件正在等待IAB本身达成内部共识。
o Community Review -- This document has completed internal consensus within the IAB and is now under community review. (The IAB normally allows community input during earlier stages of the process as well.)
o 社区审查——本文件已在IAB内部达成共识，目前正在进行社区审查。（IAB通常也允许在流程的早期阶段进行社区投入。）
o Approved by IAB, To Be Sent to RFC Editor -- The consideration of this document is complete, but it has not yet been sent to the RFC Editor for publication (although that is going to happen soon).
o 经IAB批准，将发送给RFC编辑器——本文件的审议已经完成，但尚未发送给RFC编辑器进行发布（尽管这很快就会发生）。
o Sent to a Different Organization for Publication -- The IAB does not expect to publish the document itself, but has passed it on to a different organization that might continue work on the document. The expectation is that the other organization will eventually publish the document.
o 发送到其他组织以供发布--IAB不希望发布文档本身，但已将其传递给可能继续处理文档的其他组织。我们的期望是，其他组织最终将发布该文档。
o Sent to the RFC Editor -- The IAB processing of this document is complete and it has been sent to the RFC Editor for publication. The document may be in the RFC Editor's queue, or it may have been published as an RFC; this state doesn't distinguish between different states occurring after the document has left the IAB.
o 发送到RFC编辑器--此文档的IAB处理已完成，并已发送到RFC编辑器以供发布。文档可能在RFC编辑器的队列中，也可能已作为RFC发布；此状态不区分文档离开IAB后发生的不同状态。
o Dead IAB Document -- This document was an active IAB document, but for some reason it is no longer being pursued for the IAB stream. It is possible that the document might be revived later, possibly in another stream.
o 死IAB文档——此文档是活动IAB文档，但由于某些原因，IAB流不再跟踪它。文档可能会在稍后恢复，可能是在另一个流中。
o Editor Needed -- The document has lost its editor but it is still intended to be part of the IAB stream.
o 需要编辑器--文档已丢失其编辑器，但仍打算成为IAB流的一部分。
o Waiting for Dependency on Other Document -- Activity on this document is expected to be low or non-existent while waiting for another document (probably listed in the comments) to progress.
o 正在等待对其他文档的依赖关系--在等待另一个文档（可能在注释中列出）进行时，此文档上的活动可能较低或不存在。
o Waiting for Partner Feedback -- The IAB often produces documents that need to be socialized with outside organizations (such as the IEEE) or other internal organizations (such as the IESG or the IAOC). This document has been sent out for feedback from one of these partner groups.
o 等待合作伙伴反馈——IAB通常会生成需要与外部组织（如IEEE）或其他内部组织（如IESG或IAOC）进行社交的文档。本文件已发送，以征求其中一个合作伙伴小组的反馈意见。
o Awaiting Reviews -- Activity on this document is expected to be low or non-existent while waiting for reviews that were solicited by the IAB.
o 等待审查——在等待IAB征求的审查时，本文件上的活动预计较少或不存在。
o Revised I-D Needed -- Comments that will cause changes have been submitted, and no processing is expected until a new draft is issued.
o 需要修订的I-D——已经提交了将导致变更的意见，在发布新草案之前，预计不会进行任何处理。
o Document Shepherd Followup -- The document's shepherd is expected to take some action before the document can proceed.
o Document Shepherd Followup—文档的Shepherd在继续文档之前需要执行一些操作。
Some IAB members, and members of the IAB Executive Directorate, need to be able to set the states and annotations for IAB documents during their life cycle. The IAB Chair needs to be able to grant access to individuals to modify the state and annotations; such access applies to all IAB Stream documents.
一些IAB成员和IAB执行董事会成员需要能够在其生命周期内设置IAB文件的状态和注释。IAB主席需要能够允许个人修改状态和注释；这种访问适用于所有IAB流文档。
This section describes the desired states and annotations for the IRTF stream. Some of the steps take place in IRTF Research Groups (RGs), while others take place in the Internet Research Steering Group (IRSG).
本节描述IRTF流所需的状态和注释。其中一些步骤在IRTF研究小组（RGs）中进行，而另一些步骤在互联网研究指导小组（IRSG）中进行。
o Candidate RG Document -- This document is under consideration in an RG for becoming an IRTF document. A document in this state does not imply any RG consensus and does not imply any precedence or selection. It's simply a way to indicate that somebody has asked for a document to be considered for adoption by an RG.
o 候选RG文件——RG正在考虑将此文件作为IRTF文件。处于这种状态的文件并不意味着任何RG共识，也不意味着任何优先权或选择权。这只是一种表示有人要求RG考虑采纳文档的方式。
o Active RG Document -- This document has been adopted by an RG and is being actively developed.
o 现行RG文件——该文件已被RG采用，并正在积极开发中。
o Parked RG Document -- This document has lost its author or editor, is waiting for another document to be written, or cannot currently be worked on by the RG that adopted it for some other reason.
o 停驻的RG文档--此文档已失去作者或编辑器，正在等待编写另一个文档，或者由于其他原因，当前无法由采用它的RG处理。
o In RG Last Call -- The document is in its final review in the RG.
o 在RG Last Call中——文档正在RG中进行最终审阅。
o Waiting for Document Shepherd -- IRTF documents have document shepherds who help RG documents through the process after the RG has finished with the document.
o 等待文档管理员——IRTF文档有文档管理员，他们在RG完成文档后帮助RG文档完成整个过程。
o Waiting for IRTF Chair -- The IRTF Chair is meant to be performing some task such as sending a request for IESG Review.
o 等待IRTF主席——IRTF主席应该执行一些任务，例如发送IESG审查请求。
o Awaiting IRSG Reviews -- The document shepherd has taken the document to the IRSG and solicited reviews from one or more IRSG members.
o 等待IRSG审查——文件管理人已将文件提交给IRSG，并征求一个或多个IRSG成员的审查。
o In IRSG Poll -- The IRSG is taking a poll on whether or not the document is ready to be published.
o 在IRSG轮询中——IRSG正在对文档是否准备好发布进行轮询。
o In IESG Review -- The IRSG has asked the IESG to do a review of the document, as described in [RFC5742].
o 在IESG审查中——IRSG已要求IESG对文件进行审查，如[RFC5742]所述。
o Sent to the RFC Editor -- The document has been submitted for publication (and not returned to the IRTF for further action). The document may be in the RFC Editor's queue, or it may have been published as an RFC; this state doesn't distinguish between different states occurring after the document has left the IRTF.
o 发送到RFC编辑器——文档已提交以供发布（未返回给IRTF以供进一步操作）。文档可能在RFC编辑器的队列中，也可能已作为RFC发布；此状态不区分文档离开IRTF后发生的不同状态。
o Document on Hold Based on IESG Request -- The IESG has requested that the document be held pending further review, as specified in RFC 5742, and the IRTF has agreed to such a hold.
o 基于IESG请求的搁置文件——IESG已请求按照RFC 5742的规定，在进一步审查之前搁置该文件，IRTF已同意此类搁置。
o Dead IRTF Document -- This document was an active IRTF document, but for some reason it is no longer being pursued for the IRTF stream. It is possible that the document might be revived later, possibly in another stream.
o 死的IRTF文档——该文档是一个活动的IRTF文档，但由于某些原因，IRTF流不再使用它。文档可能会在稍后恢复，可能是在另一个流中。
o Editor Needed -- The document has lost its editor but it still intended to be the output of an RG.
o 需要编辑器--文档已丢失其编辑器，但仍打算作为RG的输出。
o Shepherd Needed -- The document needs a shepherd assigned to it.
o Shepherd Needed--文档需要指定一个Shepherd。
o Waiting for Dependency on Other Document -- Activity on this document is expected to be low or non-existent while waiting for another document (probably listed in the comments) to progress.
o 正在等待对其他文档的依赖关系--在等待另一个文档（可能在注释中列出）进行时，此文档上的活动可能较低或不存在。
o Revised I-D Needed -- Discussion has ensued that is expected to cause changes, and no progress is expected until a new draft is issued.
o 需要修改I-D——随后进行了讨论，预计会引起变化，在新草案发布之前，预计不会有任何进展。
o IESG Review Completed -- The IESG has completed its review on the document, as described in [RFC5742].
o IESG审查已完成——IESG已完成对文件的审查，如[RFC5742]所述。
An RG Chair needs to be able to set the states and annotations for an IRTF document before the RG has sent the document to the IRSG for review. The RG Chair also needs to be able to give the same ability to a shepherd that is assigned by the RG chair. This access control is similar to the access control that is specified in [RFC6175] for IETF WG chairs and their document shepherds.
在RG将文件发送给IRSG审查之前，RG主席需要能够设置IRTF文件的状态和注释。RG主席还需要能够给予RG主席指定的牧羊人相同的能力。该访问控制类似于[RFC6175]中为IETF工作组主席及其文档管理员规定的访问控制。
The RG chairs should be able to modify the state and annotations for any of that RG's documents at any time. The IRTF Chair should be able to modify the state and annotations for any IRTF Stream document at any time.
RG主席应能够随时修改RG文档的状态和注释。IRTF主席应该能够随时修改任何IRTF流文档的状态和注释。
RG chairs and document shepherds may change at any point in a document's life cycle. The Datatracker must allow for and log these changes.
RG主席和文档管理员可能会在文档生命周期的任何时候发生变化。Datatracker必须允许并记录这些更改。
This section describes the desired states and annotations for the Independent Submission stream. The ISE will do his or her own record-keeping for data not related to states and annotations.
本节描述独立提交流所需的状态和注释。ISE将自行记录与状态和注释无关的数据。
Many documents in the Independent Submission stream come from the other three streams. Because of this, the tracker needs to preserve previous states and annotations on drafts that come to the Independent Submission stream.
独立提交流中的许多文档来自其他三个流。因此，跟踪器需要在提交到独立提交流的草稿上保留以前的状态和注释。
o Submission Received -- The draft has been sent to the ISE with a request for publication.
o 已收到提交文件——草案已发送至ISE，并请求发布。
o Finding Reviewers -- The ISE is finding initial reviewers for the document.
o 查找审阅者——ISE正在查找文档的初始审阅者。
o In ISE Review -- The ISE is actively working on the document.
o 在ISE审查中——ISE正在积极处理文件。
o Response to Review Needed -- One or more reviews have been sent to the author(s), and the ISE is awaiting response.
o 需要回复评论——一个或多个评论已发送给作者，ISE正在等待回复。
o In IESG Review -- The ISE has asked the IESG to do a review on the document, as described in [RFC5742].
o 在IESG审查中——ISE已要求IESG对文件进行审查，如[RFC5742]所述。
o Sent to the RFC Editor -- The ISE processing of this document is complete and it has been sent to the RFC Editor for publication. The document may be in the RFC Editor's queue, or it may have been published as an RFC; this state doesn't distinguish between different states occurring after the document has left the ISE.
o 发送到RFC编辑器--此文档的ISE处理已完成，并已发送到RFC编辑器以供发布。文档可能在RFC编辑器的队列中，也可能已作为RFC发布；此状态不区分文档离开ISE后发生的不同状态。
o No Longer In Independent Submission Stream -- This document was actively considered in the Independent Submission stream, but the ISE chose not to publish it. It is possible that the document might be revived later. A document in this state may have a comment explaining the reasoning of the ISE (such as if the document was going to move to a different stream).
o 不再在独立提交流中——该文档在独立提交流中得到了积极考虑，但ISE选择不发布它。该文件可能会在以后恢复。处于这种状态的文档可能会有一条注释，解释ISE的推理（例如文档是否将移动到其他流）。
o Document on Hold Based on IESG Request -- The IESG has requested that the document be held pending further review, as specified in RFC 5742, and the ISE has agreed to such a hold.
o 基于IESG请求的搁置文件——根据RFC 5742的规定，IESG已请求搁置该文件以等待进一步审查，且ISE已同意此类搁置。
o Waiting for Dependency on Other Document -- Activity on this document is expected to be low or non-existent while waiting for another document (probably listed in the comments) to progress. The other documents may or may not be in the Independent Submission stream.
o 正在等待对其他文档的依赖关系--在等待另一个文档（可能在注释中列出）进行时，此文档上的活动可能较低或不存在。其他文件可能在独立提交流中，也可能不在其中。
o Awaiting Reviews -- Activity on this document is expected to be low or non-existent while waiting for reviews that were solicited by the ISE.
o 等待审查——在等待ISE征求的审查时，本文件上的活动预计较少或不存在。
o Revised I-D Needed -- Requests for revisions have been sent to the author(s), and no further ISE processing is expected until a new draft is issued.
o 需要修订I-D——修订请求已发送给作者，在发布新草案之前，预计不会进行进一步的ISE处理。
o IESG Review Completed -- The IESG has completed its review on the document, as described in [RFC5742].
o IESG审查已完成——IESG已完成对文件的审查，如[RFC5742]所述。
When the Datatracker displays the metadata for an individual draft in the IAB stream, IRTF stream, or ISE stream, it should show at least the following information:
当Datatracker在IAB流、IRTF流或ISE流中显示单个草稿的元数据时，它应至少显示以下信息：
Document stream: IAB / IRTF / Independent Submission
I-D availability status: Active / Expired / Withdrawn / RFC
Replaces / Replaced I-D or RFC
(if applicable)
Last updated: year-mm-dd (e.g. 2010-07-25)
IRTF RG status: * Applicable RG state *and* name of
RG (or RGs)
Intended RFC status: Informational / Experimental / etc.
Document shepherd: ** Name of Document Shepherd (if assigned)
Approval status: Name of applicable state from the IAB /
IRTF / Independent Submission stream
Document stream: IAB / IRTF / Independent Submission
I-D availability status: Active / Expired / Withdrawn / RFC
Replaces / Replaced I-D or RFC
(if applicable)
Last updated: year-mm-dd (e.g. 2010-07-25)
IRTF RG status: * Applicable RG state *and* name of
RG (or RGs)
Intended RFC status: Informational / Experimental / etc.
Document shepherd: ** Name of Document Shepherd (if assigned)
Approval status: Name of applicable state from the IAB /
IRTF / Independent Submission stream
* The "IRTF RG status" is only shown for the IRTF stream; it is to be completely removed for the IAB and Independent Stream
* “IRTF RG状态”仅针对IRTF流显示；对于IAB和独立流，应将其完全移除
** This field displays the name and email of the person assigned as the shepherd for the I-D; the line is omitted if the shepherd has not yet been assigned
**此字段显示被指定为身份证监护人的人员的姓名和电子邮件；如果尚未指定牧羊人，则省略该行
Internet-Drafts sometimes move between streams. For example, a draft might start out in the IETF stream but then move to the Independent Submission stream, or a draft might move from an IRTF RG to the IETF stream. Thus, the IETF Datatracker needs to be able to change the designated stream of a draft. It is expected that this will be done by the stream managers. In addition, the IETF Datatracker should preserve all data from the earlier stream(s) when a document moves between streams.
Internet草稿有时在流之间移动。例如，草案可能从IETF流开始，但随后移动到独立提交流，或者草案可能从IRTF RG移动到IETF流。因此，IETF数据跟踪器需要能够更改草稿的指定流。预计这将由流管理器完成。此外，当文档在流之间移动时，IETF Datatracker应保留来自早期流的所有数据。
Internet-Drafts sometimes move out of a stream into a non-stream state. For example, a draft that is in the "Candidate IAB Document", "Candidate RG Document", or "Submission Received" state might not be adopted by the stream and revert back to having no stream-specific state. The IETF Datatracker needs to be able to handle the transition from having a stream-related state to a null state.
Internet草稿有时会从流中移出，进入非流状态。例如，处于“候选IAB文档”、“候选RG文档”或“提交已接收”状态的草稿可能不会被流采用，并恢复为没有流特定状态。IETF数据跟踪器需要能够处理从流相关状态到空状态的转换。
New streams may be added in the future, and the tool needs to be able to handle additional streams.
将来可能会添加新的流，并且该工具需要能够处理其他流。
After the IESG performs a review of potential RFCs from the IRTF and Independent streams, as described in RFC 5742, the IETF Datatracker sends out email to the IANA, the IESG, ietf-announce@ietf.org, and the stream manager with the results of the IESG's review. In the past, the subject line and body of that message has been misleading about the scope and purpose of the message. There is now a requirement that the message clearly state that the message is about the IETF-conflict review of a particular Internet-Draft.
如RFC 5742所述，IESG对来自IRTF和独立流的潜在RFC进行审查后，IETF数据跟踪器向IANA、IESG、IETF发送电子邮件-announce@ietf.org，并向流管理器提供IESG审查的结果。过去，该信息的主题行和主体对信息的范围和目的具有误导性。现在有一项要求，即该信息应明确说明该信息与IETF对特定互联网草案的冲突审查有关。
Note that these letters have effects on the state machine for the IESG, although those effects are not covered in this document.
请注意，这些字母对IESG的状态机有影响，尽管这些影响未在本文档中涵盖。
Changing the states in the Datatracker does not affect the security of the Internet in any significant fashion.
更改Datatracker中的状态不会以任何显著方式影响Internet的安全性。
The IAB has reviewed this document and agrees that this document meets the IAB's consent requirements.
IAB已审查该文件，并同意该文件符合IAB的同意要求。
The IRTF Chair has reviewed this document and agrees that this document meets the requirements for the IRTF stream.
IRTF主席已审查了本文件，并同意本文件符合IRTF流的要求。
The ISE has reviewed this document and agrees that this document meets the requirements of the technical community, as represented by the Independent Submission stream.
ISE已审查了本文件，并同意本文件符合独立提交流所代表的技术团体的要求。
This document draws heavily on, including wholesale copying from, earlier work done by Henrik Levkowetz, Phil Roberts, and Aaron Falk. Additional significant input has been received from Aaron Falk, Nevil Brownlee, Olaf Kolkman, Ross Callon, Ed Juskevicius, Subramanian SM Moonesamy, and Alfred Hoenes.
本文件大量借鉴了Henrik Levkowetz、Phil Roberts和Aaron Falk的早期作品，包括大量抄袭。从亚伦·福克、内维尔·布朗利、奥拉夫·科尔克曼、罗斯·卡隆、埃德·朱斯基维修斯、苏伯拉曼尼亚的SM·穆内萨米和阿尔弗雷德·霍恩斯那里收到了其他重要的投入。
[RFC4844] Daigle, L., Ed., and Internet Architecture Board, "The RFC Series and RFC Editor", RFC 4844, July 2007.
[RFC4844]Daigle，L.，Ed.，和互联网架构委员会，“RFC系列和RFC编辑器”，RFC 48442007年7月。
[RFC5742] Alvestrand, H. and R. Housley, "IESG Procedures for Handling of Independent and IRTF Stream Submissions", BCP 92, RFC 5742, December 2009.
[RFC5742]Alvestrand，H.和R.Housley，“IESG处理独立和IRTF流提交的程序”，BCP 92，RFC 5742，2009年12月。
[RFC6174] Juskevicius, E., "Definition of IETF Working Group Document States", RFC 6174, March 2011.
[RFC6174]Juskevicius，E.“IETF工作组文件状态的定义”，RFC 61742011年3月。
[RFC6175] Juskevicius, E., "Requirements to Extend the Datatracker for IETF Working Group Chairs and Authors", RFC 6175, March 2011.
[RFC6175]Juskevicius，E.“IETF工作组主席和作者扩展数据跟踪器的要求”，RFC 61752011年3月。
Author's Address
作者地址
Paul Hoffman VPN Consortium
保罗·霍夫曼VPN联盟
EMail: paul.hoffman@vpnc.org
EMail: paul.hoffman@vpnc.org