Thank you for your question! The authors are currently doing a push to go through the open issues* and address all the critical ones to get it ready for a wg last call for the upcoming IETF meeting. It is likely we will post some related questions here on the COSE mailing list, asking for input during the upcoming period. If you already have questions or comments, feel free to reach out to us!
*https://github.com/cose-wg/CBOR-certificates/issues Best Regards Joel Höglund On Wed, 15 Jan 2025 at 17:34, Robert Moskowitz <[email protected]> wrote: > Where does this stand wrt wg last call? > > It is getting serious consideration in some interesting aviation comm. > Well beyond what I am doing with it for UAS... > > Bob > > On 1/8/25 07:29, [email protected] wrote: > > Internet-Draft draft-ietf-cose-cbor-encoded-cert-12.txt is now > available. It > > is a work item of the CBOR Object Signing and Encryption (COSE) WG of the > > IETF. > > > > Title: CBOR Encoded X.509 Certificates (C509 Certificates) > > Authors: John Preuß Mattsson > > Göran Selander > > Shahid Raza > > Joel Höglund > > Martin Furuhed > > Name: draft-ietf-cose-cbor-encoded-cert-12.txt > > Pages: 73 > > Dates: 2025-01-08 > > > > Abstract: > > > > This document specifies a CBOR encoding of X.509 certificates. The > > resulting certificates are called C509 Certificates. The CBOR > > encoding supports a large subset of RFC 5280 and all certificates > > compatible with the RFC 7925, IEEE 802.1AR (DevID), CNSA, RPKI, GSMA > > eUICC, and CA/Browser Forum Baseline Requirements profiles. When > > used to re-encode DER encoded X.509 certificates, the CBOR encoding > > can in many cases reduce the size of RFC 7925 profiled certificates > > with over 50% while also significantly reducing memory and code size > > compared to ASN.1. The CBOR encoded structure can alternatively be > > signed directly ("natively signed"), which does not require re- > > encoding for the signature to be verified. The document also > > specifies C509 Certificate Signing Requests, C509 COSE headers, a > > C509 TLS certificate type, and a C509 file format. > > > > The IETF datatracker status page for this Internet-Draft is: > > https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/ > > > > There is also an HTML version available at: > > > https://www.ietf.org/archive/id/draft-ietf-cose-cbor-encoded-cert-12.html > > > > A diff from the previous version is available at: > > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-cbor-encoded-cert-12 > > > > Internet-Drafts are also available by rsync at: > > rsync.ietf.org::internet-drafts > > > > > > _______________________________________________ > > COSE mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > _______________________________________________ > COSE mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
