<?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-14">
   <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="January" day="9" year="2024" />
      <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) 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 &quot;cref&quot; paragraph will be removed by the RFC editor:) The
   // present revision –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.

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