It is hard for me to understand that the saving of a single byte it worth this much attention.
Anyway, if there will a change, it requires SW updates, but only for those who actually adopt the enhanced definition. My guess is that connected systems nowadays support automatic firmware updates making the latter a non-issue. In the COSE Signature Format (CSF) scheme I ran into the same issue and changed back-and-forth until I finally came up with the obvious: let key Id be a CBOR Object. In a specific application using CSF, the profile was set to use "bstr". I'm sure some people prefer "tstr" since it is JOSE compatible. By revising/extending the COSE kid to Object, everybody get what they want. Otherwise, I would suggest status quo. Anders https://test.webpki.org/csf-lab/home _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
