%% You should probably cite rfc9581 instead of this I-D.
@techreport{ietf-cbor-time-tag-11,
    number =    {draft-ietf-cbor-time-tag-11},
    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-time-tag/11/},
    author =    {Carsten Bormann and Ben Gamari and Henk Birkholz},
    title =     {{Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period}},
    pagetotal = 23,
    year =      2023,
    month =     oct,
    day =       22,
    abstract =  {The Concise Binary Object Representation (CBOR, RFC 8949) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. In CBOR, one point of extensibility is the definition of CBOR tags. RFC 8949 defines two tags for time: CBOR tag 0 (RFC3339 time as a string) and tag 1 (POSIX time as int or float). Since then, additional requirements have become known. The present document defines a CBOR tag for time that allows a more elaborate representation of time, as well as related CBOR tags for duration and time period. This document is intended as the reference document for the IANA registration of the CBOR tags defined. // (This cref will be removed by the RFC editor:) The present // revision (\textendash{}11) addresses the ARTART and IOTDIR directorate // reviews.},
}