So, draft-mattsson-cose-cbor-cert-compress has in it's title:
CBOR Encoding of X.509 Certificates (CBOR Certificates)Section 7 is: _Natively Signed CBOR Certificates_ and I strongly believe that we should remove this section, and the title. This is going to very confusing. And section 7 is not sufficient to really have native CBOR Certificates. It even says that it's an intermediate step. CBOR encoded X.509 certificates provides an intermediate step between [RFC7925] or [IEEE-802.1AR] profiled X.509 certificates and natively signed CBOR certificates: An implementation of CBOR encoded X.509 certificates contains both the CBOR encoding of the X.509 certificate and the signature operations sufficient for natively signed CBOR certificates. So if this document confuses people into thinking that this intermediate step are "CBOR Certificates", then when we actually do that (as LGL and others want to do with EAT), then there will be mass confusion. So, if that term could be struck from this otherwise excellent document on compressing PKIX certificates, that would be nice. (ps: I have some IDevID examples which I can share. I've been trying to compress them, but haven't done the OID compression that I need yet) -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
