Internet Engineering Task Force (IETF) E. Juskevicius
Request for Comments: 6175 TrekAhead
Category: Informational March 2011
ISSN: 2070-1721
Internet Engineering Task Force (IETF) E. Juskevicius
Request for Comments: 6175 TrekAhead
Category: Informational March 2011
ISSN: 2070-1721
Requirements to Extend the Datatracker for IETF Working Group Chairs and Authors
IETF工作组主席和作者的数据跟踪器扩展要求
Abstract
摘要
This document specifies requirements for new functionality to be added to the IETF Datatracker tool to make it possible for Working Group (WG) Chairs and their Delegates to input and update the status of the Internet-Drafts (I-Ds) associated with their WGs. After these requirements are implemented, WG Chairs will be able to use the Datatracker to provide everyone with more information about the status and progression of WG I-Ds than is currently possible.
本文件规定了添加到IETF数据跟踪器工具的新功能的要求，以使工作组（WG）主席及其代表能够输入和更新与其工作组相关的互联网草案（I-D）的状态。实施这些要求后，工作组主席将能够使用数据跟踪器向每个人提供更多关于工作组I-D状态和进展的信息，而不是目前可能的信息。
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/rfc6175.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6175.
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许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. Conventions Used in This Document ...............................3
3. General Requirements ............................................4
4. Privilege and Access Control Requirements .......................6
4.1. For Everyone ...............................................6
4.2. For IETF Working Group Chairs ..............................6
4.3. For Delegates of IETF WG Chairs ............................8
4.4. For IETF WG Document Shepherds .............................8
4.5. For the Responsible Area Director ..........................9
4.6. Role of the IETF Secretariat in Granting Permissions .......9
5. Inputting and Updating WG Document Status Information ..........10
5.1. WG I-D States .............................................10
5.2. WG I-D Status Annotation Tags .............................10
5.3. WG I-D Protocol Writeups ..................................11
6. Special Requirements for Some WG I-D States and Conditions .....12
6.1. Call for Adoption by WG Issued ............................12
6.2. Adopted by a WG ...........................................14
6.3. WG Document ...............................................14
6.4. Parked WG Document ........................................16
6.5. Dead WG Document ..........................................16
6.6. In WG Last Call ...........................................16
6.7. WG Consensus: Waiting for Writeup .........................17
6.8. Submitted to IESG for Publication .........................18
6.9. Revised I-D Needed (Annotation Tag) .......................18
7. Automatic State Changes for I-Ds ...............................19
8. WG I-D Status Change Reporting Requirements ....................19
9. WG I-D Status Reporting Requirements ...........................20
10. Error Handling Requirements ...................................21
11. Security Considerations .......................................21
12. References ....................................................21
13. Acknowledgments ...............................................22
1. Introduction ....................................................3
2. Conventions Used in This Document ...............................3
3. General Requirements ............................................4
4. Privilege and Access Control Requirements .......................6
4.1. For Everyone ...............................................6
4.2. For IETF Working Group Chairs ..............................6
4.3. For Delegates of IETF WG Chairs ............................8
4.4. For IETF WG Document Shepherds .............................8
4.5. For the Responsible Area Director ..........................9
4.6. Role of the IETF Secretariat in Granting Permissions .......9
5. Inputting and Updating WG Document Status Information ..........10
5.1. WG I-D States .............................................10
5.2. WG I-D Status Annotation Tags .............................10
5.3. WG I-D Protocol Writeups ..................................11
6. Special Requirements for Some WG I-D States and Conditions .....12
6.1. Call for Adoption by WG Issued ............................12
6.2. Adopted by a WG ...........................................14
6.3. WG Document ...............................................14
6.4. Parked WG Document ........................................16
6.5. Dead WG Document ..........................................16
6.6. In WG Last Call ...........................................16
6.7. WG Consensus: Waiting for Writeup .........................17
6.8. Submitted to IESG for Publication .........................18
6.9. Revised I-D Needed (Annotation Tag) .......................18
7. Automatic State Changes for I-Ds ...............................19
8. WG I-D Status Change Reporting Requirements ....................19
9. WG I-D Status Reporting Requirements ...........................20
10. Error Handling Requirements ...................................21
11. Security Considerations .......................................21
12. References ....................................................21
13. Acknowledgments ...............................................22
The IETF Datatracker is a web-based system for managing information about Internet-Drafts (I-Ds) and RFCs, IPR disclosures, liaison statements, and several other important aspects of the IETF process [IDTRACKER].
IETF数据跟踪器是一个基于网络的系统，用于管理有关互联网草稿（I-D）和RFC、知识产权披露、联络声明以及IETF过程的其他几个重要方面的信息[IDTRACKER]。
The Datatracker can track and report on the status of every I-D that has been submitted to the IESG for evaluation and publication. In contrast, the tool currently has almost no ability to track the status of I-Ds that have not been submitted to the IESG. [RFC6174]
Datatracker可以跟踪并报告已提交给IESG进行评估和发布的每个I-D的状态。相比之下，该工具目前几乎没有能力跟踪尚未提交给IESG的I-D的状态。[RFC6174]
Document authors and others have asked for more visibility into the status and progression of IETF Working Group (WG) drafts.
文件作者和其他人要求更多地了解IETF工作组（WG）草案的状态和进展。
This document specifies requirements to extend the Datatracker to enable status tracking and reporting for WG I-Ds. After these requirements are implemented, WG Chairs will be able to use the Datatracker to provide everyone with more information about the WG status of the I-Ds associated with their WGs than is currently possible.
本文件规定了扩展Datatracker以实现工作组I-Ds状态跟踪和报告的要求。实施这些要求后，工作组主席将能够使用数据跟踪器向每个人提供与其工作组相关的I-D工作组状态的更多信息，而不是当前可能的信息。
The terms "WG I-D", "WG document", and "WG draft" are used synonymously throughout this document. The same is true for the plural case of each term.
术语“工作组I-D”、“工作组文件”和“工作组草案”在本文件中同义使用。每个术语的复数情况也是如此。
A "WG draft" is an I-D that has achieved consensus for adoption as a work item by a WG (compared to an individual submission I-D that has not, or has not yet, achieved consensus).
“工作组草案”是指工作组已达成一致意见作为工作项目通过的I-D（与尚未达成一致意见的个人提交I-D相比）。
The terms "WG document" and "WG draft" are not intended to apply to any other document that may be reviewed, discussed, or produced by an IETF Working Group. WG meeting materials such as Blue Sheets, agendas, jabber logs, scribe's notes, minutes, and presentation slides are not to be considered "WG documents" or "WG drafts" in the context of this document.
术语“工作组文件”和“工作组草案”不适用于IETF工作组可能审查、讨论或编制的任何其他文件。工作组会议材料，如蓝纸、议程、叽叽喳喳的日志、抄写员的笔记、会议纪要和演示幻灯片，在本文件中不被视为“工作组文件”或“工作组草稿”。
The phrase "WG status of an I-D" refers to the WG state that an I-D is in per the definitions in Section 4.2 of [RFC6174]. This phrase does not refer to an I-D's availability status (e.g., "Expired", "Active", "Replaced by") as described in Section 3.1 of [RFC6174], or to any of the IESG states used by IETF Area Directors (ADs) to describe the status of I-Ds they may be evaluating. Note that this phrase encompasses all of the states that a WG I-D may be in, plus one more (viz. "Call for Adoption by WG Issued").
短语“工作组身份证状态”是指根据[RFC6174]第4.2节中的定义，工作组身份证所处的工作组状态。该短语不指[RFC6174]第3.1节所述的I-D可用性状态（例如，“过期”、“活动”、“替换为”），也不指IETF区域主管（ADs）用于描述其可能评估的I-D状态的任何IESG状态。请注意，该短语包括工作组识别号可能所在的所有国家，再加上一个国家（即“工作组发出的采纳呼吁”）。
The phrase "I-D associated with a WG" is intended to describe two types of Internet-Drafts:
短语“与工作组相关的I-D”旨在描述两种类型的互联网草案：
- I-Ds that have been accepted as WG drafts; and
- 已被接受为工作组草案的I-D；和
- I-Ds that are being considered under the guidance of a WG Chair for adoption by a WG.
- 在工作组主席的指导下审议的I-D，供工作组采纳。
An I-D having a filename that contains the string 'draft-ietf-' followed by a WG acronym is almost always a WG draft and is to be interpreted as being an "I-D associated with a WG" for the purposes of this document.
文件名中包含字符串“draft ietf-”和工作组首字母缩写词的I-D几乎总是工作组草案，在本文件中应解释为“与工作组相关的I-D”。
An I-D having a filename that includes the author's name and a WG acronym but does not include the string '-ietf-' may be a candidate for adoption by a WG and, if so, is also to be interpreted as being an "I-D associated with a WG" for the purposes of this document.
文件名包含作者姓名和工作组首字母缩略词但不包含字符串“-ietf-”的I-D可能是工作组采用的候选文件，如果是，也应解释为本文件中的“与工作组相关的I-D”。
The requirements specified in this document use English phrases ending with "(R-nnn)", where "nnn" is a unique requirement number.
本文件中规定的要求使用以“（R-nnn）”结尾的英语短语，其中“nnn”是唯一的要求编号。
When used in the context of the requirements in this document, the key words "MUST", "MUST NOT", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", and "MAY" are to be interpreted as described in RFC 2119 [RFC2119]. RFC 2119 defines the use of these key words to help make the intent of standards track documents as clear as possible. The same key words are used in this document to make the meaning of the requirements specified herein as clear as possible.
当在本文件要求的上下文中使用时，关键词“必须”、“不得”、“应”、“不应”、“应”、“不应”和“可”应按照RFC 2119[RFC2119]中的说明进行解释。RFC 2119定义了这些关键词的使用，以帮助尽可能明确标准跟踪文档的意图。本文件中使用了相同的关键词，以尽可能明确本文件规定要求的含义。
The enhancements to be made to the Datatracker described in this document MUST be implemented in a manner that provides WG Chairs and the people they designate to act as their Delegates with the option to input and update the WG status of some, all, or none of the I-Ds associated with their WGs using the WG I-D states and I-D status annotation tags defined in [RFC6174] (R-001). In other words, the implementation must not require that WG Chairs change their way of working, but only provide optional features. WG Chairs must have the flexibility to use the enhancements to the Datatracker to track the WG status of their I-Ds as is most appropriate for them.
本文件中所述的数据跟踪器的增强必须以一种方式实施，即工作组主席及其指定作为其代表的人员可以选择输入和更新部分、所有工作组成员的工作组状态，或者使用[RFC6174]（R-001）中定义的工作组I-D状态和I-D状态注释标记，没有与其工作组关联的I-D。换句话说，实现不能要求工作组主席改变工作方式，而只能提供可选功能。工作组主席必须能够灵活地使用Datatracker的增强功能来跟踪其I-D的工作组状态，这对他们来说是最合适的。
To ensure that at least some WG status information is tracked for every I-D associated with a WG, the Datatracker must be enhanced to generate a few automatic state transitions for every WG I-D. The requirements for this feature are specified in Section 7 of this document.
为确保与工作组相关的每个I-D至少跟踪一些工作组状态信息，必须增强Datatracker，以便为每个工作组I-D生成几个自动状态转换。本文件第7节规定了此功能的要求。
Requirement R-001 SHALL NOT impair the ability of the Datatracker to track and display the availability state of any I-D (R-002). I-D availability states (e.g., "Active", "Expired", "Replaces") are described in Section 3.1 of [RFC6174].
要求R-001不得损害数据跟踪器跟踪和显示任何I-D（R-002）可用状态的能力。[RFC6174]第3.1节描述了I-D可用性状态（例如，“活动”、“过期”、“替换”）。
The Datatracker SHALL NOT permit users other than a Working Group's Chairs (e.g., the Chairs of a different IETF WG) to update the WG status of a WG's documents through the regular Datatracker interface, unless the privileges to do so have been explicitly delegated to them by one of the WG's Chairs (R-003).
数据跟踪器不得允许工作组主席以外的用户（例如，不同IETF工作组的主席）通过常规数据跟踪器接口更新工作组文件的工作组状态，除非工作组主席之一（R-003）明确授予他们这样做的特权。
The user interface to be provided by the Datatracker to WG Chairs (and their Delegates) to input the WG status of the I-Ds associated with their WGs SHOULD have a look and feel that is similar to the interface currently used by ADs to identify the status of I-Ds under formal evaluation by the IESG (R-004).
Datatracker向工作组主席（及其代表）提供的用户界面，用于输入与其工作组相关的I-D的工作组状态，其外观应类似于ADs当前使用的界面，用于识别IESG（R-004）正式评估下的I-D状态。
Any new pages created to display the status of WG I-Ds SHOULD be designed to have a look and feel that is similar to the pages currently provided by the Datatracker to display the status of I-Ds under formal evaluation by the IESG (R-005).
为显示工作组I-Ds状态而创建的任何新页面应设计为具有与Datatracker当前提供的页面相似的外观，以显示IESG（R-005）正式评估下的I-Ds状态。
New javascript user interface code and style sheets implemented to satisfy the requirements in this document SHOULD reuse or share existing code where practical so that when a change to the IESG status of an I-D is entered into the Datatracker, the WG status tracking for that I-D can benefit, and vice versa (R-006).
为满足本文档要求而实施的新javascript用户界面代码和样式表应在可行的情况下重用或共享现有代码，以便在将I-D的IESG状态更改输入Datatracker时，该I-D的WG状态跟踪可以受益，反之亦然（R-006）。
The Datatracker MUST date and timestamp every update to the WG status of an I-D that is associated with a WG and be able to use that information when it displays the status change history for the I-D (R-007). The WG status change history for an I-D MUST also identify the person or entity that updated the WG status of the I-D (e.g., one of the WG's Chairs, a Delegate, an AD, the System, the IETF Secretariat) and describe the change (e.g., "WG State changed from 'a' to 'b'", "WG Annotation Tag 'x' Set (or Reset)") (R-008).
Datatracker必须在与工作组相关的I-D的工作组状态的每次更新上注明日期和时间戳，并且能够在显示I-D（R-007）的状态更改历史时使用该信息。ID的工作组状态更改历史还必须确定更新ID工作组状态的个人或实体（例如，工作组主席之一、代表、广告、系统、IETF秘书处）并描述更改（例如，“工作组状态从‘a’更改为‘b’”，“工作组注释标签‘x’集（或重置）”）（R-008）。
The inputting or updating of the WG status of an I-D SHALL NOT overwrite any previously archived status change history information for the I-D; every update to the WG status of an I-D MUST be added to the status change history log for the I-D (R-009).
I-D工作组状态的输入或更新不得覆盖I-D先前存档的任何状态更改历史信息；必须将I-D工作组状态的每次更新添加到I-D（R-009）的状态更改历史记录中。
WG I-D status tracking MUST be implemented per-draft, not per-WG (R-010).
工作组I-D状态跟踪必须按照草案执行，而不是按照工作组（R-010）执行。
WG I-D status tracking SHOULD be implemented as a new front-end to the Datatracker's existing IESG state machine [IESGIDSM] (R-011).
WG I-D状态跟踪应作为Datatracker现有IESG状态机[IESGISM]（R-011）的新前端实施。
The Datatracker SHALL permit authorized users (e.g., WG Chairs, Delegates) to change the WG state of a draft independently from the IESG state of the same I-D and vice versa (R-012).
Datatracker应允许授权用户（如工作组主席、代表）独立于同一I-D的IESG状态更改草案的工作组状态，反之亦然（R-012）。
Everyone needs to be able to view information about the WG status of an I-D without logging on to the Datatracker. Everyone SHALL be given 'read' access to WG I-D status information (R-013).
每个人都需要能够在不登录Datatracker的情况下查看有关I-D工作组状态的信息。每个人都应有权“读取”工作组I-D状态信息（R-013）。
People who need to input, modify or update the WG status of an I-D (e.g., WG Chairs and their Delegates) need 'write' privileges; these users SHALL be required to log-on to the Datatracker using a personal user-id and password (e.g., an IETF tools password) in order to gain 'write' access (R-014).
需要输入、修改或更新ID工作组状态的人员（如工作组主席及其代表）需要“写入”权限；应要求这些用户使用个人用户id和密码（如IETF工具密码）登录数据跟踪器，以获得“写入”访问权（R-014）。
After successfully logging on to the Datatracker as specified in Requirement R-014, WG Chairs:
按照要求R-014的规定成功登录到数据跟踪器后，工作组主席：
- SHALL be given full 'read' and 'write' privileges to input and update the WG status information for all of the I-Ds associated with their WGs (R-015).
- 应获得完整的“读”和“写”权限，以输入和更新与其工作组（R-015）相关的所有I-D的工作组状态信息。
- SHALL be able to able to choose from all of the WG I-D states and WG I-D status annotation tags defined in [RFC6174] to describe the current WG status of the I-Ds associated with their WGs (R-016).
- 应能够从[RFC6174]中定义的所有工作组I-D状态和工作组I-D状态注释标签中进行选择，以描述与其工作组（R-016）相关的I-D的当前工作组状态。
- SHALL NOT be allowed to create new WG I-D states or state names (R-017).
- 不允许创建新的WG I-D状态或状态名称（R-017）。
- SHALL NOT be allowed to update or modify information that is not related to the WG status of an I-D (e.g., IANA status, RFC-Editor status, IESG status) (R-018).
- 不允许更新或修改与ID工作组状态无关的信息（如IANA状态、RFC编辑器状态、IESG状态）（R-018）。
- SHALL be able to designate a maximum of three people to act as their Delegates to input and update the WG status of the I-Ds associated with each of their WGs (R-019). A suitable way to specify a Delegate may be to use the individual's current e-mail address, but the delegation MUST be to the individual identified by the login credentials used by the Datatracker at any given time rather than to an e-mail address (R-020). Individuals must be able to update their e-mail addresses in the future without breaking the delegation specified in Requirement R-019.
- 应能够指定最多三人作为其代表，输入和更新与其每个工作组（R-019）相关的I-D的工作组状态。指定委托的合适方式可能是使用个人的当前电子邮件地址，但委托必须是由Datatracker在任何给定时间使用的登录凭据标识的个人，而不是电子邮件地址（R-020）。个人必须能够在未来更新其电子邮件地址，而不会破坏要求R-019中规定的授权。
- SHALL be able to designate a maximum of three different people to act as their Delegates in a different WG if a WG Chair is also responsible for the different WG (R-021).
- 如果工作组主席也负责不同的工作组（R-021），则应能够指定最多三名不同人员作为其在不同工作组中的代表。
- SHALL be able to designate people who have other roles in the IETF process (e.g., are Chairs of different WGs, are ADs in a different Area) to be their Delegates (R-022).
- 应能够指定在IETF过程中具有其他角色的人员（例如，不同工作组的主席、不同区域的广告）作为其代表（R-022）。
- SHALL be able to review and change their Delegates (R-023).
- 应能够审查和更换其代表（R-023）。
- SHALL be able to input or upload Document Shepherd protocol writeups for all of the I-Ds associated with their WGs (R-024).
- 应能够为与其WGs（R-024）相关的所有I-D输入或上传文件协议书写。
- SHALL be able to designate themselves as the Document Shepherds for some or all of the I-Ds in their WGs (R-025).
- 应能够指定自己为其工作组（R-025）中部分或所有I-D的文件管理员。
- SHALL be able to designate other people to be Document Shepherds for one or more of their WG I-Ds if this role will not be performed by the WG Chairs (R-026). A suitable way to designate people to be the Document Shepherds may be to use their e-mail addresses, but the delegation MUST be to the individuals identified by the login credentials used by the Datatracker at the time, rather than to the e-mail addresses (R-027). The Datatracker MUST be able to maintain an individual's designation as a Delegate per R-026 in the event that the person changes their e-mail address in the future (R-028).
- 如果工作组主席（R-026）不履行该职责，则应能够指定其他人员担任其一个或多个工作组I-D的文件管理员。指定人员担任文档管理员的合适方式可能是使用他们的电子邮件地址，但委托必须是由Datatracker当时使用的登录凭据确定的个人，而不是电子邮件地址（R-027）。数据跟踪器必须能够根据R-026维护个人作为代理人的指定，以防此人将来更改其电子邮件地址（R-028）。
- SHALL be warned in real-time (e.g., via the Datatracker's regular user interface) if a person they try to designate as a Delegate or Document Shepherd does not have the necessary login credentials for the Datatracker (R-029). The Datatracker SHALL then allow the WG Chairs to confirm the original designee or to pick another (R-030).
- 如果试图指定为代表或文件管理员的人员没有数据跟踪器（R-029）所需的登录凭据，则应实时发出警告（例如，通过数据跟踪器的常规用户界面）。数据跟踪器应允许工作组主席确认原始指定人员或选择另一名（R-030）。
- SHALL be able to review and change the people designated to be Document Shepherds for each of their WG I-Ds (R-031).
- 应能够审查和更改每个工作组I-D（R-031）指定为文件管理员的人员。
- SHOULD be able to access the same user interfaces the Datatracker provides to their Delegates and Document Shepherds in order to mentor or coach them on how to input and update WG I-D status information in the Datatracker (R-032).
- 应能够访问Datatracker向其代表和文档管理员提供的相同用户界面，以便指导或指导他们如何在Datatracker（R-032）中输入和更新工作组I-D状态信息。
After successfully logging on to the Datatracker, the Delegates of WG Chairs (e.g., WG Secretaries) SHALL have the same privileges as their WG Chairs to input WG I-D status information and Document Shepherd protocol writeups as specified in Requirements R-015 to R-018 inclusive, R-024, and R-025 (R-033).
成功登录到数据跟踪器后，工作组主席的代表（如工作组秘书）应具有与其工作组主席相同的权限，以输入工作组I-D状态信息和R-015至R-018、R-024和R-025（R-033）中规定的文件管理协议。
The Datatracker SHALL send an e-mail to the Chairs of the WG, the IETF Secretariat, and to a newly designated Delegate if the newly designated Delegate does not have a personal user-id and password to log-on to the Datatracker (R-034). The purpose of the e-mail is to notify the WG Chairs that the person they designated to be a Delegate needs to take action to obtain a personal user-id and password, and to inform the Delegate that he/she needs to take action (e.g., to contact the IETF Secretariat) to obtain their own user-id and password for the Datatracker.
如果新指定的代表没有登录数据跟踪器（R-034）的个人用户id和密码，则数据跟踪器应向工作组主席、IETF秘书处和新指定的代表发送电子邮件。电子邮件的目的是通知工作组主席，他们指定为代表的人员需要采取行动获取个人用户id和密码，并通知代表他/她需要采取行动（例如联系IETF秘书处）获取他们自己的数据跟踪器用户id和密码。
The IETF document shepherding process and the role of an IETF WG Document Shepherd is described in RFC 4858 [RFC4858].
RFC 4858[RFC4858]中描述了IETF文件管理过程和IETF工作组文件管理者的角色。
The requirements in this Section describe the access privileges to be granted to a WG Document Shepherd who is not a WG Chair or a Delegate with the privileges specified in Section 4.3.
本节中的要求描述了授予非工作组主席或具有第4.3节规定特权的代表的工作组文件管理员的访问权限。
Per Requirement R-014, each person designated to be a Document Shepherd for a WG draft needs to have their own personal user-id and password to log-on to the Datatracker.
根据要求R-014，每个被指定为工作组草稿文档管理员的人都需要有自己的个人用户id和密码才能登录到Datatracker。
The Datatracker SHALL alert the WG Chairs, the IETF Secretariat, and the newly designated Document Shepherd (e.g., via e-mail) if a person newly designated as a Document Shepherd does not have a personal user-id and password to log-on to the Datatracker (R-035). The purpose of the e-mail is to notify the WG Chairs that the Document Shepherd needs to take action to obtain a personal user-id and password, and to inform the Document Shepherd that he/she needs to take action (e.g., to contact the IETF Secretariat) to obtain a personal user-id and password for the Datatracker.
如果新指定为文件管理员的人员没有登录数据跟踪器（R-035）的个人用户id和密码，则数据跟踪器应通知工作组主席、IETF秘书处和新指定的文件管理员（例如，通过电子邮件）。电子邮件的目的是通知工作组主席，文件管理员需要采取行动获取个人用户id和密码，并通知文件管理员他/她需要采取行动（例如，联系IETF秘书处）获取数据跟踪器的个人用户id和密码。
Document Shepherds need to be able to upload or input protocol writeups into the Datatracker for the WG I-Ds assigned to them. They also need to be able to set and reset the WG I-D status annotation tag called "Doc Shepherd Followup Underway" as defined in Section 4.3.10 of [RFC6174] for I-Ds in the "WG Consensus: Waiting for Writeup" state.
文档管理员需要能够将分配给他们的WG I-D的协议写入上传或输入到Datatracker中。他们还需要能够为处于“工作组共识：等待写入”状态的I-D设置并重置工作组I-D状态注释标签，该标签称为[RFC6174]第4.3.10节中定义的“Doc Shepherd Followup Undering”。
After successfully logging on to the Datatracker, Document Shepherds SHALL have restricted 'write' privileges to upload or input protocol writeups for the WG I-Ds assigned to them when the I-Ds are in the "WG Consensus: Waiting for Writeup" state (R-036).
成功登录到Datatracker后，当文件管理员处于“工作组共识：等待写入”状态（R-036）时，文件管理员应具有有限的“写入”权限，以上载或输入分配给他们的工作组I-Ds的协议写入。
Document Shepherds SHALL also have the ability to set and reset the WG I-D status annotation tag called "Doc Shepherd Followup Underway" as defined in Section 4.3.10 of [RFC6174] (R-037).
文件管理员还应能够按照[RFC6174]（R-037）第4.3.10节的规定，设置和重置工作组I-D状态注释标签，称为“正在进行的文件管理员后续行动”。
The "Doc Shepherd Followup Underway" annotation tag should be set to indicate when the Document Shepherd has started work on a writeup for the document. The absence or resetting of this annotation tag may indicate the protocol writeup has not yet been started, or has been put on-hold for some reason, or has been completed. The log of set and reset operations performed on this annotation tag will provide insight into the status of the protocol writeup for a WG I-D.
“Doc Shepherd Followup Undering”注释标记应设置为指示文档Shepherd何时开始编写文档。缺少或重置此注释标记可能表示协议writeup尚未启动，或由于某种原因被搁置，或已完成。在此注释标记上执行的设置和重置操作日志将提供对WG I-D协议写入状态的深入了解。
Section 5.3 describes how Document Shepherds may input or upload protocol writeups to the Datatracker for the WG I-Ds assigned to them.
第5.3节描述了文件管理员如何为分配给他们的工作组I-D向数据跟踪器输入或上传协议写入。
After successfully logging on to the Datatracker, an AD SHALL have the same privileges as a WG Chair to input and update WG I-D status information, to designate Delegates and Document Shepherds (R-038). An AD SHALL have the privileges specified in Requirement R-038 for every WG in his or her Area (R-039). ADs MUST also retain their existing privileges to input and update the IESG status of the I-Ds for which they are responsible (R-040).
成功登录数据跟踪器后，AD应具有与工作组主席相同的权限，以输入和更新工作组I-D状态信息，指定代表和文件管理员（R-038）。AD应具有R-038要求中规定的对其所在区域（R-039）内每个工作组的特权。ADs还必须保留其现有权限，以输入和更新其负责的I-D（R-040）的IESG状态。
To minimize confusion, the Datatracker MUST make it easy for ADs to distinguish between their IESG-level privileges (to input or update the IESG status of an I-D) and the WG-level privileges they will obtain as a result of R-038 and R-039 for I-Ds associated with the WGs for which they are responsible (R-041).
为了最大限度地减少混淆，Datatracker必须使ADs易于区分其IESG级权限（输入或更新I-D的IESG状态）和工作组级权限，因为R-038和R-039与其负责的工作组（R-041）相关的I-D将获得工作组级权限。
The IETF Secretariat is involved in granting permissions to people who need to log in to the Datatracker.
IETF秘书处参与向需要登录Datatracker的人员授予权限。
Before granting permissions to update WG I-D status settings to a person who does not have them, the IETF Secretariat should verify that the person requesting the permissions is a WG Chair or an AD, or has been delegated the authority to update WG I-D status information by one of the WG's Chairs or a Responsible AD. The e-mails to be generated and sent by the Datatracker per Requirements R-034 and
在向没有权限的人员授予更新工作组I-D状态设置的权限之前，IETF秘书处应验证请求权限的人员是否为工作组主席或AD，或已被工作组主席或负责广告授权更新工作组I-D状态信息。数据跟踪器根据要求R-034和
R-035 will alert the Secretariat that the granting of permissions to some new people will be needed.
R-035将提醒秘书处，需要向一些新人授予许可。
Requirements R-001, R-016, and R017 specify that the WG state of an I-D may only be described using the states defined in Section 4 of [RFC6174].
要求R-001、R-016和R017规定，I-D的WG状态只能使用[RFC6174]第4节中定义的状态进行描述。
When a WG Chair or Delegate logs on to the Datatracker to input or change the WG state of an I-D, the Datatracker SHOULD display the current state of the I-D, the length of time the document has been in its current state, the amount of time the I-D may continue to remain in its current state if this information is available (viz. per Requirements R-064 and R-083), and the most likely next WG state (or states) for the I-D (R-042). The Datatracker MAY use the WG I-D state machine illustrated in Section 4.1 of [RFC6174] to identify the 'most likely next state' (or states) for an I-D that is associated with a WG (R-043).
当工作组主席或代表登录数据跟踪器以输入或更改ID的工作组状态时，数据跟踪器应显示ID的当前状态、文档处于当前状态的时间长度、如果该信息可用，I-D可能继续保持当前状态的时间量（即，根据要求R-064和R-083），以及I-D（R-042）最可能的下一个工作组状态。数据跟踪器可使用[RFC6174]第4.1节所示的工作组I-D状态机来识别与工作组（R-043）相关的I-D的“最可能的下一个状态”（或多个状态）。
After displaying the information required by R-042, the Datatracker SHALL make it easy for the WG Chair or Delegate to select a next state for the I-D and to enter some text to explain the state change for the I-D's status change history (R-044). The Datatracker SHALL encourage the person who updates or changes the WG state of an I-D to provide some context for the status change by entering text to describe the change in the I-D's status change history log (R-045).
在显示R-042要求的信息后，数据跟踪器应使工作组主席或代表能够方便地选择I-D的下一个状态，并输入一些文本来解释I-D状态变化历史（R-044）的状态变化。数据跟踪器应鼓励更新或更改I-D工作组状态的人员通过在I-D状态更改历史记录（R-045）中输入描述更改的文本，为状态更改提供一些上下文。
The Datatracker SHALL allow a WG Chair (or Delegate) to select the next state for an I-D from the 'most likely' next states described by Requirement R-043, or from any of the other WG I-D states (per Requirement R-016) if a different state change is required (R-046).
数据跟踪器应允许工作组主席（或代表）从要求R-043中描述的“最有可能的”下一个状态中选择I-D的下一个状态，或者如果需要不同的状态更改（R-046），则从任何其他工作组I-D状态（根据要求R-016）中选择I-D的下一个状态。
WG I-D status annotation tags may be used to describe a condition that is affecting a document (e.g., why a WG I-D is in the state it is in) or to indicate an action needed to progress the document; however, annotation tags do not change the state of WG I-Ds.
WG I-D状态注释标签可用于描述影响文档的条件（例如，WG I-D处于其所处状态的原因）或指示文档进展所需的操作；但是，注释标记不会更改WG I-Ds的状态。
Section 4.3 of [RFC6174] defines the meaning and usage of the WG I-D status annotation tags to be added to the Datatracker.
[RFC6174]第4.3节定义了要添加到数据跟踪器的工作组I-D状态注释标签的含义和用法。
The Datatracker SHALL allow WG Chairs and their Delegates to set and reset each of the WG I-D status annotation tags defined in Section 4.3 of [RFC6174] for every I-D associated with their WGs (R-047).
数据跟踪器应允许工作组主席及其代表为与其工作组（R-047）相关的每个I-D设置并重置[RFC6174]第4.3节中定义的每个工作组I-D状态注释标签。
WG I-D status annotation tags SHALL be able to be used individually or in combination with other annotation tags to describe the status of any I-D associated with a WG (R-048).
WG I-D状态注释标签应能够单独使用或与其他注释标签结合使用，以描述与WG（R-048）相关的任何I-D状态。
When a WG Chair, Delegate, or Document Shepherd logs in to the Datatracker to set or reset one or more WG I-D status annotation tags for the I-Ds they are responsible for, the Datatracker SHOULD display a summary of all annotation tag set/reset operations to date for those WG I-Ds, from the present time backwards, split by pages, and then guide the user to select one (or more) annotation tags to be set or reset (R-049). Note that Document Shepherds who are not WG Chairs may only set and reset the annotation tag called "Doc Shepherd Followup Underway" per Requirement R-037.
当工作组主席、代表或文件管理员登录到数据跟踪器，为其负责的I-D设置或重置一个或多个工作组I-D状态注释标记时，数据跟踪器应显示这些工作组I-D迄今为止所有注释标记设置/重置操作的摘要，从当前向后，按页拆分，然后引导用户选择一个（或多个）要设置或重置的注释标记（R-049）。请注意，根据要求R-037，非工作组主席的文件管理员只能设置和重置名为“文件管理员后续行动”的注释标签。
The summary of annotation tag set/reset operations (required by R-049) SHALL also indicate when each annotation tag attached to the current state of each I-D was set or reset and the identity of the person or entity that set or reset each I-D status annotation tag (R-050).
注释标签设置/重置操作摘要（R-049要求）还应说明每个I-D当前状态的每个注释标签何时设置或重置，以及设置或重置每个I-D状态注释标签（R-050）的个人或实体的身份。
The Datatracker SHALL allow more than one annotation tag to be set or reset per logon, and the Datatracker SHALL encourage the user to input some text to explain why each annotation tag is being set or reset (R-051).
数据跟踪器应允许每次登录设置或重置多个注释标签，并且数据跟踪器应鼓励用户输入一些文本，以解释设置或重置每个注释标签的原因（R-051）。
The IESG currently requires a protocol writeup for every WG I-D before the I-D is submitted to the IESG for evaluation.
IESG目前要求在将I-D提交给IESG进行评估之前，为每个工作组I-D编写一份协议。
When a user (e.g., WG Chair, Document Shepherd) logs in to the Datatracker to input or upload a protocol writeup for an I-D, the Datatracker SHOULD make it easy for the user to understand the current status of the protocol writeup for every I-D for which he/she is responsible (R-052). The Datatracker SHOULD indicate at least the date when the most recent protocol writeup was uploaded or inputted for each I-D and the identity of the person or entity that performed the upload or input operation (R-053).
当用户（例如，工作组主席、文档管理员）登录到数据跟踪器以输入或上传I-D的协议写入时，数据跟踪器应便于用户了解其负责的每个I-D的协议写入的当前状态（R-052）。数据跟踪器应至少指明每个I-D上传或输入最新协议写入的日期，以及执行上传或输入操作的个人或实体的身份（R-053）。
After displaying the information required by R-053, the Datatracker SHALL provide the user with an interface to input or upload a protocol writeup for the I-Ds that he/she is responsible for, and to set or reset the "Doc Shepherd Followup Underway" annotation tag for I-Ds (R-054). The Datatracker SHALL encourage the user to set or reset the "Document Shepherd Followup Underway" annotation tag before the end of each protocol writeup uploading or inputting session and to input some descriptive text (for context) to be stored in I-D's status change history log (R-055).
显示R-053要求的信息后，数据跟踪器应向用户提供一个界面，用于输入或上传他/她负责的I-Ds的协议编写，以及设置或重置I-Ds（R-054）的“Doc Shepherd Followup Undering”注释标签。数据跟踪器应鼓励用户在每个协议写入上传或输入会话结束之前设置或重置“文件管理员后续进行中”注释标签，并输入一些描述性文本（用于上下文）以存储在I-D的状态更改历史记录（R-055）中。
Per Requirement R-100, the Datatracker will send an e-mail to the author of a WG draft (and carbon copy (CC) the WG Chairs and Delegates) when the protocol writeup for the I-D is loaded into the Datatracker. A copy of the e-mail SHALL also be sent to the Document Shepherd if he/she is not the WG Chair (or Delegate) as notification that the protocol writeup for the I-D was successfully loaded into the Datatracker (R-056).
根据要求R-100，当I-D协议书载入数据跟踪器时，数据跟踪器将向工作组草案的作者（以及工作组主席和代表的复写本（CC））发送电子邮件。如果文件管理员不是工作组主席（或代表），也应向其发送一份电子邮件副本，作为I-D协议书已成功加载到数据跟踪器（R-056）的通知。
Recall that WG Chairs and their Delegates shall be able to input a protocol writeup for any of their WG drafts at any time per Requirements R-024 and R-033.
回想一下，工作组主席及其代表应能够根据要求R-024和R-033随时为其工作组草案输入协议书。
If a Document Shepherd who is not a WG Chair or other Delegate attempts to upload or input a protocol writeup for an I-D that is not in the WG state called "WG Consensus: Waiting for Writeup", the Datatracker SHOULD warn the Document Shepherd that it may be too early to input a writeup, and then direct the Document Shepherd to contact one of the WG's Chairs for guidance (R-057). The WG Chair may decide to move the I-D into the "WG Consensus: Waiting for Writeup" state to enable the Document Shepherd to upload his/her protocol writeup, or the WG Chair may upload the protocol writeup as specified in Requirement R-024.
如果不是工作组主席或其他代表的文件管理员试图上传或输入不在工作组状态的I-D的协议写入，称为“工作组共识：等待写入”，数据跟踪器应警告文件管理员，输入写入可能为时尚早，然后指示文件管理员联系工作组的一位主席寻求指导（R-057）。工作组主席可决定将ID移至“工作组共识：等待编写”状态，以使文件管理员能够上传其协议编写，或者工作组主席可按照要求R-024的规定上传协议编写。
Requirement R-032 specifies that WG Chairs should be able to access the Document Shepherd user interface and call up a display of the same WG document protocol writeup status information that the Datatracker provides to each of a WG Chair's designated Document Shepherds. This is to enable each WG Chair (or Delegate) to be able to mentor new Document Shepherds and to review the workload assigned to each Document Shepherd. WG Chairs (and their Delegates) who are logged in to the Datatracker with their normal privileges SHALL be able to access the Document Shepherd user interface without having to logout and log back in to the Datatracker (R-058).
要求R-032规定工作组主席应能够访问文件管理员用户界面，并调用数据跟踪器向工作组主席的每个指定文件管理员提供的相同工作组文件协议写入状态信息的显示。这是为了使每个工作组主席（或代表）能够指导新的文件管理员，并审查分配给每个文件管理员的工作量。以正常权限登录数据跟踪器的工作组主席（及其代表）应能够访问文件管理员用户界面，而无需注销并重新登录数据跟踪器（R-058）。
The "Call for Adoption by WG Issued" state may be used to describe a draft that is being considered for adoption by an IETF WG. An I-D in this state has not yet achieved consensus, preference, or selection in a working group.
“工作组发布的采纳要求”状态可用于描述IETF工作组正在考虑采纳的草案。这种状态下的身份证明尚未在工作组中达成共识、偏好或选择。
This state may be used to describe an I-D that someone has asked a WG to consider for adoption if the WG Chair has agreed with the request. This state may also be used to identify an I-D that a WG Chair asked
此状态可用于描述如果WG主席同意请求，某人要求WG考虑采用的I-D。该状态也可用于识别工作组主席询问的身份证
an author to write specifically for consideration as a candidate WG item, and/or an I-D that is listed as a 'candidate draft' in the WG's charter. [RFC6174]
一位作者，专门撰写以作为工作组候选项目考虑，和/或工作组章程中作为“候选草案”列出的身份证明。[RFC6174]
The Datatracker SHALL allow a WG Chair or Delegate to move an I-D into the "Call for Adoption by WG Issued" state in her or his WG if the I-D is not currently being considered for adoption in any other WG, is not yet adopted by any other WG, is not expired, and has not been withdrawn (R-059). An I-D can only be in the "Call for Adoption by WG Issued" state in one WG at a time.
数据跟踪器应允许工作组主席或代表在其工作组中将I-D移至“工作组发布的采纳要求”状态，前提是该I-D目前未被任何其他工作组考虑采纳，未被任何其他工作组采纳，未过期，且未被撤销（R-059）。I-D一次只能在一个工作组中处于“工作组发出的采用呼吁”状态。
The Datatracker SHALL NOT change the WG status of an I-D that is in the "Call for Adoption by WG Issued" state until the I-D expires, until the WG Chair (or Delegate) moves the I-D into a different state, or until it is decided that the WG will not adopt the I-D, whichever comes first (R-060). In case a WG decides not to adopt an I-D that is in the "Call for Adoption by WG Issued" state, the Datatracker SHALL allow the WG Chairs (and Delegates) to cancel their interest in the I-D (R-061).
数据跟踪器不得更改处于“工作组发出的采纳呼吁”状态的工作组身份，直到该身份证到期，直到工作组主席（或代表）将该身份证移至不同的状态，或者直到工作组决定不采纳该身份证，以先到者为准（R-060）。如果工作组决定不采纳处于“工作组发出采纳呼吁”状态的I-D，则数据跟踪器应允许工作组主席（和代表）取消其对I-D（R-061）的兴趣。
The Datatracker SHALL transition the state of an I-D that expires or is not adopted (per Requirement R-061) from the "Call for Adoption by A WG" state into a "NULL" state with respect to the WG state machine and then update the status change history log of the I-D accordingly (R-062). An I-D that is not adopted by a WG may revert back to having no stream-specific state in the Datatracker.
数据跟踪器应将过期或未采用的I-D状态（根据要求R-061）从“工作组采用要求”状态转换为与工作组状态机相关的“空”状态，然后相应地更新I-D的状态更改历史日志（R-062）。工作组未采用的I-D可能会恢复为在Datatracker中没有特定于流的状态。
If a different WG Chair (or Delegate) attempts to move an I-D into the "Call for Adoption by WG Issued" state in while the I-D is associated with another WG, the Datatracker will not allow the attempted state change to occur because of Requirement R-059. In this case, the Datatracker SHALL inform the WG Chair or Delegate in real-time (via the user interface that he/she is logged in to) that the I-D is currently associated with a different WG and that the state change they requested cannot be made at this time (R-063).
如果不同的工作组主席（或代表）试图在将I-D与另一个工作组关联时将I-D移动到“工作组发布的采纳要求”状态，则Datatracker将不允许由于要求R-059而发生尝试的状态更改。在这种情况下，数据跟踪器应实时（通过他/她登录的用户界面）通知工作组主席或代表，I-D当前与不同的工作组关联，此时无法进行他们请求的状态更改（R-063）。
A WG Chair (or Delegate) who moves an I-D into the "Call For Adoption By WG Issued" state SHALL be able to, but is not required to, specify a length of time the I-D may remain in this state (R-064). It SHALL be possible to specify the maximum length of time as a "number of weeks"; however, the maximum length MUST NOT be allowed to extend beyond the expiry date of the I-D (R-065). Other ways to specify this length of time MAY optionally be provided (R-066).
若工作组主席（或代表）将身份证明文件移至“工作组发出的采纳呼吁”状态，则该工作组主席（或代表）应能够（但无需）指定身份证明文件在该状态下的保留时间长度（R-064）。应可将最大时间长度指定为“周数”；但是，最大长度不得超过I-D（R-065）的有效期。可以选择提供指定该时间长度的其他方法（R-066）。
If an I-D is still in the "Call for Adoption by WG Issued" state when the length of time specified in R-064 runs out, the Datatracker SHALL send an e-mail to inform the WG Chairs and Delegates that the time has run out and that the I-D is still in "Call for Adoption by WG
如果在R-064中规定的时间结束时，I-D仍处于“工作组发出的采纳呼吁”状态，则数据跟踪器应发送电子邮件通知工作组主席和代表，时间已结束，且I-D仍处于“工作组采纳呼吁”状态
Issued" state (R-067). The purpose of this message is to remind the WG Chairs and Delegates that they had planned to make a decision on adopting the I-D by now.
发布“状态（R-067）”。此信息的目的是提醒工作组主席和代表，他们计划现在就采用I-D做出决定。
The "Adopted by a WG" state describes an individual submission I-D that an IETF WG has agreed to adopt as one of its WG drafts.
“工作组采纳”状态描述了IETF工作组同意采纳为其工作组草案之一的个人提交I-D。
An individual submission I-D that is adopted by a WG may take weeks or months to be resubmitted by the author as a new (version-00) WG draft.
工作组通过的个人提交I-D可能需要数周或数月时间，才能由作者作为新的（版本-00）工作组草案重新提交。
WG Chairs who use this state will be able to clearly indicate when their WG has adopted an individual submission I-D. This will facilitate the Datatracker's ability to correctly capture "Replaces" information for WG drafts and "Replaced by" information for the individual submissions I-Ds that are replaced by WG drafts.
使用此状态的工作组主席将能够清楚地表明其工作组何时采用了个人提交ID。这将有助于数据跟踪器正确捕获工作组草稿的“替换”信息以及工作组草稿替换的个人提交ID的“替换”信息。
The Datatracker shall allow an individual submission I-D to be moved into the "Adopted by a WG" state if the I-D is not expired and it has not been withdrawn, been 'replaced by' another I-D, or been adopted by another IETF WG (R-068). When a WG Chair or Delegate moves an I-D into the "Adopted by a WG" state, the Datatracker SHALL confirm this state change via e-mail to the author of the I-D and to the Chairs and Delegates or the WG that adopted the I-D (per Requirement R-100).
如果I-D未过期且未被撤销、未被另一I-D“替换”或已被另一IETF工作组（R-068）采用，则数据跟踪器应允许个人提交I-D进入“工作组采用”状态。当工作组主席或代表将I-D移至“工作组采纳”状态时，数据跟踪器应通过电子邮件向I-D的作者、主席和代表或采纳I-D的工作组确认该状态变更（根据要求R-100）。
Requirement R-009 specifies that changes to the WG status of an I-D shall not overwrite any previously archived I-D status history information for the I-D. All status change history information for an I-D needs to be preserved, including when an I-D is revised and subsequently approved for posting as a new version-00 "WG Document" having a different filename (viz. a filename that includes the string 'draft-ietf-' followed by a WG acronym).
要求R-009规定，对I-D工作组状态的更改不得覆盖I-D的任何先前存档的I-D状态历史信息。需要保留I-D的所有状态更改历史信息，包括当I-D被修订并随后批准作为新版本-00“工作组文件”发布时具有不同的文件名（即包含字符串“draft ietf-”，后跟WG首字母缩略词的文件名）。
The "WG Document" state describes an I-D that has been adopted by an IETF WG and is being actively developed.
“工作组文件”状态描述了IETF工作组已采用并正在积极开发的I-D。
WG Chairs and their Delegates SHALL be allowed to move an I-D that is not associated with any other WG into the "WG Document" state in their WG unless the I-D has expired, been withdrawn, or 'replaced by' another I-D or RFC (R-069).
工作组主席及其代表应被允许将与任何其他工作组无关的ID移动到其工作组中的“工作组文件”状态，除非该ID已过期、被撤销或被另一个ID或RFC（R-069）“替换”。
Alternatively, WG Chairs may rely on the functionality specified in Requirement R-070 to automatically move a version-00 draft into the "WG Document" state.
或者，工作组主席可依赖要求R-070中规定的功能，自动将版本00草案移至“工作组文件”状态。
The Datatracker SHALL automatically place a new version-00 I-D into the "WG Document" state if a WG Chair approves the submission of the I-D for posting in the IETF document repository and if the filename of the I-D includes the string 'draft-ietf-wgname-' (R-070).
如果工作组主席批准提交I-D以在IETF文件存储库中发布，并且I-D文件名包含字符串“草案IETF wgname-”（R-070），则数据跟踪器应自动将新版本的I-D放入“工作组文件”状态。
The Datatracker SHOULD encourage the WG Chair to input, confirm, or correct the filename of the individual submission I-D that is being 'replaced' (if any) by a new version-00 WG draft at the time that the WG Chair approves the posting of the new I-D (R-071).
Datatracker应鼓励工作组主席在工作组主席批准发布新的I-D（R-071）时，输入、确认或更正由新版本00工作组草案“替换”（如有）的个人提交I-D的文件名。
The WG Chair (or Delegate) who approves or moves an I-D into the "WG Document" state for the first time SHALL be encouraged to input an "Intended Maturity Level" for the I-D as defined in Section 5 of [RFC6174] if the Datatracker cannot automatically determine this information for some reason (R-072). The Datatracker SHALL allow the "Intended Maturity Level" to be changed after first being set, and the Datatracker SHALL allow a WG Chair or Delegate to enter this information at a later time if the "Intended Maturity Level" for an I-D could not be identified when the I-D was initially moved into the "WG Document" state (R-073).
如果数据跟踪器因某种原因（R-072）无法自动确定该信息，则应鼓励首次批准或将I-D移至“工作组文件”状态的工作组主席（或代表）输入[RFC6174]第5节中定义的I-D“预期成熟度水平”。数据跟踪器应允许“预期成熟度水平”在首次设定后进行更改，如果在初始将I-D移至“工作组文件”状态（R-073）时无法确定I-D的“预期成熟度水平”，则数据跟踪器应允许工作组主席或代表在以后输入此信息。
The Datatracker SHALL allow WG Chairs and their Delegates to move an I-D into the "WG Document" state from any other WG I-D state (e.g., per Sections 3.2 and 4.1 of [RFC6174]) if the I-D has not expired, been withdrawn, or been 'replaced by' another I-D or RFC (R-074).
数据跟踪器应允许工作组主席及其代表将工单从任何其他工作组工单状态（例如，根据[RFC6174]第3.2节和第4.1节）移动到“工作组文件”状态，前提是工单未过期、已撤销或已被另一工单或RFC（R-074）“替换”。
Under normal conditions, it should not be possible for an I-D to be in the "WG Document" state in more than one IETF WG at a time. The Datatracker SHALL NOT allow a WG Chair or Delegate to move an I-D into the "WG Document" state in their WG if the I-D is already in some WG I-D state in a different WG (R-075).
在正常情况下，一次在多个IETF工作组中，I-D不可能处于“工作组文档”状态。数据跟踪器不得允许工作组主席或代表在其工作组中将ID移动到“工作组文件”状态，如果ID已经在不同工作组（R-075）中的某个工作组I-D状态。
An I-D that is in the "WG Document" state may be transferred from one WG to a different WG by a Responsible AD. The Datatracker SHALL allow a Responsible AD to transfer an I-D from one WG to a different WG, and it SHALL encourage the AD to input some text for the status change history log of the I-D to provide context for the transfer (R-076). If an AD transfers an I-D, the Datatracker SHALL send an e-mail to the author of the I-D and CC the Chairs, their Delegates, and the Responsible ADs (for the WGs affected by the transfer) to inform them that the I-D has been transferred (R-077).
处于“工作组文件”状态的I-D可由负责的AD从一个工作组传输到另一个工作组。数据跟踪器应允许负责的AD将I-D从一个工作组传输到另一个工作组，并应鼓励AD为I-D的状态更改历史日志输入一些文本，以提供传输上下文（R-076）。如果AD传输了一份ID，则数据跟踪器应向ID的作者发送一封电子邮件，并抄送主席、他们的代表和负责的ADs（对于受传输影响的工作组），通知他们I-D已经传输（R-077）。
A "Parked WG Document" is an I-D that has lost its author or editor, is waiting for another document to be written or for a review to be completed, or cannot be progressed by the working group for some other reason.
“工作组文件”是指已失去作者或编辑、正在等待编写另一份文件或完成审查、或工作组因其他原因无法进行审查的ID。
The Datatracker SHALL allow a Responsible AD to transfer a "Parked WG Document" that is not expired from one WG to a different WG, and it SHALL encourage the AD to input some text to provide context for the transfer in the status change history log of the I-D (R-078).
数据跟踪器应允许责任广告将未过期的“工作组文件”从一个工作组转移到另一个工作组，并应鼓励广告输入一些文本，以便在I-D（R-078）的状态变更历史记录中为转移提供上下文。
If an AD transfers an I-D, the Datatracker SHALL send an e-mail to author of the I-D, to the WG Chairs and their Delegates, and to the Responsible ADs (of the WGs affected by the transfer of an I-D) to inform them that the I-D has been transferred to a different WG (R-079).
如果AD转让了I-D，数据跟踪器应向I-D的作者、工作组主席及其代表以及负责的AD（受I-D转让影响的工作组的）发送电子邮件，通知他们I-D已转让给不同的工作组（R-079）。
A "Dead WG Document" is an I-D that has been abandoned. Note that 'Dead' is not always a final state for a WG I-D. If consensus is subsequently achieved, a "Dead WG Document" may be resurrected; however, a "Dead WG Document" that is not resurrected will eventually expire.
“死工作组文件”是一个已被放弃的ID。请注意，“死亡”并不总是工作组ID的最终状态。如果随后达成共识，“死亡工作组文件”可能会复活；然而，一个没有复活的“死工作组文档”最终将过期。
The Datatracker SHALL allow a Responsible AD to transfer an I-D that is not expired from being in the "Dead WG Document" state in one WG to a non-dead state in different WG, and the Datatracker SHALL encourage the AD to input some text to provide context for the transfer in the status change history log of the I-D (R-080).
数据跟踪器应允许责任AD将一个工作组中处于“死工作组文件”状态的未过期I-D传输到不同工作组中的非死状态，数据跟踪器应鼓励AD输入一些文本，以便在I-D（R-080）的状态更改历史记录中为传输提供上下文。
If an AD transfers an I-D under the conditions specified by Requirement R-080, the Datatracker SHALL send an e-mail to the author of the I-D, the WG Chairs, the Delegates, and the Responsible ADs (for the WGs affected by the transfer) to inform them that the I-D has been transferred to a different WG (R-081).
如果AD在要求R-080规定的条件下转让了I-D，则数据跟踪器应向I-D的作者、工作组主席、代表和负责的ADs（对于受转让影响的工作组）发送电子邮件，通知他们I-D已转让给不同的工作组（R-081）。
A document that is in the "In WG Last Call" state is an I-D for which a Working Group Last Call (WGLC) has been issued and is in progress. Note that WG Last Calls are an optional part of the IETF WG process, per Section 7.4 of RFC 2418 [RFC2418].
处于“工作组最后一次调用”状态的文档是一个已发布并正在进行的工作组最后一次调用（WGLC）的ID。请注意，根据RFC 2418[RFC2418]第7.4节，工作组最后调用是IETF工作组过程的可选部分。
A WG Chair who decides to conduct a WGLC on an I-D may use the "In WG Last Call" state to track the progress of the WGLC.
工作组主席如果决定就工单进行工作组会议，可使用“工作组最后一次会议”状态来跟踪工作组会议的进展情况。
A WG Chair (or Delegate) SHALL be able configure the Datatracker to send a WGLC message to one or more mailing lists when he/she moves a WG draft into the "In WG Last Call" state and be able to select a different set of mailing lists for each I-D because some documents may need coordination with other WGs (R-082).
工作组主席（或代表）应能够配置数据跟踪器，以便在工作组草案进入“工作组最后一次通话”状态时向一个或多个邮件列表发送WGLC消息，并能够为每个I-D选择一组不同的邮件列表，因为某些文件可能需要与其他工作组协调（R-082）。
The Datatracker also needs to be able to send an e-mail, after a specified period of time, to remind or 'nudge' a WG Chair to conclude a WGLC and to determine a next state for the I-D.
Datatracker还需要能够在指定的时间段后发送电子邮件，以提醒或“推动”工作组主席结束工作组会议，并确定身份证的下一个状态。
The WG Chair (or Delegate) who moves an I-D into the "In WG Last Call" state SHALL be required to specify a length of time for the WGLC (R-083). The amount of time SHALL be able to be expressed as a "number of weeks", but it SHALL NOT be allowed to extend beyond the expiry date of the I-D (R-084). Other measures of time (e.g., "until a specific date in the future") MAY optionally be supported (R-085). The amount of time MUST be able to be changed after first being set (R-086).
工作组主席（或代表）将ID移动到“工作组最后一次呼叫”状态时，应规定工作组LC（R-083）的时间长度。时间量应能表示为“周数”，但不得超过I-D（R-084）的到期日。可以选择支持其他时间度量（例如，“直到未来某个特定日期”）（R-085）。首次设置后必须能够更改时间量（R-086）。
If an I-D is still in the "In WG Last Call" state when the amount of time specified in R-084 or R-085 runs out, the Datatracker SHALL send an e-mail to inform the WG Chairs and Delegates that the I-D is still in the "In WG Last Call" state, and to remind them they had planned to conclude the WGLC by now (R-087).
如果在R-084或R-085中规定的时间结束时，I-D仍处于“工作组最后一次通话”状态，则数据跟踪器应发送电子邮件通知工作组主席和代表，I-D仍处于“工作组最后一次通话”状态，并提醒他们计划现在结束工作组会议（R-087）。
Note that a WGLC may lead directly back into another WGLC for the same document. For example, an I-D that completed a WGLC as an "Informational" document may need another WGLC if a decision is taken to convert the I-D into a Standards Track document. The Datatracker MUST allow this to occur. (R-088)
请注意，对于同一文档，一个WGLC可能会直接返回到另一个WGLC。例如，如果决定将I-D转换为标准跟踪文档，则作为“信息”文档完成WGLC的I-D可能需要另一个WGLC。Datatracker必须允许这种情况发生。（R-088）
A document in the "WG Consensus: Waiting for Writeup" state has essentially completed its development within the WG, and is nearly ready to be sent to the IESG for publication. The last thing to be done is the preparation of a protocol writeup by the Document Shepherd. The IESG requires that a protocol writeup be completed before publication of an I-D is requested.
“工作组共识：等待编写”状态下的一份文件基本上已经完成了其在工作组内的开发，并几乎准备好发送给IESG进行发布。最后要做的事情是由文档管理员准备一份协议书。IESG要求在请求发布I-D之前完成协议写入。
An I-D in the "WG Consensus: Waiting for Writeup" state SHALL remain in this state until the WG Chair (or Delegate) moves the document to a different state (R-089).
在工作组主席（或代表）将文件移至其他状态（R-089）之前，处于“工作组共识：等待书面批准”状态的ID应保持该状态。
The Datatracker SHOULD be configurable to send an e-mail to a WG's Chairs and Delegates after a specified period of time to remind or 'nudge' them to check the status of the Document Shepherd's writeup for an I-D (R-090). This feature SHOULD look and feel similar to the way that Requirements R-064 to R-067 inclusive are implemented (R-091).
Datatracker应可配置为在指定时间段后向工作组主席和代表发送电子邮件，以提醒或“推动”他们检查I-D（R-090）的文件Shepherd's writeup状态。该功能的外观和感觉应类似于R-064至R-067要求的实现方式（R-091）。
This state describes a WG document that has been submitted to the IESG for publication and that has not been sent back to the WG for revision. An I-D in this state may be under review by the IESG, or it may have been approved and be in the RFC Editor's queue, or it may have been published as an RFC. Other possibilities exist too. The document may be "Dead" (in the IESG state machine) or in a "Do Not Publish" state.
该状态描述了一份工作组文件，该文件已提交给IESG发布，但尚未发送回工作组进行修订。处于这种状态的I-D可能正在接受IESG的审查，或者可能已经批准并在RFC编辑队列中，或者可能已经作为RFC发布。其他可能性也存在。文档可能处于“死”（在IESG状态机中）或“不发布”状态。
The Datatracker SHOULD look for the presence of WG I-D status annotation tags when a WG draft is moved into this state. If there are any tags that have not been cleared or reset, the Datatracker SHOULD encourage the WG Chairs (or Delegates) in real-time to reset or clear any extraneous annotation tags (R-092).
当工作组草稿移动到此状态时，Datatracker应该查找是否存在工作组I-D状态注释标记。如果有任何标签未被清除或重置，Datatracker应鼓励工作组主席（或代表）实时重置或清除任何无关的注释标签（R-092）。
After an I-D is submitted to the IESG, it may be judged as needing revision before it can be published as an RFC. An AD or the IESG as a whole may return a document to a WG for revision.
I-D提交给IESG后，可能会被判断为需要修订，然后才能作为RFC发布。AD或IESG作为一个整体可以将文件返回工作组进行修订。
An I-D that needs revision may be identified when the Responsible AD appends the "Revised I-D Needed" annotation tag to the IESG state of the I-D.
当责任AD将“需要修订的I-D”注释标签附加到I-D的IESG状态时，可以识别需要修订的I-D。
If an AD or the IESG as a whole sends an I-D back to a WG for revision (e.g., as described in Section 3.2 of [RFC6174]), the WG's Chairs may decide to change the WG state of the I-D from "Submitted to IESG for Publication" to a different state and to append one or more WG I-D status annotation tags to the I-D (e.g., per Sections 4.3.8 or 4.3.9 of [RFC6174]).
如果AD或IESG作为一个整体将I-D发回工作组进行修订（如[RFC6174]第3.2节所述），工作组主席可决定将I-D的工作组状态从“提交给IESG发布”更改为不同的状态，并将一个或多个工作组I-D状态注释标签附加到I-D（例如，根据[RFC6174]第4.3.8节或第4.3.9节）。
The Datatracker SHALL allow, but not require, the WG Chair or Delegate who attaches a "Revised I-D Needed" annotation tag to the WG status of an I-D to indicate the number of weeks they expect it will take for a revised document to be produced (R-093). The Datatracker should also prompt the user to consider changing the WG state of the I-D from "Submitted to IESG for Publication" to something else (e.g., Parked WG Document, WG Document, Waiting for WG Chair Go-Ahead) (R-094).
数据跟踪器应允许但不要求工作组主席或代表将“需要修订的I-D”注释标签附在工作组的I-D状态上，以表明他们预计生成修订文件所需的周数（R-093）。DATARTRAKER还应该提示用户考虑将ID的WG状态从“提交到IESG发布”改为其他（例如，停放WG文档、WG文档、等待WG Poad前进）（R-094）。
If a revised version of the I-D is not submitted to the WG before the time specified in R-093 elapses, the Datatracker SHALL send an e-mail to the WG's Chairs and Delegates to remind or 'nudge' them to followup on the revisions to the document (R-095).
如果在R-093规定的时间内未向工作组提交I-D的修订版本，则数据跟踪器应向工作组主席和代表发送电子邮件，提醒或“推动”他们跟进文件（R-095）的修订。
The Datatracker SHALL automatically reset or clear the "Revised I-D Needed" annotation tag attached to the WG status of an I-D when a revised version of that I-D is posted (R-096).
发布I-D修订版本时，数据跟踪器应自动重置或清除附在I-D工作组状态上的“需要修订的I-D”注释标签（R-096）。
To reduce the amount of information that WG Chairs and Delegates need to input to the Datatracker, the tool must automatically generate the following WG state transitions:
为了减少工作组主席和代表需要输入到Datatracker的信息量，该工具必须自动生成以下工作组状态转换：
- The Datatracker will move a version-00 I-D into the "WG Document" state when a WG Chair approves the posting of an I-D that includes the string '-ietf-' in its filename (as specified in Requirement R-070; and
- 当工作组主席批准发布文件名中包含字符串“-ietf-”的I-D时，Datatracker将版本00 I-D移至“工作组文件”状态（如要求R-070中规定；以及
- The Datatracker SHALL transition a draft into the WG state called "Submitted To IESG For Publication" at the same time that the I-D is moved into the "Publication Requested" state in the IESG state machine by an AD or the IETF Secretariat (R-097).
- 数据跟踪器应在AD或IETF秘书处（R-097）将I-D移至IESG状态机中的“发布请求”状态的同时，将草案转换为称为“提交给IESG以供发布”的工作组状态。
Everyone with 'write' access to WG I-D status information SHALL be able to obtain a summary display of all status changes made to the WG I-Ds that *they* are responsible for, from the present time backwards, split by pages, after successfully logging on to the Datatracker (R-098).
在成功登录到数据跟踪器（R-098）后，每个对工作组I-D状态信息具有“写”访问权的人都应能够获得对工作组I-D进行的所有状态更改的摘要显示，从现在起，他们*负责按页进行划分。
The Datatracker SHOULD provide a convenient way for WG Chairs to obtain a summary of all WG I-D status changes made on their behalf by their Delegates, from the present time backwards, split by pages (R-099).
数据跟踪器应为工作组主席提供一种方便的方式，以获取其代表从当前时间向后按页（R-099）进行的所有工作组I-D状态变更的摘要。
The Datatracker SHALL send an e-mail message to the authors of an I-D and to the Chairs and Delegates of the WG to which the I-D is associated whenever the WG status of the I-D is updated; the contents of the e-mail SHALL provide details about the change in the WG status of the document (e.g., the new state the I-D has been moved to and/or the names of any newly set or reset I-D status annotation tags), the date of the change in status, and an indication of who (or which entity) caused the change to the WG status of the I-D (R-100).
每当I-D的工作组状态更新时，数据跟踪器应向I-D的作者以及与I-D相关的工作组的主席和代表发送电子邮件；电子邮件内容应提供有关文件工作组状态变化的详细信息（例如，I-D移动到的新状态和/或任何新设置或重置的I-D状态注释标签的名称），状态变化的日期，以及谁（或哪个实体）导致I-D（R-100）工作组状态变化的指示。
The Datatracker SHALL provide everyone with a convenient way to query the status of every document in an IETF WG and to see a display of the current status of some or all of the documents in the WG, including the Document Shepherd protocol writeups for I-Ds that have been submitted to the IESG and the names of the Document Shepherds (R-101).
数据跟踪器应为每个人提供一种方便的方式，以查询IETF工作组中每个文件的状态，并查看工作组中部分或所有文件的当前状态显示，包括已提交给IESG的I-Ds文件管理器协议编写和文件管理器的名称（R-101）。
The Datatracker SHALL also provide everyone with the ability to search for the status of documents written by a specific author, or I-Ds in a specific WG I-D state or having a specific "Intended Maturity Level", or having a specific annotation tag attached (R-102).
数据跟踪器还应为每个人提供搜索特定作者或处于特定工作组I-D状态或具有特定“预期成熟度水平”或附有特定注释标签（R-102）的I-D编写的文件状态的能力。
The Datatracker's existing I-D status display pages SHOULD be modified to display at least the metadata and status information for an I-D that is associated with a WG as shown in the following example (R-103):
应修改Datatracker的现有I-D状态显示页面，以至少显示与工作组关联的I-D的元数据和状态信息，如以下示例（R-103）所示：
-----------------------------------------------------------------
-----------------------------------------------------------------
Document stream: IETF
I-D availability status: Active / Expired / Withdrawn / RFC
Replaces / Replaced by I-D or RFC
(if applicable)
Last updated: year-mm-dd (e.g. 2010-11-18)
IETF WG status: * Applicable WG state & name of WG or WGs
Intended RFC status: ** Informational / Experimental / etc.
Document shepherd: *** Name of Document Shepherd (if assigned)
IESG status: **** Name of applicable IESG state
Responsible AD: Name of the Responsible AD
Document stream: IETF
I-D availability status: Active / Expired / Withdrawn / RFC
Replaces / Replaced by I-D or RFC
(if applicable)
Last updated: year-mm-dd (e.g. 2010-11-18)
IETF WG status: * Applicable WG state & name of WG or WGs
Intended RFC status: ** Informational / Experimental / etc.
Document shepherd: *** Name of Document Shepherd (if assigned)
IESG status: **** Name of applicable IESG state
Responsible AD: Name of the Responsible AD
-----------------------------------------------------------------
-----------------------------------------------------------------
* The "IETF WG status" SHALL display the current WG state of the I-D and the WG that the I-D is associated with, and any I-D status annotation tags that are currently set (R-104).
* “IETF工作组状态”应显示I-D的当前工作组状态和与I-D相关的工作组，以及当前设置的任何I-D状态注释标签（R-104）。
** The "Intended RFC status" for I-Ds in the WG state called "Adopted for WG Info Only" SHOULD be displayed as "None" (R-105).
**工作组状态下I-D的“预期RFC状态”称为“仅适用于工作组信息”，应显示为“无”（R-105）。
** The field called "Intended RFC status" SHOULD be renamed to "RFC status" when the Datatracker displays the status of a document that has been published as an RFC (R-106).
**当Datatracker显示已发布为RFC（R-106）的文档的状态时，名为“预期RFC状态”的字段应重命名为“RFC状态”。
*** This field SHOULD display the name of the person (or e-mail
address of the person) designated as the Document Shepherd for
the I-D, or be left blank if a Document Shepherd has not yet
been designated (R-107).
*** This field SHOULD display the name of the person (or e-mail
address of the person) designated as the Document Shepherd for
the I-D, or be left blank if a Document Shepherd has not yet
been designated (R-107).
**** This field SHALL display the current IESG status of the
document or the word "None" for documents that are not yet
being tracked by the IESG (R-108).
**** This field SHALL display the current IESG status of the
document or the word "None" for documents that are not yet
being tracked by the IESG (R-108).
Errors with respect to inputting or updating the status of a WG document are possible.
输入或更新工作组文件状态时可能出现错误。
Per Requirement R-009, the creation of new or updated status information cannot erase, overwrite, or cause the deletion of any previously entered document status change history information.
根据要求R-009，创建新的或更新的状态信息不能删除、覆盖或导致删除以前输入的任何文档状态更改历史信息。
Errors in data entry by a WG Chair or Delegate should be corrected by a WG Chair or Delegate taking action to update any erroneous status information in the Datatracker with correct information, so that the correct status of the I-D is displayed. For example, a document that was accidentally placed into the wrong state can be moved into the correct state by the WG Chair (or Delegate), and a comment should be entered into the document's status change history log to explain what happened.
工作组主席或代表的数据输入错误应由工作组主席或代表纠正，并采取措施用正确的信息更新Datatracker中的任何错误状态信息，以便显示I-D的正确状态。例如，工作组主席（或代表）可以将意外置于错误状态的文档移动到正确状态，并且应在文档的状态更改历史日志中输入注释，以解释发生的情况。
This document does not propose any new Internet mechanisms and has no security implications for the Internet.
本文件未提出任何新的互联网机制，对互联网没有任何安全影响。
However, this document contains specific requirements to add features to the IETF Datatracker to make it possible for a greater number of users to input and/or update status information about I-Ds associated with IETF WGs. Enhancing the Datatracker may create an opening for new denial-of-service (DoS) attacks and/or attempts by malicious users to corrupt the information in the WG document status database.
然而，本文件包含向IETF数据跟踪器添加功能的具体要求，以使更多用户能够输入和/或更新与IETF WGs相关的I-D状态信息。增强Datatracker可能会为新的拒绝服务（DoS）攻击和/或恶意用户试图破坏WG文档状态数据库中的信息创造机会。
This document does not propose any specific requirements to mitigate DoS attacks on the Datatracker.
本文档未提出任何具体要求，以减轻Datatracker上的DoS攻击。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2418] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, September 1998.
[RFC2418]Bradner，S.，“IETF工作组指南和程序”，BCP 25，RFC 2418，1998年9月。
[RFC4858] Levkowetz, H., Meyer, D., Eggert, L., and A. Mankin, "Document Shepherding from Working Group Last Call to Publication", RFC 4858, May 2007.
[RFC4858]Levkowetz，H.，Meyer，D.，Eggert，L.，和A.Mankin，“工作组最后一次呼吁出版的文件管理”，RFC 4858，2007年5月。
[RFC6174] Juskevicius, E., "Definition of IETF Working Group Document States", RFC 6174, March 2011.
[RFC6174]Juskevicius，E.“IETF工作组文件状态的定义”，RFC 61742011年3月。
[IDTRACKER] "The IETF Datatracker tool", Web Application: https://datatracker.ietf.org/, Version 3.12, February 2, 2011.
[IDTRACKER]“IETF数据跟踪器工具”，Web应用程序：https://datatracker.ietf.org/，版本3.12，2011年2月2日。
[IESGIDSM] "Diagram of Main I-D States", Web Application: https://datatracker.ietf.org/images/state_diagram.gif, October 21, 2002.
[IESGIDSM]“主要I-D状态图”，Web应用程序：https://datatracker.ietf.org/images/state_diagram.gif，2002年10月21日。
[TRCKREQTS] Levkowetz, H. and Mankin, A., "Requirements on I-D Tracker Extensions for Working Group Chairs", Work in Progress, February 2007.
[TRCKREQTS]Levkowetz，H.和Mankin，A.，“工作组主席对I-D跟踪器扩展的要求”，正在进行的工作，2007年2月。
The author would like to thank Henrik Levkowetz and Allison Mankin for writing the original I-D [TRCKREQTS] that contained many good ideas and served as a foundation for this document.
作者想感谢Henrik Levkowetz和Allison Mankin写的原始I[TrkReqtts ]，包含了许多好的想法，并作为这份文件的基础。
The author would also like to thank Henrik Levkowetz, Alfred Hoenes, Paul Hoffman, and Subramanian (SM) Moonesamy for their ongoing support during the writing of this document. Many of their comments and suggestions have been used by the author to revise and improve this document.
作者还要感谢Henrik Levkowetz、Alfred Hoenes、Paul Hoffman和Subramanian（SM）Moonesay在撰写本文件期间给予的持续支持。作者使用了他们的许多意见和建议来修订和改进本文件。
The author also offers his gratitude to Russ Housley, Scott Bradner, Robert Sparks, Spencer Dawkins, and the WG Chairs and other IETF participants at the wgdtspec BOF at IETF 77 for their inputs, comments, and suggestions, and Lars Eggert, Tim Polk, Robert Sparks, Ralph Droms, Adrian Farrel, Alexey Melnikov, and Sean Turner for their comments, suggestions, and DISCUSS points on the penultimate draft version of this document.
作者还感谢Russ Housley、Scott Bradner、Robert Sparks、Spencer Dawkins以及IETF 77工作组主席和其他IETF参与者的投入、评论和建议，以及Lars Eggert、Tim Polk、Robert Sparks、Ralph Droms、Adrian Farrel、Alexey Melnikov和Sean Turner的评论，建议，并讨论本文件倒数第二稿的要点。
This document was initially prepared using 2-Word-v2.0.template.dot.
本文件最初使用2-Word-v2.0.template.dot编制。
Author's Address
作者地址
Ed Juskevicius TrekAhead PO Box 491, Carp, ON CANADA
Ed Juskevicius TrekAhead邮政信箱491号，加拿大卡普
EMail: edj.etc@gmail.com
EMail: edj.etc@gmail.com