Open laurencelundblade opened 1 year ago
I think it's a good idea. It would be helpful to the implementors. I support adding this kind of description to the spec.
We had this type of description in an earlier version of the spec, see https://www.ietf.org/archive/id/draft-ietf-cose-hpke-05.html#name-hpke-encryption-and-decrypt
Is this what you are asking for?
As an implementor, what I really want to know is how COSE data structures go in and out of the HPKE Seal() and Open() APIs. These APIs are THE definition of HPKE.
I would write a section, maybe as a table with one Seal() parameter per row and describe how to construct them.