<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-skyfire-oauth-kyapay-token-exchange-03" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title>KYAPay Token Exchange</title>
    <seriesInfo name="Internet-Draft" value="draft-skyfire-oauth-kyapay-token-exchange-03"/>
    <author initials="A." surname="Agarwal" fullname="Ankit Agarwal">
      <organization>Skyfire Systems Inc.</organization>
      <address>
        <email>ankit_agarwal@yahoo.com</email>
        <uri>https://skyfire.xyz</uri>
      </address>
    </author>
    <author initials="M." surname="Jones" fullname="Michael B. Jones">
      <organization>Self-Issued Consulting</organization>
      <address>
        <email>michael_b_jones@hotmail.com</email>
        <uri>https://self-issued.info/</uri>
      </address>
    </author>
    <author initials="A." surname="Hingnikar" fullname="Abhishek Hingnikar">
      <organization>WorkOS</organization>
      <address>
        <email>abhishek@hingnikar.com</email>
      </address>
    </author>
    <author initials="J." surname="Hickman" fullname="Jeffrey Hickman">
      <organization>Ory</organization>
      <address>
        <email>jhickman.it@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Security</area>
    <workgroup>Web Authorization Protocol</workgroup>
    <keyword>agent</keyword>
    <keyword>identity</keyword>
    <keyword>agentic</keyword>
    <keyword>payment</keyword>
    <keyword>commerce</keyword>
    <abstract>
      <?line 124?>

<t>This specification describes how KYAPay tokens can be exchanged for
OAuth access tokens
to dynamically grant agents access to resources they need
to accomplish their mission.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://skyfire-xyz.github.io/draft-skyfire-oauth-kyapay-token-exchange/draft-skyfire-oauth-kyapay-token-exchange.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-skyfire-oauth-kyapay-token-exchange/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/skyfire-xyz/draft-skyfire-oauth-kyapay-token-exchange"/>.</t>
    </note>
  </front>
  <middle>
    <?line 132?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>KYAPay tokens <xref target="I-D.skyfire-oauth-kyapay-token"/>
are used by agents to identify themselves,
the principal they are acting on behalf of,
their payment capabilities,
their authorized scope of action or mission,
and their intended audience.
Agents may need access to resources to accomplish their mission.
This specification describes how an agent can present a KYAPay token
to obtain an OAuth access token granting access to a resource
that it needs to accomplish its mission.</t>
      <section anchor="use-cases-for-kyapay-token-exchange">
        <name>Use Cases for KYAPay Token Exchange</name>
        <t>Enabling agents to create accounts and/or log in to accounts
on behalf of their human principals is a design goal.
To achieve this, systems can utilize a token exchange workflow.
In this process, a Security Token Service (STS), Identity Provider (IdP),
or OAuth Authorization Server verifies incoming KYA tokens
and extracts claims associated with the human principal, such as email addresses.
The authorization server then performs a token exchange,
swapping the KYA token for a standard OAuth Access Token,
which the agent subsequently uses to interact with the target service.
Crucially, this architecture allows the service to know
that the agent is acting on behalf of the user,
making it possible to differentiate between
direct, human-present sessions and human-initiated, agentic sessions
for authorization, auditing, and security purposes.</t>
        <t>One example use case is to exchange a KYAPay token for an OAuth access token
for a Model Context Protocol <xref target="MCP"/> service
when the agent needs to use the MCP service to accomplish its goals.</t>
        <t>Early production deployments of KYAPay tokens are described at https://kyapay.org.</t>
      </section>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<section anchor="roles">
        <name>Roles</name>
        <t>The roles defined in <xref target="I-D.skyfire-oauth-kyapay-token"/> are incorporated into this specification.</t>
      </section>
    </section>
    <section anchor="kyapay-token-exchange">
      <name>KYAPay Token Exchange</name>
      <t>The KYAPay token contains identifying information for both
the principal on whose behalf the request is being made
(in the Human Identity (<tt>hid</tt>) claim) and
the agent that is authorized to act on behalf of the principal
(in the Agent Platform Identity (<tt>apd</tt>) claim and
the Agent Identity (<tt>aid</tt>) claim).</t>
      <t>This specification defines two methods of exchanging KYAPay tokens for access tokens:
a direct method and
a method using a
Client ID Metadata Document (CIMD) <xref target="I-D.ietf-oauth-client-id-metadata-document"/>.
It also defines an authorization grant profile identifier,
which authorization servers and clients use
to declare that they support KYAPay Token Exchange,
and an optional authorization server metadata parameter
listing supported KYAPay token issuers.</t>
      <t>The steps when successfully exchanging a KYAPay token for an access token
and using it with the protected resource are:</t>
      <ol spacing="normal" type="1"><li>
          <t>The client retrieves the OAuth protected resource metadata document <xref target="RFC9728"/>.</t>
        </li>
        <li>
          <t>The client determines from the resource metadata what authorization server(s)
can be used for the token exchange.</t>
        </li>
        <li>
          <t>The client chooses an authorization server and retrieves its metadata <xref target="RFC8414"/>.</t>
        </li>
        <li>
          <t>The client determines from the authorization server metadata whether
the authorization server supports KYAPay Token Exchange, per <xref target="as-metadata"/>.
It also may be able to determine if the authorization server
accepts tokens from specific KYAPay token issuers.</t>
        </li>
        <li>
          <t>The client makes a token exchange <xref target="RFC8693"/> request to the authorization server,
passing the KYAPay token as the <tt>subject_token</tt> value,
the <tt>subject_token_type</tt> value of <tt>urn:ietf:params:oauth:token-type:kyapay</tt>, and
passing the resource identifier <xref target="RFC8707"/> as the "resource" value.</t>
        </li>
        <li>
          <t>The authorization server returns an access token for the resource to the client
using information from the KYAPay token to create the access token.
Note that this may be a bearer access token <xref target="RFC6750"/>
or a DPoP-bound access token <xref target="RFC9449"/>.
The access token will contain or reference sufficient information
for the protected resource to be able to provision access for the client,
which may include dynamic account creation.</t>
        </li>
        <li>
          <t>The client uses the access token to make an HTTP resource request to the resource.</t>
        </li>
        <li>
          <t>The resource responds to the resource request providing the requested information.</t>
        </li>
      </ol>
      <t>Note that the ability to use information in the KYAPay token
to dynamically provision access to the resource by the agent is critical
to enable seamless agentic access to resources for the user.
This obviates the need to pre-provision an account for the user at every resource
that their agent might access -- a process that would not scale.</t>
    </section>
    <section anchor="direct-kyapay-token-exchange-method">
      <name>Direct KYAPay Token Exchange Method</name>
      <t>The direct KYAPay Token Exchange method uses a Client Identifier that
