idnits 2.17.00 (12 Aug 2021) /tmp/idnits41108/draft-eggert-bcp45bis-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- (Using the creation date from RFC3683, updated by this document, for RFC5378 checks: 2003-04-16) -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (24 February 2022) is 79 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 0 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group L. Eggert 3 Internet-Draft NetApp 4 Obsoletes: 3005 (if approved) 24 February 2022 5 Updates: 3683 (if approved) 6 Intended status: Best Current Practice 7 Expires: 28 August 2022 9 IETF Discussion List Charter 10 draft-eggert-bcp45bis-08 12 Abstract 14 The Internet Engineering Task Force (IETF) discussion mailing list 15 furthers the development and specification of Internet technology 16 through the general discussion of technical, procedural, operational 17 and other topics for which no dedicated mailing lists exists. As 18 this is the most general IETF mailing list, considerable latitude in 19 terms of topics is allowed, but there are posts and topics that are 20 unsuitable for this mailing list. This document defines the charter 21 for the IETF discussion list and explains its scope. 23 This document obsoletes RFC3005 and updates RFC3683. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on 28 August 2022. 42 Copyright Notice 44 Copyright (c) 2022 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 49 license-info) in effect on the date of publication of this document. 50 Please review these documents carefully, as they describe your rights 51 and restrictions with respect to this document. Code Components 52 extracted from this document must include Revised BSD License text as 53 described in Section 4.e of the Trust Legal Provisions and are 54 provided without warranty as described in the Revised BSD License. 56 This document may contain material from IETF Documents or IETF 57 Contributions published or made publicly available before November 58 10, 2008. The person(s) controlling the copyright in some of this 59 material may not have granted the IETF Trust the right to allow 60 modifications of such material outside the IETF Standards Process. 61 Without obtaining an adequate license from the person(s) controlling 62 the copyright in such materials, this document may not be modified 63 outside the IETF Standards Process, and derivative works of it may 64 not be created outside the IETF Standards Process, except to format 65 it for publication as an RFC or to translate it into languages other 66 than English. 68 Table of Contents 70 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 71 2. Charter for the IETF Discussion List . . . . . . . . . . . . 3 72 3. Moderation . . . . . . . . . . . . . . . . . . . . . . . . . 5 73 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 75 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 76 6.1. Normative References . . . . . . . . . . . . . . . . . . 6 77 6.2. Informative References . . . . . . . . . . . . . . . . . 6 78 Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 7 79 A.1. Since draft-eggert-bcp45bis-08 . . . . . . . . . . . . . 7 80 A.2. Since draft-eggert-bcp45bis-07 . . . . . . . . . . . . . 8 81 A.3. Since draft-eggert-bcp45bis-06 . . . . . . . . . . . . . 8 82 A.4. Since draft-eggert-bcp45bis-05 . . . . . . . . . . . . . 8 83 A.5. Since draft-eggert-bcp45bis-04 . . . . . . . . . . . . . 8 84 A.6. Since draft-eggert-bcp45bis-03 . . . . . . . . . . . . . 9 85 A.7. Since draft-eggert-bcp45bis-02 . . . . . . . . . . . . . 9 86 A.8. Since draft-eggert-bcp45bis-01 . . . . . . . . . . . . . 9 87 A.9. Since draft-eggert-bcp45bis-00 . . . . . . . . . . . . . 9 88 A.10. Since RFC3005 . . . . . . . . . . . . . . . . . . . . . . 9 89 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10 90 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 92 1. Introduction 94 The IETF discussion list [IETF-DISCUSS] furthers the development and 95 specification of Internet technology through the general discussion 96 of technical, procedural, operational and other topics for which no 97 dedicated mailing lists exists. As this is the most general IETF 98 mailing list, considerable latitude in terms of topics is allowed. 99 However, there are posts and topics that are unsuitable for this 100 mailing list. This document defines the charter for the IETF 101 discussion list and explains its scope. 103 The IETF Note Well [NOTE-WELL] applies to discussions on the IETF 104 discussion list and all other IETF mailing lists, and requires 105 conformance with the IETF Guidelines for Conduct [RFC7154] and the 106 Anti-Harassment Policy [RFC7776], among others. 108 This document obsoletes [RFC3005], documenting the use of other 109 mailing lists for discussions that used to be in scope for the IETF 110 discussion list, referring to applicable policies such as the 111 Guidelines for Conduct [RFC7154] and the Anti-Harassment Policy 112 [RFC7776], and clarifying moderation procedures. It also updates 113 part of Section 1 of [RFC3683], which copies the list of 114 "inappropriate postings" from [RFC3005]. This list in [RFC3683] is 115 hence updated by the new list in Section 2 below. 117 2. Charter for the IETF Discussion List 119 The IETF discussion list is meant for discussions for which a more 120 appropriate list does not exist, such as discussions that do not fall 121 within the scope of any working group, area, or other established 122 list. When discussions are started on the IETF discussion list for 123 which such a venue does exist, they should be continued at that other 124 venue as soon as this is pointed out. 126 When no dedicated mailing list exists for a topic, it may be 127 preferable to request the creation of one [NON-WG-LISTS] and announce 128 the availability of the new list on the IETF discussion list and on 129 other related lists, such as area lists, rather than discussing that 130 topic on the IETF discussion list. 132 Appropriate postings to the IETF discussion list include: 134 * Initial discussion of technical issues that are candidates for 135 IETF work, but have not yet identified appropriate mailing lists. 137 * Questions and clarifications concerning practical aspects of IETF 138 meetings, although most of these topics are better brought up on 139 the discussion list for IETF LLC administrative issues 140 [ADMIN-DISCUSS] or the attendee discussion list for a given IETF 141 meeting. 143 * Announcements of conferences, events, or activities that are 144 sponsored or endorsed by the IETF, IRTF, IAB or the Internet 145 Society, although the IETF announcement list [IETF-ANNOUNCE] is 146 the preferred list for these. 148 * Discussions of IETF direction, policy, and the standards process 149 in general, when a more suitable list (such as the discussion list 150 for IETF LLC administrative issues [ADMIN-DISCUSS], the IAB 151 discussion list for architectural issues [ARCH-DISCUSS], a meeting 152 attendees list, a process-oriented WG list, etc.) cannot be 153 identified. 155 These topics used to be in scope for the IETF discussion list, but 156 have since moved to dedicated lists: 158 * Last Call discussions of documents now take place on the IETF Last 159 Calls mailing list [LAST-CALLS]. 161 * Discussion of IETF administrative policies now takes place on the 162 discussion list for IETF LLC administrative issues 163 [ADMIN-DISCUSS]. 165 Inappropriate postings include: 167 * Advertising and other unsolicited bulk e-mail 169 * Discussion of subjects unrelated to IETF policy, meetings, 170 activities, or technical topics 172 * Uncivil commentary, regardless of the general subject, per the 173 IETF Note Well [NOTE-WELL] 175 * Announcements of conferences, events, or activities that are not 176 sponsored or endorsed by the Internet Society or the IETF. 178 3. Moderation 180 The IETF Chair appoints _Moderators_ (previously known as the 181 "sergeant-at-arms") for the IETF discussion list that are empowered 182 to restrict posting by a person, or to an email thread, when the 183 content is inappropriate and represents a pattern of abuse. They are 184 encouraged to take into account the overall nature of the postings by 185 an individual and whether particular postings are an aberration or 186 typical. 188 Moderation of the IETF discussion list, including the handling of any 189 appeals, is to be guided by the IETF discussion list charter 190 specified in Section 2, and the related guidance from Section 1 that 191 applies to all mailing lists. The moderators are intended to 192 establish a self-moderation function on the community, by the 193 community. Because the IESG and IAB are in the appeals chain for 194 moderator decisions (see below), the IETF Chair therefore should not 195 appoint a moderator who is serving in such a role. If a moderator is 196 selected for the IESG or IAB, they will step down from the moderator 197 team. 199 Apart from appointing moderators, the IETF Chair should refrain from 200 the day-to-day operation and management of the moderator team. The 201 moderator team will independently define, publish, and execute their 202 role; see the current set of operating procedures [MOD-SOP] and abuse 203 patterns [MOD-UPC]. The moderator team should reach out to the IETF 204 Chair for any conflict resolution in a timely manner. 206 Because a moderator serves at the discretion of the IETF Chair - even 207 if the IETF Chair is not otherwise involved in the operation of the 208 moderator team - any moderator decision can be appealed to the IETF 209 Chair, per [RFC2026]. Decisions by the IETF Chair can be appealed to 210 the IESG as whole, again per [RFC2026]. 212 4. Security Considerations 214 The usual security considerations [RFC3552] do not apply to this 215 document. 217 Potential abuse of the moderation process for the suppression of 218 undesired opinions is counteracted by the availability of an appeals 219 process, per Section 3. 221 5. IANA Considerations 223 This document does not request any IANA actions. 225 6. References 226 6.1. Normative References 228 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 229 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 230 . 232 6.2. Informative References 234 [ADMIN-DISCUSS] 235 IETF, "Discussion List for IETF LLC Administrative 236 Issues", 20 October 2021, 237 . 239 [ARCH-DISCUSS] 240 IAB, "Open Discussion Forum For Long/Wide-Range 241 Architectural Issues", 20 October 2021, 242 . 244 [IETF-ANNOUNCE] 245 IETF, "IETF Announcement List", 20 October 2021, 246 . 248 [IETF-DISCUSS] 249 IETF, "IETF Discussion List", 20 October 2021, 250 . 252 [LAST-CALLS] 253 IETF, "IETF Last Calls", 20 October 2021, 254 . 256 [MOD-SOP] IETF Discussion List Moderator Team, "IETF Discussion List 257 Moderator Team Standard Operating Procedures", 20 October 258 2021, . 260 [MOD-UPC] IETF Discussion List Moderator Team, "Unprofessional 261 Commentary", 20 October 2021, 262 . 265 [NON-WG-LISTS] 266 IETF, "Non-Working Group Email List Guidelines", 20 267 October 2021, 268 . 270 [NOTE-WELL] 271 IETF, "Note Well", 20 October 2021, 272 . 274 [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, 275 RFC 3005, DOI 10.17487/RFC3005, November 2000, 276 . 278 [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC 279 Text on Security Considerations", BCP 72, RFC 3552, 280 DOI 10.17487/RFC3552, July 2003, 281 . 283 [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF 284 Mailing Lists", BCP 83, RFC 3683, DOI 10.17487/RFC3683, 285 March 2004, . 287 [RFC7154] Moonesamy, S., Ed., "IETF Guidelines for Conduct", BCP 54, 288 RFC 7154, DOI 10.17487/RFC7154, March 2014, 289 . 291 [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment 292 Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March 293 2016, . 295 Appendix A. Changes 297 | RFC Editor: Please remove this appendix before publication. 299 A.1. Since draft-eggert-bcp45bis-08 301 * Update [RFC3683], because it copies text from [RFC3005] that this 302 document updates. See this issue 303 (https://github.com/larseggert/bcp45bis/issues/11). 305 * addressed Eric Vyncke's IESG review 306 (https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/ 307 ballot/#draft-eggert-bcp45bis_eric-vyncke) 309 * addressed Francesca Palombini's IESG review 310 (https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/ 311 ballot/#draft-eggert-bcp45bis_francesca-palombini) and Carsten 312 Bormann's ART ART review 313 (https://mailarchive.ietf.org/arch/msg/art/ZnkYEl- 314 9mRWfKXtzHVUu7u92QB0/) 316 * addressed John Scudder's IESG review 317 (https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/ 318 ballot/#draft-eggert-bcp45bis_john-scudder) 320 * addressed Roman Danyliw's IESG review 321 (https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/ 322 ballot/#draft-eggert-bcp45bis_roman-danyliw) 324 * addressed Ben Kaduk's IESG review 325 (https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/ 326 ballot/#draft-eggert-bcp45bis_benjamin-kaduk) 328 A.2. Since draft-eggert-bcp45bis-07 330 * incorporated suggestions from Adrian Farrel 331 (https://mailarchive.ietf.org/arch/msg/last-call/ 332 bt79VpEeM4iAiFVD5vtxHAa_kdc) 334 * incorporated some suggestions from S Moonesamy 335 (https://mailarchive.ietf.org/arch/msg/last-call/ 336 xQoWLovElvnS80ZPgHquAwJs3Mw) 338 * applied suggestions from Robert Wilton 339 (https://mailarchive.ietf.org/arch/msg/last-call/ 340 qCC0p5Yow7AOQLo8T3862jPl4i0) 342 A.3. Since draft-eggert-bcp45bis-06 344 * applied a suggestion from Lloyd Wood 345 (https://mailarchive.ietf.org/arch/msg/ietf/ 346 jVF496BFjekl9eVx1q9sqDIqOCs) to add access dates to cited URLs 348 * fixes to this change log 350 * applied a suggestion from Brian Carpenter to change 351 "unprofessional" to "uncivil" 353 A.4. Since draft-eggert-bcp45bis-05 355 * clarification of list scope as suggested by Brian Carpenter 356 (https://github.com/larseggert/bcp45bis/pull/10) 358 A.5. Since draft-eggert-bcp45bis-04 360 * use RFC2026 appeals process 361 (https://github.com/larseggert/bcp45bis/pull/7) 363 * addressed comments from Barry Leiba 364 (https://github.com/larseggert/bcp45bis/pull/6) 366 * quote cited text from Wikipedia 368 A.6. Since draft-eggert-bcp45bis-03 370 * addressed Robert Wilton's AD review 371 (https://github.com/larseggert/bcp45bis/pull/5) 373 A.7. Since draft-eggert-bcp45bis-02 375 * additional details about and guidelines for the SAA team, based on 376 a suggestion from Dhruv Dhody 377 (https://github.com/larseggert/bcp45bis/pull/1) 379 * remove reference to the IETF 110 attendees list, since those lists 380 are being removed by the secretariat shortly after each meeting 382 A.8. Since draft-eggert-bcp45bis-01 384 * applied a suggestion from Brian Carpenter 385 (https://mailarchive.ietf.org/arch/msg/gendispatch/- 386 U2LWKf0VonKnQXs4jPEqIg_L_A) 388 * rephrased beginning of Section 2, as suggested by Stephen Farrell 389 (https://mailarchive.ietf.org/arch/msg/gendispatch/p73lu- 390 D-WvQrbKBZ80c2T7bbBlQ/) 392 * incorporated a suggestion from Christian Huitema 393 (https://mailarchive.ietf.org/arch/msg/ 394 gendispatch/64LgqlIk0h62mAK09Muqn1ccqRE/) 396 A.9. Since draft-eggert-bcp45bis-00 398 * added introduction, security considerations and IANA 399 considerations sections 401 * added "note to readers" with pointers to the discussion list and 402 the repo 404 * added references to IETF Sergeants-at-Arms procedures 406 * added references to various mailing lists for topics that used to 407 be in scope for the IETF discussion list but no longer are 409 * added references to the Note Well and relevant other policies that 410 apply 412 A.10. Since RFC3005 414 * converted to Markdown and xml2rfc v3 415 * updated references (as part of the conversion) 417 * updated author information 419 * various formatting changes 421 Acknowledgements 423 The following people have made contributions to this document: 425 * Adrian Farrel 427 * Barry Leiba 429 * Ben Kaduk 431 * Brian Carpenter 433 * Carsten Bormann 435 * Christian Huitema 437 * Dhruv Dhody 439 * Eric Rescorla 441 * Eric Vyncke 443 * Francesca Palombini 445 * John Scudder 447 * Lloyd Wood 449 * Martin Thomson 451 * Robert Wilton 453 * S Moonesamy 455 * Stephen Farrell 457 Susan R. Harris authored [RFC3005], which this document replaces. 459 Author's Address 460 Lars Eggert 461 NetApp 462 Stenbergintie 12 B 463 FI-02700 Kauniainen 464 Finland 465 Email: lars@eggert.org 466 URI: https://eggert.org/