RFC 3005

RFC 3005: IETF Discussion List Charter ✨

okay bestie, here's the tea 🫖 This is RFC 3005, the IETF Discussion List Charter, written by Susan R. Harris at Merit Network 🎀 It was published in November 2000 and it's a Best Current Practice (that's BCP 45 🌸). The title block doesn't list anything it obsoletes or updates, so there's nothing to flag there 🫶

Status of this Memo

This document specifies an Internet Best Current Practice for the Internet Community, and it's asking for discussion and suggestions for improvements 💬 Distribution of this memo is unlimited, so share away ✨

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved. 💜

Abstract

The IETF discussion mailing list is where people get the Internet's technical stuff developed and specified 🧚 It's for talking through technical issues, and it also hosts chats about IETF direction, policy, meetings, and procedures. Since it's the most general IETF mailing list, it's got a lot of room for different topics 🌈 Advertising, whether it's trying to sell something or promote a job, is way outside what's allowed 💀 Personal discussions are out too.

Charter for the IETF Discussion List

The IETF discussion list lives at ietf@ietf.org and it has two jobs 👑 First, it helps develop and specify Internet technology by discussing technical issues. Second, it hosts discussions about IETF direction, policy, meetings, and procedures. Because it's the most general IETF list, there's considerable latitude 🦋 Advertising, whether to solicit business or promote employment opportunities, is well outside the acceptable topics, and so are discussions of a personal nature 🙈

This list is meant for initial discussion only 🌸 If a conversation belongs to a working group or a well-established list, it should be moved to that more specific forum as soon as someone points it out. The exception is an issue where the working group actually needs wider input or direction 🫶

Besides the topics above, appropriate posts include:

• Last Call discussions of proposed protocol actions 🔥
• Discussion of technical issues that could become IETF work but don't have a proper email home yet 🧚
• Discussion of IETF administrative policies 📋
• Questions and clarifications about IETF meetings 🎀
• Announcements of conferences, events, or activities that are sponsored or endorsed by the Internet Society or IETF ✨

Inappropriate posts include:

• Unsolicited bulk e-mail 💀
• Discussion of subjects unrelated to IETF policy, meetings, activities, or technical concerns 🙅
• Unprofessional commentary, no matter the general subject 😭
• Announcements of conferences, events, or activities that are not sponsored or endorsed by the Internet Society or IETF 💅

The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed by the Chair can restrict posting by a person, or restrict a thread, when the content is inappropriate and represents a pattern of abuse ⚠️ They're encouraged to look at the overall nature of a person's posts and whether a particular post is a one-off or the norm. Complaints about their decisions should go to the IAB 🌈

Acknowledgements

Big thanks to Donald E. Eastlake 3rd and the other members of the IETF POISSON working group for their comments 🫶💖

Author's Address

Susan R. Harris Merit Network, Inc. 4251 Plymouth Rd., Suite C Ann Arbor, MI 48105-2785

Phone: (734) 936-2100 Fax: (734) 647-3185 EMail: srh@merit.edu 📬

Full Copyright Statement

Copyright (C) The Internet Society (2000). All Rights Reserved. 🌷

This document and translations of it may be copied and shared with others. Derivative works that comment on or explain it, or help with implementing it, may be prepared, copied, published, and distributed, in whole or in part, with no restrictions of any kind 💜 That's allowed as long as the above copyright notice and this paragraph are included on every copy and derivative work. However, this document itself may not be modified in any way, such as by removing the copyright notice or the references to the Internet Society or other Internet organizations. The exceptions are when it's needed for developing Internet standards, in which case the copyright procedures in the Internet Standards process must be followed, or when it's being translated into a language other than English 🌍

The permissions above are perpetual and won't be revoked by the Internet Society or its successors or assigns ♾️

This document and the information in it are provided on an "AS IS" basis, and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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 😭

Acknowledgement

Funding for the RFC Editor function is currently provided by the Internet Society 🎀