Network Working Group S. Hartman
Request for Comments: 4633 MIT
Category: Experimental August 2006
Network Working Group S. Hartman
Request for Comments: 4633 MIT
Category: Experimental August 2006
Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists
互联网工程任务组（IETF）邮件列表中的长期暂停试验
Status of This Memo
关于下段备忘
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.
这份备忘录为互联网社区定义了一个实验性协议。它没有规定任何类型的互联网标准。要求进行讨论并提出改进建议。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
Discussion in the community has begun to question whether RFC 3683 and RFC 3934 provide the appropriate flexibility for managing Internet Engineering Task Force (IETF) mailing lists. This document is an RFC 3933 experiment designed to allow the community to experiment with a broader set of tools for mailing list management while trying to determine what the long-term guidelines should be.
社区中的讨论已经开始质疑RFC 3683和RFC 3934是否为管理互联网工程任务组（IETF）邮件列表提供了适当的灵活性。本文档是一个RFC3933实验，旨在让社区在尝试确定长期指导原则的同时，尝试使用一套更广泛的邮件列表管理工具。
Table of Contents
目录
1. Introduction ....................................................1
2. Requirements notation ...........................................3
3. Definition of IETF Mailing List .................................3
4. The Experiment ..................................................4
5. How the Experiment May Be Used (Informative) ....................4
6. Security Considerations .........................................5
7. Acknowledgements ................................................5
8. References ......................................................5
8.1. Normative References .......................................5
8.2. Informative References .....................................5
1. Introduction ....................................................1
2. Requirements notation ...........................................3
3. Definition of IETF Mailing List .................................3
4. The Experiment ..................................................4
5. How the Experiment May Be Used (Informative) ....................4
6. Security Considerations .........................................5
7. Acknowledgements ................................................5
8. References ......................................................5
8.1. Normative References .......................................5
8.2. Informative References .....................................5
As discussed in RFC 3683, the IETF needs to have rules of conduct to limit disruptive or abusive behavior while permitting a fair and open forum for the discussion of Internet standardization. The IETF has a long and complicated history of rules for managing conduct on its mailing lists.
如RFC 3683所述，IETF需要有行为规则来限制破坏性或滥用行为，同时允许一个公平、公开的论坛来讨论互联网标准化。IETF有着悠久而复杂的管理邮件列表上行为的规则历史。
RFC 2418 [RFC2418] permitted individuals to be blocked from posting to a mailing list: "As a last resort and after explicit warnings, the Area Director, with the approval of the IESG, may request that the mailing list maintainer block the ability of the offending individual to post to the mailing list." RFC 2418 also allowed other forms of mailing list control to be applied with the approval of the area director and Internet Engineering Steering Group (IESG). However, RFC 2418 applied only to working group mailing lists.
RFC 2418[RFC2418]允许阻止个人向邮件列表投递：“作为最后手段，在明确警告后，经IESG批准，区域总监可要求邮件列表维护者阻止违规个人向邮件列表投递。”RFC 2418还允许在区域总监和互联网工程指导小组（IESG）的批准下应用其他形式的邮件列表控制。然而，RFC 2418仅适用于工作组邮件列表。
The IETF discussion list charter [RFC3005] provides guidelines for ietf@ietf.org. These guidelines provide more flexibility than RFC 2418. "The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair is empowered to restrict posting by a person, or of a thread, when the content is inappropriate and represents a pattern of abuse. They are encouraged to take into account the overall nature of the postings by an individual and whether particular postings are an aberration or typical. Complaints regarding their decisions should be referred to the IAB." In particular it appears that these decisions do not follow the normal appeals path outlined in RFC 2026 [RFC2026].
IETF讨论列表章程[RFC3005]提供了以下指南：ietf@ietf.org. 这些指南比RFC 2418提供了更多的灵活性。“IETF主席、IETF执行董事或主席任命的军士有权在内容不适当且代表滥用模式时限制个人或线索的发布。鼓励他们考虑个人发布的总体性质，以及特定发布是否符合要求e异常或典型。有关其决定的投诉应提交IAB。”特别是，这些决定似乎没有遵循RFC 2026[RFC2026]中概述的正常上诉路径。
RFC 3683 [RFC3683] provides a procedure for banning named individuals from posting to an IETF mailing list for at least one year. However once such a ban is put in place for one mailing list, the individuals responsible for other IETF mailing lists can unilaterally remove the posting rights of that individual.
RFC 3683[RFC3683]提供了一个程序，禁止具名个人在至少一年内张贴到IETF邮件列表中。然而，一旦对一个邮件列表实施了此类禁令，负责其他IETF邮件列表的个人可以单方面取消该个人的发布权利。
RFC 3934 [RFC3934] amends RFC 2418 and grants the working group chair the ability to suspend a member's posting rights for 30 days. However, it appears to remove the ability of the AD and IESG to approve longer suspensions or alternative procedures: "Other methods of mailing list control, including longer suspensions, must be carried out in accordance with other IETF-approved procedures." An argument could be made that the amendment was not intended to remove the already-approved procedures in RFC 2418, although a perhaps stronger argument can be made that the actual textual changes have the effect of removing these procedures.
RFC 3934[RFC3934]对RFC 2418进行了修订，并授予工作组主席暂停成员发布权30天的权利。然而，它似乎取消了AD和IESG批准较长暂停或替代程序的能力：“其他邮件列表控制方法，包括较长暂停，必须按照IETF批准的其他程序执行。”可以提出这样的论点，即该修正案并非旨在删除RFC 2418中已经批准的程序，尽管可以提出更有力的论点，即实际的文本更改具有删除这些程序的效果。
The IESG has issued a statement on mailing list management [IESGLIST] that allows working group mailing lists to be moderated. Under this procedure, specific off-topic postings could be discarded. However, this procedure does not allow the posting rights of an individual to be suspended; it simply allows the list as a whole to be moderated.
IESG发布了一份关于邮件列表管理的声明[IESGLIST]，允许对工作组邮件列表进行调节。在此过程中，可以放弃特定的非主题帖子。但是，该程序不允许暂停个人的张贴权利；它只是允许列表作为一个整体进行调节。
The IESG issued a statement on disruptive postings [IESGDISRUPT] . This statement applies procedures similar to RFC 3934 and to the statement on moderated lists to non-working group lists.
IESG发布了一份关于破坏性帖子[IESGDISRUPT]的声明。本声明适用于与RFC 3934类似的程序，并适用于非工作组名单的主持人名单声明。
The result of these guidelines is that there is a large gap between the levels of sanction that can be applied. An individual can be suspended from a working group list easily for 30 days. However, the only option available to the IESG that permits a longer suspension for any list besides ietf@ietf.org is the ability to suspend an individual for an indefinite time period from one list. This suspension can expand to any IETF list without community or IESG involvement. This memo is an RFC 3933 [RFC3933] experiment to provide the IESG with the ability to create additional mechanisms to manage IETF mailing lists while the community decides what mailing list guidelines are appropriate. In particular, this experiment allows the IESG to create a level of sanction between RFC 3934 and RFC 3683 for working group lists and to create sanctions other than RFC 3683 for non-working group lists. The goal of this experiment is to improve the functioning of IETF mailing lists while keeping the process open and fair. This experiment is successful if it gives the community useful input on how to design a mailing list management process. It is not expected that this experiment will be adopted in its current form as a permanent Best Current Practice (BCP).
这些准则的结果是，可适用的制裁水平之间存在很大差距。个人可以轻松地从工作组名单中暂停30天。然而，IESG唯一的选择是允许对任何列表进行更长时间的暂停ietf@ietf.org是从一个列表中无限期暂停某个人的能力。此暂停可以扩展到任何IETF列表，而无需社区或IESG参与。本备忘录是一项RFC 3933[RFC3933]实验，旨在为IESG提供创建额外机制来管理IETF邮件列表的能力，同时社区决定哪些邮件列表指南是合适的。特别是，该实验允许IESG为工作组名单创建RFC 3934和RFC 3683之间的制裁级别，并为非工作组名单创建RFC 3683以外的制裁级别。本实验的目标是改进IETF邮件列表的功能，同时保持过程的公开和公平。如果这个实验能够为社区提供关于如何设计邮件列表管理流程的有用信息，那么它就是成功的。预计该实验不会以当前形式作为永久性最佳实践（BCP）采用。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
This experiment applies to all IETF mailing lists, including those not associated with a working group. The definition of a working group list is clear, but the definition of an IETF mailing list comprehensive enough to include all IETF mailing lists is not obvious. For the purpose of this experiment, an IETF mailing list is defined as follows.
该实验适用于所有IETF邮件列表，包括与工作组无关的邮件列表。工作组列表的定义是明确的，但IETF邮件列表的定义不够全面，足以包括所有IETF邮件列表，这一点并不明显。为了本实验的目的，IETF邮件列表定义如下。
An "IETF mailing list" is defined as the IETF list itself, any mailing list operated to further the work of a current IETF Working Group (WG), any mailing list created for WG use but retained for ongoing discussion after that WG was shut down, any mailing list created in support of an IETF-specified procedure (including mailing lists whose purpose is the discussion of registration actions), and any mailing list hosted on any site or system operated by the IASA or otherwise on behalf of the IETF. Mailing lists listed at https://datatracker.ietf.org/public/nwg_list.cgi are explicitly included in this definition.
“IETF邮件列表”定义为IETF列表本身、为推进当前IETF工作组（WG）工作而运行的任何邮件列表、为工作组使用而创建但在工作组关闭后保留以供持续讨论的任何邮件列表、为支持IETF指定程序而创建的任何邮件列表（包括以讨论注册行动为目的的邮件列表）以及由IASA或以其他方式代表IETF运营的任何网站或系统上托管的任何邮件列表https://datatracker.ietf.org/public/nwg_list.cgi 明确包括在本定义中。
This experiment runs for a period of 18 months. During the experiment period, the IESG MAY approve other methods of mailing list control besides those outlined in RFC 3683 and RFC 3934 to be used on a specified set of IETF mailing lists. Such methods include but are not limited to suspending the posting rights of an individual beyond 30 days on those lists. Under such procedures the IESG may delegate the authority to perform longer-term suspensions of specific individuals on specific mailing lists.
这个实验为期18个月。在试验期间，IESG可批准除RFC 3683和RFC 3934中概述的邮件列表控制方法外的其他邮件列表控制方法，以用于指定的IETF邮件列表集。此类方法包括但不限于暂停个人在这些名单上的张贴权超过30天。根据此类程序，IESG可授权对特定邮寄名单上的特定个人进行长期停职。
The procedures of this memo MUST NOT be used to suspend the posting rights of an individual beyond the period of the experiment. The procedures of this memo MUST NOT be used to limit an individual's ability to read the contents of a mailing list.
本备忘录中的程序不得用于在试验期后暂停个人的张贴权。本备忘录的程序不得用于限制个人阅读邮件列表内容的能力。
The IESG MUST inform the community in a public statement of any procedures for mailing list management approved under this experiment. Such a statement should include the description of the procedure and the description of mailing lists to which it applies or an indication that it applies to all IETF mailing lists. The IESG MUST make a public announcement of a new procedure at least 14 days prior to the procedure taking effect. Although the community is encouraged to comment on any IESG action, community consensus is not required to approve such a procedure. All currently active procedures under this experiment MUST be made public in an appropriate, easy-to-find location.
IESG必须在公开声明中告知社区根据本实验批准的任何邮件列表管理程序。此类声明应包括程序说明及其适用的邮件列表说明，或说明其适用于所有IETF邮件列表。IESG必须在新程序生效前至少14天发布公告。尽管鼓励社区对IESG的任何行动发表意见，但批准此类程序不需要社区共识。所有目前正在进行的实验程序都必须在一个合适的、容易找到的地方公开。
Sanctions made under this memo may be appealed using the procedures outlined in [RFC2026].
可使用[RFC2026]中概述的程序对根据本备忘录作出的制裁提出上诉。
The IESG could approve a procedure allowing it to suspend an individual from one or more mailing lists for a fixed period of time greater than 30 days.
IESG可以批准一项程序，允许其将个人从一个或多个邮件列表中暂停30天以上的固定时间。
Also, the IESG could delegate this power. Two types of delegation are envisioned. In the first, the IESG has a procedure that allows it to suspend a named individual from a list and to grant the managers of that list the delegated authority to continue to apply longer suspensions if disruptive behavior continues. In the second, the IESG approves a procedure that specifies a set of lists and allows managers of those lists to take action unilaterally after an initial suspension in a manner similar to RFC 3683.
此外，IESG可以将这一权力下放。设想了两种类型的委托。在第一种情况下，IESG有一个程序，允许其暂停名单上的某个指定个人，并授予该名单的管理者授权，如果破坏性行为继续存在，可以继续实施更长时间的暂停。在第二种情况下，IESG批准了一个程序，该程序规定了一组名单，并允许这些名单的管理人员在初始暂停后以类似于RFC 3683的方式单方面采取行动。
This document describes a modification to the IETF process for managing mailing list discussions. It has no security considerations.
本文档描述了IETF过程的修改，用于管理邮件列表讨论。它没有安全考虑。
I would like to thank Brian Carpenter and John Klensin for valuable input in drafting this experiment.
我要感谢Brian Carpenter和John Klensin在起草本实验时提供的宝贵意见。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[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月。
[RFC3933] Klensin, J. and S. Dawkins, "A Model for IETF Process Experiments", BCP 93, RFC 3933, November 2004.
[RFC3933]Klensin，J.和S.Dawkins，“IETF过程实验的模型”，BCP 93，RFC 3933，2004年11月。
[IESGDISRUPT] "IESG Statement on Disruptive Posting", URL http://www.ietf.org/IESG/STATEMENTS/statement-disruptive-posting.txt, February 2006.
[IESGDISRUPT]“IESG关于破坏性发布的声明”，URLhttp://www.ietf.org/IESG/STATEMENTS/statement-disruptive-posting.txt，2006年2月。
[IESGLIST] "IESG guidance on the moderation of IETF Working Group Mailing Lists", URL http://www.ietf.org/IESG/STATEMENTS/moderated-lists.txt, August 2000.
[IESGLIST]“IESG关于IETF工作组邮件列表审核的指南”，URLhttp://www.ietf.org/IESG/STATEMENTS/moderated-lists.txt，2000年8月。
[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月。
[RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, RFC 3005, November 2000.
[RFC3005]Harris，S.，“IETF讨论列表章程”，BCP 45，RFC 3005，2000年11月。
[RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF Mailing Lists", BCP 83, RFC 3683, March 2004.
[RFC3683]Rose，M.，“撤销IETF邮件列表发布权的实践”，BCP 83，RFC 3683，2004年3月。
[RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the Management of IETF Mailing Lists", BCP 94, RFC 3934, October 2004.
[RFC3934]Wasserman，M.，“关于IETF邮件列表管理的RFC 2418更新”，BCP 94，RFC 3934，2004年10月。
Author's Address
作者地址
Sam Hartman Massachusetts Institute of Technology
山姆·哈特曼麻省理工学院
EMail: hartmans-ietf@mit.edu
EMail: hartmans-ietf@mit.edu
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。