Additional Authentication Method Reference Values
draft-skyfire-oauth-amr-values-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Ankit Agarwal , Michael B. Jones | ||
| Last updated | 2026-07-06 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-skyfire-oauth-amr-values-00
Network Working Group A. Agarwal
Internet-Draft Skyfire Systems Inc.
Intended status: Standards Track M. Jones
Expires: 7 January 2027 Self-Issued Consulting
6 July 2026
Additional Authentication Method Reference Values
draft-skyfire-oauth-amr-values-00
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."
This Internet-Draft will expire on 7 January 2027.
Agarwal & Jones Expires 7 January 2027 [Page 1]
Internet-Draft Additional AMR Values July 2026
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
3. Authentication Method Reference Values . . . . . . . . . . . 3
3.1. "app" (Authenticator App) Method . . . . . . . . . . . . 3
3.2. "inp" (In-person Authentication) Method . . . . . . . . . 3
3.3. "vid" (Video Authentication) Method . . . . . . . . . . . 3
3.4. "bg" (Background Authentication) Method . . . . . . . . . 3
3.5. "email" (Code or link sent to e-mail) Method . . . . . . 3
3.6. "push" (Push notification to mobile phone) Method . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6.1. Authentication Method References Registry . . . . . . . . 4
6.1.1. "app" Method . . . . . . . . . . . . . . . . . . . . 4
6.1.2. "inp" Method . . . . . . . . . . . . . . . . . . . . 4
6.1.3. "vid" Method . . . . . . . . . . . . . . . . . . . . 4
6.1.4. "bg" Method . . . . . . . . . . . . . . . . . . . . . 5
6.1.5. "email" Method . . . . . . . . . . . . . . . . . . . 5
6.1.6. "push" Method . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Document History . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
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].
Agarwal & Jones Expires 7 January 2027 [Page 2]
Internet-Draft Additional AMR Values July 2026
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. "inp" (In-person Authentication) Method
inp: In-person Authentication
3.3. "vid" (Video Authentication) Method
vid: Video Authentication (live video interview)
3.4. "bg" (Background Authentication) Method
bg: Background Authentication (Silent network authentication of
phone number, device recognition, geo-location, etc.)
3.5. "email" (Code or link sent to e-mail) Method
email: Use of code or link sent to e-mail
Agarwal & Jones Expires 7 January 2027 [Page 3]
Internet-Draft Additional AMR Values July 2026
3.6. "push" (Push notification to mobile phone) Method
push: Push notification to mobile phone
4. Security Considerations
The security considerations defined in Authentication Method
Reference Values [RFC8176] apply to this specification.
5. Privacy Considerations
The privacy considerations defined in Authentication Method Reference
Values [RFC8176] apply to this specification.
6. IANA Considerations
6.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].
6.1.1. "app" Method
* Authentication Method Reference Name: app
* Authentication Method Reference Description: Authenticator App
* Change Controller: IETF
* Specification Document(s): (#appMethod) of this specification
6.1.2. "inp" Method
* Authentication Method Reference Name: inp
* Authentication Method Reference Description: In-person
Authentication
* Change Controller: IETF
* Specification Document(s): (#inpMethod) of this specification
6.1.3. "vid" Method
* Authentication Method Reference Name: vid
* Authentication Method Reference Description: Video Authentication
Agarwal & Jones Expires 7 January 2027 [Page 4]
Internet-Draft Additional AMR Values July 2026
* Change Controller: IETF
* Specification Document(s): (#vidMethod) of this specification
6.1.4. "bg" Method
* Authentication Method Reference Name: bg
* Authentication Method Reference Description: Background
Authentication
* Change Controller: IETF
* Specification Document(s): (#bgMethod) of this specification
6.1.5. "email" Method
* Authentication Method Reference Name: email
* Authentication Method Reference Description: Code or link sent to
e-mail
* Change Controller: IETF
* Specification Document(s): (#emailMethod) of this specification
6.1.6. "push" Method
* Authentication Method Reference Name: push
* Authentication Method Reference Description: Push notification to
mobile phone
* Change Controller: IETF
* Specification Document(s): (#pushMethod) of this specification
7. References
7.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,
<https://www.rfc-editor.org/rfc/rfc2119>.
Agarwal & Jones Expires 7 January 2027 [Page 5]
Internet-Draft Additional AMR Values July 2026
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8176] Jones, M., Hunt, P., and A. Nadalin, "Authentication
Method Reference Values", RFC 8176, DOI 10.17487/RFC8176,
June 2017, <https://www.rfc-editor.org/rfc/rfc8176>.
7.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-00, 5 July 2026,
<https://datatracker.ietf.org/doc/html/draft-skyfire-
oauth-kyapay-token-00>.
[IANA.AMR] IANA, "Authentication Method Reference Values", n.d.,
<https://www.iana.org/assignments/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,
<https://openid.net/specs/openid-connect-core-1_0.html>.
[RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token
(JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015,
<https://www.rfc-editor.org/rfc/rfc7519>.
Document History
[[ to be removed by the RFC Editor before publication as an RFC ]]
-00
* Initial draft.
Authors' Addresses
Ankit Agarwal
Skyfire Systems Inc.
Email: ankit_agarwal@yahoo.com
URI: https://skyfire.xyz
Agarwal & Jones Expires 7 January 2027 [Page 6]
Internet-Draft Additional AMR Values July 2026
Michael B. Jones
Self-Issued Consulting
Email: michael_b_jones@hotmail.com
URI: https://self-issued.info/
Agarwal & Jones Expires 7 January 2027 [Page 7]