Registries for Web Authentication (WebAuthn)Google1600 Amphitheatre ParkwayMountain ViewCA94043United States of Americajdhodges@google.comhttps://kingsmountain.com/people/Jeff.Hodges/Qualcomm Technologies Inc.5775 Morehouse DriveSan DiegoCA92121United States of America+1 858 651 7200mandyam@qti.qualcomm.comMicrosoftmbj@microsoft.comhttps://self-issued.info/
Security
W3C WebAuthn Working Groupwebauthnattestationextensionsregistry
This specification defines IANA registries for W3C Web Authentication (WebAuthn)
attestation statement format identifiers and extension identifiers.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
.
Copyright Notice
Copyright (c) 2020 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
() 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 Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Table of Contents
. Introduction
. Requirements Notation and Conventions
. IANA Considerations
. WebAuthn Attestation Statement Format Identifiers Registry
. Registering Attestation Statement Format Identifiers
. Registration Request Processing
. Initial Values in the WebAuthn Attestation Statement Format Identifiers Registry
. WebAuthn Extension Identifiers Registry
. Registering Extension Identifiers
. Registration Request Processing
. Initial Values in the WebAuthn Extension Identifiers Registry
. Security Considerations
. Normative References
Acknowledgements
Authors' Addresses
Introduction
This specification establishes IANA registries for W3C Web
Authentication attestation
statement format identifiers and extension identifiers. The initial
values for these registries are in the IANA Considerations section of
the specification.
Requirements Notation and ConventionsThe 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.IANA ConsiderationsThis specification establishes two registries:
the "WebAuthn Attestation Statement Format Identifiers" registry
(see )
the "WebAuthn Extension Identifiers" registry (see )
Any additional processes established by the expert(s) after the
publication of this document will be recorded on the registry web page
at the discretion of the expert(s).WebAuthn Attestation Statement Format Identifiers Registry
WebAuthn attestation statement format identifiers are strings whose semantic, syntactic,
and string-matching criteria are specified in the
"Attestation Statement Format Identifiers" section of ,
along with the concepts of attestation and attestation statement formats.
Registered attestation statement format identifiers are those that have been added to the
registry by following the procedure in
.
Each attestation statement format identifier added to this registry
MUST be unique amongst the set of registered
attestation statement format identifiers.Registered attestation statement format identifiers
MUST be a maximum of 32 octets in length and
MUST consist only of printable ASCII characters, excluding backslash
and double quote, i.e., VCHAR as defined in but without %x22 and %x5c. Attestation statement
format identifiers are case sensitive and may not match other
registered identifiers in a case-insensitive manner unless the
designated experts determine that there is a compelling reason to
allow an exception.Registering Attestation Statement Format IdentifiersWebAuthn attestation statement format identifiers are registered
using the Specification Required policy (see ).
The "WebAuthn Attestation Statement Format Identifiers" registry is located at
.
Registration requests can be made by following the instructions located there or by
sending an email to the webauthn-reg-review@ietf.org mailing list.
Registration requests consist of at least the following information:
WebAuthn Attestation Statement Format Identifier:
An identifier meeting the requirements given in
.
Description:
A relatively short description of the attestation format.
Specification Document(s):
Reference to the document or documents that specify the
attestation statement format.
Change Controller:
For Standards Track RFCs, list "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.
Notes:
[optional]
Registrations MUST reference a freely available,
stable specification, e.g., as described in . This specification
MUST include security and privacy considerations
relevant to the attestation statement format.
Note that WebAuthn attestation statement format identifiers can be registered by third
parties (including the expert(s) themselves), if the expert(s) determines that an
unregistered attestation statement format is widely deployed and not likely to be
registered in a timely manner otherwise.
Such registrations still are subject to the requirements defined, including the need to
reference a specification.
Registration Request Processing
As noted in ,
WebAuthn attestation statement format identifiers are registered using the
Specification Required policy.
The expert(s) will clearly identify any issues that cause a registration to be refused,
such as an incompletely specified attestation format.
When a request is approved, the expert(s) will inform IANA, and the registration will
be processed.
The IESG is the arbiter of any objection.
Initial Values in the WebAuthn Attestation Statement Format Identifiers Registry
The initial values for the "WebAuthn Attestation Statement Format
Identifiers" registry have been
populated with the values listed in the
"WebAuthn Attestation Statement Format Identifier
Registrations" section
of .
Also, the Change Controller entry for each of those registrations is:
Change Controller:
W3C Web Authentication Working Group (public‑webauthn@w3.org)
WebAuthn Extension Identifiers Registry
WebAuthn extension identifiers are strings whose semantic, syntactic,
and string-matching criteria are specified in the
"Extension Identifiers" section of .
Registered extension identifiers are those that have been added to the
registry by following the procedure in
.
Each extension identifier added to this registry MUST be unique
amongst the set of registered extension identifiers.
Registered extension identifiers MUST be a maximum
of 32 octets in length and MUST consist only of
printable ASCII characters, excluding backslash and double quote,
i.e., VCHAR as defined in
but without %x22 and %x5c. Extension identifiers are case sensitive
and may not match other registered identifiers in a case-insensitive
manner unless the designated experts determine that there is a
compelling reason to allow an exception.Registering Extension IdentifiersWebAuthn extension identifiers are registered using the
Specification Required policy (see ).The "WebAuthn Extension Identifiers" registry is located at . Registration requests can be made by following
the instructions located there or by sending an email to the
webauthn-reg-review@ietf.org mailing list.Registration requests consist of at least the following information:
WebAuthn Extension Identifier:
An identifier meeting the requirements given in
.
Description:
A relatively short description of the extension.
Specification Document(s):
Reference to the document or documents that specify the extension.
Change Controller:
For Standards Track RFCs, list "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.
Notes:
[optional]
Registrations MUST reference a freely available,
stable specification, e.g., as described in . This specification
MUST include security and privacy considerations
relevant to the extension.Note that WebAuthn extensions can be registered by third parties
(including the expert(s) themselves), if the expert(s) determines
that an unregistered extension is widely deployed and not likely to
be registered in a timely manner otherwise. Such registrations still
are subject to the requirements defined, including the need to
reference a specification.Registration Request Processing
As noted in ,
WebAuthn extension identifiers are registered using the
Specification Required policy.
The expert(s) will clearly identify any issues that cause a registration to be refused,
such as an incompletely specified extension.
When a request is approved, the expert(s) will inform IANA, and the registration will
be processed.
The IESG is the arbiter of any objection.
Initial Values in the WebAuthn Extension Identifiers Registry
The initial values for the "WebAuthn Extension Identifiers"
registry have been
populated with the values listed in the
"WebAuthn Extension Identifier Registrations" section
of .
Also, the Change Controller entry for each of those registrations is:
Change Controller:
W3C Web Authentication Working Group (public‑webauthn@w3.org)
Security ConsiderationsSee for relevant security
considerations.Normative ReferencesASCII format for network interchangeKey words for use in RFCs to Indicate Requirement LevelsIn 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.Augmented BNF for Syntax Specifications: ABNFInternet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]Guidelines for Writing an IANA Considerations Section in RFCsMany protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.This is the third edition of this document; it obsoletes RFC 5226.Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsRFC 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.Web Authentication: An API for accessing Public Key CredentialsGooglebalfanz@google.comGoogleaczeskis@google.comPayPaljdhodges@google.comMozillajc@mozilla.comMicrosoftmbj@microsoft.comhttp://self-issued.info/Microsoftakshayku@microsoft.comMicrosofthuliao@microsoft.comNok Nok Labsrolf@noknok.comYubicoemil@yubico.comAcknowledgementsThanks to for valuable comments
and suggestions. Thanks to and
for their Area Director sponsorship
of this specification. Thanks to ,
, ,
, , , , , , and
for their reviews.Authors' AddressesGoogle1600 Amphitheatre ParkwayMountain ViewCA94043United States of Americajdhodges@google.comhttps://kingsmountain.com/people/Jeff.Hodges/Qualcomm Technologies Inc.5775 Morehouse DriveSan DiegoCA92121United States of America+1 858 651 7200mandyam@qti.qualcomm.comMicrosoftmbj@microsoft.comhttps://self-issued.info/