]> 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 The JWT "amr" (Authentication Methods References) claim contains values conveying authentication methods used in the authentication. This specification defines additional Authentication Method Reference values beyond those already registered to represent additional authentication methods in use today. 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 The JWT "amr" (Authentication Methods References) claim contains values conveying authentication methods used in the authentication. They are registered in the IANA "Authentication Method Reference Values" registry . Since the Authentication Method Reference Values specification was published, several new authentication methods have been developed and/or come into widespread use. This specification defines additional Authentication Method Reference values to represent these additional authentication methods in use today. While these Authentication Method Reference 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.

Authentication Method Reference Values The following Authentication Method Reference values are defined by this specification:

"app" (Authenticator App) Method

app:

Authenticator App (e.g., Okta Verify, Google Authenticator, Microsoft Authenticator)

"bg" (Background Authentication) Method

bg:

Background Authentication (Silent network authentication of phone number, device recognition, geo-location, etc.)

"email" (Code or link sent to e-mail) Method

email:

Use of code or link sent to e-mail

"call" (Voice call providing code) Method

call:

Voice call providing code

"code" (Code provided to and entered by user) Method

code:

Code provided to and entered by user

"url" (URL provided to and clicked on by user) Method

url:

URL provided to and clicked on by user

"push" (Push notification to mobile phone) Method

push:

Push notification to mobile phone

"facliv" (Facial Recognition with Liveness Check) Method

facliv:

Facial Recognition with Liveness Check

"sqa" (Security Question Answers) Method

sqa:

Security Question Answers

"psk" (Passkey) Method

psk:

Passkey

Security Considerations The security considerations defined in Authentication Method Reference Values apply to this specification.

Privacy Considerations The privacy considerations defined in Authentication Method Reference Values apply to this specification.

IANA Considerations

Authentication Method References Registry This specification registers the following Authentication Method Reference values in the IANA "Authentication Method Reference Values" registry established by .

"app" Method

• Authentication Method Reference Name: app
• Authentication Method Reference Description: Authenticator App
• Change Controller: IETF
• Specification Document(s): of this specification

"bg" Method

• Authentication Method Reference Name: bg
• Authentication Method Reference Description: Background Authentication
• Change Controller: IETF
• Specification Document(s): of this specification

"email" Method

• Authentication Method Reference Name: email
• Authentication Method Reference Description: Code or link sent to e-mail
• Change Controller: IETF
• Specification Document(s): of this specification

"call" Method

• Authentication Method Reference Name: call
• Authentication Method Reference Description: Voice call providing code
• Change Controller: IETF
• Specification Document(s): of this specification

"code" Method

• Authentication Method Reference Name: code
• Authentication Method Reference Description: Code provided to and entered by user
• Change Controller: IETF
• Specification Document(s): of this specification

"url" Method

• Authentication Method Reference Name: url
• Authentication Method Reference Description: URL provided to and clicked on by user
• Change Controller: IETF
• Specification Document(s): of this specification

"push" Method

• Authentication Method Reference Name: push
• Authentication Method Reference Description: Push notification to mobile phone
• Change Controller: IETF
• Specification Document(s): of this specification

"facliv" Method

• Authentication Method Reference Name: facliv
• Authentication Method Reference Description: Facial Recognition with Liveness Check
• Change Controller: IETF
• Specification Document(s): of this specification

"sqa" Method

• Authentication Method Reference Name: sqa
• Authentication Method Reference Description: Security Question Answers
• Change Controller: IETF
• Specification Document(s): of this specification

"psk" Method

• Authentication Method Reference Name: psk
• Authentication Method Reference Description: Passkey
• Change Controller: IETF
• Specification Document(s): of this specification

References Normative References The "amr" (Authentication Methods References) claim is defined and registered in the IANA "JSON Web Token Claims" registry, but no standard Authentication Method Reference values are currently defined. This specification establishes a registry for Authentication Method Reference values and defines an initial set of Authentication Method Reference values. 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 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. 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

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

• Moved "inp" and "vid" methods to the ID Verification spec.
• Added "call", "code", "url", "facliv", "sqa", and "psk" methods.
• Added Nash Ali and Srinivasa Thumma as authors.

-00

• Initial draft.