<?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.39 (Ruby 3.4.7) -->


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

]>


<rfc ipr="trust200902" docName="draft-kavian-aep-api-key-session-credential-05" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="AEP API Key">API-Key Session Credential Grant Type for the Agent Enrollment Protocol</title>

    <author initials="N." surname="Kavian" fullname="N. Kavian">
      <organization>Jarwin, Inc. (InFlow)</organization>
      <address>
        <email>nas@inflowpay.ai</email>
      </address>
    </author>

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

    
    
    

    <abstract>


<?line 39?>

<t>This document defines the API-key session-credential grant type for the Agent Enrollment Protocol (AEP).  The grant type lets an AEP Service issue an opaque API key through the AEP Grant command for deployments that already operate header-based API-key authentication.</t>



    </abstract>



  </front>

  <middle>


<?line 43?>

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

<t>AEP session credentials allow a Service to issue a stateful credential after an Agent authenticates with a baseline AEP client assertion <xref target="AEP-CORE"/>.  This document defines the <spanx style="verb">api-key</spanx> grant type for Services that want to reuse existing API-key middleware while preserving AEP key possession as the issuance root.  Grant type request and response bodies are JSON objects <xref target="RFC8259"/> carried over HTTP semantics <xref target="RFC9110"/> as defined by AEP.</t>

<t>This grant type does not replace baseline AEP authentication.  Services that implement this grant type <bcp14>MUST</bcp14> continue to accept baseline AEP authentication on authenticated AEP commands.</t>

</section>
<section anchor="requirements-language"><name>Requirements Language</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?>

</section>
<section anchor="grant-type"><name>Grant Type</name>

<t>The grant type identifier is:</t>

<figure><sourcecode type="text"><![CDATA[
api-key
]]></sourcecode></figure>

<t>A Service that enables this grant type lists <spanx style="verb">api-key</spanx> in <spanx style="verb">commands.grant_types</spanx> and lists <spanx style="verb">grant</spanx> and <spanx style="verb">revoke</spanx> in <spanx style="verb">commands.supported</spanx> in its AEP Inspect document.</t>

</section>
<section anchor="inspect-configuration"><name>Inspect Configuration</name>

<t>A Service <bcp14>MAY</bcp14> publish configuration under <spanx style="verb">commands.grant_types_config.api-key</spanx>:</t>

<figure><sourcecode type="json"><![CDATA[
{
  "commands": {
    "grant_types": ["api-key"],
    "grant_types_config": {
      "api-key": {
        "default_lifetime_seconds": "2592000",
        "header_names": ["x-api-key"],
        "scopes_supported": ["read", "write"],
        "supports_per_credential_revoke": "true"
      }
    },
    "supported": ["enroll", "grant", "inspect", "revoke", "status"]
  }
}
]]></sourcecode></figure>

<t><spanx style="verb">default_lifetime_seconds</spanx> is an AEP-owned numeric value and is therefore represented as a JSON string.</t>

<t><spanx style="verb">header_names</spanx>, when present, lists HTTP header names the Service can issue for API-key presentation. Header names are case-insensitive on the wire, but Services <bcp14>SHOULD</bcp14> publish lowercase names. This field provides issuance guidance only; there is no default API-key header name. The Grant response <spanx style="verb">header</spanx> value is authoritative for each issued credential.</t>

<t><spanx style="verb">scopes_supported</spanx>, when present, lists Service-defined scope strings an Agent can request.</t>

<t><spanx style="verb">supports_per_credential_revoke</spanx> is a string boolean.  If absent, the default is <spanx style="verb">"false"</spanx>.  Every successful Grant response includes <spanx style="verb">credential_id</spanx>.  When this value is <spanx style="verb">"true"</spanx>, the Service <bcp14>MUST</bcp14> support a Revoke request containing both <spanx style="verb">grant_type</spanx> and that <spanx style="verb">credential_id</spanx>.  When this value is <spanx style="verb">"false"</spanx> or absent, the Agent <bcp14>MUST</bcp14> use grant-type or all-grant-types Revoke instead.</t>

</section>
<section anchor="grant-request"><name>Grant Request</name>

