idnits 2.17.1 draft-ietf-cose-webauthn-algorithms-08.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 (June 11, 2020) is 1408 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'DSS' ** Downref: Normative reference to an Informational RFC: RFC 6194 ** Downref: Normative reference to an Informational RFC: RFC 8017 ** Obsolete normative reference: RFC 8152 (Obsoleted by RFC 9052, RFC 9053) -- Possible downref: Non-RFC (?) normative reference: ref. 'SEC1' -- Possible downref: Non-RFC (?) normative reference: ref. 'SEC2' Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 COSE Working Group M. Jones 3 Internet-Draft Microsoft 4 Intended status: Standards Track June 11, 2020 5 Expires: December 13, 2020 7 COSE and JOSE Registrations for WebAuthn Algorithms 8 draft-ietf-cose-webauthn-algorithms-08 10 Abstract 12 The W3C Web Authentication (WebAuthn) specification and the FIDO 13 Alliance Client to Authenticator Protocol (CTAP) specification use 14 CBOR Object Signing and Encryption (COSE) algorithm identifiers. 15 This specification registers the following algorithms in the IANA 16 "COSE Algorithms" registry, which are used by WebAuthn and CTAP 17 implementations: RSASSA-PKCS1-v1_5 using SHA-256, SHA-384, SHA-512, 18 and SHA-1, and ECDSA using the secp256k1 curve and SHA-256. It 19 registers the secp256k1 elliptic curve in the IANA "COSE Elliptic 20 Curves" registry. Also, for use with JSON Object Signing and 21 Encryption (JOSE), it registers the algorithm ECDSA using the 22 secp256k1 curve and SHA-256 in the IANA "JSON Web Signature and 23 Encryption Algorithms" registry and the secp256k1 elliptic curve in 24 the IANA "JSON Web Key Elliptic Curve" registry. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on December 13, 2020. 43 Copyright Notice 45 Copyright (c) 2020 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. Requirements Notation and Conventions . . . . . . . . . . 3 62 2. RSASSA-PKCS1-v1_5 Signature Algorithm . . . . . . . . . . . . 3 63 3. Using secp256k1 with JOSE and COSE . . . . . . . . . . . . . 4 64 3.1. JOSE and COSE secp256k1 Curve Key Representations . . . . 5 65 3.2. ECDSA Signature with secp256k1 Curve . . . . . . . . . . 5 66 3.3. Other Uses of the secp256k1 Elliptic Curve . . . . . . . 7 67 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 68 4.1. COSE Algorithms Registrations . . . . . . . . . . . . . . 7 69 4.2. COSE Elliptic Curves Registrations . . . . . . . . . . . 8 70 4.3. JOSE Algorithms Registrations . . . . . . . . . . . . . . 8 71 4.4. JSON Web Key Elliptic Curves Registrations . . . . . . . 9 72 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 73 5.1. RSA Key Size Security Considerations . . . . . . . . . . 9 74 5.2. RSASSA-PKCS1-v1_5 with SHA-2 Security Considerations . . 9 75 5.3. RSASSA-PKCS1-v1_5 with SHA-1 Security Considerations . . 9 76 5.4. secp256k1 Security Considerations . . . . . . . . . . . . 9 77 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 78 6.1. Normative References . . . . . . . . . . . . . . . . . . 10 79 6.2. Informative References . . . . . . . . . . . . . . . . . 11 80 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 12 81 Document History . . . . . . . . . . . . . . . . . . . . . . . . 12 82 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14 84 1. Introduction 86 This specification defines how to use several algorithms with CBOR 87 Object Signing and Encryption (COSE) [RFC8152] that are used by 88 implementations of the W3C Web Authentication (WebAuthn) [WebAuthn] 89 and FIDO Alliance FIDO2 Client to Authenticator Protocol (CTAP) 90 [CTAP] specifications. This specification registers these algorithms 91 in the IANA "COSE Algorithms" registry [IANA.COSE.Algorithms] and 92 registers an elliptic curve in the IANA "COSE Elliptic Curves" 93 registry [IANA.COSE.Curves]. This specification also registers a 94 corresponding algorithm for use with JSON Object Signing and 95 Encryption (JOSE) [RFC7515] in the IANA "JSON Web Signature and 96 Encryption Algorithms" registry [IANA.JOSE.Algorithms] and registers 97 an elliptic curve in the IANA "JSON Web Key Elliptic Curve" registry 98 [IANA.JOSE.Curves]. 100 1.1. Requirements Notation and Conventions 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 104 "OPTIONAL" in this document are to be interpreted as described in BCP 105 14 [RFC2119] [RFC8174] when, and only when, they appear in all 106 capitals, as shown here. 108 2. RSASSA-PKCS1-v1_5 Signature Algorithm 110 The RSASSA-PKCS1-v1_5 signature algorithm is defined in [RFC8017]. 111 The RSASSA-PKCS1-v1_5 signature algorithm is parameterized with a 112 hash function (h). 114 A key of size 2048 bits or larger MUST be used with these algorithms. 115 Implementations need to check that the key type is 'RSA' when 116 creating or verifying a signature. 118 The RSASSA-PKCS1-v1_5 algorithms specified in this document are in 119 the following table. 121 +-------+---------------+---------+-------------------+-------------+ 122 | Name | Value | Hash | Description | Recommended | 123 +-------+---------------+---------+-------------------+-------------+ 124 | RS256 | TBD | SHA-256 | RSASSA-PKCS1-v1_5 | No | 125 | | (temporary | | using SHA-256 | | 126 | | assignment | | | | 127 | | -257 already | | | | 128 | | in place) | | | | 129 | RS384 | TBD | SHA-384 | RSASSA-PKCS1-v1_5 | No | 130 | | (temporary | | using SHA-384 | | 131 | | assignment | | | | 132 | | -258 already | | | | 133 | | in place) | | | | 134 | RS512 | TBD | SHA-512 | RSASSA-PKCS1-v1_5 | No | 135 | | (temporary | | using SHA-512 | | 136 | | assignment | | | | 137 | | -259 already | | | | 138 | | in place) | | | | 139 | RS1 | TBD | SHA-1 | RSASSA-PKCS1-v1_5 | Deprecated | 140 | | (temporary | | using SHA-1 | | 141 | | assignment | | | | 142 | | -65535 | | | | 143 | | already in | | | | 144 | | place) | | | | 145 +-------+---------------+---------+-------------------+-------------+ 147 Table 1: RSASSA-PKCS1-v1_5 Algorithm Values 149 Security considerations for use of the first three algorithms are in 150 Section 5.2. Security considerations for use of the last algorithm 151 are in Section 5.3. 153 Note that these algorithms are already present in the IANA "JSON Web 154 Signature and Encryption Algorithms" registry [IANA.JOSE.Algorithms], 155 and so these registrations are only for the IANA "COSE Algorithms" 156 registry [IANA.COSE.Algorithms]. 158 3. Using secp256k1 with JOSE and COSE 160 This section defines algorithm encodings and representations enabling 161 the Standards for Efficient Cryptography Group (SECG) elliptic curve 162 secp256k1 [SEC2] to be used for JOSE [RFC7515] and COSE [RFC8152] 163 messages. 165 3.1. JOSE and COSE secp256k1 Curve Key Representations 167 The Standards for Efficient Cryptography Group (SECG) elliptic curve 168 secp256k1 [SEC2] is represented in a JSON Web Key (JWK) [RFC7517] 169 using these values: 171 o "kty": "EC" 172 o "crv": "secp256k1" 174 plus the values needed to represent the curve point, as defined in 175 Section 6.2.1 of [RFC7518]. As a compressed point encoding 176 representation is not defined for JWK elliptic curve points, the 177 uncompressed point encoding defined there MUST be used. The "x" and 178 "y" values represented MUST both be exactly 256 bits, with any 179 leading zeros preserved. Other optional values such as "alg" MAY 180 also be present. 182 It is represented in a COSE_Key [RFC8152] using these values: 184 o "kty" (1): "EC2" (2) 185 o "crv" (-1): "secp256k1" (TBD - requested assignment 8) 187 plus the values needed to represent the curve point, as defined in 188 Section 13.1.1 of [RFC8152]. Either the uncompressed or compressed 189 point encoding representations defined there can be used. The "x" 190 value represented MUST be exactly 256 bits, with any leading zeros 191 preserved. If the uncompressed representation is used, the "y" value 192 represented MUST likewise be exactly 256 bits, with any leading zeros 193 preserved; if the compressed representation is used, the "y" value is 194 a boolean value, as specified in Section 13.1.1 of [RFC8152]. Other 195 optional values such as "alg" (3) MAY also be present. 197 3.2. ECDSA Signature with secp256k1 Curve 199 The ECDSA signature algorithm is defined in [DSS]. This 200 specification defines the "ES256K" algorithm identifier, which is 201 used to specify the use of ECDSA with the secp256k1 curve and the 202 SHA-256 [DSS] cryptographic hash function. Implementations need to 203 check that the key type is "EC" for JOSE or "EC2" (2) for COSE and 204 that the curve of the key is secp256k1 when creating or verifying a 205 signature. 207 The ECDSA secp256k1 SHA-256 digital signature is generated as 208 follows: 210 1. Generate a digital signature of the JWS Signing Input or the COSE 211 Sig_structure using ECDSA secp256k1 SHA-256 with the desired 212 private key. The output will be the pair (R, S), where R and S 213 are 256-bit unsigned integers. 215 2. Turn R and S into octet sequences in big-endian order, with each 216 array being be 32 octets long. The octet sequence 217 representations MUST NOT be shortened to omit any leading zero 218 octets contained in the values. 220 3. Concatenate the two octet sequences in the order R and then S. 221 (Note that many ECDSA implementations will directly produce this 222 concatenation as their output.) 224 4. The resulting 64-octet sequence is the JWS Signature or COSE 225 signature value. 227 Implementations SHOULD use a deterministic algorithm to generate the 228 ECDSA nonce, k, such as [RFC6979]. However, in situations where 229 devices are vulnerable to physical attacks, deterministic ECDSA has 230 been shown to be susceptible to fault injection attacks [Kudelski17] 231 [EuroSP18]. Where this is a possibility, implementations SHOULD 232 implement appropriate countermeasures. Where there are specific 233 certification requirements (such as FIPS approval), implementors 234 should check whether deterministic ECDSA is an approved nonce 235 generation method. 237 The ECDSA secp256k1 SHA-256 algorithm specified in this document uses 238 these identifiers: 240 +----------+-------------------+----------------------+-------------+ 241 | JOSE Alg | COSE Alg Value | Description | Recommended | 242 | Name | | | | 243 +----------+-------------------+----------------------+-------------+ 244 | ES256K | TBD (requested | ECDSA using | No | 245 | | assignment -47) | secp256k1 curve and | | 246 | | | SHA-256 | | 247 +----------+-------------------+----------------------+-------------+ 249 Table 2: ECDSA Algorithm Values 251 When using a JWK or COSE_Key for this algorithm, the following checks 252 are made: 254 o The "kty" field MUST be present and it MUST be "EC" for JOSE or 255 "EC2" for COSE. 257 o The "crv" field MUST be present and it MUST represent the 258 "secp256k1" elliptic curve. 260 o If the "alg" field is present, it MUST represent the "ES256K" 261 algorithm. 263 o If the "key_ops" field is present, it MUST include "sign" when 264 creating an ECDSA signature. 266 o If the "key_ops" field is present, it MUST include "verify" when 267 verifying an ECDSA signature. 269 o If the JWK _use_ field is present, its value MUST be "sig". 271 3.3. Other Uses of the secp256k1 Elliptic Curve 273 This specification defines how to use the secp256k1 curve for ECDSA 274 signatures for both JOSE and COSE implementations. While in theory, 275 the curve could also be used for ECDH-ES key agreement, it is beyond 276 the scope of this specification to state whether this is or is not 277 advisable. Thus, whether to recommend its use with ECDH-ES is left 278 for experts to decide in future specifications. 280 When used for ECDSA, the secp256k1 curve MUST be used only with the 281 "ES256K" algorithm identifier and not any others, including not with 282 the COSE "ES256" identifier. Note that the "ES256K" algorithm 283 identifier needed to be introduced for JOSE to sign with the 284 secp256k1 curve because the JOSE "ES256" algorithm is defined to be 285 used only with the P-256 curve. The COSE treatment of how to sign 286 with secp256k1 is intentionally parallel to that for JOSE, where the 287 secp256k1 curve MUST be used with the "ES256K" algorithm identifier. 289 4. IANA Considerations 291 4.1. COSE Algorithms Registrations 293 This section registers the following values in the IANA "COSE 294 Algorithms" registry [IANA.COSE.Algorithms]. 296 o Name: RS256 297 o Value: TBD (temporary assignment -257 already in place) 298 o Description: RSASSA-PKCS1-v1_5 using SHA-256 299 o Reference: Section 2 of this document 300 o Recommended: No 302 o Name: RS384 303 o Value: TBD (temporary assignment -258 already in place) 304 o Description: RSASSA-PKCS1-v1_5 using SHA-384 305 o Reference: Section 2 of this document 306 o Recommended: No 307 o Name: RS512 308 o Value: TBD (temporary assignment -259 already in place) 309 o Description: RSASSA-PKCS1-v1_5 using SHA-512 310 o Reference: Section 2 of this document 311 o Recommended: No 313 o Name: RS1 314 o Value: TBD (temporary assignment -65535 already in place) 315 o Description: RSASSA-PKCS1-v1_5 using SHA-1 316 o Reference: Section 2 of this document 317 o Recommended: Deprecated 319 o Name: ES256K 320 o Value: TBD (requested assignment -47) 321 o Description: ECDSA using secp256k1 curve and SHA-256 322 o Reference: Section 3.2 of this document 323 o Recommended: No 325 4.2. COSE Elliptic Curves Registrations 327 This section registers the following value in the IANA "COSE Elliptic 328 Curves" registry [IANA.COSE.Curves]. 330 o Name: secp256k1 331 o Value: TBD (requested assignment 8) 332 o Key Type: EC2 333 o Description: SECG secp256k1 curve 334 o Change Controller: IESG 335 o Reference: Section 3.1 of [[ this specification ]] 336 o Recommended: No 338 4.3. JOSE Algorithms Registrations 340 This section registers the following value in the IANA "JSON Web 341 Signature and Encryption Algorithms" registry [IANA.JOSE.Algorithms]. 343 o Algorithm Name: ES256K 344 o Algorithm Description: ECDSA using secp256k1 curve and SHA-256 345 o Algorithm Usage Locations: alg 346 o JOSE Implementation Requirements: Optional 347 o Change Controller: IESG 348 o Reference: Section 3.2 of [[ this specification ]] 349 o Algorithm Analysis Document(s): [SEC2] 351 4.4. JSON Web Key Elliptic Curves Registrations 353 This section registers the following value in the IANA "JSON Web Key 354 Elliptic Curve" registry [IANA.JOSE.Curves]. 356 o Curve Name: secp256k1 357 o Curve Description: SECG secp256k1 curve 358 o JOSE Implementation Requirements: Optional 359 o Change Controller: IESG 360 o Specification Document(s): Section 3.1 of [[ this specification ]] 362 5. Security Considerations 364 5.1. RSA Key Size Security Considerations 366 The security considerations on key sizes for RSA algorithms from 367 Section 6.1 of [RFC8230] also apply to the RSA algorithms in this 368 specification. 370 5.2. RSASSA-PKCS1-v1_5 with SHA-2 Security Considerations 372 The security considerations on the use of RSASSA-PKCS1-v1_5 with 373 SHA-2 hash functions (SHA-256, SHA-384, and SHA-512) from Section 8.3 374 of [RFC7518] also apply to their use in this specification. For that 375 reason, these algorithms are registered as being "Not Recommended". 376 Likewise, the exponent restrictions described in Section 8.3 of 377 [RFC7518] also apply. 379 5.3. RSASSA-PKCS1-v1_5 with SHA-1 Security Considerations 381 The security considerations on the use of the SHA-1 hash function 382 from [RFC6194] apply in this specification. For that reason, the 383 "RS1" algorithm is registered as "Deprecated". Likewise, the 384 exponent restrictions described in Section 8.3 of [RFC7518] also 385 apply. 387 A COSE algorithm identifier for this algorithm is nonetheless being 388 registered because deployed TPMs continue to use it, and therefore 389 WebAuthn implementations need a COSE algorithm identifier for "RS1" 390 when TPM attestations using this algorithm are being represented. 391 New COSE applications and protocols MUST NOT use this algorithm. 393 5.4. secp256k1 Security Considerations 395 Care should be taken that a secp256k1 key is not mistaken for a P-256 396 [RFC7518] key, given that their representations are the same except 397 for the "crv" value. As described in Section 8.1.1 of [RFC8152], we 398 currently do not have any way to deal with this attack except to 399 restrict the set of curves that can be used. 401 The procedures and security considerations described in the [SEC1], 402 [SEC2], and [DSS] specifications apply to implementations of this 403 specification. 405 Timing side-channel attacks are possible if the implementation of 406 scalar multiplication over the curve does not execute in constant 407 time. 409 There are theoretical weaknesses with this curve that could result in 410 future attacks. While these potential weaknesses are not unique to 411 this curve, they are the reason that this curve is registered as 412 "Recommended: No". 414 6. References 416 6.1. Normative References 418 [DSS] National Institute of Standards and Technology (NIST), 419 "Digital Signature Standard (DSS)", FIPS PUB 186-4, July 420 2013, . 423 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 424 Requirement Levels", BCP 14, RFC 2119, 425 DOI 10.17487/RFC2119, March 1997, 426 . 428 [RFC6194] Polk, T., Chen, L., Turner, S., and P. Hoffman, "Security 429 Considerations for the SHA-0 and SHA-1 Message-Digest 430 Algorithms", RFC 6194, DOI 10.17487/RFC6194, March 2011, 431 . 433 [RFC7515] Jones, M., Bradley, J., and N. Sakimura, "JSON Web 434 Signature (JWS)", RFC 7515, DOI 10.17487/RFC7515, May 435 2015, . 437 [RFC7517] Jones, M., "JSON Web Key (JWK)", RFC 7517, 438 DOI 10.17487/RFC7517, May 2015, 439 . 441 [RFC7518] Jones, M., "JSON Web Algorithms (JWA)", RFC 7518, 442 DOI 10.17487/RFC7518, May 2015, 443 . 445 [RFC8017] Moriarty, K., Ed., Kaliski, B., Jonsson, J., and A. Rusch, 446 "PKCS #1: RSA Cryptography Specifications Version 2.2", 447 RFC 8017, DOI 10.17487/RFC8017, November 2016, 448 . 450 [RFC8152] Schaad, J., "CBOR Object Signing and Encryption (COSE)", 451 RFC 8152, DOI 10.17487/RFC8152, July 2017, 452 . 454 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 455 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 456 May 2017, . 458 [RFC8230] Jones, M., "Using RSA Algorithms with CBOR Object Signing 459 and Encryption (COSE) Messages", RFC 8230, 460 DOI 10.17487/RFC8230, September 2017, 461 . 463 [SEC1] Standards for Efficient Cryptography Group, "SEC 1: 464 Elliptic Curve Cryptography", Version 2.0, May 2009, 465 . 467 [SEC2] Standards for Efficient Cryptography Group, "SEC 2: 468 Recommended Elliptic Curve Domain Parameters", 469 Version 2.0, January 2010, 470 . 472 6.2. Informative References 474 [CTAP] Brand, C., Czeskis, A., Ehrensvaerd, J., Jones, M., Kumar, 475 A., Lindemann, R., Powers, A., and J. Verrept, "Client to 476 Authenticator Protocol (CTAP)", FIDO Alliance Proposed 477 Standard, January 2019, . 481 [EuroSP18] 482 Poddebniak, D., Somorovsky, J., Schinzel, S., Lochter, M., 483 and P. Roesler, "Attacking Deterministic Signature Schemes 484 using Fault Attacks", IEEE European Symposium on Security 485 and Privacy (EuroS&P) 2018, April 2018, 486 . 488 [IANA.COSE.Algorithms] 489 IANA, "COSE Algorithms", 490 . 493 [IANA.COSE.Curves] 494 IANA, "COSE Elliptic Curves", 495 . 498 [IANA.JOSE.Algorithms] 499 IANA, "JSON Web Signature and Encryption Algorithms", 500 . 503 [IANA.JOSE.Curves] 504 IANA, "JSON Web Key Elliptic Curve", 505 . 508 [Kudelski17] 509 Romailler, Y., "How to defeat Ed25519 and EdDSA using 510 faults", October 2017, 511 . 514 [RFC6979] Pornin, T., "Deterministic Usage of the Digital Signature 515 Algorithm (DSA) and Elliptic Curve Digital Signature 516 Algorithm (ECDSA)", RFC 6979, DOI 10.17487/RFC6979, August 517 2013, . 519 [WebAuthn] 520 Balfanz, D., Czeskis, A., Hodges, J., Jones, J., Jones, 521 M., Kumar, A., Liao, A., Lindemann, R., and E. Lundberg, 522 "Web Authentication: An API for accessing Public Key 523 Credentials - Level 1", World Wide Web Consortium 524 (W3C) Recommendation, March 2019, 525 . 527 Acknowledgements 529 Thanks to Roman Danyliw, Linda Dunbar, Stephen Farrell, John Fontana, 530 Jeff Hodges, Kevin Jacobs, J.C. Jones, Benjamin Kaduk, Murray 531 Kucherawy, Neil Madden, John Mattsson, Matthew Miller, Tony Nadalin, 532 Matt Palmer, Eric Rescorla, Rich Salz, Jim Schaad, Goeran Selander, 533 Wendy Seltzer, Sean Turner, and Samuel Weiler for their roles in 534 registering these algorithm identifiers. 536 Document History 538 [[ to be removed by the RFC Editor before publication as an RFC ]] 540 -08 541 o Addressed IESG review comments by Benjamin Kaduk and Roman 542 Danyliw, primarily completing the edits to register secp256k1 and 543 ES256K as "Recommended: No" for COSE. Some additional security 544 considerations were also added. 546 -07 548 o Addressed editorial SecDir review comment by Linda Dunbar about 549 SHA-2 algorithms. 551 o Addressed IETF last call comments by Jim Schaad, Rich Salz, and 552 Eric Rescorla, now registering secp256k1 and ES256K as 553 "Recommended: No" for COSE. 555 -06 557 o Addressed Area Director review comment by Murray Kucherawy (which 558 requested an editorial correction). 560 o Changed requested assignment for ES256K from -46 to -47, due to an 561 assignment conflict. 563 -05 565 o Removed unused reference to RFC 7049. 567 -04 569 o Added explanatory comments on design decisions made that were 570 discussed on the mailing list that Jim Schaad requested be added 571 to the draft. 573 -03 575 o Addressed review of -02 by Jim Schaad. 577 -02 579 o Addressed working group last call comments. Thanks to J.C. 580 Jones, Kevin Jacobs, Jim Schaad, Neil Madden, and Benjamin Kaduk 581 for their useful feedback. 583 -01 585 o Changed the JOSE curve identifier from "P-256K" to "secp256k1". 587 o Specified that secp256k1 signing is done using the SHA-256 hash 588 function. 590 -00 592 o Created the initial working group draft from draft-jones-cose- 593 additional-algorithms-00, changing only the title, date, and 594 history entry. 596 Author's Address 598 Michael B. Jones 599 Microsoft 601 Email: mbj@microsoft.com 602 URI: http://self-issued.info/