I support this proposal. OS
On Mon, Jul 17, 2023 at 2:41 AM Hannes Tschofenig <[email protected]> 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. > > > For the COSE-HPKE draft I would register a few of the currently needed > algorithm values. Future specifications may add new values they find > useful. > > > This is a pragmatic and simple approach. It has been used in the IETF > many times already. > > > Ciao > Hannes > > > Am 17.07.2023 um 09:29 schrieb Ilari Liusvaara: > > On Thu, Jul 13, 2023 at 11:41:49AM +0200, Hannes Tschofenig wrote: > >> Hi all, > >> > >> The following people expressed their preference for a single algorithm > >> to express the HPKE combination of KEM/KDF/AEAD*: > > ... > > > >> *: Various ways for registering this combination have been mentioned > >> and discussed. I leave those details for later. > > Has there been a proposal for a way that is none of the following? > > > > > > 1) Systematic embedding of the ciphersuite (internal HPKE term) > > identifiers into alg. > > > > > > 2) Creating some sort of special procedure to allow registering new > > algorithms for ciphersuites just specifying the HPKE identifer values. > > > > > > 3) Not allowing adding new ciphersuites. Any new ciphersuites would > > require a new version of COSE-HPKE. > > > > > > I'm drawing a blank trying to think a way that is none of the above > > three (even after re-reading the alg discussion thread). > > > > > > Every other user of HPKE I am aware of is either not using ciphersuites > > (most), or is not mixing HPKE ciphersuites with non-HPKE stuff (MLS), > > so this kind of thing never even comes up. > > > > > > > > > > -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 > -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
