wdiff rfc8809.original rfc8809.txt

W3C WebAuthn Working Group

Internet Engineering Task Force (IETF) J. Hodges
Internet-Draft
Request for Comments: 8809 Google
Intended status:
Category: Informational G. Mandyam
Expires: December 3, 2020
ISSN: 2070-1721 Qualcomm Technologies Inc.
M. Jones
Microsoft
June 1,
August 2020

Registries for Web Authentication (WebAuthn)
draft-hodges-webauthn-registries-10

Abstract

This specification defines IANA registries for W3C Web Authentication
(WebAuthn) attestation statement format identifiers and extension
identifiers.

Note to Readers

_RFC EDITOR: please remove this section before publication_

This is a work-in-progress.

The issues list can be found at https://github.com/w3c/webauthn/
issues?q=is%3Aopen+is%3Aissue+label%3Aspec%3Awebauthn-registries [1].

The most recent _published_ draft revision is at
https://tools.ietf.org/html/draft-hodges-webauthn-registries [2].

The editors' draft is at https://github.com/w3c/webauthn/blob/master/
draft-hodges-webauthn-registries.txt [3]

Changes in the editors' draft, both proposed and incorporated, are
listed at https://github.com/w3c/webauthn/
pulls?q=is%3Apr+label%3Aspec%3Awebauthn-registries [4]

Status of This Memo

This Internet-Draft document is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the Internet Engineering Task Force
(IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list It represents the consensus of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents valid
approved by the IESG are candidates for a maximum any level of Internet
Standard; see Section 2 of RFC 7841.

Information about the current status of six months this document, any errata,
and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained 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 December 3, 2020.
https://www.rfc-editor.org/info/rfc8809.

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 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

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Notation and Conventions . . . . . . . . . . 3
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
2.1. WebAuthn Attestation Statement Format Identifier Identifiers Registry 3
2.1.1. Registering Attestation Statement Format Identifiers 4
2.1.2. Registration Request Processing . . . . . . . . . . . 5
2.1.3. Initial Values in the WebAuthn Attestation Statement
Format
Identifier Identifiers Registry Values . . . . . . . . . . . . . 5
2.2. WebAuthn Extension Identifier Identifiers Registry . . . . . . . . . 5
2.2.1. Registering Extension Identifiers . . . . . . . . . . 6
2.2.2. Registration Request Processing . . . . . . . . . . . 6
2.2.3. Initial Values in the WebAuthn Extension Identifier Identifiers
Registry Values 7
3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
5. Document History . . . . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. Normative References . . . . . . . . . . . . . . . . . . 9
6.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Acknowledgements
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10

1. Introduction

This specification establishes IANA registries for W3C Web
Authentication [WebAuthn] attestation statement format identifiers
and extension identifiers. The initial values for these registries
are in the IANA Considerations section of the [WebAuthn]
specification.

1.1. Requirements Notation and Conventions

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.

2. IANA Considerations

This specification establishes two registries:

* the "WebAuthn Attestation Statement Format Identifier" registry;
see Identifiers" registry
(see Section 2.1.
o 2.1)

* the "WebAuthn Extension Identifier" registry; see Identifiers" registry (see Section 2.2.

[[ Per discussions in an email thread between the authors and IANA (
"[IANA #1154148]" ), it is requested that the registries be located
at <https://www.iana.org/assignments/webauthn>. RFC Editor - please
delete this request after the registries have been created. ]] 2.2)

Any additional processes established by the expert(s) after the
publication of this document will be recorded on the registry Web web
page at the expert(s)' discretion. discretion of the expert(s).

2.1. WebAuthn Attestation Statement Format Identifier Identifiers Registry