<t>The Agent invokes AEP Grant using baseline <spanx style="verb">Authorization: AEP &lt;jwt&gt;</spanx> authentication with <spanx style="verb">op</spanx> equal to <spanx style="verb">grant</spanx>.</t>

<figure><sourcecode type="json"><![CDATA[
{
  "grant_type": "api-key",
  "label": "agent-prod-read",
  "requested_scopes": ["read"]
}
]]></sourcecode></figure>

<t><spanx style="verb">grant_type</spanx> <bcp14>MUST</bcp14> be <spanx style="verb">api-key</spanx>.</t>

<t><spanx style="verb">label</spanx> is <bcp14>OPTIONAL</bcp14> and is an Agent-provided display label.  Services <bcp14>MAY</bcp14> ignore it.</t>

<t><spanx style="verb">requested_scopes</spanx> is <bcp14>OPTIONAL</bcp14>.  A Service <bcp14>MAY</bcp14> grant fewer scopes than requested.  Unsupported requested scopes <bcp14>MAY</bcp14> be omitted from the response <spanx style="verb">scopes</spanx> array.  If the Service cannot issue a useful credential for the requested scopes, it <bcp14>MUST</bcp14> return <spanx style="verb">invalid_request</spanx>.</t>

</section>
<section anchor="grant-response"><name>Grant Response</name>

<t>A successful Grant response is a JSON object:</t>

<figure><sourcecode type="json"><![CDATA[
{
  "api_key": "aep_live_7Jm5Example",
  "credential_id": "key_01HZY8W7Q2F8J7D3P9G9Z1N6TT",
  "expires_at": "2026-12-01T00:00:00Z",
  "header": "x-api-key",
  "scopes": ["read"]
}
]]></sourcecode></figure>

<t><spanx style="verb">api_key</spanx> is <bcp14>REQUIRED</bcp14> and contains the complete, opaque HTTP field value to send in <spanx style="verb">header</spanx>. The value <bcp14>MAY</bcp14> include a Service-required authentication scheme, such as <spanx style="verb">Bearer </spanx>, followed by the secret. Services <bcp14>MUST</bcp14> generate the secret component with at least 128 bits of entropy. Agents <bcp14>MUST</bcp14> treat the entire value as a secret.</t>

<t>API key values <bcp14>MUST</bcp14> match the following syntax. Numeric character values and repetition operators are defined by RFC 5234 <xref target="RFC5234"/>.</t>

<figure><sourcecode type="abnf"><![CDATA[
api-key-value = %x21-7E [*(%x20-7E) %x21-7E]
]]></sourcecode></figure>

<t>This syntax permits visible ASCII characters and internal spaces. The value <bcp14>MUST NOT</bcp14> be empty or contain leading or trailing spaces, control characters (including tab, carriage return, line feed, and NUL), or non-ASCII characters. These constraints allow unchanged HTTP transmission without header injection or whitespace normalization. The Service is responsible for choosing a value that is valid for its selected header.</t>

<t><spanx style="verb">header</spanx> is <bcp14>REQUIRED</bcp14> and identifies the HTTP header used for presentation.  When <spanx style="verb">header_names</spanx> is advertised, the value <bcp14>MUST</bcp14> be one of the advertised names.</t>

<t><spanx style="verb">expires_at</spanx> is <bcp14>REQUIRED</bcp14> and is an RFC 3339 <xref target="RFC3339"/> timestamp for credential expiry.</t>

<t><spanx style="verb">scopes</spanx> is <bcp14>OPTIONAL</bcp14> and contains the granted scope strings when present.  A missing or <spanx style="verb">null</spanx> value means the API key has no scope-limited authorization.  The Service <bcp14>MAY</bcp14> return an empty array with the same meaning.</t>

<t><spanx style="verb">credential_id</spanx> is <bcp14>REQUIRED</bcp14> and is a stable Service-issued identifier for the issued API key. It follows the Service-wide uniqueness and non-reassignment requirements in the Core Grant command. It is not the API key and is not used for credential presentation. The Agent stores it with the credential and sends it only when targeting that credential in a Revoke request supported by the Service.</t>

