<?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-oauth-session-credential-05" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="AEP OAuth">OAuth Bearer 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 42?>

<t>This document defines the OAuth Bearer session-credential grant type for the Agent Enrollment Protocol (AEP).  The grant type lets an AEP Service issue an OAuth-style Bearer access token through the AEP Grant command while preserving baseline AEP client assertion authentication as the root of trust.</t>



    </abstract>



  </front>

  <middle>


<?line 46?>

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

<t>The Agent Enrollment Protocol (AEP) defines Grant and Revoke commands for optional session credentials <xref target="AEP-CORE"/>.  Session credentials are an optimization for deployments that want to reuse existing authentication middleware after an Agent has proven possession of its AEP identity key.</t>

<t>This document defines the <spanx style="verb">oauth-bearer</spanx> grant type.  The grant type issues an OAuth Bearer access token <xref target="RFC6750"/> through the AEP Grant command.  Grant type request and response bodies are JSON objects <xref target="RFC8259"/> carried over HTTP semantics <xref target="RFC9110"/> as defined by AEP.  This grant type does not redefine OAuth authorization grants, refresh tokens, token introspection, or token revocation.  When a Service exposes standard OAuth token introspection <xref target="RFC7662"/> or revocation <xref target="RFC7009"/> endpoints, it advertises those endpoints as grant type configuration.</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[
oauth-bearer
]]></sourcecode></figure>

<t>A Service that enables this grant type lists <spanx style="verb">oauth-bearer</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.oauth-bearer</spanx>:</t>

<figure><sourcecode type="json"><![CDATA[
{
  "commands": {
    "grant_types": ["oauth-bearer"],
    "grant_types_config": {
      "oauth-bearer": {
        "access_token_formats": ["opaque"],
        "default_lifetime_seconds": "900",
        "introspection_endpoint": "https://api.example.com/i",
        "revocation_endpoint": "https://api.example.com/r",
        "scopes_supported": ["read", "write"],
        "supports_per_credential_revoke": "true"
      }
    },
    "supported": ["enroll", "grant", "inspect", "revoke", "status"]
  }
}
]]></sourcecode></figure>

<t><spanx style="verb">access_token_formats</spanx> is an array of strings.  This document defines <spanx style="verb">opaque</spanx> and <spanx style="verb">jwt</spanx> as descriptive values.  Agents <bcp14>MUST</bcp14> treat returned access tokens as opaque regardless of the advertised format.</t>

<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">introspection_endpoint</spanx> and <spanx style="verb">revocation_endpoint</spanx>, when present, are HTTPS URLs for standard OAuth operational tooling.  AEP-aware Agents use AEP Revoke for AEP-issued session credentials.</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": "oauth-bearer",
  "requested_scopes": ["read"],
  "token_format": "opaque"
}
]]></sourcecode></figure>

<t><spanx style="verb">grant_type</spanx> <bcp14>MUST</bcp14> be <spanx style="verb">oauth-bearer</spanx>.</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>

<t><spanx style="verb">token_format</spanx> is <bcp14>OPTIONAL</bcp14>.  The values defined by this document are <spanx style="verb">opaque</spanx> and <spanx style="verb">jwt</spanx>.  A Service <bcp14>MAY</bcp14> ignore this preference.</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[
{
  "access_token": "ya29.example",
  "credential_id": "tok_01HZY8W7Q2F8J7D3P9G9Z1N6TT",
  "expires_at": "2026-12-01T00:00:00Z",
  "scopes": ["read"],
  "token_format": "opaque",
  "token_type": "Bearer"
}
]]></sourcecode></figure>

<t><spanx style="verb">access_token</spanx> is <bcp14>REQUIRED</bcp14> and contains the Bearer token value.</t>

<t><spanx style="verb">token_type</spanx> is <bcp14>REQUIRED</bcp14> and <bcp14>MUST</bcp14> be <spanx style="verb">Bearer</spanx>, compared case-insensitively as specified in Section 5.1 of <xref target="RFC6749"/>. Agents <bcp14>MUST</bcp14> accept any capitalization of this value. The <spanx style="verb">access_token</spanx> value remains case-sensitive and <bcp14>MUST NOT</bcp14> be modified.</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 token has no scope-limited authorization.  The Service <bcp14>MAY</bcp14> return an empty array with the same meaning.</t>

