Skip to main content

ML-DSA for JOSE and COSE
draft-ietf-cose-dilithium-11

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, cose-chairs@ietf.org, cose@ietf.org, draft-ietf-cose-dilithium@ietf.org, lucas.prabel@huawei.com, paul.wouters@aiven.io, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'ML-DSA for JOSE and COSE' to Proposed Standard (draft-ietf-cose-dilithium-10.txt)

The IESG has approved the following document:
- 'ML-DSA for JOSE and COSE'
  (draft-ietf-cose-dilithium-10.txt) as Proposed Standard

This document is the product of the CBOR Object Signing and Encryption
Working Group.

The IESG contact persons are Paul Wouters and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-cose-dilithium/


Ballot Text

Technical Summary

   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), a Post-Quantum
   Cryptography (PQC) digital signature scheme defined in FIPS 204.

Working Group Summary

   Extended discussions took place on the mailing list concerning the appropriate
   “kty” value to define and use for ML-DSA. The solution of introducing the new
   Algorithm Key Pair (AKP) type seemed to gather working group support.
   Additionally, comments were made about the specification of the “context”
   string in ML-DSA, as well as the draft being too underspecified. The authors
   addressed these comments during the WGLC.

   Ultimately, none of the document updates encountered significant objections. No
   one spoke against the adoption of the document during the WGLC. Consequently,
   there was no particular controversy over specific points, nor were there
   significant difficulties in reaching consensus.

Document Quality

   There are no known existing implementations yet, but the examples in
   Appendix A were generated using code specifically written for the draft,
   as reported on the COSE mailing list
   (https://mailarchive.ietf.org/arch/msg/cose/_IbCQoSJeXFG-GDZFlJZnZHCP1U/).


Personnel

   The Document Shepherd for this document is Lucas Prabel. The Responsible
   Area Director is Paul Wouters.

RFC Editor Note