is constructed directly from information in the KYA Token.
Its value contains
the token issuer,
the token originator,
the agent platform identifier, and
the agent identity identifier.
Specifically, it is the string concatenation of
- the string literal "kyapay:",
- the <tt>iss</tt> claim value,
- the string literal "|",
- the <tt>ori</tt> claim value,
- the string literal "|",
- the <tt>apd</tt> claim's <tt>id</tt> value,
- the string literal "|", and
- the <tt>aid</tt> claim's <tt>id</tt> value.</t>
      <t>If the KYAPay token has no <tt>ori</tt> claim,
that part is the empty string,
so the Client ID always has four parts separated by "|".</t>
      <t>An example such Client ID value is:</t>
      <artwork><![CDATA[
kyapay:https://app.skyfire.xyz|https://app.skyfire.xyz|a283ced5-95be-4abe-81aa-51552e8876ad|7d889702-7b6a-46cb-9bdd-10e83d17b18d
]]></artwork>
      <t>This requires the authorization server to recognize and accept these Client IDs
without client pre-registration (as described in <xref section="2" sectionFormat="of" target="RFC6749"/>)
or dynamic client registration <xref target="RFC7591"/>.
There is precedent for authorization servers using non-pre-registered clients
based on the syntax of their Client Identifiers;
the Client ID Metadata Document (CIMD) <xref target="I-D.ietf-oauth-client-id-metadata-document"/>
specification uses unregistered Client IDs,
the OpenID Federation <xref target="OpenID.Federation"/>
specification uses unregistered Client IDs,
and the OpenID for Verifiable Presentations <xref target="OpenID4VP"/>
specification uses unregistered Client IDs.
The OpenID4VP specification also uses Client ID prefixes,
as this specification does.</t>
      <t>The token exchange uses <xref target="RFC8693"/> and is performed as follows:</t>
      <ul spacing="normal">
        <li>
          <t>The "none" client authentication method <xref target="RFC7591"/> is used.</t>
        </li>
        <li>
          <t>An HTTP POST is made to the authorization server's token endpoint.</t>
        </li>
        <li>
          <t>The <tt>grant_type</tt> value is <tt>urn:ietf:params:oauth:grant-type:token-exchange</tt>.</t>
        </li>
        <li>
          <t>The <tt>client_id</tt> value is the Client ID constructed as described above.</t>
        </li>
        <li>
          <t>The <tt>subject_token</tt> value is the KYAPay token being exchanged.</t>
        </li>
        <li>
          <t>The <tt>subject_token_type</tt> value is <tt>urn:ietf:params:oauth:token-type:kyapay</tt>.</t>
        </li>
        <li>
          <t>The <tt>resource</tt> value is the URL of the protected resource
that the resulting token is intended for.</t>
        </li>
        <li>
          <t>The <tt>requested_token_type</tt> parameter <bcp14>MAY</bcp14> be included;
if included, its value is <tt>urn:ietf:params:oauth:token-type:access_token</tt>.</t>
        </li>
        <li>
          <t>No <tt>actor_token</tt> or <tt>actor_token_type</tt> parameters are included.</t>
        </li>
      </ul>
      <t>The following is a non-normative example of a POST request
to perform a direct KYAPay token exchange for an access token:</t>
      <artwork><![CDATA[
POST /token HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded

grant_type=urn:ietf:params:oauth:grant-type:token-exchange
&client_id=kyapay:https://app.skyfire.xyz|https://app.skyfire.xyz|a283ced5-95be-4abe-81aa-51552e8876ad|7d889702-7b6a-46cb-9bdd-10e83d17b18d
&subject_token=*KYAPay Token*
&subject_token_type=urn:ietf:params:oauth:token-type:kyapay
&resource=https://mcp.acme.example/
&requested_token_type=urn:ietf:params:oauth:token-type:access_token
]]></artwork>
    </section>
    <section anchor="kyapay-token-exchange-method-using-client-id-metadata-document-cimd">
      <name>KYAPay Token Exchange Method using Client ID Metadata Document (CIMD)</name>
      <t>This section describes a KYAPay token exchange method using a
Client ID Metadata Document (CIMD) <xref target="I-D.ietf-oauth-client-id-metadata-document"/>.
This method uses the CIMD URL as the Client ID.</t>
      <t>As described in <xref section="5" sectionFormat="of" target="I-D.ietf-oauth-client-id-metadata-document"/>
(Client Authentication),
clients that are capable of maintaining private key material and
performing client authentication <bcp14>SHOULD</bcp14> do so with an acceptable
method, such as the private_key_jwt <xref target="OpenID.Core"/> <xref target="RFC7523"/> client authentication method,
as updated by <xref target="RFC10070"/>.
Otherwise, the "none" client authentication method <xref target="RFC7591"/> is used,
and the <tt>client_id</tt> parameter is the CIMD URL.</t>
      <t>The token exchange uses <xref target="RFC8693"/> and is performed as follows:</t>
      <ul spacing="normal">
        <li>
          <t>An HTTP POST is made to the authorization server's token endpoint.</t>
        </li>
        <li>
          <t>The <tt>grant_type</tt> value is <tt>urn:ietf:params:oauth:grant-type:token-exchange</tt>.</t>
        </li>
        <li>
          <t>The <tt>subject_token</tt> value is the KYAPay token being exchanged.</t>
        </li>
        <li>
          <t>The <tt>subject_token_type</tt> value is <tt>urn:ietf:params:oauth:token-type:kyapay</tt>.</t>
        </li>
        <li>
          <t>The <tt>resource</tt> value is the URL of the protected resource
that the resulting token is intended for.</t>
        </li>
        <li>
          <t>The <tt>requested_token_type</tt> parameter <bcp14>MAY</bcp14> be included;
if included, its value is <tt>urn:ietf:params:oauth:token-type:access_token</tt>.</t>
        </li>
        <li>
          <t>No <tt>actor_token</tt> or <tt>actor_token_type</tt> parameters are included.</t>
        </li>
      </ul>
      <t>The following is a non-normative example of a POST request
by a CIMD client using the private_key_jwt client authentication method
to perform a KYAPay token exchange for an access token:</t>
      <artwork><![CDATA[
POST /token HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded

grant_type=urn:ietf:params:oauth:grant-type:token-exchange
&subject_token=*KYAPay Token*
&subject_token_type=urn:ietf:params:oauth:token-type:kyapay
&resource=https://mcp.acme.example/
&requested_token_type=urn:ietf:params:oauth:token-type:access_token
&client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer
&client_assertion=*JWT whose iss and sub are the CIMD URL*
]]></artwork>
    </section>
    <section anchor="as-metadata">
      <name>Authorization Server Metadata</name>
      <t>An authorization server declares support for KYAPay token exchange by including the value
