<?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.30 (Ruby 3.4.8) -->
<?rfc strict="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-core-yang-sid-pen-06" category="std" consensus="true" submissionType="IETF" tocDepth="4" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.31.0 -->
  <front>
    <title abbrev="SID ranges for PEN holders">YANG-CBOR: Allocating SID ranges for PEN holders</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-core-yang-sid-pen-06"/>
    <author initials="C." surname="Bormann" fullname="Carsten Bormann">
      <organization>Universität Bremen TZI</organization>
      <address>
        <postal>
          <street>Postfach 330440</street>
          <city>D-28359 Bremen</city>
          <country>Germany</country>
        </postal>
        <phone>+49-421-218-63921</phone>
        <email>cabo@tzi.org</email>
      </address>
    </author>
    <date year="2025" month="December" day="30"/>
    <area>Applications and Real-Time Area (art)</area>
    <workgroup>CoRE Working Group</workgroup>
    <keyword>YANG-CBOR</keyword>
    <abstract>
      <?line 59?>

<t>YANG-CBOR (RFC 9254, "Encoding of Data Modeled with YANG in the
Concise Binary Object Representation (CBOR)") defines
    YANG Schema Item iDentifiers (YANG SID), globally unique 63-bit
    unsigned integers used to identify YANG items. RFC 9595
("YANG Schema Item iDentifier (YANG SID)") defines ways to allocate these SIDs on
    the basis of IANA registries.</t>
      <t>The present specification employs these SID allocation
    mechanisms to allocate ranges with 100 000 SIDs
    (representation size 64 bits) each
    for each of the holders of IANA-registered
    Private Enterprise Numbers (PENs) &lt; 1 000 000, as well as ranges with
    10 000 SIDs (representation size 32 bits) each
    for each of the holders of PENs &lt; 100 000.</t>
      <t><cref anchor="status"><br/>
The present revision –06 is a resubmission of -05 with
"Intended Status: Standards Track", after IESG discussion pointed
into this direction.</cref></t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-core-yang-sid-pen/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        CoRE Working Group mailing list (<eref target="mailto:core@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/core/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/core/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/core-wg/sid-pen"/>.</t>
    </note>
  </front>
  <middle>
    <?line 89?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>YANG-CBOR <xref target="RFC9254"/> defines
    YANG Schema Item iDentifiers (YANG SID), globally unique 63-bit
    unsigned integers used to identify YANG items. <xref target="RFC9595"/> defines ways to allocate these SIDs on
    the basis of IANA registries.</t>
      <t>The present specification employs these SID allocation
    mechanisms to allocate ranges with 100 000 SIDs
    (representation size 64 bits) each
    for each of the holders of IANA-registered
    Private Enterprise Numbers (PENs) &lt; 1 000 000, as well as ranges with
    10 000 SIDs (representation size 32 bits) each
    for each of the holders of PENs &lt; 100 000.</t>
      <t>IANA [is requested to allocate/has allocated] a mega-range with
100 billion SIDs (representation size 64 bits), for the SID numbers 300 000 000 000 to 399 999 999 999.</t>
      <t>IANA also [is requested to allocate/has allocated] a mega-range with
1 billion SIDs (representation size 32 bits), for the SID numbers 3 000 000 000 to 3 999 999 999.</t>
      <t>Private Enterprise Numbers (PENs) are registered in
<xref target="IANA.enterprise-numbers"/> in a low-threshold, low-overhead
registration process.
At the time of writing (~ 37 years after
creating this registry), around 65 000 PENs are registered.
In this document, the registrant for a PEN is referred to as the "PEN holder".</t>
      <t>The present specification makes the following SID ranges available to
certain (current or future) PEN holders for allocation in a scheme defined
by the holder:</t>
      <ul spacing="normal">
        <li>
          <t>The holder of a PEN ppp ppp (&lt; 1 000 000) can use the SID numbers
3pp ppp p00 000 to 3pp ppp p99 999.</t>
        </li>
        <li>
          <t>The holder of a PEN pp ppp (&lt; 100 000) can also use the smaller SID numbers
3 ppp pp0 000 to 3 ppp pp9 999.</t>
        </li>
      </ul>
    </section>
    <section anchor="example">
      <name>Example</name>
      <t><xref target="RFC5612"/> has allocated Enterprise Number 32473 "for use in examples
in RFCs, books, documentation, and the like".</t>
      <t>If this Enterprise Number had an actual PEN holder, the present
specification would confer control to it over the SID ranges:</t>
      <ul spacing="normal">
        <li>
          <t>3<strong>03 247 3</strong>00 000 up to 3<strong>03 247 3</strong>99 999, and</t>
        </li>
        <li>
          <t>3 <strong>324 73</strong>0 000 up to 3 <strong>324 73</strong>9 999.</t>
        </li>
      </ul>
      <t>(The plaintext form of this document shows "*" characters around the
digits conveying the PEN, which are shown in <strong>boldface</strong> in the
typographic forms.)</t>
      <t>As Enterprise Number 32473 is intended to be used in documentation,
the SIDs in the two SID ranges listed here for the documentation PEN
are consequently also available for use in documentation.</t>
    </section>
    <section anchor="discussion">
      <name>Discussion</name>
      <t>This allocation provides an extremely-low-threshold (zero-interaction)
way for PEN holders to get number space for the YANG SIDs used in
their YANG modules.
If a PEN is not already available to the entity needing such number
space, it can be obtained in a very low-threshold process.
Employing this number space is, however, not always the approach to
recommend to a module author:</t>
      <ul spacing="normal">
        <li>
          <t>In the larger of the two spaces, each SID number needs a
representation size of 64 bits ("64-bit SIDs").
(This larger representation size of the absolute value of the SID is
of comparatively little consequence due to the delta-encoding used for
SIDs in YANG-CBOR.)</t>
        </li>
        <li>
          <t>For the holders of PENs &lt; 100 000, there additionally is a smaller space
where each SID number needs a representation size of 32 bits
("32-bit SIDs").
PEN numbers that have access to this space (PEN &lt; 100 000) are likely to run out
before or around 2040; the
expectation is that by that time there will be enough opportunities
to request SID ranges within mega-ranges allocated by other registrants that
this mechanism is less needed.</t>
        </li>
        <li>
          <t>This space has no infrastructure to discover the YANG module behind
a SID.  Of course, each PEN holder can provide such infrastructure,
but even then the problem remains of how to find that infrastructure
for a SID.  (Search engines may mitigate this somewhat.)
On the other hand, in some cases this relative obscurity may be exactly what a PEN
holder wants to achieve by using this mechanism.  </t>
          <t>
If obscurity is not the intention, one or both of the following
approaches are encouraged:  </t>
          <ul spacing="normal">
            <li>
              <t>The PEN holder can provide a public repository where their YANG
models can be found alongside the applicable SID files.
Such a repository may be easy to set up using a popular git forge
such as, at the time of writing, GitHub.</t>
            </li>
            <li>
              <t>Implementations that employ PEN-based SIDs can facilitate
information discovery by providing <xref target="I-D.ietf-core-yang-library"/> or
another form of YANG library <xref target="RFC8525"/>.</t>
            </li>
          </ul>
        </li>
      </ul>
      <t>Relying on the PEN registry might theoretically trigger a land-grab by
prospective writers of YANG modules.
However, PENs have been around for decades (see <xref section="3.1.4" sectionFormat="of" target="RFC1065"/>, which continues to be in force with no technical changes as
Section <xref target="RFC1155" section="3.1.4" sectionFormat="bare"/> of RFC 1155 <xref target="STD16"/>), and such a land-grab has not
occurred for the other allocations implicitly provided by obtaining a
PEN.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t><cref anchor="replace-xxxx">RFC Ed.: throughout this section, please replace
RFC-XXXX with the RFC number of this specification and remove this
note.</cref></t>
      <t>As per <xref section="6.3" sectionFormat="of" target="RFC9595"/>,
in the <xref section="&quot;YANG-SID Mega-Ranges&quot;" relative="#sid-mega-range" sectionFormat="bare" target="IANA.yang-sid"/>
registry within the "YANG SIDs" registry group <xref target="IANA.yang-sid"/>,
this document allocates two mega-ranges, one with 1 billion
SIDs ranging from 3 000 000 000 up to 3 999 999 999 (32-bit
representation size), and
one with 100 billion
SIDs ranging from 300 000 000 000 up to 399 999 999 999 (64-bit
representation size),
as summarized in <xref target="tab-allocations"/>.</t>
      <table anchor="tab-allocations">
        <name>YANG-SID Mega-Range Allocations for use by PEN holders</name>
        <thead>
          <tr>
            <th align="left">Entry Point</th>
            <th align="left">Size</th>
            <th align="left">Allocation</th>
            <th align="left">Org Name</th>
            <th align="left">URL</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">3 000 000 000</td>
            <td align="left">1 000 000 000</td>
            <td align="left">Private</td>
            <td align="left">IANA</td>
            <td align="left">https://rfc-editor.org/info/rfcxxxx</td>
          </tr>
          <tr>
            <td align="left">300 000 000 000</td>
            <td align="left">100 000 000 000</td>
            <td align="left">Private</td>
            <td align="left">IANA</td>
            <td align="left">https://rfc-editor.org/info/rfcxxxx</td>
          </tr>
        </tbody>
      </table>
      <t>IANA is requested to mark the following ranges as reserved for documentation:</t>
      <ul spacing="normal">
        <li>
          <t>303 247 300 000 up to 303 247 399 999</t>
        </li>
        <li>
          <t>3 324 730 000 up to 3 324 739 999</t>
        </li>
      </ul>
      <t>An additional contact for the allocation is: IETF CORE Working Group
(core@ietf.org) or IETF Applications and Real-Time Area
(art@ietf.org).</t>
      <t>The allocation policy inside the mega-range is "private" (see <xref section="6.3.2" sectionFormat="of" target="RFC9595"/>).
The URL is that of the present specification.</t>
      <t>The management of the SID block of 100 000 SIDs each, ranging from
3pp ppp p00 000 to 3pp ppp p99 999, is delegated to the PEN holder
for PEN ppp ppp (i.e., the PEN holder for ppp ppp controls SID
3pp ppp p00 000 to 3pp ppp p99 999).</t>
      <t>Similarly, the management of the SID block of 10 000 SIDs each,
ranging from 3 ppp pp0 000 to 3 ppp pp9 999, is delegated to the PEN holder
for PEN pp ppp (i.e., the PEN holder for pp ppp controls SID
3 ppp pp0 000 to 3 ppp pp9 999).</t>
      <t><xref section="6.3.2" sectionFormat="of" target="RFC9595"/> requires an organization that requests an
entry in the "YANG-SID Mega-Ranges" registry to ensure the technical
capacity to manage the SID ranges within those mega-ranges for a
period of at least 10 years (Private ranges).
The individual SID ranges within the mega-ranges allocated in this
document are assigned through the registration of PEN numbers.
The technical capacity to ensure the sustained operation of the PEN
number registry is derived from the demonstrated capacity of IANA to
maintain this registry as well as the importance of a functioning PEN
number registry in other contexts.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Section <xref target="RFC9595" section="5" sectionFormat="bare">Security Considerations</xref> of <xref target="RFC9595"/> applies, as well as
Section <xref target="RFC9254" section="8" sectionFormat="bare">Security Considerations</xref> of <xref target="RFC9254"/>.
In particular, the fact that a certain Private Enterprise Number
appears in a SID is not an indicator of provenance, i.e., it does not
guarantee that the SID or underlying YANG model actually does
originate from the holder of that PEN.
The requirement to ascertain the authoritative source of this
information, as discussed in the above security considerations, remains.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC9254">
          <front>
            <title>Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)</title>
            <author fullname="M. Veillette" initials="M." role="editor" surname="Veillette"/>
            <author fullname="I. Petrov" initials="I." role="editor" surname="Petrov"/>
            <author fullname="A. Pelov" initials="A." surname="Pelov"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <date month="July" year="2022"/>
            <abstract>
              <t>YANG (RFC 7950) is a data modeling language used to model configuration data, state data, parameters and results of Remote Procedure Call (RPC) operations or actions, and notifications.</t>
              <t>This document defines encoding rules for YANG in the Concise Binary Object Representation (CBOR) (RFC 8949).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9254"/>
          <seriesInfo name="DOI" value="10.17487/RFC9254"/>
        </reference>
        <reference anchor="RFC9595">
          <front>
            <title>YANG Schema Item iDentifier (YANG SID)</title>
            <author fullname="M. Veillette" initials="M." role="editor" surname="Veillette"/>
            <author fullname="A. Pelov" initials="A." role="editor" surname="Pelov"/>
            <author fullname="I. Petrov" initials="I." role="editor" surname="Petrov"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <date month="July" year="2024"/>
            <abstract>
              <t>YANG Schema Item iDentifiers (YANG SIDs) are globally unique 63-bit unsigned integers used to identify YANG items. SIDs provide a more compact method for identifying those YANG items that can be used efficiently, notably in constrained environments (RFC 7228). This document defines the semantics, registration processes, and assignment processes for YANG SIDs for IETF-managed YANG modules. To enable the implementation of these processes, this document also defines a file format used to persist and publish assigned YANG SIDs.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9595"/>
          <seriesInfo name="DOI" value="10.17487/RFC9595"/>
        </reference>
        <reference anchor="IANA.enterprise-numbers" target="http://www.iana.org/assignments/enterprise-numbers">
          <front>
            <title>Enterprise Numbers</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="IANA.yang-sid" target="https://www.iana.org/assignments/yang-sid">
          <front>
            <title>YANG SIDs</title>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC1065">
          <front>
            <title>Structure and identification of management information for TCP/IP-based internets</title>
            <author fullname="K. McCloghrie" initials="K." surname="McCloghrie"/>
            <author fullname="M.T. Rose" initials="M.T." surname="Rose"/>
            <date month="August" year="1988"/>
            <abstract>
              <t>This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1065"/>
          <seriesInfo name="DOI" value="10.17487/RFC1065"/>
        </reference>
        <referencegroup anchor="STD16" target="https://www.rfc-editor.org/info/std16">
          <reference anchor="RFC1155" target="https://www.rfc-editor.org/info/rfc1155">
            <front>
              <title>Structure and identification of management information for TCP/IP-based internets</title>
              <author fullname="M.T. Rose" initials="M.T." surname="Rose"/>
              <author fullname="K. McCloghrie" initials="K." surname="McCloghrie"/>
              <date month="May" year="1990"/>
              <abstract>
                <t>This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="16"/>
            <seriesInfo name="RFC" value="1155"/>
            <seriesInfo name="DOI" value="10.17487/RFC1155"/>
          </reference>
          <reference anchor="RFC1212" target="https://www.rfc-editor.org/info/rfc1212">
            <front>
              <title>Concise MIB definitions</title>
              <author fullname="M.T. Rose" initials="M.T." surname="Rose"/>
              <author fullname="K. McCloghrie" initials="K." surname="McCloghrie"/>
              <date month="March" year="1991"/>
              <abstract>
                <t>This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="16"/>
            <seriesInfo name="RFC" value="1212"/>
            <seriesInfo name="DOI" value="10.17487/RFC1212"/>
          </reference>
        </referencegroup>
        <reference anchor="RFC5612">
          <front>
            <title>Enterprise Number for Documentation Use</title>
            <author fullname="P. Eronen" initials="P." surname="Eronen"/>
            <author fullname="D. Harrington" initials="D." surname="Harrington"/>
            <date month="August" year="2009"/>
            <abstract>
              <t>This document describes an Enterprise Number (also known as SMI Network Management Private Enterprise Code) for use in documentation. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5612"/>
          <seriesInfo name="DOI" value="10.17487/RFC5612"/>
        </reference>
        <reference anchor="I-D.ietf-core-yang-library">
          <front>
            <title>Constrained YANG Module Library</title>
            <author fullname="Michel Veillette" initials="M." surname="Veillette">
              <organization>Trilliant Networks Inc.</organization>
            </author>
            <author fullname="Ivaylo Petrov" initials="I." surname="Petrov">
              <organization>Acklio</organization>
            </author>
            <date day="11" month="January" year="2021"/>
            <abstract>
              <t>   This document describes a constrained version of the YANG library
   that provides information about the YANG modules, datastores, and
   datastore schemas used by a constrained network management server
   (e.g., a CORECONF server).

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-core-yang-library-03"/>
        </reference>
        <reference anchor="RFC8525">
          <front>
            <title>YANG Library</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="R. Wilton" initials="R." surname="Wilton"/>
            <date month="March" year="2019"/>
            <abstract>
              <t>This document describes a YANG library that provides information about the YANG modules, datastores, and datastore schemas used by a network management server. Simple caching mechanisms are provided to allow clients to minimize retrieval of this information. This version of the YANG library supports the Network Management Datastore Architecture (NMDA) by listing all datastores supported by a network management server and the schema that is used by each of these datastores.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8525"/>
          <seriesInfo name="DOI" value="10.17487/RFC8525"/>
        </reference>
      </references>
    </references>
    <?line 256?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>This document was inspired by the discussion of the authors of
<xref target="RFC9254"/> and <xref target="RFC9595"/> on how to handle <contact fullname="Rob Wilton's"/> feedback.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA6Va23IcOXJ9x1fArQc16a7mnSO2ZzdGI2m0jNiVJkRurO0d
OQJVhe6GWV1oF1Bs9VDc2H/wD/jB7/4H+0/2S3wygbo1SWkmlg+k6oLMROJk
5sksJUkibmfyRIjcZqVa6ZnMKzX3idF+nmS20slWlYvEmTxZ6zIplNfOC298
gVd/K6T8l5fv3iavvn//YSZfFoXNlDflQl5dvpYVFmon57aSP755J5e2yHXl
hErTSkPnl16ptIK49bowJM+WTqoylx+0KpJrs9LyJV6QY1X5PbFZzOQr++GN
/JOtbkj128rWa3GzmXWmCUiZSedz4TxWrmby8s31D+KZzCBal652M+mrWou1
mWFLeMlkWPB8q91zXHubDS5yvfZL3Dmla7ddVXruuhecrfzwTmZXa9UX6Oq0
u1fa50LVfmmrmUikKbHw1VR+b6uVKku8HE7llaqc12Xvvq2w8z+W5hYeM/7/
/tvL7yu9wivX/3oZNqE15P9onZ+rbClPTg5PTw/JHOO3M/k6OX5xcnYRF7GV
dekrPHmrScUWt9ZLW0L36B9PL5LT46Pk+OhFcn5ycXw0wkO9UqaYyUyl9jv/
s5nCHiFudVlr8uGCTiGcDK7iq4DTdwQsfhfvGL+s03A/2SwOIsiEKGmTHjsj
SR9+eHVxfHY6kwzELLVVvHl2cRbXYiEOU16+fPdyqkuvq3VlnE7KepXCOTNp
VKlY8jNgaK4rXWYanp4HNbaUymEf2VLnEhd+qWU4kOdOFmrt7XpCbxQW6MLf
jYac3JbPvVxoL5fer93s4CDsZoqDPeDg8dYW7iA16adVkThd3ZpMHxjnau0O
Tl9cyLn5pHPa4FNm45GUSc96uvaqWtCxklYo3Ww2U3pOHj1QzplFidP07uCh
vLA8BO6b9ql813vawJAVB4CRcXydI/Jncq4Kpxubm8wwk8/k9dI4OE/LDcLQ
/YMQrXvbUzw6PD+jf15dvz46pzW4J4+Ozs4m8kpnfA4n06PpaXj77PzoeCYp
5yAzkcbk9XQnKRUmrRQh9sGtIOLF2fFZhE1zXyRJIlWK4EDwCdFmCDkmYwhn
Ezl6U2Y2p1Ri5/K18kr+wea6ADg2OGLOKgAPwUS8smVGTvzelJAu36f/jo0A
Y+tKI6/4AK4xKdgb7ck//xs0H6nkI++c8CvGIxZ3BeytlLz0eiXNa6w0c6Mr
OQ4PL193q9PkoxCtIGRrPTelDsdHP18Q53ryJnJR2FQVxVbWpfmPWsvzkyQ1
vpVTl4Ql7NkAKgtaXDtceStNzgK30RHQ4aaNSWnPJLlRW0cLVCgLmjwGX0E9
IaXVROGWKkfwmTOuZKUXhnKwbgUft7s+Jg3XWBJdLN1aZ9heqBNISuvCktpG
VaPd9DSudLZUpXGroXmxGPEhHx0e/u2v/3N4eMjmtivH1fBonfkZnjuV8Jzb
kxoppH2VahrdoF3RFmNtazaZhE0iF+Xtkh8rc0uGPIxOOUZ5hIZv5VEwK/ye
hHRUFPS3Z34r8ai/i8etPzn+ldaTJWRIYwSfkYPI2n3s/XP2008srX9WqPvG
kea//fU/D88ljlzhHqrhCnmR7kN8cnjW7WF0CVeUOYB3xVJn9LfMVZU7eY0Q
vhnBBXN4CwX96q3MjcvqIGltCbjBt/iXxS6gLjdVyDTTkAlWJs8LLZDPoaiy
ec0P+3nh7i5p6879fS+E8aCpPe39tA9TIRjMP/0ZeiuNEMNp533AHSxxas1F
/hG+WOmFSvgcgwvg4//9r9QUBe3o6SNsADjhY6PjIuDHtC9PmoPq/yY7Ti4u
cHEx/D2NZiPP27/P9l9ieQO+Jyx/wu5Hrf568IBVyi7qgApxd/dE7cWJIsMr
lPxN4pcwm/A/4UsLvrXUKhcxS4XdrCubaYd89dLzNjyxVKB5Uxnmw+O/yJNv
5FaDxQXAigxElB8xMKOwLTyhwJxAds/P4o453oa2T8VlGQFts5oK/oS1NiYh
1Mifikk1SwfpqeIJcnKUo45vj+C9pzPqSt3osGRucd6bHXavbkHtVFpgy1Zk
uvIKjhtnNdRBFIyY176u9F6f3wfj2rwcXO2oZulYPHKRbnt5ZybEPieScEmO
DXtbr9fwEn7L8U5q3AOhK6lm7aJKnDRr6PcAV/0HHbKe0txTPFTKodNodits
FAsHFnRq1ju4bm53uH4m33xSqGrIUkg5kQ8Bn4MAfIh6hNbpNydyRK4mW+Bj
HeQ4UDMiIG4iU2tv8KcBEZ/GhFstMr0wN5qwcTkPWHuoY6lySRvOfK2K3gkH
NEY8iSGeNrYucmq8AEn6g7RbMK0AWhBa7XEFfPHJn+zvH5JzsCP8pqvGa/Wa
Hbf7vDk83gsJwOX+PjyCv9/Q28PlO0873485LApFpeQTx9QqFMRe5Enkho2T
o/2RBKsgWkkIj0FMHDE36AwcbfVWb0PAa/LVRG6WBhWWQptkcBzs76fwIPo1
vb/fkEy/XdtFpdZ4m01w0z0hXj52HuHMYZxpyia2l+pA3SBteNAiutpFRdJv
bD+0C8NZf4mM06bngQTaBfXqoY1GlSg9+CTDv0sLPQAOFjO0X7cFm1KQcf2s
gJR6C65JrT+g66lNLbbJICPL8c+6sgntlhyPVXsCrHN3nkBeoE4txB/yG9zb
7qihxK7xErnFVOH+CpSgIBp6Oe+yaWk97ET6zreD9MfiiBv7rSy15g7C1Tjh
oFew3gkBnbIEjsWmlC3D0SgJ8G+HBaerKm+Y1rbVYrARgwgGfPQtxV2wLTBv
amPXEEE0DskZzMeu4P5QBeLW2pYPUXIZUFBQh1k1xI8wwXqghQlhl8h4kzge
cKzHajsERGIix6PzU+ou2M+jvSlWjPm4o64nlvMOUmeLGnX9VhV1e5eMMETL
cc2TlIobTaCvMB4dbodIOCiv29NBG+dVopv+jk98zgOFJg5a5ocg25c/RJB8
gf5yrkMMqDw3ZD33VMxsm9TP7oOKDb/3hBOf8kFkSOSx0cnxjhMJkA1Z8kvl
kZBvYUlGoJEN5w0oIQ4kB6WKApdSPMzFq1UN9l1T/5dqeERT6Y5J7Pjw9PCf
OBNJBCKSeTTRRKVcqvGXOU9wxgbMjxCuS1sv0ESs17byaDS94VaV9AVW2c83
RBtxAh2R7Bc4KLEku8dxgnoSR9tsmzqyqyAHkGeJK+2H4UTwA5XN0tLwp1IQ
A8IPdkIGUe/QFqBe8GMbsIoaCUXGTqV8T5irK6djRHSZhgM75q0Q+kM9E3Jv
7SVilWOtjHXSIoGssLMV0gGDDPFMNoEK5cG3QzlCRn4XDBpfgVdCmS4X3Hiv
kAJX8PUiNN20d7vSG8gBqGF/UBvcCZ+B2MLt9Arsd0z2mDMWHFPIUsjRFSU1
kkuH+gm5FqghgSErQmh0wCacCxJMtjTYJp1b7drE1R4Ssr+USKqd8JhYyTKu
XoGL0EQJO01hbBP7LQ2lI4n5TQeGTIFdV2pBczXq/AJ1e+J8lFzXaYGaisiz
znhbbWOIdgUg9MMrGv+4JmvPOSgUTQMdyYl5lkbVVAcI0HPDRYMXXxEMVF9J
40blOPIcKhOISPASjLLrGmmRhqN0yAsdxDCaFJKwerTBmMi3xv+uTqdx35fE
9NpaGwM1DEfIH0mqKPVx0qNtgXAYZE7gJWjrz0abwNjSWQbnkaVN/9sfr4GW
cjKlUWIZ8NVwJo6o+FrbVLfLYPYHJCKeuZUNQWqbIoB5seRtQ6GHnynF+sos
qHagSQOEExCkFAYKGEh8k5FLvolZe1jNf9eUS07mnDRTjWiMCY9iK9eZIvIx
dlrD3sGAEgJFnGfe3zc0jqisKWvtIudCSEFOFrphSjke2C/JeOKJIbs58VAy
T0qPzs6+4zHp/f1eIOTh/Ht7DYnMC5txs5W3hCb4vSNSKGsrQqehmI3gD/mU
6QejTsARTMi493+FRXgptLaOJhpAb4HsmXzCz8cZjy/f5NMZ9FWU4FE4Yp4J
m5mANAPe1JDyOoYEFiX/jJ/gELKUxMQq2LDqYa9AG0dWBPr4KYvBnvX0gU1M
iNcQ1Dn0fHrC86RuSjMRkeje3dGnht7EIoxhE4rdP9DdD3xAo71vB3Pu+3vR
QjIWK26lWwo56iDL3z9kHDB0Aoh095uHpsA5Jlq90hdSX5hFomLHUYrgiKU3
6NjmlV09OiTp+pqdOYkcBw4hHmEbAWiiU8vivqD40blSVP3YaEmOAwt8XLkA
nl29WqkKl0yJ7+68SpMekDlPfKa+Bw7+kQZ8zbjys7wivjT8+dx+kISSz/J9
tfg2rX77TiFxfpZ//PB7+bWfz1D2mHtJ9NET95sxFF9wNIV/Nl+JqnmWoDVA
IeBPNpRo6R6BOOh71KufO+K2c//v03c3k892nBw+Ef3msYDo+dO1fV267bda
o/s4P9wdHOJcb3amSA3Hozfp+1jMYYMuMfT//e5+F2n9Zw3SaI1sGvqHQdE8
ad4WL8sefedMDobTJtT+pMqFT8fy1fsHX5zHg8+be0Rb+NWvfMYW9Bm7WxZn
cf0+2GL5lj4MN2yjl7jg5tE6QGC0W6uQAKfHOykQ8kk8ob+h75FWPTr9i9as
VAlSxQmr14ClMPGGbgw/ljApngxyxa+cuU3INvritlARPX5A40TT3/fGf2aq
p5Od9/gEu3fisMmRlb/SIjqWK7NCq18V26Dmqz554BLxIG//siHgr3DHL/DG
o874xbaQI76MMA57U4W5DRANuv9zADKjLSYFeio0J/J+FX1QgbuCCnvof2oE
et6RKZEp9HXUQHCSoTPZGSF2pdo6PeguuYcSYA3G5jzZ9ZJoi8fhxVH9uEmv
YUWMHnRlBiyKZp6PqdFPtLAmzOxFV/xpbODid9ZIpQZzfB+/ifX6/GBBj0v2
tt/zj6tdnC3Zte4ERUSIyLpa5zLAsFVKwQTOMCtZIWORFbjbqmm+0XorqFvl
cf/gC0b/kyQ3cyvq/RUNYnh4Pq9LBg8FwqOmlJHBEkL1J++YlwJxoU3c5aYd
GM+oD370rb1Iq+mLOwDKzRoxrM7SnpgXXxdzfHZKVOQSuRm522TUr4Vom1Pd
8KEvbj6GPPlhSsAQRhmP/8JIKwzwSoYYUGOZGRNp1yW5EKmAIxu9YW51aAAW
taJpiNZxChPBT+W5hO2hq2r6H13EaT16AZIgLNooU5J97cF3nzpYILcG14xK
DmyGLn9IanbY/YcZaiGp83JowzPdsHrRayfZ6/E7bRMTNOUjju8av2cDv0+a
yUj8aJuq7IYw8TK7Ke2m0PmC/8sLkZkAJp3/ZsT/UYXYyPWAb28UudutTRV6
IAZ699W4GTryZqhxFDvff6l+D7/8YlWc1tAopaACfPfBpvJPpvC2fA7Sei/n
Wudk9VT8Pz7vSzNwJwAA

-->

</rfc>
