> On May 1, 2023, at 11:34 PM, AJITOMI Daisuke <[email protected]> wrote: > > > How will you know what the actual serializations for pub(-1) and priv(-2) > > will be? They have to vary by KEM, right? > > You can use the ”kem" value in the "hkc" parameter to know the serialization > format. > > However, you don't need to know the serialization format for pub/priv because > it's an internal HPKE layer's business. The COSE layer just needs to pass > ”pub" or "priv" value as it is to the HPKE layer.
Well, that explains a lot. Now I understand the proposal.You are talking about RFC 9180 section 7.1.1 and 7.1.2. It’s not mentioned in your draft so I didn’t know. For EC, this serialization is pretty much the same as COSE_Key uses. (Note that I haven’t used the HPKE Python API. All I do is read RFCs and drafts. You and Ilari probably know many things easily that are maybe not stated in RFCs and drafts because you do a lot with the Python API.) I haven’t changed my mind yet. Looking for specific details of the good and the bad rather than “non-trivial” or “big problem”. LL _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