<t><spanx style="verb">token_format</spanx>, when present, describes the Service-selected format.</t>

<t><spanx style="verb">credential_id</spanx> is <bcp14>REQUIRED</bcp14> and is a stable Service-issued identifier for the issued OAuth Bearer credential. It follows the Service-wide uniqueness and non-reassignment requirements in the Core Grant command. It is not the access token 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>This document does not define refresh tokens.  Agents renew by invoking AEP Grant again with a fresh baseline client assertion.</t>

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

<t>On later HTTP requests, the Agent presents the token using the Bearer authentication scheme:</t>

<figure><sourcecode type="http-message"><![CDATA[
Authorization: Bearer ya29.example
]]></sourcecode></figure>

<t>On protected resources, the Agent <bcp14>MAY</bcp14> instead use the dedicated AEP carrier while preserving the Bearer field value:</t>

<figure><sourcecode type="http-message"><![CDATA[
AEP-Authorization: Bearer ya29.example
]]></sourcecode></figure>

<t>Services implementing this grant type <bcp14>MUST</bcp14> accept both carriers on protected resources. Agents <bcp14>MUST</bcp14> use only one AEP carrier per request, and the ambiguity and precedence rules are defined by AEP core.</t>

<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 OAuth Bearer session credentials of this type for the authenticated Agent:</t>

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

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

<figure><sourcecode type="json"><![CDATA[
{
  "credential_id": "tok_01HZY8W7Q2F8J7D3P9G9Z1N6TT",
  "grant_type": "oauth-bearer"
}
]]></sourcecode></figure>

<t>Revoke returns an empty JSON object on success.  The Service <bcp14>MUST</bcp14> return success regardless of whether a matching token 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.  A token 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">oauth-bearer</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">oauth-bearer</spanx></c>
      <c>Description</c>
      <c>OAuth Bearer access token issued through AEP Grant</c>
      <c>Reference</c>
      <c>This document</c>
</texttable>

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

<t>Bearer tokens are usable by any party that presents them.  Services <bcp14>SHOULD</bcp14> issue short-lived tokens.  Services <bcp14>MUST NOT</bcp14> log raw access token values, and Services <bcp14>MUST</bcp14> support AEP Revoke for every advertised grant type.  Agents that suspect token disclosure <bcp14>SHOULD</bcp14> call AEP Revoke using baseline AEP authentication and then fall back to per-request signed client assertions until a new token is issued.</t>

<t>Services <bcp14>MUST</bcp14> bind issued tokens to the authenticated AEP Agent identity.  JWT access tokens <bcp14>SHOULD</bcp14> include an audience identifying the issuing Service.  Services <bcp14>MUST</bcp14> reject tokens whose audience does not identify the receiving Service.</t>

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

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

</section>


  </middle>

  <back>


<references title='References' anchor="sec-combined-references">

    <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="RFC6749">
  <front>
    <title>The OAuth 2.0 Authorization Framework</title>
    <author fullname="D. Hardt" initials="D." role="editor" surname="Hardt"/>
    <date month="October" year="2012"/>
    <abstract>
      <t>The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 1.0 protocol described in RFC 5849. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6749"/>
  <seriesInfo name="DOI" value="10.17487/RFC6749"/>
</reference>
<reference anchor="RFC6750">
  <front>
    <title>The OAuth 2.0 Authorization Framework: Bearer Token Usage</title>
    <author fullname="M. Jones" initials="M." surname="Jones"/>
    <author fullname="D. Hardt" initials="D." surname="Hardt"/>
    <date month="October" year="2012"/>
    <abstract>
      <t>This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a "bearer") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6750"/>
  <seriesInfo name="DOI" value="10.17487/RFC6750"/>
</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>

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



