<?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.3.8) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-lake-private-use-ranges-00" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="Additional Private Use Ranges for LAKE">Additional Private Use Ranges in the IANA Registries of the Lightweight Authenticated Key Exchange (LAKE) Protocol</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-lake-private-use-ranges-00"/>
    <author initials="M." surname="Tiloca" fullname="Marco Tiloca">
      <organization>RISE AB</organization>
      <address>
        <postal>
          <street>Isafjordsgatan 22</street>
          <city>Kista</city>
          <code>164 40</code>
          <country>Sweden</country>
        </postal>
        <email>marco.tiloca@ri.se</email>
      </address>
    </author>
    <author initials="T." surname="Müller" fullname="Tobias Müller">
      <organization>Robert Bosch GmbH</organization>
      <address>
        <postal>
          <street>Markwiesenstraße 58</street>
          <city>Reutlingen</city>
          <code>72770</code>
          <country>Germany</country>
        </postal>
        <email>Tobias.Mueller9@de.bosch.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>Security</area>
    <workgroup>LAKE Working Group</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 72?>

<t>This document adds Private Use ranges to IANA registries that pertain to the Lightweight Authenticated Key Exchange (LAKE) protocol.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
    Lightweight Authenticated Key Exchange Working Group mailing list (lake@ietf.org),
    which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/lake/"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/lake-wg/private-use-ranges"/>.</t>
    </note>
  </front>
  <middle>
    <?line 76?>

