> On Mar 21, 2022, at 11:20 PM, Michael Richardson <[email protected]>
> wrote:
>
> Laurence Lundblade <[email protected] <mailto:[email protected]>>
> wrote:
>> Let me try to be more clear.
>
>> The COSE standard now is:
>
>> kid => bstr
>
>> If we make this change:
>
>> kid => int / bstr
>
>> then we break backwards compatibility for COSE as Mike pointed out
>
> I don't think that this breaks *compatibility*
> Old signed objects are still valid.
I guess you are right.
If you give
kid => int
to an existing implementation it will say “kid is in the wrong format”
If you give
Intkid => int
to an existing implémentation it will say “there is no kid”
Can’t see it matters that much which.
LL
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
