2.1.1. Registering Attestation Statement Format Identifiers

WebAuthn attestation statement format identifiers are registered using the Specification Required policy (see Section 4.6 of [RFC8126]).¶

The "WebAuthn Attestation Statement Format Identifiers" registry is located at <https://www.iana.org/assignments/webauthn>. 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 Section 2.1.¶

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 Section 4.6 of [RFC8126]. 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.¶

2.1.2. Registration Request Processing

As noted in Section 2.1.1, 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.¶

2.1.3. 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 [WebAuthn]. Also, the Change Controller entry for each of those registrations is:¶

Change Controller:

W3C Web Authentication Working Group (public‑webauthn@w3.org)¶

2.2.1. Registering Extension Identifiers

WebAuthn extension identifiers are registered using the Specification Required policy (see Section 4.6 of [RFC8126]).¶

The "WebAuthn Extension Identifiers" registry is located at <https://www.iana.org/assignments/webauthn>. 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 Section 2.2.¶

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 Section 4.6 of [RFC8126]. 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.¶

2.2.2. Registration Request Processing

As noted in Section 2.2.1, 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.¶

2.2.3. 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 [WebAuthn]. Also, the Change Controller entry for each of those registrations is:¶

Change Controller:

W3C Web Authentication Working Group (public‑webauthn@w3.org)¶