I don’t think tstr can be removed from the standard. That would break backwards
compatibility. Maybe a strong recommendation could be added with the comment
that many implementations don’t support tstr.
There is a revision of 8152 in process right now called 8152bis. That seems
like the place
Hi folks,
> I prefer to see the option of `tstr` labels removed if possible.
I'm glad to see that there are several people who agree with me.
To remove the option of tstr labels from the spec, would a revised RFC be
needed? Or would an errata enough for that?
Anyway, I would like to hear from
Hi list,
I agree with Laurence on this. I work on platform-related security standards at
GlobalPlatform where we are using COSE quite extensively. A major use-case is
highly constrained embedded targets where the benefits from eliminating string
handling are considerable – many such platforms
