<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.mcnally-deterministic-cbor" target="https://datatracker.ietf.org/doc/html/draft-mcnally-deterministic-cbor-11">
   <front>
      <title>dCBOR: A Deterministic CBOR Application Profile</title>
      <author initials="W." surname="McNally" fullname="Wolf McNally">
         <organization>Blockchain Commons</organization>
      </author>
      <author initials="C." surname="Allen" fullname="Christopher Allen">
         <organization>Blockchain Commons</organization>
      </author>
      <author initials="C." surname="Bormann" fullname="Carsten Bormann">
         <organization>Universität Bremen TZI</organization>
      </author>
      <author initials="L." surname="Lundblade" fullname="Laurence Lundblade">
         <organization>Security Theory LLC</organization>
      </author>
      <date month="August" day="8" year="2024" />
      <abstract>
	 <t>   The purpose of determinism is to ensure that semantically equivalent
   data items are encoded into identical byte streams.  CBOR (RFC 8949)
   defines &quot;Deterministically Encoded CBOR&quot; in its Section 4.2, but
   leaves some important choices up to the application developer.  The
   CBOR Common Deterministic Encoding (CDE) Internet Draft builds on
   this by specifying a baseline for application profiles that wish to
   implement deterministic encoding with CBOR.  The present document
   provides an application profile &quot;dCBOR&quot; that can be used to help
   achieve interoperable deterministic encoding based on CDE for a
   variety of applications wishing an even narrower and clearly defined
   set of choices.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-mcnally-deterministic-cbor-11" />
   
</reference>
