<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version  -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc docmapping="yes"?>

<rfc docName="draft-ietf-tls-certificate-compression-04" category="std">

  <front>
    <title abbrev="TLS Certificate Compression">TLS Certificate Compression</title>

    <author initials="A." surname="Ghedini" fullname="Alessandro Ghedini">
      <organization>Cloudflare, Inc.</organization>
      <address>
        <email>alessandro@cloudflare.com</email>
      </address>
    </author>
    <author initials="V." surname="Vasiliev" fullname="Victor Vasiliev">
      <organization>Google</organization>
      <address>
        <email>vasilvv@google.com</email>
      </address>
    </author>

    <date year="2018" month="October" day="03"/>

    <area>Security</area>
    <workgroup>TLS</workgroup>
    

    <abstract>


<t>In TLS handshakes, certificate chains often take up
the majority of the bytes transmitted.</t>

<t>This document describes how certificate chains can be compressed to reduce the
amount of data transmitted and avoid some round trips.</t>



    </abstract>


  </front>

  <middle>


<section anchor="introduction" title="Introduction">

<t>In order to reduce latency and improve performance it can be useful to reduce
the amount of data exchanged during a TLS handshake.</t>

<t><xref target="RFC7924"></xref> describes a mechanism that allows a client and a server to avoid
transmitting certificates already shared in an earlier handshake, but it
doesn’t help when the client connects to a server for the first time and
doesn’t already have knowledge of the server’s certificate chain.</t>

<t>This document describes a mechanism that would allow certificates to be
compressed during full handshakes.</t>

</section>
<section anchor="notational-conventions" title="Notational Conventions">

<t>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
“SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” 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="negotiating-certificate-compression" title="Negotiating Certificate Compression">

<t>This extension is only supported with TLS 1.3 and newer; if TLS 1.2 or earlier
is negotiated, the peers MUST ignore this extension.</t>

<t>This document defines a new extension type (compress_certificate(27)), which
can be used to signal the supported compression formats for the Certificate
message to the peer.  Whenever it is sent by the client as a ClientHello message
extension (<xref target="RFC8446"></xref>, Section 4.1.2), it indicates the support for
compressed server certificates.  Whenever it is sent by the server as a
CertificateRequest extension (<xref target="RFC8446"></xref>, Section 4.3.2), it indicates
the support for compressed client certificates.</t>

<t>By sending a compress_certificate extension, the sender indicates to the peer
the certificate compression algorithms it is willing to use for decompression.
The “extension_data” field of this extension SHALL contain a
CertificateCompressionAlgorithms value:</t>

<figure><artwork><![CDATA[
    enum {
        zlib(1),
        brotli(2),
        (65535)
    } CertificateCompressionAlgorithm;

    struct {
        CertificateCompressionAlgorithm algorithms<1..2^8-1>;
    } CertificateCompressionAlgorithms;
]]></artwork></figure>

<t>There is no ServerHello extension that the server is required to echo back.</t>

</section>
<section anchor="compressed-certificate-message" title="Compressed Certificate Message">

<t>If the peer has indicated that it supports compression, server and client MAY
compress their corresponding Certificate messages and send them in the form of
the CompressedCertificate message (replacing the Certificate message).</t>

<t>The CompressedCertificate message is formed as follows:</t>

<figure><artwork><![CDATA[
    struct {
         CertificateCompressionAlgorithm algorithm;
         uint24 uncompressed_length;
         opaque compressed_certificate_message<1..2^24-1>;
    } CompressedCertificate;
]]></artwork></figure>

<t><list style="hanging">
  <t hangText='algorithm'>
  The algorithm used to compress the certificate.  The algorithm MUST be one of
the algorithms listed in the peer’s compress_certificate extension.</t>
  <t hangText='uncompressed_length'>
  The length of the Certificate message once it is uncompressed.  If after
decompression the specified length does not match the actual length, the
party receiving the invalid message MUST abort the connection with the
“bad_certificate” alert.</t>
  <t hangText='compressed_certificate_message'>
  The compressed body of the Certificate message, in the same format as it
