Network Working Group B. Carpenter Internet-Draft IBM Obsoletes: 3683 (if approved) August 9, 2006 Updates: 2418, 3934 (if approved) Intended status: Best Current Practice Expires: February 10, 2007 Progressive Posting Rights Supsensions draft-carpenter-rescind-3683-00 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 February 10, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document abolishes the existing form of indefinite Posting Rights Action and restores the previous option of finite posting rights suspensions authorized by an Area Director. It obsoletes RFC 3683 and updates RFC 2418 and RFC 3934. Carpenter Expires February 10, 2007 [Page 1]
Internet-Draft Progressive Posting Supsensions August 2006 Table of Contents 1. Posting Rights . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 5. Change log [RFC Editor: please remove this section] . . . . . . 3 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 6.1. Normative References . . . . . . . . . . . . . . . . . . . 3 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 Intellectual Property and Copyright Statements . . . . . . . . . . 5 Carpenter Expires February 10, 2007 [Page 2]
Internet-Draft Progressive Posting Supsensions August 2006 1. Posting Rights 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. BCP 94 [RFC3934] has been interpreted as 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, so [RFC3934] shall not be interpreted to prevent the Area Director, with the approval of the IESG, from authorizing posting rights suspensions of increasing length upon the request of a Working Group Chair, i.e., the Area Director's power under [RFC2418] section 3.2 is reinstated at the time of approval of this document. 2. Security Considerations This document does not directly affect the security of the Internet. 3. IANA Considerations This document makes no request for IANA assignments. 4. Acknowledgements John Leslie contributed about half the substantive text. This document was produced using the xml2rfc tool [RFC2629]. 5. Change log [RFC Editor: please remove this section] draft-carpenter-rescind-3683-00: original version, 2006-08-09. 6. References 6.1. Normative References [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. Carpenter Expires February 10, 2007 [Page 3]
Internet-Draft Progressive Posting Supsensions August 2006 [RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the Management of IETF Mailing Lists", BCP 94, RFC 3934, October 2004. 6.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 February 10, 2007 [Page 4]
Internet-Draft Progressive Posting Supsensions August 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 February 10, 2007 [Page 5]
