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


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="pre5378Trust200902" docName="draft-josefsson-ssh-rfc4716-00" category="std" consensus="true" submissionType="IETF" obsoletes="4716" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="SSH Public Key File Format">The Secure Shell (SSH) Public Key File Format</title>

    <author fullname="Joseph Galbraith">
      <organization>VanDyke Software</organization>
      <address>
        <email>galb@vandyke.com</email>
      </address>
    </author>
    <author fullname="Rodney Thayer">
      <organization>Canola &amp; Jones</organization>
      <address>
        <email>rodney@canola-jones.com</email>
      </address>
    </author>
    <author fullname="Simon Josefsson" role="editor">
      <organization></organization>
      <address>
        <email>simon@josefsson.org</email>
      </address>
    </author>

    <date year="2026" month="November" day="17"/>

    <area>int</area>
    
    <keyword>Internet-Draft</keyword>

    <abstract>


<?line 43?>

<t>This document formally documents an existing public key file format in
use for exchanging public keys between different Secure Shell (SSH)
implementations.</t>

<t>In addition, this document defines a standard textual representation
for SSH public key fingerprints.</t>



    </abstract>

    <note title="About This Document" removeInRFC="true">
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-josefsson-ssh-rfc4716/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://gitlab.com/jas/ietf-ssh-rfc4716bis"/>.</t>
    </note>


  </front>

  <middle>


<?line 52?>

<section anchor="introduction"><name>Introduction</name>

<t>The SSH protocol supports the use of public/private key pairs in order
to perform authentication based on public key cryptography.  However,
in order to use public key authentication in the SSH protocol, public
keys must first be exchanged between client and server.</t>

<t>This document formally describes an existing public key file format
that can be used with any of the common existing file transfer
mechanisms in order to exchange public keys.</t>

<t>The SSH protocol also uses public/private key pairs to authenticate
the server.  In this scenario, it is important to verify that the
public key provided by the server is indeed the server's public key.
This document describes a mechanism for creating a short text string
that uniquely represents a particular public key, called
fingerprinting.</t>

</section>
<section anchor="conventions"><name>Conventions Used in This Document</name>

<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref target="RFC2119"></xref>.</t>

</section>
<section anchor="key-file-format"><name>Key File Format</name>

<t>In order to implement public key authentication, SSH implementations
must share public key files between the client and the server in order
to interoperate.</t>

<t>A key file is a text file, containing a sequence of lines.  Each line
in the file MUST NOT be longer than 72 8-bit bytes excluding line
termination characters.</t>

<section anchor="line-termination-characters"><name>Line Termination Characters</name>

<t>Implementations SHOULD generate public key files using their system's
local text file representation.</t>

<t>In the event that public key files are not transferred as text files,
implementations SHOULD be prepared to read files using any of the
common line termination sequence, &lt;CR&gt;, &lt;LF&gt;, or &lt;CR&gt;&lt;LF&gt;.</t>

</section>
<section anchor="begin-and-end-markers"><name>Begin and End Markers</name>

<t>The first line of a conforming key file MUST be a begin marker, which
is the literal text:</t>

<figure><artwork><![CDATA[
---- BEGIN SSH2 PUBLIC KEY ----
]]></artwork></figure>

<t>The last line of a conforming key file MUST be an end marker, which is
the literal text:</t>

<figure><artwork><![CDATA[
---- END SSH2 PUBLIC KEY ----
]]></artwork></figure>

</section>
<section anchor="key-file-header"><name>Key File Header</name>

<t>The key file header section consists of multiple RFC822-style header
fields.  Each field is a line of the following format:</t>

<figure><artwork><![CDATA[
Header-tag ':' ' ' Header-value
]]></artwork></figure>

<t>The Header-tag MUST NOT be more than 64 8-bit bytes and is case-
insensitive.  The Header-value MUST NOT be more than 1024 8-bit bytes.
Each line in the header MUST NOT be more than 72 8-bit bytes.</t>

<t>A line is continued if the last character in the line is a '\'.  If
the last character of a line is a '\', then the logical contents of
the line are formed by removing the '\' and the line termination
characters, and appending the contents of the next line.</t>

<t>The Header-tag MUST be encoded in US-ASCII.  The Header-value MUST be
encoded in UTF-8 <xref target="RFC3629"></xref>.</t>

<t>A line that is not a continuation line that has no ':' in it is the
first line of the base64-encoded body.  (See Section 3.4.)</t>

