On Jul 14, 2023, at 12:12 PM, Orie Steele <[email protected]<mailto:[email protected]>> wrote:
Inline: On Fri, Jul 14, 2023 at 1:09 PM lgl island-resort.com<http://island-resort.com/> <[email protected]<mailto:[email protected]>> wrote: Looks to me that HPKE internally defines what “enc” should be. The formatting of “enc” is an internal HPKE issue. It happens to be a serialized public key produced by the HPKE SerializePublicKey() function, but no one but the HPKE libraries need to know that. Why would any thing other than an HPKE library ever look inside “enc”? Exactly, and since it's "opaque"... such a library can output whatever it likes... possibly randomly alternating between valid opaque representations.... No, it absolutely can not output whatever it likes. It can only output what RFC 9180 says and I don’t see any ambiguity in 9180 on what these bytes are. Maybe the confusion is because RFC 9180 is written in the form of a Python API? It is unconventional, but I don’t see any problems with it being ambiguous or non-interoperable so far. LL
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
