--- 1/draft-ietf-cose-webauthn-algorithms-06.txt 2020-06-03 10:13:36.898070036 -0700 +++ 2/draft-ietf-cose-webauthn-algorithms-07.txt 2020-06-03 10:13:36.926070750 -0700 @@ -1,18 +1,18 @@ COSE Working Group M. Jones Internet-Draft Microsoft -Intended status: Standards Track May 13, 2020 -Expires: November 14, 2020 +Intended status: Standards Track June 3, 2020 +Expires: December 5, 2020 COSE and JOSE Registrations for WebAuthn Algorithms - draft-ietf-cose-webauthn-algorithms-06 + draft-ietf-cose-webauthn-algorithms-07 Abstract The W3C Web Authentication (WebAuthn) specification and the FIDO Alliance Client to Authenticator Protocol (CTAP) specification use CBOR Object Signing and Encryption (COSE) algorithm identifiers. This specification registers the following algorithms in the IANA "COSE Algorithms" registry, which are used by WebAuthn and CTAP implementations: RSASSA-PKCS1-v1_5 using SHA-256, SHA-384, SHA-512, and SHA-1, and ECDSA using the secp256k1 curve and SHA-256. It @@ -31,21 +31,21 @@ 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 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 November 14, 2020. + This Internet-Draft will expire on December 5, 2020. Copyright Notice Copyright (c) 2020 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 @@ -318,34 +318,34 @@ o Name: RS1 o Value: TBD (temporary assignment -65535 already in place) o Description: RSASSA-PKCS1-v1_5 using SHA-1 o Reference: Section 2 of this document o Recommended: Deprecated o Name: ES256K o Value: TBD (requested assignment -47) o Description: ECDSA using secp256k1 curve and SHA-256 o Reference: Section 3.2 of this document - o Recommended: Yes + o Recommended: No 4.2. COSE Elliptic Curves Registrations This section registers the following value in the IANA "COSE Elliptic Curves" registry [IANA.COSE.Curves]. o Name: secp256k1 o Value: TBD (requested assignment 8) o Key Type: EC2 o Description: SECG secp256k1 curve o Change Controller: IESG o Reference: Section 3.1 of [[ this specification ]] - o Recommended: Yes + o Recommended: No 4.3. JOSE Algorithms Registrations This section registers the following value in the IANA "JSON Web Signature and Encryption Algorithms" registry [IANA.JOSE.Algorithms]. o Algorithm Name: ES256K o Algorithm Description: ECDSA using secp256k1 curve and SHA-256 o Algorithm Usage Locations: alg o JOSE Implementation Requirements: Optional @@ -368,23 +368,23 @@ 5.1. RSA Key Size Security Considerations The security considerations on key sizes for RSA algorithms from Section 6.1 of [RFC8230] also apply to the RSA algorithms in this specification. 5.2. RSASSA-PKCS1-v1_5 with SHA-2 Security Considerations The security considerations on the use of RSASSA-PKCS1-v1_5 with - SHA-2 hash functions from Section 8.3 of [RFC7518] also apply to - their use in this specification. For that reason, these algorithms - are registered as being "Not Recommended". + SHA-2 hash functions (SHA-256, SHA-384, and SHA-512) from Section 8.3 + of [RFC7518] also apply to their use in this specification. For that + reason, these algorithms are registered as being "Not Recommended". 5.3. RSASSA-PKCS1-v1_5 with SHA-1 Security Considerations The security considerations on the use of the SHA-1 hash function from [RFC6194] apply in this specification. For that reason, the "RS1" algorithm is registered as "Deprecated". Likewise, the exponent restrictions described in Section 8.3 of [RFC7518] also apply. A COSE algorithm identifier for this algorithm is nonetheless being @@ -511,32 +511,41 @@ [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 - Level 1", World Wide Web Consortium (W3C) Recommendation, March 2019, . Acknowledgements - Thanks to Stephen Farrell, John Fontana, Jeff Hodges, Kevin Jacobs, - J.C. Jones, Benjamin Kaduk, Murray Kucherawy, Neil Madden, John - Mattsson, Tony Nadalin, Matt Palmer, Jim Schaad, Goeran Selander, - Wendy Seltzer, Sean Turner, and Samuel Weiler for their roles in - registering these algorithm identifiers. + Thanks to Linda Dunbar, Stephen Farrell, John Fontana, Jeff Hodges, + Kevin Jacobs, J.C. Jones, Benjamin Kaduk, Murray Kucherawy, Neil + Madden, John Mattsson, Matthew Miller, Tony Nadalin, Matt Palmer, + Eric Rescorla, Rich Salz, Jim Schaad, Goeran Selander, Wendy Seltzer, + Sean Turner, and Samuel Weiler for their roles in registering these + algorithm identifiers. Document History [[ to be removed by the RFC Editor before publication as an RFC ]] - -06 + -07 + o Addressed editorial SecDir review comment by Linda Dunbar about + SHA-2 algorithms. + + o Addressed IETF last call comments by Jim Schaad, Rich Salz, and + Eric Rescorla, now registering secp256k1 and ES256K as + "Recommended: No" for COSE. + + -06 o Addressed Area Directory review comment by Murray Kucherawy (which requested an editorial correction). o Changed requested assignment for ES256K from -46 to -47, due to an assignment conflict. -05 o Removed unused reference to RFC 7049.