<?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.31 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-deen-ietf-ipmc-update-03" category="info" consensus="true" submissionType="IETF" updates="5378, 8714, 8721" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.32.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-03"/>
    <author fullname="Glenn Deen">
      <organization>Comcast-NBCUniversal</organization>
      <address>
        <email>rgd.ietf@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="April" day="01"/>
    <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 BCP 78, currently specified in <xref target="RFC5378"/> and its predecessors.</t>
      <t>The IETF Intellectual Property Management Corporation (IPMC), a Delaware not-for-profit corporation was established in December 2022 as the successor to the IETF Trust, replacing it and assuming all of its roles and responsibilities. Since its establishment the IETF IPMC has been undertaking the necessary steps to establish itself as a 501c3 non-profit, to prepare for and execute the transfer of all assets held by the IETF Trust, and to update where necessary agreements and IETF documents to complete the task of assuming the role as the replacement of the IETF Trust.</t>
      <t>The IETF Trust has never held or been involved in patents and likewise, the IETF IPMC will continue not being involved with any patent related activity.</t>
      <t>This document updates RFC 5378, RFC 8714, RFC 8721 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.</t>
        <t>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="websites-and-urls">
        <name>Websites and URLs</name>
        <section anchor="ietf-ipr-ietforgipr-and-ietforgprocessipr">
          <name>IETF IPR: ietf.org/ipr and ietf.org/process/ipr</name>
          <t>The IETF publishes information on intellectual property rights (IPR) at <eref target="https://ietf.org/ipr">IETF IPR</eref> and more general information at the <eref target="https://ietf.org/process/ipr">IETF IPR Process</eref> dealing with IETF IPR topics in general and including patents.</t>
        </section>
        <section anchor="ietf-trust-trusteeietforg">
          <name>IETF Trust: trustee.ietf.org</name>
          <t>The IETF Trust, historically, has published information related to licensing, assets, finances and notices of actions and changes on its web site <eref target="https://trustees.ietf.org">https://trustee.ietf.org</eref>.  This web site shall be maintained in perpetuity as URLs to it appear in published documents and the Trust Legal Provisions (TLP) version 1.0-5.0 that were active at the time of an I-D submission and the date of a RFC publication will continue to apply to those works even after subsequent transfer of those IPR assets to the IETF IPMC.   The existing URLs in the required copyright boilerplate and other sections of I-Ds and RFCs will continue to work correctly for users of those documents.</t>
        </section>
        <section anchor="ietf-ipmc-wwwietf-ipmorg">
          <name>IETF IPMC: www.ietf-ipm.org</name>
          <t>The IETF IPMC, has established the <eref target="https://www.ietf-ipm.org">IETF IPMC Website https://www.ietf-ipm.org</eref> as its official corporate website which it will use to publish governance and operational information including bylaws and financial statements and legal notices, along with the updated IETF IPMC published Technical Legal Provisions (TLP 6.0) which provide licensing terms for I-Ds and RFCs.</t>
          <t>Cross reference navigation links on the old IETF Trust and the new IETF IPMC websites shall be established to provide easy navigation between them to users.</t>
        </section>
      </section>
      <section anchor="updates-to-rfc5378">
        <name>Updates to RFC5378</name>
        <t>RFC5378 has a number of cited URLs directing readers to the locations of various IPR related information.   The IETF Trust web site URLs shall be maintained to preserve the URLs to it found in RFC5378.  There is no need to update or modify existing references in I-Ds or RFCs.</t>
        <t>Additionally, RFC5378 is hence updated to include the IPMC web site as the location IETF IPMC licensing information for assets, including required notices.</t>
        <section anchor="ietf-ipmc-technical-legal-provisions-relating-to-ietf-documents-tlp">
          <name>IETF IPMC Technical Legal Provisions Relating to IETF Documents (TLP)</name>
          <t>The IETF Trust published a series of documents commonly known as the "TLP" versions 1.0-5.0 containing basic common licensing declarations and required boilerplates and notices in I-Ds and RFCs.  The formal name for these documents was "IETF Trust Legal Provisions Relating to IETF Documents", hence the easier "TLP" common name.  To maintain this common terminology, while recognizing that the IETF IPMC is not a trust, the next version shall be also known as the TLP 6.0, with the new formal name being the "IETF IPMC Technical Legal Provisions Relating to IETF Documents" which shall be published starting as IETF IPMC TLP version 6.0 to maintain version consistency with the IETF Trust's TLP 1.0-5.0.</t>
          <t>TLP 6.0 is published by the IETF IPMC on its website.</t>
        </section>
      </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>All references to the IETF Trust in <xref target="RFC5378"/> (BCP78) and related operational documents shall be read as referring to the IETF IPMC effective upon the transition.</t>
        <t>Updated versions of required copyright notices in I-Ds and RFCs reflecting this change can be found in Section 6 of the TLP 6.0.</t>
        <t>Note that no required retroactive changes of copyright notices in prior IETF documents are to be made.</t>
        <t>While it is not necessary to update pre-IPMC copyright notices, it is correct and accurate to refer to the IETF IPMC as the holder of all the intellectual property rights and assets previously held by the IETF Trust, since these have all been moved to the IETF IPMC.</t>
      </section>
      <section anchor="rfc8721-advice-to-the-ipmc-directors-on-the-ietf-ipmc-on-rights-to-be-granted-in-ietf-documents">
        <name>RFC8721 Advice to the IPMC Directors on the IETF IPMC on Rights to be Granted in IETF Documents</name>
        <t><xref target="RFC8721"/> provides advice to the IETF Trustees of the IETF Trust on rights to be granted in IETF documents.  This advice is now direxted to the IETF IPMC Board of Directors in the same capacity.</t>
      </section>
      <section anchor="intellectual-property-rights-held-by-ietf-trust">
        <name>Intellectual Property Rights Held by IETF Trust</name>
        <t>The intellectual property rights held by the IETF Trust have been transferred to the IETF IPMC, as the successor to the IETF Trust.  Inquiries regarding licenses and other IPR topics should now be made to the IETF IPMC.</t>
      </section>
      <section anchor="rfc-streams">
        <name>RFC Streams</name>
        <t><xref target="RFC8729"/> defines a series of RFC Streams - IETF, IAB, IRTF and Independent Stream and <xref target="RFC9920"/> adds the Editorial Stream as the distinct publication streams of the RFC Series.    Mentions of the IETF Trust and intellectual property rights management in RFC8729, RFC9920 and their related RFCs are updated to recognize the IETF IPMC as the successor and replacement to the IETF Trust as the party responsible for providing the same role of copyright holder and administrator for those RFC Streams.</t>
        <t>Specifics for each RFC Series Stream were described in the IETF Trust TLP 5.0 section 8, with the exception of the Editorial Stream which was not mentioned explicitly in TLP 5.0 due to its creation after the publication of TLP 5.0. The IETF IPMC is assuming the role of the IETF Trust as described in TLP 5.0 and additionally it is formally adding the Editorial Stream into TLP 6.0.</t>
        <t>Additional details on the RFC Series Streams can be found in the IETF IPMC TLP version 6.0 published on the IPMC website.</t>
      </section>
      <section anchor="ietf-trustees-and-ipmc-directors">
        <name>IETF Trustees and IPMC Directors</name>
        <t><xref target="RFC8714"/> defines the selection and recall processes for IETF Trustees, under which Trustees are directly selected by the designated selecting organizations (the IETF NomCom, the IESG, and the ISOC Board of Trustees) to serve as Trustees of the IETF Trust.</t>
        <t>The process for selecting IETF IPMC Directors is structurally different but functionally equivalent. While IPMC Directors are not appointed directly by the selecting organizations, the outcome is the same: director selection authority is effectively exercised by the same RFC 8714-designated bodies, and director terms track the same durations specified in RFC 8714 for IETF Trustees.</t>
        <section anchor="corporate-governance-context">
          <name>Corporate Governance Context</name>
          <t>The IETF IPMC is a Delaware nonstock corporation with no members. Because Delaware General Corporation Law (DGCL) does not provide for the appointment of directors by third-parties, such corporations typically operate with self‑perpetuating boards, meaning that directors are elected by the sitting board rather than by members or shareholders or third-parties. This governance model is expressly reflected in the IPMC bylaws.</t>
        </section>
        <section anchor="ipmc-director-selection-mechanism">
          <name>IPMC Director Selection Mechanism</name>
          <t>The process for IPMC board composition is defined in IPMC Bylaws § 3.3, and operates as follows:</t>
          <ul spacing="normal">
            <li>
              <t>Initial Board Formation (§ 3.3(a))</t>
            </li>
          </ul>
          <t>The initial directors of the IPMC were the IETF Trustees serving at the time of the IPMC’s incorporation. This ensured continuity of fiduciary responsibility and alignment between the Trust and the newly formed IPMC.</t>
          <ul spacing="normal">
            <li>
              <t>Subsequent Director Selection (§ 3.3(b))</t>
            </li>
          </ul>
          <t>Upon expiration of an IPMC director’s term or their resignation, the sitting IPMC Board elects a successor director. However, the pool of eligible candidates is constrained:</t>
          <ul spacing="normal">
            <li>
              <t>Each director seat is associated with a specific nominating organization (IETF NomCom, IESG, or ISOC Board of Trustees), consistent with RFC 8714.</t>
            </li>
            <li>
              <t>When a term expires or a director resigns, the relevant nominating organization selects the individual to be nominated.</t>
            </li>
            <li>
              <t>That individual is then submitted to the IPMC Board, which is then required under the bylaws to formally elect the nominee as a director.</t>
            </li>
          </ul>
          <t>In practice, this means that while the legal act of election is performed by the IPMC Board (as required by Delaware law), the substantive selection authority rests with the RFC 8714-designated nominating organizations.</t>
        </section>
        <section anchor="protection-of-nominating-organization-rights">
          <name>Protection of Nominating Organization Rights</name>
          <t>The rights of the nominating organizations are protected by IPMC Bylaws § 3.6. That provision restricts the Board’s ability to:</t>
          <ul spacing="normal">
            <li>
              <t>Modify eligibility requirements for directors, or</t>
            </li>
            <li>
              <t>Alter or eliminate the rights of nominating organizations to nominate directors</t>
            </li>
          </ul>
          <t>unless such changes are approved by:</t>
          <ul spacing="normal">
            <li>
              <t>A two‑thirds vote of all then‑serving directors, and the affirmative vote of any director representing a nominating organization that would be adversely affected by the change.</t>
            </li>
          </ul>
          <t>The practical effect of this safeguard is that no nominating organization can be disenfranchised or have its representation diluted without its own consent, expressed through its representative director’s affirmative vote. This creates a strong governance lock‑in consistent with both Delaware law and the community‑driven structure envisioned by RFC 8714 and is in fact a more stringent control than exists under the Trust Agreement, where the consent of an affected organization is not required.</t>
        </section>
        <section anchor="ipmc-director-recall">
          <name>IPMC Director Recall</name>
          <t>RFC 8714 also defines recall mechanisms for IETF Trustees appointed by each of the selecting organizations.</t>
          <t>Within the IPMC governance framework, these RFC 8714 recall authorities are implemented through IPMC Bylaws § 3.3(c). Under that provision:</t>
          <ul spacing="normal">
            <li>
              <t>Each nominating organization retains the authority to replace its designated representative on the IPMC Board of Directors.</t>
            </li>
            <li>
              <t>When a nominating organization exercises its recall or replacement authority, the IPMC Board is required under the bylaws to elect the replacement nominee.</t>
            </li>
          </ul>
          <t>As with director selection, the Board’s role is ministerial and legally required under Delaware corporate law, while the decision to recall or replace a director remains entirely with the relevant nominating organization, consistent with RFC 8714.</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>
    <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="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>
      <reference anchor="RFC8721">
        <front>
          <title>Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents</title>
          <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/>
          <date month="February" year="2020"/>
          <abstract>
            <t>Contributors grant intellectual property rights to the IETF. The IETF Trust holds and manages those rights on behalf of the IETF. The Trustees of the IETF Trust are responsible for that management. This management includes granting the licenses to copy, implement, and otherwise use IETF Contributions, among them Internet-Drafts and RFCs. The Trustees of the IETF Trust accept direction from the IETF regarding the rights to be granted. This document describes the desires of the IETF regarding outbound rights to be granted in IETF Contributions. This document obsoletes RFC 5377 solely for the purpose of removing references to the IETF Administrative Oversight Committee (IAOC), which was part of the IETF Administrative Support Activity (IASA).</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8721"/>
        <seriesInfo name="DOI" value="10.17487/RFC8721"/>
      </reference>
      <reference anchor="RFC8729">
        <front>
          <title>The RFC Series and RFC Editor</title>
          <author fullname="R. Housley" initials="R." role="editor" surname="Housley"/>
          <author fullname="L. Daigle" initials="L." role="editor" surname="Daigle"/>
          <date month="February" year="2020"/>
          <abstract>
            <t>This document describes the framework for an RFC Series and an RFC Editor function that incorporate the principles of organized community involvement and accountability that has become necessary as the Internet technical community has grown, thereby enabling the RFC Series to continue to fulfill its mandate. This document obsoletes RFC 4844.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8729"/>
        <seriesInfo name="DOI" value="10.17487/RFC8729"/>
      </reference>
      <reference anchor="RFC9730">
        <front>
          <title>Interworking of GMPLS Control and Centralized Controller Systems</title>
          <author fullname="H. Zheng" initials="H." surname="Zheng"/>
          <author fullname="Y. Lin" initials="Y." surname="Lin"/>
          <author fullname="Y. Zhao" initials="Y." surname="Zhao"/>
          <author fullname="Y. Xu" initials="Y." surname="Xu"/>
          <author fullname="D. Beller" initials="D." surname="Beller"/>
          <date month="March" year="2025"/>
          <abstract>
            <t>Generalized Multiprotocol Label Switching (GMPLS) control allows each network element (NE) to perform local resource discovery, routing, and signaling in a distributed manner.</t>
            <t>The advancement of software-defined transport networking technology enables a group of NEs to be managed through centralized controller hierarchies. This helps to tackle challenges arising from multiple domains, vendors, and technologies. An example of such a centralized architecture is the Abstraction and Control of Traffic-Engineered Networks (ACTN) controller hierarchy, as described in RFC 8453.</t>
            <t>Both the distributed and centralized control planes have their respective advantages and should complement each other in the system, rather than compete. This document outlines how the GMPLS distributed control plane can work together with a centralized controller system in a transport network.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9730"/>
        <seriesInfo name="DOI" value="10.17487/RFC9730"/>
      </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="RFC9920">
        <front>
          <title>RFC Editor Model (Version 3)</title>
          <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
          <author fullname="A. Rossi" initials="A." surname="Rossi"/>
          <date month="February" year="2026"/>
          <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 specifies the Editorial Stream for publication of future policy definition documents produced through the processes defined herein.</t>
            <t>Since the publication of RFC 9280, lessons have been learned about implementing this model. This document lists some of those lessons learned and updates RFC 9280 based on that experience. This document obsoletes RFC 9280.</t>
            <t>This document updates RFCs 7841, 7991, 7992, 7993, 7994, 7995, 7996, 7997, 8729, 8730, and 9720.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9920"/>
        <seriesInfo name="DOI" value="10.17487/RFC9920"/>
      </reference>
    </references>
    <?line 195?>

