WebAuthn Working Group | M. Jones |
Internet-Draft | Microsoft |
Intended status: Informational | May 30, 2018 |
Expires: December 1, 2018 |
Using secp256k1 with JOSE and COSE
draft-jones-webauthn-secp256k1-00
This specification defines algorithm encodings and representations enabling the Standards for Efficient Cryptography Group (SECG) elliptic curve "secp256k1" to be used for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) messages.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
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 December 1, 2018.
Copyright (c) 2018 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This specification defines algorithm encodings and representations enabling the Standards for Efficient Cryptography Group (SECG) elliptic curve "secp256k1" [SEC2] to be used for JSON Object Signing and Encryption (JOSE) [RFC7515] and CBOR Object Signing and Encryption (COSE) [RFC8152] messages. The elliptic curve and associated algorithm are registered in appropriate IANA JOSE and COSE registries.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
The Standards for Efficient Cryptography Group (SECG) elliptic curve "secp256k1" [SEC2] is represented in a JSON Web Key (JWK) [RFC7517] using these values:
plus x and y values to represent the curve point for the key. Other optional values such as alg MAY also be present.
It is represented in a COSE_Key [RFC8152] using these values:
plus x (-2) and y (-3) values to represent the curve point for the key. Other optional values such as alg (3) MAY also be present.
The ECDSA signature algorithm is defined in [DSS]. Implementations need to check that the key type is EC for JOSE or EC2 (2) for COSE when creating or verifying a signature.
The ECDSA algorithm specified in this document is:
JOSE Alg Name | COSE Alg Value | Description |
---|---|---|
ES256K | TBD (requested assignment -43) | ECDSA w/ secp256k1 Curve |
This section registers the following value in the IANA "JSON Web Key Elliptic Curve" registry [IANA.JOSE.Curves].
This section registers the following value in the IANA "JSON Web Signature and Encryption Algorithms" registry [IANA.JOSE.Algorithms].
This section registers the following value in the IANA "COSE Elliptic Curves" registry [IANA.COSE.Curves].
This section registers the following value in the IANA "COSE Algorithms" registry [IANA.COSE.Algorithms].
Care should be taken that a secp256k1 key not be mistaken for a P-256 key, given that their representations are the same except for the crv value.
The procedures and security considerations described in the [SEC1], [SEC2], and [DSS] specifications apply to implementations of this specification.
[DSS] | National Institute of Standards and Technology (NIST), "Digital Signature Standard (DSS)", FIPS PUB 186-4, July 2013. |
[RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. |
[RFC7515] | Jones, M., Bradley, J. and N. Sakimura, "JSON Web Signature (JWS)", RFC 7515, DOI 10.17487/RFC7515, May 2015. |
[RFC7517] | Jones, M., "JSON Web Key (JWK)", RFC 7517, DOI 10.17487/RFC7517, May 2015. |
[RFC8152] | Schaad, J., "CBOR Object Signing and Encryption (COSE)", RFC 8152, DOI 10.17487/RFC8152, July 2017. |
[RFC8174] | Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017. |
[SEC1] | Standards for Efficient Cryptography Group, "SEC 1: Elliptic Curve Cryptography", Version 2.0, May 2009. |
[SEC2] | Standards for Efficient Cryptography Group, "SEC 2: Recommended Elliptic Curve Domain Parameters", Version 2.0, January 2010. |
[IANA.COSE.Algorithms] | IANA, "COSE Algorithms" |
[IANA.COSE.Curves] | IANA, "COSE Elliptic Curves" |
[IANA.JOSE.Algorithms] | IANA, "JSON Web Signature and Encryption Algorithms" |
[IANA.JOSE.Curves] | IANA, "JSON Web Key Elliptic Curve" |
TBD
[[ to be removed by the RFC Editor before publication as an RFC ]]
-00