Internet-Draft | IETF Discussion List Charter | June 2021 |
Eggert | Expires 25 December 2021 | [Page] |
The Internet Engineering Task Force (IETF) discussion mailing list furthers the development and specification of Internet technology through the general discussion of topics for which no dedicated mailing lists exists. As this is the most general IETF mailing list, considerable latitude is allowed, but there are posts that are unsuitable for this mailing list.¶
This document obsoletes RFC3005.¶
Discussion of this draft takes place on the GENDISPATCH working group mailing list, which is archived at https://mailarchive.ietf.org/arch/browse/gendispatch/.¶
Working Group information can be found at https://datatracker.ietf.org/wg/gendispatch/; source code and the issues list for this draft can be found at https://github.com/larseggert/bcp45bis.¶
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 25 December 2021.¶
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.¶
The IETF discussion list [IETF-DISCUSS] furthers the development and specification of Internet technology through the general discussion of topics for which no dedicated mailing lists exists. As this is the most general IETF mailing list, considerable latitude is allowed. However, there are posts 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 [IETF-AHP], among others.¶
The IETF discussion list is meant for discussions for which a more appropriate list does not exists, such as discussions that do not fall within the area of any working group, area or other established list. When discussions are started on the IETF discussion list for which such venues do exist, they should be moved there as soon as this is pointed out.¶
When no dedicated mailing list exists, it may be preferable to request the creation of one [NON-WG-LISTS] and only announce the availability of the new list on the IETF discussion list and on other related lists, such as area lists.¶
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:¶
The IETF Chair, the IETF Executive Director, or a sergeant-at-arms [SAA-SOP] appointed by the Chair is empowered to restrict posting by a person, or of a thread, when the content is inappropriate and represents a pattern of abuse [SAA-UPC]. 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. Complaints regarding their decisions should be referred to the IAB.¶
This document does not request any IANA actions.¶
Susan R. Harris authored [RFC3005], which this document replaces.¶