would normally be expressed in. The compression algorithm defines how the
bytes in the compressed_certificate_message field are converted into the
Certificate message.</t>
</list></t>

<t>If the specified compression algorithm is zlib, then the Certificate message
MUST be compressed with the ZLIB compression algorithm, as defined in <xref target="RFC1950"></xref>.
If the specified compression algorithm is brotli, the Certificate message MUST
be compressed with the Brotli compression algorithm as defined in <xref target="RFC7932"></xref>.</t>

<t>If the received CompressedCertificate message cannot be decompressed, the
connection MUST be torn down with the “bad_certificate” alert.</t>

<t>If the format of the Certificate message is altered using the
server_certificate_type or client_certificate_type extensions <xref target="RFC7250"></xref>, the
resulting altered message is compressed instead.</t>

</section>
<section anchor="security-considerations" title="Security Considerations">

<t>After decompression, the Certificate message MUST be processed as if it were
encoded without being compressed.  This way, the parsing and the verification
have the same security properties as they would have in TLS normally.</t>

<t>Since certificate chains are typically presented on a per-server name or
per-user basis, the attacker does not have control over any individual fragments
in the Certificate message, meaning that they cannot leak information about the
certificate by modifying the plaintext.</t>

<t>The implementations SHOULD bound the memory usage when decompressing the
CompressedCertificate message.</t>

<t>The implementations MUST limit the size of the resulting decompressed chain to
the specified uncompressed length, and they MUST abort the connection if the
size exceeds that limit.  TLS framing imposes 16777216 byte limit on the
certificate message size, and the implementations MAY impose a limit that is
lower than that; in both cases, they MUST apply the same limit as if no
compression were used.</t>

</section>
<section anchor="middlebox-compatibility" title="Middlebox Compatibility">

<t>It’s been observed that a significant number of middleboxes intercept and try
to validate the Certificate message exchanged during a TLS handshake. This
means that middleboxes that don’t understand the CompressedCertificate message
might misbehave and drop connections that adopt certificate compression.
Because of that, the extension is only supported in the versions of TLS where
the certificate message is encrypted in a way that prevents middleboxes from
intercepting it, that is, TLS version 1.3 <xref target="RFC8446"></xref> and higher.</t>

</section>
<section anchor="iana-considerations" title="IANA Considerations">

<section anchor="update-of-the-tls-extensiontype-registry" title="Update of the TLS ExtensionType Registry">

<t>Create an entry, compress_certificate(27), in the existing registry for
ExtensionType (defined in <xref target="RFC8446"></xref>), with “TLS 1.3” column values
being set to “CH, CR”, and “Recommended” column being set to “Yes”.</t>

</section>
<section anchor="update-of-the-tls-handshaketype-registry" title="Update of the TLS HandshakeType Registry">

<t>Create an entry, compressed_certificate(25), in the existing registry for
HandshakeType (defined in <xref target="RFC8446"></xref>).</t>

</section>
<section anchor="registry-for-compression-algorithms" title="Registry for Compression Algorithms">

<t>This document establishes a registry of compression algorithms supported for
compressing the Certificate message, titled “Certificate Compression Algorithm
IDs”, under the existing “Transport Layer Security (TLS) Extensions” heading.</t>

<t>The entries in the registry are:</t>

<texttable>
      <ttcol align='left'>Algorithm Number</ttcol>
      <ttcol align='left'>Description</ttcol>
      <c>0</c>
      <c>Reserved</c>
      <c>1</c>
      <c>zlib</c>
      <c>2</c>
      <c>brotli</c>
      <c>16384 to 65535</c>
      <c>Reserved for Experimental Use</c>
</texttable>

<t>The values in this registry shall be allocated under “IETF Review” policy for
values strictly smaller than 256, under “Specification Required” policy for
values 256-16383, and under “Experimental Use” otherwise (see <xref target="RFC8126"></xref> for the
definition of relevant policies).  Experimental Use extensions can be used both
on private networks and over the open Internet.</t>

