On 1/16/25 10:30, Carsten Bormann wrote:
On 2025-01-16, at 13:55, Göran Selander <[email protected]> wrote:• text strings of byte strings (even number of characters ‘0’-‘9’ and ‘a’-‘f’) are encoded as (untagged) CBOR byte strings.We have tag 23 for representing hexadecimal strings as byte strings (which I think this is about) [1]. [1]: https://www.rfc-editor.org/rfc/rfc8949#name-expected-later-encoding-for However, this is for uppercase strings. About half of the hex strings I’m seeing are lowercase. I’m assuming here that makes a difference in the X.509 signature?
I don't think so. I see X.509 hex strings presented in either upper or lower. And sometimes the same OID is displayed differently in different apps.
I don't think 5280 makes a distinction. All case discussions I reviewed in 5280 are about case within a string field.
I propose that we add a (1+1) tag for those two (e.g. 108 for ‘l’ as in lowercase). (No help with mixed case, but I haven’t seen those.) Grüße, Carsten _______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
