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. Or just rely on the .cbor file extension and a CBOR-cert tag.
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
<https://github.com/EricssonResearch/CBOR-certificates/issues/84> for it.
0xd9d9f7 also definitely distinguishes CBOR from PEM and DER.
LL
_______________________________________________
COSE mailing list
COSE@ietf.org
https://www.ietf.org/mailman/listinfo/cose