<t>The procedures for requesting values in the Specification Required space are
specified in <xref target="RFC8447"></xref>.</t>

</section>
</section>


  </middle>

  <back>

    <references title='Normative References'>





<reference  anchor="RFC1950" target='https://www.rfc-editor.org/info/rfc1950'>
<front>
<title>ZLIB Compressed Data Format Specification version 3.3</title>
<author initials='P.' surname='Deutsch' fullname='P. Deutsch'><organization /></author>
<author initials='J-L.' surname='Gailly' fullname='J-L. Gailly'><organization /></author>
<date year='1996' month='May' />
<abstract><t>This specification defines a lossless compressed data format.  This memo provides information for the Internet community.  This memo does not specify an Internet standard of any kind.</t></abstract>
</front>
<seriesInfo name='RFC' value='1950'/>
<seriesInfo name='DOI' value='10.17487/RFC1950'/>
</reference>



<reference  anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'>
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1997' month='March' />
<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="RFC7250" target='https://www.rfc-editor.org/info/rfc7250'>
<front>
<title>Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)</title>
<author initials='P.' surname='Wouters' fullname='P. Wouters' role='editor'><organization /></author>
<author initials='H.' surname='Tschofenig' fullname='H. Tschofenig' role='editor'><organization /></author>
<author initials='J.' surname='Gilmore' fullname='J. Gilmore'><organization /></author>
<author initials='S.' surname='Weiler' fullname='S. Weiler'><organization /></author>
<author initials='T.' surname='Kivinen' fullname='T. Kivinen'><organization /></author>
<date year='2014' month='June' />
<abstract><t>This document specifies a new certificate type and two TLS extensions for exchanging raw public keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS).  The new certificate type allows raw public keys to be used for authentication.</t></abstract>
</front>
<seriesInfo name='RFC' value='7250'/>
<seriesInfo name='DOI' value='10.17487/RFC7250'/>
</reference>



<reference  anchor="RFC7932" target='https://www.rfc-editor.org/info/rfc7932'>
<front>
<title>Brotli Compressed Data Format</title>
<author initials='J.' surname='Alakuijala' fullname='J. Alakuijala'><organization /></author>
<author initials='Z.' surname='Szabadka' fullname='Z. Szabadka'><organization /></author>
<date year='2016' month='July' />
<abstract><t>This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods.</t></abstract>
</front>
<seriesInfo name='RFC' value='7932'/>
<seriesInfo name='DOI' value='10.17487/RFC7932'/>
</reference>



<reference  anchor="RFC7924" target='https://www.rfc-editor.org/info/rfc7924'>
<front>
<title>Transport Layer Security (TLS) Cached Information Extension</title>
<author initials='S.' surname='Santesson' fullname='S. Santesson'><organization /></author>
<author initials='H.' surname='Tschofenig' fullname='H. Tschofenig'><organization /></author>
<date year='2016' month='July' />
<abstract><t>Transport Layer Security (TLS) handshakes often include fairly static information, such as the server certificate and a list of trusted certification authorities (CAs).  This information can be of considerable size, particularly if the server certificate is bundled with a complete certificate chain (i.e., the certificates of intermediate CAs up to the root CA).</t><t>This document defines an extension that allows a TLS client to inform a server of cached information, thereby enabling the server to omit already available information.</t></abstract>
</front>
<seriesInfo name='RFC' value='7924'/>
<seriesInfo name='DOI' value='10.17487/RFC7924'/>
</reference>



<reference  anchor="RFC8126" target='https://www.rfc-editor.org/info/rfc8126'>
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials='M.' surname='Cotton' fullname='M. Cotton'><organization /></author>
<author initials='B.' surname='Leiba' fullname='B. Leiba'><organization /></author>
<author initials='T.' surname='Narten' fullname='T. Narten'><organization /></author>
<date year='2017' month='June' />
<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="RFC8174" target='https://www.rfc-editor.org/info/rfc8174'>
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
<author initials='B.' surname='Leiba' fullname='B. Leiba'><organization /></author>
<date year='2017' month='May' />
<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>



