<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-deen-ietf-ipmc-update-00" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.31.0 -->
  <front>
    <title abbrev="IETFIPMC">Update to Recognize the IETF IPMC as the IETF Trust Successor</title>
    <seriesInfo name="Internet-Draft" value="draft-deen-ietf-ipmc-update-00"/>
    <author fullname="Glenn Deen">
      <organization>Comcast-NBCUniversal</organization>
      <address>
        <email>rgd.ietf@gmail.com</email>
      </address>
    </author>
    <author fullname="Kristin Berdan">
      <organization>Internet Security Research Group</organization>
      <address>
        <email>kristin.berdan@gmail.com</email>
      </address>
    </author>
    <date year="2025" month="November" day="21"/>
    <area>General Area</area>
    <workgroup>gen</workgroup>
    <keyword>IETF IPR</keyword>
    <keyword>IETF Trust</keyword>
    <keyword>IETF IPMC</keyword>
    <abstract>
      <?line 51?>

<t>This document updates IETF documents that reference the IETF Trust to include the Trust's successor, the IETF Intellectual Property Management Corporation.</t>
      <t>Discussion of this draft is on the ipr-wg@ietf.org mailing list.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://gitnnelg.github.io/draft-deen-ietf-ipmc-update/draft-deen-ietf-ipmc-update.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-deen-ietf-ipmc-update/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        genarea Working Group mailing list (<eref target="mailto:ipr-wg@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/ipr-wg"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/ipr-wg/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/gitnnelg/draft-deen-ietf-ipmc-update"/>.</t>
    </note>
  </front>
  <middle>
    <?line 57?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The IETF Trust, a Virginia trust, was established in 2005 as the intellectual property rights (IPR) manager for the IETF. The IETF Trust has held and managed IPR, including those granted by authors of IETF Contributions and IETF Documents following the terms of BCP78, currently specified in <xref target="RFC5378"/> and its predecessors.</t>
      <t>The IETF Intellectual Property Management Corporation (IPMC) is a Delaware not-for-profit corporation established in 2022 with the intention of being the successor to the IETF Trust, replacing it and assuming all of its roles and responsibilities.</t>
      <t>This document updates RFC 5378, RFC8714 and other IETF documents to recognize that the IETF IPMC is now the proper custodian of all IETF-related intellectual property rights and successor in interest to the IETF Trust.</t>
    </section>
    <section anchor="updates">
      <name>Updates</name>
      <section anchor="references-to-the-ietf-trust-in-ietf-rfcs-and-bcps">
        <name>References to the IETF Trust in IETF RFCs and BCPs</name>
        <t>All references to “IETF Trust” in any IETF document, including RFCs, BCPs, Internet-Drafts, and other IETF publications, shall be read and interpreted as referring to the IETF Intellectual Property Management Corporation (IETF IPMC) as the successor entity. The IETF IPMC has assumed all rights, responsibilities, and obligations previously held by or attributed to the IETF Trust in such documents.</t>
      </section>
      <section anchor="use-of-ietf-trust-and-ietf-ipmc-in-other-ietf-ipr-framework-documents">
        <name>Use of IETF Trust and IETF IPMC in other IETF IPR Framework Documents</name>
        <t>The intellectual property rights framework for IETF contributions is established in RFC 5378 (BCP 78).  The IETF Trust has implemented this framework through its <eref target="https://trustee.ietf.org/documents/trust-legal-provisions/">Trust Legal Provisions</eref> at https://trustee.ietf.org/documents/trust-legal-provisions, and the IETF IPMC will continue this implementation as the successor entity.</t>
        <t>All references to the IETF Trust in RFC 5378 and related operational documents shall be read as referring to the IETF IPMC effective upon the transition.</t>
        <t>Updated copyright notices reflecting this change can be found in Section 6 of the <eref target="https://www.ietf-ipm.org/tlp">IPMC TLP</eref> at https://www.ietf-ipm.org/tlp.</t>
        <t>Note that no retroactive changes of copyright notices in prior IETF documents are to be made.</t>
      </section>
      <section anchor="intellectual-property-rights-held-by-ietf-trust">
        <name>Intellectual Property Rights Held by IETF Trust</name>
        <t>The rights held by the IETF Trust have transferred to the IETF IPMC, as the successor the IETF Trust.  Inquiries regarding licenses and other IPR topics should now be made to the IETF IPMC.</t>
      </section>
      <section anchor="ietf-trustees-and-ipmc-directors-appointment">
        <name>IETF Trustees and IPMC Directors Appointment</name>
        <t>The process defined in <xref target="RFC8714"/> shall define the process by which IETF IPMC Directors are nominated   Nominations done via RFC8714 to the IETF IPMC shall also be eligible to accept appointment as IETF Trustees until the Trust is dissolved.</t>
      </section>
      <section anchor="update-to-urls-in-rfc5378">
        <name>Update to URLs in RFC5378</name>
        <t>The existing URLs in RFC5378 which reference the <eref target="https://trustee.ietf.org/">IETF Trust</eref> web site (https://trustee.ietf.org/) will continue to be maintained as they appear in published documents and will be maintained in perpetuity.</t>
        <t>Additionally, the IPMC has established a new web site for the <eref target="https://www.ietf-ipm.org/">IETF IPMC</eref> (https://www.ietf-ipm.org/) which will henceforth contain IPMC- specific materials, including the updated Trust Legal Provisions (which have been renamed the Technical Legal Provisions) version 6.0 and beyond.</t>
      </section>
    </section>
    <section anchor="ietf-ipmc-recognition-of-ietf-bcps">
      <name>IETF IPMC recognition of IETF BCPs</name>
      <t>The IETF IPMC bylaws obligate the IETF IPMC to manage IETF assets for the benefit of the IETF. Therefore, the IETF IPMC looks to comply with IETF BCPs, as far as legally possible to guide its directors in carrying out that obligation.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document has no security considerations.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="RFC4748">
        <front>
          <title>RFC 3978 Update to Recognize the IETF Trust</title>
          <author fullname="S. Bradner" initials="S." role="editor" surname="Bradner"/>
          <date month="October" year="2006"/>
          <abstract>
            <t>This document updates RFC 3978 "IETF Rights in Contributions" to recognize that the IETF Trust is now the proper custodian of all IETF-related intellectual property rights.</t>
            <t>This document does not constrain how the IETF Trust exercises those rights. 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="4748"/>
        <seriesInfo name="DOI" value="10.17487/RFC4748"/>
      </reference>
      <reference anchor="RFC5378">
        <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>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>
      <reference anchor="RFC9280">
        <front>
          <title>RFC Editor Model (Version 3)</title>
          <author fullname="P. Saint-Andre" initials="P." role="editor" surname="Saint-Andre"/>
          <date month="June" year="2022"/>
          <abstract>
            <t>This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy definition is the joint responsibility of the RFC Series Working Group (RSWG), which produces policy proposals, and the RFC Series Approval Board (RSAB), which approves such proposals. Second, policy implementation is primarily the responsibility of the RFC Production Center (RPC) as contractually overseen by the IETF Administration Limited Liability Company (IETF LLC). In addition, various responsibilities of the RFC Editor function are now performed alone or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor (RSCE), and IETF LLC. Finally, this document establishes the Editorial Stream for publication of future policy definition documents produced through the processes defined herein.</t>
            <t>This document obsoletes RFC 8728. This document updates RFCs 7841, 8729, and 8730.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9280"/>
        <seriesInfo name="DOI" value="10.17487/RFC9280"/>
      </reference>
      <reference anchor="RFC8714">
        <front>
          <title>Update to the Process for Selection of Trustees for the IETF Trust</title>
          <author fullname="J. Arkko" initials="J." surname="Arkko"/>
          <author fullname="T. Hardie" initials="T." surname="Hardie"/>
          <date month="February" year="2020"/>
          <abstract>
            <t>This memo updates the process for selection of Trustees for the IETF Trust. Previously, the IETF Administrative Oversight Committee (IAOC) members also acted as Trustees, but the IAOC has been eliminated as part of an update to the structure of the IETF Administrative Support Activity (IASA). This memo specifies that the Trustees shall be selected separately.</t>
            <t>This memo obsoletes RFC 4371. The changes relate only to the selection of Trustees. All other aspects of the IETF Trust remain as they are today.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="101"/>
        <seriesInfo name="RFC" value="8714"/>
        <seriesInfo name="DOI" value="10.17487/RFC8714"/>
      </reference>
    </references>
    <?line 109?>

<section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The IETF Trustees and IETF Intellectual Property Management Corporation directors during the restructuring of the IETF Trust to the IETF IPMC were: Glenn Deen, John Levine, Joel Halpern, Kathleen Moriarty, Victor Kuarsingh, Jon Peterson, Kristin Berdan, Wendy Seltzer.</t>
    </section>
  </back>

</rfc>
