idnits 2.17.1 draft-jones-webauthn-cose-algorithms-00.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 23, 2018) is 2197 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC7049' is defined on line 186, but no explicit reference was found in the text == Unused Reference: 'RFC7515' is defined on line 190, but no explicit reference was found in the text ** Obsolete normative reference: RFC 7049 (Obsoleted by RFC 8949) ** Obsolete normative reference: RFC 8152 (Obsoleted by RFC 9052, RFC 9053) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 WebAuthn Working Group M. Jones 3 Internet-Draft Microsoft 4 Intended status: Informational March 23, 2018 5 Expires: September 24, 2018 7 COSE Algorithms for Web Authentication (WebAuthn) 8 draft-jones-webauthn-cose-algorithms-00 10 Abstract 12 The W3C Web Authentication (WebAuthn) specification uses COSE 13 algorithm identifiers. This specification registers algorithms in 14 the IANA "COSE Algorithms" registry that are used by WebAuthn that 15 are not already registered. Also, they are registered in the IANA 16 "JSON Web Signature and Encryption Algorithms" registry, when not 17 already registered there. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on September 24, 2018. 36 Copyright Notice 38 Copyright (c) 2018 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirements Notation and Conventions . . . . . . . . . . 2 55 2. RSASSA-PKCS1-v1_5 Signature Algorithm . . . . . . . . . . . . 2 56 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 57 3.1. COSE Algorithms Registrations . . . . . . . . . . . . . . 3 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 59 4.1. RSA Key Size Security Considerations . . . . . . . . . . 4 60 4.2. RSASSA-PKCS1-v1_5 with SHA-2 Security Considerations . . 4 61 4.3. RSASSA-PKCS1-v1_5 with SHA-1 Security Considerations . . 4 62 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 5.2. Informative References . . . . . . . . . . . . . . . . . 5 65 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5 66 Document History . . . . . . . . . . . . . . . . . . . . . . . . 6 67 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 69 1. Introduction 71 This specification defines how to use several algorithms with COSE 72 [RFC8152] that are used by the W3C Web Authentication (WebAuthn) 73 [WebAuthn] specification. These algorithms are registered in the 74 IANA "COSE Algorithms" registry [IANA.COSE.Algorithms] and also in 75 the IANA "JSON Web Signature and Encryption Algorithms" registry 76 [IANA.JOSE.Algorithms], when not already registered there. 78 1.1. Requirements Notation and Conventions 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 82 "OPTIONAL" in this document are to be interpreted as described in BCP 83 14 [RFC2119] [RFC8174] when, and only when, they appear in all 84 capitals, as shown here. 86 2. RSASSA-PKCS1-v1_5 Signature Algorithm 88 The RSASSA-PKCS1-v1_5 signature algorithm is defined in [RFC8017]. 89 The RSASSA-PKCS1-v1_5 signature algorithm is parameterized with a 90 hash function (h). 92 A key of size 2048 bits or larger MUST be used with these algorithms. 93 Implementations need to check that the key type is 'RSA' when 94 creating or verifying a signature. 96 The RSASSA-PKCS1-v1_5 algorithms specified in this document are in 97 the following table. 99 +-------+-------------------------+---------+-----------------------+ 100 | Name | Value | Hash | Description | 101 +-------+-------------------------+---------+-----------------------+ 102 | RS256 | TBD (requested | SHA-256 | RSASSA-PKCS1-v1_5 w/ | 103 | | assignment -257) | | SHA-256 | 104 | RS384 | TBD (requested | SHA-384 | RSASSA-PKCS1-v1_5 w/ | 105 | | assignment -258) | | SHA-384 | 106 | RS512 | TBD (requested | SHA-512 | RSASSA-PKCS1-v1_5 w/ | 107 | | assignment -259) | | SHA-512 | 108 | RS1 | TBD (requested | SHA-1 | RSASSA-PKCS1-v1_5 w/ | 109 | | assignment -262) | | SHA-1 | 110 +-------+-------------------------+---------+-----------------------+ 112 Table 1: RSASSA-PKCS1-v1_5 Algorithm Values 114 3. IANA Considerations 116 3.1. COSE Algorithms Registrations 118 This section registers the following values in the IANA "COSE 119 Algorithms" registry [IANA.COSE.Algorithms]. 121 o Name: RS256 122 o Value: TBD (requested assignment -257) 123 o Description: RSASSA-PKCS1-v1_5 w/ SHA-256 124 o Reference: Section 2 of this document 125 o Recommended: No 127 o Name: RS384 128 o Value: TBD (requested assignment -258) 129 o Description: RSASSA-PKCS1-v1_5 w/ SHA-384 130 o Reference: Section 2 of this document 131 o Recommended: No 133 o Name: RS512 134 o Value: TBD (requested assignment -259) 135 o Description: RSASSA-PKCS1-v1_5 w/ SHA-512 136 o Reference: Section 2 of this document 137 o Recommended: No 139 o Name: RS1 140 o Value: TBD (requested assignment -262) 141 o Description: RSASSA-PKCS1-v1_5 w/ SHA-1 142 o Reference: Section 2 of this document 143 o Recommended: No 145 4. Security Considerations 147 4.1. RSA Key Size Security Considerations 149 The security considerations on key sizes for RSA algorithms from 150 Section 6.1 of [RFC8230] also apply to the RSA algorithms in this 151 specification. 153 4.2. RSASSA-PKCS1-v1_5 with SHA-2 Security Considerations 155 The security considerations on the use of RSASSA-PKCS1-v1_5 with 156 SHA-2 hash functions from Section 8.3 of [RFC7518] also apply to 157 their use in this specification. For that reason, these algorithms 158 are registered as being "Not Recommended". 160 4.3. RSASSA-PKCS1-v1_5 with SHA-1 Security Considerations 162 The security considerations on the use of the SHA-1 hash function 163 from [RFC6194] apply in this specification. For that reason, the 164 "RS1" algorithm is registered as "Not Recommended". It MUST NOT be 165 used by COSE implementations. 167 A COSE algorithm identifier for this algorithm is nonetheless being 168 registered because deployed TPMs continue to use it, and therefore 169 WebAuthn implementations need a COSE algorithm identifier for "RS1" 170 when TPM attestations using this algorithm are being represented. 172 5. References 174 5.1. Normative References 176 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 177 Requirement Levels", BCP 14, RFC 2119, 178 DOI 10.17487/RFC2119, March 1997, 179 . 181 [RFC6194] Polk, T., Chen, L., Turner, S., and P. Hoffman, "Security 182 Considerations for the SHA-0 and SHA-1 Message-Digest 183 Algorithms", RFC 6194, DOI 10.17487/RFC6194, March 2011, 184 . 186 [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object 187 Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, 188 October 2013, . 190 [RFC7515] Jones, M., Bradley, J., and N. Sakimura, "JSON Web 191 Signature (JWS)", RFC 7515, DOI 10.17487/RFC7515, May 192 2015, . 194 [RFC7518] Jones, M., "JSON Web Algorithms (JWA)", RFC 7518, 195 DOI 10.17487/RFC7518, May 2015, 196 . 198 [RFC8017] Moriarty, K., Ed., Kaliski, B., Jonsson, J., and A. Rusch, 199 "PKCS #1: RSA Cryptography Specifications Version 2.2", 200 RFC 8017, DOI 10.17487/RFC8017, November 2016, 201 . 203 [RFC8152] Schaad, J., "CBOR Object Signing and Encryption (COSE)", 204 RFC 8152, DOI 10.17487/RFC8152, July 2017, 205 . 207 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 208 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 209 May 2017, . 211 [RFC8230] Jones, M., "Using RSA Algorithms with CBOR Object Signing 212 and Encryption (COSE) Messages", RFC 8230, 213 DOI 10.17487/RFC8230, September 2017, 214 . 216 5.2. Informative References 218 [IANA.COSE.Algorithms] 219 IANA, "COSE Algorithms", 220 . 223 [IANA.JOSE.Algorithms] 224 IANA, "JSON Web Signature and Encryption Algorithms", 225 . 228 [WebAuthn] 229 Balfanz, D., Czeskis, A., Hodges, J., Jones, J., Jones, 230 M., Kumar, A., Liao, A., Lindemann, R., and E. Lundberg, 231 "Web Authentication: An API for accessing Public Key 232 Credentials", Candidate Recommendation, World Wide Web 233 Consortium (W3C) Recommendation-track, March 2018, 234 . 236 Acknowledgements 238 TBD 240 Document History 242 [[ to be removed by the RFC Editor before publication as an RFC ]] 244 -00 246 o Initial version. 248 Author's Address 250 Michael B. Jones 251 Microsoft 253 Email: mbj@microsoft.com 254 URI: http://self-issued.info/