<t>The space of header-tags is managed as described in Section 5.</t>

<t>Compliant implementations MUST ignore headers with unrecognized
header-tags.  Implementations SHOULD preserve such unrecognized
headers when manipulating the key file.</t>

<section anchor="subject-header"><name>Subject Header</name>

<t>This field is used to store the login-name that the key was generated
under.  For example:</t>

<figure><artwork><![CDATA[
Subject: user
]]></artwork></figure>

</section>
<section anchor="comment-header"><name>Comment Header</name>

<t>The comment header contains a user-specified comment.  The comment
SHOULD be displayed when using the key.</t>

<t>It is suggested that this field default to user@hostname for the user
and machine used to generate the key.  For example:</t>

<figure><artwork><![CDATA[
Comment: user@example.com
]]></artwork></figure>

<t>Currently, common practice is to quote the Header-value of the Comment
by prefixing and suffixing it with '"' characters, and some existing
implementations fail if these quotation marks are omitted.</t>

<t>Compliant implementations MUST function correctly if the quotation
marks are omitted.</t>

<t>Implementations MAY include the quotation marks.  If the first and
last characters of the Header-value are matching quotation marks,
implementations SHOULD remove them before using the value.</t>

</section>
<section anchor="private-use-headers"><name>Private Use Headers</name>

<t>Headers with header-tags beginning with "x-" are reserved for private
use.</t>

</section>
</section>
<section anchor="public-key-file-body"><name>Public Key File Body</name>

<t>The body of a public key file is the base64 encoded (<xref target="RFC2045"></xref>) public
key data as specified by <xref target="RFC4253"></xref>, Section 6.6:</t>

<figure><artwork><![CDATA[
      string    certificate or public key format identifier
      byte[n]   key/certificate data
]]></artwork></figure>

<t>As with all other lines, each line in the body MUST NOT be longer than
72 8-bit bytes excluding line termination characters.</t>

</section>
<section anchor="differences-with-rfc1421-pem-formats"><name>Differences with RFC 1421 PEM Formats</name>

<t>Implementers should take care to notice that while the format is
superficially similar to those specified by PEM <xref target="RFC1421"></xref> and OpenPGP
<xref target="RFC2440"></xref>, it is not identical; most notably:</t>

<figure><artwork><![CDATA[
o  The other specifications use different BEGIN/END delimiters (five
   dashes, no space rather than four dashes and a space).

o  There is no blank line before the start of the base64-encoded
   contents.

o  There is no Cyclic Redundancy Check (CRC) at the end of the
   base64-encoded block.

o  Header continuation uses a backslash at the end of the continued
   line rather than whitespace at the start of the next line.
]]></artwork></figure>

</section>
<section anchor="examples"><name>Examples</name>

<t>The following are some examples of public key files that are compliant
(note that the examples all wrap before 72 bytes to meet IETF document
requirements; however, they are still compliant.)</t>

<figure><artwork><![CDATA[
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "1024-bit RSA, converted from OpenSSH by me@example.com"
x-command: /home/me/bin/lock-in-guest.sh
AAAAB3NzaC1yc2EAAAABIwAAAIEA1on8gxCGJJWSRT4uOrR13mUaUk0hRf4RzxSZ1zRb
YYFw8pfGesIFoEuVth4HKyF8k1y4mRUnYHP1XNMNMJl1JcEArC2asV8sHf6zSPVffozZ
5TT4SfsUu/iKy9lUcCfXzwre4WWZSXXcPff+EHtWshahu3WzBdnGxm5Xoi89zcE=
---- END SSH2 PUBLIC KEY ----
]]></artwork></figure>