<section anchor="intro">
      <name>Introduction</name>
      <t>The Lightweight Authenticated Key Exchange (LAKE) protocol <xref target="RFC9528"/> provides points of extensibility, for which related IANA registries exist.</t>
      <t>When they were created, some of those registries did not include ranges with registration procedure "Private Use" (see <xref section="4.1" sectionFormat="of" target="RFC8126"/>). Later on, it was brought to attention that having such ranges available would be convenient for private deployments.</t>
      <t>Private Use ranges enable controlled proprietary ecosystems to use LAKE extensibility points consistently without making their application-specific protocol semantics public. They also support the development and testing of additional LAKE-based procedures before a decision is made to specify them publicly. Furthermore, Private Use ranges separate locally chosen values from IANA-assigned values, preserving the other ranges for publicly specified uses. Deployments using Private Use values are responsible for preventing collisions within their intended scope; independent deployments might use the same value differently.</t>
      <t>This document rectifies the original situation: As specified in <xref target="iana"/>, it adds Private Use ranges to three IANA registries of the LAKE protocol that originally did not include such ranges.</t>
      <section anchor="terminology">
        <name>Terminology</name>
        <t>This document uses the acronym LAKE, expanded to Lightweight Authenticated Key Exchange, to denote the protocol specified as EDHOC in <xref target="RFC9528"/>. Identifiers defined literally in <xref target="RFC9528"/> or in IANA registries (e.g., the names of the EDHOC registries themselves) are unchanged.</t>
      </section>
    </section>
    <section anchor="use-of-values-from-private-use-ranges">
      <name>Use of Values from Private Use Ranges</name>
      <section anchor="range-boundaries-and-encoding">
        <name>Range Boundaries and Encoding</name>
        <t>The Private Use ranges defined in <xref target="iana"/> extend beyond the values that are admitted by the existing ranges with other registration policies in the same IANA registries.</t>
        <t>The values admitted by the new Private Use ranges are bounded by the values that can be encoded as CBOR integers with a four-byte argument (see <xref section="3.1" sectionFormat="of" target="RFC8949"/>). For an unsigned integer N, a four-byte argument makes it possible to represent values of N up to 4294967295. For a negative integer N, a four-byte argument encodes the absolute value of N minus 1 and thus makes it possible to represent values of N down to -4294967296.</t>
        <t>Together with the initial byte of the CBOR integer, these encodings result in a total of five bytes. These bounds preserve the existing ranges for registry values that result in shorter encodings, while limiting the newly defined Private Use ranges to values with five-byte encodings. In contrast, the "EDHOC Authentication Credential Types" registry <xref target="Auth.Cred.Types"/> defined in <xref target="RFC9668"/> includes open-ended Private Use ranges. With respect to the Private Use ranges defined in this document, no values are designated whose CBOR encoding requires an eight-byte argument.</t>
        <t>When using values from these Private Use ranges, implementations need to account for the additional message size compared with the case where values with shorter encodings are used. Method types and error codes in the new ranges are each encoded in five bytes. For EAD items, positive labels in the new range are each encoded in five bytes as well. When using a critical EAD item (see <xref section="3.8" sectionFormat="of" target="RFC9528"/>), the negative ead_label in the EAD item is encoded in five bytes, except for -65536 that is encoded in three bytes (i.e., its two-byte argument is 65535).</t>
        <t>The four-byte argument does not imply that the decoded integer fits in a signed 32-bit type. In particular, neither 4294967295 nor -4294967296 is representable in such a type. Implementations supporting the newly defined Private Use ranges in full also need to support a representation that preserves all the values admitted by those ranges, such as a signed 64-bit integer or a separate sign and unsigned argument. Range checks and, for EAD labels, absolute-value calculations also need to preserve the full values of decoded integers.</t>
      </section>
      <section anchor="ead-labels">
        <name>EAD Labels</name>
        <t>As specified in <xref section="3.8" sectionFormat="of" target="RFC9528"/>, the "EDHOC External Authorization Data" registry <xref target="External.Authorization.Data"/> records the absolute values of the integer values used as ead_label in EAD items. Consistent with that, the Private Use range added to this registry pertains to both positive and negative ead_label values used in EAD items on the wire, with the absolute values listed in that range. The sign of ead_label retains its existing meaning: A negative value indicates that the EAD item is critical, and a nonnegative value indicates that the EAD item is non-critical.</t>
        <t>For example, the ead_label values 65536 and -65536 identify the same privately-defined EAD item as non-critical and critical, respectively. The processing rules for critical and non-critical EAD items in <xref section="3.8" sectionFormat="of" target="RFC9528"/> continue to apply.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document and the Private Use ranges defined in <xref target="iana"/> do not impact the security of the LAKE protocol. When using values from such Private Use ranges, the security considerations compiled in <xref section="9" sectionFormat="of" target="RFC9528"/> still apply.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document has the following actions for IANA.</t>
      <t>Note to RFC Editor: Please replace all occurrences of "[RFC-XXXX]" with the RFC number of this specification and delete this paragraph.</t>
      <section anchor="edhoc-method-types-registry">
        <name>EDHOC Method Types Registry</name>
        <t>IANA is asked to add the following two ranges to the "EDHOC Method Types" registry <xref target="Method.Types"/> within the "Ephemeral Diffie-Hellman Over COSE (EDHOC)" registry group:</t>
        <ul spacing="normal">
          <li>
            <t>-4294967296 to -65537</t>
          </li>
          <li>
            <t>65536 to 4294967295</t>
          </li>
        </ul>
        <t>For both ranges, the registration procedure is "Private Use" per <xref section="4.1" sectionFormat="of" target="RFC8126"/>.</t>
        <t>Consistent with the above, the following two entries are added to the registry, thereby registering the indicated values as reserved for private use:</t>
        <ul spacing="normal">
          <li>
            <t>Value: -4294967296 to -65537</t>
          </li>
          <li>
            <t>Initiator Authentication Key: N/A</t>
          </li>
          <li>
            <t>Responder Authentication Key: N/A</t>
          </li>
          <li>
            <t>Reference: [RFC-XXXX]</t>
          </li>
        </ul>
        <t><br/></t>
        <ul spacing="normal">
          <li>
            <t>Value: 65536 to 4294967295</t>
          </li>
          <li>
            <t>Initiator Authentication Key: N/A</t>
          </li>
          <li>
            <t>Responder Authentication Key: N/A</t>
          </li>
          <li>
            <t>Reference: [RFC-XXXX]</t>
          </li>
        </ul>
      </section>
      <section anchor="edhoc-error-codes-registry">
        <name>EDHOC Error Codes Registry</name>
        <t>IANA is asked to add the following two ranges to the "EDHOC Error Codes" registry <xref target="Error.Codes"/> within the "Ephemeral Diffie-Hellman Over COSE (EDHOC)" registry group.</t>
        <ul spacing="normal">
          <li>
            <t>-4294967296 to -65537</t>
          </li>
          <li>
            <t>65536 to 4294967295</t>
          </li>
        </ul>
        <t>For both ranges, the registration procedure is "Private Use" per <xref section="4.1" sectionFormat="of" target="RFC8126"/>.</t>
        <t>Consistent with the above, the following two entries are added to the registry, thereby registering the indicated values as reserved for private use:</t>
        <ul spacing="normal">
          <li>
            <t>ERR_CODE: -4294967296 to -65537</t>
          </li>
          <li>
            <t>ERR_INFO Type: N/A</t>
          </li>
          <li>
            <t>Description: Reserved for Private Use</t>
          </li>
          <li>
            <t>Change Controller: IETF</t>
          </li>
          <li>
            <t>Reference: [RFC-XXXX]</t>
          </li>
        </ul>
        <t><br/></t>
        <ul spacing="normal">
          <li>
            <t>ERR_CODE: 65536 to 4294967295</t>
          </li>
          <li>
            <t>ERR_INFO Type: N/A</t>
          </li>
          <li>
            <t>Description: Reserved for Private Use</t>
          </li>
          <li>
            <t>Change Controller: IETF</t>
          </li>
          <li>
            <t>Reference: [RFC-XXXX]</t>
          </li>
        </ul>
      </section>
      <section anchor="edhoc-external-authorization-data-registry">
        <name>EDHOC External Authorization Data Registry</name>
        <t>IANA is asked to add the following range to the "EDHOC External Authorization Data" registry <xref target="External.Authorization.Data"/> within the "Ephemeral Diffie-Hellman Over COSE (EDHOC)" registry group:</t>
        <ul spacing="normal">
          <li>
            <t>65536 to 4294967295</t>
          </li>
        </ul>
        <t>For this range, the registration procedure is "Private Use" per <xref section="4.1" sectionFormat="of" target="RFC8126"/>.</t>
        <t>Consistent with the above, the following entry is added to the registry, thereby registering the indicated values as reserved for private use:</t>
        <ul spacing="normal">
          <li>
            <t>Name: N/A</t>
          </li>
          <li>
            <t>Label: 65536 to 4294967295</t>
          </li>
          <li>
            <t>Description: Reserved for Private Use</t>
          </li>
          <li>
            <t>Reference: [RFC-XXXX]</t>
          </li>
        </ul>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC9528">
          <front>
            <title>Ephemeral Diffie-Hellman Over COSE (EDHOC)</title>
            <author fullname="G. Selander" initials="G." surname="Selander"/>
            <author fullname="J. Preuß Mattsson" initials="J." surname="Preuß Mattsson"/>
            <author fullname="F. Palombini" initials="F." surname="Palombini"/>
            <date month="March" year="2024"/>
            <abstract>
              <t>This document specifies Ephemeral Diffie-Hellman Over COSE (EDHOC), a very compact and lightweight authenticated Diffie-Hellman key exchange with ephemeral keys. EDHOC provides mutual authentication, forward secrecy, and identity protection. EDHOC is intended for usage in constrained scenarios, and a main use case is to establish an Object Security for Constrained RESTful Environments (OSCORE) security context. By reusing CBOR Object Signing and Encryption (COSE) for cryptography, Concise Binary Object Representation (CBOR) for encoding, and Constrained Application Protocol (CoAP) for transport, the additional code size can be kept very low.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9528"/>
          <seriesInfo name="DOI" value="10.17487/RFC9528"/>
        </reference>
        <reference anchor="External.Authorization.Data" target="https://www.iana.org/assignments/edhoc/edhoc.xhtml#edhoc-ead">
          <front>
            <title>EDHOC External Authorization Data</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="Method.Types" target="https://www.iana.org/assignments/edhoc#edhoc-method-types">
          <front>
            <title>EDHOC Method Types</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="Error.Codes" target="https://www.iana.org/assignments/edhoc/edhoc.xhtml#edhoc-error-codes">
          <front>
            <title>EDHOC Error Codes</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC8949">
          <front>
            <title>Concise Binary Object Representation (CBOR)</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.</t>
              <t>This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="94"/>
          <seriesInfo name="RFC" value="8949"/>
          <seriesInfo name="DOI" value="10.17487/RFC8949"/>
        </reference>
        <reference anchor="RFC9668">
          <front>
            <title>Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)</title>
            <author fullname="F. Palombini" initials="F." surname="Palombini"/>
            <author fullname="M. Tiloca" initials="M." surname="Tiloca"/>
            <author fullname="R. Höglund" initials="R." surname="Höglund"/>
            <author fullname="S. Hristozov" initials="S." surname="Hristozov"/>
            <author fullname="G. Selander" initials="G." surname="Selander"/>
            <date month="November" year="2024"/>
            <abstract>
              <t>The lightweight authenticated key exchange protocol Ephemeral Diffie-Hellman Over COSE (EDHOC) can be run over the Constrained Application Protocol (CoAP) and used by two peers to establish a Security Context for the security protocol Object Security for Constrained RESTful Environments (OSCORE). This document details this use of the EDHOC protocol by specifying a number of additional and optional mechanisms, including an optimization approach for combining the execution of EDHOC with the first OSCORE transaction. This combination reduces the number of round trips required to set up an OSCORE Security Context and to complete an OSCORE transaction using that Security Context.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9668"/>
          <seriesInfo name="DOI" value="10.17487/RFC9668"/>
        </reference>
        <reference anchor="Auth.Cred.Types" target="https://www.iana.org/assignments/edhoc#edhoc-authentication-credential-types">
          <front>
            <title>EDHOC Authentication Credential Types</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
      </references>
    </references>
    <?line 185?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors thank <contact fullname="Göran Selander"/> and <contact fullname="Mališa Vučinić"/> for their early feedback during the preparation of this document.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+1a3W4bxxW+36cYSEBhF9y1Lduyxf4gikQ7gm05kNWkQFEE
