On 2021-01-20, at 18:12, Laurence Lundblade <[email protected]> wrote: > > One way to handle CBOR certs in files would be to use the CBOR magic number > 55799 (0xd9d9f7) to identify it as CBOR and then define a tag to identify it > as a CBOR-cert.
A single tag will be enough. (Having both would be useful if there is a meaningful way to handle these by tools that need to recognize this is CBOR, but not that these are CBOR certs.) > Or just rely on the .cbor file extension and a CBOR-cert tag. Right. > It seems to be common practice to define a tag for CBOR protocol messages. > Why not CBOR cert? COSE, CWT, CoSWID and others do it. I opened an issue for > it. > > 0xd9d9f7 also definitely distinguishes CBOR from PEM and DER. Indeed, as would be any smartly chosen tag specifically for CBOR certs. We may want to make this optional, which means that it wouldn’t go into deterministic encoding, but can easily prefixed (to a data item(!)) when writing the file. Grüße, Carsten _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