<tt>urn:ietf:params:oauth:grant-profile:kyapay</tt>
in its <tt>authorization_grant_profiles_supported</tt> metadata parameter
<xref target="I-D.ietf-oauth-identity-assertion-authz-grant"/>.
An authorization server that includes this value <bcp14>MUST</bcp14> also include
<tt>urn:ietf:params:oauth:grant-type:token-exchange</tt> in <tt>grant_types_supported</tt>.</t>
      <t>Including this value indicates only that the authorization server
implements the processing rules of this specification.
It does not indicate that a token from any particular KYAPay token issuer
will be accepted.</t>
      <t>An authorization server <bcp14>MAY</bcp14> also include the
<tt>kyapay_issuers_supported</tt> metadata parameter <xref target="RFC8414"/>.
The definition of this parameter is:</t>
      <dl newline="true">
        <dt><tt>kyapay_issuers_supported</tt>:</dt>
        <dd>
          <t><bcp14>OPTIONAL</bcp14>.
JSON array containing a list of issuer identifiers of KYAPay token issuers,
as specified in <xref target="I-D.skyfire-oauth-kyapay-token"/>,
that can be used with this authorization server.
Authorization servers <bcp14>MAY</bcp14> choose not to advertise some supported token issuers,
even when this parameter is used.
In some use cases, the set of token issuers will not be enumerable.
The array <bcp14>MAY</bcp14> be empty.</t>
        </dd>
      </dl>
      <t>An authorization server that includes <tt>kyapay_issuers_supported</tt> <bcp14>MUST</bcp14> also include
<tt>urn:ietf:params:oauth:grant-profile:kyapay</tt> in <tt>authorization_grant_profiles_supported</tt>.</t>
    </section>
    <section anchor="client-metadata">
      <name>Client Metadata</name>
      <t>A client can declare support for KYAPay token exchange by including the value
<tt>urn:ietf:params:oauth:grant-profile:kyapay</tt>
in its <tt>authorization_grant_profiles_supported</tt> client metadata parameter
<xref target="I-D.ietf-oauth-identity-assertion-authz-grant"/>,
for example, in its Client ID Metadata Document.
A client that includes this value <bcp14>MUST</bcp14> also include
<tt>urn:ietf:params:oauth:grant-type:token-exchange</tt> in its <tt>grant_types</tt>.</t>
      <t>Clients using the direct method have no client metadata,
so this applies only to clients that publish or register metadata.</t>
    </section>
    <section anchor="kyapay-token-example">
      <name>KYAPay Token Example</name>
      <t>An example decoded set of JWT Header Parameters for a KYAPay token is:</t>
      <artwork><![CDATA[
{
  "alg": "ES256",
  "kid": "BEDD-0",
  "typ": "kya+jwt"
}
]]></artwork>
      <t>An example decoded JWT Claims Set for a KYAPay token is:</t>
      <artwork><![CDATA[
{
  "env": "production",
  "ori": "https://app.skyfire.xyz",
  "itg": "cursor-agent",
  "tsi": "886eef79-4d90-4b8d-81f0-ce5c6c7dac13",
  "tdm": "auth101.dev",
  "hid": {
    "id": "ed0f64ef-3c7b-4df2-8d91-db3c4fb8c80b",
    "email": "example@skyfire.xyz",
    "verifier": "https://app.skyfire.xyz",
    "verified": true
  },
  "aid": {
    "id": "7d889702-7b6a-46cb-9bdd-10e83d17b18d",
    "name": "Buyer 1",
    "creation_ip": "12.50.206.98"
  },
  "apd": {
    "id": "a283ced5-95be-4abe-81aa-51552e8876ad",
    "name": "E2E Test Org 1",
    "email": "example@skyfire.xyz",
    "verifier": "https://app.skyfire.xyz",
    "verified": true
  },
  "scope": "xyz pdq",
  "iat": 1782245616,
  "iss": "https://app.skyfire.xyz",
  "jti": "019ef61d-eb8f-759b-9302-d998b294fcc9",
  "aud": "886eef79-4d90-4b8d-81f0-ce5c6c7dac13",
  "sub": "8fa1438f-8dd0-4e91-abb8-888cdbeb6d5d",
  "exp": 1782245916
}
]]></artwork>
      <t>The KYAPay token is used as the <tt>subject_token</tt> value for the token exchange.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The security considerations defined in <xref target="I-D.skyfire-oauth-kyapay-token"/>
and <xref target="RFC8693"/> apply to this specification.</t>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>The privacy considerations defined in <xref target="I-D.skyfire-oauth-kyapay-token"/>
and <xref target="RFC8693"/> apply to this specification.</t>
      <t>The <tt>kyapay_issuers_supported</tt> value may disclose a set of
KYAPay token issuers that the authorization server trusts.
Clients may need to know, before making a request,
whether a KYAPay token they hold or can obtain will be accepted.
Deployments that consider their issuer relationships sensitive
should take this into account before publishing the list.
As in <xref section="9.4" sectionFormat="of" target="I-D.ietf-oauth-identity-assertion-authz-grant"/>,
issuer lists are not conveyed in <tt>authorization_grant_profiles_supported</tt>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="oauth-uri-registration">
        <name>OAuth URI Registration</name>
        <t>This specification registers the following values in the
IANA "OAuth URI" registry <xref target="IANA.OAuth.Parameters"/>
established by <xref target="RFC6755"/>.</t>
        <section anchor="urnietfparamsoauthtoken-typekyapay">
          <name>urn:ietf:params:oauth:token-type:kyapay</name>
          <ul spacing="normal">
            <li>
              <t>URN: urn:ietf:params:oauth:token-type:kyapay</t>
            </li>
            <li>
              <t>Common Name: KYAPay Token Type</t>
            </li>
            <li>
              <t>Change controller: IETF</t>
            </li>
            <li>
              <t>Specification Document: <xref target="kyapay-token-exchange"/> of this specification</t>
            </li>
          </ul>
        </section>
        <section anchor="urnietfparamsoauthgrant-profilekyapay">
          <name>urn:ietf:params:oauth:grant-profile:kyapay</name>
          <ul spacing="normal">
            <li>
              <t>URN: urn:ietf:params:oauth:grant-profile:kyapay</t>
            </li>
            <li>
              <t>Common Name: Authorization grant profile identifier for KYAPay Token Exchange</t>
            </li>
            <li>
              <t>Change controller: IETF</t>
            </li>
            <li>
              <t>Specification Document: <xref target="as-metadata"/> of this specification</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="oauth-authorization-server-metadata-registration">
        <name>OAuth Authorization Server Metadata Registration</name>
        <t>This specification registers the following parameter in the
