Confirmed that was the one that got added. I approve.
spt > On Jul 24, 2025, at 10:24, Sean Turner <[email protected]> wrote: > > Hi! > > Is the “new” one from "8.1.3.2. AKP Private Key”. It’s the one I don’t see in > the registries. > > spt > >> On Jul 22, 2025, at 01:00, David Dong via RT >> <[email protected]> wrote: >> >> Hi Goran, Derek, Sean, >> >> Just a ping for this; I understand its IETF week. >> >> Could you review the registration request below from Mike Jones? This is a >> follow-up to the prior registration request, now for the remaining >> registrations in the document. >> >> Please note that this document is in IETF Last Call as well. >> >> Registry: https://www.iana.org/assignments/cose >> Document: https://datatracker.ietf.org/doc/html/draft-ietf-cose-dilithium-08 >> >> The due date for this request would be July 31st. >> >> Best regards, >> >> David Dong >> IANA Services Sr. Specialist >> >> On Thu Jul 10 20:22:07 2025, david.dong wrote: >>> Hi Goran, Derek, Sean, >>> >>> Could you review the registration request below from Mike Jones? This >>> is a follow-up to the prior registration request, now for the >>> remaining registrations in the document. >>> >>> Please note that this document is in IETF Last Call as well. >>> >>> Registry: https://www.iana.org/assignments/cose >>> Document: https://datatracker.ietf.org/doc/html/draft-ietf-cose- >>> dilithium-08 >>> >>> The due date for this request would be July 31st. >>> >>> Best regards, >>> >>> David Dong >>> IANA Services Sr. Specialist >>> >>> On Tue Jul 08 17:59:13 2025, [email protected] wrote: >>>> Dear IANA, >>>> >>>> Now that https://datatracker.ietf.org/doc/draft-ietf-cose-dilithium/ >>>> has been submitted to the IESG for publication, I'm writing as COSE >>>> chair to request early allocation of the remaining registry entries >>>> requested in the specification. Recall that the early allocations >>>> requested in the message below were performed under [IANA #1416863]. >>>> >>>> The additional values to allocate are in the sections: >>>> >>>> * 8.1.3.2. <https://www.ietf.org/archive/id/draft-ietf-cose- >>>> dilithium-08.html#section-8.1.3.2> AKP Private >>>> Key<https://www.ietf.org/archive/id/draft-ietf-cose-dilithium- >>>> 08.html#name-akp-private-key> >>>> * 8.1.6.2. <https://www.ietf.org/archive/id/draft-ietf-cose- >>>> dilithium-08.html#section-8.1.6.2> AKP Private >>>> Key<https://www.ietf.org/archive/id/draft-ietf-cose-dilithium- >>>> 08.html#name-akp-private-key-2> >>>> >>>> Thank you, >>>> -- Mike >>>> >>>> From: Michael Jones >>>> Sent: Friday, April 11, 2025 2:16 PM >>>> To: [email protected] >>>> Cc: [email protected]; [email protected]; Deb Cooley <[email protected]> >>>> Subject: Request for early allocation of values defined in draft- >>>> ietf- >>>> cose-dilithium >>>> >>>> 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] To unsubscribe send an email to [email protected]