<reference  anchor="RFC8446" target='https://www.rfc-editor.org/info/rfc8446'>
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
<author initials='E.' surname='Rescorla' fullname='E. Rescorla'><organization /></author>
<date year='2018' month='August' />
<abstract><t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol.  TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t><t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961.  This document also specifies new requirements for TLS 1.2 implementations.</t></abstract>
</front>
<seriesInfo name='RFC' value='8446'/>
<seriesInfo name='DOI' value='10.17487/RFC8446'/>
</reference>



<reference  anchor="RFC8447" target='https://www.rfc-editor.org/info/rfc8447'>
<front>
<title>IANA Registry Updates for TLS and DTLS</title>
<author initials='J.' surname='Salowey' fullname='J. Salowey'><organization /></author>
<author initials='S.' surname='Turner' fullname='S. Turner'><organization /></author>
<date year='2018' month='August' />
<abstract><t>This document describes a number of changes to TLS and DTLS IANA registries that range from adding notes to the registry all the way to changing the registration policy.  These changes were mostly motivated by WG review of the TLS- and DTLS-related registries undertaken as part of the TLS 1.3 development process.</t><t>This document updates the following RFCs: 3749, 5077, 4680, 5246, 5705, 5878, 6520, and 7301.</t></abstract>
</front>
<seriesInfo name='RFC' value='8447'/>
<seriesInfo name='DOI' value='10.17487/RFC8447'/>
</reference>




    </references>



<section anchor="acknowledgements" title="Acknowledgements">

<t>Certificate compression was originally introduced in the QUIC Crypto protocol,
designed by Adam Langley and Wan-Teh Chang.</t>

<t>This document has benefited from contributions and suggestions from David
Benjamin, Ryan Hamilton, Ilari Liusvaara, Piotr Sikora, Ian Swett, Martin
Thomson, Sean Turner and many others.</t>

</section>


  </back>

