Internet-Draft IETF Discussion List Charter February 2022
Eggert Expires 28 August 2022 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-eggert-bcp45bis-08
Obsoletes:
3005 (if approved)
Updates:
3683 (if approved)
Published:
Intended Status:
Best Current Practice
Expires:
Author:
L. Eggert
NetApp

IETF Discussion List Charter

Abstract

The Internet Engineering Task Force (IETF) discussion mailing list furthers the development and specification of Internet technology through the general discussion of technical, procedural, operational and other topics for which no dedicated mailing lists exists. As this is the most general IETF mailing list, considerable latitude in terms of topics is allowed, but there are posts and topics that are unsuitable for this mailing list. This document defines the charter for the IETF discussion list and explains its scope.

This document obsoletes RFC3005 and updates RFC3683.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

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."

This Internet-Draft will expire on 28 August 2022.

Table of Contents

1. Introduction

The IETF discussion list [IETF-DISCUSS] furthers the development and specification of Internet technology through the general discussion of technical, procedural, operational and other topics for which no dedicated mailing lists exists. As this is the most general IETF mailing list, considerable latitude in terms of topics is allowed. However, there are posts and topics that are unsuitable for this mailing list. This document defines the charter for the IETF discussion list and explains its scope.

The IETF Note Well [NOTE-WELL] applies to discussions on the IETF discussion list and all other IETF mailing lists, and requires conformance with the IETF Guidelines for Conduct [RFC7154] and the Anti-Harassment Policy [RFC7776], among others.

This document obsoletes [RFC3005], documenting the use of other mailing lists for discussions that used to be in scope for the IETF discussion list, referring to applicable policies such as the Guidelines for Conduct [RFC7154] and the Anti-Harassment Policy [RFC7776], and clarifying moderation procedures. It also updates part of Section 1 of [RFC3683], which copies the list of "inappropriate postings" from [RFC3005]. This list in [RFC3683] is hence updated by the new list in Section 2 below.

2. Charter for the IETF Discussion List

The IETF discussion list is meant for discussions for which a more appropriate list does not exist, such as discussions that do not fall within the scope of any working group, area, or other established list. When discussions are started on the IETF discussion list for which such a venue does exist, they should be continued at that other venue as soon as this is pointed out.

When no dedicated mailing list exists for a topic, it may be preferable to request the creation of one [NON-WG-LISTS] and announce the availability of the new list on the IETF discussion list and on other related lists, such as area lists, rather than discussing that topic on the IETF discussion list.

Appropriate postings to the IETF discussion list include:

These topics used to be in scope for the IETF discussion list, but have since moved to dedicated lists:

Inappropriate postings include:

3. Moderation

The IETF Chair appoints Moderators (previously known as the "sergeant-at-arms") for the IETF discussion list that are empowered to restrict posting by a person, or to an email thread, when the content is inappropriate and represents a pattern of abuse. They are encouraged to take into account the overall nature of the postings by an individual and whether particular postings are an aberration or typical.

Moderation of the IETF discussion list, including the handling of any appeals, is to be guided by the IETF discussion list charter specified in Section 2, and the related guidance from Section 1 that applies to all mailing lists. The moderators are intended to establish a self-moderation function on the community, by the community. Because the IESG and IAB are in the appeals chain for moderator decisions (see below), the IETF Chair therefore should not appoint a moderator who is serving in such a role. If a moderator is selected for the IESG or IAB, they will step down from the moderator team.

Apart from appointing moderators, the IETF Chair should refrain from the day-to-day operation and management of the moderator team. The moderator team will independently define, publish, and execute their role; see the current set of operating procedures [MOD-SOP] and abuse patterns [MOD-UPC]. The moderator team should reach out to the IETF Chair for any conflict resolution in a timely manner.

Because a moderator serves at the discretion of the IETF Chair - even if the IETF Chair is not otherwise involved in the operation of the moderator team - any moderator decision can be appealed to the IETF Chair, per [RFC2026]. Decisions by the IETF Chair can be appealed to the IESG as whole, again per [RFC2026].

4. Security Considerations

