%% You should probably cite draft-ietf-cbor-edn-literals-16 instead of this revision.
@techreport{ietf-cbor-edn-literals-02,
    number =    {draft-ietf-cbor-edn-literals-02},
    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-cbor-edn-literals/02/},
    author =    {Carsten Bormann},
    title =     {{Application-Oriented Literals in CBOR Extended Diagnostic Notation}},
    pagetotal = 17,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {The Concise Binary Object Representation, CBOR (RFC 8949), defines a "diagnostic notation" in order to be able to converse about CBOR data items without having to resort to binary data. This document specifies how to add application-oriented extensions to the diagnostic notation. It then defines two such extensions for text representations of epoch-based date/times and of Constrained Resource Identifiers (draft-ietf-core-href). To facilitate tool interoperation, this document also specifies a formal ABNF definition for extended diagnostic notation (EDN) that accommodates application-oriented literals.},
}