> On 19. Nov 2025, at 18:38, Robert Moskowitz <[email protected]> wrote: > > > > On 11/19/25 12:08 PM, Lijun Liao wrote: >> As I understand it, this depends on how you represent the serial number. >> >> If you represent it as even-number lower-case text, e.g. „789abc“, then it >> can be represented >> as three bytes [0x78, 0x9a, 0xbc], otherwise, it will be encoded as normal >> text. > What do you mean by "normal text"?
I mean the textual representation, e.g. „789ABC“ is represented as [0x37, 0x38, 0x39, 0x41, 0x42, 0x43]. > > All 24-bit Aircraft Numbers CAN be represented as 000000 - ffffff. And are > you saying it make a difference upper or lower case? Yes. As per text "If the text string has an even length ≥ 2 and contains only the symbols '0'–'9' or 'a'–'f', it is encoded as a CBOR byte string“ in Section 3.1.4. > > I am setting up some testing in both subject and subjectAltName to see any > difference. Particularly as in the "normal" case, subject is null. As per definition: „Name = [ * Attribute ] / SpecialText“, if a subject does not have any attributes, it is represented as an empty array, but not null. > >> >>> On 18. Nov 2025, at 19:03, Robert Moskowitz >>> <[email protected]> wrote: >>> >>> I have a question on encoding of the DN attribute, serialNumber. >>> >>> In 3.1.4, Issuer this is covered. >>> >>> i.e., serialNumber SHALL only contain the 74-character subset of >>> ASCII allowed by printableString >>> >>> If the serialNumber is an integer, is it still encoded as >>> >>> In CBOR, all text strings are UTF-8 encoded >>> >>> or is it recognized as an int and encoded thusly? >>> >>> Case in point: For the 24-bit Aircraft Number (max value 16777215 or >>> xFFFFFF), how best to efficiently represent that? >>> >>> as the integer number or in hex string? >>> >>> Also since this would be the only subject attribute and there is already >>> subjectAltName, make this the only subject element or add it to >>> subjectAltName. >>> >>> Obviously, I could experiment around, but you want me to review >>> text-vectors! >>> >>> thanks >>> >>> _______________________________________________ >>> COSE mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >> _______________________________________________ >> COSE mailing list -- [email protected] <mailto:[email protected]> >> To unsubscribe send an email to [email protected] >> <mailto:[email protected]>
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