<figure><artwork><![CDATA[
---- BEGIN SSH2 PUBLIC KEY ----
Comment: This is my public key for use on \
servers which I don't like.
AAAAB3NzaC1kc3MAAACBAPY8ZOHY2yFSJA6XYC9HRwNHxaehvx5wOJ0rzZdzoSOXxbET
W6ToHv8D1UJ/z+zHo9Fiko5XybZnDIaBDHtblQ+Yp7StxyltHnXF1YLfKD1G4T6JYrdH
YI14Om1eg9e4NnCRleaqoZPF3UGfZia6bXrGTQf3gJq2e7Yisk/gF+1VAAAAFQDb8D5c
vwHWTZDPfX0D2s9Rd7NBvQAAAIEAlN92+Bb7D4KLYk3IwRbXblwXdkPggA4pfdtW9vGf
J0/RHd+NjB4eo1D+0dix6tXwYGN7PKS5R/FXPNwxHPapcj9uL1Jn2AWQ2dsknf+i/FAA
vioUPkmdMc0zuWoSOEsSNhVDtX3WdvVcGcBq9cetzrtOKWOocJmJ80qadxTRHtUAAACB
AN7CY+KKv1gHpRzFwdQm7HK9bb1LAo2KwaoXnadFgeptNBQeSXG1vO+JsvphVMBJc9HS
n24VYtYtsMu74qXviYjziVucWKjjKEb11juqnF0GDlB3VVmxHLmxnAz643WK42Z7dLM5
sY29ouezv4Xz2PuMch5VGPP+CDqzCM4loWgV
---- END SSH2 PUBLIC KEY ----
]]></artwork></figure>

<figure><artwork><![CDATA[
---- BEGIN SSH2 PUBLIC KEY ----
Comment: DSA Public Key for use with MyIsp
AAAAB3NzaC1kc3MAAACBAPY8ZOHY2yFSJA6XYC9HRwNHxaehvx5wOJ0rzZdzoSOXxbET
W6ToHv8D1UJ/z+zHo9Fiko5XybZnDIaBDHtblQ+Yp7StxyltHnXF1YLfKD1G4T6JYrdH
YI14Om1eg9e4NnCRleaqoZPF3UGfZia6bXrGTQf3gJq2e7Yisk/gF+1VAAAAFQDb8D5c
vwHWTZDPfX0D2s9Rd7NBvQAAAIEAlN92+Bb7D4KLYk3IwRbXblwXdkPggA4pfdtW9vGf
J0/RHd+NjB4eo1D+0dix6tXwYGN7PKS5R/FXPNwxHPapcj9uL1Jn2AWQ2dsknf+i/FAA
vioUPkmdMc0zuWoSOEsSNhVDtX3WdvVcGcBq9cetzrtOKWOocJmJ80qadxTRHtUAAACB
AN7CY+KKv1gHpRzFwdQm7HK9bb1LAo2KwaoXnadFgeptNBQeSXG1vO+JsvphVMBJc9HS
n24VYtYtsMu74qXviYjziVucWKjjKEb11juqnF0GDlB3VVmxHLmxnAz643WK42Z7dLM5
sY29ouezv4Xz2PuMch5VGPP+CDqzCM4loWgV
---- END SSH2 PUBLIC KEY ----
]]></artwork></figure>

<figure><artwork><![CDATA[
---- BEGIN SSH2 PUBLIC KEY ----
Subject: me
Comment: 1024-bit rsa, created by me@example.com Mon Jan 15 \
08:31:24 2001
AAAAB3NzaC1yc2EAAAABJQAAAIEAiPWx6WM4lhHNedGfBpPJNPpZ7yKu+dnn1SJejgt4
596k6YjzGGphH2TUxwKzxcKDKKezwkpfnxPkSMkuEspGRt/aZZ9wa++Oi7Qkr8prgHc4
soW6NUlfDzpvZK2H5E7eQaSeP3SAwGmQKUFHCddNaP0L+hM7zhFNzjFvpaMgJw0=
---- END SSH2 PUBLIC KEY ----
]]></artwork></figure>

</section>
</section>
<section anchor="public-key-fingerprints"><name>Public Key Fingerprints</name>

<t>The security of the SSH protocols relies on the verification of public
host keys.  Since public keys tend to be very large, it is difficult
for a human to verify an entire host key.  Even with a Public Key
Infrastructure (PKI) in place, it is useful to have a standard for
exchanging short fingerprints of public keys.</t>

<t>This section formally describes the method of generating public key
fingerprints that is in common use in the SSH community.</t>

<t>The fingerprint of a public key consists of the output of the MD5
message-digest algorithm <xref target="RFC1321"></xref>.  The input to the algorithm is the
public key data as specified by <xref target="RFC4253"></xref>.  (This is the same data
that is base64 encoded to form the body of the public key file.)</t>

<t>The output of the algorithm is presented to the user as a sequence of
16 octets printed as hexadecimal with lowercase letters and separated
by colons.</t>

<t>For example: "c1:b1:30:29:d7:b8:de:6c:97:77:10:d7:46:41:63:87"</t>

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