<!-- ##markdown-source:
H4sIAHO1tFsAA5VZ224bNxq+51MQ6kVtQBIqxbFbZ7Go42QbA3bS2k6LbpAN
qBlKYjMznCUpyWqTog+y+3J9kv1+kjNDWbLc9Y3nxP/4/UcNBgPmlCvkKb+9
vOHn0jg1VZlwkp/rsjbSWqUrluusEiU+yo2YuoGSbjpwhR1k3feDrPt+UOCB
dUxMJkYu95OmBzNt1qfcupwJI8Upv5HZwii3ZittPs6MXtSeBmPWiSr/IApd
QZa1tKxWp/yd01mfW22ckVOLq3UZLiB1KepaVbP3jImFm2tzyviAcfypyp7y
syH/bi5zVSn/LKh4VkAysDF646U2s1N+XuhFPi0gZZ9fVNnQv5GlUMUpF+25
b7P2syGsssHyxyH/UVhVKLlMeP6oMqfN5hvP8DutZ4VM2Szpm+Xy25l/4+mz
SptSOLWUUI9f/+N89M3Tr+LleDT6Jl6ejNunJ988GbeX46N4+fVofNxenrRP
j46Ou8uTU8ZUNe0YssFgwMXEOiMyx9hF5b09hyHsXHyUcEMCEp7NBczA9dTJ
iju854uaubnkpfhFk8vxitP9ZA0EcRCtbKmck/mQsdu5suTURSkrx3NpM6Mm
+GquV7uYZKLiE9xFsMmcO82NzBeZJBZMlHoBOmCYCydSXhzSc7HUKgesSsmB
QDxwRtV2GBQuVZ7DL+wLwMAZDZqOwEzqa5NLk7CiWKiytaepIIpeSl5L401Y
4b1yjaQLK6eLojvqDXNPSnkH7aoZZMwRItWMi017Q7530avvExMJXko6qGwJ
3YUDWgu9oucZAAf6XmNupVkG4b32rLUJcUpMjIMFIjVfczCFsMA2KHApDKiZ
Tpo+nywcNEQCkbb60vG5LGq+mpPzoVvknemqkpmznm8jA+zjv5kqYx13Cm4A
1ZZQw38uYM6PlV4VMp/JBj2Bxpd2GxZ7YLRlo5VeFHmw1KbykHMiWQKs6At4
r0igPyR8vNZOEDZEgbRXLcESN5akgNxyDSYmt7x39fbmttcP//nrN/76+uUP
by+uX76g65tXZ5eX7UXzxc2rN28v8Z7Fq+7k+Zurq5evX4TDeMrvPbo6+xn/
yOu9N9/fXrx5fXbZIy86GIe1xoFvg7J45aSBuj46bGs17/nn59/z0RH/7beY
bz5/DteURD5/ZuTuwEpXxZqHW3gJIVHXgIwHDwyXiVo5USBjgIFFUFeAi5HB
iqgRTgmPw4cqSXCsvEO40T3HjWdoF3WN4gBZV8rNfbiMhk+8QJVcSfOMq2l8
Okb0NihmOF9FtjL3EiNupbHc+0jNkHWlt1fHcwe6pqry2AKrRDa3riU/aBD0
IUHXwfjk8LAPK6lszrrE4JOXBVPgyCO8VSqpuzzkZdsGT2IqVlJ5mnl/NqoM
Of8J3pAUb0hDENyS0JN1Gp2CpD/3168kYoFHQqzT5uBdrBPv+1S7CeH8aAhz
QhGiW+VN4HSSk4xpCMWwT+Nsv3jxAInHEj2v5b8X6D34Y9I92ZKO3ZMurRxN
pkqlY+z5miTKQxre5cxOin6UuaLikBikc4Znv5GvEseKYkblcV7aaImVKgri
CwJAhxc3l8mJoU8wvZb/B6oePWRTiZTms+RGrISsgkTsBEVjatAkxM46KZai
WFD1//3330N3Ui1K/pu/pL9fCzU5GB322wcTo12hDsbJo4Pjp0+fPD3095/5
IxyfMf8d2gyU2oTRI8cSw/1tNByO//X1YPT3Z3+NpX3mtSNDItApG2jgh0AX
4iCJZqoWCSbxrQEMlQlhi6qCHCqyjz6VnXeoSjPZVYwqdjFtIYFaYluw5IEN
3B8xalOE9Nt4qFq0Ise3EUY0FUHa4K7WAbQp/xjV1hMgnNKJMpQEj68SsPEY
7RTYcZ4fGFkXIvPY3MxAzSeHw1D99tNRPouVodxMtW9XErxtAeGvI+FZd2aB
sjY+4ouqC/UPhaxmbp58pGuBlJJkgzTCP0R5A7rGRym8dukXMdUKwzDZUJfX
itnk+tRxaVpAUtw84KsRigRmIvIQ9weSfFEo60KdbmD1pX0kWcFBO0wSRQ03
Tae1y3U6trVwYUoGkgPbmB+R6/hmtgrBU8sMpCBrZEG9HoLOYThw2TzolbkF
KmD4wOdUkKqFweBgZCbVssGdqpCh0L83MnkriQmldm/Q0HISa98UBEK9idhw
bo+GOuNgjv3Oj5ZJ6sVE5+s9Juo37rAY/2LVJpyjU+ax7fQzXYH2ZUKOaeii
gd1gtVEb2m6DBqKgURijIrP9SsTaQC1fRo2qCagJFYrxXWoM22zV+W63ZIAC
lQTvseohq7AGyokhG+/wf15ePN9NvB8aUlLdw/xdnIDfD/8P6UJ96j+IaRKN
PSDac3/2AdrbstHw/b4zXcAtVYO9+RCtIIUCROgiJ7alLEFzY0KnTYUAWnX4
3oPuKEnE4Z7IVjT4IX4h7cLGUGOh8GxAyre31EH5QrT9qs00NlhkDG8FVaDW
ovBtfsMo4Z0YHwO+wwDoK2qzLqIByyo0WCLOWGeUazYzzX4Pk+UwoWeBBwXk
lBIZhgS0u0hleXS7XpAn/FCcpjff+6/EOg4LwngbiVBLOYwUeNKw4ufWNgPY
RgMwr0k2qsM2DEkhHfjvVViuNKkByt8oyrU7lh9+clvXeEY5hESEIySNYGhV
wWIQ2wXaP8FTjB6h9Bj0KVbZoIBwDk0LWbBJxF4K6hKNLrgO7cbadyhLlVNi
nhoxo8HHMvVgmPdxgSnboyf0TesG3YUUH3m7XiJZJ2Rqj/GEECaAUudqum6y
PToOGlDvXGwtVFkXkuQISOBxOp6EPQ6tm2SpzRogJs/7fUSCkojrvfH4ACMP
okKVKvaD6td2J9EhOw3g4C+EK9tMVGnhbMtdRNJ6TzVT0xCTxFjeZVLmNpjZ
C0UYBYDgpZIEgfTawrWj45OTk/Ho2JeLKH4oyhtmbyKFiLfCbJvg7OdIGEhr
TEGNq2Xo4Wi7NBehZX5GgJ5opKdMWGn7qW51Xay7+AhkQjxWmqWZlmLTN00+
FVz5vdxE3/lsCokmqqBFMrtw6HomEo7WEw/92E4LP1R7DdExY4iZQEJ4rGwI
+fKJNJLJOmzJnFkzFEXfXpBVHsonj27qfLpgFAvRRSlP/yDXtOpa0MzoN9/8
0fablWo2J0p2In2w0qkcSSXBSCQucl27hwbOIXsuM0GTpUevcCEj7FuuxIBH
UgiJXYelyoqmp63ZNknqyKtmXUcKgtJnkA+i0LbMbphlanTJWn94DHvRPL76
nmEUwO942snf22EO20jjcXJx9vpsq1x88QV/W3ufxpAlci8blW+pcF3LGdpp
IICdG0lf0tYT6RAp/6FlTtvryTscJZFNJOJXIJv0D+71Cl54WgdREe/F1VUP
vIpFWYUh3LJQiax0NDf0zl/1+fl1s9y7plxT0tohb49tfv+ztL3hA8q/asD6
V5XfbC0Pxk8fU3+Tw271g3TXybF078e7gf3+9k0iaiaYf+Z+A9fyhYIP7FY6
NKfbqT2zLLBHv57B0A9sJTvp2MULC6/4aN40SO+W1ux+7XQp1njbNjQHcMJh
B0Hb43M0PTgTyw9ZX3UNfqshqj9m5U8dc/46ZLZP/IXf3Na+WGz/fWKfTgf3
/3Y82nwPTl9tUYLDYqLd+UeHRtuHaErYfaA5NN4+FJr3fYdGx0++PiK4+53T
pniEp5d3aICUr2IFf4u09ykYOERYsxjvDAzIFgV1i/TrQNjOBMf2Ll7e/gO0
l0querzWhcoC0CMlnFaZo8RJLVxTDcdPjxtk9G5CDxD6RH4d90i7aOHUgBR7
EmI9nP/zj//cV+bPP/7LUWWlWSlodmClDME1GiMxxlUx85GnPE/Eh5GFXFJF
9FwBsUO0DltGStr4dFNNJZ2BTm3UksKhko5+yA2rJd81EljR6Fb065k0eB/x
7HtvlEsZVtgm7HIpRlJHSL7bRmifBLphgJ91jVSXSU7exx/vaBVHReAsa384
Cj1ruvbcSBErtB4IpJmqfDut4m9+XdX74e3FOT+nOqZJCaeRavuwKTUXZJE1
P8tFifCuZoUMvwX+JKrBrZzzc+oStn44oM3fRFZwis9GKHuh71aTRajhfk23
mM3IPnTvP3kh0IejdFe/UIPX59druOUVrgtHo89FIYzil2phl0IY0effK+2Q
btRHTXcX+PhmJR0q6pWAISrIpEtLJ2/QpfDbBVwVNowl9f0eU3bI/gd2aT/x
RSAAAA==

-->

</rfc>