WebAuthn attestation statement format identifiers are strings whose
semantic, syntactic, and string-matching criteria are specified in
[WebAuthn]
the "Attestation Statement Format Identifiers" [5],
(https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-attstn-fmt-
ids) section of [WebAuthn], 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
Section 2.1.1.

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
[RFC20] characters, excluding backslash and doublequote, double quote, i.e., VCHAR
as defined in [RFC5234] 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
designated experts determine that there is a compelling reason to
allow an exception.

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 "WebAuthn Attestation Statement Format Identifiers" registry is
located at https://www.iana.org/assignments/webauthn [6]. <https://www.iana.org/assignments/webauthn>. Registration
requests can be made by following the instructions located there, there or
by sending an e-mail email to the webauthn-reg-
review@ietf.org 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 above in Section 2.1.
o

Description:
A relatively short description of the attestation format.
o

Specification Document(s):
Reference to the document or documents that specify the
attestation statement format.
o

Change Controller:
For Standards Track RFCs, list the "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.
o

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) determine 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 Identifier
Identifiers Registry Values

The initial values for the WebAuthn "WebAuthn Attestation Statement Format
Identifier Registry are to be
Identifiers" registry have been populated from with the values listed in
the "WebAuthn Attestation Statement Format Identifier Registrations" [7]
(https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-att-fmt-
reg) section of [WebAuthn]. Also, the Change Controller entry to be used for
each of those registrations is:

Change Controller:
W3C Web Authentication Working Group -
public-webauthn@w3.org (public-webauthn@w3.org)

2.2. WebAuthn Extension Identifier Identifiers Registry

WebAuthn extension identifiers are strings whose semantic, syntactic,
and string-matching criteria are specified in [WebAuthn] the "Extension
Identifiers" [8]. (https://www.w3.org/TR/2019/REC-webauthn-1-
20190304/#sctn-extension-id) section of [WebAuthn].

Registered extension identifiers are those that have been added to
the registry by following the procedure in Section 2.2.1.

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 doublequote, double quote, i.e., VCHAR as defined in [RFC5234] 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 designated experts determine that there is a
compelling reason to allow an exception.

2.2.1. Registering Extension Identifiers

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

The WebAuthn extension identifiers "WebAuthn Extension Identifiers" registry is located at
https://www.iana.org/assignments/webauthn.
<https://www.iana.org/assignments/webauthn>. Registration requests
can be made by following the instructions located there, there or by sending
an
e-mail 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 above in Section 2.2.
o

Description:
A relatively short description of the extension.
o

Specification Document(s):
Reference to the document or documents that specify the extension.
o

Notes:
[optional]

Note that WebAuthn extensions can be registered by third parties
(including the expert(s) themselves), if the expert(s) determine 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 Identifier Identifiers Registry Values

The initial values for the WebAuthn "WebAuthn Extension Identifier Registry are
to be Identifiers" registry
have been populated from with the values listed in the "WebAuthn Extension
Identifier Registrations" [9] (https://www.w3.org/TR/2019/REC-webauthn-1-
20190304/#sctn-extensions-reg) section of [WebAuthn]. Also, the
Change Controller entry to be used for each of those registrations is:

Change Controller:
W3C Web Authentication Working Group -
public-webauthn@w3.org (public-webauthn@w3.org)

3. Security Considerations

See [WebAuthn] for relevant security considerations.

4. Acknowledgements

Thanks to Mark Nottingham for valuable comments and suggestions.
Thanks to Kathleen Moriarty and Benjamin Kaduk for their Area
Director sponsorship of this specification. Thanks to Amanda Baber,
Sarah Banks, Alissa Cooper, Roman Danyliw, Murray Kucherawy, Paul
Kyzivat, Barry Leiba, Hilarie Orman, Magnus Westerlund, and Robert
Wilton for their reviews.

5. Document History

[[ to be removed by the RFC Editor before publication as an RFC ]]

-10

o Changed IESG to IETF in Change Controller instructions, per
suggestion by Magnus Westerlund.

-09

o Added Change Controller fields to registries, per suggestion by
Magnus Westerlund.
o Applied editorial suggestions by Amanda Baber, Murray Kucherawy,
and Barry Leiba.

