<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-model href="rfc7991bis.rnc"?>
<!--<?xml-stylesheet type="text/css" href="rfc-xml.css" title="RFC XML Style" alternate="no"?>-->

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="bcp" submissionType="IETF" ipr="trust200902" docName="draft-halpern-gendispatch-antitrust-02" version="3">
  <front>
    <title abbrev="IETF Antitrust Guidelines">Antitrust Guidelines for IETF Particiants</title>
    <author fullname="Joel M. Halpern" initials="J. M." role="editor" surname="Halpern">
      <organization abbrev="Ericsson">Ericsson</organization>
      <address>
        <postal>
          <street>P. O. Box 6049</street>
          <city>Leesburg</city>
          <region>VA</region>
          <code>20178</code>
          <country>US</country>
        </postal>
        <email>joel.halpern@ericsson.com</email>
      </address>
    </author>
    <author fullname="Brad Biddle" initials="B." surname="Biddle">
      <organization abbrev="Biddle Law PC">Biddle Law PC</organization>
      <address>
        <postal>
          <street>650 NE Holladay Street, Suite 1600</street>
          <city>Portland</city>
          <region>OR</region>
          <code>97232</code>
          <country>US</country>
        </postal>
        <email>brad@biddle.law</email>
      </address>
    </author>
    <author fullname="Jay Daley" initials="J." surname="Daley">
      <organization abbrev="IETF Administration LLC">IETF Administration LLC</organization>
      <address>
        <postal>
          <street>1000 N. West Street, Suite 1200</street>
          <city>Wilimington</city>
          <region>DE</region>
          <code>19801</code>
          <country>US</country>
        </postal>
        <email>jay@staff.ietf.org</email>
      </address>
    </author>
    <date month="December" year="2021"/>
    <area>General</area>
    <abstract>
      <t>
        This document specifies policy for IETF participants on compliance with antitrust laws and how to reduce antitrust risks in connection with IETF activities.
      </t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction">
      <t>
        Standards development frequently requires collaboration between competitors. Cooperation among competitors can spark concerns about antitrust law or competition law violations (antitrust law and competition law are used here synonymously). Certain actions taken by a company that holds a dominant market position can similarly spark concerns about competition law violations. This document specifies policy for IETF participants about how to reduce antitrust risks in connection with IETF activities.
      </t>
    </section>
    <section title="Terminology">
      <t>
        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14
        <xref target="RFC2119"/>
        <xref target="RFC8174"/>
        when, and only when, they appear in all capitals, as shown here.
      </t>
    </section>
    <section title="Legal Advice">
      <t>
        The IETF does not provide legal advice to participants, and instead encourages participants to obtain independent legal advice as needed. IETF participants should always consult with their own counsel when antitrust or competition law-related questions arise.
      </t>
    </section>
    <section title="Existing BCPs">
      <t>
        Compliance with the BCPs that document the established rules and norms of the IETF facilitates compliance with antitrust law, as the IETF structure and processes are intended to mitigate antitrust risks. As a reminder, participants are already required to comply with the following policies documented in the BCPs:
      </t>
      <ul>
        <li>
          The Internet Standards Process as described in BCP 9
          <xref target="BCP9"/>
          , which is designed to "provide a fair, open, and objective basis for developing, evaluating, and adopting Internet Standards," and provides robust procedural rules, including an appeals process.
        </li>
        <li>
          The Working Group Guidelines and Procedures described in BCP 25
          <xref target="BCP25"/>
          , which emphasize requirements for "open and fair participation and for thorough consideration of technical alternatives," and describe IETF's consensus-based decision-making processes.
        </li>
        <li>
          The IETF framework that participants engage in their individual capacity, not as company representatives, 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 BCP 54
          <xref target="BCP54"/>
          .
        </li>
        <li>
          The IETF's intellectual property rights policies as set forth in BCP 78
          <xref target="BCP78"/>
          and BCP 79
          <xref target="BCP79"/>
          ; these policies are carefully designed to "benefit the Internet community and the public at large, while respecting the legitimate rights of others."
        </li>
        <li>
          The established conflict of interest policies, such as the IESG Conflict of Interest Policy, the IAB Conflict of Interest Policy or the IETF LLC Conflict of Interest Policy, if and when applicable.
        </li>
      </ul>
    </section>
    <section title="Antitrust Policy">
      <t>
        All IETF participants <bcp14>MUST</bcp14> behave lawfully when engaged in IETF activities, including by following applicable antitrust laws.  While antitrust laws vary between jurisdictions, IETF participants <bcp14>SHOULD NOT</bcp14> assume that they need only comply with the laws of the jurisdiction they reside in as the laws of multiple jurisdictions may apply.  Accordingly IETF participants <bcp14>SHOULD NOT</bcp14> engage in or otherwise support any of the following:
      </t>
      <ul>
        <li>anti-competitive agreements between two or more independent market operators</li>
        <li>abusive behaviour by companies holding a dominant position on any given market</li>
      </ul>
    </section>
    <section title="Escalation of antitrust-related concerns">
      <t>
        Participants <bcp14>SHOULD</bcp14> report potential antitrust concerns in the context of IETF activities through the following channels: IETF Chair (chair@ietf.org), the IETF LLC executive director (exec-director@ietf.org), the IETF legal counsel (legal@ietf.org), or via the IETF LLC whistleblower service.
      </t>
    </section>
    <section title="IANA Considerations">
      <t>
        No values are assigned in this document, no registries are created, and there is no action assigned to the IANA by this document.
      </t>
    </section>
    <section title="Security Considerations">
      <t>
        This document may be considered to document means to avoid risks to the IETF and IETF participants related to antitrust. One may consider those to be security considerations. Other than that, this document introduces no known security aspects to the IETF or IETF participants.
      </t>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
      <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
      <referencegroup anchor="BCP9" target="https://www.rfc-editor.org/info/bcp9">
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2026.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5657.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6410.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7100.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7127.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7475.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8789.xml"/>
      </referencegroup>
      <referencegroup anchor="BCP25" target="https://www.rfc-editor.org/info/bcp25">
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2418.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3934.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7776.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8716.xml"/>
      </referencegroup>
      <referencegroup anchor="BCP54" target="https://www.rfc-editor.org/info/bcp54">
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7154.xml"/>
      </referencegroup>
      <referencegroup anchor="BCP78" target="https://www.rfc-editor.org/info/bcp78">
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5378.xml"/>
      </referencegroup>
      <referencegroup anchor="BCP79" target="https://www.rfc-editor.org/info/bcp79">
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8179.xml"/>
      </referencegroup>
    </references>
    <references>
      <name>Informative References</name>
    </references>
  </back>
</rfc>
