<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="bcp" consensus="true" docName="draft-eggert-bcp45bis-08" indexInclude="true" ipr="pre5378Trust200902" number="9245" obsoletes="3005" prepTime="2022-06-21T15:26:00" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" updates="3683">
  <link href="https://datatracker.ietf.org/doc/draft-eggert-bcp45bis-08" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9245" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title>IETF Discussion List Charter</title>
    <seriesInfo name="RFC" value="9245" stream="IETF"/>
    <seriesInfo name="BCP" value="45" stream="IETF"/>
    <author initials="L." surname="Eggert" fullname="Lars Eggert">
      <organization showOnFrontPage="true">NetApp</organization>
      <address>
        <postal>
          <street>Stenbergintie 12 B</street>
          <city>Kauniainen</city>
          <code>02700</code>
          <country>FI</country>
        </postal>
        <email>lars@eggert.org</email>
        <uri>https://eggert.org/</uri>
      </address>
    </author>
    <author initials="S." surname="Harris" fullname="Susan Harris">
      <organization showOnFrontPage="true"/>
      <address>
      </address>
    </author>
    <date month="06" year="2022"/>
    <keyword>mail list</keyword>
    <keyword>mailing list</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">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 exist. 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.</t>
      <t indent="0" pn="section-abstract-2">This document obsoletes RFC 3005 and updates RFC 3683.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This memo documents an Internet Best Current Practice.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further information
            on BCPs is available in Section 2 of RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9245" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2022 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) 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 Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
        <t indent="0" pn="section-boilerplate.2-3">
            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.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-charter-for-the-ietf-discus">Charter for the IETF Discussion List</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-moderation">Moderation</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2">
              <li pn="section-toc.1-1.6.2.1">
                <t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.2">
                <t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="intro" numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">The IETF discussion list <xref target="IETF-DISCUSS" format="default" sectionFormat="of" derivedContent="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 exist. 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.</t>
      <t indent="0" pn="section-1-2">The IETF Note Well <xref target="NOTE-WELL" format="default" sectionFormat="of" derivedContent="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 <xref target="RFC7154" format="default" sectionFormat="of" derivedContent="RFC7154"/> and the Anti-Harassment Policy <xref target="RFC7776" format="default" sectionFormat="of" derivedContent="RFC7776"/>,
among others.</t>
      <t indent="0" pn="section-1-3">This document obsoletes <xref target="RFC3005" format="default" sectionFormat="of" derivedContent="RFC3005"/>, as it documents the use of other mailing
lists for discussions that were previously in scope for the IETF discussion list,
refers to applicable policies such as the Guidelines for Conduct
<xref target="RFC7154" format="default" sectionFormat="of" derivedContent="RFC7154"/> and the Anti-Harassment Policy <xref target="RFC7776" format="default" sectionFormat="of" derivedContent="RFC7776"/>, and clarifies
moderation procedures. It also updates part of <xref section="1" sectionFormat="of" target="RFC3683" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3683#section-1" derivedContent="RFC3683"/>, which
copies the list of "inappropriate postings" from <xref target="RFC3005" format="default" sectionFormat="of" derivedContent="RFC3005"/>. The list in
<xref target="RFC3683" format="default" sectionFormat="of" derivedContent="RFC3683"/> is hence updated by the new list in <xref target="charter" format="default" sectionFormat="of" derivedContent="Section 2"/>.</t>
    </section>
    <section anchor="charter" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-charter-for-the-ietf-discus">Charter for the IETF Discussion List</name>
      <t indent="0" pn="section-2-1">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 there is an existing venue 
for discussion, this should be noted and discussion should be moved there.</t>
      <t indent="0" pn="section-2-2">When no dedicated mailing list exists for a topic, it may be preferable to
request that one be created <xref target="NON-WG-LISTS" format="default" sectionFormat="of" derivedContent="NON-WG-LISTS"/> rather than discuss it on
the IETF discussion list.  Availability of the new list
may be announced on the IETF discussion list and on other
related lists, such as area lists.</t>
      <t indent="0" pn="section-2-3">Appropriate postings to the IETF discussion list include:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2-4">
        <li pn="section-2-4.1">Initial discussion of technical issues that are candidates for IETF work, but
appropriate mailing lists have not yet been identified.</li>
        <li pn="section-2-4.2">Questions and clarifications concerning practical aspects of IETF meetings,
