Internet-Draft draft-ietf-cose-cbor-encoded-cert-15.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-15.txt
Pages: 86
Dates: 2025-08-18
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 1.0, RPKI,
GSMA eUICC, and CA/Browser Forum Baseline Requirements profiles.
C509 is deployed in different settings including, in-vehicle and
vehicle-to-cloud communication, Unmanned Aircraft Systems (UAS), and
Global Navigation Satellite System (GNSS). 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 by 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 TLSA selectors registry defined in RFC
6698 is extended to include C509 certificates. The document also
specifies C509 Certificate 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-15.html
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-cbor-encoded-cert-15
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]