IANA "OAuth Authorization Server Metadata" registry <xref target="IANA.OAuth.Parameters"/>
established by <xref target="RFC8414"/>.</t>
        <section anchor="kyapayissuerssupported">
          <name>kyapay_issuers_supported</name>
          <ul spacing="normal">
            <li>
              <t>Metadata Name: kyapay_issuers_supported</t>
            </li>
            <li>
              <t>Metadata Description: JSON array containing a list of issuer identifiers of
KYAPay token issuers that can be used with this authorization server</t>
            </li>
            <li>
              <t>Change Controller: IETF</t>
            </li>
            <li>
              <t>Specification Document(s): <xref target="as-metadata"/> of this specification</t>
            </li>
          </ul>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC8414">
          <front>
            <title>OAuth 2.0 Authorization Server Metadata</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <date month="June" year="2018"/>
            <abstract>
              <t>This specification defines a metadata format that an OAuth 2.0 client can use to obtain the information needed to interact with an OAuth 2.0 authorization server, including its endpoint locations and authorization server capabilities.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8414"/>
          <seriesInfo name="DOI" value="10.17487/RFC8414"/>
        </reference>
        <reference anchor="RFC8693">
          <front>
            <title>OAuth 2.0 Token Exchange</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="A. Nadalin" initials="A." surname="Nadalin"/>
            <author fullname="B. Campbell" initials="B." role="editor" surname="Campbell"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="C. Mortimore" initials="C." surname="Mortimore"/>
            <date month="January" year="2020"/>
            <abstract>
              <t>This specification defines a protocol for an HTTP- and JSON-based Security Token Service (STS) by defining how to request and obtain security tokens from OAuth 2.0 authorization servers, including security tokens employing impersonation and delegation.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8693"/>
          <seriesInfo name="DOI" value="10.17487/RFC8693"/>
        </reference>
        <reference anchor="RFC8707">
          <front>
            <title>Resource Indicators for OAuth 2.0</title>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
            <date month="February" year="2020"/>
            <abstract>
              <t>This document specifies an extension to the OAuth 2.0 Authorization Framework defining request parameters that enable a client to explicitly signal to an authorization server about the identity of the protected resource(s) to which it is requesting access.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8707"/>
          <seriesInfo name="DOI" value="10.17487/RFC8707"/>
        </reference>
        <reference anchor="RFC9728">
          <front>
            <title>OAuth 2.0 Protected Resource Metadata</title>
            <author fullname="M.B. Jones" initials="M.B." surname="Jones"/>
            <author fullname="P. Hunt" initials="P." surname="Hunt"/>
            <author fullname="A. Parecki" initials="A." surname="Parecki"/>
            <date month="April" year="2025"/>
            <abstract>
              <t>This specification defines a metadata format that an OAuth 2.0 client or authorization server can use to obtain the information needed to interact with an OAuth 2.0 protected resource.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9728"/>
          <seriesInfo name="DOI" value="10.17487/RFC9728"/>
        </reference>
        <reference anchor="I-D.skyfire-oauth-kyapay-token">
          <front>
            <title>KYAPay Token</title>
            <author fullname="Ankit Agarwal" initials="A." surname="Agarwal">
              <organization>Skyfire Systems Inc.</organization>
            </author>
            <author fullname="Michael B. Jones" initials="M. B." surname="Jones">
              <organization>Self-Issued Consulting</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   This document defines a token format for agent identity and payment
   tokens in JSON Web Token (JWT) format.  Authorization servers and
   resource servers from different vendors can leverage this token
   format to consume identity and payment tokens in an interoperable
   manner.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-skyfire-oauth-kyapay-token-03"/>
        </reference>
        <reference anchor="I-D.ietf-oauth-client-id-metadata-document">
          <front>
            <title>OAuth Client ID Metadata Document</title>
            <author fullname="Aaron Parecki" initials="A." surname="Parecki">
              <organization>Okta</organization>
            </author>
            <author fullname="Emelia Smith" initials="E." surname="Smith">
              <organization>independent</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   This specification defines a mechanism through which an OAuth client
   can identify itself to authorization servers, without prior dynamic
   client registration or other existing registration.  This is through
   the usage of a URL as a client_id in an OAuth flow, where the URL
   refers to a document containing the necessary client metadata,
   enabling the authorization server to fetch the metadata about the
   client as needed.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-oauth-client-id-metadata-document-03"/>
        </reference>
        <reference anchor="I-D.ietf-oauth-identity-assertion-authz-grant">
          <front>
            <title>Identity Assertion JWT Authorization Grant</title>
            <author fullname="Aaron Parecki" initials="A." surname="Parecki">
              <organization>Okta</organization>
            </author>
            <author fullname="Karl McGuinness" initials="K." surname="McGuinness">
              <organization>Independent</organization>
            </author>
            <author fullname="Brian Campbell" initials="B." surname="Campbell">
              <organization>Ping Identity</organization>
            </author>
            <date day="30" month="October" year="2026"/>
            <abstract>
              <t>   This specification provides a mechanism for an application to use an
   identity assertion to obtain an access token for a third-party API by
   coordinating through an identity provider that the downstream
   Resource Authorization Server already trusts for single sign-on
   (SSO), using OAuth 2.0 Token Exchange (RFC 8693) and the JWT Profile
   for OAuth 2.0 Authorization Grants (RFC 7523).  This pattern is
   informally referred to as Cross-App Access (XAA).

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-oauth-identity-assertion-authz-grant-06"/>
        </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 anchor="sec-informative-references">
        <name>Informative References</name>
        <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="RFC6755">
          <front>
            <title>An IETF URN Sub-Namespace for OAuth</title>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
            <date month="October" year="2012"/>
            <abstract>
              <t>This document establishes an IETF URN Sub-namespace for use with OAuth-related specifications. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6755"/>
          <seriesInfo name="DOI" value="10.17487/RFC6755"/>
        </reference>
        <reference anchor="RFC7523">
          <front>
            <title>JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <author fullname="C. Mortimore" initials="C." surname="Mortimore"/>
            <date month="May" year="2015"/>
            <abstract>
              <t>This specification defines the use of a JSON Web Token (JWT) Bearer Token as a means for requesting an OAuth 2.0 access token as well as for client authentication.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7523"/>
          <seriesInfo name="DOI" value="10.17487/RFC7523"/>
        </reference>
        <reference anchor="RFC7591">
          <front>
            <title>OAuth 2.0 Dynamic Client Registration Protocol</title>
            <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="M. Machulak" initials="M." surname="Machulak"/>
            <author fullname="P. Hunt" initials="P." surname="Hunt"/>
            <date month="July" year="2015"/>
            <abstract>
              <t>This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during registration.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7591"/>
          <seriesInfo name="DOI" value="10.17487/RFC7591"/>
        </reference>
        <reference anchor="RFC9449">
          <front>
            <title>OAuth 2.0 Demonstrating Proof of Possession (DPoP)</title>
            <author fullname="D. Fett" initials="D." surname="Fett"/>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="T. Lodderstedt" initials="T." surname="Lodderstedt"/>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="D. Waite" initials="D." surname="Waite"/>
            <date month="September" year="2023"/>
            <abstract>
              <t>This document describes a mechanism for sender-constraining OAuth 2.0 tokens via a proof-of-possession mechanism on the application level. This mechanism allows for the detection of replay attacks with access and refresh tokens.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9449"/>
          <seriesInfo name="DOI" value="10.17487/RFC9449"/>
        </reference>
        <reference anchor="RFC10070">
          <front>
            <title>Updates to OAuth 2.0 JSON Web Token (JWT) Client Authentication and Assertion-Based Authorization Grants</title>
            <author fullname="M.B. Jones" initials="M.B." surname="Jones"/>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <author fullname="C. Mortimore" initials="C." surname="Mortimore"/>
            <author fullname="F. Skokan" initials="F." surname="Skokan"/>
            <date month="November" year="2026"/>
            <abstract>
              <t>This document updates RFCs 7521, 7522, 7523, and 9126 with respect to the treatment of audience values in OAuth 2.0 Client Assertion Authentication and Assertion-based Authorization Grants to address a security vulnerability identified in the previous requirements for those audience values in multiple OAuth 2.0 specifications.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="10070"/>
          <seriesInfo name="DOI" value="10.17487/RFC10070"/>
        </reference>
        <reference anchor="MCP" target="https://modelcontextprotocol.io/specification/2026-07-28">
          <front>
            <title>Model Context Protocol Specification</title>
            <author>
              <organization>Anthropic and the Model Context Protocol Contributors</organization>
            </author>
            <date year="2026" month="July"/>
          </front>
        </reference>
        <reference anchor="OpenID.Core" target="https://openid.net/specs/openid-connect-core-1_0.html">
          <front>
            <title>OpenID Connect Core 1.0 incorporating errata set 2</title>
            <author initials="N." surname="Sakimura" fullname="Nat Sakimura">
              <organization/>
            </author>
            <author initials="J." surname="Bradley" fullname="John Bradley">
              <organization/>
            </author>
            <author initials="M. B." surname="Jones" fullname="Michael B. Jones">
              <organization/>
            </author>
            <author initials="B. de" surname="Medeiros" fullname="Breno de Medeiros">
              <organization/>
            </author>
            <author initials="C." surname="Mortimore" fullname="Chuck Mortimore">
              <organization/>
            </author>
            <date year="2023" month="December" day="15"/>
          </front>
        </reference>
        <reference anchor="OpenID.Federation" target="https://openid.net/specs/openid-federation-1_0.html">
          <front>
            <title>OpenID Federation 1.0</title>
            <author initials="R." surname="Hedberg" fullname="Roland Hedberg">
              <organization/>
            </author>
            <author initials="M. B." surname="Jones" fullname="Michael B. Jones">
              <organization/>
            </author>
            <author initials="A. Å." surname="Solberg" fullname="Andreas Åkre Solberg">
              <organization/>
            </author>
            <author initials="J." surname="Bradley" fullname="John Bradley">
              <organization/>
            </author>
            <author initials="G. D." surname="Marco" fullname="Giuseppe De Marco">
              <organization/>
            </author>
            <author initials="V." surname="Dzhuvinov" fullname="Vladimir Dzhuvinov">
              <organization/>
            </author>
            <date year="2026" month="February"/>
          </front>
        </reference>
        <reference anchor="OpenID4VP" target="https://openid.net/specs/openid-4-verifiable-presentations-1_0.html">
          <front>
            <title>OpenID for Verifiable Presentations</title>
            <author initials="O." surname="Terbu" fullname="Oliver Terbu">
              <organization/>
            </author>
            <author initials="T." surname="Lodderstedt" fullname="Torsten Lodderstedt">
              <organization/>
            </author>
            <author initials="K." surname="Yasuda" fullname="Kristina Yasuda">
              <organization/>
            </author>
            <author initials="D." surname="Fett" fullname="Daniel Fett">
              <organization/>
            </author>
            <author initials="J." surname="Heenan" fullname="Joseph Heenan">
              <organization/>
            </author>
            <date year="2025" month="July"/>
          </front>
        </reference>
        <reference anchor="IANA.OAuth.Parameters" target="http://www.iana.org/assignments/oauth-parameters">
          <front>
            <title>OAuth Parameters</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
      </references>
    </references>
    <?line 519?>