although most of these topics are better brought up on the discussion list for
IETF LLC administrative issues <xref target="ADMIN-DISCUSS" format="default" sectionFormat="of" derivedContent="ADMIN-DISCUSS"/> or the attendee discussion
list for a given IETF meeting.</li>
        <li pn="section-2-4.3">Announcements of conferences, events, or activities that are sponsored or
endorsed by the IETF, IRTF, IAB or the Internet Society, although the IETF
announcement list <xref target="IETF-ANNOUNCE" format="default" sectionFormat="of" derivedContent="IETF-ANNOUNCE"/> is the preferred list for these.</li>
        <li pn="section-2-4.4">Discussions of IETF direction, policy, and the standards process in general,
when a more suitable list (such as the discussion list for IETF LLC
administrative issues <xref target="ADMIN-DISCUSS" format="default" sectionFormat="of" derivedContent="ADMIN-DISCUSS"/>, the IAB discussion list for
architectural issues <xref target="ARCH-DISCUSS" format="default" sectionFormat="of" derivedContent="ARCH-DISCUSS"/>, a meeting attendees list, a
process-oriented WG list, etc.) cannot be identified.</li>
      </ul>
      <t indent="0" pn="section-2-5">These topics used to be in scope for the IETF discussion list, but have since
moved to dedicated lists:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2-6">
        <li pn="section-2-6.1">Last Call discussions of documents now take place on the IETF
Last Calls mailing list <xref target="LAST-CALLS" format="default" sectionFormat="of" derivedContent="LAST-CALLS"/>.</li>
        <li pn="section-2-6.2">Discussion of IETF administrative policies now takes place on the discussion
list for IETF LLC administrative issues <xref target="ADMIN-DISCUSS" format="default" sectionFormat="of" derivedContent="ADMIN-DISCUSS"/>.</li>
      </ul>
      <t indent="0" pn="section-2-7">Inappropriate postings include:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2-8">
        <li pn="section-2-8.1">Advertising and other unsolicited bulk e-mail</li>
        <li pn="section-2-8.2">Discussion of subjects unrelated to IETF policy, meetings, activities, or
technical topics</li>
        <li pn="section-2-8.3">Uncivil commentary, regardless of the general subject, per the IETF Note Well
<xref target="NOTE-WELL" format="default" sectionFormat="of" derivedContent="NOTE-WELL"/></li>
        <li pn="section-2-8.4">Announcements of conferences, events, or activities that are not sponsored or
