Web Authorization Protocol A. Agarwal Internet-Draft Skyfire Systems Inc. Updates: 8176 (if approved) M. Jones Intended status: Standards Track Self-Issued Consulting Expires: 5 April 2027 N. Ali Experian S. Thumma Akamai 2 October 2026 Additional Authentication Method Reference Values draft-skyfire-oauth-amr-values-02 Abstract 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 This note is to be removed before publishing as an RFC. The latest revision of this draft can be found at https://skyfire- xyz.github.io/draft-skyfire-oauth-amr-values/draft-skyfire-oauth-amr- values.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-skyfire-oauth-amr-values/. Source for this draft and an issue tracker can be found at https://github.com/skyfire-xyz/draft-skyfire-oauth-amr-values. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." Agarwal, et al. Expires 5 April 2027 [Page 1] Internet-Draft Additional AMR Values October 2026 This Internet-Draft will expire on 5 April 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3 3. Authentication Method Reference Values . . . . . . . . . . . 3 3.1. "app" (Authenticator App) Method . . . . . . . . . . . . 3 3.2. "bg" (Background Authentication) Method . . . . . . . . . 3 3.3. "email" (Code or link sent to e-mail) Method . . . . . . 4 3.4. "code" (Code provided to and entered by user) Method . . 4 3.5. "url" (URL provided to and clicked on by user) Method . . 4 3.6. "push" (Push notification to mobile phone) Method . . . . 4 3.7. "facliv" (Facial Recognition with Liveness Check) Method . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.8. "sqa" (Security Question Answers) Method . . . . . . . . 4 3.9. "passkey" (Passkey) Method . . . . . . . . . . . . . . . 4 4. Updated Authentication Method Reference Value . . . . . . . . 4 4.1. "tel" (Telephone Call) Method . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7.1. Authentication Method References Registry . . . . . . . . 5 7.1.1. "app" Method . . . . . . . . . . . . . . . . . . . . 5 7.1.2. "bg" Method . . . . . . . . . . . . . . . . . . . . . 5 7.1.3. "email" Method . . . . . . . . . . . . . . . . . . . 6 7.1.4. "code" Method . . . . . . . . . . . . . . . . . . . . 6 7.1.5. "url" Method . . . . . . . . . . . . . . . . . . . . 6 7.1.6. "push" Method . . . . . . . . . . . . . . . . . . . . 6 7.1.7. "facliv" Method . . . . . . . . . . . . . . . . . . . 6 7.1.8. "sqa" Method . . . . . . . . . . . . . . . . . . . . 7 7.1.9. "passkey" Method . . . . . . . . . . . . . . . . . . 7 7.1.10. "tel" Method . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 Agarwal, et al. Expires 5 April 2027 [Page 2] Internet-Draft Additional AMR Values October 2026 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 8 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 8 Document History . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction The JWT [RFC7519] "amr" (Authentication Methods References) claim [OpenID.Core] contains values conveying authentication methods used in the authentication. They are registered in the IANA "Authentication Method Reference Values" registry [IANA.AMR]. Since the Authentication Method Reference Values [RFC8176] 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) [RFC7519], one use case for them is use in KYAPay tokens [I-D.skyfire-oauth-kyapay-token]. 2. 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. Authentication Method Reference Values The following Authentication Method Reference values are defined by this specification: 3.1. "app" (Authenticator App) Method app: Authenticator App (e.g., Okta Verify, Google Authenticator, Microsoft Authenticator) 3.2. "bg" (Background Authentication) Method bg: Background Authentication (Silent network authentication of phone number, device recognition, geo-location, etc.) Agarwal, et al. Expires 5 April 2027 [Page 3] Internet-Draft Additional AMR Values October 2026 3.3. "email" (Code or link sent to e-mail) Method email: Use of code or link sent to e-mail 3.4. "code" (Code provided to and entered by user) Method code: Code provided to and entered by user 3.5. "url" (URL provided to and clicked on by user) Method url: URL provided to and clicked on by user 3.6. "push" (Push notification to mobile phone) Method push: Push notification to mobile phone 3.7. "facliv" (Facial Recognition with Liveness Check) Method facliv: Facial Recognition with Liveness Check 3.8. "sqa" (Security Question Answers) Method sqa: Security Question Answers 3.9. "passkey" (Passkey) Method passkey: Passkey 4. Updated Authentication Method Reference Value The following Authentication Method Reference value is updated by this specification: 4.1. "tel" (Telephone Call) Method tel: Telephone call to the user at a registered number. The call may be used to provide information to the user, such as a code, that is then used in another channel. The call may be used for the user to provide information that the caller uses in the authentication. Agarwal, et al. Expires 5 April 2027 [Page 4] Internet-Draft Additional AMR Values October 2026 This definition replaces the one in [RFC8176], which is "Confirmation by telephone call to the user at a registered number. This authentication technique is sometimes also referred to as 'call back' [RFC4949]." 5. Security Considerations The security considerations defined in Authentication Method Reference Values [RFC8176] apply to this specification. Note that security questions are not acceptable authentication secrets under current NIST guidance [SP800-63-4]. 6. Privacy Considerations The privacy considerations defined in Authentication Method Reference Values [RFC8176] apply to this specification. 7. IANA Considerations 7.1. Authentication Method References Registry This specification registers the following Authentication Method Reference values in the IANA "Authentication Method Reference Values" registry [IANA.AMR] established by [RFC8176]. 7.1.1. "app" Method * Authentication Method Reference Name: app * Authentication Method Reference Description: Authenticator App * Change Controller: IETF * Specification Document(s): Section 3.1 of this specification 7.1.2. "bg" Method * Authentication Method Reference Name: bg * Authentication Method Reference Description: Background Authentication * Change Controller: IETF * Specification Document(s): Section 3.2 of this specification Agarwal, et al. Expires 5 April 2027 [Page 5] Internet-Draft Additional AMR Values October 2026 7.1.3. "email" Method * Authentication Method Reference Name: email * Authentication Method Reference Description: Code or link sent to e-mail * Change Controller: IETF * Specification Document(s): Section 3.3 of this specification 7.1.4. "code" Method * Authentication Method Reference Name: code * Authentication Method Reference Description: Code provided to and entered by user * Change Controller: IETF * Specification Document(s): Section 3.4 of this specification 7.1.5. "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): Section 3.5 of this specification 7.1.6. "push" Method * Authentication Method Reference Name: push * Authentication Method Reference Description: Push notification to mobile phone * Change Controller: IETF * Specification Document(s): Section 3.6 of this specification 7.1.7. "facliv" Method * Authentication Method Reference Name: facliv Agarwal, et al. Expires 5 April 2027 [Page 6] Internet-Draft Additional AMR Values October 2026 * Authentication Method Reference Description: Facial Recognition with Liveness Check * Change Controller: IETF * Specification Document(s): Section 3.7 of this specification 7.1.8. "sqa" Method * Authentication Method Reference Name: sqa * Authentication Method Reference Description: Security Question Answers * Change Controller: IETF * Specification Document(s): Section 3.8 of this specification 7.1.9. "passkey" Method * Authentication Method Reference Name: passkey * Authentication Method Reference Description: Passkey * Change Controller: IETF * Specification Document(s): Section 3.9 of this specification 7.1.10. "tel" Method * Authentication Method Reference Name: tel * Authentication Method Reference Description: Telephone call to the user at a registered number * Change Controller: IETF * Specification Document(s): Section 4.1 of this specification 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Agarwal, et al. Expires 5 April 2027 [Page 7] Internet-Draft Additional AMR Values October 2026 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8176] Jones, M., Hunt, P., and A. Nadalin, "Authentication Method Reference Values", RFC 8176, DOI 10.17487/RFC8176, June 2017, . 8.2. Informative References [I-D.skyfire-oauth-kyapay-token] Agarwal, A. and M. B. Jones, "KYAPay Token", Work in Progress, Internet-Draft, draft-skyfire-oauth-kyapay- token-01, 19 July 2026, . [IANA.AMR] IANA, "Authentication Method Reference Values", . [OpenID.Core] Sakimura, N., Bradley, J., Jones, M. B., Medeiros, B. de., and C. Mortimore, "OpenID Connect Core 1.0 incorporating errata set 2", 15 December 2023, . [RFC4949] Shirey, R., "Internet Security Glossary, Version 2", FYI 36, RFC 4949, DOI 10.17487/RFC4949, August 2007, . [RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015, . [SP800-63-4] National Institute of Standards (NIST), "NIST SP 800-63-4: Digital Identity Guidelines", July 2025, . Acknowledgments We would like to thank Jean Diaconu and Rob Zagarella for their contributions to the specification. Agarwal, et al. Expires 5 April 2027 [Page 8] Internet-Draft Additional AMR Values October 2026 Document History [[ to be removed by the RFC Editor before publication as an RFC ]] -02 * Updated the definition of "tel" to incorporate calls to provide information such as codes and removed "call". * Renamed "psk" to "passkey" because of the potential confusion with pre-shared key. * Added warning in Security Considerations that security questions are not acceptable authentication secrets under current NIST guidance. * Added {:vspace} syntax to definition list entries. -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. Authors' Addresses Ankit Agarwal Skyfire Systems Inc. Email: ankit_agarwal@yahoo.com URI: https://skyfire.xyz Michael B. Jones Self-Issued Consulting Email: michael_b_jones@hotmail.com URI: https://self-issued.info/ Nash Ali Experian Email: nash.ali@experian.com Agarwal, et al. Expires 5 April 2027 [Page 9] Internet-Draft Additional AMR Values October 2026 Srinivasa Thumma Akamai Email: sthumma@akamai.com Agarwal, et al. Expires 5 April 2027 [Page 10]