%% You should probably cite draft-ietf-core-href-15 instead of this revision.
@techreport{ietf-core-href-14,
    number =    {draft-ietf-core-href-14},
    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-core-href/14/},
    author =    {Carsten Bormann and Henk Birkholz},
    title =     {{Constrained Resource Identifiers}},
    pagetotal = 57,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {The Constrained Resource Identifier (CRI) is a complement to the Uniform Resource Identifier (URI) that represents the URI components in Concise Binary Object Representation (CBOR) instead of a sequence of characters. This simplifies parsing, comparison, and reference resolution in environments with severe limitations on processing power, code size, and memory size. // (This "cref" paragraph will be removed by the RFC editor:) The // present revision \textendash{}14 of this draft picks up comments from the // shepherd review and adds sections on CoAP integration and on cri // application-oriented literals for the Extended Diagnostic // Notation. This revision still contains open issues and is // intended to serve as a snapshot while the processing of the // shepherd review is being completed.},
}