<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" submissionType="IETF" ipr="trust200902" docName="draft-halpern-gendispatch-antitrust-09" number="9680" consensus="true" xml:lang="en" tocInclude="true" updates="" obsoletes="" symRefs="true" sortRefs="false" prepTime="2024-10-30T14:16:54" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust-09" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9680" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="IETF Antitrust Guidelines">Antitrust Guidelines for IETF Participants</title>
    <seriesInfo name="RFC" value="9680" stream="IETF"/>
    <author fullname="Joel M. Halpern" initials="J." role="editor" surname="Halpern">
      <organization abbrev="Ericsson" showOnFrontPage="true">Ericsson</organization>
      <address>
        <postal>
          <street>P.O. Box 6049</street>
          <city>Leesburg</city>
          <region>VA</region>
          <code>20178</code>
          <country>United States of America</country>
        </postal>
        <email>joel.halpern@ericsson.com</email>
      </address>
    </author>
    <author fullname="Jay Daley" initials="J." surname="Daley">
      <organization abbrev="IETF Administration LLC" showOnFrontPage="true">IETF Administration LLC</organization>
      <address>
        <postal>
          <street>1000 N. West Street, Suite 1200</street>
          <city>Wilmington</city>
          <region>DE</region>
          <code>19801</code>
          <country>United States of America</country>
        </postal>
        <email>jay@staff.ietf.org</email>
      </address>
    </author>
    <date month="10" year="2024"/>
    <keyword>anticompetitive</keyword>
    <keyword>competition law</keyword>
    <keyword>policy</keyword>
    <keyword>compliance</keyword>
    <keyword>recommendations</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">
        This document provides education and guidance for IETF participants on compliance with antitrust laws and how to reduce antitrust risks in connection with IETF activities.
      </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 document is not an Internet Standards Track specification; it is
            published for informational purposes.  
        </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).  Not all documents
            approved by the IESG are candidates for any level of Internet
            Standard; see 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/rfc9680" 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) 2024 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>
      </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" 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-background">Background</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2">
              <li pn="section-toc.1-1.2.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-a-note-about-terminology">A Note About Terminology</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.2">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.2.2.1"><xref derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-purpose-of-antitrust-or-com">Purpose of Antitrust or Competition Law</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.3">
                <t indent="0" pn="section-toc.1-1.2.2.3.1"><xref derivedContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-overlapping-areas-of-concer">Overlapping Areas of Concern</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" 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-existing-ietf-antitrust-com">Existing IETF Antitrust Compliance Strategy</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-additional-recommendations">Additional Recommendations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-topics-to-avoid">Topics to Avoid</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-obtaining-independent-legal">Obtaining Independent Legal Advice</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.3">
                <t indent="0" pn="section-toc.1-1.4.2.3.1"><xref derivedContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-escalating-antitrust-relate">Escalating Antitrust-Related Concerns</xref></t>
              </li>
            </ul>
          </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-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <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.7.2">
              <li pn="section-toc.1-1.7.2.1">
                <t indent="0" pn="section-toc.1-1.7.2.1.1"><xref derivedContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.2">
                <t indent="0" pn="section-toc.1-1.7.2.2.1"><xref derivedContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </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.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">
        Standards development frequently requires collaboration between competitors.  Cooperation among competitors can spark concerns about antitrust law or competition law violations. This document is intended to educate IETF participants about how to reduce antitrust risks in connection with IETF activities. Nothing in this document changes existing IETF policies.
      </t>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-background">Background</name>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.1">
        <name slugifiedName="name-a-note-about-terminology">A Note About Terminology</name>
        <t indent="0" pn="section-2.1-1">
          "Antitrust law" and "competition law" are used synonymously in this document. "Antitrust" is the word that is used in the US and in several other jurisdictions; "competition law" is the terminology used in Europe and in many other jurisdictions. There can be some nuanced differences between how different jurisdictions address this general area of law, and sometimes people use the terminology differently to highlight these nuances, but here they are being used as synonyms. 
        </t>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.2">
        <name slugifiedName="name-purpose-of-antitrust-or-com">Purpose of Antitrust or Competition Law</name>
        <t indent="0" pn="section-2.2-1">
          The U.S. Department of Justice states that "the goal of the antitrust laws is to protect economic freedom and opportunity by promoting free and fair competition in the marketplace. Competition in a free market benefits consumers through lower prices, better quality and greater choice. Competition provides businesses the opportunity to compete on price and quality, in an open market and on a level playing field, unhampered by anticompetitive restraints" <xref target="DOJ" format="default" sectionFormat="of" derivedContent="DOJ"/>. Similarly, the European Commission states that the purpose of its competition law rules is "to make EU markets work better, by ensuring that all companies compete equally and fairly on their merits" which "benefits consumers, businesses and the European economy as a whole" <xref target="EC" format="default" sectionFormat="of" derivedContent="EC"/>. Fundamentally, antitrust or competition laws are designed to facilitate open, fair, robust competition, ultimately to benefit consumers. 
        </t>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.3">
        <name slugifiedName="name-overlapping-areas-of-concer">Overlapping Areas of Concern</name>
        <t indent="0" pn="section-2.3-1">
          There are two overlapping areas of concern the IETF has in connection
          with antitrust compliance:
        </t>
        <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-2.3-2">
          <li pn="section-2.3-2.1">Most acutely, the IETF cannot have anyone who is officially representing the IETF, in any capacity, engage in anticompetitive behavior and create liability for the IETF.</li>
          <li pn="section-2.3-2.2">Additionally, the IETF cannot be a forum where participants engage in anticompetitive behavior, even if direct liability for that behavior falls on those participants and not the IETF, to avoid reputational harm to the IETF.</li>
        </ul>
      </section>
    </section>
    <section anchor="compliance" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-existing-ietf-antitrust-com">Existing IETF Antitrust Compliance Strategy</name>
      <t indent="0" pn="section-3-1">
        Compliance with the BCPs and other relevant policies that document the established rules and norms of the IETF facilitates compliance with antitrust law, as the IETF structure and processes are designed to mitigate antitrust risks.  As a reminder, participants are required to comply with the following policies:
      </t>
      <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-3-2">
        <li pn="section-3-2.1">
          The Internet Standards Process as described in BCP 9 <xref target="BCP9" format="default" sectionFormat="of" derivedContent="BCP9"/>, which is designed to "provide a fair, open, and objective basis for developing, evaluating, and adopting Internet Standards" (RFC 2026) and provides robust procedural rules, including an appeals process.
        </li>
        <li pn="section-3-2.2">
          The Working Group Guidelines and Procedures described in BCP 25 <xref target="BCP25" format="default" sectionFormat="of" derivedContent="BCP25"/>, which emphasize requirements for "open and fair participation and for thorough consideration of technical alternatives" (RFC 2418) and describe the IETF's consensus-based decision-making processes.
        </li>
        <li pn="section-3-2.3">
          The IETF framework that participants engage in their individual capacity, not as company representatives (see <xref target="BCP9" format="default" sectionFormat="of" derivedContent="BCP9"/> and <xref target="LLC" format="default" sectionFormat="of" derivedContent="LLC"/>), and "use their best engineering judgment to find the best solution for the whole Internet, not just the best solution for any particular network, technology, vendor, or user," as described in RFC 7154 <xref target="BCP54" format="default" sectionFormat="of" derivedContent="BCP54"/>.
        </li>
        <li pn="section-3-2.4">
          The IETF's intellectual property rights policies as set forth in BCP 78 <xref target="BCP78" format="default" sectionFormat="of" derivedContent="BCP78"/> and BCP 79 <xref target="BCP79" format="default" sectionFormat="of" derivedContent="BCP79"/>. These policies are carefully designed to "benefit the Internet community and the public at large, while respecting the legitimate rights of others" (RFC 8179).
        </li>
        <li pn="section-3-2.5">
          The established conflict of interest policies, such as the <eref target="https://www.ietf.org/about/groups/iesg/iesg-coi-policy/" brackets="none">IESG Conflict of Interest Policy</eref>, the <eref target="https://www.iab.org/about/conflict-of-interest-policy/" brackets="none">IAB Conflict of Interest Policy</eref>, or the <eref target="https://www.ietf.org/administration/policies-procedures/conflict-interest/" brackets="none">IETF LLC Conflict of Interest Policy</eref>, if and when applicable.
        </li>
      </ul>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-additional-recommendations">Additional Recommendations</name>
      <t indent="0" pn="section-4-1">
        The most important recommendation is for IETF participants to rigorously follow all applicable IETF policies as set out in <xref target="compliance" format="default" sectionFormat="of" derivedContent="Section 3"/>.
      </t>
      <t indent="0" pn="section-4-2">This section provides more information about:</t>
      <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-4-3">
        <li pn="section-4-3.1">certain topics that are generally inappropriate for discussion in a standards-setting environment,</li>
        <li pn="section-4-3.2">the importance of participants obtaining independent legal advice, as appropriate, and</li>
        <li pn="section-4-3.3">paths to escalate antitrust-related concerns.</li>
      </ul>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-4.1">
        <name slugifiedName="name-topics-to-avoid">Topics to Avoid</name>
        <t indent="0" pn="section-4.1-1">
          While IETF participants are expected to participate as individuals, their actions could still be construed as representing their employer, whatever their role. Therefore, participants should be aware that some topics are generally inappropriate for discussion in a standards-setting environment where representatives from competitors to their employer are likely to be present. These topics include the following:</t>
        <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-4.1-2">
          <li pn="section-4.1-2.1">discussion about product pricing or profit margins among potential competitors, </li>
          <li pn="section-4.1-2.2">the details of business relationships between specific vendors and customers,</li>
          <li pn="section-4.1-2.3">details about the supply chains of specific companies, </li>
          <li pn="section-4.1-2.4">discussions about market opportunities for specific companies, and</li>
          <li pn="section-4.1-2.5">employee compensation or benefits among potentially competitive employers.</li>
        </ul>
        <t indent="0" pn="section-4.1-3">
