<?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.19 (Ruby 3.0.2) -->
<?rfc strict="yes"?>
<?rfc comments="yes"?>
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-reddy-cose-jose-pqc-hybrid-hpke-03" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.24.0 -->
  <front>
    <title abbrev="PQ/T Hybrid KEM: HPKE with JOSE/COSE">PQ/T Hybrid KEM: HPKE with JOSE/COSE</title>
    <seriesInfo name="Internet-Draft" value="draft-reddy-cose-jose-pqc-hybrid-hpke-03"/>
    <author fullname="Tirumaleswar Reddy">
      <organization>Nokia</organization>
      <address>
        <postal>
          <city>Bangalore</city>
          <region>Karnataka</region>
          <country>India</country>
        </postal>
        <email>kondtir@gmail.com</email>
      </address>
    </author>
    <author fullname="Hannes Tschofenig">
      <organization/>
      <address>
        <postal>
          <country>Germany</country>
        </postal>
        <email>hannes.tschofenig@gmx.net</email>
      </address>
    </author>
    <date year="2024" month="November" day="03"/>
    <area>Security</area>
    <workgroup>COSE</workgroup>
    <keyword>PQC</keyword>
    <keyword>COSE</keyword>
    <keyword>JOSE</keyword>
    <keyword>Hybrid</keyword>
    <keyword>HPKE</keyword>
    <abstract>
      <?line 63?>