<section numbered="false" anchor="document-history">
      <name>Document History</name>
      <t>[[ to be removed by the RFC Editor before publication as an RFC ]]</t>
      <t>-03</t>
      <ul spacing="normal">
        <li>
          <t>Updated the Client ID Metadata Document section reference for -03.</t>
        </li>
        <li>
          <t>Added the required <tt>hid.id</tt> sub-claim to the example KYAPay token.</t>
        </li>
        <li>
          <t>Removed the case of a KYAPay token with no <tt>apd</tt> claim from the direct method's Client ID, since <tt>apd</tt> is <bcp14>REQUIRED</bcp14> in KYA and KYA-PAY tokens.</t>
        </li>
        <li>
          <t>Cited RFC 10070, which updates the audience rules of RFC 7523 for private_key_jwt client authentication.</t>
        </li>
      </ul>
      <t>-02</t>
      <ul spacing="normal">
        <li>
          <t>Reworked to use OAuth 2.0 Token Exchange <xref target="RFC8693"/>.
Both direct exchange of a KYAPay token for an access token
and token exchange for a client using CIMD are defined.</t>
        </li>
        <li>
          <t>Defined the <tt>urn:ietf:params:oauth:grant-profile:kyapay</tt> authorization grant profile
for authorization server and client metadata,
and the optional <tt>kyapay_issuers_supported</tt> authorization server metadata parameter.</t>
        </li>
        <li>
          <t>Registered the <tt>urn:ietf:params:oauth:token-type:kyapay</tt> token type,
