%% You should probably cite draft-ietf-cose-cbor-encoded-cert-09 instead of this revision.
@techreport{ietf-cose-cbor-encoded-cert-00,
    number =    {draft-ietf-cose-cbor-encoded-cert-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/00/},
    author =    {Shahid Raza and Joel Höglund and Göran Selander and John Preuß Mattsson and Martin Furuhed},
    title =     {{CBOR Encoded X.509 Certificates (C509 Certificates)}},
    pagetotal = 40,
    year =      2021,
    month =     apr,
    day =       28,
    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 significantly reduces the size of certificates compatible with e.g. RFC 7925, IEEE 802.1AR (DevID), CNSA, and CA/Browser Forum Baseline Requirements. 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\%. 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 COSE headers as well as a TLS certificate type for C509 certificates. NOTE: "C509" is a placeholder, name to be decided by the COSE WG.},
}