idnits 2.17.1 draft-hodges-webauthn-registries-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([2], [3], [4], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 129: '... MUST be unique amongst the set of r...' RFC 2119 keyword, line 130: '... The Experts(s) MAY also designate at...' RFC 2119 keyword, line 135: '...t format identifiers MUST be a maximum...' RFC 2119 keyword, line 136: '...ts in length and MUST consist only of ...' RFC 2119 keyword, line 170: '... Registrations MUST reference a free...' (6 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Dec 12, 2019) is 1598 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 349 -- Looks like a reference, but probably isn't: '2' on line 352 -- Looks like a reference, but probably isn't: '3' on line 354 -- Looks like a reference, but probably isn't: '4' on line 357 -- Looks like a reference, but probably isn't: '5' on line 360 -- Looks like a reference, but probably isn't: '6' on line 362 -- Looks like a reference, but probably isn't: '7' on line 364 -- Looks like a reference, but probably isn't: '8' on line 366 -- Looks like a reference, but probably isn't: '9' on line 368 -- Looks like a reference, but probably isn't: '10' on line 370 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 W3C WebAuthn Working Group J. Hodges 3 Internet-Draft Google 4 Intended status: Informational G. Mandyam 5 Expires: June 14, 2020 Qualcomm Technologies Inc. 6 M. Jones 7 Microsoft 8 Dec 12, 2019 10 Registries for Web Authentication (WebAuthn) 11 draft-hodges-webauthn-registries-04 13 Abstract 15 This specification defines IANA registries for W3C Web Authentication 16 attestation statement format identifiers and extension identifiers. 18 Note to Readers 20 _RFC EDITOR: please remove this section before publication_ 22 This is a work-in-progress. 24 The issues list can be found at https://github.com/w3c/webauthn/ 25 issues?q=is%3Aopen+is%3Aissue+label%3Aspec%3Awebauthn-registries [1]. 27 The most recent _published_ draft revision is at 28 https://tools.ietf.org/html/draft-hodges-webauthn-registries [2]. 30 The editors' draft is at https://github.com/w3c/webauthn/blob/master/ 31 draft-hodges-webauthn-registries.txt [3] 33 Changes in the editors' draft, both proposed and incorporated, are 34 listed at https://github.com/w3c/webauthn/ 35 pulls?q=is%3Apr+label%3Aspec%3Awebauthn-registries [4] 37 Status of This Memo 39 This Internet-Draft is submitted in full conformance with the 40 provisions of BCP 78 and BCP 79. 42 Internet-Drafts are working documents of the Internet Engineering 43 Task Force (IETF). Note that other groups may also distribute 44 working documents as Internet-Drafts. The list of current Internet- 45 Drafts is at https://datatracker.ietf.org/drafts/current/. 47 Internet-Drafts are draft documents valid for a maximum of six months 48 and may be updated, replaced, or obsoleted by other documents at any 49 time. It is inappropriate to use Internet-Drafts as reference 50 material or to cite them other than as "work in progress." 52 This Internet-Draft will expire on June 14, 2020. 54 Copyright Notice 56 Copyright (c) 2019 IETF Trust and the persons identified as the 57 document authors. All rights reserved. 59 This document is subject to BCP 78 and the IETF Trust's Legal 60 Provisions Relating to IETF Documents 61 (https://trustee.ietf.org/license-info) in effect on the date of 62 publication of this document. Please review these documents 63 carefully, as they describe your rights and restrictions with respect 64 to this document. Code Components extracted from this document must 65 include Simplified BSD License text as described in Section 4.e of 66 the Trust Legal Provisions and are provided without warranty as 67 described in the Simplified BSD License. 69 Table of Contents 71 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 72 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 73 2.1. WebAuthn Attestation Statement Format Identifier Registry 3 74 2.1.1. Registering Attestation Statement Format Identifiers 4 75 2.1.2. Registration Request Processing . . . . . . . . . . . 4 76 2.1.3. Initial WebAuthn Attestation Statement Format 77 Identifier Registry Values . . . . . . . . . . . . . 5 78 2.2. WebAuthn Extension Identifier Registry . . . . . . . . . 5 79 2.2.1. Registering Extension Identifiers . . . . . . . . . . 5 80 2.2.2. Registration Request Processing . . . . . . . . . . . 6 81 2.2.3. Initial WebAuthn Extension Identifier Registry Values 6 82 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6 83 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 84 5. Document History . . . . . . . . . . . . . . . . . . . . . . 7 85 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 86 6.1. Normative References . . . . . . . . . . . . . . . . . . 7 87 6.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 8 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 90 1. Introduction 92 This specification establishes IANA registries for W3C Web 93 Authentication [WebAuthn] attestation statement format identifiers 94 and extension identifiers. The initial values for these registries 95 are in the IANA Considerations section of the [WebAuthn] 96 specification. 98 2. IANA Considerations 100 This specification establishes two registries: 102 o the "WebAuthn Attestation Statement Format Identifier" registry; 103 see Section 2.1. 104 o the "WebAuthn Extension Identifier" registry; see Section 2.2. 106 For both registries, the expert(s) and IANA will interact as outlined 107 below: 109 IANA will direct any incoming requests regarding either of these 110 registries to this document and, if defined, the processes 111 established by the expert(s); typically, this will mean referring 112 them to the registry Web page. 114 Note that the expert(s) are allowed (as per Section 2.1.1) to define 115 additional fields to be collected in the registry. 117 2.1. WebAuthn Attestation Statement Format Identifier Registry 119 WebAuthn attestation statement format identifiers are strings whose 120 semantic, syntactic, and string-matching criteria are specified in 121 [WebAuthn] "Attestation Statement Format Identifiers" [5], along with 122 the concepts of attestation and attestation statement formats. 124 Registered attestation statement format identifiers are those that 125 have been added to the registry by following the procedure in 126 Section 2.1.1. 128 Each attestation statement format identifier added to this registry 129 MUST be unique amongst the set of registered attestation statement 130 format identifiers. The Experts(s) MAY also designate attestation 131 statement formats as proprietary if they lack complete 132 specifications, and will assign a prefix indicating as such to the 133 identifier. 135 Registered attestation statement format identifiers MUST be a maximum 136 of 32 octets in length and MUST consist only of printable USASCII 137 characters, excluding backslash and doublequote, i.e., VCHAR as 138 defined in [RFC5234] but without %x22 and %x5c. Attestation 139 statement format identifiers are case sensitive. Attestation 140 statement format identifiers may not match other registered 141 identifiers in a case-insensitive manner unless the Designated 142 Experts determine that there is a compelling reason to allow an 143 exception. 145 2.1.1. Registering Attestation Statement Format Identifiers 147 WebAuthn attestation statement format identifiers are registered 148 using the Specification Required policy (see Section 4.6 of 149 [RFC8126]), which implies review and approval by a designated expert. 151 The WebAuthn attestation statement format identifiers registry is 152 located at https://www.iana.org/assignments/(fill-in-here-per-IANA)/ 153 [6]. Registration requests can be made by following the instructions 154 located there, or by sending an e-mail to the "public- 155 webauthn@w3.org" mailing list. 157 Registration requests consist of at least the following information: 159 o *WebAuthn Attestation Statement Format Identifier*: An identifier 160 meeting the requirements given above in Section 2.1. 161 o *Description*: A relatively short description of the attestation 162 format. 163 o *Reference*: Reference to the specification of the attestation 164 statement format. 165 o Notes: [optional] 167 The expert(s) can define additional fields to be collected in the 168 registry. 170 Registrations MUST reference a freely available, stable 171 specification, e.g., as described in Section 7 of [RFC2026]. This 172 specification MUST include security and privacy considerations 173 relevant to the attestation statement format. 175 Note that WebAuthn attestation statement format identifiers can be 176 registered by third parties (including the expert(s) themselves), if 177 the expert(s) determine that an unregistered attestation statement 178 format is widely deployed and not likely to be registered in a timely 179 manner otherwise. Such registrations still are subject to the 180 requirements defined, including the need to reference a 181 specification. 183 2.1.2. Registration Request Processing 185 As noted in Section 2.1.1, WebAuthn attestation statement format 186 identifiers are registered using the Specification Required policy, 187 implying review and approval by a designated expert. 189 The expert(s) will clearly identify any issues which cause a 190 registration to be refused. 192 When a request is approved, the expert(s) will inform IANA, and the 193 registration will be processed. The IESG is the arbiter of any 194 objection. 196 2.1.3. Initial WebAuthn Attestation Statement Format Identifier 197 Registry Values 199 The initial values for the WebAuthn Attestation Statement Format 200 Identifier Registry are to be populated from the values listed in 201 "WebAuthn Attestation Statement Format Identifier Registrations" [7] 202 of [WebAuthn]. 204 2.2. WebAuthn Extension Identifier Registry 206 WebAuthn extension identifiers are strings whose semantic, syntactic, 207 and string-matching criteria are specified in [WebAuthn] "Extension 208 Identifiers" [8]. 210 Registered extension identifiers are those that have been added to 211 the registry by following the procedure in Section 2.2.1. 213 Each extension identifier added to this registry MUST be unique 214 amongst the set of registered extension identifiers. 216 Registered extension identifiers MUST be a maximum of 32 octets in 217 length and MUST consist only of printable USASCII characters, 218 excluding backslash and doublequote, i.e., VCHAR as defined in 219 [RFC5234] but without %x22 and %x5c. Extension identifiers are case 220 sensitive. Extension identifiers may not match other registered 221 names in a case-insensitive manner unless the Designated Experts 222 determine that there is a compelling reason to allow an exception. 224 2.2.1. Registering Extension Identifiers 226 WebAuthn extension identifiers registry are registered using the 227 Specification Required policy (see Section 4.6 of [RFC8126]), which 228 implies review and approval by a designated expert. 230 The WebAuthn extension identifiers registry is located at 231 https://www.iana.org/assignments/(fill-in-here-per-IANA)/ [9]. 232 Registration requests can be made by following the instructions 233 located there, or by sending an e-mail to the "public- 234 webauthn@w3.org" mailing list. 236 Registration requests consist of at least the following information: 238 o *WebAuthn Extension Identifier*: An identifier meeting the 239 requirements given above in Section 2.2. 241 o *Description*: A relatively short description of the extension. 242 o *Reference*: Reference to the specification of the extension. 243 o Notes: [optional] 245 The expert(s) can define additional fields to be collected in the 246 registry. 248 Registrations MUST reference a freely available, stable 249 specification, e.g., as described in Section 7 of [RFC2026]. This 250 specification MUST include security and privacy considerations 251 relevant to the extension. 253 Note that WebAuthn extensions can be registered by third parties 254 (including the expert(s) themselves), if the expert(s) determine that 255 an unregistered extension is widely deployed and not likely to be 256 registered in a timely manner otherwise. Such registrations still 257 are subject to the requirements defined, including the need to 258 reference a specification. 260 2.2.2. Registration Request Processing 262 As noted in Section 2.2.1, WebAuthn extension identifiers are 263 registered using the Specification Required policy, implying review 264 and approval by a designated expert. 266 The expert(s) will clearly identify any issues which cause a 267 registration to be refused. 269 When a request is approved, the expert(s) will inform IANA, and the 270 registration will be processed. The IESG is the arbiter of any 271 objection. 273 2.2.3. Initial WebAuthn Extension Identifier Registry Values 275 The initial values for the WebAuthn Extension Identifier Registry are 276 to be populated from the values listed in "WebAuthn Extension 277 Identifier Registrations" [10] of [WebAuthn]. 279 3. Security Considerations 281 See [WebAuthn] for relevant security considerations. 283 4. Acknowledgements 285 Thanks to Mark Nottingham for valuable comments and suggestions. 286 Thanks to Kathleen Moriarty and Benjamin Kaduk for their Area 287 Director sponsorship of this specification. 289 5. Document History 291 [[ to be removed by the RFC Editor before publication as an RFC ]] 293 -04 295 o Update per Benjamin Kaduk's further AD review: Remove 'final' wrt 296 IESG arbitrating objections; Add explicit requirement for 297 extension or attestation specs to include security and privacy 298 considerations. 299 o Update per IANA review: Move "IANA considerations section up in 300 doc to encompass (former) sections 2 and 3. 302 -03 304 o Update per Benjamin Kaduk's AD review. Align with RFC 8288, 305 rather than draft-nottingham-rfc5988bis. 307 -02 309 o Refresh now that the WebAuthn spec is at Recommendation (REC) 310 maturity level. 312 -01 314 o Refresh now that the WebAuthn Committee Recommendation (CR) draft 315 is pending. 317 -00 319 o Initial version, based on draft-nottingham-rfc5988bis. 321 6. References 323 6.1. Normative References 325 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 326 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 327 . 329 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 330 Specifications: ABNF", STD 68, RFC 5234, 331 DOI 10.17487/RFC5234, January 2008, 332 . 334 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 335 Writing an IANA Considerations Section in RFCs", BCP 26, 336 RFC 8126, DOI 10.17487/RFC8126, June 2017, 337 . 339 [WebAuthn] 340 Balfanz, D., Czeskis, A., Hodges, J., Jones, J., Jones, 341 M., Kumar, A., Liao, A., Lindemann, R., and E. Lundberg, 342 "Web Authentication: An API for accessing Public Key 343 Credentials", World Wide Web Consortium 344 (W3C) Recommendation, March 2019, 345 . 347 6.2. URIs 349 [1] https://github.com/w3c/webauthn/ 350 issues?q=is%3Aopen+is%3Aissue+label%3Aspec%3Awebauthn-registries 352 [2] https://tools.ietf.org/html/draft-hodges-webauthn-registries 354 [3] https://github.com/w3c/webauthn/blob/master/draft-hodges- 355 webauthn-registries.txt 357 [4] https://github.com/w3c/webauthn/ 358 pulls?q=is%3Apr+label%3Aspec%3Awebauthn-registries 360 [5] https://www.w3.org/TR/webauthn/#sctn-attstn-fmt-ids 362 [6] https://www.iana.org/assignments/(fill-in-here-per-IANA)/ 364 [7] https://www.w3.org/TR/webauthn/#sctn-att-fmt-reg 366 [8] https://www.w3.org/TR/webauthn/#sctn-extension-id 368 [9] https://www.iana.org/assignments/(fill-in-here-per-IANA)/ 370 [10] https://www.w3.org/TR/webauthn/#sctn-extensions-reg 372 Authors' Addresses 374 Jeff Hodges 375 Google 376 1600 Amphitheater Parkway 377 Mountain View, California 94043 378 US 380 Email: jdhodges@google.com 381 URI: http://kingsmountain.com/people/Jeff.Hodges/ 382 Giridhar Mandyam 383 Qualcomm Technologies Inc. 384 5775 Morehouse Drive 385 San Diego, California 92121 386 USA 388 Phone: +1 858 651 7200 389 Email: mandyam@qti.qualcomm.com 391 Michael B. Jones 392 Microsoft 394 Email: mbj@microsoft.com 395 URI: http://self-issued.info/