Jim Schaad <[email protected]> wrote: > I just made a relatively fast read through on the compressed > certificate draft. If we are looking to do "native CBOR" certificates > then I think that we need to be very explicit what it is meant by > "native CBOR". When I hear that term I end up with a number of > different things that this could end up being:
> 1. A CBOR Encoding for ASN.1.
I'll bet Nico could whip that up from the Heimdal ASN.1 compiler tools.
It's worth investigating what the resulting benefits would be.
> 2. A CBOR Encoding for an X.509 certificate replacement. (CWT?)
Or possibly an EAT, which is really a subset of CWT.
draft-birkholz-core-coid
> 3. What is being proposed in the document which amounts to CBOR
> Compressed X.509 certificate signed in the CBOR format.
No, that's #4 :-)
0. is CBOR compressed certificates signed in ASN.1 format, because
the CBOR compression was 100% bit-for-bit reversible.
> It might be that coining a new term for this might be best because I
> definitely got a surprise on the definition.
I think that we have use cases for all these.
We probably shouldn't do them all.
It would be very nice if we were able to deploy this incrementally.
I agree that some terms would be helpful.
--
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
