<?xml version="1.0" encoding="utf-8"?>
<?xml-model href="rfc7991bis.rnc"?>


<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc 
  xmlns:xi="http://www.w3.org/2001/XInclude" 
  category="info" 
  submissionType="IETF" 
  ipr="trust200902" 
  docName="draft-halpern-gendispatch-antitrust-03" 
  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="October" year="2022" day="21"/>
    <area>General</area>
    <abstract>
      <t>
        This document provides guidance 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. This document provides guidance for IETF participants about how to reduce antitrust risks in connection with IETF activities. 
      </t>
    </section>
    <section title="Background">
      <section title="A Note About Terminology">
        <t>
          "Antitrust law" and "competition law" are used synonymously in this document. “Antitrust” is the word that's 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 these kinds of legal issues, and sometimes people use the terminology differently to highlight these nuances, but here they are being used as synonyms. 
        </t>
      </section>
      <section title="Purpose of Antitrust or Competition law">
        <t>
          The U.S. Department of Justice says 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.” Fundamentally, antitrust or competition laws are designed to facilitate open, fair, robust competition, ultimately to benefit consumers. 
        </t>
      </section>
      <section title="Overlapping Areas of Concern">
        <t>
          There are two overlapping areas of concern the IETF has in connection
          with antitrust compliance:
        </t>
        <ul>
          <li>Most acutely, the iETF must not have anyone who is officially representing the IETF, in any capacity, engage in problematic antitrust behavior and create liability for the IETF.</li>
          <li>Additionally, the IETF must not be a forum where participants engage in problematic antitrust 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 title="Existing IETF Antitrust Compliance Strategy">
      <t>
        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>
        <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="Key Recommendations">
      <t>
        The most important recommendation is for IETF participants to rigorously follow all applicable IETF policies as set out in section 3 above.
      </t>
      <t>Additionally it is recommended that IETF participants:</t>
      <ul>
        <li>Avoid 'red flag' topics</li>
        <li>Use caution with 'yellow flag' topics</li>
        <li>Obtain independent legal advice, as appropriate</li>
        <li>Escalate antitrust-related concerns</li>
      </ul>
      <section title="Avoid 'red flag' Topics">
        <t>
          Some topics are particularly inappropriate for discussion in a standards setting environment where representatives from competitors are likely to be present. These topics include: product pricing, profit margins, business relationships between specific vendors and customers, details about particular supply chains, discussions about particular market opportunities, or employee compensation or benefits. While not all discussions of these topics would necessarily be antitrust violations, prudence suggests that avoiding these topics altogether in the context of collaborative IETF discussions best mitigates antitrust risks for the IETF and its participants. 
        </t>
        <t>
          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 must ensure that their conduct does not violate any antitrust laws or regulations.
        </t>
      </section>
      <section title="Use Caution With 'yellow flag' Topics">
        <t>
          Two topics that can be relevant at times in a standard setting context but that can also raise some competition law risks are: 
        </t>
        <ul>
          <li>Evaluating the relative implementation costs of two technical alternatives to decide whether one is significantly more feasible in the market and thus a better candidate for standardization. </li>
          <li>Seeking clarifications about IPR disclosures, particularly when any such clarifications could be perceived as entering into negotiations of IPR terms.</li>
        </ul>
        <t>IETF participants should consult with IETF legal counsel and/or other IETF experts as needed to ensure that an investigation of these topics follows established best practices.</t>
      </section>
      <section title="Obtain Independent Legal Advice">
        <t>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. IETF participants should consult with their own counsel when antitrust or competition law-related questions arise.</t>
      </section>
      <section title="Escalate Antitrust-Related Concerns">
        <t>
          Participants should 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>
    <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>
      <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>
