Hi Hannes, Thanks for updating the examples of my proposal.
> Thoughts about the direction we should go? I would like to reiterate my thoughts. I am thinking that it may be necessary to define HPKE Mode Information (Base, Auth, PSK, AuthPSK) and HPKE Version Information as optional parameters for HPKE Sender Information (HSI). However, it is possible that neither is required. I am not sure and would like to hear your opinions on this point on this mailing list (or perhaps we should ask the authors of the HPKE spec about this point). If the HSI needs to have at least one optional parameter other than KEM, then the array structure is not suitable for it very well and my proposal might be better. Otherwise, Ilari's proposal would be better. Basically, I think small message size is a feature for COSE to pursue, so it would be better to adopt Ilari's proposal if we can. Regards, Daisuke 2022年11月24日(木) 21:15 Hannes Tschofenig <[email protected]>: > Hi all, > > I have updated the two proposals from Ilari & Daisuke and I think they are > detailed enough to make a decision. > > Daisuke's proposal is here: > > https://github.com/cose-wg/HPKE/blob/d54703e0894f69f74db34526fb5c5f300ff3e03e/draft-ietf-cose-hpke.md > > Ilari's proposal is here: > > https://github.com/cose-wg/HPKE/blob/010965883cf02d357d972e05dbb96795069f68ba/draft-ietf-cose-hpke.md > > At this point in time it is probably best to look at the examples. > > The main differences between the two proposals are: > > * Terminology: Daisuke uses the term HPKE Sender Information structure to > refer to the payload that contains the HPKE information while Ilari calls > it encapsulated_key structure. > > * Encoding: Ilari uses an array for the encapsulated_key structure with no > option for extensibility. As a result there is no need to register the > parameter labels. Daisuke uses a map structure for the HPKE sender > information. > > Thoughts about the direction we should go? > > Ciao > Hannes > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > _______________________________________________ > COSE mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/cose >
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