<reference anchor="RFC7009">
  <front>
    <title>OAuth 2.0 Token Revocation</title>
    <author fullname="T. Lodderstedt" initials="T." role="editor" surname="Lodderstedt"/>
    <author fullname="S. Dronia" initials="S." surname="Dronia"/>
    <author fullname="M. Scurtescu" initials="M." surname="Scurtescu"/>
    <date month="August" year="2013"/>
    <abstract>
      <t>This document proposes an additional endpoint for OAuth authorization servers, which allows clients to notify the authorization server that a previously obtained refresh or access token is no longer needed. This allows the authorization server to clean up security credentials. A revocation request will invalidate the actual token and, if applicable, other tokens based on the same authorization grant.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7009"/>
  <seriesInfo name="DOI" value="10.17487/RFC7009"/>
</reference>
<reference anchor="RFC7662">
  <front>
    <title>OAuth 2.0 Token Introspection</title>
    <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
    <date month="October" year="2015"/>
    <abstract>
      <t>This specification defines a method for a protected resource to query an OAuth 2.0 authorization server to determine the active state of an OAuth 2.0 token and to determine meta-information about this token. OAuth 2.0 deployments can use this method to convey information about the authorization context of the token from the authorization server to the protected resource.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7662"/>
  <seriesInfo name="DOI" value="10.17487/RFC7662"/>
</reference>



    </references>

</references>



  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA61a63LbNhb+z6fAav+0O6ZiOVdrOu26idM4m8Su7Wyn7XQk
