idnits 2.17.1 draft-carpenter-rescind-3683-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 204. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 215. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 222. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 228. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. -- The draft header indicates that this document obsoletes RFC3934, but the abstract doesn't seem to directly say this. It does mention RFC3934 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year (Using the creation date from RFC2418, updated by this document, for RFC5378 checks: 1997-03-25) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 16, 2006) is 6403 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Carpenter 3 Internet-Draft IBM 4 Obsoletes: 3683, 3934 (if October 16, 2006 5 approved) 6 Updates: 2418 (if approved) 7 Intended status: Best Current 8 Practice 9 Expires: April 19, 2007 11 Progressive Posting Rights Suspensions 12 draft-carpenter-rescind-3683-03 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on April 19, 2007. 39 Copyright Notice 41 Copyright (C) The Internet Society (2006). 43 Abstract 45 This document restores the previous option of finite posting rights 46 suspensions authorized by an Area Director. It also abolishes the 47 existing form of indefinite Posting Rights Action. It obsoletes RFC 48 3683 and RFC 3934, and updates RFC 2418. 50 Table of Contents 52 1. Restoring the intent of RFC 2418 . . . . . . . . . . . . . . . 3 53 2. Specific Changes to RFC 2418 . . . . . . . . . . . . . . . . . 3 54 3. Rescinding RFC 3683 . . . . . . . . . . . . . . . . . . . . . . 4 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 57 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 58 7. Change log [RFC Editor: please remove this section] . . . . . . 4 59 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 61 8.2. Informative References . . . . . . . . . . . . . . . . . . 5 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 Intellectual Property and Copyright Statements . . . . . . . . . . 6 65 1. Restoring the intent of RFC 2418 67 BCP 94 [RFC3934] had the effect of removing the option of 68 progressively increasing the length of posting rights suspensions, as 69 implicitly allowed by BCP 25 [RFC2418] section 3.2. Suspensions 70 longer than one month have been found to be necessary. This document 71 obsoletes [RFC3934] and updates [RFC2418] in such a way as to restore 72 the intent of [RFC2418] while retaining the WG Chair's power under 73 [RFC3934]. 75 Management of non-working group mailing lists is not currently 76 covered by this BCP, but is covered by relevant IESG Statements, 77 which may be located via http://www.ietf.org/IESG/Statements.html. 79 2. Specific Changes to RFC 2418 81 The following three paragraphs supersede the last paragraph of RFC 82 2418, section 3.2: 84 As in face-to-face sessions, occasionally one or more individuals may 85 engage in behavior on a mailing list that, in the opinion of the WG 86 Chair, is disruptive to the WG process. Unless the disruptive 87 behavior is severe enough that it must be stopped immediately, the WG 88 Chair should attempt to discourage the disruptive behavior by 89 communicating directly with the offending individual. If the 90 behavior persists, the WG Chair should send at least one public 91 warning on the WG mailing list. If the behavior still persists, and 92 typically after one or more explicit warnings and consultation with 93 the responsible Area Director, the WG Chair may suspend the mailing 94 list posting privileges of the disruptive individual for a period of 95 not more than 30 days. Even while posting privileges are suspended, 96 the individual must not be prevented from receiving messages posted 97 to the list. Like all other WG Chair decisions, any suspension of 98 posting privileges is subject to appeal, as described in RFC 2026 99 [RFC2026]. 101 This mechanism is intended to permit a WG Chair to suspend posting 102 privileges of a disruptive individual for a short period of time. 103 This mechanism does not permit WG Chairs to suspend an individual's 104 posting privileges for a period longer than 30 days regardless of the 105 type or severity of the disruptive incident. However, further 106 disruptive behavior by the same individual will be considered 107 separately and may result in further warnings or 30 day suspensions 108 by the WG Chair. 110 If the disruptive behavior still persists and after explicit 111 warnings, the Area Director, with the approval of the IESG, may 112 request that the mailing list maintainer block the ability of the 113 offending individual to post to the mailing list for periods longer 114 than 30 days. Other methods of mailing list control may be 115 considered but must be approved by the AD(s) and the IESG. Even 116 while posting privileges are suspended, the individual must not be 117 prevented from receiving messages posted to the list. Like all other 118 Area Director decisions, any such suspension of posting privileges is 119 subject to appeal, as described in RFC 2026 [RFC2026]. 121 3. Rescinding RFC 3683 123 BCP 83 [RFC3683] has been found troublesome and contentious in 124 practice. It is hereby rescinded. Any suspensions in place under 125 BCP 83 at the time of approval of this document are not affected. 127 4. Security Considerations 129 This document does not directly affect the security of the Internet. 131 5. IANA Considerations 133 This document makes no request for IANA assignments. 135 6. Acknowledgements 137 John Klensin first proposed this approach and John Leslie contributed 138 about half of the first draft. Useful comments were received from 139 Lansing Sloan, Ted Ts'o, and others. 141 This document was produced using the xml2rfc tool [RFC2629]. 143 7. Change log [RFC Editor: please remove this section] 145 draft-carpenter-rescind-3683-00: original version, 2006-08-09. 147 draft-carpenter-rescind-3683-01: update to mention non-WG lists, 148 2006-08-17. 150 draft-carpenter-rescind-3683-02: updated for Last Call comments, 151 2006-10-03. Added URL for IESG Statements. Folded in text from RFC 152 3934 and 2418. 154 draft-carpenter-rescind-3683-03: updated for IESG comments, 155 2006-10-16. Reordered content to separate topics, improved self- 156 consistency. 158 8. References 160 8.1. Normative References 162 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 163 3", BCP 9, RFC 2026, October 1996. 165 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 166 Procedures", BCP 25, RFC 2418, September 1998. 168 [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF 169 mailing lists", BCP 83, RFC 3683, February 2004. 171 [RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the 172 Management of IETF Mailing Lists", BCP 94, RFC 3934, 173 October 2004. 175 8.2. Informative References 177 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 178 June 1999. 180 Author's Address 182 Brian Carpenter 183 IBM 184 8 Chemin de Blandonnet 185 1214 Vernier, 186 Switzerland 188 Email: brc@zurich.ibm.com 190 Full Copyright Statement 192 Copyright (C) The Internet Society (2006). 194 This document is subject to the rights, licenses and restrictions 195 contained in BCP 78, and except as set forth therein, the authors 196 retain all their rights. 198 This document and the information contained herein are provided on an 199 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 200 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 201 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 202 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 203 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 204 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 206 Intellectual Property 208 The IETF takes no position regarding the validity or scope of any 209 Intellectual Property Rights or other rights that might be claimed to 210 pertain to the implementation or use of the technology described in 211 this document or the extent to which any license under such rights 212 might or might not be available; nor does it represent that it has 213 made any independent effort to identify any such rights. Information 214 on the procedures with respect to rights in RFC documents can be 215 found in BCP 78 and BCP 79. 217 Copies of IPR disclosures made to the IETF Secretariat and any 218 assurances of licenses to be made available, or the result of an 219 attempt made to obtain a general license or permission for the use of 220 such proprietary rights by implementers or users of this 221 specification can be obtained from the IETF on-line IPR repository at 222 http://www.ietf.org/ipr. 224 The IETF invites any interested party to bring to its attention any 225 copyrights, patents or patent applications, or other proprietary 226 rights that may cover technology that may be required to implement 227 this standard. Please address the information to the IETF at 228 ietf-ipr@ietf.org. 230 Acknowledgment 232 Funding for the RFC Editor function is provided by the IETF 233 Administrative Support Activity (IASA).