<?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-id-verification-04" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title>Identity Verification Methods Values</title>
    <seriesInfo name="Internet-Draft" value="draft-skyfire-oauth-id-verification-04"/>
    <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="N." surname="Ali" fullname="Nash Ali">
      <organization>Experian</organization>
      <address>
        <email>nash.ali@experian.com</email>
      </address>
    </author>
    <author initials="S." surname="Thumma" fullname="Srinivasa Thumma">
      <organization>Akamai</organization>
      <address>
        <email>sthumma@akamai.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 114?>

<t>Knowing how a person's identity was verified can be important when making trust decisions.
This specification defines a claim and values for declaring how the person's identity was verified.</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-id-verification/draft-skyfire-oauth-id-verification.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-skyfire-oauth-id-verification/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/skyfire-xyz/draft-skyfire-oauth-id-verification"/>.</t>
    </note>
  </front>
  <middle>
    <?line 120?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Knowing how a person's identity was verified can be important when making trust decisions.
This specification defines the "ivm" (Identity Verification Methods) claim and values for it
for declaring how the person's identity was verified.
The "idv_time" (Identity Verification Time) claim conveys when that verification
result was established.
It also creates a registry for Identity Verification Methods Values
and initializes the registry with the values defined in this specification.</t>
      <t>The usage of the "ivm" (Identity Verification Methods) claim parallels that of the
"amr" (Authentication Methods References) claim and uses parallel syntax.
Presence of a value in the claim indicates that the use of the indicated
identity verification method succeeded.</t>
      <t>The "ivm" claim contains a set of identity verification methods that succeeded.
It does not provide evidence for or details of how they were used.
Should that level of detail be desired,
OpenID Identity Assurance Schema Definition 1.0 <xref target="OpenID.IDA"/> can be used,
either with the "ivm" claim, or separately.
Likewise, Vectors of Trust <xref target="RFC8485"/> can be used to provide more detail,
either with the "ivm" claim, or separately.</t>
      <t>While this claim and values are general purpose
and can be used in any JSON Web Token (JWT) <xref target="RFC7519"/>,
one use case for them is use in KYAPay tokens <xref target="I-D.skyfire-oauth-kyapay-token"/>.</t>
    </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>
    <section anchor="ivm">
      <name>Identity Verification Methods</name>
      <t>This section defines the "ivm" (Identity Verification Methods) claim and
values used with it to indicate that particular identity verification methods
were used.
In many ways, this parallels the "amr" (Authentication Methods References) claim
defined in <xref target="OpenID.Core"/>.
Like "amr", "ivm" is a JWT claim whose value is
an array that lists a set of methods that were used,
in this case, as identity verification methods,
rather than authentication method references.</t>
      <section anchor="ivmClaim">
        <name>"ivm" (Identity Verification Methods) Claim</name>
        <t>The "ivm" (Identity Verification Methods) claim is a
JSON array of case-sensitive strings that are identifiers for
identity verification methods used.
For instance, values might indicate that both
physical document verification and database PII verification methods were used.
Values used in the "ivm" claim <bcp14>SHOULD</bcp14> be from those registered in the
IANA "Identity Verification Methods" registry
established by <xref target="ivmRegistry"/>;
parties using this claim will need to agree upon the meanings of
any unregistered values used, which may be context specific.</t>
      </section>
      <section anchor="idvTimeClaim">
        <name>"idv_time" (Identity Verification Time) Claim</name>
        <t>The "idv_time" (Identity Verification Time) claim is <bcp14>OPTIONAL</bcp14>.
It is the time at which the identity verification result
described by the accompanying "ivm" claim was established.
Its value is a NumericDate <xref target="RFC7519"/>,
as for the "auth_time" claim <xref target="OpenID.Core"/>.
This is the time when the issuer had completed all steps
required to assert that result.
It is not necessarily the earliest or latest individual evidence-collection event.
The times of individual verification steps are kept
in the verifier's record of the verification,
rather than inferred from "idv_time".</t>
      </section>
      <section anchor="ivmValues">
        <name>Identity Verification Method Values</name>
        <t>The following Identity Verification Method values
are defined by this specification.</t>
        <section anchor="dbvMethod">
          <name>"dbv" (Database Verification of PII) Method</name>
          <dl newline="true">
            <dt>dbv:</dt>
            <dd>
              <t>Database Verification of PII (match of name/address/dob/ssn/nid, etc.)
using an unspecified number of consumer reporting data sources</t>
            </dd>
          </dl>
        </section>
        <section anchor="dbv1Method">
          <name>"dbv1" (Database Verification of PII One Source) Method</name>
          <dl newline="true">
            <dt>dbv1:</dt>
            <dd>
              <t>Database Verification of PII (match of name/address/dob/ssn/nid, etc.)
using one consumer reporting data source</t>
            </dd>
          </dl>
        </section>
        <section anchor="dbvmMethod">
          <name>"dbvm" (Database Verification of PII Multiple Sources) Method</name>
          <dl newline="true">
            <dt>dbvm:</dt>
            <dd>
              <t>Database Verification of PII (match of name/address/dob/ssn/nid, etc.)