iIRkJBTBBUgrapo+yz7LPtmeC0CClJKmO+tppxQIHJz7+c5h0zRNal0XaipG
5ydNfSO+VdIqK66Uc9qU4rFVuSprLQvxnZVlLa63lRJLY0V9o8TJCt6J09Ka
oljj44U1tclMMUrkYmHVLZA9Ob0QRHqU5CYr5Rruyq1c1ulbeatlmUpVpUbC
htTxpWnWXpoe3k9yWcORo8OjB+lkkk7uJxksrIzdToWr80RXdipq27j66PDw
+PAocc1irYlQDbxOxdnp9dPE1bLMZ7IwpaLdKqn0NBECuJ2KrXLw6IytrVq6
9vd23f1E/ozFEyn8K4Qu4cWrsfgHyUBLLFp/zdiVLPWvsgZupuK5tBtdHoiz
MhuLL87Kp4XZfEn71FrqYgok3N91uYTlSm7HUidJaewaTt8qvPry6eO7d+8e
+8cHD+91j/cP/eOjo/th9XgyoVWwQPr4/PJ0SlcFc19/2n60VdqVqqfipq4r
N71zBywhayuzt8qOtaqXYxDvDhj1Tt+eSDRVLdG08kTvENHYnIfp3QktOmW1
ciC6YSYF6KhWtlR1+gRpD13mY1egv+Dpzlz4l+4z1z6TJchBX+EPwanC44MH
R9NkPB4nSZqmQi4cKqNOkusb7QTooSEd5mqpS+UoQHoxteveYkUxVX9WTIkv
wJBfjoVAy0UHC1U7IUs0M4StvdWZEuD/jcJFYiB19bZQgQ2ZZcAIeP5bVcKN
1jSrG74ZCHCQZ2a9hngRmxsN5yqrHNItV2IhnSpAOtqbFRr5kw7eooOT1lGw
TPJP1oE1phZmyTHqdbfWeV6oJPkr2tmavMnwBGryDxXQ6pdZRTYv1S0IE7h2
pEpTIUVQsde66LTuxPv3ISY+fACFXu3ZAqpC/SGZtQ9gopurqjBb5Aulk7XY
kCGMsKpxSqh32tWoqYEuWOANUV3WaIXSC3oDagL3vQVjVMYFbkFfGm5ANWvi
qd6Kt2o7/pSzzTmLLsjM88hFdn2G/MO1DrLXNd6/95nlw4dPuwmQ/64jbdW/
gDQbBhynMiWoZWFyrVipz6/OXwmzeKOy2vEdmLLgjkxaSAK5AFVY8ez6+gJM
B+RBhX4f5jPYB/piqXOx2CI3JB4oJZIvN3BbCX6HFsW9Xk7OC8GedMAdwKYl
cHrDcsNvll+jZ7pKkWseCAxPWoeyZtiqcPEPYGQh27hT78CGcDWVG2lzf+0e
giwSphQQCWh3VP0byDvwRpV5ZTRxqUGn+S2GmiODG3S38Bq1EsmfmXKpV41l
NjHOLsEs2ip23BeyXDWQRDngwK/ExlgInNHL11fXowP+r3h1Ts+Xp9+/Prs8
fYLPV89OXrxoHxK/4+rZ+esXT7qn7uTj85cvT1894cOwKnpLyejlyY/wBl1l
dH5xfXb+6uTFCPQE0sVOjm4DEbZQqEJlIR/VYHzpkly5zOoF/IAz3z6++M+/
J/dAfX8B/R1NJqg//vFo8vAe/NiAsfg2UxZb/xNcepvIqoIIQCqyKMATK11D
EjhArbobsynFjbIK9Pi3n1Ezv0zFV4usmtz72i+gwL3FoLPeIulsd2XnMCtx
z9Kea1pt9tYHmu7ze/Jj73fQe7T41TeU49PJo2++TtB5OujHHhNnEspOSw0x
q900SX7//XdRq3d1EicjXE2SkzZMKHGqUi4K8uR+7BaQQd0wmYFl5iG/j2nz
DDe7OZnTH6F1XplbqgmDg66pKkB5Kqf1kGDPSgrK1t/GXJd48XEcSbEMoEdR
NQu4+qYfbqIpc9DGXnZnvHPcE85r7Y2DC94D1BiFk6OpeE9YZRSRgMWfR/H5
0S8HO5v8PS0BeNs70q3DG876M0pSM8Y//pZKQi4P9GkvZFPZFPWs0EsFlVHN
nIKriNXR8eHhKNraS3ezkKlwY8CTEGZj9U6uq0KNQeY7Oj7eJcTPOmvjsy4z
qITW3CSNVTLHNLSxuu4L5fe5WaXsrAMBM/YhvBU7hpE/8IH++8ErvX8HQ1K8
hYyBD5odCR89PXiC+lA3bvRLguQ+cHjM99kBHJXKNNRGuUVUAJgT4IULNW8H
CMzZaD4K3mwwHrBgYqKsENeKW1lAgQYChD+coAQGnY/Ealk3FgtrDASotjBV
2LCCqlbgO0R0kArakpQLZhmiZ/4xLwnSIPqCrApnSuDe6oyZIp41gRkoycbi
fQQ+S873UGgJPbAO8KL9PhalgIEHzQ8o6wtP9YBKC2KNK/H68gUjx0HtBk/i
uAYsWRtT4M3cU0mCc16LCP4wmXgsioRwDwGtfB8IRfaHfrrDHic2n3LSAHvo
WPCEDklmsgzoi4h/0qvZFJ4I4DNTKImA5myJjQ1djub1lsTN89ES2FajOew6
BaNvhWvITZZNGA60eE+XWdHk6I7RxTqfB8REOZ9tTpQpvuZ8ZZtg0S+9EMCp
V2yAl+BPtdQlMw9mmnfZj81PNeYzr/eCIQ6LhWe1Eh9oXrohpRqFG4si7VZc
4A/CvYZEM+7K5iVzHDc3usS9LoLSjeu1V/OTGKhOaeNXEMxfz4eNxUaj8Kaa
C7iGXDTUwfGwrHQawpTWqweYzEZetSqfsV92WZOS5ShOTESBy0Obv2ILkNIW
w54E3XJ4CzliACEYWb0Ky7hgqTbYP9N+NGzr5wqbj9dlG0DdetiNRIAPs9Y1
ri6tWXNXGlx1HtigFMsRELshRBU2Er6jRkdAf496+NC4D68mxE564LQqIFuB
z+l85neSOmKlDlWBDsPZOu54drHxbs7f0aNelZhP6SxklyUk2DJTPS9lfSDE
+URctzmYO7gd6BLXMPSRrTw6DnWavawXkVRbzdvZ4eTZTz8++uHh90dPHz1/
+OTuxfF3xz9NXj24vuZD0FdB8+Jm7Hg8PDpKDyfXh4dT+ucn3venHDd6F4KC
++DR3pJM1gnAnlTtcxB3376F5laPrNaZl2NieLyNET4K6Q+ATAWPQBkSQQqU
ofpqLNrQrWArAoUOoTa1O1e+j7w/nmAt9t36vWOcaMSVHUWosB3fhr4mtL9U
wUMiHJO3DQTmFGlxOglSElMtS50I2G2AGGvo8ZE5FLuz167YDAGAW4HDTGYc
n3DMAFgByu+6oqCKYozobbuS2YuUXVtQ1tgplHFppQChMTGkXbhrXjZFEQRe
QylkQmxNHNGUhqmlhYZUgnAkztA+WOOI80EPoqp1VW89gqN0jZSdXPNFHsn0
8sAQBoQ+18WZCUxRgA/0gFe/3O1VPeIb6LtaKh6hRH1cSGj+TW9C1F0wFmeQ
mAHtmk2frQ2Qgh5IQ4iVCBTx4tKUKQQkqHtVUtqy8TiCGn4FrRZkqMFk6Yyg
ByZgApvxfMoLhO8aDz9jl/HK8+bpaq+r4RqHubm1RXQKicKxnDa0UwI/CUdf
IVgRHcCRwRCbdOWI0nWrmt3pXRhT+SFVfxDVQXRI1mqDxAg4IBsdcpArcHuW
RQo+3sKI4YSW8n30Seci0lGSnJeikHUYvnlhXAyFvE7j2GDgEiXAAT5x2Q1Y
2dcJbN5SCHGHs6cBxPHH44LBSfgcA8HU7OrAgGlspnpsUYFj3EVAjYFrjizA
ERpV02zR7g60I8bB94ucM8BedgHNfy7L3t7gRLiGpua7+oOOOD0ThvVcQm+1
V+R+XkdByUFNGMd7GQHuB+MdeCQMkbNe6FWDU2RcAQVk6ASQqmxT+MFsf6gK
IUgTr5POnEGX/uNAN3skfjAB67KhSV0QKv5a0PcLP5PEsPkYMPZB9X9Fxr73
wUA0gn/QxG/fd5re54BQK3ufamRfNyjBDiD6BOgOKMO3JF35iMa8YMz4exHr
JPZ9bvpIEFOqjyXr3RHT/4LCPkOWNhNi8XNd9YswI3q3R5jDshmBZb9jMHGA
ZIzDAch0UPCyG4oqSkP03YWwR9+wH7Glov61i8WDuI2nkoC1aA4UZr1hYz/R
kxOfWgvu8AwiAkcDPsNHUd44X7bRUxVtxrHEoikksNDD9f7a8DGTMEr4TCep
EDKuyg9A/AKrPj6ytPDQlG9Ls+FPFQvTYORDKApAZQT3a+8xS6kLmunMofJA
L5KZVal/Vfmc554nr05w6OmgivPcww2rVqgMaBuN30ADmtyd2fa/F11To+xP
IZr7TTylpMt/v4l/Evz6U3+/AZG0+xO9X5/5R0Si/70BiAxE+VxOnoQ5Gyjk
t098W/PQKnxW61SERC5De0Y66ev+MzkBQ0J/0FhM+ENjxo0KZ/7GESJcbKlL
gA6k3rLHxfV+TR9KfV3z3yO4KXaQj2vAxbcoUUAu7da2RSjMSli56SuC21uu
U/0jYfIzGKpx5EZTx95nTh/FxLxreILPF+XaZYVxDYjrmc8wP3y80OzWrFBM
SwghOLqQ2VuMMEzRLfIDfIvt2wB3QV4BKoAuBeK44ALeC8YRXuCWUBOyZQ9h
K8E1ewoOcOjLpv9EDBp4/sP1YHobbMUjORomN7km//KgfxuQEF6KzwGvDs1o
1ZtWo9hP4SfIllgLZgNVPxXJlL6NiaJzXlh9K7M/8k2sbQvIT2tKjFYVbIYb
zLUIrpb80T0XpqmRzEdkiFETOqL36ng+278XtG2ozATp/6w/Y+ozNtclpnjY
5+jrsUIoSInvvw+rNxZ3JQAA

-->

</rfc>