w90hOdVyh5nZJc0Iuu5Vn6HoS/Sqd0nfq985M/tHUrKTOO1NfSFTw9nzf77z
zaziOI6WQ/E4ikpd5moojrNMl9oUMhdfWr2UpRJ/cEpcyGKqnNCFKGdKnB2f
H4sLNdWutBrLZsLLr/V0Vq4U/RTHFVaKUqeQkIlXai1G79MZSRH3Xh+/Gt2H
eFOa1OSRHI+tWn5I9cRYQQ9GmUkLOYepmZWTMtaqnMS5vFLxwj8UV07Flh/C
eqlcGcGIIWyfmMhV47l2DlrK9QIyzkaXL6JIL+xQlLZy5cHDh0cPDyJplRyK
dyqtrC7X0Wo6ZN3ia2OvdDEVL62pFtHVCgKKUtlClfEpWRNFqcmwYSgqWPU8
iiTCYOwwEvwvDv8LGOOG4k0iLnVuUtkse8feSJuaza+MhdSLs3cjcfx5s4j4
KwXfzpyc/MXYzE1lKQtxcNDsSGH/ULxCplpRsBFa3o3iR4dPxJOHnfWqKC22
v1upTBXNuppLnQ/FnMxKSjbrM6sTp3a7dZmIN9//K8+V3fDr0oy1dFtfes/M
WNlSfG5cOhMv5+MvtnxEVK5WqDZVYEV+/3clnj7fcPNCVWWO8Hds974+O3j2
bIefL5Wdy2K96ai3M3lTKbLz6LNMJWOyK0nNPIoKg4dKvVSU1YsXJ88fHRyG
j0dPD57Tx9F7KgqZJ8ecfv2dpLpOTpEcXwr9suAAUE/x7xlqdigmMg/xDY05
Ov3i7UkjWfQkC5LsN0s7pWDNynLhhg8erFarRMtCJtDxQKLwp8UcbekeqGxm
Uv8zeT8r5/k+f46VzCDojYL0LLlEj7ifabEXJVjUTzAxmDVnKXEZpIysNTY5
QW5/rnksSbCkTxRAEhinLDAizNmolqMnR3W1HB5ytVAqkxOrPk28O8BLlUFy
6VeUzM9MgewJjtNGcMhKRL+hC6Hh3ej1i6HY+xOcjP+If3/ei6I4joUcU+um
gMnLmXYCSF6RHiGzzPUw38O3KI0fNbYdNeVMlmIBqJA0i8xPmDuLMHcSb9Nc
Z1muomifoNyarEo5bvviel/Twg0Z+1N1iOvrAAs3N7S41CgLsTCQzFNToZ0L
p8c6R+QGPONWMw0EtCpn4Zvuq/f4BMu/hgHk+1qslFUCyaDtA+HMXPlxbCiM
7YOZzkRhSiB0mldZE+GVLmf1Nl8wsDJVWQWhe52M7Il7Tim4g5nI254kj0hP
wL+bm/uJeI29VphiIHQpVgD6MaYkxQtpkmVJETOFT+BMLmmMuopc9ZbIJbBX
jnMlVqbKMzGGV6ZYqkJThVBkwnwXmVrkZs0FikjsKBtVsBw8jvwBwjNyCk8r
1P1aqNS4tSvVnOsLZMGP9l4q6hRBhENooCpfc6xMVWIOMgdA9LUVcrHI65Zw
C5XqiU7b9DtMFCoU5LwaYx8GPuUMnWvg/GJhMPKogjO1VLlZ+GYoMkGshXQg
wrJlRWRnPJbOO+SzhCgrBEcJCSGpJmYj0FpziRzDPW/SmpTMgw35OhEvKosV
O8eDg12N59RCWlqjWZ/D95TqqRBLmVfExayZc2nGHixgkP9mAMMwoe0yBEgY
UlNL5SQGG4JlGo8iBS4Rp21WsULPd+0KisHLUK1uQWmhFPuyQPAKDhdCnnMI
fGF7tookIZeqyKDKpWahfoPfUUO0gnB3qglYQOVKJUG2O5AWrxjdM5mgz6gM
kk3wstQRE49NcNjqqaZkOV1WXBYgtq7jLYy6viawvbnhRrkD+8oZmM8WBNRk
m4q2KTTuqlo3orvZ7p1OgwP7++IS2deFyc10LfYJ7Mp24WbTRcoQK5WpNcV6
zsoHaJmF5LDC1o/DxwFtRdhN6UPcNkoTH+CGH2QcqAY9E3HG4wZ7LCxTE01V
h15Vlh3u70YoaGUzdPdUMk0GrJkYaRNLr7A3ZQAPKl8qd59rriq8/RkFj7OE
J7/qNMP2gYWjzB9BaqsikyyYmntU+EOCHyw7Ul971ykVD0+EimtD+DBrWoIz
TzbKbK5LCviY292PCuqKLtSHfuwBvkFD6vZwx2W/EbnE21p34YamQq12uUFG
jcn1dmfX5hQHFYC8omj4vJ98/vaCe3VKOWZ7JVq8svF4DdEgLb4cN0bR43YU
gVzxKHqB/EN8VQR0CkLF+WC3REA6BQDMwjiPLKhTqxjM8HUwG0rORbWg754c
QNXhs4Ojp0EZgjBlnvdBXd7h0E9jZ/KqrGGGFaALKyce+Tkwq9yPMS4zK2ZF
cWPfIaXOgO1R3jmkpFcXmikhWxaaoBt97hEXkoMacoS6VU54AqdKU+JZPDYh
f0mG48HmQr5dPQXUzkIk0A6lte5VRKvDgfsSmWj0D4gXwfNco/Tq4YK6I6gL
3bIbQ4N89pzM9clo5AJWCk8UpCs9Mux9FI/ea124vt5g8GjXXgsHro/lAMfI
FsZP7GfStt2J+NrTMkLFsma5dwNF2QXsAbC/OzKhEX3AaLxiYsi5roMARd9W
2jI6CUbwfsXWdNNP5S4F8EWybRgG23yRK3qYo+eQKj8mZMqHb64BboCW3QCP
nQRaOv0dcbc5GAjZW5dsCt4D64ntdnO6VSker8GRkvroyccTbic+mwnffgHt
CLs6eKUk5mQNSdjSrXDq89HxKToRw2FA3ai54cFaVb4t8APyCPBWKs+R7Da4
EkxeU83ljaZttHse0M6PuvthntXwgwP8N2xRbVAjSLvdltAgT9XCJyU+fPr0
8aHvx/4Dno142+/pRCVEX9BjK7MBcHiMhDy9H6bGDgzMDIQwP0GdrL02z4Nr
dR5DJ6SBMScA+eODeAwkpJRy66JIEK4ql4CsQmlGuRabocJ2sZBMa4CTzwiE
NUSNZC1yo24DSf9oxKHAVnnuGX5d9DXTlx3l7VmoxkpURJ53p2R/zJpOd3mT
XRuWwyccljpsPJAaDk97uPybcdh0diAo6UylV9wi/gxKJeOretCMqNiPKJQm
hdtHp+dlD/M5CO1k2shr4KCk5jWriaJtjnxbwfdQ+o77sB5C33EjB1gGhafL
0x0juaGIdWjDKgEMZaDXbQ04JOKkOTjWCCbDeNkqGsJAH0HG8MbocMnBU2wM
3tYCDuVyR793TetaI4wHgpWm014DqJuO5mRv6HQaxmQbj3VfQHRb0aiyyptG
7dmM97mSBd99H7fW+aLBeYsPA67t9C4q1Zg3YM9ApUzx4wQUfB/lhaC0CKjV
e0mt7GO+FSMPcqQt4J32h4t1y4DDbUO+jut2bzTKvkaW0/oQxjaMp5P2pT/l
pBhuPGqrPDCg3tM9cW3i7uwDpi3gikwH6RpizYeT+qWFL8FMeZbvtq7cwini
I48fmanhWqY+/q7Ws+s82htqXcbAyLWLMPREpj3TmQzofBMXjvrRQA0S7jZx
4BNMPwZ0pUfubMZiJn3rT0yemxXP4dQ/QIkiQZB4zmdWQxrFCKTF2KH4MleS
r9kWuUwV47dJ4YPF2PTQsXd9/Su6Db252Ws7j0QU1XxMSD3xXV9fHXn4ouRk
Kld8Ssa3BORTKxezgJtbF+v1y7h1FLHfmujFVaBcWbbhHUZ275ahQdOuyB58
dt8HINbt5QqeXOCsTIdwcaonQO/4C5CaOZjk2yX8O3n7biTusfT7HYlTen82
jKJf96YzHVyoHZ9hPdCQ7knLNzZDYbdqbrm9RAj6F5jA0zvuLxHZbcwmkDTL
ACL9+GGXP9DbHoA35qz5Iaswu/2KsjWJqMEsawY9H69odma9i04gOceILxqG
t4bqjA9zKMjNM8srtR6K8wfH2HPBl2bohDv38B1XClVN1UbRb8f29x0jduXl
lzahKfnOy5pPVPEdiX2+0L5g+mT1nvy/3j+u3kcXF9+cvD0d3V7ytOPs/MVb
hqq6eE6Vwwxd+DvXi66CTlyw78S/qjmpXw/Y8GcAH+qA1qzdTfBfNartidsZ
8I/rEU9GN9rjk9DrTzgubm0Tz53DHfP/pEuoQ9Yc41+4Pc75jyl8efHx6baC
/Nja211h9HJ0LNMrIlPH6VVhVqBgU/+ihF4YyP7aTXQ99KRGZb/b45fTe+Hd
qX+Xzdy9uIKK65ff/xOpAlXN6f2BvUGNEOXBN29krv/9Dym+qn74my70D3+l
78JlkQarlxbn7wlOnGSZQErrKOL0ycddymJNqmqCl0T/AcY/573nJAAA

-->

</rfc>
