Hi Hannes, Thank you for your efforts in organizing the discussion. I also believe that it is necessary to summarize the long COSE-HPKE discussions at this stage.
Regarding "enc", as Ilari and Laurence mentioned, it seems that there is no solution other than representing it as a byte string. Regarding the algorithm identifier, in the following two messages, I compared and organized the current draft's approach with the approach of including KEM/KDF/AEAD all within the alg value: https://mailarchive.ietf.org/arch/msg/cose/KTpXbZ3UxUH8BuLT4OmhfaToYTk/ https://mailarchive.ietf.org/arch/msg/cose/cPqYqCagPbWPKwvQODjqn98U3F4/ Based on the comparison, I concluded that the former is superior. Since then, I haven't received any specific and reasonable counterarguments from anyone. Personally, I still believe that the current draft's alg values are a result of some compromises but provide a good middle ground. My opinion remains unchanged that it is a much better approach than including KEM/KDF/AEAD all within the alg value. Best, Daisuke 2023年7月18日(火) 0:31 Ilari Liusvaara <[email protected]>: > 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