<t>Services <bcp14>MUST</bcp14> issue expiring API keys.</t>

</section>
<section anchor="credential-presentation"><name>Credential Presentation</name>

<t>On later protected-resource requests, the Agent presents the API key in exactly the response-selected <spanx style="verb">header</spanx>. AEP does not standardize <spanx style="verb">x-api-key</spanx> or any other API-key header name. The following name is only the Service-selected value in this example:</t>

<t>A field value outside the response-selected <spanx style="verb">header</spanx> is not an API-key credential presentation, even if the value equals an issued API key. If the request contains no other AEP credential presentation, the Service returns the core <spanx style="verb">authentication_required</spanx> error. When the response-selected <spanx style="verb">header</spanx> is present but its value is malformed, expired, revoked, unknown, or bound to a different Agent, the Service returns <spanx style="verb">not_recognized</spanx>.</t>

<t>Agents <bcp14>MUST</bcp14> send <spanx style="verb">api_key</spanx> unchanged in the issued <spanx style="verb">header</spanx>. They <bcp14>MUST NOT</bcp14> add or remove an authentication scheme, split or decode the value, or trim whitespace. Selecting <spanx style="verb">Authorization</spanx> does not cause the Agent to add <spanx style="verb">Bearer </spanx>. Selecting the dedicated AEP carrier does not override the issued API-key header.</t>

<t>For example, a Service can issue <spanx style="verb">header: "Authorization"</spanx> and <spanx style="verb">api_key: "Bearer example-secret"</spanx>. The Agent sends exactly <spanx style="verb">Authorization: Bearer example-secret</spanx>, not <spanx style="verb">Authorization: Bearer Bearer example-secret</spanx>. This remains an <spanx style="verb">api-key</spanx> grant; unlike <spanx style="verb">oauth-bearer</spanx>, its complete field value is supplied by the Service rather than constructed by the Agent.</t>

<t>A <spanx style="verb">Bearer</spanx>, <spanx style="verb">bearer</spanx>, <spanx style="verb">Basic</spanx>, or <spanx style="verb">basic</spanx> prefix does not change the Grant Type. The Service validates the complete value as the issued API key; accepting it does not require the corresponding OAuth Bearer or Basic Grant Type to be enabled.</t>

<figure><sourcecode type="http-message"><![CDATA[
x-api-key: aep_live_7Jm5Example
]]></sourcecode></figure>

<t>Authenticated AEP command endpoints <bcp14>MUST</bcp14> continue to accept baseline AEP authentication.</t>

</section>
<section anchor="revoke"><name>Revoke</name>

<t>The Agent invokes AEP Revoke using baseline <spanx style="verb">Authorization: AEP &lt;jwt&gt;</spanx> authentication with <spanx style="verb">op</spanx> equal to <spanx style="verb">revoke</spanx>.</t>

<t>To revoke all API keys of this type for the authenticated Agent:</t>

<figure><sourcecode type="json"><![CDATA[
{
  "grant_type": "api-key"
}
]]></sourcecode></figure>

<t>When the Service advertises per-credential Revoke, the Agent can revoke one API key:</t>

<figure><sourcecode type="json"><![CDATA[
{
  "credential_id": "key_01HZY8W7Q2F8J7D3P9G9Z1N6TT",
  "grant_type": "api-key"
}
]]></sourcecode></figure>

<t>Revoke returns an empty JSON object on success.  The Service <bcp14>MUST</bcp14> return success regardless of whether a matching key existed.</t>

<t>To revoke all session credentials of every grant type, Agents use the core <spanx style="verb">all_grant_types</spanx> Revoke request.</t>

</section>
<section anchor="error-handling"><name>Error Handling</name>

<t>This grant type uses the AEP error vocabulary defined by the core protocol. An API key presented in the response-selected <spanx style="verb">header</spanx> that is expired, malformed, revoked, unknown, or bound to a different Agent fails as <spanx style="verb">not_recognized</spanx>.</t>

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

<t>This document requests registration of <spanx style="verb">api-key</spanx> in the AEP Grant Types registry.</t>