The usual security considerations [RFC3552] do not apply to this document.

Potential abuse of the moderation process for the suppression of undesired opinions is counteracted by the availability of an appeals process, per Section 3.

5. IANA Considerations

This document does not request any IANA actions.

6. References

6.1. Normative References

[RFC2026]
Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, , <https://www.rfc-editor.org/rfc/rfc2026>.

6.2. Informative References

[ADMIN-DISCUSS]
IETF, "Discussion List for IETF LLC Administrative Issues", , <https://ietf.org/mailman/listinfo/admin-discuss>.
[ARCH-DISCUSS]
IAB, "Open Discussion Forum For Long/Wide-Range Architectural Issues", , <https://ietf.org/mailman/listinfo/architecture-discuss>.
[IETF-ANNOUNCE]
IETF, "IETF Announcement List", , <https://ietf.org/mailman/listinfo/ietf-announce>.
[IETF-DISCUSS]
IETF, "IETF Discussion List", , <https://ietf.org/mailman/listinfo/ietf>.
[LAST-CALLS]
IETF, "IETF Last Calls", , <https://ietf.org/mailman/listinfo/last-call>.
[MOD-SOP]
IETF Discussion List Moderator Team, "IETF Discussion List Moderator Team Standard Operating Procedures", , <https://github.com/ietf/saa/blob/main/sop.md>.
[MOD-UPC]
IETF Discussion List Moderator Team, "Unprofessional Commentary", , <https://github.com/ietf/saa/blob/main/unprofessional-commentary.md>.
[NON-WG-LISTS]
IETF, "Non-Working Group Email List Guidelines", , <https://ietf.org/how/lists/nonwglist-guidelines/>.
[NOTE-WELL]
IETF, "Note Well", , <https://ietf.org/about/note-well/>.
[RFC3005]
Harris, S., "IETF Discussion List Charter", BCP 45, RFC 3005, DOI 10.17487/RFC3005, , <https://www.rfc-editor.org/rfc/rfc3005>.
[RFC3552]
Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/rfc/rfc3552>.
[RFC3683]
Rose, M., "A Practice for Revoking Posting Rights to IETF Mailing Lists", BCP 83, RFC 3683, DOI 10.17487/RFC3683, , <https://www.rfc-editor.org/rfc/rfc3683>.
[RFC7154]
Moonesamy, S., Ed., "IETF Guidelines for Conduct", BCP 54, RFC 7154, DOI 10.17487/RFC7154, , <https://www.rfc-editor.org/rfc/rfc7154>.
[RFC7776]
Resnick, P. and A. Farrel, "IETF Anti-Harassment Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, , <https://www.rfc-editor.org/rfc/rfc7776>.

Appendix A. Changes

A.2. Since draft-eggert-bcp45bis-07

A.3. Since draft-eggert-bcp45bis-06

  • applied a suggestion from Lloyd Wood to add access dates to cited URLs
  • fixes to this change log
  • applied a suggestion from Brian Carpenter to change "unprofessional" to "uncivil"

A.7. Since draft-eggert-bcp45bis-02

  • additional details about and guidelines for the SAA team, based on a suggestion from Dhruv Dhody
  • remove reference to the IETF 110 attendees list, since those lists are being removed by the secretariat shortly after each meeting

A.9. Since draft-eggert-bcp45bis-00

  • added introduction, security considerations and IANA considerations sections
  • added "note to readers" with pointers to the discussion list and the repo
  • added references to IETF Sergeants-at-Arms procedures
  • added references to various mailing lists for topics that used to be in scope for the IETF discussion list but no longer are
  • added references to the Note Well and relevant other policies that apply

A.10. Since RFC3005

  • converted to Markdown and xml2rfc v3
  • updated references (as part of the conversion)
  • updated author information
  • various formatting changes

Acknowledgements

The following people have made contributions to this document:

Susan R. Harris authored [RFC3005], which this document replaces.

Author's Address

Lars Eggert
NetApp
Stenbergintie 12 B
FI-02700 Kauniainen
Finland

mirror server hosted at Truenetwork, Russian Federation.