Skip to main content

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

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 8809.
Authors Jeff Hodges , Giridhar Mandyam , Michael B. Jones
Last updated 2019-11-12 (Latest revision 2019-10-18)
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
Additional resources
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 8809 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Benjamin Kaduk
Send notices to (None)
draft-hodges-webauthn-registries-03
W3C WebAuthn Working Group                                     J. Hodges
Internet-Draft                                                    Google
Intended status: Informational                                G. Mandyam
Expires: April 20, 2020                       Qualcomm Technologies Inc.
                                                                M. Jones
                                                               Microsoft
                                                            Oct 18, 2019

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

Abstract

   This specification defines IANA registries for W3C Web Authentication
   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 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

Hodges, et al.           Expires April 20, 2020                 [Page 1]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

   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 April 20, 2020.

Copyright Notice

   Copyright (c) 2019 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 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
   2.  WebAuthn Attestation Statement Format Identifier Registry . .   3
     2.1.  Registering Attestation Statement Format Identifiers  . .   3
     2.2.  Registration Request Processing . . . . . . . . . . . . .   4
     2.3.  Initial WebAuthn Attestation Statement Format Identifier
           Registry Values . . . . . . . . . . . . . . . . . . . . .   4
   3.  WebAuthn Extension Identifier Registry  . . . . . . . . . . .   4
     3.1.  Registering Extension Identifiers . . . . . . . . . . . .   5
     3.2.  Registration Request Processing . . . . . . . . . . . . .   6
     3.3.  Initial WebAuthn Extension Identifier Registry Values . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  WebAuthn Attestation Statement Format Identifier and
           Extension Identifiers Registries  . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Document History  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

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

Hodges, et al.           Expires April 20, 2020                 [Page 2]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

   are in the IANA Considerations section of the [WebAuthn]
   specification.

2.  WebAuthn Attestation Statement Format Identifier Registry

   WebAuthn attestation statement format identifiers are strings whose
   semantic, syntactic, and string-matching criteria are specified in
   [WebAuthn] "Attestation Statement Format Identifiers" [5], 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.

   Each attestation statement format identifier added to this registry
   MUST be unique amongst the set of registered attestation statement
   format identifiers.  The Experts(s) MAY also designate attestation
   statement formats as proprietary if they lack complete
   specifications, and will assign a prefix indicating as such to the
   identifier.

   Registered attestation statement format identifiers MUST be a maximum
   of 32 octets in length and MUST consist only of printable USASCII
   characters, excluding backslash and doublequote, i.e., VCHAR as
   defined in [RFC5234] but without %x22 and %x5c.  Attestation
   statement format identifiers are case sensitive.  Attestation
   statement format identifiers 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.

2.1.  Registering Attestation Statement Format Identifiers

   WebAuthn attestation statement format identifiers are registered
   using the Specification Required policy (see Section 4.6 of
   [RFC8126]), which implies review and approval by a designated expert.

   The WebAuthn attestation statement format identifiers registry is
   located at https://www.iana.org/assignments/(fill-in-here-per-IANA)/
   [6].  Registration requests can be made by following the instructions
   located there, or by sending an e-mail to the "public-
   webauthn@w3.org" mailing list.

   Registration requests consist of at least the following information:

   o  *WebAuthn Attestation Statement Format Identifier*: An identifier
      meeting the requirements given above in Section 2.

Hodges, et al.           Expires April 20, 2020                 [Page 3]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

   o  *Description*: A relatively short description of the attestation
      format.
   o  *Reference*: Reference to the specification of the attestation
      statement format.
   o  Notes: [optional]

   The expert(s) can define additional fields to be collected in the
   registry.

   Registrations MUST reference a freely available, stable
   specification, e.g., as described in Section 7 of [RFC2026].

   Note that WebAuthn attestation statement format identifiers can be
   registered by third parties (including the expert(s) themselves), if
   the expert(s) determine 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.2.  Registration Request Processing

   As noted in Section 2.1, WebAuthn attestation statement format
   identifiers are registered using the Specification Required policy,
   implying review and approval by a designated expert.

   The expert(s) will clearly identify any issues which cause a
   registration to be refused.

   When a request is approved, the expert(s) will inform IANA, and the
   registration will be processed.  The IESG is the final arbiter of any
   objection.

2.3.  Initial WebAuthn Attestation Statement Format Identifier Registry
      Values

   The initial values for the WebAuthn Attestation Statement Format
   Identifier Registry are to be populated from the values listed in
   "WebAuthn Attestation Statement Format Identifier Registrations" [7]
   of [WebAuthn].