<texttable>
      <ttcol align='left'>Field</ttcol>
      <ttcol align='left'>Value</ttcol>
      <c>Grant Type</c>
      <c><spanx style="verb">api-key</spanx></c>
      <c>Description</c>
      <c>Opaque API key issued through AEP Grant</c>
      <c>Reference</c>
      <c>This document</c>
</texttable>

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

<t>API keys are bearer secrets.  Services <bcp14>MUST</bcp14> store only salted hashes or equivalent one-way verifiers.  Services <bcp14>MUST NOT</bcp14> log raw API-key values, and Services <bcp14>MUST</bcp14> support AEP Revoke for every advertised grant type.  Agents that suspect key disclosure <bcp14>SHOULD</bcp14> call AEP Revoke using baseline AEP authentication and then fall back to per-request signed client assertions until a new key is issued.</t>

<t>Services <bcp14>MUST</bcp14> validate only the configured API-key header for this grant type.  Services <bcp14>SHOULD</bcp14> reject ambiguous requests that present multiple API-key headers or multiple non-baseline bearer credentials when that ambiguity would affect authorization semantics.</t>

</section>
<section anchor="privacy-considerations"><name>Privacy Considerations</name>

<t>API keys can become correlation handles if reused outside the issuing Service.  Agents <bcp14>MUST NOT</bcp14> present AEP-issued API keys to other Services.  Services <bcp14>MUST NOT</bcp14> log raw API-key values in ordinary logs or telemetry.</t>

</section>


  </middle>

  <back>



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



<reference anchor="RFC3339">
  <front>
    <title>Date and Time on the Internet: Timestamps</title>
    <author fullname="G. Klyne" initials="G." surname="Klyne"/>
    <author fullname="C. Newman" initials="C." surname="Newman"/>
    <date month="July" year="2002"/>
    <abstract>
      <t>This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="3339"/>
  <seriesInfo name="DOI" value="10.17487/RFC3339"/>
</reference>
<reference anchor="RFC5234">
  <front>
    <title>Augmented BNF for Syntax Specifications: ABNF</title>
    <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
    <author fullname="P. Overell" initials="P." surname="Overell"/>
    <date month="January" year="2008"/>
    <abstract>
      <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="68"/>
  <seriesInfo name="RFC" value="5234"/>
  <seriesInfo name="DOI" value="10.17487/RFC5234"/>
</reference>
<reference anchor="RFC8259">
  <front>
    <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
    <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
    <date month="December" year="2017"/>
    <abstract>
      <t>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
      <t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="90"/>
  <seriesInfo name="RFC" value="8259"/>
  <seriesInfo name="DOI" value="10.17487/RFC8259"/>
</reference>
<reference anchor="RFC9110">
  <front>
    <title>HTTP Semantics</title>
    <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
    <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
    <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
      <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="97"/>
  <seriesInfo name="RFC" value="9110"/>
  <seriesInfo name="DOI" value="10.17487/RFC9110"/>
</reference>

<reference anchor="AEP-CORE" target="https://datatracker.ietf.org/doc/draft-kavian-agent-enrollment-protocol/">
  <front>
    <title>The Agent Enrollment Protocol</title>
    <author initials="N." surname="Kavian" fullname="N. Kavian">
      <organization></organization>
    </author>
    <date year="2026" month="October" day="31"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-kavian-agent-enrollment-protocol-05"/>
</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="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>





  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA61a/3LbxhH+n09xZaYzSYagRTmubSZNq9hyrMSRHFtuJ8l4