<t>This document outlines the construction of a PQ/T Hybrid Key Encapsulation Mechanism (KEM) in Hybrid Public-Key Encryption (HPKE) for integration with JOSE and COSE. It specifies the utilization of both traditional and Post-Quantum Cryptography (PQC) algorithms, referred to as PQ/T Hybrid KEM, within the context of JOSE and COSE.</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-reddy-cose-jose-pqc-hybrid/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        cose Working Group mailing list (<eref target="mailto:cose@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/cose/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/cose/"/>.
      </t>
    </note>
  </front>
  <middle>
    <?line 67?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The migration to Post-Quantum Cryptography (PQC) is unique in the history of modern digital cryptography in that neither the traditional algorithms nor the post-quantum algorithms are fully trusted to protect data for the required data lifetimes. The traditional algorithms, such as RSA and elliptic curve, will fall to quantum cryptalanysis, while the post-quantum algorithms face uncertainty about the underlying mathematics, compliance issues, unknown vulnerabilities, hardware and software implementations that have not had sufficient maturing time to rule out classical cryptanalytic attacks and implementation bugs.</t>
      <t>During the transition from traditional to post-quantum algorithms, there is a desire or a requirement for protocols that use both algorithm types. Hybrid key exchange refers to using multiple key exchange algorithms simultaneously and combining the result with the goal of providing security even if all but one of the component algorithms is broken. It is motivated by transition to post-quantum cryptography.</t>
      <t>HPKE offers a variant of public-key encryption of arbitrary-sized plaintexts for a recipient public key. The specifications for the use of HPKE with JOSE and COSE are described in <xref target="I-D.rha-jose-hpke-encrypt"/> and <xref target="I-D.ietf-cose-hpke"/>, respectively. HPKE can be extended to support PQ/T Hybrid KEM as defined in <xref target="I-D.connolly-cfrg-xwing-kem"/>. This specification defines PQ/T Hybrid KEM in HPKE for use with JOSE and COSE.</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>
      <?line -18?>

<t>This document makes use of the terms defined in <xref target="I-D.ietf-pquip-pqt-hybrid-terminology"/>. For the purposes of this document, it is helpful to be able to divide cryptographic algorithms into two classes:</t>
      <t>"Traditional Algorithm":  An asymmetric cryptographic algorithm based on integer factorisation, finite field discrete logarithms, elliptic curve discrete logarithms, or related mathematical problems. In the context of JOSE, examples of traditional key exchange algorithms include Elliptic Curve Diffie-Hellman Ephemeral Static <xref target="RFC6090"/> <xref target="RFC8037"/>. In the context of COSE, examples of traditional key exchange algorithms include Ephemeral-Static (ES) DH and Static-Static (SS) DH <xref target="RFC9052"/>.</t>
      <t>"Post-Quantum Algorithm":  An asymmetric cryptographic algorithm that is believed to be secure against attacks using quantum computers as well as classical computers. Examples of PQC key exchange algorithms include ML-KEM.</t>
      <t>"Post-Quantum Traditional (PQ/T) Hybrid Scheme":  A multi-algorithm scheme where at least one component algorithm is a post-quantum algorithm and at least one is a traditional algorithm.</t>
      <t>"PQ/T Hybrid Key Encapsulation Mechanism":  A multi-algorithm KEM made up of two or more component KEM algorithms where at least one is a post-quantum algorithm and at least one is a traditional algorithm.</t>
    </section>
    <section anchor="construction">
      <name>Construction</name>
      <t>ML-KEM is a one-pass (store-and-forward) cryptographic mechanism for an originator to securely send keying material to a recipient using the recipient's ML-KEM public key. Three parameters sets for ML-KEMs are specified by <xref target="FIPS203"/>. In order of increasing security strength (and decreasing performance), these parameter sets
are ML-KEM-512, ML-KEM-768, and ML-KEM-1024. <xref target="I-D.connolly-cfrg-xwing-kem"/> uses a multi-algorithm scheme,
where one component algorithm is a post-quantum algorithm and another one is a traditional algorithm. The Combiner function defined in Section 5.3 of <xref target="I-D.connolly-cfrg-xwing-kem"/> combines the output of a post-quantum KEM and a traditional KEM to generate a single shared secret.</t>
    </section>
    <section anchor="ciphersuite-registration">
      <name>Ciphersuite Registration</name>
      <t>This specification registers a number of PQ/T Hybrid KEMs for use with HPKE. A ciphersuite is thereby a combination of several algorithm configurations:</t>
      <ul spacing="normal">
        <li>
          <t>KEM algorithm (Traditional Algorithm + PQ KEM, for example, X25519MLKEM768)</t>
        </li>
        <li>
          <t>KDF algorithm</t>
        </li>
        <li>
          <t>AEAD algorithm</t>
        </li>
      </ul>
      <t>The "KEM", "KDF", and "AEAD" values are conceptually taken from the HPKE IANA registry <xref target="HPKE-IANA"/>. Hence, JOSE and COSE cannot use an algorithm combination that is not already available with HPKE.</t>
      <t>For readability the algorithm ciphersuites labels are built according to the following scheme:</t>
      <artwork><![CDATA[
   HPKE-<KEM>-<KDF>-<AEAD>
]]></artwork>
      <t>The HPKE PQ/T hybrid ciphersuites for JOSE and COSE are defined in <xref target="IANA"/>. Note that the PQ/T Hybrid KEM in HPKE is not an authenticated KEM. The HPKE Base mode can only be supported with the PQ/T Hybrid KEM.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The security considerations in <xref target="I-D.connolly-cfrg-xwing-kem"/> are to be taken into account.</t>
      <t>The shared secrets computed in the hybrid key exchange should be computed in a way that achieves the "hybrid" property: the resulting secret is secure as long as at least one of the component key exchange algorithms is unbroken. PQC KEMs used in the manner described in this document <bcp14>MUST</bcp14> explicitly be designed to be secure in the event that the public key is reused, such as achieving IND-CCA2 security. ML-KEM has such security properties.</t>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <section anchor="jose">
        <name>JOSE</name>
        <t>This document requests IANA to add new values to the "JSON Web Signature and Encryption Algorithms" registry.</t>
      </section>
      <section anchor="jose-algorithms-registry">
        <name>JOSE Algorithms Registry</name>
        <ul spacing="normal">
          <li>
            <t>Algorithm Name: HPKE-X25519MLKEM768-SHA256-AES256GCM</t>
          </li>
          <li>
            <t>Algorithm Description: Cipher suite for JOSE-HPKE in Base Mode that uses the X25519MLKEM768 Hybrid 
KEM, the HKDF-SHA256 KDF, and the AES-256-GCM AEAD.</t>
          </li>
          <li>
            <t>Algorithm Usage Location(s): "alg"</t>
          </li>
          <li>
            <t>JOSE Implementation Requirements: Optional</t>
          </li>
          <li>
            <t>Change Controller: IANA</t>
          </li>
          <li>
            <t>Specification Document(s): [[TBD: This RFC]]</t>
          </li>
          <li>
            <t>Algorithm Analysis Documents(s): TODO</t>
          </li>
          <li>
            <t>Algorithm Name: HPKE-X25519MLKEM768-SHA256-ChaCha20Poly1305</t>
          </li>
          <li>
            <t>Algorithm Description: Cipher suite for JOSE-HPKE in Base Mode that uses the X25519MLKEM768 Hybrid<br/>
KEM, the HKDF-SHA256 KDF, and the ChaCha20Poly1305 AEAD.</t>
          </li>
          <li>
            <t>Algorithm Usage Location(s): "alg"</t>
          </li>
          <li>
            <t>JOSE Implementation Requirements: Optional</t>
          </li>
          <li>
            <t>Change Controller: IANA</t>
          </li>
          <li>
            <t>Specification Document(s): [[TBD: This RFC]]</t>
          </li>
          <li>
            <t>Algorithm Analysis Documents(s): TODO</t>
          </li>
        </ul>
      </section>
      <section anchor="cose">
        <name>COSE</name>
        <t>This document requests IANA to add new values to the 'COSE Algorithms' registry.</t>
        <section anchor="cose-algorithms-registry">
          <name>COSE Algorithms Registry</name>
          <ul spacing="normal">
            <li>
              <t>Name: HPKE-Base-X25519MLKEM768-SHA256-AES256GCM</t>
            </li>
            <li>
              <t>Value: TBD1</t>
            </li>
            <li>
              <t>Description: Cipher suite for COSE-HPKE in Base Mode that uses the X25519MLKEM768 Hybrid KEM, the<br/>
HKDF-SHA256 KDF, and the AES-256-GCM AEAD.</t>
            </li>
            <li>
              <t>Capabilities: [kty]</t>
            </li>
            <li>
              <t>Change Controller: IANA</t>
            </li>
            <li>
              <t>Reference: [[TBD: This RFC]]</t>
            </li>
            <li>
              <t>Name: HPKE-Base-X25519MLKEM768-SHA256-ChaCha20Poly1305</t>
            </li>
            <li>
              <t>Value: TBD2</t>
            </li>
            <li>
              <t>Description: Cipher suite for COSE-HPKE in Base Mode that uses the X25519MLKEM768 Hybrid    <br/>
KEM, the HKDF-SHA256 KDF, and the ChaCha20Poly1305 AEAD.</t>
            </li>
            <li>
              <t>Capabilities: [kty]</t>
            </li>
            <li>
              <t>Change Controller: IANA</t>
            </li>
            <li>
              <t>Reference: [[TBD: This RFC]]</t>
            </li>
          </ul>
        </section>
      </section>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Thanks to Ilari Liusvaara and Orie Steele for the discussion and comments.</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="FIPS203" target="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.203.pdf">
          <front>
            <title>Module-Lattice-based Key-Encapsulation Mechanism Standard</title>
            <author>
              <organization/>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="HPKE-IANA" target="https://www.iana.org/assignments/hpke/hpke.xhtml">
          <front>
            <title>Hybrid Public Key Encryption (HPKE) IANA Registry</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="I-D.rha-jose-hpke-encrypt">
          <front>
            <title>Use of Hybrid Public Key Encryption (HPKE) with JSON Object Signing and Encryption (JOSE)</title>
            <author fullname="Tirumaleswar Reddy.K" initials="T." surname="Reddy.K">
              <organization>Nokia</organization>
            </author>
            <author fullname="Hannes Tschofenig" initials="H." surname="Tschofenig">
         </author>
            <author fullname="Aritra Banerjee" initials="A." surname="Banerjee">
              <organization>Nokia</organization>
            </author>
            <author fullname="Orie Steele" initials="O." surname="Steele">
              <organization>Transmute</organization>
            </author>
            <author fullname="Michael B. Jones" initials="M. B." surname="Jones">
              <organization>Self-Issued Consulting</organization>
            </author>
            <date day="31" month="March" year="2024"/>
            <abstract>
              <t>   This specification defines Hybrid Public Key Encryption (HPKE) for
   use with JSON Object Signing and Encryption (JOSE).  HPKE offers a
   variant of public key encryption of arbitrary-sized plaintexts for a
   recipient public key.

   HPKE works for any combination of an asymmetric key encapsulation
   mechanism (KEM), key derivation function (KDF), and authenticated
   encryption with additional data (AEAD) function.  Authentication for
   HPKE in JOSE is provided by JOSE-native security mechanisms or by one
   of the authenticated variants of HPKE.

   This document defines the use of the HPKE with JOSE.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-rha-jose-hpke-encrypt-07"/>
        </reference>
        <reference anchor="I-D.ietf-cose-hpke">
          <front>
            <title>Use of Hybrid Public-Key Encryption (HPKE) with CBOR Object Signing and Encryption (COSE)</title>
            <author fullname="Hannes Tschofenig" initials="H." surname="Tschofenig">
              <organization>University of Applied Sciences Bonn-Rhein-Sieg</organization>
            </author>
            <author fullname="Orie Steele" initials="O." surname="Steele">
              <organization>Transmute</organization>
            </author>
            <author fullname="Ajitomi, Daisuke" initials="A." surname="Daisuke">
              <organization>bibital</organization>
            </author>
            <author fullname="Laurence Lundblade" initials="L." surname="Lundblade">
              <organization>Security Theory LLC</organization>
            </author>
            <date day="12" month="July" year="2024"/>
            <abstract>
              <t>   This specification defines hybrid public-key encryption (HPKE) for
   use with CBOR Object Signing and Encryption (COSE).  HPKE offers a
   variant of public-key encryption of arbitrary-sized plaintexts for a
   recipient public key.

   HPKE works for any combination of an asymmetric key encapsulation
   mechanism (KEM), key derivation function (KDF), and authenticated
   encryption with additional data (AEAD) function.  Authentication for
   HPKE in COSE is provided by COSE-native security mechanisms or by one
   of the authenticated variants of HPKE.

   This document defines the use of the HPKE with COSE.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-cose-hpke-09"/>
        </reference>
        <reference anchor="I-D.connolly-cfrg-xwing-kem">
          <front>
            <title>X-Wing: general-purpose hybrid post-quantum KEM</title>
            <author fullname="Deirdre Connolly" initials="D." surname="Connolly">
              <organization>SandboxAQ</organization>
            </author>
            <author fullname="Peter Schwabe" initials="P." surname="Schwabe">
              <organization>MPI-SP &amp; Radboud University</organization>
            </author>
            <author fullname="Bas Westerbaan" initials="B." surname="Westerbaan">
              <organization>Cloudflare</organization>
            </author>
            <date day="21" month="October" year="2024"/>
            <abstract>
              <t>   This memo defines X-Wing, a general-purpose post-quantum/traditional
   hybrid key encapsulation mechanism (PQ/T KEM) built on X25519 and ML-
   KEM-768.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-connolly-cfrg-xwing-kem-06"/>
        </reference>
        <reference anchor="I-D.ietf-pquip-pqt-hybrid-terminology">
          <front>
            <title>Terminology for Post-Quantum Traditional Hybrid Schemes</title>
            <author fullname="Florence D" initials="F." surname="D">
              <organization>UK National Cyber Security Centre</organization>
            </author>
            <author fullname="Michael P" initials="M." surname="P">
              <organization>UK National Cyber Security Centre</organization>
            </author>
            <author fullname="Britta Hale" initials="B." surname="Hale">
              <organization>Naval Postgraduate School</organization>
            </author>
            <date day="10" month="September" year="2024"/>
            <abstract>
              <t>   One aspect of the transition to post-quantum algorithms in
   cryptographic protocols is the development of hybrid schemes that
   incorporate both post-quantum and traditional asymmetric algorithms.
   This document defines terminology for such schemes.  It is intended
   to be used as a reference and, hopefully, to ensure consistency and
   clarity across different protocols, standards, and organisations.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-pquip-pqt-hybrid-terminology-04"/>
        </reference>
        <reference anchor="RFC6090">
          <front>
            <title>Fundamental Elliptic Curve Cryptography Algorithms</title>
            <author fullname="D. McGrew" initials="D." surname="McGrew"/>
            <author fullname="K. Igoe" initials="K." surname="Igoe"/>
            <author fullname="M. Salter" initials="M." surname="Salter"/>
            <date month="February" year="2011"/>
            <abstract>
              <t>This note describes the fundamental algorithms of Elliptic Curve Cryptography (ECC) as they were defined in some seminal references from 1994 and earlier. These descriptions may be useful for implementing the fundamental algorithms without using any of the specialized methods that were developed in following years. Only elliptic curves defined over fields of characteristic greater than three are in scope; these curves are those used in Suite B. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6090"/>
          <seriesInfo name="DOI" value="10.17487/RFC6090"/>
        </reference>
        <reference anchor="RFC8037">
          <front>
            <title>CFRG Elliptic Curve Diffie-Hellman (ECDH) and Signatures in JSON Object Signing and Encryption (JOSE)</title>
            <author fullname="I. Liusvaara" initials="I." surname="Liusvaara"/>
            <date month="January" year="2017"/>
            <abstract>
              <t>This document defines how to use the Diffie-Hellman algorithms "X25519" and "X448" as well as the signature algorithms "Ed25519" and "Ed448" from the IRTF CFRG elliptic curves work in JSON Object Signing and Encryption (JOSE).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8037"/>
          <seriesInfo name="DOI" value="10.17487/RFC8037"/>
        </reference>
        <reference anchor="RFC9052">
          <front>
            <title>CBOR Object Signing and Encryption (COSE): Structures and Process</title>
            <author fullname="J. Schaad" initials="J." surname="Schaad"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.</t>
              <t>This document, along with RFC 9053, obsoletes RFC 8152.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="96"/>
          <seriesInfo name="RFC" value="9052"/>
          <seriesInfo name="DOI" value="10.17487/RFC9052"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA91a63LbxhX+j6fY0j8ipQJ1sZXYnNQJTUqREt0syk0zHk9n
CSzJrUAA3l2IYjzKs/RZ+mT9zlkABCQqdp2mP5rxiMDezv075ywShmHgtEtU
T3QuXm9fiaPl2OhY/Hhw2hNHFz8eiIV2M/HD+ehge4A/nUCOx0bdfPLySDo1
zcyyJ6yLgyDOolTOQS02cuJCo+J4GUaZVeE/6E/+PgpnfGQ4y69VYIvxXFur
s9Qtc+w6Prg6DNJiPlamF8Q4uhdEWWpVagvbE84UKgBrTwNplASLIxUVRrtl
J1hk5npqsiLHqGfsWi0xGPcCEYqL1wP6oQn6/aH89cLxE0QLghuVFqAoRHUS
Md7Bu2eu8xOI6HQqvqdpGp9LnZTLvtPKTbqZmdK4NNEM4zPnctvb3qZlNKRv
VLdatk0D22OTLazapgO2aWMQWCfT+O8yyVJQXCob5Lon3ros2hI2M86oicXT
cl4+OKMjtyWibD5XqcMIDDCXeQ423wWBLNwsM6QCnC3EpEgSb50rbYq5TJRd
SCMuyUi8AHzJVP8iHQzSE2fZtZY8HkHHPfFKplMwZhSPGTXlVT9Kk0onr8uV
WZE68objNC43q1JL11kaO22+m9J7Fxx3HvJ1JNNUWXFlo1k2UamePmRrxVCb
4PfKzGW6bJGc8XFdVx8H4rfdVLlOEIggzbDDwSi9INDpZPUmcMjh8cVob+ep
JyKqEDrN4iJR4Yl0TkcqHEurEBxqGR6kkcxtkTCP4lRFIK3tXIzInNLEnfIc
aabK9UTlGelNkhdj28Va151mN9v0QCPbRH/77Hh01aWnLljp5vHEn8KBISYy
sWQK8t3wuH/WL3mtjV7+B+3BHJhviVIG9kUxTnREIgiIYJY5879BZ27yJnjH
FDyZ5XoBFotFV8tUepdGJE9TdsRtCm/+072duXnykHE/EoRhKOQYBGTkguBq
pi25cEGHiKxwiSZ/cDMlCAcAABEzmE2EFC2A8gKstcEG0GtT6LQtc7heZrgB
lgLTjD+mxjsBQzKCdMWxEzZXkZ7okrfC6aT0T2JtnGEPJIo1jciEt15k1oWv
C5m6Yi4GRDUDjXy2FBuAp00hE8AoiM0RxAhuZYCdwmVCWnEPibeYKchTqsWp
W0dk21wGrNq5juMEyn6CgHQG3sv6I0UrzFVCgszH2INdilS/L5QoCcNSDrhP
hOdZrEwqYj3VDtJGzd28WjqRKvCsDG9tqaYWWyAeeTonVt6XrDTmAfoMFUtK
BNZ59eQmcypy5FqSjUcnGPW+0KQ/Hk30RDk9BxCIq0epA0uLaEbavhz1WYsq
STRcIxLIMTeKlJ4k5LsJka3YY1llAuCxGmcsZjpRvynEREbwlzRSxkn42RLO
Dzf3XpRCjcmSMgyQaKYIjiLL4J4nCDJsRK4sFIaK9DrNFqm4KZJUGTmG+zlN
EzNgzYIURRLYbOL4ReMARSHF5rbeIjN5o6BzesDSYjLRkaaoA1kkVTBBOiNZ
DSCPYlFECUV4VJkYYZ8sSUFAQxldW6bZJiXGxdTCFYfliV79qWX9i4nJ5i1z
kD3X622L9pIkoCJiZWFdABueS1MzXpD5yR+yKEtKIQurfDjWR3EyhyuU8YQy
Qahbgoqp8nFniY3CshmKxGnI017VsKbVtESmKiss/JIUAGuNdVpJaxQAyXkU
ofdpBjERMmDzRse0ypY1jFAoP4QGsMHDxtA2KgBa6YN8nuMVIjZoQxUoH65V
yoCEt3mG9CUpLsbLpprva7UZn12UHFzXZRMWXYobaeBrDCi5B0oWfgWUhL1m
rEHALEOrfwG9PCFfBgxZtgFZJdI5e5M/gxToo68Ezqj0xCpiyU44uF1i1mDG
oQ+rR0aPQQ6Y8uHDt8fhsGtm0heWlGnCksm7O95YLqGCy1egtObujtCVmKBU
n4ApJhlJuKqCiZ1CEDKw2CLPUXDdB19CiFhNkJaafACF0wzIFEYTMw1vFzAs
1Da/uyOhYZqW1OX+B7jOKYq4IaWQQtblHoLyQZbCV7wCaWZI57GtrUd2shgV
vxYVy5vRVWfL/4qzc36+PHj95vjyYEjPo6P+yUn9EJQrRkfnb06Gq6fVzsH5
6enB2dBvxqhoDQWd0/7PmCGuOucXV8fnZ/2Tjk8CzcxO9oSOx4pzrcmNIreV
NmgZ+dXg4l//3H0GJf/p8nCwt7v7Aqb1L893v36Gl8VMpZ5aliL+/Cv8aRmg
BlaSUjnHEwoDSk2AEZjPzgg6CU6ATF++Jc2864lvxlG+++xlOUACtwYrnbUG
WWcPRx5s9kpcM7SGTK3N1vg9Tbf57f/ceq/03hj85lsqpES4+/zbl8H9Mmsu
r+GMZQQyRKOUXuflHEo58DbHX1c1crRaw/uz6ZL8/bDK4oUB6uBgPrRBb0to
hquZSnKk89IP5Dhhl4g1cFE1MYoSTAP1Uixyi8wnI2VRu3euGimkXy3t9ITo
w/roleaK2qTHzhS+ikdcct2HGgU5GqWNthytW4KDC6WHVgkqCg0HhbcKyCur
3NQuFdavgVqMShieV9kdDCMTQPQ5MtLx2ooOp99KSqpekw1RH0tKOo2SAjo8
qLgaMFdDjRSvwiMwi0ZJHOTgAbVDQj0KrYKREVhf7bzY4Sijl+c7T78mmz7k
bPD7OKtohyXtjYPRphgecST7oXpm5Gc8Qy929veIIRi9VbB+htW5PKAcqhKN
1BuXfsjpGExPkdGsq0sbXw/UGRT5uHCcL61YQKH026iOqumuOGhoCHX0RzVz
ehIiE3Tvy9f08A1KG5tV3hhFpEoW25cr4UpEy3OEiiSRE4mS1tcVawoKX1qt
L7/YLq0DePHaSpp5/7TObD3XlAnnEroocvYrxDpiZ56ZJtuciVfqWyPif08c
Trh17xkE3kZ+DzaHOewuNqgbUiFODpG+UXXHm/dcb143pFwjoZAyaJhS6Qgw
s9LxkMQsShDyk7IPUCjHGCSbVZV3R19glmNf2NJ57pVcRgGLpZEIB3JYq8oi
zS/2XVXVzXLl+OFDefdRRj7qCGAiLAEfNdBYq2iFWlQ6RZmyQTqNVb0iV4Zv
VNC1bHJKtg02mAu6xCu5CPd397aq56+/eu5Tevm+u7P3rPvRQovyFxlkfQxs
Bd5DPtv30SdR9/oRX+EKd8ANAKURtHmNeo8z6Uj5of3uU1LpR6Xy3UR5zYAe
LC+cv/xoMcvRQGy2+KJR+M1UUYuIbCQFWQZp1qJLBDuWrOW8g2sgsrEF5bny
wkdWFwUPylfDC3y34O9qPbq1ilnbrmKpru0i2KMGIW19Uwefk6Wg9RWKBSSb
pm4p+Uz0tPB8UdoP2yAgNtaWAeLP4MzfmhBDZcbaEn/b29/ffXF6ghk43Cad
NjxcnYb3/kF/2BjgwrqD5VT4Ym1V5dKyDrqmpFA+mMBopHJXSL6pQG1VNbrY
z+U9X6uZ8loNLlBf4FHAHaGJAXvt9gftCTXqpE2ZtnSyUlqVz2ihTBCGMdR6
QzfPVFmtjIDy75BrERn7e4Mlc9Y4dGUiK7BbJV6ucaHRycooAiAw+mS8cQLH
zRYMChxqsMyvv/5Kt3ss1zfQ2Ev8HR7iL+nqJU+zNlkb7De+lGyTJnOt6wIb
VWmltLPMKa8A4uixtqpSTspXpNRARVyOUcIVNT+vUA3yjRY3hdxWUFngu0Gs
rlv5e2Q4jqoPEpwxUMeW3urFrUEzak1+ShvZaJi8R3EZTLYoUopgPr4Z1bYq
QuL6vm7NfQc6oQI17Vi1VkuxkEuvThnNqDjy8NPxR3SoZAW80yeB1RVHmRVA
mvRcVVFwoAwT+G2l2wfXGo+WRXTrWN1yUP3EyFLYlVhzuuI37cuBdq/J7Zy6
zZETtfPWpAukaXq/5itPpHsYt/KmVTYlbowi4qvLQq8gEv74bBgOBv292szd
Kh/PqOek9bUDlArUyrLXMCC0PUZ8eMLOjekn/nvVvaaN7r2UhZ15MzlDHItU
LSokKqOz88Po/Ez8pMZiBInpZs9fDTYuvmuotJ0albo13cZ0/SlAEPiuEPbM
f7qhaG+jaohueG//q7B/MMLP94PT1rYhmyz335p8AhI+MVSRH/qwTX1MnlJM
Vpd63iPb5KpgBPYw3jPgAnhKNgjgPWbTBHgKiTdwxUjfbfH2xko44knmM96G
3eyJDtyyE/iPh+K4fct5ubqEtD1xnvskhMUD79GwrTMIbGXKLzGhGLVS6rA0
K1N6+/bq1bDnL47Q87x712KtT7euFlPVHsubrs6H5/+hWcAc/u3tXGTJcvfp
zv7/xjqfZp77vP0f2QiBNfj8gP5i0A7KL9ox689+JGi/FE2nILN9NGCx5a9E
H8y/Gu4Kev9tzxh8vmfUXiG4evj0yAVTA5nXX0FgnWu3fMfDj9gWU5d010/F
1jpjfrqqHgRRS2N7f6jC/BdU8Tvi6Q/Q3BPRj+jjVKLiKbt+8KFXtgkq/kuH
P/527sj7ZXrNbn2cSKPFiS7sjUSHyDyfG63EyCmVqPobAV2rFfw/i1QfWvj8
bvBvnDzTfuUiAAA=

-->

</rfc>
