Hi Ilari, here is what I would do.
>From your example let's say that - KEM=49 corresponds to DHKEM(P-256, HKDF-SHA256), - KDF=4 corresponds to HKDF-SHA256, - AEAD=2 corresponds to AES-128-GCM, and - AEAD=3 corresponds to ChaCha20Poly1305. I would register two values in the IANA COSE algorithm registry with TBD1 DHKEM(P-256, HKDF-SHA256) + HKDF-SHA256 + AES-128-GCM TBD2 DHKEM(P-256, HKDF-SHA256) + HKDF-SHA256 + ChaCha20Poly1305 where TBD1 and TBD2 are values selected by IANA. Ciao Hannes -----Ursprüngliche Nachricht----- Von: COSE <[email protected]> Im Auftrag von Ilari Liusvaara Gesendet: Montag, 17. Juli 2023 17:31 An: 'cose' <[email protected]> Betreff: Re: [COSE] COSE-HPKE and the Single Algorithm Discussion On Mon, Jul 17, 2023 at 09:41:37AM +0200, Hannes Tschofenig wrote: > Hi Ilari, > > > we have been for too long turning the allocation of a few values in an > IANA registry into rocket science. > > Hence, I would just go ahead with having specifications register > values into the IANA registry whenever the need arises. There are no > problems with writing new documents. > > This is a pragmatic and simple approach. It has been used in the IETF > many times already. What would the specification for say, the following two (hypothetical) ciphersuites look like (skipping all the boilerplate): - KEM=49, KDF=4, AEAD=2 - KEM=49, KDF=4, AEAD=3 ? I think this should be too simple to even need a document... -Ilari _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
