<?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.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-deen-ietf-ipmc-update-04" category="bcp" consensus="true" submissionType="IETF" updates="5378, 8714, 8721" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.1 -->
  <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-04"/>
    <author fullname="Glenn Deen">
      <organization>Comcast-NBCUniversal</organization>
      <address>
        <email>rgd.ietf@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="October" day="15"/>
    <area>General Area</area>
    <workgroup>gen</workgroup>
    <keyword>IETF IPR</keyword>
    <keyword>IETF Trust</keyword>
    <keyword>IETF IPMC</keyword>
    <abstract>
      <?line 57?>

<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 63?>

<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 <xref target="RFC5378"/>, <xref target="RFC8714"/> and <xref target="RFC8721"/> 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">
          <name>IETF 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">
          <name>IETF Trust</name>
          <t>The IETF Trust, historically, has published information related to licensing, assets, finances and notices of actions and changes on <eref target="https://trustee.ietf.org">the Trust web site</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 when a contribution was made, 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">
          <name>IETF IPMC</name>
          <t>The IETF IPMC, has established the <eref target="https://www.ietf-ipm.org">IETF IPMC Website</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><xref target="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" <xref target="TRUST-TLP"/>. Versions 1.0-5.0 of <xref target="TRUST-TLP"/> contain basic common licensing declarations and required boilerplates and notices in I-Ds and RFCs.  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"/> 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 directed 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, the IETF, IAB, IRTF and Independent Stream, and <xref target="RFC9280"/> adds the Editorial Stream as the distinct publication streams of the RFC Series.    Mentions of the IETF Trust and intellectual property rights management in <xref target="RFC8729"/> and  <xref target="RFC9920"/> 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 <xref target="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 <xref target="RFC8714"/>-designated bodies, and director terms track the same durations specified in <xref target="RFC8714"/> for IETF Trustees.</t>
        <section anchor="corporate-governance-context">
          <name>Corporate Governance Context</name>
          <t>The IETF IPMC is a Delaware nonstock corporation. 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 the directors are elected by the sitting board rather than by shareholders or third-parties. This governance model is expressly reflected in the <xref target="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 <xref target="IPMC-BYLAWS"/> § 3.3, and operates as follows:</t>
          <ul spacing="normal">
            <li>
              <t>Initial Board Formation (Section 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 (Section 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 <xref target="RFC8714"/>.</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 <xref target="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 <xref target="RFC8714"/> 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><xref target="RFC8714"/> also defines recall mechanisms for IETF Trustees appointed by each of the selecting organizations.</t>
          <t>Within the IPMC governance framework, these <xref target="RFC8714"/> recall authorities are implemented through <xref target="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 <xref target="RFC8714"/>.</t>
        </section>
      </section>
      <section anchor="ietf-ipmc-recognition-of-ietf-bcps">
        <name>IETF IPMC recognition of IETF BCPs</name>
        <t><xref target="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-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <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="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>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="IPMC-BYLAWS" target="https://www.ietf-ipm.org/administration/bylaws/">
          <front>
            <title>BY-LAWS OF IETF INTELLECTUAL PROPERTY MANAGEMENT CORPORATION</title>
            <author>
              <organization/>
            </author>
            <date year="2025" month="December" day="10"/>
          </front>
        </reference>
        <reference anchor="TRUST-TLP" target="https://trustee.ietf.org/documents/trust-legal-provisions/">
          <front>
            <title>Corrected Legal Provisions Relating to IETF Documents</title>
            <author>
              <organization/>
            </author>
            <date year="2015" month="March" day="25"/>
          </front>
        </reference>
      </references>
    </references>
    <?line 202?>

<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:</t>
      <ul spacing="normal">
        <li>
          <t>Kristin Berdan</t>
        </li>
        <li>
          <t>Glenn Deen</t>
        </li>
        <li>
          <t>Lars Eggert</t>
        </li>
        <li>
          <t>Joel Halpern</t>
        </li>
        <li>
          <t>Victor Kuarsingh</t>
        </li>
        <li>
          <t>John Levine</t>
        </li>
        <li>
          <t>Kathleen Moriarty</t>
        </li>
        <li>
          <t>Jon Peterson</t>
        </li>
        <li>
          <t>Wendy Seltzer</t>
        </li>
        <li>
          <t>Sean Turner</t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA6VbyZIbuZm+51MgSgerHCQllUbtVp1cKi0tu0pSVJVa0eHw
AcwESUQlARrIJEV3dIReYY4TMXOeo9/Bj6In8b9gSy7q9syhSyQT+PGv378g
ezweV1Wnu1adi5OPq0Z2SnRW3Kjazo3+O3xZKPH21d1r8fbD9aWQPv9w53rf
idu+rpX31p1Ucjp1ag108DEuP6lqoDe3bnsupvWq6om+PxfPnv7h+5H4/g9P
/gP/nj2pGlsbuQQeGidn3bhRyoy16mZjvVrWY943bnFzV1W+ny6199qabruC
PcSNeCBk6y2crk2jVgr+mO5kJE5UozvrtGzxy9uLF/CPdfDp5u71SWX65VS5
8wrpn1e1NV4Z3wOHnetVBbI8raRTEqi+UUY52YoL+HpSbay7nzvbr87FXJnK
d9I0srUGuNkqX1X3agtLmvNKjKP2btJnUlzx5PqyqtbK9MCBECKQPQG6ks6C
31jOk09wqjZz8QaX0IOl1O250Cs33sz/iAqbWDfHB9LVi3Ox6LqVP3/0CJfh
L3qtJnHVI/zh0dTZjVePmAIdr7tFPz3Hf41R7fzRNyyC69ko+ai4b8KEJtp+
i8K3nk0W3bKtKtl3C+tQk3icmPVty67yplXGiJewlR6ASBI8VnbgF+fi0i5r
6bvxuxeXHw2I7bxsaZlilbl5Q5r44xy/T2q7rCpj3RK2r9kON68v0U3jZ3TW
/PnsSfH5efz8/Oz7x+nz8zP4XGkzK6misccvfrq6+HRLC0UMvRc/jfFH8f51
8Ip3d6+url5d3n28uBIfbt5/eHVz95O4vnh38ebV9at3d+Ly/c2H9zcXd2/f
vzthStLNVWGIzWYziSplezdLbbTvHKno0XTbyo1/RHvJ/cXZ47Nn4ydn4yeP
K/j17ubj7d347urDkNFL65yqO9WIKzWHePjg7FpjLHoADXAG9E8AEBLipa37
JYShP8xhh3GgCo9s4np+NG7xhPEqnTBk9smz8eOn47NnVVWNx2MhpyhaDfhw
t9BeRFoigA5zlE4AGJOdcGqmnDK12kU1kECbuu0bfkI//s4LH8FuVOCi6VTb
gkp61sZKuW4rrqWRc0UMgMZWlpU+qaqX2tc9gZewM6CCrGIMCPgAvyHZnXCm
IEe1tmC8CQu71E3Tqqp6gMc72/Q1kkfRSzFGQooftZuD2aXo+JcNQDgErJwC
tQVYURtQ5eNnEdl1Kc0qSuP0fAE6ewgodgrsoGhOgGMnLUzE8GSxAHoL1TYC
gDHsaBAER0Gv5CYL6xXgnTToTtOt4FD3qBgidQkI7/S078i9kNLQrYCFtrUb
pgWWUm5Jm19cfhCYYOoefNV07Vb4lar1TLO8P/8cYvuXX4ioBkorpxrFtvWT
Qo//jnVRP9eXp6j1lxAKG4BvYWw3BkWhE890J+pi9QFLvAQWMCFhKJ5FkySn
Q6/sdgzs1KqVNWoAqKMw0vt+id9l26IuUDhnW8X6c8qvQJd6Ch7VaeUn4laj
++OqxAvJNcz7aM4pIK3oIa+6Tt5HnRtSmnSg4k6tPLKY6CBV1c5QDimePX5S
PwV1mKCKES4Fra9QS+hKyJ76rOq+45iDYDYewhOFQFlAMNUFpwJf2VUEbgeK
HO1is1CuZE7OnVLsM8mNCiywYJjlqlXxaOnv6dioS/wRlRhNwlpnB6AoLnmZ
7IYhac8oSELMPQhLutRmbds1W34FXEfuWn2vNtqr0Y4RNhrUADUKYGxPngVk
yPKRzgZSLlDYBmrAJmZn8AlAh7XutpNj2FhExIi/YLoL4RG+nz2B76ApV5SG
ctdPgLixG/qRwQNi0He20dJEO+LiceTsm3CDh2fn14ZWgwd3+4EwQSgUXL9C
+fXgASSjAO1+fzXSom8gGB8DiAHbLoA9N9j39ct/521fv/wP7kQFDxyoxDSk
OCJyI8IOZ1Q3fokA79lHLbDieP+qhzCpCQzgoV+gdqboXJJhk8SFECETeubM
hfz6f0o/AFDRUqf76AKLo4/shj4FAnKBCiLjjPagJIgHIs1ZJIzutba9B/yN
UYtx3jGmq+awYYChRY7NCRnzk5p63QUM+3hzRSZ+kCvrzDLpFODUi1R5YaY1
vyWxgTf/JZL868NYpaTqBNLyKaczC9gyD/1AeUwIh0QE7YHKPUBsxU+YaKMk
JXiK37S5sytdoxzpLHaK6GoBMiaFLriz2KsCIOaxBarBfNsRGTSqqRnwH6MS
7AKOCZ0QHDMKwDsSM20kxQWyAeij8TMGdZ3zc72QZq6okvlLKpzERk0F2i/r
Ybf0O51AwYnQFJfmcIDqx3TwX8BJiAjV9eCo6MDoClSrQe5brZQklMiyZYSn
7JD42atcH0KZeyqwS0A1PJk8Hj+bPGZ822AiIQBV0b6dXlKGAYMTHMcShTL6
UjZqlM6jZIQ6QmAoA34HzEEGEAAChUICyyLsMCEnr/GUGeAAxMXUq7/1lJuL
1Mir0V9CghyAAwQwaJaKM/UZvAD9hpSmTUhkf+s1lD7AyWpLwSCmVregZPSE
ArC8ClbG2mz8kjVK8LknCHKOhQ62CSAR5vbeKy7rmNthdD/IvO5gD/tqWSOV
4QXYFHAh+9Vu00Mwh8WNnc10rWWbKjCFrkaetlnoGmsVlgRYpcqEnUjMLXgF
+T0rA/yP7LcT+Tkqua2ixRwweChI0BXlB/U1MYTAWVobgx/l46TcFBCcPfpO
1QuDgXzYh8V3k8enQSBqm6B/SZEc6mO0x8CCYIRLZ70vuiEj1wHFYbu5T52J
bZsSraOXG7Upy5QI1imEBxa0iTMl/bY8aqq6DdZFQHJJtRx6DSeAkNlpNMWV
SlWVZTwlKcHTHPSzWqMGydMbjY6I8mNiRT8MEdLakHtxw1o6TFUUSLk4SQaO
QVQIn5CKTjkEV1zgghBrLisLtJrZnrA8SkPwh0hDBRQoVJXVLFhsCTXUbJuD
uChTsJhBe8KqYM6LptHspIj34QgkvSDrRgfbaXKj8ViqUB5EJRX2zQ5VRgCV
8CFT5GhI+BKcfTfgv+XQx8cJjNd7ZXYOEwl45TSnp5wEoMZfWgOQdA81qokS
ngCtEyhy07zjl18m4kdOBT7lAiA0WEKIB2YWU+l1HUgXqoFmspVO5syYNFHg
6zCVRjumuASfsMmfeFQQzsFI1sa2dg72hXBvVSrLuV05XJhDxMYxAIft5y4l
veTAOEUdaigAyyhDFAY8mR5QTEIy5D6EtPn/NO1JQK/ETjYqgIijTdKXDgTM
RRm+w6RdqCz+jnNdiBtw/m2WITvO7zxRCabGApgFRqXl48uek05G2O98hLuA
U16l6UXGyMIMpmwAEGxeO1Agpcykg0ONyH6dvDvFiKhVpqjs+zvdxdFuAplU
s5nigqdfBeCnikOHEdbHgB/rGCQg8YFC4phf49FtgGR2aioaRS0xBWRovOWS
Q3wXW+xgFuDgne1C+2lsPho6JWdDqZYK0dlhjlYA9253DoCjCNAGoXiDFv1E
oaW7GD55oJDBGSB+TGrbO2cUdoZaiMczdd27cMlCJthXf4i6BSTbPP341dlc
mP2o7mDftTst8ToMPcFfFxJLW/IOSL5Lu97pzKiI5J6a5wDiolnrWqVFyPRL
yrI0vDP7cXLDPLJu34SBX2zCC78vRw2hSgDJhqclKZTy+8MXPM2Vp813Tsu1
Z+g4AvkwueBq4YAGxAsrXYMHZlFDEe0RAmu5kjX3zw8eHOnKgxp+CEbZbdm+
ad/DlmTjkeFiU+AOMD/6DbNE0Mdbg5GEedMBYruGh86Y0kKqCtiVm1O/sH3b
kOZC1Bx3HXHbAfgsCzM/BzM3CspkJF+k7GJxnoGNxNuLF/DnBugSqOZrvrB4
lMdVeBODuNg0LPereAkYlkZ9NFRO1d2gNfN8dHQu4oZ4wypQXOOcJKDejjHi
0OaoEZd5LBMRPKgBtwbWn58R625QqLlvX8hmu3IqyOPJ/dwRtqwkMRanOC1P
YTnqYjYnz6bB5wBHAzQR5ORLJRuvBLDFK0wIDnDL4/eauw8lIcFnrUaTUKcN
AV9DPx0H9WXFhWVYaEPF90Uxoj7XatWlC5V9Y49CTYHtOaL4ki2ocN68Aqtr
bFPhOMwveEjDfSwm9xr282iHenDSW+EpcGDYVFyAxHprf3p8wGP8UOLIAqs2
V/Ehk3DNBV/xWaC859rggbbIlbkZgKOgLGoTRO+ZwO/l4KGz7dZauTiKoF/0
fwEIB3BNcTtIFwkMaNwcwYB8T7XB2OzSOL0SYWymQhtbEh/x3USwdT4SnUqH
WQTTzMUc6F7PDcVYOA6UWl4kQ6uRVPDOLi/tMgLS7Zs85Xl7+77ID/HoU3Qi
7v7AzMdTVpi4BtFIsMxMVn6RdjxCVA8Q48gZoDOkUrET0x5ay97UyW2wNFrL
Fp5NBBczO7TCHRVOn6ymRJmUFXR0RDGsB9t30JJQ9ox4cR4oZDHQhHSzh1M7
WJnqS2Tws3K19tkkBDmFT4wLG02hCY6D5nQITzXw6vc+E2j62Hvt3/wFX9tz
oNCbXqYB0Zs8+8GbSOiWdmfjGOXlXZ/xna3vy1u+iXgBnotDpbQsvklSDuav
5EY8fPnm8uoUChTFMBXHJPGeNZgoXjo1yYakOe2aMUI6KYhm6AUXHt8g4flv
6A8U4yfez3398p9hqso92RQdGYgsFVi77CabgdfshBKEfN4t4IQF4SXiyRa7
D6c4a9CcYsDuhOuwYtK2tI1qyVM+4wAFC9nQM6iESj//XLxLAS17FSYLpXsD
ukUHvFbYEWi/3A822sJs4y2g5T4Hj2c4Cp4zOE7883+/fvnH08nTUTEWRLSJ
d9L+vKp+DzUK0AJTMza8TsOSh7G3AQoP5elprP94ddZzxAqGVbf7mgLCCQIM
NcXFbLrY9vXLf2GdOvBIUje+58T9Gk1uMTRh20w3fa2xwRlc72w5IbUQiOR+
xaRufxTIM9+lamL593txm2fXB2wz0MYUtfER+04wvnYpz4IjkRqickgwjH32
J6UdskxIATtGA58s6nc6lKrNVDFFihPxg93gLS1vXllLF+gKpKbyCHJjo3kM
SU2dwaoH/YNM/QqLmgL5ZBdqAAv67NLlbMSjGkIcigO5B6zhji4mG0406KWH
c8woDzc6PqLAuAnw9YnvKUhTpFFFESgzr6y2AOgOFLSGjukoez5okBvSRgNE
YaXLzVbYpBo8+Q5xo1jCOQIv+KZLMEzRpiTzxEotLk2tPad2XBzm67A1FUPE
EXsfnq8Uv3GQ7FpVb7Hhx8lATZfqQB7BLbwExPMzGnbSnArWsd2DV+IUSLng
0rEDyx71kIYpcbi3zTgP/5wGPwT370CpOJg4lBPxTtvnghbsB+CCJiyT3xGD
xLQFTWYXCAPz7/Li96X1uANluAk9SQCLY+QJ61dMnAU8AoXfTdji6XUtEsvp
6CykLYpaGTClsxQ512G0TXHGT4I+40s+OUY9xgLsuWixHMdeotXscuy9SaSj
4oDjRC/NVKuqNy3mA06cYXaEkkPSdTQRmW6J2QvRbSxkTMpgXqxtuN/jEY2B
JxGQC5YjOMrZTIeXAfNOsy1DkS4MDI85j8Yguy113jiwbbAmx2JKUmGVvZQF
SfUlBQA4ONdf6fUzL2dq3qMra5+GaseODg0C9M3KzBxk6wUVb8A7TSLobaMo
BO9odNtH/INykW/jNjyUpZcnQpKn2z1n+/lij8paDWF/V48hpVGzxqOEzuGV
WlFStFCXgXG02cPLqYU/ZdAmc+GwvYecvIWNjdN4FRvrbih/DHt5jInhOzOa
hkMzhBLJ7wtgKIAxTMdXxrbl4ogudHyBb5xOL+L7SqPwKhPzQxoL2TAZe2Cf
MKiMgDQ5VBXdUC817Lxo6h/br9BsLWPNdKDbKhoGEJ86+gAkR/oFnKaCunXR
KBbmmcUp+CgMJUveAjsRL3UITY1vbKGOCs85VqY9rE8n4mNQcglSOXcf83iH
TbNhDMuQTSMZmrKQtxY4veO4ZWe8P0IsMvSx82OH5ENYkC4YK9KQJ/E12j1M
+28n0Zw7S3ohj+L0IOSl/Z5utIPqNOHAzErzIEUTiXTZ3W532UgRly/k4YdR
kY0bKJQoj/D4ayj2sIBZkoUQNx3iYMqkv1bN/Er1VA2uKsMILqZYesDvje16
XXgJandWR1dTOADk38K0PrZ3U2gL8RXRYj4w4UthWLH3LmBr7X1+cXFbvDrE
755hIyLxRjbpHxobHvPBpnmPjSU5bjnMrqVzW9JR33Gc5Ne56A07KNR7cv9L
VFsTLpr87muF9L4jzj7C6nqwmii9vXh38duo0MrwjlF4+3kKvT4SuajxnrJV
zTzcHwwvhNPE6d9+Ty5rpeldGuGpiP6kor1Z3t6NAXZsgC9j8WdHY2bxQrlG
Gvih+F8XxtD7wzmv5nNgCL79yULr+4NsgT98+KMmF/8z5Ge8V17QioURVwqK
DIW0odNusRe7xiEgyEQrjPigIAa9RRqflGm22G91f1cOvt9C7Svuemfg278A
o70z0wA0AAA=

-->

</rfc>
