]> Skyfire Systems Inc.

ankit_agarwal@yahoo.com https://skyfire.xyz

Self-Issued Consulting

michael_b_jones@hotmail.com https://self-issued.info/

Experian

nash.ali@experian.com

Akamai

sthumma@akamai.com

Security Web Authorization Protocol agent identity agentic payment commerce 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. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Source for this draft and an issue tracker can be found at .

Introduction 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. It also creates a registry for Identity Verification Methods Values and initializes the registry with the values defined in this specification. 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. 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 can be used, either with the "ivm" claim, or separately. Likewise, Vectors of Trust can be used to provide more detail, either with the "ivm" claim, or separately. While this claim and values are general purpose and can be used in any JSON Web Token (JWT) , one use case for them is use in KYAPay tokens .

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Identity Verification Methods 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 . 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.

"ivm" (Identity Verification Methods) Claim 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 SHOULD be from those registered in the IANA "Identity Verification Methods" registry established by ; parties using this claim will need to agree upon the meanings of any unregistered values used, which may be context specific.

Identity Verification Method Values The following Identity Verification Method values are defined by this specification.

"dbv" (Database Verification of PII) Method

dbv:

Database Verification of PII (match of name/address/dob/ssn/nid, etc.) using an unspecified number of consumer reporting data sources

"dbv1" (Database Verification of PII One Source) Method

dbv1:

Database Verification of PII (match of name/address/dob/ssn/nid, etc.) using one consumer reporting data source

"dbvm" (Database Verification of PII Multiple Sources) Method

dbvm:

Database Verification of PII (match of name/address/dob/ssn/nid, etc.) using Multiple consumer reporting data sources

"dig" (Digital ID Document Verification) Method

dig:

Digital ID Document Verification (for example Mobile Driver's Licenses)

"phy" (Physical ID Document Verification) Method

phy:

Physical ID Document Verification (for example via a real time capture of the front and back of DL or Passport photo page)

"sec" (Secondary Document Verification) Method

sec:

Secondary Document Verification (for example via bank statements, financial statements, utility bills, government-issued papers, etc.)

"inp" (In-person Verification) Method

inp:

In-person Verification

"vid" (Video Verification) Method

vid:

Video Verification (live video interview)

Security Considerations The security considerations defined in JSON Web Token (JWT) apply to this specification.

Privacy Considerations The privacy considerations defined in JSON Web Token (JWT) apply to this specification.

IANA Considerations

JSON Web Token Claims Registration This specification registers the following Claim in the IANA "JSON Web Token Claims" established by .

"ivm" Claim

• Claim Name: ivm
• Claim Description: Identity Verification Methods
• Change Controller: Michael B. Jones - michael_b_jones@hotmail.com
• Reference: of this specification

Identity Verification Methods Registry This specification establishes the IANA "Identity Verification Methods" registry for ivm 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 . Values are registered on an Expert Review basis after a three-week review period on the <jwt-reg-review@ietf.org> 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. Registration requests sent to the mailing list for review should use an appropriate subject (e.g., "Request to register Identity Verification Method value: example"). 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 iesg@ietf.org mailing list) for resolution. IANA must only accept registry updates from the Designated Experts and should direct all requests for registration to the review mailing list. 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 . 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.

Registration Template

Identity Verification Method Name:

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 RECOMMENDED 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.

Identity Verification Method Description:

Brief description of the Identity Verification Method (e.g., "Physical ID Document verification").

Change Controller:

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.

Specification Document(s):

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.

Initial Registry Contents

"dbv" Method

• Identity Verification Method Name: dbv
• Identity Verification Method Description: Database Verification of PII
• Change Controller: IETF
• Specification Document(s): of this specification

"dbv1" Method

• Identity Verification Method Name: dbv1
• Identity Verification Method Description: Database Verification of PII One Source
• Change Controller: IETF
• Specification Document(s): of this specification

"dbvm" Method

• Identity Verification Method Name: dbvm
• Identity Verification Method Description: Database Verification of PII Multiple Sources
• Change Controller: IETF
• Specification Document(s): of this specification

"dig" Method

• Identity Verification Method Name: dig
• Identity Verification Method Description: Digital ID Document Verification
• Change Controller: IETF
• Specification Document(s): of this specification

"phy" Method

• Identity Verification Method Name: phy
• Identity Verification Method Description: Physical ID Document Verification
• Change Controller: IETF
• Specification Document(s): of this specification

"sec" Method

• Identity Verification Method Name: sec
• Identity Verification Method Description: Secondary Document Verification
• Change Controller: IETF
• Specification Document(s): of this specification

"inp" Method

• Identity Verification Method Reference Name: inp
• Identity Verification Method Reference Description: In-person Verification
• Change Controller: IETF
• Specification Document(s): of this specification

"vid" Method

• Identity Verification Method Reference Name: vid
• Identity Verification Method Reference Description: Video Verification
• Change Controller: IETF
• Specification Document(s): of this specification

References Normative References 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. 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. 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. Informative References 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). 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. This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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. Skyfire Systems Inc. Self-Issued Consulting 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. IANA IANA

Acknowledgments We would like to thank Jean Diaconu and Rob Zagarella for their contributions to the specification.

Document History [[ to be removed by the RFC Editor before publication as an RFC ]] -02

• Described that the "ivm" claim contains a set of identity verification methods that succeeded.
• Described the relationship to the OpenID Identity Assurance claims.
• Added {:vspace} syntax to definition list entries.

-01

• Added "dbv1", "dbvm", "inp", and "vid" methods.
• Added Nash Ali and Srinivasa Thumma as authors.

-00

• Initial draft.