< draft-hodges-webauthn-registries-01.txt   draft-hodges-webauthn-registries-02.txt >
W3C WebAuthn Working Group J. Hodges W3C WebAuthn Working Group J. Hodges
Internet-Draft PayPal Internet-Draft Google
Intended status: Informational G. Mandyam Intended status: Informational G. Mandyam
Expires: August 31, 2018 Qualcomm Technologies Inc. Expires: September 12, 2019 Qualcomm Technologies Inc.
M. Jones M. Jones
Microsoft Microsoft
February 27, 2018 March 11, 2019
Registries for Web Authentication (WebAuthn) Registries for Web Authentication (WebAuthn)
draft-hodges-webauthn-registries-01 draft-hodges-webauthn-registries-02
Abstract Abstract
This specification defines IANA registries for W3C Web Authentication This specification defines IANA registries for W3C Web Authentication
attestation statement formats and extension identifiers. attestation statement format identifiers and extension identifiers.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 31, 2018. This Internet-Draft will expire on September 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. WebAuthn Attestation Statement Format Identifier Registry . . 2 2. WebAuthn Attestation Statement Format Identifier Registry . . 2
2.1. Initial WebAuthn Attestation Statement Format Identifier
Registry Values . . . . . . . . . . . . . . . . . . . . . 3
3. WebAuthn Extension Identifier Registry . . . . . . . . . . . 3 3. WebAuthn Extension Identifier Registry . . . . . . . . . . . 3
3.1. Initial WebAuthn Extension Identifier Registry Values . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4.1. WebAuthn Attestation Statement Format Identifier and 4.1. WebAuthn Attestation Statement Format Identifier and
Extension Identifiers Registries . . . . . . . . . . . . 4 Extension Identifiers Registries . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. Document History . . . . . . . . . . . . . . . . . . . . . . 5 7. Document History . . . . . . . . . . . . . . . . . . . . . . 6
8. Normative References . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
This specification establishes IANA registries for W3C Web This specification establishes IANA registries for W3C Web
Authentication [WebAuthn] attestation statement formats and extension Authentication [WebAuthn] attestation statement format identifiers
identifiers. The initial values for these registries are in the IANA and extension identifiers. The initial values for these registries
Considerations section of the [WebAuthn] specification. are in the IANA Considerations section of the [WebAuthn]
specification.
2. WebAuthn Attestation Statement Format Identifier Registry 2. WebAuthn Attestation Statement Format Identifier Registry
WebAuthn attestation statement format identifiers are strings whose WebAuthn attestation statement format identifiers are strings whose
semantic, syntactic, and string-matching criteria are specified in semantic, syntactic, and string-matching criteria are specified in
[WebAuthn], along with the concepts of attestation and attestation [WebAuthn] Section 8.1 "Attestation Statement Format Identifiers"
statement formats. [1], along with the concepts of attestation and attestation statement
formats.
WebAuthn attestation statement formats are registered on the advice WebAuthn attestation statement format identifiers are registered on
of a Designated Expert (appointed by the IESG or their delegate), the advice of a Designated Expert (appointed by the IESG or their
with a Specification Required (per [RFC5226]). delegate), with a Specification Required (per [RFC5226]).
The Expert(s) will establish procedures for requesting registrations, The Expert(s) will establish procedures for requesting registrations,
and make them available from the registry page. and make them available from the registry page.
Registration requests consist of at least the following information: Registration requests consist of at least the following information:
o WebAuthn Attestation Statement Format Identifier: This identifier o WebAuthn Attestation Statement Format Identifier: This identifier
MUST be a maximum of 32 octets in length and MUST consist only of MUST be a maximum of 32 octets in length and MUST consist only of
printable USASCII characters, excluding backslash and doublequote. printable USASCII characters, excluding backslash and doublequote.
This name is case sensitive. Names may not match other registered This name is case sensitive. Names may not match other registered
skipping to change at page 3, line 15 skipping to change at page 3, line 23
registry. Each attestation statement format identifier added to this registry. Each attestation statement format identifier added to this
registry MUST be unique amongst the set of registered attestation registry MUST be unique amongst the set of registered attestation
statement format identifiers. The Experts(s) MAY also designate statement format identifiers. The Experts(s) MAY also designate
attestation statement formats as proprietary if they lack complete attestation statement formats as proprietary if they lack complete
specifications, and will assign a prefix indicating as such to the specifications, and will assign a prefix indicating as such to the
identifier. identifier.
Registrations MUST reference a freely available specification, e.g., Registrations MUST reference a freely available specification, e.g.,
as described in [RFC2026] Section 7. as described in [RFC2026] Section 7.
Note that WebAuthn attestation statement formats can be registered by Note that WebAuthn attestation statement format identifiers can be
third parties, if the Expert(s) determine that an unregistered registered by third parties, if the Expert(s) determine that an
attestation statement format is widely deployed and not likely to be unregistered attestation statement format is widely deployed and not
registered in a timely manner. likely to be registered in a timely manner.
Decisions (or lack thereof) made by the Designated Expert can be Decisions (or lack thereof) made by the Designated Expert can be
first appealed to Application Area Directors (contactable using app- first appealed to Application Area Directors (contactable using app-
ads@tools.ietf.org email address or directly by looking up their ads@tools.ietf.org email address or directly by looking up their
email addresses on http://www.iesg.org/ website) and, if the email addresses on http://www.iesg.org/ website) and, if the
appellant is not satisfied with the response, to the full IESG (using appellant is not satisfied with the response, to the full IESG (using
the iesg@iesg.org mailing list). the iesg@iesg.org mailing list).
2.1. 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
Section 11.1 "WebAuthn Attestation Statement Format Identifier
Registrations" [2] of [WebAuthn].
3. WebAuthn Extension Identifier Registry 3. WebAuthn Extension Identifier Registry
WebAuthn extension identifiers are strings whose semantic, syntactic, WebAuthn extension identifiers are strings whose semantic, syntactic,
and string-matching criteria are specified in [WebAuthn]. and string-matching criteria are specified in [WebAuthn] Section 9.1
"Extension Identifiers" [3].
WebAuthn extension identifiers are registered on the advice of a WebAuthn extension identifiers are registered on the advice of a
Designated Expert (appointed by the IESG or their delegate), with a Designated Expert (appointed by the IESG or their delegate), with a
Specification Required (per [RFC5226]). Specification Required (per [RFC5226]).
The Expert(s) will establish procedures for requesting registrations, The Expert(s) will establish procedures for requesting registrations,
and make them available from the registry page. and make them available from the registry page.
Registration requests consist of at least the following information: Registration requests consist of at least the following information:
skipping to change at page 4, line 22 skipping to change at page 4, line 39
the Expert(s) determine that an unregistered extension is widely the Expert(s) determine that an unregistered extension is widely
deployed and not likely to be registered in a timely manner. deployed and not likely to be registered in a timely manner.
Decisions (or lack thereof) made by the Designated Expert can be Decisions (or lack thereof) made by the Designated Expert can be
first appealed to Application Area Directors (contactable using app- first appealed to Application Area Directors (contactable using app-
ads@tools.ietf.org email address or directly by looking up their ads@tools.ietf.org email address or directly by looking up their
email addresses on http://www.iesg.org/ website) and, if the email addresses on http://www.iesg.org/ website) and, if the
appellant is not satisfied with the response, to the full IESG (using appellant is not satisfied with the response, to the full IESG (using
the iesg@iesg.org mailing list). the iesg@iesg.org mailing list).
3.1. Initial WebAuthn Extension Identifier Registry Values
The initial values for the WebAuthn Extension Identifier Registry are
to be populated from the values listed in Section 11.2 "WebAuthn
Extension Identifier Registrations" [4] of [WebAuthn].
4. IANA Considerations 4. IANA Considerations
4.1. WebAuthn Attestation Statement Format Identifier and Extension 4.1. WebAuthn Attestation Statement Format Identifier and Extension
Identifiers Registries Identifiers Registries
This specification establishes two registries: This specification establishes two registries:
o the "WebAuthn Attestation Statement Format Identifier" registry; o the "WebAuthn Attestation Statement Format Identifier" registry;
see Section 2. see Section 2.
o the "WebAuthn Extension Identifier" registry; see Section 3. o the "WebAuthn Extension Identifier" registry; see Section 3.
skipping to change at page 5, line 10 skipping to change at page 5, line 33
Each published document will be at a URL agreed to by IANA and the Each published document will be at a URL agreed to by IANA and the
Expert(s) and IANA will set HTTP response headers on them as Expert(s) and IANA will set HTTP response headers on them as
(reasonably) requested by the Expert(s). (reasonably) requested by the Expert(s).
Additionally, the HTML generated by IANA will: Additionally, the HTML generated by IANA will:
o Take directions from the Expert(s) as to the content of the HTML o Take directions from the Expert(s) as to the content of the HTML
page's introductory text and markup. page's introductory text and markup.
o Include a stable HTML fragment identifier for each registered o Include a stable HTML fragment identifier for each registered
attestation statement format or extension identifier. attestation statement format identifier or extension identifier.
All registry data documents MUST include Simplified BSD License text All registry data documents MUST include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions as described in Section 4.e of the Trust Legal Provisions
(<http://trustee.ietf.org/license-info>). (<http://trustee.ietf.org/license-info>).
5. Security Considerations 5. Security Considerations
See [WebAuthn] for relevant security considerations. See [WebAuthn] for relevant security considerations.
6. Acknowledgements 6. Acknowledgements
Thanks to Mark Nottingham for valuable comments and suggestions. Thanks to Mark Nottingham for valuable comments and suggestions.
Thanks to Kathleen Moriarty and Benjamin Kaduk for their Area Thanks to Kathleen Moriarty and Benjamin Kaduk for their Area
Director sponsorship of this specification. Director sponsorship of this specification.
7. Document History 7. Document History
[[ to be removed by the RFC Editor before publication as an RFC ]] [[ to be removed by the RFC Editor before publication as an RFC ]]
-02
o Refresh now that the WebAuthn spec is at Recommendation (REC)
maturity level.
-01 -01
o Refresh now that the WebAuthn Committee Recommendation (CR) draft o Refresh now that the WebAuthn Committee Recommendation (CR) draft
is pending. is pending.
-00 -00
o Initial version. o Initial version.
8. Normative References 8. References
8.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<https://www.rfc-editor.org/info/rfc2026>. <https://www.rfc-editor.org/info/rfc2026>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226, IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<https://www.rfc-editor.org/info/rfc5226>. <https://www.rfc-editor.org/info/rfc5226>.
[WebAuthn] [WebAuthn]
Balfanz, D., Czeskis, A., Hodges, J., Jones, J., Jones, Balfanz, D., Czeskis, A., Hodges, J., Jones, J., Jones,
M., Kumar, A., Liao, A., Lindemann, R., and E. Lundberg, M., Kumar, A., Liao, A., Lindemann, R., and E. Lundberg,
"Web Authentication: An API for accessing Public Key "Web Authentication: An API for accessing Public Key
Credentials", Editors' Draft, World Wide Web Consortium Credentials", World Wide Web Consortium
(W3C) Recommendation-track, February 2018, (W3C) Recommendation, March 2019,
<https://w3c.github.io/webauthn/>. <https://www.w3.org/TR/2019/REC-webauthn-1-20190304/>.
8.2. URIs
[1] https://www.w3.org/TR/webauthn/#sctn-attstn-fmt-ids
[2] https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-att-fmt-
reg
[3] https://www.w3.org/TR/webauthn/#sctn-extension-id
[4] https://www.w3.org/TR/2019/REC-webauthn-1-20190304/#sctn-
extensions-reg
Authors' Addresses Authors' Addresses
Jeff Hodges Jeff Hodges
PayPal Google
2211 North First Street 1600 Amphitheater Parkway
San Jose, California 95131 Mountain View, California 94043
US US
Email: Jeff.Hodges@PayPal.com Email: jdhodges@google.com
URI: http://kingsmountain.com/people/Jeff.Hodges/ URI: http://kingsmountain.com/people/Jeff.Hodges/
Giridhar Mandyam Giridhar Mandyam
Qualcomm Technologies Inc. Qualcomm Technologies Inc.
5775 Morehouse Drive 5775 Morehouse Drive
San Diego, California 92121 San Diego, California 92121
USA USA
Phone: +1 858 651 7200 Phone: +1 858 651 7200
Email: mandyam@qti.qualcomm.com Email: mandyam@qti.qualcomm.com
 End of changes. 23 change blocks. 
32 lines changed or deleted 73 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/