<?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-00">
   <front>
      <title>dCBOR: Deterministic CBOR Implementation Practices</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>
      <date month="March" day="8" year="2023" />
      <abstract>
	 <t>   CBOR has many advantages over other data serialization formats.  One
   of its strengths is specifications and guidelines for serializing
   data deterministically, such that multiple agents serializing the
   same data automatically achieve consensus on the exact byte-level
   form of that serialized data.  Nonetheless, determinism is an opt-in
   feature of the specification, and most existing CBOR codecs put the
   primary burden of correct deterministic serialization and validation
   of deterministic encoding during deserialization on the engineer.
   This document specifies a set of norms and practices for CBOR codec
   implementors intended to support deterministic CBOR (&quot;dCBOR&quot;) at the
   codec API level.

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