-08

o Addressed review feedback by Murray Kucherawy.
o Added BCP 14 Requirements Notation and Conventions section.
o Referenced RFC 20, which defines ASCII characters.

o Applied editorial cleanups.

-07

o Removed a duplicate URI listing pointed out by Hilarie Orman.

-06

o Addressed Gen-Art review comments by Paul Kyzivat by deleting text
about designated experts defining additional registry fields.
o Addressed Ops-Dir review comments by Sarah Banks by deleting text
that duplicated requirements already specified in RFC 8126.
o Addressed Security review comments by Hilarie Orman by deleting
unnecessary text about attestation statement formats lacking
complete specifications.
o Replaced uses of the URL https://www.w3.org/TR/webauthn/ with
https://www.w3.org/TR/2019/REC-webauthn-1-20190304/ so that the
reference remains stable after the level 2 WebAuthn specification
is published.

-05

o Updated to address the solicited IANA review comments, per
discussions in an email thread between the authors and IANA (
"[IANA #1154148]" ).

-04

o Update per Benjamin Kaduk's further AD review: Remove 'final' wrt
IESG arbitrating objections; Add explicit requirement for
extension or attestation specs to include security and privacy
considerations.
o Update per IANA review: Move "IANA considerations section up in
doc to encompass (former) sections 2 and 3.

-03

o Update per Benjamin Kaduk's AD review. Align with RFC 8288,
rather than draft-nottingham-rfc5988bis.

-02

o Refresh now that the WebAuthn spec is at Recommendation (REC)
maturity level.

-01
o Refresh now that the WebAuthn Committee Recommendation (CR) draft
is pending.

-00

o Initial version, based on draft-nottingham-rfc5988bis.

6. References

6.1. Normative References

[RFC20] Cerf, V., "ASCII format for Network Interchange", network interchange", STD 80,
RFC 20, DOI 10.17487/RFC0020, October 1969,
<http://www.rfc-editor.org/info/rfc20>.
<https://www.rfc-editor.org/info/rfc20>.

[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/info/rfc2119>.

[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>.

[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.

[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/info/rfc8174>.

[WebAuthn] Balfanz, D., Czeskis, A., Hodges, J., Jones, J., J.C., Jones,
M., Kumar, A., Liao, A., Lindemann, R., and E. Lundberg,
"Web Authentication: An API for accessing Public Key
Credentials", World Wide Web Consortium
(W3C) Recommendation, 4 March 2019,
<https://www.w3.org/TR/2019/REC-webauthn-1-20190304/>.

6.2. URIs

[1] https://github.com/w3c/webauthn/
issues?q=is%3Aopen+is%3Aissue+label%3Aspec%3Awebauthn-registries

[2] https://tools.ietf.org/html/draft-hodges-webauthn-registries
[3] https://github.com/w3c/webauthn/blob/master/draft-hodges-
webauthn-registries.txt

[4] https://github.com/w3c/webauthn/
pulls?q=is%3Apr+label%3Aspec%3Awebauthn-registries

[5] https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-attstn-
fmt-ids

[6] https://www.iana.org/assignments/webauthn

[7] https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-att-fmt-
reg

[8] https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-
extension-id

[9] https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-
extensions-reg

Acknowledgements

Authors' Addresses

Jeff Hodges
Google
1600 Amphitheater Amphitheatre Parkway
Mountain View, California CA 94043
US
United States of America

Email: jdhodges@google.com
URI: https://kingsmountain.com/people/Jeff.Hodges/

Giridhar Mandyam
Qualcomm Technologies Inc.
5775 Morehouse Drive
San Diego, California CA 92121
USA
United States of America

Phone: +1 858 651 7200
Email: mandyam@qti.qualcomm.com

Michael B. Jones
Microsoft

Email: mbj@microsoft.com
URI: https://self-issued.info/