<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-core-href" target="https://datatracker.ietf.org/doc/html/draft-ietf-core-href-29">
   <front>
      <title>Constrained Resource Identifiers</title>
      <author initials="C." surname="Bormann" fullname="Carsten Bormann">
         <organization>Universität Bremen TZI</organization>
      </author>
      <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
         <organization>Fraunhofer SIT</organization>
      </author>
      <date month="November" day="17" year="2025" />
      <abstract>
	 <t>   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 &quot;URI Schemes&quot;
   registry.


   // (This &quot;cref&quot; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-href-29" />
   
</reference>
