Mike, As one of the designated experts, I am fine with early registration of ML-DSA.
As a group participant, I would ask if there is any interest in early registration for ML-KEM as well? -derek On Wed, April 23, 2025 4:20 pm, Michael Jones wrote: > The reason for omitting the private key registrations at this time is that > that their representations are still being debated, in a discussion > including both the COSE and LAMPS working groups. See the thread > https://mailarchive.ietf.org/arch/msg/cose/9F54S32Xgn_zOdU_oFjnXQta-nE/ > (which I need to reinvigorate to try to drive it to a conclusion). > > Wearing my COSE chair hat, I didn't request registration of the values > that might change. That said, it's very useful for people to be able to > start implementing using the ML-DSA public key representations. > > -- Mike > > From: Filip Skokan <[email protected]> > Sent: Wednesday, April 23, 2025 12:57 PM > To: Michael Jones <[email protected]> > Cc: [email protected]; [email protected]; [email protected]; Deb Cooley > <[email protected]> > Subject: Re: [COSE] Request for early allocation of values defined in > draft-ietf-cose-dilithium > > (JOSE review) > > The "alg" values (section-8.1.7) are good to go. > > An early allocation just for the JWK "kty" value and "pub" parameter > (Given the request to omit "priv"and "seed" from section-8.1.8) would make > an incomplete JWK representation and would in my opinion diminish the > value of such allocation. Thoughts? > > S pozdravem, > Filip Skokan > > > On Fri, 11 Apr 2025 at 23:16, Michael Jones > <[email protected]<mailto:[email protected]>> wrote: > Dear IANA, > > https://datatracker.ietf.org/doc/draft-ietf-cose-dilithium/ defines > identifiers needed for interoperable use of the post-quantum ML-DSA > signature algorithm defined by NIST. Implementers are waiting on the code > point allocations in this draft to be able to produce interoperable > implementations using this algorithm. The draft has completed WGLC and > publication has been requested. > > I am writing as a COSE working group chair requesting that early > allocation be performed for these values defined by the specification: > All values defined in the IANA Considerations section at > https://www.ietf.org/archive/id/draft-ietf-cose-dilithium-06.html#name-iana-considerations > EXCEPT FOR the private key and seed values in Sections 8.1.4, 8.1.6, > 8.1.9.1, and 8.1.9.3. (The private key and seed representations are still > being discussed in coordination with the Lamps working group, and may > change.) > > This action has support from both COSE chairs (Ivo and Mike) and the COSE > area director (Paul). > > Thank you, > -- Mike > > _______________________________________________ > COSE mailing list -- [email protected]<mailto:[email protected]> > To unsubscribe send an email to > [email protected]<mailto:[email protected]> > _______________________________________________ > COSE mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- Derek Atkins 617-623-3745 [email protected] www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