the <tt>urn:ietf:params:oauth:grant-profile:kyapay</tt> grant profile,
and the <tt>kyapay_issuers_supported</tt> metadata parameter.</t>
        </li>
      </ul>
      <t>-01</t>
      <ul spacing="normal">
        <li>
          <t>Added Abhishek Hingnikar and Jeffrey Hickman as authors.</t>
        </li>
      </ul>
      <t>-00</t>
      <ul spacing="normal">
        <li>
          <t>Initial draft.</t>
        </li>
      </ul>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact initials="A." surname="Safdari" fullname="Ammar Safdari">
        <organization>Skyfire Systems Inc.</organization>
        <address>
      </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+1c63LbRpb+j6fopas2tpegSOpGccYzliU5lseytJacVCqV
khpAU0QEAhg0IJpR9HPfY59l98X2nNMXXAjSVCqzMzW7+RFDQF9On+vXp0/T
dV0nD/NIjFnnLz8cXvAFu0ruRMxOvvhTHt+KjvOMe14m7qFBx/F5Lm6TbDFm
Mg8cJ0j8mM+gb5DxSe7Ku8UkzISb8CKfuncLnvKFm+NwrtDDuf1tRxbeLJQy
TOJ8kULn05Ort4w9YzySCcwSxoFIBfwvzjtd1hFBmCdZyCP84/TwDfyTZPD0
6eot0BYXM09kYycAwsaOn8RSxLKQY5ZnhXCA6G2HZ4KP2aXwiyzMF848ye5u
s6RIx+x74bFDIBWG/4XnQA+7yJI88ZPIuRMLaBiMHeYyfguk4EOINOEY5mXo
4yOscqZb+MlsJjIfZhZxAQQxdhvm08KDZRnmfFn8srUxu2CFMISm9lv8Q7Hs
e1hEGN+yb/ETvp7xMMImr8UXPksj0QNK8D3P/OmYTfM8leOtrcrHLRiOsQjY
JnOgzrSoUNlTpPfCZHN6N2/Zm+azqOM4nPg/dlygRunSYXwX5uzwlmdzHsHb
JLvlsRYQyFENzS4XMhczyU5jvweNhGIAx77XXPV9veDTJCFOMAbCL/mg6evB
KmniMAaNOeux90kspCXkLARSRcTelB8atIho4p5KWYiAHYHqFVEOQimpmakB
rr3rn7H/62mS44dWinCokIbqhfEk2aoyxJuGciru2DsYPQ7veLZECerD+WWF
D7rL66npQpOWY74Xk0kmFjCkfzfj8dKA59miHO3nqWrVC/PXt3YFaG15FnpF
3pDfbMYzdsknAc/CzeQHmiqFsMzQioda6nMv2brL+CxI5rGbTfyteXgXbl0u
4px/GT5T2iPdCinSceIkm8F092SAn94ejXYGO+Zx72DbPO739/Xjwf5whI+n
7nFvte6aFqHIJ/qzH4Vg+W4YuDORc3BC3AWfWKA7aGlt/IfLpRQZ8sPF97+4
txnHDg5Kvk763v7OgX3c7ZePu/pxf3e4bR8PBmZBO7bboN/fp35nRxf4D7gQ
nt2KvNS9WRKICDkovuSpdoBo9TIVfjgJfZLc1rA/3HP7++5wpAZRQeMM+6Ly
Y2frPtlltSu1JwfN3hfRgg1HXYaj0Xtj/4z+c1FbwB0dxvk0S9LQB4sOWD4V
qyY6qggevAlj5xA6To97R0km2lebQIMw6MUipwVK/QJVKBZ+Dv+C8AfXfXJQ
1aV21NA4JTZkOAUb9PrgPaBPmmQcrZ+JDB446HPOhp3K0mHF2+5g6A52W9et
bOcjz8Fy7sJZkfHGp/fJNGZvMh5EYtH41OKoqp/fZCJOWAA8FIEIs6T5/Wha
+HfAYNDIGaypwsW30CFThvskXk5sv1ZOakaWoyMbK6x6K7ys4NmCDXbXaIoi
/lMSoYq8EwHggNunMeYwDgAbSPbf/3GHHimJWoZYw/Zvw0KKNBXsGFgLgTZp
fP8u4kE4CzN2/Mu0uA/j5L5k7c53K4xxFUt33HuRgUlxLxJumgnAOTnxTq5j
MbgT9p3tB2ZT6dc0ywPi9TrtPI/AMWXsSmRe0fh0BfaXA2z8kAQgVHgM8kaL
v2ShBAPh7Acui6Cp3ccQIkBQb0Xe7Pc+ASZPQcAihjiFTvXw42HvHHFb74JD
ZBA5TDheIlu7Emy9xGjg83w+74U85j1otQX+OLyN0WsDv8lVp3bkGldxVnZR
/6ZYOAH0CqbT60E0c1wXAKIn84z7ueNcQSxmNWcKxih9cFtCsmkyZxp4U5CR
zOcx8wQzQClAITpqZu77Qkrd0MnBqBfAJBg0AvlREFG4VJYtGYg8KQCSSnSj
CxYLEWBPaJAAFgSUgO9BSTUkN+TPwgBU3sHQfAouNgkKn3y5Uyf24WF9zHx8
RPzNwFAC5i0MdTC/ioWTBc4+A/RzL2TXQUefZuBPw5RHil7sDVxEz5ogX6Y8
mrBkQm2Bao29gWkp98IozEM9DnzjGtrD1NIHM4JuNBSMk9j1dh0dYaBDCMEF
9h0B9Awgrvui5xwqgmdcca6dr+u4+VXhg7SJKyR3bdiM13QC5ZV4OQ9jbL2s
Ckr0yKKSPG4JBG5AVAFIjQtoUhvi4krJP3vGPkvBjrgE6tB5tO4JHeckBn9C
E1qB+uBKc0FjF6SBcbAFA0TJLfDVzIpfnKocNbumxYxWr0UvGTCNI6PALNlt
wiNgJI4wDcW9gD6h7DKpESTyrchB9r/A7JohxngY7vYmUTLvOacx9YNJEuRR
F9qaPaFe3qXI7kNfsOeXV5cvuuxUozUEG/egrhl7fhpcvOg6sColg/reEbtD
I+WmgX0IC2bII+ChMVnUNcAv6BeA8IiHQD84n8QPgXcBmwPwJbTT4AcstvBB
5lIhcsYDCFyAISXql7CKruiQig4YBkYQGSJKucSYriPnPE2RPJzPkkhCB/SS
A6U8C8xClVoRm7rOHLYDikyluLCfl+KvBTyCFyqksgi0JVxmuSblgIm8EE3r
KCtg2eC5ukowuFUNc0BWBZp8BEIjl2U64KB3cTJX6lzOjj2X/QM1AFqyrjPj
tFUGA0gTUHSMg+g5w8lEZChh1FpP5HMIME4AXszPu4r/JswCBWQgpNP6UxiH
1DPomkyAbeUQC6si6ZJDQRq7NIQ0epcWgBtJjM55jC6ftudIN2g1/C8kVlpl
rnsFJao2f6AoWAWZHx5gJ/D4aPgK4hRxhZ/WSyAVhLyPLqoyaDgPNE6k/4Rn
IP3UBgow3jRKyDlLlEc9bKBXN24QnGpu4Y+KHRiUyR0h9ffIXsP9YzEh1iOf
SffvIEZgpkayztnnyytMEuG/7OM5PX86+ffPp59OjvH58t3hhw/2wdEtLt+d
f/5wXD6VPY/Oz85OPh6rzvCW1V45nbPDHzpKoJ3zi6vT84+HHzrk61CbzTaQ
lgpsg4hOJgE6hZbOpVOuH/q8Obr4r/8c7IBw/gX2bMPB4AAkpP4YDfZ34A8U
k5otiYHT6k8MkQ7YseAYvdBqMBKGOciki+5CQoSJ2RQUHdj58kfkzE9j9kfP
Twc7f9IvcMG1l4ZntZfEs+U3S50VE1tetUxjuVl73+B0nd7DH2p/G75XXv7x
zxCYBHMHoz//SUU02CIIrS0ZPoLmgRIpvn8dv5AAyy0edQN55ktxXSlsa8Bk
D89ak2CPiqqaVeNGHCK9tAiJnJdJDCTK7L0knzbQEnyZT8GZGB+IXzN0y5J8
pCdwnBkPhPM8VPb+joKMDXPPb6ZhcPNChaUXqGlO6RUUhpBVTEW+IF/2upYk
OxGBKHYR8RxXUZ2Rp3ZGO6FqXW1UIau3Ak6jQMFrzRMGyHyaBORzNJt1DK64
H/KPVSw9dgBtkO/X/Ykabv4oJGEd54jSPQw2Vmc63cOOjZ0/Pzo9O36hFWqz
FNHjI8CSnPLedgkIB2vhXMF6cKyTEEKDVooQA5uKw23BX/lKNbNER057BQEs
RGek4+cCAncKOp2366wCxkBOkuLIoGGtMMMsitkdkxPRRu/WDA+qUlNwynJm
sqd0HzBcKsmbIcZBkUwK3M1UZNce9moBD0lVQgoriAOTWSBSIMBgYTTmseMM
egznVgyCj3mGuFLBDRVOW7ralVrX/vCgc4coyPqYAXJiRhKdZMlMW2NzpDmK
oo2tz+UL3FvqrSDtnnDZBKNqOK45rz9NEFAsq5EWFzKqXC+hf0MMrQZTpZut
Zr02gEChESaqVzfW+iFX6B+CVyCKS2s4SBgMaEwGN2XAHW4QnSGShZOVk2J/
1Jw0l9YZ4IqMP1mhqnV2AKIUy5BaM3DvYBuChvG8FCnaSekiLSmmHkoQXk7N
lTbeALj+GRTxmt7esHseFaJr2Fr/eo1nQ7oJur+bIovH6InGZJtyTA5prEIQ
nSOpoHRDsKJJjdXW0uXoFe739zEsKgI7pl1HTWx51SpyUD0gSjbt1yq3nVTz
TTEcSdPWXY2DRhNrfCt3osT3yiSkOx+T3HrAUFoVgv+BZ6gHBbVazLo/PmJX
wtTHF8mF68E+Nmhpi1l3raNXjcnBKSE2U7Edh8oEbT9gqbKYgOKRYlWWh4MY
rrQ4I4UojeqnuEPFzYeZ0/RU/CN9UdECFwzhOSoCYZJHZmOu+EZApq7uakvX
XFCekB2gKN9dXV2UpDVU37y3o1YayjSJ1WYjr39QI9CyglIh6S0BMMsmiCJV
kSJLMAu0MBuYqsJoNNLMrFRzaEuMbJLmLepbT0DwOfbFgURM8pCCzyLsazaG
bTkjIyDcouokUeLd445SsZqSTSRZzPZaomIrrOoAuIECf54tGjkfnQYjWmfh
7TQ3pGB60iRCFOvmSREFLE5gswurEQrLHitE1A5pzwgaqSAerGtoMRT5TAOh
SqeC8zvIStjT5VlBeq4GBIGQkbcLUc2DCEpqn2egs1PGSeXBu5U34JMAVfA8
0W8Ve1IDTisAqwGBzeldpUnPsQddlMcISScoaQEhFvQWKMKSiVjRnkwct/oV
FFVkAKw6yg+PYVOpvt8A2TcaFmuP397x17ILrOupXRB9qy7fSJgzuPlqT2KJ
6R229gbVOZ0s++UpxIs4qZLZVUoKsclyTcxS4K+at+tIZXsl6ObRnC8kDTUB
NaeusBUQGN5ylWAGIoGAw9jmUihxVg6hFCUEwE+5e814k32AnXSvUhvw66r3
fDja9kWw6x7sesLd4fC/0YBzd3ewuzsUo9H+Hg9+3Q9Go4P9/tDd9/a4u7Pn
e+6BFwTuoC9G28Fg3xuMAr2bQdcGY8vVWImch5/cxpTl1NEnJROXFRZJB8Fv
UuTGd6P/yMRtiGcRNN5zLlkt8/DwcClUxmaIoEGfOT8+vsA8pwkRFilXRqKQ
h2fOGPKuMMfAKL0qgDNCe6j2zYmK5XFCGTZNHnS3OxbH44h4E2Xqks76y1zx
kgeRf3DqevI7bc6c+iaTHFgRV8gt2a5cyfK55sPD0knqE8c1598bHOjZ2Xa+
u3jSLCqLbPs2NteEtal7yWGQ2yT8gkctBAOXN+SJMBu8BkimgapIGReIeqMy
1ZQag1VS+heM9CVBhg7oCgBMrYUoOYqsai4dXyrqiOPhnqkH3Q81PLk4v7xi
hPgCsQ6Vf2PwjYiDNAnjvKdpuKGNeA1jw3ArMDa1VRi7nvG5scOpxVxbv2l8
YMnkakCsWS33knthB2rbIZjBai5YpYDsuWL7ABsucHkTYYczGKRByudPH8oM
URPPOqxEcPBOFVLZEF4ezIGKVObReLBGuE1DsLPDH1TWldBu8Aes85rYP7u0
+X3CMhV00lxGIj5CNOM+4AjDeTDN6osmQdJkEml+bR1K02lrg+gIfaKtXrIx
DM8tlQLrNSPa1AbDeAN9NeytJVuiYx8NuKWao4lsDXoD+vAuwZJALnvVWkL8
QEcJoNdXVIMIQTEyxUFf3Pl87iI9bpFFsK1JYIlqmtJsXj3RVqj7v1o7efV3
D9ZET81aXr2sYt6XLS3WrXzJiFR/YxSvbIGWn/a4PxNGIFum3bIBfH2mqh6v
yVifVTOfXw+tJi0rzOGPOeLmK/Tyb59ZJYKqmw/yrjAUuSLe8LaIGlcio100
wSdBh+d64MNarHrRdUxSltwdOgSqXFBGPoPNC25gkCVpFt5jFgPPt8AdCKyA
JvSt7Z52F63xUB+3BAmDuE25UG3/aY4TOYol5ZGyztnjbNcw2/XP87zELVjk
RidRutQQntdFYcIDRRoYOE79qAIRJXKOKcF5KEVXpY5+W1QvMVE1hpZ+P6xL
+neCIf+wOOL/w///vfCPlVRKwW2KzmTJmpa8zrrqMOKfFD/8U8XrKiKyReTr
BtJRqiw4pzFBMVyV8W4f8dXL999f6ePkUKrTROCSqmWo+NaXBCBay6BsGH94
Vj3BodxMa4ZDH09KeypZKT9r6KRncthG6cmOnbU+VB+gGnflQHxHD3BTo+Va
KZtuK6/tCeZN2znnEiBZX9+PEXDV4tXxuvINekOtfBMVaNAOXH9dv8q2SIFQ
phJ0qqvCXF2FkXbWMA7QMoEUqjUpk+ttJ2ohqvhMgxph0so4YlZgtQV5/eVi
idOcsgSUczbzaVRkDoUw98vjBeX5Qr8A9Wg7nnPoaMUTGuOQb13FZwwKVW4i
xc6N0olrfdq3Xur1Y1JKftuSJLvUKhgBb/kwvpcp98XjmqnGzpiZahY8QXp/
ef4R7C2Dxeq0tjoKx8N1nEeNUMlFL1VZmdNLPP3hlv2blr10TUyunkHrk/VK
HUiVu0j2Yct7SWxXJ9MkbqwcCe7RQuCFTGaiUiqwRLq4x9MzVaPWYK1O8jB2
GqthTOGc7OrKQWJVbUh1EIdUYI11DHg9Q1SMo9CZHXFcYwdKR6/RprrVrlGj
J1pxw1eRAW/op3TVnAr6FR+s40DVD9uSAR7b2pB/TN9rjt1/BxfcpdpIHZe7
TFOyZvfZKxn1t3bSxJOKo0ZhHtkaHsPvepnSlN+jTTVZpA9P0FARZVlHnrDa
/jMtPCrkpPNolRi2Q7SWsxHbaucroDmI1YytIW54JzhWS5fXJHRRccM5aRj5
oO97dHh02xmzzsnlcHev0zVv78IA3745OT52++VrYBC+Bo36NwAz6p7VYyth
SNGRqrS+FPlmpIj4Hkcvq1nLiUFfO5X7so1kU9kuzGk1fpHJJHPpBLFCvaRB
RqM9ISb7B+5OcNB3d7xR4I4Gk77ri11/z98PuD/YrnQKZtgJFWnQH/QCcV9+
mxKXDP04PXFNBP3J3o6YuNv+vgezTIbuKDgYuIG37e9MvJE/6nt2EFw3VpdT
R8XE121Lg3a6xj3bhBNlcySJrmWr14+Wet5O/SY5ueo0eF+IdKVYgPoNqp9M
acN1SGozGPZ2+71hf693MOosk5O2krNJHrGNnJPhCbvCcobz7LZO1d+J3XQZ
BseCfiwN/lpRWp7D+8H+aDjc2d0b7JUfpNxI63/OSbH7gwMx2RsErvBGE3d/
9wAktw2CDA4ORt7wYGfi+wdlJ14ET7cG2I5Qpwkf7GzDJKMggE4ClJt73sgd
jUZ+4AlvL9gthQJ8Tsv1HQz2jNu4auZKNLZYW4W1siIP/aa9WoL3wkNz9qer
kG39v1/7+LS6ZMqC1TJY4OkXbE1p8gWmBvx2klL97X+RIsrirMZMisdYrxSE
0o8QO3IdZZw2mLt+l4KWIHPZswHV3ujS10q6APgmeKNXXxfhJtmCdbZUy9gM
GzmW0E6TKMDwiSBKX9Fa3o4cV65CKEytuaxPtDWWz0Sk2D4NU0ylQxvMAzly
SsU5OVZbESepAN0UAmmydSg3KAG3CT3MaNfy2Ae9nZZM9tcxkyYQB1VpLMTP
Pl7NWCjleBo8xTuZS1r47Jkuvf386ZR9qhQatFZ8G7ii7LNMo5HWSF0l5NBE
HTtsxxQwYGK69RopKDGInBMrKxlsvG+P2z0g8hnbNDfkvIQ5P443bv8SWDKb
wdo+qvuyVeSFGTNsoDA4/doBLFlk6sdT4Evtwr0FrxDFHtovHjy2b8vXrbAN
y39lka1dGuus7xhXVbuvuYz429hSKytexYxSKdfnuH6zulZ2s8sau3bO36zL
JnVBkl7lflGudnVKTiubVloe0/FZqn7p4zdlMCAir3bum6ciSqU42lQpnssX
m+sF3pD2uH+nyiTNQeU7WFmSLZyHMVO/SySCVx26GN4BkPHjj7pqNxOz5F5J
BLUBZMJO6EeOar7cVN9QsTS2+eknmLe/TSanT9i+VvZkjmPLYmM0IxiEKmOC
QA+hy88ChjeAeniaBnjHVbWE+ojL7KqqwsFBPum1ULExXlmkw4qaCElSWPpX
lhuWtdu13ew3lZ14l8GO1zdFiiACcysNLQWrPxFswL/uxeEPupIf6TkKkS/I
Ljp17OqyZ3Ukaerr1OXuMj2JzfFwk7iz0QFKD0UxdIgBeMVY4QhMPynTHfb6
S1fASmCEyaY3CTTTq7fJlWXmtV12YepHUVrOaerHQZSlVzctCcUhf441oCNU
+5Qc1JpLSQ5bWetXuYdUyU0w+6su9m7RGiC44bUjpY22um3NApcPLw2ig1cq
7/lE5tTYUV3fk1LLpFQDx5rm8u8+0biNn24iD6F+BokG6OMAp3Q9OVK/y9Zz
/geV8BID5k0AAA==

-->

</rfc>