using Multiple consumer reporting data sources</t>
            </dd>
          </dl>
        </section>
        <section anchor="digMethod">
          <name>"dig" (Digital ID Document Verification) Method</name>
          <dl newline="true">
            <dt>dig:</dt>
            <dd>
              <t>Digital ID Document Verification (for example Mobile Driver's Licenses)</t>
            </dd>
          </dl>
        </section>
        <section anchor="phyMethod">
          <name>"phy" (Physical ID Document Verification) Method</name>
          <dl newline="true">
            <dt>phy:</dt>
            <dd>
              <t>Physical ID Document Verification (for example via a real time capture of the front and back of DL or Passport photo page)</t>
            </dd>
          </dl>
        </section>
        <section anchor="secMethod">
          <name>"sec" (Secondary Document Verification) Method</name>
          <dl newline="true">
            <dt>sec:</dt>
            <dd>
              <t>Secondary Document Verification (for example via bank statements, financial statements, utility bills, government-issued papers, etc.)</t>
            </dd>
          </dl>
        </section>
        <section anchor="inpMethod">
          <name>"inp" (In-person Verification) Method</name>
          <dl newline="true">
            <dt>inp:</dt>
            <dd>
              <t>In-person Verification</t>
            </dd>
          </dl>
        </section>
        <section anchor="vidMethod">
          <name>"vid" (Video Verification) Method</name>
          <dl newline="true">
            <dt>vid:</dt>
            <dd>
              <t>Video Verification (live video interview)</t>
            </dd>
          </dl>
        </section>
        <section anchor="lfmMethod">
          <name>"lfm" (Live Facial Match to Identity Evidence) Method</name>
          <dl newline="true">
            <dt>lfm:</dt>
            <dd>
              <t>Live Facial Match to Identity Evidence (automated comparison of the person's
face, captured live as an image or video, against the portrait on the identity
evidence, such as the photo in an identity document, with presentation attack
detection <xref target="ISO30107-1"/> applied to the live capture; see the Identity
Verification Methods section of <xref target="NIST.SP.800-63A-4"/>).
This value indicates that the person presenting was matched to the identity
evidence. It is typically used together with a value for the verification
of that evidence itself, such as "phy" or "dig".</t>
            </dd>
          </dl>
        </section>
        <section anchor="regMethod">
          <name>"brv" (Business Registry Verification) Method</name>
          <dl newline="true">
            <dt>brv:</dt>
            <dd>
              <t>Business Registry Verification (match of the organization's legal name, registration number and status
against an official company register, for example a US state's business registry, such as the Delaware
Division of Corporations, or Companies House in the UK)</t>
            </dd>
          </dl>
        </section>
        <section anchor="tinMethod">
          <name>"tin" (Tax Identification Number Verification) Method</name>
          <dl newline="true">
            <dt>tin:</dt>
            <dd>
              <t>Tax Identification Number Verification (match of the organization's legal name and tax identification number
with the tax authority, for example via the US IRS TIN Matching program)</t>
            </dd>
          </dl>
        </section>
        <section anchor="bdocMethod">
          <name>"bdoc" (Business Document Verification) Method</name>
          <dl newline="true">
            <dt>bdoc:</dt>
            <dd>
              <t>Business Document Verification (for example via a certificate of incorporation,
a certificate of good standing, or a shareholder register)</t>
            </dd>
          </dl>
        </section>
        <section anchor="bovMethod">
          <name>"bov" (Beneficial Owner Verification) Method</name>
          <dl newline="true">
            <dt>bov:</dt>
            <dd>
              <t>Beneficial Owner Verification (identification of the natural persons who ultimately own or control the
organization, and verification of each one's identity; the term follows the definition of beneficial
owner in <xref target="FATF.Glossary"/>)</t>
            </dd>
          </dl>
        </section>
        <section anchor="repMethod">
          <name>"rep" (Representative Verification) Method</name>
          <dl newline="true">
            <dt>rep:</dt>
            <dd>
              <t>Representative Verification (verification of the identity of the person acting for the organization,
and of their authority to act for it)</t>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="example">
        <name>Example</name>
        <t>The following is an example JWT Claims Set
for a person whose physical identity document was verified
and whose face, captured live, was matched to the portrait on that document:</t>
        <sourcecode type="json"><![CDATA[
{
  "iss": "https://server.example.com",
  "sub": "248289761001",
  "ivm": ["phy", "lfm"]
}
]]></sourcecode>
        <t>Without "lfm", the "ivm" claim would say only that the document was verified,
not that the person presenting it is the person it identifies.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The security considerations defined in
JSON Web Token (JWT) <xref target="RFC7519"/>
apply to this specification.</t>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>The privacy considerations defined in
JSON Web Token (JWT) <xref target="RFC7519"/>
apply to this specification.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="json-web-token-claims-registration">
        <name>JSON Web Token Claims Registration</name>
        <t>This specification registers the following Claim in the
IANA "JSON Web Token Claims" <xref target="IANA.JWT.Claims"/>
established by <xref target="RFC7519"/>.</t>
        <section anchor="ivm-claim">
          <name>"ivm" Claim</name>
          <ul spacing="normal">
            <li>
              <t>Claim Name: ivm</t>
            </li>
            <li>
              <t>Claim Description: Identity Verification Methods</t>
            </li>
            <li>
              <t>Change Controller: Michael B. Jones - michael_b_jones@hotmail.com</t>
            </li>
            <li>
              <t>Reference: <xref target="ivmClaim"/> of this specification</t>
            </li>
          </ul>
        </section>
        <section anchor="idvtime-claim">
          <name>"idv_time" Claim</name>
          <ul spacing="normal">
            <li>
              <t>Claim Name: idv_time</t>
            </li>
            <li>
              <t>Claim Description: Identity Verification Time</t>
            </li>
            <li>
              <t>Change Controller: Michael B. Jones - michael_b_jones@hotmail.com</t>
            </li>
            <li>
              <t>Reference: <xref target="idvTimeClaim"/> of this specification</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="ivmRegistry">
        <name>Identity Verification Methods Registry</name>
        <t>This specification establishes the IANA "Identity Verification Methods" registry
for <tt>ivm</tt> claim array element values.
The registry records the Identity Verification Method value
and a reference to the specification that defines it.
This specification registers the Identity Verification Method values
defined in <xref target="ivmValues"/>.</t>
        <t>Values are registered on an Expert Review
<xref target="RFC5226"/> basis after a three-week review period on the &lt;jwt-reg-review@ietf.org&gt; mailing
list, on the advice of one or more Designated Experts.
To increase potential interoperability, the Designated Experts are requested to encourage
registrants to provide the location of a publicly accessible specification
defining the values being registered,
so that their intended usage can be more easily  understood.</t>
        <t>Registration requests sent to the mailing list for review should use
an appropriate subject
(e.g., "Request to register Identity Verification Method value: example").</t>
        <t>Within the review period, the Designated Experts will either approve or
deny the registration request, communicating this decision to the review list and IANA.
Denials should include an explanation and, if applicable, suggestions as to how to make
the request successful.
Registration requests that are undetermined for
a period longer than 21 days can be brought to the IESG's attention
(using the <eref target="mailto:iesg@ietf.org">iesg@ietf.org</eref> mailing list) for resolution.</t>
        <t>IANA must only accept registry updates from the Designated Experts and should direct
all requests for registration to the review mailing list.</t>
        <t>It is suggested that the same Designated Experts evaluate these
registration requests as those who evaluate registration requests
for the IANA "Authentication Method Reference Values" registry <xref target="IANA.AMR"/>.</t>
        <t>Criteria that should be applied by the Designated Experts include
determining whether the proposed registration duplicates existing functionality;
whether it is likely to be of general applicability
or whether it is useful only for a single application;
whether the value is actually being used;
and whether the registration description is clear.</t>
        <section anchor="registration-template">
          <name>Registration Template</name>
          <dl newline="true">
            <dt>Identity Verification Method Name:</dt>
            <dd>
              <t>The name requested (e.g., "dig") for the authentication method
or family of closely related authentication methods.
Because a core goal of this specification is for the resulting
representations to be compact, it is <bcp14>RECOMMENDED</bcp14> that the name be short
-- that is, not to exceed 8 characters without a compelling reason to do so.
To facilitate interoperability, the name must use only
printable ASCII characters excluding double quote ('"') and backslash ('\')
(the Unicode characters with code points U+0021, U+0023 through U+005B, and
U+005D through U+007E).
This name is case sensitive.
Names may not match other registered names in a case-insensitive manner
unless the Designated Experts state that there is a compelling reason
to allow an exception.</t>
            </dd>
            <dt>Identity Verification Method Description:</dt>
            <dd>
              <t>Brief description of the Identity Verification Method
(e.g., "Physical ID Document verification").</t>
            </dd>
            <dt>Change Controller:</dt>
            <dd>
              <t>For Standards Track RFCs, state "IETF". For others, give the name of the
responsible party. Other details (e.g., postal address, email address, home page
URI) may also be included.</t>
            </dd>
            <dt>Specification Document(s):</dt>
            <dd>
              <t>Reference to the document or documents that specify the parameter,
preferably including URIs that
can be used to retrieve copies of the documents.
An indication of the relevant
sections may also be included but is not required.</t>
            </dd>
          </dl>
        </section>
        <section anchor="initial-registry-contents">
          <name>Initial Registry Contents</name>
          <section anchor="dbv-method">
            <name>"dbv" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: dbv</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Database Verification of PII</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="dbvMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="dbv1-method">
            <name>"dbv1" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: dbv1</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Database Verification of PII One Source</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="dbv1Method"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="dbvm-method">
            <name>"dbvm" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: dbvm</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Database Verification of PII Multiple Sources</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="dbvmMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="dig-method">
            <name>"dig" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: dig</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Digital ID Document Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="digMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="phy-method">
            <name>"phy" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: phy</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Physical ID Document Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="phyMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="sec-method">
            <name>"sec" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: sec</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Secondary Document Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="secMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="inp-method">
            <name>"inp" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Reference Name: inp</t>
              </li>
              <li>
                <t>Identity Verification Method Reference Description: In-person Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="inpMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="vid-method">
            <name>"vid" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Reference Name: vid</t>
              </li>
              <li>
                <t>Identity Verification Method Reference Description: Video Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="vidMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="lfm-method">
            <name>"lfm" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: lfm</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Live Facial Match to Identity Evidence</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="lfmMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="brv-method">
            <name>"brv" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: brv</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Business Registry Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="regMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="tin-method">
            <name>"tin" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: tin</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Tax Identification Number Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="tinMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="bdoc-method">
            <name>"bdoc" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: bdoc</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Business Document Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="bdocMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="bov-method">
            <name>"bov" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: bov</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Beneficial Owner Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="bovMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
          <section anchor="rep-method">
            <name>"rep" Method</name>
            <ul spacing="normal">
              <li>
                <t>Identity Verification Method Name: rep</t>
              </li>
              <li>
                <t>Identity Verification Method Description: Representative Verification</t>
              </li>
              <li>
                <t>Change Controller: IETF</t>
              </li>
              <li>
                <t>Specification Document(s): <xref target="repMethod"/> of this specification</t>
              </li>
            </ul>
          </section>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC7519">
          <front>
            <title>JSON Web Token (JWT)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
            <date month="May" year="2015"/>
            <abstract>
              <t>JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7519"/>
          <seriesInfo name="DOI" value="10.17487/RFC7519"/>
        </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="RFC5226">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <author fullname="H. Alvestrand" initials="H." surname="Alvestrand"/>
            <date month="May" year="2008"/>
            <abstract>
              <t>Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).</t>
              <t>In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.</t>
              <t>This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5226"/>
          <seriesInfo name="DOI" value="10.17487/RFC5226"/>
        </reference>
        <reference anchor="ISO30107-1" target="https://www.iso.org/standard/83828.html">
          <front>
            <title>Information technology - Biometric presentation attack detection - Part 1: Framework</title>
            <author>
              <organization>International Organization for Standardization</organization>
            </author>
            <date year="2023"/>
          </front>
          <seriesInfo name="ISO/IEC" value="30107-1:2023"/>
        </reference>
        <reference anchor="NIST.SP.800-63A-4" target="https://pages.nist.gov/800-63-4/sp800-63a.html">
          <front>
            <title>Digital Identity Guidelines: Identity Proofing and Enrollment</title>
            <author>
              <organization>National Institute of Standards and Technology</organization>
            </author>
            <date year="2025" month="August"/>
          </front>
          <seriesInfo name="NIST Special Publication" value="800-63A-4"/>
        </reference>
        <reference anchor="RFC8485">
          <front>
            <title>Vectors of Trust</title>
            <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
            <author fullname="L. Johansson" initials="L." surname="Johansson"/>
            <date month="October" year="2018"/>
            <abstract>
              <t>This document defines a mechanism for describing and signaling several aspects of a digital identity transaction and its participants. These aspects are used to determine the amount of trust to be placed in that transaction.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8485"/>
          <seriesInfo name="DOI" value="10.17487/RFC8485"/>
        </reference>
        <reference anchor="FATF.Glossary" target="https://www.fatf-gafi.org/en/pages/fatf-glossary.html">
          <front>
            <title>FATF Glossary</title>
            <author>
              <organization>Financial Action Task Force</organization>
            </author>
            <date/>
          </front>
        </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="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="IANA.JWT.Claims" target="https://www.iana.org/assignments/jwt">
          <front>
            <title>JSON Web Token Claims</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="IANA.AMR" target="https://www.iana.org/assignments/authentication-method-reference-values">
          <front>
            <title>Authentication Method Reference Values</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="OpenID.IDA" target="https://openid.net/specs/openid-ida-verified-claims-1_0.html">
          <front>
            <title>OpenID Identity Assurance Schema Definition 1.0 incorporating errata set 1</title>
            <author initials="T." surname="Lodderstedt" fullname="Torsten Lodderstedt">
              <organization/>
            </author>
            <author initials="D." surname="Fett" fullname="Daniel Fett">
              <organization/>
            </author>
            <author initials="M." surname="Haine" fullname="Mark Haine">
              <organization/>
            </author>
            <author initials="A." surname="Pulido" fullname="Alberto Pulido">
              <organization/>
            </author>
            <author initials="K." surname="Lehmann" fullname="Kai Lehmann">
              <organization/>
            </author>
            <author initials="K." surname="Koiwai" fullname="Kosuke Koiwai">
              <organization/>
            </author>
            <date year="2026" month="July"/>
          </front>
        </reference>
      </references>
    </references>
    <?line 554?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>We would like to thank
Jean Diaconu
and
Rob Zagarella
for their contributions to the specification.</t>
    </section>
    <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>-04</t>
      <ul spacing="normal">
        <li>
          <t>Added the "lfm" (Live Facial Match to Identity Evidence) method and an example of its use.</t>
        </li>
        <li>
          <t>Added the "idv_time" (Identity Verification Time) claim.</t>
        </li>
      </ul>
      <t>-03</t>
      <ul spacing="normal">
        <li>
          <t>Added the "brv", "tin", "bdoc", "bov", and "rep" methods for verifying organizations.</t>
        </li>
      </ul>
      <t>-02</t>
      <ul spacing="normal">
        <li>
          <t>Described that the "ivm" claim contains a set of identity verification methods that succeeded.</t>
        </li>
        <li>
          <t>Described the relationship to the OpenID Identity Assurance claims.</t>
        </li>
        <li>
          <t>Added {:vspace} syntax to definition list entries.</t>
        </li>
      </ul>
      <t>-01</t>
      <ul spacing="normal">
        <li>
          <t>Added "dbv1", "dbvm", "inp", and "vid" methods.</t>
        </li>
        <li>
          <t>Added Nash Ali and Srinivasa Thumma as authors.</t>
        </li>
      </ul>
      <t>-00</t>
      <ul spacing="normal">
        <li>
          <t>Initial draft.</t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA8Vc+3YbRZr/v5+iVjlncFhJtpwAGTPLoNgJCOIkGxs4swyH
KXWXpcKtLtHVbUfj43mWeZZ9sv19X1X1RW5LVoCz/EGk7rp897s8GAyiQhep
OhK9SaIyfF6J71WuL3QsC20ycaqKuUms+F6mpbK96JGcTnN1hfW9CEvUzOSr
I2GLJIoSE2dygaOSXF4UA3u5utC5GhhZFvOBTgZXjXMHB08jW04X2lp8K1ZL
bJu8OH8pxCMhU2twvs4StVQZQdXri55KdGFyLVP6Mhk/xz8mx6d35y8BVVYu
pio/ihKAdBTFJrMqs6U9EkVeqgjgPolkruSROFNxmQPL6Nrkl7PclMsj8YOa
ijGAxPH/dFi/zU1hYpNGl2qFhclRJAZCzgAKfdCeUtVDHdPHpVwt/IrYLBYq
j3GzykoAJMRMF/NyCrQCWd6v/rn/AEIBN2z2cH5FXxyxfgD4OpuJr+gVPV5I
ndKSL9V7uVimaggY6LnM4/mRmBfF0h7t7zde7uM4IVIQzBaAK6xowDd0QA+1
eQikD1kznBeLtBdFkql9FA0AgZOZcXapCzGeyfxapnhq8pnMPDvANXeoOFvZ
Qi2smGTxEIuUQ1rS3p+l2/vlSs6NYeyFAKtr3D1kQ2DGF+sM8nE6FN+YTNkK
kFMdz6VKxfP6xRosKr0YTKwtVSKOIWhlWoARNTQLd8DP059/of1fzk1BLzoh
oqM0HzXU2YXZbxDktbRzMU71nftfvF+CojKrb8ywdChTDda7V3xXfdRZrjN9
Ja0U5/NysZB3jhxfSpxUH2gLXvel5Od8WpSZfIHlVyzN714ef/bJ6M9HUURg
t198cnj4KX2cnL15cjA6+Gwwom+QW5nPVFEjf319PdTWDAHKvi1klsg82X/2
5NnhM5YStyfYpnALdLNQ8TwzqZmtoGjPtVmoItexWOYKOl+4NbIoZHwpEoXF
/GAg3sq8EKMj8TIHTUj5e3xDkETB/w2IMLBEWaHyjI+SqXjToJUAHOLMQ+uf
8V42POLw4PAJf7Xgg7JEnHB0D/TYn7w47gGdQBdaTmC8npydD8/eDp8dHAw+
fTIePO2m2BLGxg4zbYvhzFztu9WDp/t26T7Ku4Q70dBh4FAZ969KWK9UQzCP
6ocwd+aCrAnwEi+y3KQpWbINFHodiDPJLI4oCyXMRUUYywedV4xqU+iTwcGz
+4hElBBnSxXD0Iu35TQNZhC4VNTpOUF79vTZJ7Tx5fj85fCr1Fgr4YvulbUL
WVwMZvJCs8SpzJFz3z32u+8SkA4X4fC7BPHkeKkzmTHMYydv59JeipeGXECN
+wU8G32fDE6GbTN5uZLwHoPCXKqMDn4Dxzc5GR6bXHUjZLBAJ8NMFeC+iq1/
MIDnyyDy+Bdnj34+uIuQO5osFy0UdIUYDQ9gDbFnaXJJ1kyoHB8kOFSIw96a
gA9Gh4PRJ52yEUxXIc7kpV6UuVx79Y2ZZ+J5LpNUrdZedRje5uvnucoMNBoR
SaJ0btbfH89LaPypyQu9AE5E5vHr8fCbH86Hx6nUC3t0H/No3f0WSmaSBUYi
UpllpBZ2/5froknTb87evOYg4pz4J9x1XXwngMan735HSOgQDkBcVLXgaG2Q
qwsFcsVqcMVhWxPYcWuHj+/Eu7DDB3od0HuZnJyMdxNJnUgfAyjIJ9Nmo2RW
VmkMx5hLguksnsMziRMFI6UZ7I0SO2pK7Eh8U6YrEtxPN4jsuckRWWTilUkS
RR+TYm3FCXwApPOlKtbfnMr8UnwtYVPXXoxTxKSFgR1LdWLWXn4rtXil5guZ
ZetvjC0vFf7R13DK0XA4jKLBAKHm1Ba5jIso+jYz14Tz3FwLKeDzrck+slVc
Kq6lFYHkIpaZmCqhFyAV7HMhrsF/hIscPiI8tgW0KtYUh9thdD7XVhD/6hQg
IbIr2HTB3GPb7uSKvSE2pzIP4EC4tgAEbBidhU5gBSLEqHC3uUlKtpz/X8gR
3D19teiJvY2J0ONuIugi+jBanPO9ydXPMFvq3svP8TLcDBN/pVbWYVrMYWub
EXaEMAgRKd+CwF7Cg9o5XTQpOLESMdKggrmZqxlCiXzFCDwk+4sIadZABJv/
9ESrTrlGssBPPFkcZWkDnq7THUJAmJcWPpgih13Jv5S5TFOVWkcBd0LUk4sc
J3SaOFvbuBYTSwtYw3HCrhBCvh9GbzmajBk26TByiCi/Fdkpna88AAUjU6ES
3iZRxfYmk4Sz08KWcazgzhJPDkeBis0FbAoximwaDt50lAejcSD4nRiAl5kC
sbG5wm6h6P+EFXGcxRVXgIY43Msr2AgaESo44mxuyjRxJ6fqCuTBQreHlC5B
7JarpB/tarhvbmpfcnsbdJju7EcKUqTyWpgaJOGE3yriVaHS1TB6pS/Vtbaq
D1GJC1hwgu+clf7mxgeI7fMFrHEgBkUJHpvdro1+mOtUOaG+YwwkDp2pTEGe
xLKEe4LvpNdNICBIMluthw17CFUeO8Apt7q97UcIg1iqYmkdzwAaRM/yQ5zy
7d/Gb+VKcNhosXVzYHl7S6b3EYV+V8Qpk7k4veaOdWJ4SWJgKIzvnX53dk4F
F/pXvH7Dn9+9+O/vJu9enNDns6/Hr15VHyK/4uzrN9+9Oqk/1TuP35yevnh9
4jbjqWg9inqn47/hDUHVe/P2fPLm9fhVr7IgiYlLCnuYyOAkGX7K1JD6QdWE
tBFEMs711NH4+fHb//336Cno8h+g6eGIaOq/PBt99hRfyIS620yGGMF9JS2I
5HKpZM6cSlPQf0lZlMVa2DGoSiYgLQrk/PhHosxPR+Iv03g5evqFf0AItx4G
mrUeMs3uPrmz2RGx41HHNRU1W8/XKN2Gd/y31vdA98bDv/yVMkYxGD376xcR
y9Bmd3HzCOpzG3l/61Pw3+BpI69crD2so7ogAQhm1pkoaChsfpkS3zaZyqhh
4iYULGTklFe276Ss6VoA6W4uJWp4vcrMUY5Fykf2yh3Y9xTQZN6h9x7V6znM
RfA25G4h6TkpOFtguNmGN2jZ/QqjfhSUhWwGy+tGWvQjWDWyfDgmE+1sInip
KptABBU9evRA5nEW5CSBP942XdzDOE/UidhKOjIAa8JqQLVdTRUngcADwZYn
AlkFhyxCq5zjso3u13oZeEnxW0YlqBgU86K20LN5sSZgU1PMo+V8ZfEsra1R
62gyJkg85JRM9tvJpPvihgR+3xBtH2E0wwCv6DB1F7lZ4DVJiIu5cEbYElHm
uKWE36tCtagRGIrpCoKKC9/5l7e3n0esSQwUh9G1o7vWsIaZco5UznIFLJbG
Qb1QyJCIGeYiIpUqswaYDQXuQ8yR6kPvVoQWxTnqfVGFh0HGHhYSV1KWXNGD
tqTtElUDxWD4OHbSTv1pvyAFY5A5tOuUKBd1N/zPdMWrZRybxRLkIEI2+doR
n9tK86HlryFbuY5PSPhaMYG0IRKAKYG+ehTdqXdMDlvgJi4+a6BbbAm9n8uE
uhXL1LlQsBccW1qkEb+WFN0xo61FHut0wCEaSETBZaZgGSyyntShDL+ZQngK
Cptcd4HVCDFXCa0JIeggNjCyzjMoCkdcKkQwchjX2NIiNEPHqn6plkXkNcbn
UznyrFzFCF1CIN7c27Z1OoNVIwRZr2phcfK3SZN8NuRsm/vsRe4COLnkdeN+
X5SRHH86d8Hi0pEkPSJdSKZXkOGTYFVaRwJPWJnH4eibR1jsPgOmm6Mru5Sx
uo3w9CiiIsb9Z4i9hSwg5PhGdYh9mSRgtt1PzHTf2mw/01BdVcTDx9TGsK5c
DC33IAMJ14RjM019EQgwuEGJOa1NuDpjyhzSUuM12oKYeIO444x3tXEcdSM5
+gOwpCh8M0I1Pott+JxSuwja5pGybawW3Vgt/gCsKkAeyCs9I9RCO+FEnAT3
1wSniY2edSGjZ4zLlnPEHtk436wUp2ZKCddJDpdPKv5Kx4gAQDsPG1wyYHsb
HPMDgMOODuDwlIDbelAbuistuZiCDWxhkSwUZV6VAmBeKGNBWDCllhSenrwi
0/gWVpXoLZZzQ1mpnKmADyJm4HMGQ0bdlNVWbLC+Axs8JWy2HHMXl6nMLmFm
Ybm5xNwXF1Vzo/m0LHRKBg6socRoZsAbLkr7hiYwotpXEDuHmc6W5I2zgSuL
3YcQlnUghKeEUPdufwFcBi74Hj7G3Hc4lnQcjqd0+N2dYi+lSPOKX3C6eaXV
dUAovSCNf0UrXkqm0SkrIjhauYAX3uU1YMC2DhjwlGB42GliD97fLKjIxA4c
Dtg6e9AsO0LdLySFtV4qE8HYSMr8hV5w9S13yCFZmFHByRWzSDRziTTLR3f1
zEPlwvtUbprTWbyBxZhLG3WMFGLkvsvaOnq0OK/u0t7c1E1jpOdIwlPtQhC6
gSH3eHyONEjx00kNWGcuGtJPEObm5k6j9fb2MQ0ScJgUqnx3Cnte3Dz0ZCAp
emOLW0PXQaCh8IHkakn2BPGRr0HNVF1tCtXFENS1irnC8RNwVKU7XdDUQE17
Z/1oFIZMdAgZpjmFDM/J1MMPiBDc36cTiNQ75BGHkDxuPqXhegj85mABTHWq
ZpBi8kn9kH64XT5WILtIVqUkSQ3yJ4lbOJ8UwIfPVcrTF017JcV3Z84q4a5p
gDPkOW0BPVGpvJbcGTxBaGm9UByHHhLcIJf6jvlGSn++Nr7ORtu/+zboPCQA
tD2X773sVZR47XC6h8bY1kFjPCUaP+y0h9KayVrgSN0+0hEdBKjqnLTIdcQg
um3aki9gxM/E5N2ZOJ+8dtaI5H+Zm1kuF4EiU+h5U9y2OSxa3yVveNwSuAd7
3xj5iVugXPIQ11ztk2Str5gZw4IHZc9mzHYEPHNIx9ykCcdCTtwqDA3rk8qU
l8s319n9rMbqLvSMU6dNh4i9NZZ5VmdQES4psymi5o8RFMAtuCYtqCIJHCiX
zk3KFYH2jI+rcl6tRY5KkjBlqtGe+tyJhcoXPptxypPUFXzsm1Yo0DWMBNe7
WpMYMK2eeAgsQbx3qjb/V+p+S9Tl+vGUSLfhCLG3jlwrWW+5RWTlbMWDyW0R
iqQlC/mjzmvt4Ew4Lny7j3ETL7wU3jzy8ngnEdTsaYO0UqnPjQcgLnMtw9Di
9MW/qrx0x4e2GofcU3A7Ovx7v8tBtT26LKqDj6LoX//6l/gFQEQ3QL+HAK7X
nAhEyKPyYWN0sEdU6tlySssOnz47fPbnzz4dHRyM3AsqcxyJH9kz9V2M9FN0
S5dE0Q+wPKYs3NP+nXLXNXecLBX7snRVu+BOIvQjqj9scNO6quP4d/QgVAit
64aEgVCe5cNL7wocH214GbdeNnqb0bYuDrUS0pVjQkeCDwjeIq+RcTcAS//u
j7yfa4frl0O4O8daQhDgg+6OjnownY7wtSYc+75po17ZeUOPwsD26A6wuFOy
rBAMIQ9LEa+Poo/9ba95oAJvqicnXKFburnHjfVS2jKXGSLkY2dWU5XfnVIS
g40Dnx/XLYIjV2d1JcpbZ2DWiRdQqSqX3fj417sgde7X/+4YNQuvG7Da0jGq
QksuqlW16E4Bq0XBidhutW+yuf/AHf8I7SVuLahUuVo+l+ZcLbKabHAlRdtK
N+4v7LFplnXXJNjfNhLOAvuWmC46Z1PamvSQkmKr+1RXJ0lHvq/70426PHcs
3EhxASZQahuxbtEUL/g5lZY82EVBsTrAyJUaXCt1iTNoLdlVbZKQJP4pLT7/
5boY4IKBW/ClVsUFTa39aVZ8zjPqNCtNrax+2CSTK+0GLajQBu5wYx4irWcZ
Z7cOOmIK5Zc0v0J+0hREDnKUlJMbLJFTrkj0fbS/vt+j/iuoUDivCO4YRFUz
FYXUJMOyxogAZ52mDingq3kkFfZUxlT11tN0jbGOBa5tUo3CTBU9qMnej6yp
/JbOGYUsUYmfh/GzAkwHIEuFdVFmPJeGsBW8bNrggBJlulkRhM1TmpuGHLF4
flk30lHyVAIl2KBcrikohjf/BalytKeGsyH16t2xdGAA/AEieBRCnd7joXP2
Pn1qycu9LOL+kp/FYOCuSCJA02zVHDZqId7nX1uUGYMT2lVh6CvQw1/P5CD9
ZAcTnagMEmQDVSBcaZkoF7AtU5lVLb2+0BeuHBHD9HDlYzbD3W6GgmWGB2gM
jZ6pyN3o6McjOdZelOnwHr5VzUviMUXerMLUvZRBv1IDq+0bF4cjkciVDVIy
zU1JrUqP6OTF2VcI52VRuBGPaC808ZT4C4KeWaWRX7SE5LGXEmvS0ocGbFcX
NE3DsRhJ/LKorWK5TLhM4vuS3SpH6b0jbqJzEi/qMFWYuysbNGlzqwkfwcPR
nKe8SurAz1LK23G7IpF03VuEhFGX8DjucRxNKVW1o3NtFBIG53EeNklbu54Q
14xP37FFPkZkST/X8KNbjkzgaCh7+RZiB2JeUKMgLlySmivf3KKo0dDgUdJG
IylZfoln6j0ecwpUZrGb5KfcLwqHuMA51ZfKhY5TlzT7uaagCGxuI9CkvQ3G
BdLuhMZlOCSBqQr76L76qspMcqoUFyUXypzFpHLZ5z7VqVe3kapDH8FtaiVz
HxG2tO1cwSoB92ZWudGccahFlRnOvhdN1xFMJBXcHldZZOfwBKfhSNEWZMSp
MYbkmGiaq5Q52rnJUknyuYollZ+koFl+MTMy7Y6uCO0Ag+vOup8j5apZbrWe
jVxPi2E0Ha8aQ0G1PjG6WAuRzGnYeTBw77Ttc8eXXOd7mjMUzwQCRZpJpiDl
2qd2ki9RaeqcnrROsRMjrOFiq6GclYSHNK3bfTMIbHt4qhKihI3wVBmFfkqM
z44nk+bdgAcawb0rU9KKX0sECGLvo95Hj6vmi03pN1V7H/397x9RH2yPq1vw
GwY2fw0PwQ+XRlNE8N1/Hhwcjvru3ycUBZHJ5a+fPOfKCk7jbyetl5+9qIvL
jJAfyxHVAAu9JkGzPA1BtPUFPhb2RpyW8SKqrrsRGJ3VQzA0Qs5VvTJLqWp2
j9HgMmnF5NzPGdxhFc6hQgdlbc4RktV3DuGBmtPMRqjelWt10dJTX4zZdAix
x2tZZzuu9RPJxy3Y7qY4AOJl42dbVpzn1IpDlAuBdmTp0Y9Pe0Nex8SnlhYR
txJGP2JMemWXlCyTlNGgzGoo3jC7wjStBxwWmFqcvhXbd7+tq7/OzUJx149k
593kMUsAT2jzWCMb+KSF2FlL6wMp9uxjVxpbSzeqignN+frPYUqYD3Lehabd
FuRG+qxgdAo0bOUhILEAcG4fFqyN0ub00ztFXRmz1G5uo3k127FxFloqDdbD
/MHV0m9lQ3/GduIvpmU1ZxImUrhoQQmlG0SvU0fiON3Kr8PYhBcnpK3brb3A
jm0LW6n2ppZ8d7JNYoY397MSQUI9wbGpSlDNT+yK4eh3Q7ExnPGbsB09GN3F
7ugufj9012c3fhPSiwciTXMXu+GsZ7uhvGUW4zdgWY2AbEGSW5g7IYkdOyG5
dabjw7GsZ0m2YMljHTthiR07Ybll1uPDcawnTLbgyAMeD8Sxdlm+rJktH76l
XfLsHgn5YHTr+ZMt6PK4yQeii70fiO7dIZUPR7WehtmCKk+67CS92LGT9D5s
7uXDUa2HbragysMTO6GKHTuhunmk4sNRrOc4tqDIMww7oYgdO6H4sImGD0e1
HqfYxk0eTtiNndjyYfz8ne1uY1BiG5ZmZ5k1O8rsprmF34CieWC0y1MEO2GI
HTthuGG84Leo5FZfwj+HpgIFt2PH8WVmrlOVzDiHQgLo53ZU8l89/jF+7zaK
flC+V05FOpfzyewy+kYhQzvREnFASYWz6J2Ziv+hP42DJF+GAqb2oyJ6Wla1
oTstKtccrgT6a9gpk6/uAefHH319KVcLc1UXL5Fjixf8l5vw8oIKWcv6j3r4
MURa89NPoMLBU2LsOEm4uKt2na70P1fi9ls9ckHjQAUXJYftw3f5eQj9Av/g
yRp05Cb6zpT2vZnpO0X0v2BkiQ0/+SHSc9WCfwrSHDmxfPohnX5S/X6kKsb9
nr8Jbl+gXBWSIJjrZZCB+3/M6/52Q03FqjLhfzXNRb56Toh7LYqkTDkMRzX9
XOra9zld38WNnmocU1WF0LAj/DkkXrP+B41YkHhOx910wAbC1wf4z1INo/8D
4LZs5etMAAA=

-->

</rfc>
