idnits 2.17.1 draft-eggert-bcp45bis-01.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: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, 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 (29 March 2021) is 1122 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 normative reference: RFC 3005 (Obsoleted by RFC 9245) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). 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) 29 March 2021 5 Intended status: Best Current Practice 6 Expires: 30 September 2021 8 IETF Discussion List Charter 9 draft-eggert-bcp45bis-01 11 Abstract 13 The Internet Engineering Task Force (IETF) discussion mailing list 14 furthers the development and specification of Internet technology 15 through the general discussion of topics for which no dedicated 16 mailing lists exists. As this is the most general IETF mailing list, 17 considerable latitude is allowed. Advertising, whether to solicit 18 business or promote employment opportunities, falls well outside the 19 range of acceptable topics, as do discussions of a personal nature. 21 This document obsoletes RFC3005. 23 Note to Readers 25 Discussion of this draft takes place on the GENDISPATCH working group 26 mailing list (mailto:gendispatch@ietf.org), which is archived at 27 https://mailarchive.ietf.org/arch/browse/gendispatch/. 29 Working Group information can be found at 30 https://datatracker.ietf.org/wg/gendispatch/; source code and the 31 issues list for this draft can be found at 32 https://github.com/larseggert/bcp45bis. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at https://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on 30 September 2021. 50 Copyright Notice 52 Copyright (c) 2021 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 57 license-info) in effect on the date of publication of this document. 58 Please review these documents carefully, as they describe your rights 59 and restrictions with respect to this document. Code Components 60 extracted from this document must include Simplified BSD License text 61 as described in Section 4.e of the Trust Legal Provisions and are 62 provided without warranty as described in the Simplified BSD License. 64 This document may contain material from IETF Documents or IETF 65 Contributions published or made publicly available before November 66 10, 2008. The person(s) controlling the copyright in some of this 67 material may not have granted the IETF Trust the right to allow 68 modifications of such material outside the IETF Standards Process. 69 Without obtaining an adequate license from the person(s) controlling 70 the copyright in such materials, this document may not be modified 71 outside the IETF Standards Process, and derivative works of it may 72 not be created outside the IETF Standards Process, except to format 73 it for publication as an RFC or to translate it into languages other 74 than English. 76 Table of Contents 78 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 79 2. Charter for the IETF Discussion List . . . . . . . . . . . . 3 80 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 81 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 82 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 83 5.1. Normative References . . . . . . . . . . . . . . . . . . 4 84 5.2. Informative References . . . . . . . . . . . . . . . . . 4 85 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5 86 Appendix B. Changes . . . . . . . . . . . . . . . . . . . . . . 5 87 B.1. Since draft-eggert-bcp45bis-00 . . . . . . . . . . . . . 5 88 B.2. Since RFC3005 . . . . . . . . . . . . . . . . . . . . . . 6 89 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 91 1. Introduction 93 The IETF discussion list [IETF-DISCUSS] furthers the development and 94 specification of Internet technology through the general discussion 95 of topics for which no dedicated mailing lists exists. As this is 96 the most general IETF mailing list, considerable latitude is allowed. 97 Advertising, whether to solicit business or promote employment 98 opportunities, falls well outside the range of acceptable topics, as 99 do discussions of a personal nature. 101 The IETF Note Well [NOTE-WELL] applies to discussions on the IETF 102 discussion list and all other IETF mailing lists, and requires 103 conformance with the IETF Guidelines for Conduct [RFC7154] and the 104 Anti-Harassment Policy [IETF-AHP], among others. 106 2. Charter for the IETF Discussion List 108 This list is meant for initial technical discussion only. 109 Discussions that fall within the area of any working group, area or 110 well established list should be moved to such more specific forums as 111 soon as this is pointed out. 113 When no dedicated mailing list exists, it may be preferable to 114 request the creation of one [NON-WG-LISTS] and only announce the 115 availability of the new list on the IETF discussion list. 117 In addition to the topics noted above, appropriate postings include: 119 * Initial discussion of technical issues that are candidates for 120 IETF work, but have not yet identified appropriate mailing lists. 122 * Questions and clarifications concerning IETF meetings, although 123 most of these topics are better brought up on the discussion list 124 for IETF LLC administrative issues [ADMIN-DISCUSS] or the attendee 125 discussion list for a given IETF meeting, such as 126 [IETF110-ATTENDEES] for IETF-110. 128 * Announcements of conferences, events, or activities that are 129 sponsored or endorsed by the Internet Society or IETF, although 130 the IETF announcement list [IETF-ANNOUNCE] is the preferred list 131 for these. 133 These topics used to be in scope for the IETF discussion list, but 134 have since moved to dedicated lists: 136 * Last Call discussions of proposed protocol actions now take place 137 on the IETF Last Calls mailing list [LAST-CALLS]. 139 * Discussion of IETF administrative policies now take place on the 140 discussion list for IETF LLC administrative issues 141 [ADMIN-DISCUSS]. 143 Inappropriate postings include: 145 * Unsolicited bulk e-mail 147 * Discussion of subjects unrelated to IETF policy, meetings, 148 activities, or technical concerns 150 * Unprofessional commentary, regardless of the general subject 152 * Announcements of conferences, events, or activities that are not 153 sponsored or endorsed by the Internet Society or IETF. 155 3. Security Considerations 157 The IETF Chair, the IETF Executive Director, or a sergeant-at-arms 158 [SAA-SOP] appointed by the Chair is empowered to restrict posting by 159 a person, or of a thread, when the content is inappropriate and 160 represents a pattern of abuse [SAA-UPC]. They are encouraged to take 161 into account the overall nature of the postings by an individual and 162 whether particular postings are an aberration or typical. Complaints 163 regarding their decisions should be referred to the IAB. 165 4. IANA Considerations 167 This document does not request any IANA actions. 169 5. References 171 5.1. Normative References 173 [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, 174 RFC 3005, DOI 10.17487/RFC3005, November 2000, 175 . 177 5.2. Informative References 179 [ADMIN-DISCUSS] 180 IETF, "Discussion List for IETF LLC Administrative 181 Issues", n.d., 182 . 184 [IETF-AHP] IETF, "IETF Anti-Harassment Policy", n.d., 185 . 188 [IETF-ANNOUNCE] 189 IETF, "IETF Announcement List", n.d., 190 . 192 [IETF-DISCUSS] 193 IETF, "IETF Discussion List", n.d., 194 . 196 [IETF110-ATTENDEES] 197 IETF, "Mailing List for IETF 110 Attendees", n.d., 198 . 200 [LAST-CALLS] 201 IETF, "IETF Last Calls", n.d., 202 . 204 [NON-WG-LISTS] 205 IETF, "Non-Working Group Email List Guidelines", n.d., 206 . 208 [NOTE-WELL] 209 IETF, "Note Well", n.d., 210 . 212 [RFC7154] Moonesamy, S., Ed., "IETF Guidelines for Conduct", BCP 54, 213 RFC 7154, DOI 10.17487/RFC7154, March 2014, 214 . 216 [SAA-SOP] IETF Sergeants-at-Arms, "Sergeant-at-Arms Standard 217 Operating Procedures", n.d., 218 . 220 [SAA-UPC] IETF Sergeants-at-Arms, "Unprofessional commentary", n.d., 221 . 224 Appendix A. Acknowledgements 226 Susan R. Harris authored [RFC3005], which this document replaces. 228 Appendix B. Changes 230 B.1. Since draft-eggert-bcp45bis-00 232 * added introduction, security considerations and IANA 233 considerations sections 235 * added "note to readers" with pointers to the discussion list and 236 the repo 238 * added references to IETF Sergeants-at-Arms procedures 240 * added references to various mailing lists for topics that used to 241 be in scope for the IETF discussion list but no longer are 243 * added references to the Note Well and relevant other policies that 244 apply 246 B.2. Since RFC3005 248 * converted to Markdown and xml2rfc v3 250 * updated references (as part of the conversion) 252 * updated author information 254 * various formatting changes 256 Author's Address 258 Lars Eggert 259 NetApp 260 Stenbergintie 12 B 261 FI-02700 Kauniainen 262 Finland 264 Email: lars@eggert.org 265 URI: https://eggert.org/