| Internet-Draft | jose-cose-dilithium | June 2024 |
| Prorock, et al. | Expires 4 December 2024 | [Page] |
This document describes JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) serializations for Module-Lattice-Based Digital Signature Standard (ML-DSA), which was derived from Dilithium, a Post-Quantum Cryptography (PQC) based digital signature scheme.¶
This document does not define any new cryptography, only seralizations of existing cryptographic systems described in [FIPS-204].¶
Note to RFC Editor: This document should not proceed to AUTH48 until NIST completes paramater tuning and selection as a part of the PQC standardization process.¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://cose-wg.github.io/draft-ietf-cose-dilithium/draft-ietf-cose-dilithium.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-ietf-cose-dilithium/.¶
Discussion of this document takes place on the CBOR Object Signing and Encryption Working Group mailing list (mailto:cose@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/cose/. Subscribe at https://www.ietf.org/mailman/listinfo/cose/.¶
Source for this draft and an issue tracker can be found at https://github.com/cose-wg/draft-ietf-cose-dilithium.¶
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 4 December 2024.¶
Copyright (c) 2024 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
As noted in [FIPS-204], ML-DSA is derived from Version 3.1 of CRYSTALS-DILITHIUM, and is believed to be secure even against adversaries in possession of a large-scale quantum computer.¶
CRYSTALS-DILITHIUM is one of the post quantum cryptography algorithms selected in [NIST-PQC-2022].¶
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 ML-DSA Signature Scheme is paramaterized to support different security levels.¶
This document requests the registration of the following algorithms in [IANA.jose]:¶
| Name | alg | Description |
|---|---|---|
| ML-DSA-44 | ML-DSA-44 | JSON Web Signature Algorithm for ML-DSA-44 |
| ML-DSA-65 | ML-DSA-65 | JSON Web Signature Algorithm for ML-DSA-65 |
| ML-DSA-87 | ML-DSA-87 | JSON Web Signature Algorithm for ML-DSA-87 |
This document requests the registration of the following algorithms in [IANA.cose]:¶
| Name | alg | Description |
|---|---|---|
| ML-DSA-44 | TBD (requested assignment -48) | CBOR Object Signing Algorithm for ML-DSA-44 |
| ML-DSA-65 | TBD (requested assignment -49) | CBOR Object Signing Algorithm for ML-DSA-65 |
| ML-DSA-87 | TBD (requested assignment -50) | CBOR Object Signing Algorithm for ML-DSA-87 |
The ML-DSA Key Type is used to express Public and Private Keys for use with ML-DSA Algorithms.¶
This document requests the registration of the following key types in [IANA.jose]:¶
| Name | kty | Description |
|---|---|---|
| ML-DSA | ML-DSA | JSON Web Key Type for the ML-DSA Algorithm Family. |
This document requests the registration of the following algorithms in [IANA.cose]:¶
| Name | kty | Description |
|---|---|---|
| ML-DSA | TBD (requested assignment 7) | COSE Key Type for the ML-DSA Algorithm Family. |
The security considerations of [RFC7515], [RFC7517] and [RFC9053] applies to this specification as well.¶
A detailed security analysis of ML-DSA is beyond the scope of this specification, see [FIPS-204] for additional details.¶
IANA is requested to add the following entries to the COSE Algorithms Registry. The following completed registration templates are provided as described in RFC9053 and RFC9054.¶
IANA is requested to add the following entries to the COSE Key Types Registry. The following completed registration templates are provided as described in RFC9053.¶
IANA is requested to add the following entries to the COSE Key Type Parameters. The following completed registration templates are provided as described in RFC9053.¶
IANA is requested to add the following entries to the JSON Web Signature and Encryption Algorithms Registry. The following completed registration templates are provided as described in RFC7518.¶
Algorithm Name: ML-DSA-44¶
Algorithm Description: ML-DSA-44 as described in FIPS 204.¶
Algorithm Usage Location(s): alg¶
JOSE Implementation Requirements: Optional¶
Change Controller: IETF¶
Specification Document(s): RFC XXXX¶
Algorithm Analysis Documents(s): https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.ipd.pdf¶
Algorithm Name: ML-DSA-65¶
Algorithm Description: ML-DSA-65 as described in FIPS 204.¶
Algorithm Usage Location(s): alg¶
JOSE Implementation Requirements: Optional¶
Change Controller: IETF¶
Specification Document(s): RFC XXXX¶
Algorithm Analysis Documents(s): https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.ipd.pdf¶
Algorithm Name: ML-DSA-87¶
Algorithm Description: ML-DSA-87 as described in FIPS 204.¶
Algorithm Usage Location(s): alg¶
JOSE Implementation Requirements: Optional¶
Change Controller: IETF¶
Specification Document(s): RFC XXXX¶
Algorithm Analysis Documents(s): https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.ipd.pdf¶
IANA is requested to add the following entries to the JSON Web Key Types Registry. The following completed registration templates are provided as described in RFC7518 RFC7638.¶
IANA is requested to add the following entries to the JSON Web Key Parameters Registry. The following completed registration templates are provided as described in RFC7517, and RFC7638.¶
{
"kty": "ML-DSA",
"alg": "ML-DSA-44",
"pub": "V53SIdVF...uvw2nuCQ",
"priv": "V53SIdVF...cDKLbsBY"
}
{
"kty": "ML-DSA",
"alg": "ML-DSA-44",
"pub": "V53SIdVF...uvw2nuCQ"
}
TODO¶
{
"alg": "ML-DSA-44"
}
eyJhbGciOiJ...LCJraWQiOiI0MiJ9\ .\ eyJpc3MiOiJ1cm46d...XVpZDo0NTYifQ\ .\ 5MSEgQ0dZB4SeLC...AAAAAABIhMUE
{ / COSE Key /
1: 7, / ML-DSA Key Type /
3: -48, / ML-DSA-44 Algorithm /
-1: h'7803c0f9...3f6e2c70', / ML-DSA Private Key /
-2: h'7803c0f9...3bba7abd', / ML-DSA Public Key /
}
{ / COSE Key /
1: 7, / ML-DSA Key Type /
3: -48, / ML-DSA-44 Algorithm /
-2: h'7803c0f9...3f6e2c70' / ML-DSA Private Key /
}
TODO¶
/ cose-sign1 / 18(
[
/ protected / <<
/ algorithm / 1 : -49 / ML-DSA-65 /
>>
/ unprotected / {},
/ payload / h'66616b65',
/ signature / h'53e855e8...0f263549'
]
)
We would like to thank Simo Sorce, Ilari Liusvaara, Neil Madden, Anders Rundgren, David Waite, and Russ Housley for their review feedback.¶