While not all discussions of these topics would necessarily be antitrust violations, and recognizing that analysis of antitrust considerations will be different for differently positioned participants, prudence suggests that avoiding these specific topics in the context of the collaborative IETF process best mitigates antitrust risks for the IETF and its participants. 
        </t>
        <t indent="0" pn="section-4.1-4">
          Note that antitrust law reaches beyond these topics, however. For example, any behavior that amounts to an agreement to restrain marketplace competition, or that facilitates monopolization of particular markets, raises potential antitrust risks. Participants are responsible for ensuring that their conduct does not violate any antitrust laws or regulations.
        </t>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-4.2">
        <name slugifiedName="name-obtaining-independent-legal">Obtaining Independent Legal Advice</name>
        <t indent="0" pn="section-4.2-1">All IETF participants are expected to behave lawfully when engaged in IETF activities, including by following applicable antitrust law. The IETF does not provide legal advice to participants, and instead recommends that participants obtain independent legal advice as needed.</t>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-4.3">
        <name slugifiedName="name-escalating-antitrust-relate">Escalating Antitrust-Related Concerns</name>
        <t indent="0" pn="section-4.3-1">
          Participants can report potential antitrust issues in the context of IETF activities by contacting IETF legal counsel (legal@ietf.org) or via the IETF LLC whistleblower service <xref target="Whistleblower" format="default" sectionFormat="of" derivedContent="Whistleblower"/>. Note that reports will only be assessed for their impact upon the IETF; participants directly impacted by an antitrust issue are responsible for obtaining their own legal advice.
        </t>
      </section>
    </section>
    <section 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 has no IANA actions.
      </t>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-6-1">
        This document introduces no known security aspects to the IETF or IETF participants.
      </t>
    </section>
  </middle>
  <back>
    <references pn="section-7">
      <name slugifiedName="name-references">References</name>
      <references pn="section-7.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <referencegroup anchor="BCP9" target="https://www.rfc-editor.org/info/bcp9" derivedAnchor="BCP9">
          <reference anchor="RFC2026" target="https://www.rfc-editor.org/info/rfc2026" quoteTitle="true">
            <front>
              <title>The Internet Standards Process -- Revision 3</title>
              <author fullname="S. Bradner" initials="S." surname="Bradner"/>
              <date month="October" year="1996"/>
              <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>
          <reference anchor="RFC5657" target="https://www.rfc-editor.org/info/rfc5657" quoteTitle="true">
            <front>
              <title>Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard</title>
              <author fullname="L. Dusseault" initials="L." surname="Dusseault"/>
              <author fullname="R. Sparks" initials="R." surname="Sparks"/>
              <date month="September" year="2009"/>
              <abstract>
                <t indent="0">Advancing a protocol to Draft Standard requires documentation of the interoperation and implementation of the protocol. Historic reports have varied widely in form and level of content and there is little guidance available to new report preparers. This document updates the existing processes and provides more detail on what is appropriate in an interoperability and implementation report. 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="5657"/>
            <seriesInfo name="DOI" value="10.17487/RFC5657"/>
          </reference>
          <reference anchor="RFC6410" target="https://www.rfc-editor.org/info/rfc6410" quoteTitle="true">
            <front>
              <title>Reducing the Standards Track to Two Maturity Levels</title>
              <author fullname="R. Housley" initials="R." surname="Housley"/>
              <author fullname="D. Crocker" initials="D." surname="Crocker"/>
              <author fullname="E. Burger" initials="E." surname="Burger"/>
              <date month="October" year="2011"/>
              <abstract>
                <t indent="0">This document updates the Internet Engineering Task Force (IETF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards Process from three Standards Track maturity levels to two. This memo documents an Internet Best Current Practice.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="9"/>
            <seriesInfo name="RFC" value="6410"/>
            <seriesInfo name="DOI" value="10.17487/RFC6410"/>
          </reference>
          <reference anchor="RFC7100" target="https://www.rfc-editor.org/info/rfc7100" quoteTitle="true">
            <front>
              <title>Retirement of the "Internet Official Protocol Standards" Summary Document</title>
              <author fullname="P. Resnick" initials="P." surname="Resnick"/>
              <date month="December" year="2013"/>
              <abstract>
                <t indent="0">This document updates RFC 2026 to no longer use STD 1 as a summary of "Internet Official Protocol Standards". It obsoletes RFC 5000 and requests the IESG to move RFC 5000 (and therefore STD 1) to Historic status.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="9"/>
            <seriesInfo name="RFC" value="7100"/>
            <seriesInfo name="DOI" value="10.17487/RFC7100"/>
          </reference>
          <reference anchor="RFC7127" target="https://www.rfc-editor.org/info/rfc7127" quoteTitle="true">
            <front>
              <title>Characterization of Proposed Standards</title>
              <author fullname="O. Kolkman" initials="O." surname="Kolkman"/>
              <author fullname="S. Bradner" initials="S." surname="Bradner"/>
              <author fullname="S. Turner" initials="S." surname="Turner"/>
              <date month="January" year="2014"/>
              <abstract>
                <t indent="0">RFC 2026 describes the review performed by the Internet Engineering Steering Group (IESG) on IETF Proposed Standard RFCs and characterizes the maturity level of those documents. This document updates RFC 2026 by providing a current and more accurate characterization of Proposed Standards.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="9"/>
            <seriesInfo name="RFC" value="7127"/>
            <seriesInfo name="DOI" value="10.17487/RFC7127"/>
          </reference>
          <reference anchor="RFC7475" target="https://www.rfc-editor.org/info/rfc7475" quoteTitle="true">
            <front>
              <title>Increasing the Number of Area Directors in an IETF Area</title>
              <author fullname="S. Dawkins" initials="S." surname="Dawkins"/>
              <date month="March" year="2015"/>
              <abstract>
                <t indent="0">This document removes a limit on the number of Area Directors who manage an Area in the definition of "IETF Area". This document updates RFC 2026 (BCP 9) and RFC 2418 (BCP 25).</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="9"/>
            <seriesInfo name="RFC" value="7475"/>
            <seriesInfo name="DOI" value="10.17487/RFC7475"/>
          </reference>
          <reference anchor="RFC8789" target="https://www.rfc-editor.org/info/rfc8789" quoteTitle="true">
            <front>
              <title>IETF Stream Documents Require IETF Rough Consensus</title>
              <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/>
              <author fullname="E. Rescorla" initials="E." role="editor" surname="Rescorla"/>
              <date month="June" year="2020"/>
              <abstract>
                <t indent="0">This document requires that the IETF never publish any IETF Stream RFCs without IETF rough consensus. This updates RFC 2026.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="9"/>
            <seriesInfo name="RFC" value="8789"/>
            <seriesInfo name="DOI" value="10.17487/RFC8789"/>
          </reference>
          <reference anchor="RFC9282" target="https://www.rfc-editor.org/info/rfc9282" quoteTitle="true">
            <front>
              <title>Responsibility Change for the RFC Series</title>
              <author fullname="B. Rosen" initials="B." surname="Rosen"/>
              <date month="June" year="2022"/>
              <abstract>
                <t indent="0">In RFC 9280, responsibility for the RFC Series moved to the RFC Series Working Group and the RFC Series Approval Board. It is no longer the responsibility of the RFC Editor, and the role of the IAB in the RFC Series is altered. Accordingly, in Section 2.1 of RFC 2026, the sentence "RFC publication is the direct responsibility of the RFC Editor, under the general direction of the IAB" is deleted.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="9"/>
            <seriesInfo name="RFC" value="9282"/>
            <seriesInfo name="DOI" value="10.17487/RFC9282"/>
          </reference>
        </referencegroup>
        <referencegroup anchor="BCP25" target="https://www.rfc-editor.org/info/bcp25" derivedAnchor="BCP25">
          <reference anchor="RFC2418" target="https://www.rfc-editor.org/info/rfc2418" quoteTitle="true">
            <front>
              <title>IETF Working Group Guidelines and Procedures</title>
              <author fullname="S. Bradner" initials="S." surname="Bradner"/>
              <date month="September" year="1998"/>
              <abstract>
                <t indent="0">This document describes the guidelines and procedures for formation and operation of IETF working groups. 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="25"/>
            <seriesInfo name="RFC" value="2418"/>
            <seriesInfo name="DOI" value="10.17487/RFC2418"/>
          </reference>
          <reference anchor="RFC3934" target="https://www.rfc-editor.org/info/rfc3934" quoteTitle="true">
            <front>
              <title>Updates to RFC 2418 Regarding the Management of IETF Mailing Lists</title>
              <author fullname="M. Wasserman" initials="M." surname="Wasserman"/>
              <date month="October" year="2004"/>
              <abstract>
                <t indent="0">This document is an update to RFC 2418 that gives WG chairs explicit responsibility for managing WG mailing lists. In particular, it gives WG chairs the authority to temporarily suspend the mailing list posting privileges of disruptive individuals. 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="25"/>
            <seriesInfo name="RFC" value="3934"/>
            <seriesInfo name="DOI" value="10.17487/RFC3934"/>
          </reference>
          <reference anchor="RFC7776" target="https://www.rfc-editor.org/info/rfc7776" quoteTitle="true">
            <front>
              <title>IETF Anti-Harassment Procedures</title>
              <author fullname="P. Resnick" initials="P." surname="Resnick"/>
              <author fullname="A. Farrel" initials="A." surname="Farrel"/>
              <date month="March" year="2016"/>
              <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>
          <reference anchor="RFC8716" target="https://www.rfc-editor.org/info/rfc8716" quoteTitle="true">
            <front>
              <title>Update to the IETF Anti-Harassment Procedures for the Replacement of the IETF Administrative Oversight Committee (IAOC) with the IETF Administration LLC</title>
              <author fullname="P. Resnick" initials="P." surname="Resnick"/>
              <author fullname="A. Farrel" initials="A." surname="Farrel"/>
              <date month="February" year="2020"/>
              <abstract>
                <t indent="0">The IETF Anti-Harassment Procedures are described in RFC 7776.</t>
                <t indent="0">The IETF Administrative Oversight Committee (IAOC) has been replaced by the IETF Administration LLC, and the IETF Administrative Director has been replaced by the IETF LLC Executive Director. This document updates RFC 7776 to amend these terms.</t>
                <t indent="0">RFC 7776 contained updates to RFC 7437. RFC 8713 has incorporated those updates, so this document also updates RFC 7776 to remove those updates.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="25"/>
            <seriesInfo name="RFC" value="8716"/>
            <seriesInfo name="DOI" value="10.17487/RFC8716"/>
          </reference>
        </referencegroup>
        <referencegroup anchor="BCP54" target="https://www.rfc-editor.org/info/bcp54" derivedAnchor="BCP54">
          <reference anchor="RFC7154" target="https://www.rfc-editor.org/info/rfc7154" quoteTitle="true">
            <front>
              <title>IETF Guidelines for Conduct</title>
              <author fullname="S. Moonesamy" initials="S." role="editor" surname="Moonesamy"/>
              <date month="March" year="2014"/>
              <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>
        </referencegroup>
        <referencegroup anchor="BCP78" target="https://www.rfc-editor.org/info/bcp78" derivedAnchor="BCP78">
          <reference anchor="RFC5378" target="https://www.rfc-editor.org/info/rfc5378" quoteTitle="true">
            <front>
              <title>Rights Contributors Provide to the IETF Trust</title>
              <author fullname="S. Bradner" initials="S." role="editor" surname="Bradner"/>
              <author fullname="J. Contreras" initials="J." role="editor" surname="Contreras"/>
              <date month="November" year="2008"/>
              <abstract>
                <t indent="0">The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replaces Section 10 of RFC 2026. 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="78"/>
            <seriesInfo name="RFC" value="5378"/>
            <seriesInfo name="DOI" value="10.17487/RFC5378"/>
          </reference>
        </referencegroup>
        <referencegroup anchor="BCP79" target="https://www.rfc-editor.org/info/bcp79" derivedAnchor="BCP79">
          <reference anchor="RFC8179" target="https://www.rfc-editor.org/info/rfc8179" quoteTitle="true">
            <front>
              <title>Intellectual Property Rights in IETF Technology</title>
              <author fullname="S. Bradner" initials="S." surname="Bradner"/>
              <author fullname="J. Contreras" initials="J." surname="Contreras"/>
              <date month="May" year="2017"/>
              <abstract>
                <t indent="0">The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information as possible about any IPR constraints on a technical proposal as early as possible in the development process. The policies are intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This document sets out the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This document updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026. This document also obsoletes RFCs 3979 and 4879.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="79"/>
            <seriesInfo name="RFC" value="8179"/>
            <seriesInfo name="DOI" value="10.17487/RFC8179"/>
          </reference>
        </referencegroup>
      </references>
      <references pn="section-7.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="DOJ" target="https://www.justice.gov/atr/mission" quoteTitle="true" derivedAnchor="DOJ">
          <front>
            <title>Mission</title>
            <author>
              <organization showOnFrontPage="true">U.S. Department of Justice Antitrust Division</organization>
            </author>
          </front>
        </reference>
        <reference anchor="EC" target="https://commission.europa.eu/about-european-commission/departments-and-executive-agencies/competition_en" quoteTitle="true" derivedAnchor="EC">
          <front>
            <title>Competition</title>
            <author>
              <organization showOnFrontPage="true">European Commission</organization>
            </author>
          </front>
        </reference>
        <reference anchor="LLC" target="https://www.ietf.org/blog/ietf-llc-statement-competition-law-issues/" quoteTitle="true" derivedAnchor="LLC">
          <front>
            <title>IETF Administration LLC Statement on Competition Law Issues</title>
            <author>
              <organization showOnFrontPage="true">IETF Administration LLC</organization>
            </author>
            <date day="28" month="July" year="2020"/>
          </front>
        </reference>
        <reference anchor="Whistleblower" target="https://www.ietf.org/administration/policies-procedures/whistleblower/" quoteTitle="true" derivedAnchor="Whistleblower">
          <front>
            <title>IETF LLC Whistleblower Policy</title>
            <author>
              <organization showOnFrontPage="true">IETF Administration LLC</organization>
            </author>
          </front>
        </reference>
      </references>
    </references>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Joel M. Halpern" initials="J." role="editor" surname="Halpern">
        <organization abbrev="Ericsson" showOnFrontPage="true">Ericsson</organization>
        <address>
          <postal>
            <street>P.O. Box 6049</street>
            <city>Leesburg</city>
            <region>VA</region>
            <code>20178</code>
            <country>United States of America</country>
          </postal>
          <email>joel.halpern@ericsson.com</email>
        </address>
      </author>
      <author fullname="Jay Daley" initials="J." surname="Daley">
        <organization abbrev="IETF Administration LLC" showOnFrontPage="true">IETF Administration LLC</organization>
        <address>
          <postal>
            <street>1000 N. West Street, Suite 1200</street>
            <city>Wilmington</city>
            <region>DE</region>
            <code>19801</code>
            <country>United States of America</country>
          </postal>
          <email>jay@staff.ietf.org</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
