Network Working Group B. Carpenter Internet-Draft IBM Obsoletes: 3683, 3934 (if October 16, 2006 approved) Updates: 2418 (if approved) Intended status: Best Current Practice Expires: April 19, 2007 Progressive Posting Rights Suspensions draft-carpenter-rescind-3683-03 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 19, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document restores the previous option of finite posting rights suspensions authorized by an Area Director. It also abolishes the existing form of indefinite Posting Rights Action. It obsoletes RFC 3683 and RFC 3934, and updates RFC 2418. Carpenter Expires April 19, 2007 [Page 1]
Internet-Draft Progressive Posting Suspensions October 2006 Table of Contents 1. Restoring the intent of RFC 2418 . . . . . . . . . . . . . . . 3 2. Specific Changes to RFC 2418 . . . . . . . . . . . . . . . . . 3 3. Rescinding RFC 3683 . . . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 7. Change log [RFC Editor: please remove this section] . . . . . . 4 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 6 Carpenter Expires April 19, 2007 [Page 2]
Internet-Draft Progressive Posting Suspensions October 2006 1. Restoring the intent of RFC 2418 BCP 94 [RFC3934] had the effect of removing the option of progressively increasing the length of posting rights suspensions, as implicitly allowed by BCP 25 [RFC2418] section 3.2. Suspensions longer than one month have been found to be necessary. This document obsoletes [RFC3934] and updates [RFC2418] in such a way as to restore the intent of [RFC2418] while retaining the WG Chair's power under [RFC3934]. Management of non-working group mailing lists is not currently covered by this BCP, but is covered by relevant IESG Statements, which may be located via http://www.ietf.org/IESG/Statements.html. 2. Specific Changes to RFC 2418 The following three paragraphs supersede the last paragraph of RFC 2418, section 3.2: As in face-to-face sessions, occasionally one or more individuals may engage in behavior on a mailing list that, in the opinion of the WG Chair, is disruptive to the WG process. Unless the disruptive behavior is severe enough that it must be stopped immediately, the WG Chair should attempt to discourage the disruptive behavior by communicating directly with the offending individual. If the behavior persists, the WG Chair should send at least one public warning on the WG mailing list. If the behavior still persists, and typically after one or more explicit warnings and consultation with the responsible Area Director, the WG Chair may suspend the mailing list posting privileges of the disruptive individual for a period of not more than 30 days. Even while posting privileges are suspended, the individual must not be prevented from receiving messages posted to the list. Like all other WG Chair decisions, any suspension of posting privileges is subject to appeal, as described in RFC 2026 [RFC2026]. This mechanism is intended to permit a WG Chair to suspend posting privileges of a disruptive individual for a short period of time. This mechanism does not permit WG Chairs to suspend an individual's posting privileges for a period longer than 30 days regardless of the type or severity of the disruptive incident. However, further disruptive behavior by the same individual will be considered separately and may result in further warnings or 30 day suspensions by the WG Chair. If the disruptive behavior still persists and after explicit warnings, the Area Director, with the approval of the IESG, may Carpenter Expires April 19, 2007 [Page 3]
Internet-Draft Progressive Posting Suspensions October 2006 request that the mailing list maintainer block the ability of the offending individual to post to the mailing list for periods longer than 30 days. Other methods of mailing list control may be considered but must be approved by the AD(s) and the IESG. Even while posting privileges are suspended, the individual must not be prevented from receiving messages posted to the list. Like all other Area Director decisions, any such suspension of posting privileges is subject to appeal, as described in RFC 2026 [RFC2026]. 3. Rescinding RFC 3683 BCP 83 [RFC3683] has been found troublesome and contentious in practice. It is hereby rescinded. Any suspensions in place under BCP 83 at the time of approval of this document are not affected. 4. Security Considerations This document does not directly affect the security of the Internet. 5. IANA Considerations This document makes no request for IANA assignments. 6. Acknowledgements John Klensin first proposed this approach and John Leslie contributed about half of the first draft. Useful comments were received from Lansing Sloan, Ted Ts'o, and others. This document was produced using the xml2rfc tool [RFC2629]. 7. Change log [RFC Editor: please remove this section] draft-carpenter-rescind-3683-00: original version, 2006-08-09. draft-carpenter-rescind-3683-01: update to mention non-WG lists, 2006-08-17. draft-carpenter-rescind-3683-02: updated for Last Call comments, 2006-10-03. Added URL for IESG Statements. Folded in text from RFC 3934 and 2418. draft-carpenter-rescind-3683-03: updated for IESG comments, Carpenter Expires April 19, 2007 [Page 4]
Internet-Draft Progressive Posting Suspensions October 2006 2006-10-16. Reordered content to separate topics, improved self- consistency. 8. References 8.1. Normative References [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [RFC2418] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, September 1998. [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF mailing lists", BCP 83, RFC 3683, February 2004. [RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the Management of IETF Mailing Lists", BCP 94, RFC 3934, October 2004. 8.2. Informative References [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999. Author's Address Brian Carpenter IBM 8 Chemin de Blandonnet 1214 Vernier, Switzerland Email: brc@zurich.ibm.com Carpenter Expires April 19, 2007 [Page 5]
Internet-Draft Progressive Posting Suspensions October 2006 Full Copyright Statement Copyright (C) The Internet Society (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. 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. 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. 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. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Carpenter Expires April 19, 2007 [Page 6]