3.  WebAuthn Extension Identifier Registry

   WebAuthn extension identifiers are strings whose semantic, syntactic,
   and string-matching criteria are specified in [WebAuthn] "Extension
   Identifiers" [8].

Hodges, et al.           Expires April 20, 2020                 [Page 4]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

   Registered extension identifiers are those that have been added to
   the registry by following the procedure in Section 3.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 USASCII characters,
   excluding backslash and doublequote, i.e., VCHAR as defined in
   [RFC5234] but without %x22 and %x5c.  Extension identifiers are case
   sensitive.  Extension identifiers may not match other registered
   names in a case-insensitive manner unless the Designated Experts
   determine that there is a compelling reason to allow an exception.

3.1.  Registering Extension Identifiers

   WebAuthn extension identifiers registry are registered using the
   Specification Required policy (see Section 4.6 of [RFC8126]), which
   implies review and approval by a designated expert.

   The WebAuthn extension identifiers registry is located at
   https://www.iana.org/assignments/(fill-in-here-per-IANA)/ [9].
   Registration requests can be made by following the instructions
   located there, or by sending an e-mail to the "public-
   webauthn@w3.org" mailing list.

   Registration requests consist of at least the following information:

   o  *WebAuthn Extension Identifier*: An identifier meeting the
      requirements given above in Section 3.
   o  *Description*: A relatively short description of the extension.
   o  *Reference*: Reference to the specification of the extension.
   o  Notes: [optional]

   The expert(s) can define additional fields to be collected in the
   registry.

   Registrations MUST reference a freely available, stable
   specification, e.g., as described in Section 7 of [RFC2026].

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

Hodges, et al.           Expires April 20, 2020                 [Page 5]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

3.2.  Registration Request Processing

   As noted in Section 3.1, WebAuthn extension identifiers are
   registered using the Specification Required policy, implying review
   and approval by a designated expert.

   The expert(s) will clearly identify any issues which cause a
   registration to be refused.

   When a request is approved, the expert(s) will inform IANA, and the
   registration will be processed.  The IESG is the final arbiter of any
   objection.

3.3.  Initial WebAuthn Extension Identifier Registry Values

   The initial values for the WebAuthn Extension Identifier Registry are
   to be populated from the values listed in "WebAuthn Extension
   Identifier Registrations" [10] of [WebAuthn].

4.  IANA Considerations

4.1.  WebAuthn Attestation Statement Format Identifier and Extension
      Identifiers Registries

   This specification establishes two registries:

   o  the "WebAuthn Attestation Statement Format Identifier" registry;
      see Section 2.
   o  the "WebAuthn Extension Identifier" registry; see Section 3.

   For both registries, the expert(s) and IANA will interact as outlined
   below:

   IANA will direct any incoming requests regarding either of these
   registries to this document and, if defined, the processes
   established by the expert(s); typically, this will mean referring
   them to the registry Web page.

   Note that the expert(s) are allowed (as per Section 2.1) to define
   additional fields to be collected in the registry.

5.  Security Considerations

   See [WebAuthn] for relevant security considerations.

Hodges, et al.           Expires April 20, 2020                 [Page 6]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

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

7.  Document History

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

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

8.  References

8.1.  Normative References

   [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
              3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
              <https://www.rfc-editor.org/info/rfc2026>.

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

Hodges, et al.           Expires April 20, 2020                 [Page 7]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

   [WebAuthn]
              Balfanz, D., Czeskis, A., Hodges, J., Jones, J., 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, March 2019,
              <https://www.w3.org/TR/2019/REC-webauthn-1-20190304/>.

8.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/webauthn/#sctn-attstn-fmt-ids

   [6] https://www.iana.org/assignments/(fill-in-here-per-IANA)/

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

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

   [9] https://www.iana.org/assignments/(fill-in-here-per-IANA)/

   [10] https://www.w3.org/TR/webauthn/#sctn-extensions-reg

Authors' Addresses

   Jeff Hodges
   Google
   1600 Amphitheater Parkway
   Mountain View, California  94043
   US

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

Hodges, et al.           Expires April 20, 2020                 [Page 8]
Internet-DraftRegistries for Web Authentication (WebAuthn)      Oct 2019

   Giridhar Mandyam
   Qualcomm Technologies Inc.
   5775 Morehouse Drive
   San Diego, California  92121
   USA

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

   Michael B. Jones
   Microsoft

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

Hodges, et al.           Expires April 20, 2020                 [Page 9]