The IESG has approved the following document:
- 'Internet X.509 Public Key Infrastructure - Algorithm Identifiers for
   the Module-Lattice-Based Digital Signature Algorithm (ML-DSA)'
  (draft-ietf-lamps-dilithium-certificates-12.txt) as Proposed Standard

This document is the product of the Limited Additional Mechanisms for PKIX
and SMIME 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-lamps-dilithium-certificates/




Technical Summary

   Digital signatures are used within X.509 certificates, Certificate
   Revocation Lists (CRLs), and to sign messages.  This document
   describes the conventions for using FIPS 204, the Module-Lattice-
   Based Digital Signature Algorithm (ML-DSA) in Internet X.509
   certificates and certificate revocation lists.  The conventions for
   the associated signatures, subject public keys, and private key are
   also described.

Working Group Summary

   There is support in the LAMPS WG for this document.  The discussion was
   very active, and LAMPS WG consensus was reached.

   There was much controversy, especially about the private key format.
   The LAMPS WG reached a place that everyone can live with the result,
   even if everyone is not happy.  That is, the document represents a
   place where all parties are equally unhappy.

Document Quality

   Some implementations have been written, which is the reason that the private 
key format
   discussion became so difficult.  No implementer wanted to make changes.

   Only ASN.1 is used.  Once a placeholder value is inserted for the module
   identifier that will be assigned by IANA, the ASN.1 module in Appendix A
   compiler without error.
 
   There is a normative DOWNREF to RFC 5912, which is already in the
   DOWNREF registry.


Personnel

   The Document Shepherd for this document is Russ Housley. The Responsible
   Area Director is Deb Cooley.

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to