%% You should probably cite draft-ietf-core-href-30 instead of this revision.
@techreport{ietf-core-href-29,
    number =    {draft-ietf-core-href-29},
    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/29/},
    author =    {Carsten Bormann and Henk Birkholz},
    title =     {{Constrained Resource Identifiers}},
    pagetotal = 58,
    year =      2025,
    month =     nov,
    day =       17,
    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) rather than as a sequence of characters. This approach simplifies parsing, comparison, and reference resolution in environments with severe limitations on processing power, code size, and memory size. This RFC updates RFC 7595 by adding a column on the "URI Schemes" registry. // (This "cref" paragraph will be removed by the RFC editor:) After // approval of -28, the present revision -29 pulls in the newest URI // Schemes and assigns URI scheme numbers for them; it also adjusts // the content-format registration to follow the preferred string // format defined in Section 4.1.4 of RFC 9876. This is now intended // to be ready for integration into the IANA database.},
}