<t>Section 3.3 defines a new namespace of "Header-tags".  These are
US-ASCII strings of maximum length 64 characters and are
case-insensitive.</t>

<t>IANA has created and maintains a registry of these header-tags.  The
registry maps each header-tag to a reference defining the header.</t>

<t>The initial contents of the registry are as follows:</t>

<figure><artwork><![CDATA[
   subject defined in Section 3.3.1

   comment defined in Section 3.3.2
]]></artwork></figure>

<t>Header-tags beginning with "x-" are reserved for private use, as
defined in <xref target="RFC2434"></xref>.</t>

<t>All other allocations are to be made by IETF consensus, as defined in
<xref target="RFC2434"></xref>.</t>

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

<t>The file format described by this document provides no mechanism to
verify the integrity or otherwise detect tampering with the data
stored in such files.  Given the potential of adversarial tampering
with this data, system-specific measures (e.g., Access Control Lists,
UNIX permissions, other Discretionary and/or Mandatory Access
Controls) SHOULD be used to protect these files.  Also, if the
contents of these files are transferred it SHOULD be done over a
trusted channel.</t>

<t>The header data allowed by this file format could contain an unlimited
range of information.  While in many environments the information
conveyed by this header data may be considered innocuous public
information, it may constitute a channel through which information
about a user, a key, or its use may be disclosed intentionally or
otherwise (e.g., "Comment: Mary E. Jones, 123 Main St, Home
Phone:...").  The presence and use of this header data SHOULD be
reviewed by sites that deploy this file format.</t>

<t>The public key fingerprint method presented here relies on the MD5
one-way hash function, which is known to have certain weaknesses
regarding its collision resistance; however, the particular use made
of MD5 here depends solely on its 2nd-preimage resistance, not on its
collision resistance.</t>

<t>MD5 is used here for historical reasons.</t>

</section>


  </middle>

  <back>


    <references title='Normative References' anchor="sec-normative-references">



<reference anchor="RFC1321">
  <front>
    <title>The MD5 Message-Digest Algorithm</title>
    <author fullname="R. Rivest" initials="R." surname="Rivest"/>
    <date month="April" year="1992"/>
    <abstract>
      <t>This document describes the MD5 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="1321"/>
  <seriesInfo name="DOI" value="10.17487/RFC1321"/>
</reference>
<reference anchor="RFC2045">
  <front>
    <title>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
    <author fullname="N. Freed" initials="N." surname="Freed"/>
    <author fullname="N. Borenstein" initials="N." surname="Borenstein"/>
    <date month="November" year="1996"/>
    <abstract>
      <t>This initial document specifies the various headers used to describe the structure of MIME messages. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2045"/>
  <seriesInfo name="DOI" value="10.17487/RFC2045"/>
</reference>
<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="RFC3629">
  <front>
    <title>UTF-8, a transformation format of ISO 10646</title>
    <author fullname="F. Yergeau" initials="F." surname="Yergeau"/>
    <date month="November" year="2003"/>
    <abstract>
      <t>ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="63"/>
  <seriesInfo name="RFC" value="3629"/>
  <seriesInfo name="DOI" value="10.17487/RFC3629"/>
</reference>
<reference anchor="RFC4253">
  <front>
    <title>The Secure Shell (SSH) Transport Layer Protocol</title>
    <author fullname="T. Ylonen" initials="T." surname="Ylonen"/>
    <author fullname="C. Lonvick" initials="C." role="editor" surname="Lonvick"/>
    <date month="January" year="2006"/>
    <abstract>
      <t>The Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.</t>
      <t>This document describes the SSH transport layer protocol, which typically runs on top of TCP/IP. The protocol can be used as a basis for a number of secure network services. It provides strong encryption, server authentication, and integrity protection. It may also provide compression.</t>
      <t>Key exchange method, public key algorithm, symmetric encryption algorithm, message authentication algorithm, and hash algorithm are all negotiated.</t>
      <t>This document also describes the Diffie-Hellman key exchange method and the minimal set of algorithms that are needed to implement the SSH transport layer protocol. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4253"/>
  <seriesInfo name="DOI" value="10.17487/RFC4253"/>
</reference>
<reference anchor="RFC2434">
  <front>
    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
    <author fullname="T. Narten" initials="T." surname="Narten"/>
    <author fullname="H. Alvestrand" initials="H." surname="Alvestrand"/>
    <date month="October" year="1998"/>
    <abstract>
      <t>This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2434"/>
  <seriesInfo name="DOI" value="10.17487/RFC2434"/>
</reference>



    </references>

    <references title='Informative References' anchor="sec-informative-references">



<reference anchor="RFC1421">
  <front>
    <title>Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures</title>
    <author fullname="J. Linn" initials="J." surname="Linn"/>
    <date month="February" year="1993"/>
    <abstract>
      <t>This document defines message encryption and authentication procedures, in order to provide privacy-enhanced mail (PEM) services for electronic mail transfer in the Internet. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="1421"/>
  <seriesInfo name="DOI" value="10.17487/RFC1421"/>
</reference>
<reference anchor="RFC2440">
  <front>
    <title>OpenPGP Message Format</title>
    <author fullname="J. Callas" initials="J." surname="Callas"/>
    <author fullname="L. Donnerhacke" initials="L." surname="Donnerhacke"/>
    <author fullname="H. Finney" initials="H." surname="Finney"/>
    <author fullname="R. Thayer" initials="R." surname="Thayer"/>
    <date month="November" year="1998"/>
    <abstract>
      <t>This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2440"/>
  <seriesInfo name="DOI" value="10.17487/RFC2440"/>
</reference>



    </references>



  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA+06a3PiuJbf9StU6art7kpIwiMv7u7WEAghIRAa8u7p2hK2
wAp+tSVDYOre337PkWRjSHp2dms/7IfbM93YsnR0dN4PlUolooTyeZ3u3Hmc
jriTJvDjcd+nX0ajzlc6SMe+cGiXL2lb+Jy2oyRgaoew8Tjhc1gHs345yWGK
T6NkWadSucSNnJAFsJebsIkqvUaST6SMwpKUXimZOLWT8nHp8JCIOKnTOOFH
1ZPTuySVqnJ4eHZYIdFYRj5XXNYpTiUs4axORajIjC8XUeLW6VWoeBJyVWrh
FkSm40BIKaLwbhnDxlcXd20y52HK64RSpcd2HqNkJsIpvUyiNN6B8YTHEYx7
SsWyfnAwBQKx8b4TBQevTB4IriZFjMdC7hCpWOj+F/OjECAuuSSx0DtETp2q
JOXwLKNEJXDg9cAyKLyzVHlRAotK8IlOUt83tLoGKsUevWT+OGFCefiVB0z4
dTqFsd/msPFyxhE9/BQl0zp9YGELxugomqgFUOkd0GHkhsCrO48teVKAmOjx
3xwWRj4DBoVcbgBu6g/03wAr+PQO7EgEUagx1nwtAJb45bec4/sADb8mEYoe
d4WKEhJqoRFzzZthu1muVsr2sXJYO8oey+Uz+1g9rmSPtcpRNZtQq9bqRIST
bXC1Nbha7bBOSKlUomwsVcIcRcidJyQFEU0DHiqqV/v+Mh+RlIWUvwmpUFZi
I/Agd3SCAm82A1kkqdRvMNXxWDjdnCzpmKsF5yF1xWTCE9zpvc4REcQ+x00B
/yiU+4RchZS5QCZ43aNqA1OXTwQwgzKqhZAlLlX8TaXMR0FOuMzgEEQLtXUD
+XDKkzgBJcJtkCKBcF2fE/IJlQkEInVwMf3jkyi8/h3pxQ20JAIxj3wq0zgG
GZeAH6dIhmhitzqADeZgCvSWMROJBEqBRLkgfCqiMU+QfhRVAJAVjkaXjpnk
LoWHAr5OsoxVNE1Y7C33Ke1ECz7nyR7JwIHG6a0LS7agwky1hfmenU40hwIw
OECXBP4d84yNgEjGOccXSHYgNZU8gd33fy07XDqJGPO/IjtEeSBAoHm4a4on
X4C2w8Il0hFRBkVE9crh6MUgvKEESSIBR0SFDNa0RWJk+BeFcP8D5jFfasrJ
X7MMoBVoyQniZClAQVaMWEqHhywR0R4VoA6AS4AywYAqsBymismS6pPCalKg
BCAyFy6SeUnXgDWE0OUwvh78LAuH2d+ifYHkNCeJVkgHvIWmGygKWFqltQR0
BmR/aoifhuJnyoFvud4glJglcODUZ0lh2z3glO9zlxQUCJ72UW2aUThHIoHm
0ntkJPBDI9nKkPzjk7OeY1UJiYA+TNKd3v3obmfP/NL+rX4eXny7vxpetPB5
1Gnc3OQPZgaBl9v7G/sdn9Yrm7e93kW/ZRb3Gs/wg9K7czu4u7rtN252jFII
SXIygtNAhoEoCvSoQA4FB2Eyp68+1Xdrj3/oc295fzglnKmEUloyIv53bcdy
0cyt3K+1dU8L6ZY5JFpDpYc4bunS2r5qhVlralGkCpZHHy4C+wPyDGdorJVS
IOu1hOArsDuC7UVo5YeDnISOtnA+Gl9QgAvmePqFWAujwWQsREpCcDDFk4NM
0pMKPS2NQUXGS4hnUEv91EXgGgIgFYjQ2CsQYfRPPEG1/fSJ3sAEeleY0Mwn
AMVxeamwvLRejtTfJCS1gjLloabAe2qmEnGC04gEwhWpePBZEj8C2V/TZsvL
GGeFBOAo4UbZ3wFG3oWRys1XYqQrByr3tp1ghiwQErYDpUSbEMHmzN1Adm0w
iTWYSBNaJGnGvj36+783h7//J/7etPEXzIQZMgOG4uccvLiWogv422PJzNB6
jOMlGC9x+BuYcavNxn/onQEZhuKDOoAI5iKmZQOOw6iGRA2EPbrwhOMRYfyo
LwBzS24IWf7xj3+gky7R84vLqz5qR4UO7s9vrpq0e/FM8ZOeo5Hw2V/HAfwK
HG4DBdAB8mcogEn5EwQ+FQxCB5gEkl8wCJ4eKZg+jY0ZBf6YkAMQluDrJKIf
pL4SIBAYvp1WKiWplvkCMMLcd3Ml1G9GgbPDa32MfD9aaMeprZE9isGtpNiU
fq5/pvifHZozH+LynJqFiUWtDiI0lajTx7UNnUaBASQciGJKYBNAQaTAcBTQ
LIDTm/wCYPmwsgFyn+RGJgtjLMU+Xr9pZLR9M2ulNmcC0iBA0VBHy0puLDLw
2XRGP//++2d08xPywWwtXptzMUq1ZtiPpgItBu6pfWpkgeACNATID+P5Ex5A
GGBMjgaTG+9tJSZrw2a8GYtjkOBsbWEv/R6iYUEY+x8zEyO90Ilc49fuR6XG
qHl19UtWjTkpTr9rl061M8SM5Mea0Nr2AUnQ0rGM5sYGrb97DCdo4QNYJmpC
67VpQvAQGBAf10rZzuPIxRj4y4jrxF2Dre7X9r+aI8qYGQ/l5WeVCDtgIZt+
4MwzEEeAfzMC4yswatu2wvr4YhqikBnA0gSqaZhwJ5qGYgVRUWFLFJqPLbn2
GuCSIXFwPlwPkFGGAGERQ/ylMuZm9kKb5090lI5fAfe1lZFmoGhk4Ny5WdDB
NbgOqYymGAkNS5jD5rGpiceARplzdEkKgSiGum2d3TE8lLUhFoM6gk4y84eB
YKDDmxwxxwxsWj87mKmyDTRQjxBaScbcEYC7m020QmnfyNotukLGPiT0riFb
7rtNmEyutGTJdDrlUumAWp80pwzkkQyMrM2gkt+8SCpNEgyebUqXEKa9hOOh
WGaEzOOHbLOPaGSJYWj0m/2miwuaXs00wWzYx8jauO0Y1Vs42qbAJj/TyO6w
oY5WNSx0MsZMAhLiNxMKQIqWTuwbaJYW1M87n+m28ZBRwPPE6l3kMWHCt3YS
UktExOgweksTykSBUEDT/15zJmmY+TY4rwPnzQxwDpZ8BHZbhSCKB53FoJFv
rjZIaUtto1C0InBGsmmzc8u4QU3cFFwjsne6DfOXEZk22hqNAMRwgkq1lj0N
1yrqwKaUkBTZbTGMsolmCeTCKgYGUZ2ibSlaMB0r6Thcf9p5K+1otK0xcbW4
WphYjDEx3HaB8hxsJ+6th0t5WIIm1aolPhrHtp2v28jMWOPcbXz5butUP74W
ygnUZYqhqV2rMYjod1ux+rGXW93j/WOrKFT/MXkpPjkc8s+JTrkxPi1iY4tO
LiZMADuxa9Hdfw9/wBPMOiiuR2yMvjUsaSGLpREcJzGJzB7l2yGGJsQv8hjy
p3kM/bM8pmULYA63mABNKNbo6OCiZ1NIFA93Pa+E87DsitNKMQ9sXrmR2qDQ
QH6fgkVTbAZ20qay4IPRmGirB+Gtz21QaEgoiUyxDCUcoSs3UgQCM35YqMAQ
8k3+IYbfbUnxhzYgtxB8DC4H5LutLv7I6h/o+g2DIAT6GwRnoIQwxsb+0vI7
MvbcMMFu41gNw1LWulKoY/4DDLtd7gOC+qxfJhBTIuNdJj1kIMQSxvWDSfay
fHMSpYmdYaIlM+cr8MLsn3CDLR37LJwZ9lll1rmzYon6OA7BvbNw6z245tJB
cR1yF9wnC50l5KvcmdEvzWHzK7W+FlMPm7Oh+G6FOZBvzgzgztpF5oGUrllB
CsWcmQQT572HuQ52Ebo+WZE0IAwguppidunGYQuRY5bXXBjnhdJp/Vie9uU5
Bkqd9Sp2cl4NLaTBWhpxqpO5DfIlNH4uO0a2HBV1kbA44wpontE5ENGAc6V7
G3kdjCSQ44pEa4T8G/VsnRRBLg1uSvj+elsMGv9Kbpl78R1MTrTmD0cNXR4B
+BhWTJIo0OqAlRvQlYAXnf0OeSuhfwcZrNMDDwh0AP+PRXiAXC5BFDZNITzZ
lx5pwJ/zan/FmuWlU7nQr1cL+PfqolGOwtPpW/Py+vpxNLyrpbfJsFwN7tn9
7NAbTmrD1dvopbwajsnzc3txGk8uubxqRxfpg/Jqne6yfTorL2vB8D587gzK
T/1ev3ftl6+di0bSrDD5cCo7k+PVaPAwmUSrF3J0d1cbTeR9eiC6yzP/3mlO
nlaLhNceH19GT0/OYDLZveioR+kxL60+rs7d8PItOHqKxOnZyrn4j7+SLv+P
iK/jWQzll1vuwJTdQ/o7McUuaTP5KxCM8DPK8QzkuEDZmVPtwVvzvDF4Pn25
7TxXlu3RdeP46bl51hku+p03xr3529Hi9vowWb24q2h0+/Q2vrgjj8d3UWd+
2irfXx+sdled6KwtZtHR03L8Erau2Hmro8b+t93n+GSk3pa+6oRP7fLzzaTb
Kl/W7o6vnxO3Q56vyrXboMynZ7zWD5tDn7Of0cugXb2/nLwIdjx+Si7vvk2q
0+ufFX7yLOTsYNreLT/gCdrfWuPT1pFD5ovO491LazB5OmxV5NnQPemfz78Z
QfH7Z5Xd8/FJq9a9eZ5VrxbD8dPYXzy5s8F02qjFE1c9ns0vJ+T68GDYcXf7
r+c1HpVbu4eueDtWT4vny/7JoDs6Gh60nwb9xVtnwGLn9Sy9KV+Hlcbjt4or
Z+FkVxy0Gw0yF9H9YBa4PedwlT4CqS7kqO89tNRT9dGdPziXzvnPM4erVaJu
u4+3kXMdXJ8e/mTu292wo+41I0ijf9J83u125+VpJx6u2gv3W3DS6Z6Nx+Wb
RlTpLlj0FDK3PeWx6p9/46Ony/L8dvdazmPvoXd+7Zx1RiSs1B6e1bOSvfSk
9vNpLp5fV+IhdR67r6/di3G5/Jr+DNuHly3/vPrwELx1boK3sLE6rlUfu7XK
y4l70zsi8rlyFqV8Na89rSqDtOd4Rw+Xg8Fus/Vz1ezV/Ohx+vB/LtutUaMY
rWVCrUOE3vJKxv8S33+J7/878c0rAAFfi3LuIhPJ9kz/ycSPmz6R9rBpjvW+
IzDch6f1arleqdHK4WH5Qyd4bYVDDB7fjh/hIF6nz93LyXk8uO4P4peTZTfd
dcOwPLrmr1NVI0dnx7NjoODlZex1Knf3b4vu6s3ptrpdvlrM4kn4NpiNerP0
QsaXQ3XAXl7OFmx391acfJslp3Ey7Tg1IqPH4/69P2mt4vlLt9I5ujjh39iI
D6qjxuIy+Na9b3earttng8ObXa93svLa/dVrex6z3vR6cfiXnOBWnrZuTW+n
ausvNvCS2EQXKu+VFnubEnJDX2AEZhIa3YXM2sF5VEaw3mHao5SOBHZ3in17
hfGk6YjB+iWF5GDKsyAfQ3RsESrdYmfUSyHAKTQ8dXVdCSyZ2U2wVj3noc3B
CscmV+EkgUw9SR2F1wK+DLpXXzEVi33m5BuCRZykPu7gsTkvtv4BAVK4emA6
nUWCbcahMmteZzX3D3rXSLOAQxqkA2pb7NlsZJONHbKypwizWg5a8ELjHUfT
ENi1n3VL8tXvUu5iEwDXR6mK0zw677WOSMClZFNecgVWtiBQnkYgCl5gUrQq
pGi2ZCZCXKlTOl6YZuuthT3/PGnHmmsWgel0AYtkOrPODr5VGoAd9f0GVSgr
4PNWOpAVbjdPuIGnbbQZmFlNDjHd6EmS8jGNINVWuECEtnPrgclx4TzAXiN2
kKnwBNsT1OdK55LmTkPMTL1zjMT3zf2TYj2P7jjl+rhcrx7WK2d196Q+Pq27
vH7s1M9O6icn9fIhDtaO67Vy/bhaPz3Z0ZdJGv0GtsYlZMOJTW//+AS5Bys5
G6Og0etqdrVwvSXkC4oFybywvbOu4ssdw2Opa1gkK+DbMorpILE3EaQBHDac
wumBP4VimM6JYaHu1hSbNYRoxLFInxlwUwIVeZk24VMQ0CRjq+R0s/wNaJF8
TsBiaWos60n6ZgWAsXUOc+SsgGamWUWBYSU2Wyl6Ug4eUztA1eShcl1RsiVx
S82Nej8Qeb9MTBYfFG4UvZtUMUa6878sxqGs7gFypAD+u72vpXsmeSUK7E+U
VUDWFxEC2Bb1UOe5KDLAoxTrt7KAMClC/GTuVqFbeCd4mcN4L3x3We/e1obW
TRJ9NaV42cReWtGFjvVlExWR/KKLuT8xNa4pMedbCKzqcIX8UKBSPMkJiAu0
JdG9CU0i3RzR1QIQpUsxt021OEIBQFlAg+lirscSfM0hEgsREQaQe7aBnzUU
HMCYSXAxkn7h+9P9PdpwHLCkSCqVRD69Qau7R+77V094Q8veowSCGya1BJCF
I9EYyl3oHsD5euiFAPWlBUYsMPm10L7P2gbonzUNtM5kR2z4Ei8PZR38DTnP
phmpKFwdAK9Y6INE2DLDqx5gkfH6KPZOgDch960a2VaLMfOoKQXmFlnv6DKi
7cigF09DU3dzSaIvVQFa+UXDKATsH3VlUTfzwyU4gLlIotBcHzTCkE8mumSy
LOxcxCpgSzxKJpxaFEIQuyjNLj+RAiwdFuASnK+EShXGBPbMADyJ0qmXNfUL
KLAx+BrbaAJFMhebgI1CmdKjxcIFVvuRucmkzK0lHSJAqLEWaCtEO3n020O5
uNg3V0X3aLlShSE0KWqPdiKIkwce3pbd39/f+WodtHFvWIgDE2tvEL4jTc5o
MKpzwS3vpFBZPc3lsR+956bl/ceXH7MAZ+1gdQ1zM3DEYANQLi2ALB6WGrNu
zvrCBJ2F0SLMAzOsveOZF5zNgAqSS/QEEKeZhhT24X1foF6hyRQYxTl8s1xX
vH9meOJyAnQBZAyOcFyITSFYiXy8u4ZXHAFwJXRLcBjw9lNegL2nC9JmDvlo
c6ASQs7apHoHNOJATNBr3ccHNyh1VPBP3Y6j6T4uAAA=

-->

</rfc>

