<?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.18 (Ruby 2.6.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-davies-internal-tld-08" category="info" submissionType="independent" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.1 -->
  <front>
    <title abbrev="Private-Use TLD">A Top-level Domain for Private Use</title>
    <seriesInfo name="Internet-Draft" value="draft-davies-internal-tld-08"/>
    <author initials="K." surname="Davies" fullname="Kim Davies">
      <organization abbrev="IANA">Internet Assigned Numbers Authority</organization>
      <address>
        <email>kim.davies@iana.org</email>
      </address>
    </author>
    <author initials="A." surname="McConachie" fullname="Andrew McConachie">
      <organization abbrev="ICANN">Internet Corporation for Assigned Names and Numbers</organization>
      <address>
        <email>andrew.mcconachie@icann.org</email>
      </address>
    </author>
    <author initials="W." surname="Kumari" fullname="Warren Kumari">
      <organization>Google</organization>
      <address>
        <email>warren@kumari.net</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <keyword>Internet-Draft</keyword>
    <abstract>

<t>This document describes the "internal" top-level domain for use in
private applications.</t>
    </abstract>
  </front>
  <middle>

<section anchor="introduction">
      <name>Introduction</name>
      <t>There are situations in which private network operators may
wish to use their own domain naming scheme that is not intended to be
used or accessible via the global domain name system (DNS), such as
within corporate or home networks.</t>
      <t>The "internal" top-level domain (TLD) is specifically designated for this
purpose. Names under this TLD are not resolvable in the global DNS but can be
configured and used within private networks according to the operator's
requirements. This concept is analogous to private-use IP address ranges (e.g.,
<xref target="RFC4193"/>, <xref target="RFC1918"/>), providing a similar function within the DNS
ecosystem.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>

</section>
    <section anchor="using-the-internal-namespace">
      <name>Using the "internal" Namespace</name>
      <t>Network operators have long relied on various unregistered names for
private-use DNS, often in an uncoordinated manner. This practice can lead to
incompatibilities and unintended consequences for Internet users. For instance,
an organization might adopt a name for internal use that is later introduced
into the global DNS, resulting in name collisions and unpredictable behavior.</t>
      <t>In almost all cases, an entity should use a subdomain of a global DNS
name that it controls. This ensures that names are globally unique
and avoids the potential for confusion that may arise from the use of
private-use namespaces. However, in some cases, such as for isolated
networks that will never be connected to the global Internet, use of
the "internal" top-level domain may be appropriate. One such example
could be for communication between services within containers and other
virtualized environments.</t>
      <t>Entities choosing to do so should be cognizant of the implications of this
decision, including:</t>
      <ol spacing="normal" type="1"><li>
          <t>The potential for collisions if multiple networks using "internal" are
interconnected in the future.</t>
        </li>
        <li>
          <t>The risk of leakage of "internal" names into the global DNS.</t>
        </li>
        <li>
          <t>The lack of global uniqueness of "internal" names.</t>
        </li>
        <li>
          <t>DNSSEC-validating resolvers relying on the global DNS trust anchor will fail
to resolve names ending in "internal".</t>
        </li>
      </ol>
    </section>
    <section anchor="comparisons-to-similar-namespaces">
      <name>Comparisons to Similar Namespaces</name>
      <t>Several other reserved namespaces may superficially appear to serve the same
purpose as "internal", but are intended for different use cases.</t>
      <ul spacing="normal">
        <li>
          <t>The "local" namespace <xref target="RFC6762"/> is reserved for use with the multicast DNS
protocol. This protocol allows for resolution between devices on a local
network. This namespace does not use typical DNS zones for name allocation,
and instead uses the multicast DNS protocol to negotiate names and resolve
conflicts. By contrast, "internal" is intended for applications where names
are specified in locally configured zones.</t>
        </li>
        <li>
          <t>The "alt" namespace <xref target="RFC9476"/> is reserved for contexts where identifiers
are used that may look like domain names, but do not use the DNS protocol for
resolution. This is in contrast to the "internal" domain which is to be used
with the DNS protocol, but in limited private-use network scope.</t>
        </li>
        <li>
          <t>The "home.arpa" namespace <xref target="RFC8375"/> is reserved for use within residential
networks, including with the Home Networking Control Protocol <xref target="RFC7788"/>.</t>
        </li>
      </ul>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>The "internal" top-level domain has been reserved from delegation in the
global DNS by the ICANN Board <xref target="ICANN-Board-Resolution"/>.</t>
      <section anchor="special-use-domain-names-registry">
        <name>Special-Use Domain Names Registry</name>
        <t>IANA is requested to add "internal" to the "Special-Use Domain Names"
registry <xref target="RFC6761"/>, with a reference to this document.</t>
        <section anchor="domain-name-reservation-considerations">
          <name>Domain Name Reservation Considerations</name>
          <t>This section exists to meet the requirements of <xref target="RFC6761"/>. The answers
below are adapted from Section 6.1 of <xref target="RFC6761"/>, "Domain Name
Reservation Considerations for Private Addresses".</t>
          <ol spacing="normal" type="1"><li>
              <t>Users are free to use these names within the "internal" top-level domain
  as they would any other domain names.  However, since there is no central
  authority responsible for use of these names, users should be aware that
  these names are likely to yield different results on different networks.</t>
            </li>
            <li>
              <t>Application software <bcp14>SHOULD NOT</bcp14> recognize these names as special, and <bcp14>SHOULD</bcp14>
use these names as they would other domain names</t>
            </li>
            <li>
              <t>Name resolution APIs and libraries <bcp14>SHOULD NOT</bcp14> recognize these names as
  special and <bcp14>SHOULD NOT</bcp14> treat them differently.  Name resolution APIs <bcp14>SHOULD</bcp14>
  send queries for these names to their configured caching DNS server(s).</t>
            </li>
            <li>
              <t>Caching DNS servers <bcp14>SHOULD</bcp14> recognize these names as special and <bcp14>SHOULD NOT</bcp14>,
  by default, attempt to look up NS records for them, or otherwise query
  authoritative DNS servers in an attempt to resolve these names.  Instead,
  caching DNS servers <bcp14>SHOULD</bcp14>, by default, generate immediate (positive or
  negative) responses for all such queries.  This is to avoid unnecessary load
  on the root name servers and other name servers.  Caching DNS servers <bcp14>SHOULD</bcp14>
  offer a configuration option (disabled by default) to enable upstream
  resolution of such names, for use in private networks where names ending in
  ".internal" are known to be handled by an authoritative DNS server in that private
  network.</t>
            </li>
            <li>
              <t>Authoritative DNS servers <bcp14>SHOULD NOT</bcp14> recognize these names as special unless
explicitly configured by the administrator for names within the
"internal" namespace.</t>
            </li>
            <li>
              <t>DNS server operators <bcp14>SHOULD</bcp14>, if they are using names within the "internal"
  top-level domain, configure their authoritative DNS servers to act as
  authoritative for these names.</t>
            </li>
            <li>
              <t>DNS Registries/Registrars <bcp14>MUST NOT</bcp14> grant requests to register any of these
  names. These names are reserved for use in private networks, and fall outside
  the set of names available for allocation by registries/registrars. Attempting
  to allocate one of these names in the global DNS name will probably not work as
  desired, for reasons 4, 5 and 6 above.</t>
            </li>
          </ol>
        </section>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>While the "internal" namespace is designated for private use, it is important
to recognize its limitations and potential risks:</t>
      <ol spacing="normal" type="1"><li>
          <t><strong>Leakage into the broader Internet</strong>: Names within the "internal" namespace
may inadvertently appear in log files, email headers, or other contexts,
leading to potential exposure. Users should not rely on the confidentiality
of these names.</t>
        </li>
        <li>
          <t><strong>Lack of global uniqueness</strong>: Names in the "internal" namespace are not
globally unique. For example, multiple networks may use the same name, such
as "accounting.internal", for entirely different purposes. This is similar
to the use of the "local" namespace in multicast DNS, where many devices
might share the name "printer.local". Users should exercise caution when
performing operations that require authenticity, such as entering
credentials.</t>
        </li>
        <li>
          <t><strong>Collision risks</strong>: If two networks using the "internal" namespace are
interconnected, name collisions may occur. This is analogous to IP address
conflicts when private-use IPv4 ranges (e.g., <xref target="RFC1918"/>) are
interconnected. Organizations should carefully evaluate this risk before
adopting the "internal" namespace.</t>
        </li>
        <li>
          <t><strong>DNSSEC limitations</strong>: DNSSEC-validating resolvers that rely on the global
DNS trust anchor will fail to resolve names ending in "internal". This
limitation should be considered when planning network configurations.</t>
        </li>
        <li>
          <t><strong>Implications for HTTP cookies</strong>: Cookies set for a domain like
"accounting.internal" on one network may be sent to a different
"accounting.internal" if the user switches networks. To mitigate this,
organizations can use the Secure flag for cookies. Additionally, since the
"internal" namespace does not resolve in the global DNS, Certificate
Authorities are not expected to issue certificates for it. Organizations
requiring HTTPS for "internal" domains will need to establish their own
private Certificate Authority (CA), which is beyond the scope of this
document.</t>
        </li>
        <li>
          <t><strong>Impacts on traceability</strong>: Users should not assume the appearance of such
names is indicative of the true source of transmissions. When diagnosing
network issues, the appearance of such names must be interpreted with
the associated context to ascertain the private network with which the name
is being used. A name within the "internal" namespace can never be used by
itself to identify the origin of a communication.</t>
        </li>
      </ol>
    </section>
    <section anchor="additional-information">
      <name>Additional Information</name>
      <t>This reservation is the result of community deliberations on this
topic over many years, culminating in <xref target="SAC113"/>. The SAC113 advisory
recommended the establishment of a single top-level domain for
private-use applications.</t>
      <t>A selection process <xref target="IANA-Assessment"/> determined that "internal" was
the best-suited string given the requirement that a single string be
selected, and the ICANN Board reserved it for this purpose in July 2024
<xref target="ICANN-Board-Resolution"/>.</t>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors would like to thank the members of the Internet community
who participated in the discussions that led to the establishment of
the "internal" top-level domain, including those who contributed to the
SAC113 advisory and the IANA assessment process.</t>
      <t>The authors would especially like to thank Eliot Lear for extensive
discussion and feedback on this document. Additional feedback and
suggestions were received from Joe Abley, Mark Andrews, Brian Carpenter,
Stuart Cheshire, Wes Hardaker, Paul Hoffman, Philip Homburg, David
Lawrence, John Levine, Benno Overeinder, Petr Špaček, Ondřej Surý,
Peter Thomassen and Suzanne Woolf.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. 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="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC1918">
          <front>
            <title>Address Allocation for Private Internets</title>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <author fullname="B. Moskowitz" initials="B." surname="Moskowitz"/>
            <author fullname="D. Karrenberg" initials="D." surname="Karrenberg"/>
            <author fullname="G. J. de Groot" initials="G. J." surname="de Groot"/>
            <author fullname="E. Lear" initials="E." surname="Lear"/>
            <date month="February" year="1996"/>
            <abstract>
              <t>This document describes address allocation for private internets. 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="5"/>
          <seriesInfo name="RFC" value="1918"/>
          <seriesInfo name="DOI" value="10.17487/RFC1918"/>
        </reference>
        <reference anchor="RFC4193">
          <front>
            <title>Unique Local IPv6 Unicast Addresses</title>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <author fullname="B. Haberman" initials="B." surname="Haberman"/>
            <date month="October" year="2005"/>
            <abstract>
              <t>This document defines an IPv6 unicast address format that is globally unique and is intended for local communications, usually inside of a site. These addresses are not expected to be routable on the global Internet. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4193"/>
          <seriesInfo name="DOI" value="10.17487/RFC4193"/>
        </reference>
        <reference anchor="RFC6761">
          <front>
            <title>Special-Use Domain Names</title>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <author fullname="M. Krochmal" initials="M." surname="Krochmal"/>
            <date month="February" year="2013"/>
            <abstract>
              <t>This document describes what it means to say that a Domain Name (DNS name) is reserved for special use, when reserving such a name is appropriate, and the procedure for doing so. It establishes an IANA registry for such domain names, and seeds it with entries for some of the already established special domain names.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6761"/>
          <seriesInfo name="DOI" value="10.17487/RFC6761"/>
        </reference>
        <reference anchor="RFC6762">
          <front>
            <title>Multicast DNS</title>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <author fullname="M. Krochmal" initials="M." surname="Krochmal"/>
            <date month="February" year="2013"/>
            <abstract>
              <t>As networked devices become smaller, more portable, and more ubiquitous, the ability to operate with less configured infrastructure is increasingly important. In particular, the ability to look up DNS resource record data types (including, but not limited to, host names) in the absence of a conventional managed DNS server is useful.</t>
              <t>Multicast DNS (mDNS) provides the ability to perform DNS-like operations on the local link in the absence of any conventional Unicast DNS server. In addition, Multicast DNS designates a portion of the DNS namespace to be free for local use, without the need to pay any annual fee, and without the need to set up delegations or otherwise configure a conventional DNS server to answer for those names.</t>
              <t>The primary benefits of Multicast DNS names are that (i) they require little or no administration or configuration to set them up, (ii) they work when no infrastructure is present, and (iii) they work during infrastructure failures.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6762"/>
          <seriesInfo name="DOI" value="10.17487/RFC6762"/>
        </reference>
        <reference anchor="RFC7788">
          <front>
            <title>Home Networking Control Protocol</title>
            <author fullname="M. Stenberg" initials="M." surname="Stenberg"/>
            <author fullname="S. Barth" initials="S." surname="Barth"/>
            <author fullname="P. Pfister" initials="P." surname="Pfister"/>
            <date month="April" year="2016"/>
            <abstract>
              <t>This document describes the Home Networking Control Protocol (HNCP), an extensible configuration protocol, and a set of requirements for home network devices. HNCP is described as a profile of and extension to the Distributed Node Consensus Protocol (DNCP). HNCP enables discovery of network borders, automated configuration of addresses, name resolution, service discovery, and the use of any routing protocol that supports routing based on both the source and destination address.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7788"/>
          <seriesInfo name="DOI" value="10.17487/RFC7788"/>
        </reference>
        <reference anchor="RFC8375">
          <front>
            <title>Special-Use Domain 'home.arpa.'</title>
            <author fullname="P. Pfister" initials="P." surname="Pfister"/>
            <author fullname="T. Lemon" initials="T." surname="Lemon"/>
            <date month="May" year="2018"/>
            <abstract>
              <t>This document specifies the behavior that is expected from the Domain Name System with regard to DNS queries for names ending with '.home.arpa.' and designates this domain as a special-use domain name. 'home.arpa.' is designated for non-unique use in residential home networks. The Home Networking Control Protocol (HNCP) is updated to use the 'home.arpa.' domain instead of '.home'.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8375"/>
          <seriesInfo name="DOI" value="10.17487/RFC8375"/>
        </reference>
        <reference anchor="RFC9476">
          <front>
            <title>The .alt Special-Use Top-Level Domain</title>
            <author fullname="W. Kumari" initials="W." surname="Kumari"/>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="September" year="2023"/>
            <abstract>
              <t>This document reserves a Top-Level Domain (TLD) label "alt" to be used in non-DNS contexts. It also provides advice and guidance to developers creating alternative namespaces.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9476"/>
          <seriesInfo name="DOI" value="10.17487/RFC9476"/>
        </reference>
        <reference anchor="SAC113" target="https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-113-en.pdf">
          <front>
            <title>SSAC Advisory on Private-Use TLDs</title>
            <author>
              <organization/>
            </author>
            <date year="2020" month="September"/>
          </front>
        </reference>
        <reference anchor="IANA-Assessment" target="https://itp.cdn.icann.org/en/files/root-system/identification-tld-private-use-24-01-2024-en.pdf">
          <front>
            <title>Identification of a top-level domain for private use</title>
            <author>
              <organization/>
            </author>
            <date year="2024" month="January"/>
          </front>
        </reference>
        <reference anchor="ICANN-Board-Resolution" target="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-07-2024-en#section2.a">
          <front>
            <title>Reserving .INTERNAL for Private-Use Applications</title>
            <author>
              <organization/>
            </author>
            <date year="2024" month="July"/>
          </front>
        </reference>
      </references>
    </references>

<section numbered="false" anchor="notes-for-removal-before-publication">
      <name>Notes (for removal before publication)</name>
      <ul spacing="normal">
        <li>
          <t>I-D source is maintained at: <eref target="https://github.com/kjd/draft-davies-internal-tld">https://github.com/kjd/draft-davies-internal-tld</eref></t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAOle+2oAA5Vay3IbSXbd11ek2QtLCgAU2Ww9GO2eZpMai9MSJYtUKCYc
DkeiKgHksKoSrqwChFbwE+YDZjc/4o3t+S+fczPrAYCUZhYSgULlzfs895E5
Ho+T2ta5OVVn6sYtx7lZmVxduELbUs1cpd5XdqVroz56k+jptDKr0/bZGM/U
zZuLJHNpqQvQyCo9q8eZXlnjx7asTVXqfFzn2TjH+75OfK3L7D917kq8XVeN
wZPK6OJU2TIzS4P/yjqxy0p+9fXx06cvnx4nt+tTdSnkTD2+4CZJqmsumrlk
aU8TpbyrQGnmT9XGeH7fFP1X3dQLV/G1Mf4prMMPv07UhXAqj4IAv9pi+NBV
835jdea9nZcmU1dNMTWVV2dC1tYbebnVzuXZ1Zk8MFBifqpubTEJKvnZ6lJP
QHSbkbOJepueu1KnC2sGzJyVWWXWu79t83TuqqWrdG1dMFfPI0h4BW233G7z
eH52dTVkUstekyJN414/21SX5T6znybq16bQlR0w+klXlSmHz4XJf3Vunpvh
Lmt58edbeXEC/hNasCrA/8rQPB9+f3708uhF/Hhy9PL7+PHZ82dH/cfj+PH5
8xftuy++f/5D/Pjy5Pkzfrw+Oz86EgJKRSc/uMZDdZatLPxlo6C0HV/2B+F1
Xc0NHGxR10t/enho6+UkzcpJp5RDUx7ObG78oTdpQx8YQ4Vj+PfU5vIt7jFO
XVHYujZm7L1Ox5WBvWosw2dwNzblZJnNZNMMfJyq46fHT8dPX+IJHWkMgxrv
C4TFtiCXjBQ7A0NiezdTWtVdAGd9AC9jADfe/MOyVc7VY7/xtSkO7daGEtSR
9Bikx8cn46dHYzB/cq9I/JUi0e/GvzhdZeMPxru8IbFtyfDcVCtbztXk8urm
1YerszdDJBJLnS2XeeTkAYut1+ttiaayqU7harYmPtFehTE1dvKHcEFTWZ37
Q71cVm5lMliq5c+P/dKk+LV9f+xm43phxrLBOFA+fjl++rxVwHfwCq48nug9
PTxPkvF4jFAE9IGdJLlZWA+LpQ2trDLj08pOEbzYQR20KHpwv3WhesRl0hpZ
D/QyCfsUNssQhcl3BI3KZY0wxl1NhQX4523dhCUgpdYLmy46r0GMrl11q9zS
AGUcQK/Qm2Rt/QL8yO7g0lbKrcuWLWACjefThSn4s64V5Csd/kAWIHzGpVOT
YHUGpFA6TeHidpobtbJaxJ7nbqrzAUVwKW6oHl1cXT8eKd+ASe3BSb3AG2mE
QUN6C1d0jFMLN9/Q4yPE/WPyKFamh+f5hnYAkoJkJorGNj5ZNtjGm0lE1wbC
hF8IHaJLiimOs9KUB9QH4oB1NW1qBa+h/IDamZ03FXYgTos6ojw76vfUkasy
6hW6I8nWIP/sk8r8V2MrQ+/xEyXeBNKpWYrikXJyN3eN58pBxKrL90pnQH3v
VaXLOeR5ZCbzySj58iVi793dSMkXYvLdHdTO0LDChobbFDbXlZo1pbhUyzu5
g6SJSV2w2YTOhxy2IoDQyyjthZnZ0sr3YKFbs1GQNfPq4O3H65uDUfirrt7J
5w+v/u3j5YdXF/x8/frszZvuQxLfuH797uObi/5Tv/L83du3r64uwmI8VVuP
koO3Z3/EL+Tq4N37m8t3QJyDYLphYNK84rjix9WyMvQN+GAbsRnX/HL+/n/+
enQCvf0TFHd8dPTy7i5+eXH0/ARf1gtTht1cCT8LX6G0TYLoNVAoqMAD4SVL
WwOR8C5cc8EIY8hCm0/+nZr5j1P14zRdHp38FB9Q4K2Hrc62HorO9p/sLQ5K
vOfRPdt02tx6vqPpbX7P/rj1vdX74OGPv8ttadT46MXvfkroQh+9+P92NEsk
LnUKhLvaw6qFXhmFYnOOmMwt0aZUK5QejIamrMzcwj8Zf6XEM+I8GUYIvHiE
zArQEpuUWJM6CUOBhQLgb6oYcUtiuU2NBHduNEEO1Q2y/xLYKkWBjQVZU3ZA
iDj1iF6DaJXt+8IO+1eI5t87+gPL5tSMEpBGNtOl/S1k/cLOF3DMzCHUdYDJ
mSwI2on4HACYFbj8JDnAZGAuQkmPTiNiV5MzxakWd1OX59Z3cduUcPzMprXg
29RAxdZVcMpLem3hfB2dF2ULvVwx6OsNHbjJBeQIHc00Yq/ULT0DiWwZWK6p
HXCbt6BmSg+w9OHnYDHGZFiNSIJeocqEXOqVs1nIoEtXkwXQp2qIuQ2lCVSQ
zEDDgqlZ5Qp5nxy62ZYflK2PgZPXbo3cUY2oH89EEyWNCSnoH/hPD0k6+JbN
1haKKbmaIAJOShQJIRsOzNB6wKjl5FtlAGWYSuqvHLjGxhP1DoEjHJnPuljm
zDXU/tREJRQFlBVLxymYNHBxqbroh11OLWvQZ6MjYAU+qmRlKxQLuf0NfJsS
31wZ8k6SvKKh6ePpwjkfU1XmoKXW+CL1nN4LOIXlKZkt+oolPLNE1FRcjlpO
84YJ5zRJjugH+wbt3NPOVEHnhbx94myEk4H+4DKJNDN40Nsg5q1ZUzeE2OOw
FTzjlkwhnm/1nNYYUgoueE8YTZLvw/pcp7I+/hQctGTGvYfSJDmZcPX1q/Px
CipGzWgFuVhN0ArAsA2fuL2iQnplWAmar4KbzdBvUUzwFglEdoE7Mbr7/WOC
BlJBYGoSq65jdu/wFWn6mr6LLcUVSBce04KnvCK+6BvgL6ooK0EZcxooytvC
uceCtpZizPScjKQ+YlR3EEkjZ3Y2A06XAosh4pgGRccHuUs7HZKLULKwS0Sy
tb7ns62X6d/Ch3gLqNUCPYrVTe3gUB2kh68ENLcOod03BV3cZCaEDR5pJcyA
VPS/SKnnLXMm1MICzZsli00x4W+ujClAIJBbhqgYgRrjj1mAaQUL/T73PbPQ
dGnmrrZSP3ZTgOgFIEYIRMixVvxlEzAWREZDf7R+W//DtoIFSxUpkzU2EKFu
DmEkGsiFcFvdimy9wXRe75mLPfs95iJ35nPdbtr2oGGcwa2laO6gPHfuVuX2
1gw7Bx+cCkjU6T1UqL3OmPjVwLbRbKKGTkMtTg/0FHcJLZP1sTwkTyDXudlw
q8AL1YT4IvBs5ZlYwPgUJUyvL/YzE10t9Z7WOPT4ipNjGzwPSht6pR/gas/m
a2azWEPxh/OQfdF3Ry3Jlhy53N0JYnA+wbe4QxhB+W83WwvE+5Rh03PMzJuZ
3MxDPgpQnAx7po0wKMMDJcMD8HL/KCGw9p26jg07hwVxmhl6tg9S9FUbFCxk
X1QHUPYxEaMj2mY/mPwhcgdJFel1qHPErkmUqkFaYCs1gdCgmxAuvxvSUmHu
EXSwr1W2p2GmgJyOHcXZOI4QBoctIHPLgJmQiXTp14yaqQGUSeToTC/rVv3X
kfSzydHOcuDCgMnkYSa3psVnobGEgiaStz96KSMq1lnGDEYHbXU1bB6/4j6M
ekE/9oosKXS5ieloGPET1ddpyP+pbEX8IPaq1DCgGQ+6HeDSG5cUh0VtG0Kh
Qmk5HIWSfFDL6LW0hAAfkBrKwsdEIaAgJN1Yg/f7FBZKbMkX/cPBuALqGoy3
UD7Natmo775AItRR2yrUcYKh89BehgWsAnaVva3Dff0JE+KUg3x39v4ypJLc
TitUCqDzd7DEUXxgasCTrODgX7y36PWQb2C6ezfuhPFISwoRKwyEyUy/X4hX
Ww2zT8p5NvCMSCKQUz3yj4Oez/d+6mT6lop3pGGWnnJoNNMwLvRf16ZYSs6Q
pNQsFfYgUU44ItvFiOMqUf+aPQil2gzcUsbiW8yFNnRAvC3uBkxCg5ehViBT
+9K3Io62GJ6jLpUBmi0K9Hf89Aj1mRUWJD2WAtAr87gNlqh/tnvSa0SjYP82
exJQ2Ymh8kWdDUDQFZO0ZnqMVSxHzHHAF7nrmo2tx6D6sLVIjh4EyG0NH8fi
S/nzKLOe/Wo2EPkxuTOltLHNMhxDbRUBjH+RK4Z/P27dH88NaqK+wga1g8lW
46FuS45xQpmwgKCRJdr0AZuHdIhAiXsOassAFQ/6yj+AF7BPDusQKsxnQo+t
tyu4mIF1VtiS6Y7jla5YHYI3Sew2NqxXArMDsfohTeuNdhZAKZR1VOFXMgMR
dyc3jHqGIwg8HEd0zLQO8LT91g6i9HzHwgEOfhg/ahBq525qXmnBdqklfAjN
MF4KOSrmkkS1QXqzkzD2Krh7/Czg+owR55qayTdkHsglDXWktkLzp9tM1ncS
tGLVS1F1UsCLAqJA6aLYdhEiv9zNg/fMtCVOpe1EmTvFzhsptaWWFRVzlg43
GsUWSkuTeTJSP4g8z5SeupWRmvI6nqbtVUCfFjY3u+VBXw6ztNoe2A/OvUYc
JhGRCp69wU6JmKeNCQt7STmu+/F0P2TgDMCH6cOTJ2/iIKBr+qcV0Mz0c7sn
T05joXl/QdNxzEBhy2JLncEla0l+qp8A526u5BBuFA5P1cJwI9+njK45IszL
yDHOXHreEcyOM7O2AIu1SzikyDctBkvcxC4hnmZv2xymORbxH5pn9GJ/ReT2
gIT0d4Z2YdAZh1Wje8Y4VFXbunF8IFTD1I3kOETgEUlT0ocng3kCXYGSibx9
vRWnD77v9OJxRhya9JPAIM7ekIGDt2EDPoo5oGC0x5GA2FhGtH4RSsXAtzqA
c5LFSSC7Yx7z2VSplUFHSEQ8IiAtzlVcJadrAT7FXSU7xAZAwIziAsE3/VDS
cLMQ3CpFIAZT06zf06zn7QwtODuNeQm51253jPY1y+4P1UZ7A2Ra0aWI8F7t
W8dT/ZGUcNoOKkQBO2dXq5PtU6utg6r7+Zmod4PheafuFC/PGvqiWem8IWZI
qybDv6mBxoWWTNm/pgRo84TaDCO8IaJQoV8b7EUL9gEZooO7Pjzd+ztHe6Jo
AYiOn61xbEBZnjyKjnNdlpJ64yhiq5yiw/xAES+HQ1tG2Oubm/d4190isVDa
8/BR8pIkoba9YFskNcJ90UrxmXDazeNk2zNgmZT6+H2YRKgipFdTHhicLjhw
a7srdYOmGTXtvLWyYKfbcgse4LRQI+kIeTTX8ziPErkmbHDl8JIYNugxHyp/
+rlfa7K9LDpS50gD4YKF0GkrOxsLBK4GoHdnBtb7BhbsF8XDh3rHz0krwAMN
S0tdy4t7cyzfnlAE+oaXWXI56W+P+AWEYl4dcNtfhFKPzs8ej/qB2NRsXJkF
1OZQq5vw805EPwp5Fp1Kp6Ev5sUIE2/S0J32speG7EUwUUiZPB9rC/YkXkyK
A7xMPHXVYTmvnaGrbqqwAnuVvoAyxcHVJ4YB+p95KWcYQiu6oyjcjx7YNW5Z
MFZ3zohZCkhe4ULvXWqlSon5W1zb0446OsXu5QuZJgWdtilE0I36pU05cIRL
tnXYV+sOce/uEErGp1PJ+KiCTD4TxwpT1lDyw6zz9pxu69xIyrU+DFABxZtc
4XJJN5OMQz0f51ScfZBapFUzWeZ22mUzF47dUaEtbaoc+ZSUuoG6ofu0yQse
v0ag+/IlXPJqx1zhm2ovXyUs8tDPhksn+L3zaTnRF6FoZVaW99yu2ToE3Lla
cwZYyuPUDFUvm1sOJbevbN3dQTqYACy3Y+qBTdaojaWGBFdj38g4mLU5RJvD
X8vdyV4g0HEcX52aJHDChKtjsA1HpV1jYevuJktb/1CHf2iQeHg1Kfn6UFWd
pWxf0bLOZc4YZr2he/JxlCSzdymfdHkbTilMuCsZg6873+7sn6wXKFl1xZpl
qQdncejZ0yaEZZA8789Kd+34rUPS4cAb/HI+jl1lsm+nTX8Im+w4UK9QDot1
Z9jW5JP7lGBiVw21buvjVW6BXW9Y4UtZ+hl1uoelk17U0OABgadSau/cQRnm
nf4tLEl8M0ctFA9ojLSTqbHdeP0PDiCNjhC56q0GooSrpYinXyoLPDjX1VJq
xFFyXTewhTpH2lzA70bqE0DtNfxB33Ka+l43uXrtZjMEJb6hKbNLnhxMm2o+
kquzWfJGr2XoPcK2ixLyruD+2MqUpVPvENGGl31JzNSV+ttfl/r//mxuR+pd
mf3tL+ZP6rqp/ve/R8l7Rg6iGgaE3oNmrpvfeOlCfXIun8ULbtQB3fPKMQU+
Ci1m4VBpxeoNzj5tQ/dx8uW0lAuxJvuXA3TS3hzc8aTlcnzRJgXLQtWGw+9M
8Z7xj+2twjnAtZlO4LyHt3/KDh+87/xT8v9q4rKsWi0AAA==

-->

</rfc>
