Understood about the use case. Thx for the background.
> On Aug 10, 2021, at 3:13 AM, Göran Selander
> <[email protected]> wrote:
>
> Assume that we do want to allow key identifiers to be CBOR ints in certain
> settings, what is the best (least intrusive) way to allow this while still
> maintain compatibility with 'kid's supporting the type bstr? Another
> alternative to what has been listed below is to define 'kid2' to only be of
> type int - is that a better option?
I didn’t write actual code to check, but they about the same to me.
‘kid' as int/bstr seems less confusing to me than ‘kid2’. It tells you it does
exactly the same thing whether it is an int or a bstr.
So my pick is ‘kid’, but ‘kid2’ is OK too.
LL
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