yCNwJC8GcSgOEMU6zrP0Wfpk/Xb38IuUlKZTTTIGD/djb2/322/3EEXRoLRl
aqZqePLyLPrW7NRr4711mXpSmMRkpdWp+rrQWakud7lRS1eocm3UyQrv1GlW
uDTd0OPLwpUudulwoBeLwlzRjKcvFWZVmHU4SFyc6Q0WSgq9LKN3+srqLNIm
j3Ruo3dmF3lZOIqbhaOjB4NElxh0fHT8p2gyiSYPBjEaVq7YTZUvk4HNi6kq
i8qXx0dHj4+OB75abCxPVELeqTo7vXw28KXOkplOXWa4txnkdjpQChJP1c54
PHpXlIVZ+ub3btP+1FW5dgWNiPC/UjbDi/Ox+pZ3wU2yuX6bK1Y6s//UJaSZ
qm90sbXZSJ1l8Vh9fJY9S932E+5nNtqmU0zh/2qzJZpzvRtrOxhkrthg9JWh
pV89e3L//v3H4fHB8f3PwuOj4wd16+PJ5IgeofroycWr0ynPXx/x5d0Hx111
sTLlVK3LMvfTe/egfl0WOn5nirE15XKMPd3DWd7rHyNNGplm0igPk97jSbtn
eBTdn3CjN4U1Hvt1IqSCYkpTZKaMntLc+5Zy2xJkJDS6PSP6i246o5vOaUAS
NFoej8eDQRRFSi88bbscDC7X1ivsuGJtJWZpM+PFB+AxMFx1aLhqxR5T/lce
oz7GaX0yVoqOpzMwNaVXOqOzhFMWVzY2CpZdGWp0uf5HxSIoEqFcF65arWUh
9BePjd1mA8NnERKTp25HC5PwulQ6LYxOdpjJFDgftcYvU0QL7U3SbI2USluK
2YaDbjY2SVIzGHxEJ1a4pIrp5WBACwddqFYX2EMKk1a62UTp6n3AhbH0sko7
/RUO3RS8cdZYRwTofWvLNcaRlCkOgjcbp5Y7epgUSaLev6/t/8MH1uttJzgP
2DPfP7AgalDVlt85VZjKG2WurS9ttmqUJPrY6sKo7dqmRuWF8TQB9YF81Cd3
vlaNlrVJBTqDOgrnSkj5dStBYXC2HjvC2WGq3GVYduES+IuiVb55fXGu3OJn
E+Mw378PEPDhg4p1AadKlLuCBp9fXtJ5wAKgvNCP8AH9IIKoIVGLHck4Dnbe
UUPisFrmSkiQpxpy9nS+ZxhqT2N2k6eG1V3uTfvdm9eXMEwMzSo2BR3HJi/v
ml2R0jpWkMipi3H7MRniK2jMFkbM+4XOVhXwgvZkWPtbVyReDWnt4Uj+VecX
/Pzq9Ps3Z69On9Lz6+cnL140D4PQ4/XzizcvnrZP7cgnF999d3r+VAajVfWa
BsPvTn7AGzrF4cXLy7OL85MXQ+CS6KQxSDpR6GEBkyAAhPHQFrUfJMbHhV3g
B8Z89eTlv/81+QzH+Aec4/FkQuctPx5NHn6GH1soSFZzWboLP6G13UDnudEF
zQJXhJHktoRfjsgM/NptM/h+YaDHT38izbydqi8WcT757MvQQBvuNdY66zWy
zg5bDgaLEm9oumGZRpu99j1N9+U9+aH3u9Z7p/GLv7CdRZNHf/lyQMbT0hux
mI61WgalpYU7WT8dDH799VdVmutyEICDGgB8LbSR8ZtML1L2hL7pp8AN38Ec
nMe8sWLuN6N+fs6HGHpzu7TMQavcO7M30Fd5Du5iEm63GEPecZb5HPDQWNlY
4Foan7hsaVdVoQNuN+JDeyqvFlh6TT7adlJVhuBws7gz6Tmu9xXU9LPH3O8R
d4f1oOFUvec4POyMRuNPwzB0+HZ08D7M3ozF27p324RG4Jmu0nKW2qUp7cbM
vMFIXnQIcAQ7PBqO2u4S7WbEBkSE62hPCO7mY0cyNDrmrhQ3yeO3hS1Nv7v0
8zPE1Fkb0mZycCQKkc9hGPCB//0Q9txfQ4gOrcK6oAcrp0ePYT48UQCt/PDt
gKb7IOY4v00XsJCaUURwewBLBuMobKyudMq8IqEeJcEBoiAFIg5lmQAS4i5H
HjAjhDZY1LyrxfmIIUeFEaNgwByFpB9zLwl+tcHFkEa4AEXdOqCGKUJoed4d
TGAZI1RE0IbJvCXaRvGBJt0iAozUoirbYBSQpbZp8BBT0HCZbSzUAO6dJljU
XcHdfRuYV5VN+IHw9HNRC+kncypouJG4s8Ex8zjBlCZ4B03Ng6LpGJiu2pKJ
J+/e6Hgtykg6dIjUvG+Ft6g67DqqQzsPC6flW0JFOg8Mgye/02bFZMIk4CAu
NZrC/dmSKDIvTqqv9YHO8+ESwcUM5+h1Ch4CflwhxHtPNG9PLTaL04p0Pu8s
bBMa+nfaICNoo7K5eM981DMhjlBhE5D0FYvdUChiGtpmIjyo47yFFgFVRuz/
cvmwMeR1vc2LWlkO4oe8QsSITx3TNGpbfC0fzLeESYzb+PNKJJYQJFPajPr6
DqOvPO+k5krzE7GiOsWkjl/8vC2/nO9TKObNc5fPFZYByQbhCKFlvA/XrYYI
sGpUJJQapnphUm5dhRQsiQQN6W3QuUlmYrAtWL5toKmrftbYosPCyRx5Cba6
OnTXsFQbcBQ8NVGJ9aCmO8VjuhyU4phdZQRhlo18X7TeAhjZD4ESs5cGYCFO
xKy28RqTYMSbrHHHtr3uTZNgY25jS2pdFm7DltLiQS0GCDtyffanPVwk6l2n
STCrvSSpzir3lx5hw6JY0MiqAFGAEenUJrPQc94zORGHKMAdTtoAv6QcB/Ed
xzeTeDzUJkfUuTKzh99sHpxea0oDxDh6HkZdMWJ2NHn+4w+P/v7w++Nnj755
+PT+y8dfP/5xcv6ny0sZZK5zYLqf6ZLDOBcQjqOjyeXR0ZT/+1H6CbpSnzaM
84vbDTEIzYZQ81m2tIAYEqdAXbCDEmElJNwcziRgCDDAkYAETNFrkJcIIK/Z
EgXl2gw4KiRdSfa91Mdr5DAjOow1Bdz5V+DtxLtGOHDKoiVhI8kQ0nHC447N
06HDPySbb7vwHlxGeCLJc6mA4YDGyfEjtSC+6JagrEjkcxgie1iYrITKSp6J
RCzqLTERCMvDckIFgt+FgRtdxlKLEKkJs/wOar0eq/PAOOK1pvoKNhdGSrKb
g7BIzsdlCVdIyO9kq0h4FBW/JKGlJyT5YpJ6kS1rZh6JsH9Wf7w+nkQPT9VP
n36MxyM8flK3vRVbYBIg8imsuiGdXFlvQeLVyesnZ2etsCIm52kZvNDnSIx9
77xDvkTubzZ5uaMYEEyK9J6QLsh3C21T1gtPMeI+oHzdpT4Ww6FepV6MJLsH
8gbXprCPGLA0JpG07/zNi09GNHnmsmhfcBbSk0VnVNmydMpSmKky9MpW0C4b
N15mPpRQ2WIcCFXgNzYjAODjKajWURoWX3GdMg1hSNTRVqxqJGF9Em7Fa+c4
junah7hkwKHWSrWKjgAxDotBLFm85ZuHPtukaeK1Xc5ZUTmLpuyTSgnwfQLL
SJdcURHJk07L/qkSoEPfTpC67Ri4JMRr4eoGETmAkfFSEVeMl56QuBNFB4/f
5KKdFuR5vl3LAA/DYg+sOGwd8L4uU+RIx2crVjjPqjStSekGzK4pbLJPrzWT
XZ4vSi0cI0BWQzlC1bIbPEPcwWbF/jnCCfQwKEFZvFRIIfrM60a1UZWQbKdG
z8CRO7l5HQ3DmyD/WJ2VAYF6WUe0xVCYvQWgZ4h5vBD5DPAOqlllXJYpuiUl
KxnGE2IUvdoqr2GlUNZVXZCdmhsL7Jxs3xhbxueBeJSClK3CupVRTErBhjs0
RZ5Qs2eYIEfqDKCKzz4jbmlLiCRBKziMfiwR8sE2GKqdtDOpt3Uuh152tjIY
XADlNKE6lefZfaFV76oibiTwXdYcFNG3O4htrgFb6a7HmqIGEdpIS4y3qVTy
NY8uEvtPMKyGCQhfz4DElMHdnrK1sYra6PRYxV3DaQQISUFIEYwQnSnxqC43
AHJ6MrW7N1HbCfHbINstljJS5grnbZcdaGI6z9hyYPzLLkNsoQIeHTRBVdTb
VuqyUXHpmhEVxNh7vGVW8xlkF0XhinGdPv3WtsOSnLNz1K1zLUQTupUhFBZQ
xYMkpHiosneZ22Yc6hauoiTOwc4Tu1wiQ8d0bFo3b2EOTUPc2K0yWElCbLhL
eZjKtdywDY0BAIKOe0xv1wZ9nSQkFFDDXfE1zW38Lk/Jg+lWJnbBQHjvI+EG
dtOJrsTxSHdkmf2Eb96afqwp9Wz9ijQCYRoC2Z1EEvakW0vne4OinY4uEIra
dFvD6jgOFPeMihZi+qPO9U5b0wlqoqvgrtjDUM4MasbrIGWYLBJyOZz3kJFx
r4aF/cT3xgnAmmkvt/S9eUgoCRV0JZuxW+3dEX0Oo0gt8HTu6HCjBU8zH7H9
1ulCDwWIXAJzU3sAuQoMlxyRk0shZlXcQWbeOVlofY5YZt4sOP9KexvP2WTm
C34mh1ra645ZsPnyZG2Vu0/QmHTx3Vo34Wm5/mFc/Tzc2ZAt2bJ7UcQoUMOE
uD7T1ws6glrjEJcl735WIPcfUjhPApunK+gIzMjTVU6D5lN1U44Z6vC3XRJh
5iR3tnHz33f/FG6YCH1uq86EGPt/Lc+EAhxdzbkAfnx/UwdiYaJUr+1eM+9d
lJGkBwn7zRWeOjVusLu2kIbqekqPutfcsu1uPJfiIstKZDnIengl8L9UA+4W
u6E5AvQN/+xULqhQHOoc+8S1UzEJPfBzBS6R0iM0DabFvqolu6VzJjDky2A2
2f4h3XQPTnk2F0TbO6FRnXDX6B3Ca5rOehdCfQ7HBnlKkVY9h3VTHnl4f1v5
+jMFWB2HZXXlYr2oUg0ROgl1s2z9RQVYVdZwsfYCwP5mRK/zuCZkd8L474ze
aon82HMN5DBif6TOTs5P6BqL6JXcUPn9LzVqtknnaCnllbx12b+A638wcckl
2jCAEq9f1DNGcvn7Rf2NUfG3/37ByKj9U71fd/3xyA4wYmQr72+v+ZSvjHPe
6i/qov+RSEDx+luRdts08pVh9ceG99lX5V1r4jBem7gqLFxt/0AapKISjsSt
UDjyvWotMy/KfIRxe51y2q/9Gm+JZCCuIB6RKACVaIt8En7Eqd/hRMTDUrdC
bN02lEVKTFIl2Vs2XBx0QJzvYthPOzl+61iUQ6/az2h8JXeqtExifZw6X2Ej
4eIpZsC+NUDc8K2D3EkAgZc0dKHjd+QfhLtNAocMla6I9r56AYZgFiSJKjPb
cN7hyA9SuzrmtxlOfdt7wPNCYOlhS1fnYaOFYYDVmwVmcZVv3Y+1VBP9TZWW
Nk/N3iJ8ys07SsUbFQWz6eKoJL38DRMvR6a3dRXcVAND4rJfomg/gWHkeFnA
lOI7bJUi2AJwswkkJpVZ1gS0lJov5TOgpJfdkZ7pZOtcWvUKqWSStQbo7rVP
pzwdsGRktVZ/h1ETiDmkvBmhOrqwKktDX98whP0HijhI2OMpAAA=

-->

</rfc>