endorsed by the IETF, IRTF, IAB, or the Internet Society.</li>
      </ul>
    </section>
    <section anchor="mod" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-moderation">Moderation</name>
      <t indent="0" pn="section-3-1">The IETF Chair appoints <em>Moderators</em> (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 typical or an aberration.</t>
      <t indent="0" pn="section-3-2">Moderation of the IETF discussion list, including the handling of any appeals,
is guided by the IETF discussion list charter specified in
<xref target="charter" format="default" sectionFormat="of" derivedContent="Section 2"/>, and the related guidance from <xref target="intro" format="default" sectionFormat="of" derivedContent="Section 1"/> that applies to all mailing
lists. The moderators are selected from within the community to moderate 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.</t>
      <t indent="0" pn="section-3-3">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 <xref target="MOD-SOP" format="default" sectionFormat="of" derivedContent="MOD-SOP"/> and abuse patterns <xref target="MOD-UPC" format="default" sectionFormat="of" derivedContent="MOD-UPC"/>.
The moderator team should reach out to the
IETF Chair for any conflict resolution in a timely manner.</t>
      <t indent="0" pn="section-3-4">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
<xref target="RFC2026" format="default" sectionFormat="of" derivedContent="RFC2026"/>. Decisions by the IETF Chair can be appealed to the IESG as whole,
again per <xref target="RFC2026" format="default" sectionFormat="of" derivedContent="RFC2026"/>.</t>
    </section>
    <section anchor="security-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-4-1">The usual security considerations <xref target="RFC3552" format="default" sectionFormat="of" derivedContent="RFC3552"/> do not apply to this document.</t>
      <t indent="0" pn="section-4-2">Potential abuse of the moderation process for the suppression of undesired
opinions is counteracted by the availability of an appeals process, per
<xref target="mod" format="default" sectionFormat="of" derivedContent="Section 3"/>.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-5-1">This document does not request any IANA actions.</t>
    </section>
  </middle>
  <back>
    <references pn="section-6">
      <name slugifiedName="name-references">References</name>
      <references pn="section-6.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC2026" target="https://www.rfc-editor.org/info/rfc2026" quoteTitle="true" derivedAnchor="RFC2026">
          <front>
            <title>The Internet Standards Process -- Revision 3</title>
            <author initials="S." surname="Bradner" fullname="S. Bradner">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1996" month="October"/>
            <abstract>
              <t indent="0">This memo documents the process used by the Internet community for the standardization of protocols and procedures.  It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="9"/>
          <seriesInfo name="RFC" value="2026"/>
          <seriesInfo name="DOI" value="10.17487/RFC2026"/>
        </reference>
      </references>
      <references pn="section-6.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="ADMIN-DISCUSS" target="https://ietf.org/mailman/listinfo/admin-discuss" quoteTitle="true" derivedAnchor="ADMIN-DISCUSS">
          <front>
            <title>admin-discuss -- Discussion list for IETF LLC administrative issues</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
          </front>
        </reference>
        <reference anchor="ARCH-DISCUSS" target="https://ietf.org/mailman/listinfo/architecture-discuss" quoteTitle="true" derivedAnchor="ARCH-DISCUSS">
          <front>
            <title>Architecture-discuss -- open discussion forum for long/wide-range architectural issues</title>
            <author>
              <organization showOnFrontPage="true">IAB</organization>
            </author>
          </front>
        </reference>
        <reference anchor="IETF-ANNOUNCE" target="https://ietf.org/mailman/listinfo/ietf-announce" quoteTitle="true" derivedAnchor="IETF-ANNOUNCE">
          <front>
            <title>IETF-Announce -- IETF announcement list. No discussions.</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
          </front>
        </reference>
        <reference anchor="IETF-DISCUSS" target="https://ietf.org/mailman/listinfo/ietf" quoteTitle="true" derivedAnchor="IETF-DISCUSS">
          <front>
            <title>ietf -- IETF-Discussion</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
          </front>
        </reference>
        <reference anchor="LAST-CALLS" target="https://ietf.org/mailman/listinfo/last-call" quoteTitle="true" derivedAnchor="LAST-CALLS">
          <front>
            <title>last-call -- IETF Last Calls</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
          </front>
        </reference>
        <reference anchor="MOD-SOP" target="https://github.com/ietf/saa/blob/main/sop.md" quoteTitle="true" derivedAnchor="MOD-SOP">
          <front>
            <title>Sergeant-at-Arms Standard Operating Procedures</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
            <date year="2019" month="October" day="09"/>
          </front>
          <seriesInfo name="commit c1abcb0" value=""/>
        </reference>
        <reference anchor="MOD-UPC" target="https://github.com/ietf/saa/blob/main/unprofessional-commentary.md" quoteTitle="true" derivedAnchor="MOD-UPC">
          <front>
            <title>Unprofessional commentary</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
            <date year="2019" month="October" day="08"/>
          </front>
          <seriesInfo name="commit e120305" value=""/>
        </reference>
        <reference anchor="NON-WG-LISTS" target="https://ietf.org/how/lists/nonwglist-guidelines/" quoteTitle="true" derivedAnchor="NON-WG-LISTS">
          <front>
            <title>Non-Working Group Email List Guidelines</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
          </front>
        </reference>
        <reference anchor="NOTE-WELL" target="https://ietf.org/about/note-well/" quoteTitle="true" derivedAnchor="NOTE-WELL">
          <front>
            <title>Note Well</title>
            <author>
              <organization showOnFrontPage="true">IETF</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC3005" target="https://www.rfc-editor.org/info/rfc3005" quoteTitle="true" derivedAnchor="RFC3005">
          <front>
            <title>IETF Discussion List Charter</title>
            <author initials="S." surname="Harris" fullname="S. Harris">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2000" month="November"/>
            <abstract>
              <t indent="0">The Internet Engineering Task Force (IETF) discussion mailing list furthers the development and specification of Internet technology through discussion of technical issues, and hosts discussions of IETF direction, policy, meetings, and procedures.  As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="45"/>
          <seriesInfo name="RFC" value="3005"/>
          <seriesInfo name="DOI" value="10.17487/RFC3005"/>
        </reference>
        <reference anchor="RFC3160" target="https://www.rfc-editor.org/info/rfc3160" quoteTitle="true" derivedAnchor="RFC3160">
          <front>
            <title>The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force</title>
            <author initials="S." surname="Harris" fullname="S. Harris">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2001" month="August"/>
            <abstract>
              <t indent="0">This document describes the inner workings of IETF meetings and Working Groups, discusses organizations related to the IETF, and introduces the standards process.  This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3160"/>
          <seriesInfo name="DOI" value="10.17487/RFC3160"/>
        </reference>
        <reference anchor="RFC3184" target="https://www.rfc-editor.org/info/rfc3184" quoteTitle="true" derivedAnchor="RFC3184">
          <front>
            <title>IETF Guidelines for Conduct</title>
            <author initials="S." surname="Harris" fullname="S. Harris">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2001" month="October"/>
            <abstract>
              <t indent="0">This document provides a set of guidelines for personal interaction in the Internet Engineering Task Force.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3184"/>
          <seriesInfo name="DOI" value="10.17487/RFC3184"/>
        </reference>
        <reference anchor="RFC3552" target="https://www.rfc-editor.org/info/rfc3552" quoteTitle="true" derivedAnchor="RFC3552">
          <front>
            <title>Guidelines for Writing RFC Text on Security Considerations</title>
            <author initials="E." surname="Rescorla" fullname="E. Rescorla">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Korver" fullname="B. Korver">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2003" month="July"/>
            <abstract>
              <t indent="0">All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak.  This document provides guidelines to RFC authors on how to write a good Security Considerations section.   This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="72"/>
          <seriesInfo name="RFC" value="3552"/>
          <seriesInfo name="DOI" value="10.17487/RFC3552"/>
        </reference>
        <reference anchor="RFC3683" target="https://www.rfc-editor.org/info/rfc3683" quoteTitle="true" derivedAnchor="RFC3683">
          <front>
            <title>A Practice for Revoking Posting Rights to IETF Mailing Lists</title>
            <author initials="M." surname="Rose" fullname="M. Rose">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2004" month="March"/>
            <abstract>
              <t indent="0">All self-governing bodies have ways of managing the scope of participant interaction.  The IETF uses a consensus-driven process for developing computer-communications standards in an open fashion.  An important part of this consensus-driven process is the pervasive use of mailing lists for discussion.  Notably, in a small number of cases, a participant has engaged in a "denial-of-service" attack to disrupt the consensus-driven process.  Regrettably, as these bad faith attacks become more common, the IETF needs to establish a practice that reduces or eliminates these attacks.  This memo recommends such a practice for use by the IETF.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="83"/>
          <seriesInfo name="RFC" value="3683"/>
          <seriesInfo name="DOI" value="10.17487/RFC3683"/>
        </reference>
        <reference anchor="RFC7154" target="https://www.rfc-editor.org/info/rfc7154" quoteTitle="true" derivedAnchor="RFC7154">
          <front>
            <title>IETF Guidelines for Conduct</title>
            <author initials="S." surname="Moonesamy" fullname="S. Moonesamy" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="March"/>
            <abstract>
              <t indent="0">This document provides a set of guidelines for personal interaction in the Internet Engineering Task Force.  The guidelines recognize the diversity of IETF participants, emphasize the value of mutual respect, and stress the broad applicability of our work.</t>
              <t indent="0">This document is an updated version of the guidelines for conduct originally published in RFC 3184.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="54"/>
          <seriesInfo name="RFC" value="7154"/>
          <seriesInfo name="DOI" value="10.17487/RFC7154"/>
        </reference>
        <reference anchor="RFC7776" target="https://www.rfc-editor.org/info/rfc7776" quoteTitle="true" derivedAnchor="RFC7776">
          <front>
            <title>IETF Anti-Harassment Procedures</title>
            <author initials="P." surname="Resnick" fullname="P. Resnick">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Farrel" fullname="A. Farrel">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2016" month="March"/>
            <abstract>
              <t indent="0">IETF Participants must not engage in harassment while at IETF meetings, virtual meetings, or social events or while participating in mailing lists.  This document lays out procedures for managing and enforcing this policy.</t>
              <t indent="0">This document updates RFC 2418 by defining new working group guidelines and procedures.  This document updates RFC 7437 by allowing the Ombudsteam to form a recall petition without further signatories.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="25"/>
          <seriesInfo name="RFC" value="7776"/>
          <seriesInfo name="DOI" value="10.17487/RFC7776"/>
        </reference>
      </references>
    </references>
    <section numbered="false" anchor="acknowledgements" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1"><contact fullname="Susan R. Harris"/> authored <xref target="RFC3005" format="default" sectionFormat="of" derivedContent="RFC3005"/>, which this document replaces. In addition
to many technical contributions to the IETF, Susan authored a number of other
foundational documents, such as the original "IETF Guidelines for Conduct"
<xref target="RFC3184" format="default" sectionFormat="of" derivedContent="RFC3184"/> and the original "Tao of the IETF" <xref target="RFC3160" format="default" sectionFormat="of" derivedContent="RFC3160"/>.  Susan R. Harris
passed away in early 2022. This document is dedicated to her
memory, as a small token of appreciation of her many contributions.</t>
      <t indent="0" pn="section-appendix.a-2">The following people have made other contributions to this document:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-appendix.a-3">
        <li pn="section-appendix.a-3.1">
          <t indent="0" pn="section-appendix.a-3.1.1"><contact fullname="Adrian Farrel"/></t>
        </li>
        <li pn="section-appendix.a-3.2">
          <t indent="0" pn="section-appendix.a-3.2.1"><contact fullname="Barry Leiba"/></t>
        </li>
        <li pn="section-appendix.a-3.3">
          <t indent="0" pn="section-appendix.a-3.3.1"><contact fullname="Ben Kaduk"/></t>
        </li>
        <li pn="section-appendix.a-3.4">
          <t indent="0" pn="section-appendix.a-3.4.1"><contact fullname="Brian Carpenter"/></t>
        </li>
        <li pn="section-appendix.a-3.5">
          <t indent="0" pn="section-appendix.a-3.5.1"><contact fullname="Carsten Bormann"/></t>
        </li>
        <li pn="section-appendix.a-3.6">
          <t indent="0" pn="section-appendix.a-3.6.1"><contact fullname="Christian Huitema"/></t>
        </li>
        <li pn="section-appendix.a-3.7">
          <t indent="0" pn="section-appendix.a-3.7.1"><contact fullname="Dhruv Dhody"/></t>
        </li>
        <li pn="section-appendix.a-3.8">
          <t indent="0" pn="section-appendix.a-3.8.1"><contact fullname="Eric Rescorla"/></t>
        </li>
        <li pn="section-appendix.a-3.9">
          <t indent="0" pn="section-appendix.a-3.9.1"><contact fullname="Eric Vyncke"/></t>
        </li>
        <li pn="section-appendix.a-3.10">
          <t indent="0" pn="section-appendix.a-3.10.1"><contact fullname="Francesca Palombini"/></t>
        </li>
        <li pn="section-appendix.a-3.11">
          <t indent="0" pn="section-appendix.a-3.11.1"><contact fullname="John Scudder"/></t>
        </li>
        <li pn="section-appendix.a-3.12">
          <t indent="0" pn="section-appendix.a-3.12.1"><contact fullname="Lloyd Wood"/></t>
        </li>
        <li pn="section-appendix.a-3.13">
          <t indent="0" pn="section-appendix.a-3.13.1"><contact fullname="Martin Thomson"/></t>
        </li>
        <li pn="section-appendix.a-3.14">
          <t indent="0" pn="section-appendix.a-3.14.1"><contact fullname="Robert Wilton"/></t>
        </li>
        <li pn="section-appendix.a-3.15">
          <t indent="0" pn="section-appendix.a-3.15.1"><contact fullname="Subramanian Moonesamy"/></t>
        </li>
        <li pn="section-appendix.a-3.16">
          <t indent="0" pn="section-appendix.a-3.16.1"><contact fullname="Stephen Farrell"/></t>
        </li>
      </ul>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author initials="L." surname="Eggert" fullname="Lars Eggert">
        <organization showOnFrontPage="true">NetApp</organization>
        <address>
          <postal>
            <street>Stenbergintie 12 B</street>
            <city>Kauniainen</city>
            <code>02700</code>
            <country>FI</country>
          </postal>
          <email>lars@eggert.org</email>
          <uri>https://eggert.org/</uri>
        </address>
      </author>
      <author initials="S." surname="Harris" fullname="Susan Harris">
        <organization showOnFrontPage="true"/>
        <address>
      </address>
      </author>
    </section>
  </back>
</rfc>