<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>
  <!-- ##markdown-source:
H4sIAAAAAAAAA6Vby5LbyJXd4ytySgurHCRVkrpbUq1cqmqp5ZZkhR7WwjGL
JJAkMwpE0plAUbTDEfoFLx0xs57l/IM/RV/i+8oHQVa5e2bRJZIAMu/z3HNv
oqfTaVX1tm/NuTr5tGl0b1Tv1HtTu2Vn/wJfVka9+vHjC/Xq3ZtLpUP+4aMf
Qq8+DHVtQnD+pNLzuTc3sA5exttPqhrWWzq/O1e2W7hqoA3Cufr+8ZOnE/X0
ycPv8O+jh1Xj6k6vQYjG60U/bYzpptb0i6ndrOspPzc9e1xVYZivbQjWdf1u
A/eTKOqe0m1wsLXtGrMx8KfrTybqxDS2d97qFr+8ungO/zgPn95/fHFSdcN6
bvx5hWufV7XrgunCANL1fjAVKPK40t5oWPWl6YzXrbqAryfV1vnrpXfD5lwt
TVeFXneNbl0H0uxMqKprs4NbmvNKTaPp3qfPZLXiypvLqrox3QASKKVk2RNY
V9Ne8BvrefIZdrXdUr3EW+jCWtsWDLvx0+3yd2ismfNLvKB9vTpXq77fhPMH
D/A2/MXemFm86wH+8GDu3TaYB7wCbW/71TA/x3+7zrTLB3d4A+9v0Zt93io+
N+OFZtbdtcJd12arft1WlR76lfNoSdxOLYa25TB52ZquU1fwKF0AlTSEq+4h
Ls7VpVvXOvTTt88vP3Wgtg+6pdsMm8wvG7LE75b4fVa7dVVVnfNreP6GHfH+
xeV3T757Gj9jvMbPGLX586OHxedn8fOzJ4/P0udHT+FzhQmQdqhms1lVTadT
peeh97ruq+rjygYFeTCsIXiVpAqHSfwVs0/3ypuF8aarzTgZIXNtV7dDw1fo
x98EFWKOTop07nrTtqbuB4jrd95tjO936o3u9NKQAJfOb5wni4KoVzbUA6Wd
cgtYBUVF7yn4AL/hsqNApPDEgG1t6EXZtW2a1lTVPdzeu2aocXlUvVRjorT6
o/VL21mNuYi/bAF5INT0HFZbmQbUVI/Ozr6PgGRLbTZRG2+XK7DZfci/UxAH
VfMKvJCsMFP7O6sVrLcybaMgpeWJBtN3InZFfSAig4FM1bBno+Y7xUEa0DC0
1CVgk7fzAXULtBL9fJWcuHBt67a8FnjK+DU9/PzynUJYrAcP3u3bnQobU9uF
ZX3/+tf/kEj8299oVQtLbbxpDDs3zApD/hr3ooHeXJ6i2a9Mq7eAPKpz/RQs
NQVbLmyv6uLuI664AhEQS8Enjx5Fn6Sow7DsRx72ZtPqGk0Aq6MyOoRhjd91
26IxUDnvWsMG9CZswJh2DiHVWxNm6oPF+Me7kiyk1369Qn/OASTUACXB9/o6
Gr0jo2kPNu7NJqCIaR1c1bQL1EOr788e1o/BHJ2YYoK3gtU3aCWMJRTPfDH1
0HPSQTZ3AfITlUBdQDHTS1RBsIwNgY/DipzuarsyvhROL70xHDQpjgowcOCY
9aY1cWsdrmnbaEv8EY0YXcJW5wCgNC5lmY3zkKzXGcBPlh6UJVva7sa1N+z5
DUgdpWvttdnaYCYjJ2wtmAHKa2+hzGFkwTLk+bjOFqoFrLCT1UBMLCwQEwAP
N7bfzW4DR8gHoRL4iekEf3r0kERyIIk/YjZf8Bs9DhrYqXNb+pGhBDIy9K6x
uotOxZunUcw7wQelyJlgO7obwrk/zIoZAqNiEgY04t49oGEC9OHwblyLvoHC
vA3gBzx2AeL5vee+ff2v/Ni3r/+NT6K198xSIhyuOKHlJgQkvjP99ArhPkzG
Zt0MkDM1IQNcDCu0zhwjTTOIkrqQL+TPwJJ5ik33fytGgFbRU6eHUAM3x4AZ
4wBlBUqBBiLnTA5wRdQDlZasEqb6jXVDADSOKYxJ3zPCm+a4Y0CgVY64GTnz
s5kH2wugfXr/mlx8LzFEYHKRnEElZdvFHyCoUD+8UGhGpgcIDipxCyzP3S+p
hhD0f4o7/+f9yN9KCU65BjrAo6XQ33IbyZq0CLoNZTyyWCH9qWqMJlZAOZ8e
7t3G1qhH2otjJ0akwMysMBnZ+pz5gcnM9pBMAHJgD1CD33cTioRouGZPo5jO
4FCIaGgFYOOJwPdELWynKaFQMMAwi58RDepc5uuV7paGCBEWpq2ZK/S4+lM0
yVjYbCy5EtKl05lSBHpplZRbQKy6Hv4TBIb0Mv0AUY/ZgHFFNBCq6mZjNEFO
1jeDINWdyBHVa7PkzLuxgdS5//H1u1OF1BlN83B2Nv1+dsZgucUSRdBsYhT0
dm3IGABJ0yuVe7S0DVU3vIPwuQCNUXUA0UFuSDZKKyRa2G1BkYceSQEAAezA
6sH8eaBiX9RavhuDSSruHsAACIBBie6ZLxAQGFRkK9tJZfzzYIFLgSSbHWWK
mjvbgm0xKArQC0YcjmxvesWGJAg+UAQlR+YExQbJHJKFIRgmiiztPkLcy7Ke
q+12O4tN0Siu8QYO5JKGldkIiCdok1qz8Xo59MZXCFUxft1iYWvonRP7MxiM
tOp2ZWvkSaw0aEWsiMNMLR3EDWUL2w0ilFw9QpCc3fMdsE62JKcZbgqq9QX1
aSlCJfEgLaHfFhBBxZkQNAXi55j/aOpVh+l/PMrVD7OzU1Fog5egeUr5L+Qc
XbfnbPDXpXchFK1Yp2+kaMDj3XVqi1zblMUhJkRntiVFirUhJfmea12SzOiw
K7eam36LnAyWXBOPxADjeiNEgsY53DdUlXzgeqh4AILhWFu0HiVEYzFeUXes
4RiukkitkzKPD9xoj1WR8i3zoOTcmGuF4gnHaJdjYMbEGhS4YTpbYNnCDVQP
oiYEjohDxNXAmKZk0eCtNdC1xS7nesGIbMe+hLvElRdNYzlAsUJEG1kk7ejZ
GFyj7jo6jrUSJhKNVPg2B1MZ/dQ6SG3JmZBgSAJ9jAt3BfN7dIMwq1HDSWh+
QO9zimiANW+5oOUSAb3F2nWAXNdAh7uo4QmsdRIrQ0ilAYEP3EjprIOt5elC
e+hTW+11LpdJ2QJp9+trdFVKO44qsiKAgV6b2M6XYEod6kmh6K8w1clEnI6q
QrJZyA/WWPTBTVEMlyKXpyFyGfHCdq51S4gkAJXWpF6DG7Lj3QbgQpx0MDh8
6VPxTamCI859Xwh8TTIQIqyU5uFOi/z2/wyiE8HIJE4OH4AqTw/pUIYqCBd1
+AHJQ2Gy+DsOXSFDweK7rEP23G8CrSIxhqyeFUaj5e3Lrpp2zvwLU1PQMJg0
oMlIXLihK7sahLUXHgxINTzZ4Fh3dUj+9wY196GNevL0VAKegbKsiDlqR73T
rb0SSmsWC8MMbNhInSEuZGVc90kgK6UpqH6E4tyWZ7h1K1WAo5uYrao1VpyM
xh+YDKkf4jRB/AMSvHW9NNedy1tDH+idcMfElhfHJdpAhTno3XHqAtagwtGg
az9Tjtk+5lGeneR6AFVlSmY72GciTwpL40lUXQ9ezkHIBYfml/RbQW3Pg55/
O4eUMZfpj3aV48FQsAJDELgrjVybogNq/drdjPpOorc8MeCZtLpobmxt0k0o
9BUVdhpUdocJ855lZNu+lOFmHDEUCcDBjXtAcAsrAdX2t0tqGBMOB024nS+3
W462y7RYeiBZXgYzyFC+jFtv0uO5077BDbOuwu8DgmGtN7rm8cC9e7cMHcQO
P4lXijMbKp93Ovi4K9l75LnYr/gjwk9+wdwU7PGqw1TCWu0Bu33DE3assVI7
BcVyUx1Wbmgbspykze2xoz70gD7r0s/PwM+NAV6O6xc8obhbTrMm6tXFc/jz
HlYlcM1ncXIn/cwrP3v26Azn2E3DWv8YT+rSrfx7QwSu7vd6xiD7SmiRKCQY
8k71BodAAnojV8SJ1K0uXOeZE7NNtABxQhQ4snfrE5bz9M3vsUR/9+lpdjAX
hTyTPSwn8shGk4xxWtUy7+H0iwWeQpymvXuIKiBF4NMAN7F43gSmFuaEbWjh
SoiED3zoUHPbYzTU/Gzg6B0aAkDm197OOXNHgmMlQF4o/bJ6WpAU86U2mz6d
JR1xPlMN5HGI6Wt2qMFB+waCwGI7DVvGPRrut7Hm1/A4z6doVkC2KwIH9pOH
iqOfSMMOx+ZHAijsax1FYPPmNkLqClMx+IrXZOUDZSEgXVE5czcCWwFbahNg
H7ghHFTk/YAbU7DMmWIJKJpPQcU97KY03iseGRkeflcgAwWgacXZHNc4cVMy
/DPSRJerT/hURpyd98TIsjI04TUzyQPj22VHiSbbgVXL019odpIN3rr1pVvH
44gPLyep+3714Q9FtYhbn2IUcf8Jfr69gMl4WVQjxbIw2fpFEQoIWQNAjqdo
gN6UKGSv5gM0t0NXp7hBpnSjW7g2U8xtRmvJ6RyOyZylspmMJTa6xTBsBzf0
0KpQLY2gcS4rZDXQhXSoiVNFuDPRTRTwi/G1DdklhDsQEd++/i8GxbRw0Ry6
8DhUT3vwSAUPva/z880QO8O9M8+87GH4SG98mYZTL/PcCY9ggSOMjwEwycsz
zi70rr7eP91EkALKuqYDTSgozyGOccCVHosvg5RnEq/1Vt2/enn5+hTIi2HU
iiObeOAsDouHb03yKNnR+maKKE/2ouODQqqAL4HwBFuaB8OC4jnlt69/lxkw
d25zDGtYZG10l3rOZi9+RkkF2Z+fVLD6iqAToWUXDYHjEuhQvOF6Qt/3pJ4x
VSuGf2vXmJbC5wvOdZDsSl9RVAx0C8//4qyjDHeAuxiQbww2DDasD5OPFyHh
8TzUcRuEOzM8MbMkgsiTxn/+D0TV49njSTGgROSJR/PhvKp+C/wF1gFHM068
SKOb+/Hx+/r0NNJCvjWbOYIGA6wfv6qBuIJIQ13z/hA9Pvbt6z+QvhZhICbG
t5S4j6NZM+YoPLawzVBbbHz2DrV2XJpaSEmKvGJgeDiR5Cn12jSRFf5WfcjT
9iNOyaaYoyk+YTMK3rY+lVstlo+WIa0QAjiAmEoxYMATk714LDg97UgENJGn
uOJM/eS2eErND2+coxcIDKhMTAlKZGN5FEqdXocECKOCnPwj8psC/3QvVMCB
Mft0OB1hqYbUBo6gD+BVjiVjyeFyg7F5vNJM8uij5y0y1M1ArM8rPO9gQ5FB
DWWczqKy1QTVgY2aG2iibpUuiAG5SW0sIBPSX+6/5CHT4M4fES6KW7hQdHyo
05dtV/LOJJ4HyK2p3ef6jjfLiB8eTZSIJOLIw/2N4Rcuklur6hUOAXBaUNM7
BbA8Ypq8BMXDNZq50hAL7mO3S2jiiMh4CefYlOWAuk8DljiA3GV4h39OJQwh
9HswKg4rjhVGPMUPmdUeL4G3OCSiHfSdvSwMwr/NN/+h9B43pQw10qgIUNy2
PMH8hhdnBY/g3w8z9vYmzv9IJW9joJClKGG1YEnvKGneyHSdUoyviC3jC045
PQOmATxz0SIhx46itRxuHLlJnVtVgaCJEZpXraqha7EAcK2UWRJqDXXW04Rk
viNhL1S/dVAkqVoFdePkJJJHNh1ciUBciBxBUS8WVt7ay092uzIN6cyi4/nn
rfnHIUuNOE5yG2TlyKY0MascoaxIIpgU/BDcTMDSq3dBL8xywDC2IQ3Zbtta
WgRopE238FCZV8TeQHYaTNCLVlEJfqKx7RChD/giHwZueVpLr4pIQadTR++G
5epglRuzj/hjO0opo3aNBwu9xxO9gj60QM3AObY7gMq5gz9lwiZ34RR+gFq8
gwcbb/HQOBJvYD0dRzlbu6CWNBWgUdECUUTzWw+YCeCLrqdCC/0gUyI6UgoF
tHEVvYhvak3kJS4WhwwmdTD5es89MreMWHSUBb2nXoqO75LMeBgQuy/ptdaR
Ih1ptop+AZSnrl4g5JZ2AWerYOySpxXOWcTh+ERGlIVoIk0ESit5afFNNbRQ
ETbHSNn9+nSmPol5S3TK9fq2UPfYL3cMXhmnaSJDQxYK0wKcRxFbNsWHo8Si
LN+2f+yNguQD2YFBIs14klyT8WY23F05c8Es15PiiYMDKUaH3dxkBOc03MBy
SuMgQ8OIdMje7sZipFTLLwLAD5OiBDdAjqiA8PRrX+191rImDyFgegTAVD7/
HYW5mzFVe6ekMoCLZZUu8Ntx+/2g2Fbe9xqP6+jACseB/JuM7mM7N4c2EF+N
LaYDMz6UhjsO3oFsnbvOL2zuitef+DU7bD00nggnH0Abw5M+eGg5YCNJwVsO
tmvt/Y7sNPScK/nNNXqZ8IOpB0qBSzRdI6dOYfw6Jb3niZMPubveu5tWenXx
9uKXrUJ3yltR8tr3HFp9XOSixtPL1jRLOUzYP5BOA6df/Upgtkoz+DTBMxH6
yUQHo7yD0wNs08r/s2Cifu9W0NsbIAcGv0A3+5NuQRK49DN0yS02Um9wlucx
nf9oKcR/hsKMB94rfKRT7wwkWMD4/dnTLFs9N77R8P2z6ZodNlP9XwzS3X8B
k33DYowzAAA=

-->

</rfc>
