<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-mih-sokolov-cose-deterministic-encodings-01" category="std" consensus="true" submissionType="IETF" tocInclude="false" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.0 -->
  <front>
    <title abbrev="COSE Deterministic Encodings">Deterministic Encodings for COSE</title>
    <seriesInfo name="Internet-Draft" value="draft-mih-sokolov-cose-deterministic-encodings-01"/>
    <author initials="S." surname="Mih" fullname="Steven Mih">
      <organization>Action State Group, Inc.</organization>
      <address>
        <email>spec@actionstate.ai</email>
      </address>
    </author>
    <author initials="A." surname="Sokolov" fullname="Anton Sokolov">
      <organization>Tyche Institute</organization>
      <address>
        <email>anton.sokolov@tyche.institute</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>Security</area>
    <workgroup>COSE</workgroup>
    <keyword>COSE</keyword>
    <keyword>hash envelope</keyword>
    <keyword>preimage</keyword>
    <keyword>canonicalization</keyword>
    <keyword>deterministic encoding</keyword>
    <abstract>
      <?line 52?>

<t>A COSE Hash Envelope signs the digest of a preimage, not the preimage
itself. When the preimage is the encoding of a structured value, such as a
CBOR data item, and a verifier holds that value but not the bytes that were
hashed, the verifier has to encode the value again, and the digest matches
only if it applies the same deterministic encoding as the producer. RFC 8949 describes more than one such encoding for the same
content type, and the preimage content type does not identify which one was
applied. This document defines a COSE Hash Envelope protected-header
parameter that identifies the encoding, and one value for CBOR content, the
text string "dtrm", which states that the Core Deterministic Encoding
Requirements of RFC 8949 were applied.</t>
    </abstract>
    <note>
      <name>Note to Readers</name>
      <?line 65?>

<t>Individual submission, intended for the COSE Working Group (cose@ietf.org).</t>
      <t>Source for this document, with a reference emitter and verifier and test
vectors, is at
<eref target="https://github.com/action-state-group/cose-deterministic-encodings"/>.</t>
    </note>
  </front>
  <middle>
    <?line 73?>

<section anchor="intro">
      <name>Introduction</name>
      <t>The COSE Hash Envelope <xref target="RFC9995"/> signs the digest of a preimage and
identifies the hash algorithm (258), the content type of the preimage (259),
and optionally where the preimage can be retrieved (260). A verifier that
holds the preimage can check that the digest of it, produced with the hash
algorithm identified by payload-hash-alg (258), matches the payload, as
<xref target="RFC9995"/> Section 5.3 describes. That check needs no information from this
document, and retaining the preimage is the simplest way to make it
possible.</t>
      <t>The Hash Envelope carries the digest, not the preimage, and
payload-location (260) is optional. The content therefore reaches a
verifier, if at all, from outside the Hash Envelope, in whatever form its
application provides, which can be a structured value rather than the bytes
that were hashed. The content can arrive as a data item inside a larger CBOR
message, and unless the message wraps that item in a byte string, most CBOR
decoders cannot return its encoded bytes (<xref target="I-D.ietf-cbor-serialization"/>
Appendices H.1 and J.1). A system can also store the content in another
representation -- for example, a software inventory that keeps Concise
Software Identification (CoSWID) tags <xref target="RFC9393"/> as records in a database
-- rather than keep a second copy of each item as the bytes that were
hashed, provided that representation preserves each data item exactly
(<xref target="security"/>). To check such content against its Hash Envelope, the
verifier has to encode the value again, the case in which
<xref target="I-D.ietf-cbor-serialization"/> Section 5.3.1 says deterministic encoding
becomes necessary and notes that designs of this kind are often chosen to
reduce data size, preserve privacy, or meet other design constraints. COSE
meets the same need for its own Sig_structure, which
the signer and the verifier each construct rather than transmit, by fixing
how that structure is encoded (<xref target="RFC9052"/> Sections 4.4 and 9). For a Hash
Envelope preimage, whose content type the application chooses, COSE fixes
no encoding.</t>
      <t>Re-encoding reproduces the preimage only if the verifier applies the
encoding the producer applied, and <xref target="RFC8949"/> describes more than one.
Section 4.2.1 sorts map keys bytewise, while Section 4.2.3 keeps the
length-first order of the earlier CBOR specification for protocols that need
to be compatible with that order: <tt>{1000: 1, "a": 2}</tt> is
<tt>a2 19 03 e8 01 61 61 02</tt> under the former and <tt>a2 61 61 02 19 03 e8 01</tt>
under the latter. The preimage-content-type (259) names the type of the content, such as
application/swid+cbor, not the encoding applied to it, so a verifier that
guesses the encoding cannot tell a modified value from one encoded under a
different rule.</t>
      <t>This document defines one protected-header parameter,
deterministic-encodings, which identifies that encoding, and one value for
CBOR content, the text string "dtrm", the identifier the CBOR working group
defines for deterministic serialization (<xref target="dtrm"/>). It uses the extension point the Hash
Envelope protected header already provides (<xref section="4" sectionFormat="of" target="RFC9995"/>:
<tt>* (int / tstr) =&gt; any</tt>). The encoding is not carried as a media-type
parameter of preimage-content-type (259). The application/cbor media type defines no
parameters (<xref target="RFC8949"/> Section 9.3), so such a parameter would have to be
registered for every media type the encoding applies to, and a CoAP
Content-Format number carries only the parameters fixed in its registry
entry (<xref target="RFC7252"/> Section 12.3), so each pairing of media type and encoding
would also need its own number. A profile that has its own media type, such
as application/vnd.ipld.dag-cbor <xref target="DAG-CBOR"/>, is already identified by 259;
content labelled application/cbor, or with an application's own type such as
application/swid+cbor, is not.</t>
      <t>The scope of this document is structured values, such as CBOR data items,
and the deterministic encodings that serialize them. Media encodings, such
as those of images, and builds of software from source code are out of
scope; such content is checked from its bytes, as <xref target="RFC9995"/> Section 5.3
describes.</t>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP 14
<xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as
shown here.</t>
      <t>"COSE", "COSE_Sign1", and "protected header" are defined in <xref target="RFC9052"/>;
"CDDL" in <xref target="RFC8610"/>; "Hash Envelope" and "preimage" in <xref target="RFC9995"/>.
As in <xref target="RFC9995"/>, the payload of a Hash Envelope is a digest, and the
preimage consists of the bytes that were hashed to produce it.
The Hash Envelope labels this document builds on are 258 (payload-hash-alg),
259 (preimage-content-type), and 260 (payload-location).</t>
      <t>This document also uses the following terms:</t>
      <dl>
        <dt>Structured value:</dt>
        <dd>
          <t>A value with internal structure, such as a CBOR data item, that a
deterministic encoding serializes to create a preimage.</t>
        </dd>
        <dt>Content binding:</dt>
        <dd>
          <t>The correspondence between content a verifier holds -- a preimage, or a
structured value -- and the payload of a Hash Envelope. A verifier that
checks a content binding reports one of three outcomes: verified, failed,
or unverified.</t>
        </dd>
        <dt>Verified:</dt>
        <dd>
          <t>The digest of the preimage, held or re-created from a structured value,
produced with the hash algorithm identified by payload-hash-alg (258),
matches the payload, and the verifier found no inconsistency in the
protected header (<xref target="consistency"/>).</t>
        </dd>
        <dt>Failed:</dt>
        <dd>
          <t>The verifier found the protected header inconsistent (<xref target="consistency"/>), or
the digest of the preimage, held or re-created from a structured value,
produced with the hash algorithm identified by payload-hash-alg (258),
does not match the payload.</t>
        </dd>
        <dt>Unverified:</dt>
        <dd>
          <t>Neither verified nor failed. When the verifier found no inconsistency in
the protected header (<xref target="consistency"/>), this is the case if it holds
neither the preimage nor a structured value; if it holds a structured
value but not the preimage, and deterministic-encodings is absent or
carries a value the verifier does not recognize or implement, or the
verifier cannot produce the identified encoding of that value
(<xref target="verification"/>); or if it does not implement the hash algorithm
identified by payload-hash-alg (258).</t>
        </dd>
      </dl>
    </section>
    <section anchor="header-param">
      <name>The deterministic-encodings Header Parameter</name>
      <dl>
        <dt>TBD_1:</dt>
        <dd>
          <t>deterministic-encodings. The deterministic encoding with which a
structured value was serialized to create the bytes that were hashed
(preimage) to produce the payload, given as a text string (<xref target="dtrm"/>).</t>
        </dd>
      </dl>
      <t>It extends <xref target="RFC9995"/> by adding one optional member to the
Hash_Envelope_Protected_Header CDDL of <xref target="RFC9995"/> Section 4, alongside the
members for labels 258-260. The extended rule restates the <xref target="RFC9995"/> rule
with that member added:</t>
      <sourcecode type="cddl"><![CDATA[
Hash_Envelope_Protected_Header_With_Encoding = {
    ? &(alg: 1) => int,
    &(payload_hash_alg: 258) => int,
    ? &(payload_preimage_content_type: 259) => uint / tstr,
    ? &(payload_location: 260) => tstr,
    ? &(deterministic_encodings: TBD_1) => tstr,
    * (int / tstr) => any
}
]]></sourcecode>
      <t>Label TBD_1 MAY be present in the protected header and MUST NOT be present
in the unprotected header, following the placement rule <xref target="RFC9995"/> states
for labels 258 through 260. When label TBD_1 is present,
preimage-content-type (259) MUST also be present (<xref target="consistency"/>). A
producer MUST NOT list label TBD_1 in the crit header parameter
(<xref target="RFC9052"/> Section 3.1), so that a verifier that implements only
<xref target="RFC9995"/> can ignore it.</t>
      <section anchor="dtrm">
        <name>The Value "dtrm"</name>
        <t>This document defines one value of deterministic-encodings, for CBOR
content: the text string "dtrm". It states that the structured value was
encoded under the Core Deterministic Encoding Requirements of <xref target="RFC8949"/>
Section 4.2.1. The name "dtrm" is the one <xref target="I-D.ietf-cbor-serialization"/>
(Section 8) gives to its deterministic serialization (Section 5), which is
<xref target="RFC8949"/> Section 4.2.1 except for NaNs: "dtrm" excludes non-trivial NaNs,
as the CBOR working group defines it (Sections 4.1 and 5.1, and
Appendix B.5, of <xref target="I-D.ietf-cbor-serialization"/>). For a CBOR sequence <xref target="RFC8742"/>, each data item is
encoded according to these requirements. Apart from that rule for NaNs, the
choices that <xref target="RFC8949"/> Section 4.2.2 leaves to a protocol are not part of
"dtrm" (<xref target="security"/>).</t>
      </section>
    </section>
    <section anchor="behavior">
      <name>Producer and Verifier Behavior</name>
      <section anchor="producers">
        <name>Producers</name>
        <t>When a producer creates the preimage by applying a deterministic encoding to
a structured value, it SHOULD include deterministic-encodings, so that a
verifier holding only the structured value can re-create the preimage. When
present, the value MUST identify the encoding actually applied. A producer
that serializes a structured value without a deterministic encoding, or
whose preimage is not the serialization of a structured value -- for
example application/octet-stream content, an image, or an archive -- has no
encoding to identify, and the parameter is absent; the content binding can
then be checked only from the preimage bytes.</t>
      </section>
      <section anchor="consistency">
        <name>Consistency with preimage-content-type</name>
        <t>The Applicable Content Types of "dtrm" are application/cbor,
application/cbor-seq, application/cose, application/cose-key,
application/cose-key-set, application/cose-x509, application/cwt, and
application/multipart-core, and media types with
the +cbor, +cbor-seq, +cose, +cwt, or +sd-cwt structured syntax suffix. When
deterministic-encodings is present, preimage-content-type (259) MUST also
be present, and its value MUST match one of the Applicable Content Types of
the encoding that deterministic-encodings identifies:</t>
        <ul spacing="normal">
          <li>
            <t>A 259 value that is a media-type name matches when its type and subtype --
with any parameters removed, and compared case-insensitively (<xref target="RFC6838"/>
Section 4.2) -- equal a listed media type, or when its subtype ends in a
listed structured syntax suffix (<xref target="RFC6838"/> Section 4.2.8).</t>
          </li>
          <li>
            <t>A 259 value that is a Content-Format number matches when the CoAP
Content-Formats registry (<xref target="RFC7252"/> Section 12.3) assigns that number to
a matching media type with no content coding.</t>
          </li>
        </ul>
        <t>A producer MUST NOT emit a Hash Envelope that violates these rules -- for
example, one pairing "dtrm" with application/json. A verifier
that finds deterministic-encodings present with preimage-content-type
(259) absent, or with a 259 value that does not match the Applicable Content
Types of an encoding the verifier recognizes, MUST report the content
binding as failed, without attempting recomputation. This check comes
first, and takes precedence over <xref target="verification"/>. This outcome applies only
to Hash Envelopes that carry deterministic-encodings; a verifier that
implements only <xref target="RFC9995"/> ignores the parameter, and its results are
unchanged.</t>
      </section>
      <section anchor="verification">
        <name>Verifying the Content Binding</name>
        <t>A verifier that holds the preimage itself -- for example, as retrieved from
payload-location (260) -- checks the content binding as <xref target="RFC9995"/>
Section 5.3 describes: it checks whether the digest of the preimage, produced
with the hash algorithm identified by payload-hash-alg (258), matches the
payload. That check needs no encoding information, and applies whether or not deterministic-encodings
is present, subject to <xref target="consistency"/>.</t>
        <t>A verifier that holds only a structured value -- for example, content it
received, stored, or decoded in a form other than the preimage itself --
has to re-create the preimage by encoding that value, and needs
deterministic-encodings to do so. Such a verifier MUST encode the value
with the encoding that deterministic-encodings identifies, and MUST NOT infer the encoding
from preimage-content-type (259) or from the structure of the value. If
deterministic-encodings is absent, or carries a value the verifier does
not recognize or implement, the verifier cannot re-create the preimage: it
MUST NOT report the content binding as verified, and MUST report it as
unverified rather than as failed. The same applies when the verifier
cannot produce the identified encoding of the structured value -- for
example, when its encoder rejects a NaN that "dtrm" excludes (<xref target="dtrm"/>).</t>
        <t>A Hash Envelope produced without this parameter -- including any produced
before the parameter was registered -- is not defective: its content binding
can still be verified from the preimage bytes. Signature validity is
unaffected by any content-binding outcome: a verifier that has not
established the content binding can still validate the signature of the
COSE_Sign1 as specified in <xref target="RFC9052"/>.</t>
      </section>
    </section>
    <section anchor="examples">
      <name>Examples</name>
      <t>These use Extended Diagnostic Notation (<xref target="RFC8610"/> Appendix G), in the
style of <xref target="RFC9995"/> Section 4.1; signature and key material are truncated.</t>
      <t>The structured value <tt>{"b": 2, "a": 1}</tt>, a CBOR map, encoded per the Core
Deterministic Encoding Requirements of <xref target="RFC8949"/> Section 4.2.1 (bytewise
key order, placing "a" before "b"), gives the 7-octet preimage
<tt>a2616101616202</tt>, whose SHA-256 digest is
<tt>a0d3af9e86e5517f729bad0657e2c6f3b7d03899894c8d6b33759074c893b5e3</tt>:</t>
      <artwork><![CDATA[
18([ # COSE_Sign1
  <<{
    / alg                     / 1: -7, # ES256
    / hash algorithm          / 258: -16, # sha-256
    / preimage type           / 259: "application/cbor",
    / deterministic encodings / TBD_1: "dtrm",
  }>>
  / unprotected / {},
  / payload     / h'a0d3af9e...c893b5e3', # digest above
  / signature   / h'...'  # 64 octets, r || s
])
]]></artwork>
      <t><xref target="RFC9393"/> registers application/swid+cbor for Concise Software
Identification (CoSWID) tags but does not require a deterministic encoding of
them, so two producers may serialize the same tag as different byte
sequences. A producer that applies the Core Deterministic Encoding
Requirements before hashing a CoSWID tag sets preimage-content-type (259) to
application/swid+cbor and deterministic-encodings to "dtrm" -- recording
its own choice, not a CoSWID requirement -- so that a
verifier holding the decoded tag knows how to re-create the preimage.</t>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>The preimage is exactly the bytes that the identified encoding produces,
not a rendering of them.</t>
      <t>A deterministic encoding fixes the preimage for a given structured value, so
decoding a preimage and encoding the result again reproduces the preimage
only if decoding preserved that value exactly. Decoding into a programming
language's native types can lose distinctions the encoding depends on -- for
example, between integer and floating-point numbers, or the presence of a
tag. Choices that decide which data item represents a value, such as those
<xref target="RFC8949"/> Section 4.2.2 leaves to each protocol for tags and for integer
versus floating-point values, belong to the structured value, not to
the encoding that deterministic-encodings identifies. A choice that changes only how the same
data item is serialized, such as encoding every floating-point value as binary64, is a different
encoding, not "dtrm". A producer that re-reads stored content before hashing
MUST ensure the preimage it hashes is byte-identical to the encoding's own
output. A verifier that re-creates a preimage from a structured value
(<xref target="verification"/>) needs that value exactly as the producer encoded it;
otherwise its recomputed digest can differ from the payload, and the content
binding is then reported as failed.</t>
    </section>
    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>A digest over deterministically encoded content is a stable function of
that content, so the payload is linkable wherever the content recurs. If the
structured value comes from a low-entropy space, encoding and hashing
candidate values can recover it; this risk already exists wherever
<xref target="RFC9995"/> is used, and identifying the encoding removes an ambiguity that
might have slowed such an attempt.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <section anchor="iana-header">
        <name>COSE Header Parameters</name>
        <t>IANA is requested to register the following entry in the "COSE Header
Parameters" registry, in the "Integer values from 256 to 65535" range,
under the Specification Required policy (<xref target="RFC8126"/> Section 4.6) that
governs that range:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Label</th>
              <th align="left">Value Type</th>
              <th align="left">Value Registry</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">deterministic-encodings</td>
              <td align="left">TBD_1</td>
              <td align="left">tstr</td>
              <td align="left">none</td>
              <td align="left">Deterministic encoding applied to create the preimage of a Hash Envelope payload</td>
              <td align="left">This document</td>
            </tr>
          </tbody>
        </table>
        <t>The suggested value for TBD_1 is 271, the lowest unassigned value in the
"Integer values from 256 to 65535" range of the COSE Header Parameters
registry as of 2026-11-14.</t>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC6838">
          <front>
            <title>Media Type Specifications and Registration Procedures</title>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <author fullname="T. Hansen" initials="T." surname="Hansen"/>
            <date month="January" year="2013"/>
            <abstract>
              <t>This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="13"/>
          <seriesInfo name="RFC" value="6838"/>
          <seriesInfo name="DOI" value="10.17487/RFC6838"/>
        </reference>
        <reference anchor="RFC7252">
          <front>
            <title>The Constrained Application Protocol (CoAP)</title>
            <author fullname="Z. Shelby" initials="Z." surname="Shelby"/>
            <author fullname="K. Hartke" initials="K." surname="Hartke"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="June" year="2014"/>
            <abstract>
              <t>The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.</t>
              <t>CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7252"/>
          <seriesInfo name="DOI" value="10.17487/RFC7252"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8610">
          <front>
            <title>Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures</title>
            <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
            <author fullname="C. Vigano" initials="C." surname="Vigano"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="June" year="2019"/>
            <abstract>
              <t>This document proposes a notational convention to express Concise Binary Object Representation (CBOR) data structures (RFC 7049). Its main goal is to provide an easy and unambiguous way to express structures for protocol messages and data formats that use CBOR or JSON.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8610"/>
          <seriesInfo name="DOI" value="10.17487/RFC8610"/>
        </reference>
        <reference anchor="RFC8742">
          <front>
            <title>Concise Binary Object Representation (CBOR) Sequences</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="February" year="2020"/>
            <abstract>
              <t>This document describes the Concise Binary Object Representation (CBOR) Sequence format and associated media type "application/cbor-seq". A CBOR Sequence consists of any number of encoded CBOR data items, simply concatenated in sequence.</t>
              <t>Structured syntax suffixes for media types allow other media types to build on them and make it explicit that they are built on an existing media type as their foundation. This specification defines and registers "+cbor-seq" as a structured syntax suffix for CBOR Sequences.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8742"/>
          <seriesInfo name="DOI" value="10.17487/RFC8742"/>
        </reference>
        <reference anchor="RFC8949">
          <front>
            <title>Concise Binary Object Representation (CBOR)</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.</t>
              <t>This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="94"/>
          <seriesInfo name="RFC" value="8949"/>
          <seriesInfo name="DOI" value="10.17487/RFC8949"/>
        </reference>
        <reference anchor="RFC9052">
          <front>
            <title>CBOR Object Signing and Encryption (COSE): Structures and Process</title>
            <author fullname="J. Schaad" initials="J." surname="Schaad"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.</t>
              <t>This document, along with RFC 9053, obsoletes RFC 8152.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="96"/>
          <seriesInfo name="RFC" value="9052"/>
          <seriesInfo name="DOI" value="10.17487/RFC9052"/>
        </reference>
        <reference anchor="RFC9995">
          <front>
            <title>CBOR Object Signing and Encryption (COSE) Hash Envelope</title>
            <author fullname="O. Steele" initials="O." surname="Steele"/>
            <author fullname="S. Lasker" initials="S." surname="Lasker"/>
            <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
            <date month="July" year="2026"/>
            <abstract>
              <t>This document defines new CBOR Object Signing and Encryption (COSE) header parameters for signaling a payload as an output of a hash function. This mechanism enables faster validation, as access to the original payload is not required for signature validation. Additionally, hints of the hashed payload's content format and availability are defined, providing references to optional discovery mechanisms that can help to find the original payload content.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9995"/>
          <seriesInfo name="DOI" value="10.17487/RFC9995"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC9393">
          <front>
            <title>Concise Software Identification Tags</title>
            <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
            <author fullname="J. Fitzgerald-McKay" initials="J." surname="Fitzgerald-McKay"/>
            <author fullname="C. Schmidt" initials="C." surname="Schmidt"/>
            <author fullname="D. Waltermire" initials="D." surname="Waltermire"/>
            <date month="June" year="2023"/>
            <abstract>
              <t>ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an extensible XML-based structure to identify and describe individual software components, patches, and installation bundles. SWID tag representations can be too large for devices with network and storage constraints. This document defines a concise representation of SWID tags: Concise SWID (CoSWID) tags. CoSWID supports a set of semantics and features that are similar to those for SWID tags, as well as new semantics that allow CoSWIDs to describe additional types of information, all in a more memory-efficient format.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9393"/>
          <seriesInfo name="DOI" value="10.17487/RFC9393"/>
        </reference>
        <reference anchor="I-D.ietf-cbor-serialization">
          <front>
            <title>CBOR Serialization and Determinism</title>
            <author fullname="Laurence Lundblade" initials="L." surname="Lundblade">
              <organization>Security Theory LLC</organization>
            </author>
            <date day="30" month="October" year="2026"/>
            <abstract>
              <t>   RFC 8949 defines CBOR, a standard for serializing data types such as
   integers, strings, and arrays into encoded bytes.  CBOR serialization
   is flexible, allowing data types to be encoded in multiple ways to
   accommodate deployment in constrained environments.  This document
   normatively defines one particular serialization, called "preferred-
   plus serialization," that is suitable for the majority of CBOR-based
   protocols.  Protocol designers and implementers who choose it need
   not understand or specify serialization details themselves.  This
   document also normatively defines a deterministic serialization.
   These serializations are largely compatible with those widely
   implemented by the CBOR community.

   This document updates RFC 8949 with a new rule that limits how new
   tag definitions can affect the CBOR data model.

   This document provides clarifications to RFC 8949 regarding bignums
   and floating-point NaN handling, along with general background
   information on serialization, determinism, and CBOR byte-string
   wrapping.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-cbor-serialization-12"/>
        </reference>
        <reference anchor="DAG-CBOR" target="https://ipld.io/specs/codecs/dag-cbor/spec/">
          <front>
            <title>Specification: DAG-CBOR</title>
            <author>
              <organization>IPLD</organization>
            </author>
            <date year="2026"/>
          </front>
        </reference>
      </references>
    </references>
    <?line 392?>

<section removeInRFC="true" anchor="changes-from-version-00">
      <name>Changes from Version 00</name>
      <ul spacing="normal">
        <li>
          <t>The "COSE Deterministic Encodings" registry is removed. This document
requests only the registration of the header parameter (<xref target="iana"/>).</t>
        </li>
        <li>
          <t>The value of deterministic-encodings is the text string "dtrm"
(<xref target="dtrm"/>), the name <xref target="I-D.ietf-cbor-serialization"/> gives to its
deterministic serialization. Version 00 used the integer 1, the value its
registry assigned to core-deterministic. A verifier of this version
handles the integer 1 as a value it does not recognize
(<xref target="verification"/>).</t>
        </li>
        <li>
          <t>"dtrm" excludes non-trivial NaNs, as <xref target="I-D.ietf-cbor-serialization"/>
defines. In version 00, value 1 was <xref target="RFC8949"/> Section 4.2.1 without
that exclusion.</t>
        </li>
        <li>
          <t>The Applicable Content Types, which version 00 put in the registry
entry, are listed in <xref target="consistency"/>.</t>
        </li>
        <li>
          <t>A verifier that cannot produce the identified encoding of a structured
value reports the content binding as unverified (<xref target="verification"/>).</t>
        </li>
      </ul>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors thank Amaury Chamayou for a detailed review that aligned this
document's terminology, CDDL, and verification rules with <xref target="RFC9995"/> and
proposed the name core-deterministic, and Henk Birkholz for a review of its
scope, motivation, and terminology.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA81cbXPbRpL+Pr9iSq7aWBuSEiVLsuR9k1+y8VVi+ywnqau9
LXkIDCmsQIALgJK5sva339PdM4MBSErJ3ZdL7SYUOK/93k83OBwOVZM1uT3T
O69tY6t5VmR1kyX6TZGUaVbMaj0tK/3q/cWbHWUmk8reYCj9qbeM31FpmRRm
jiXTykyb4Ty7GtbldZmXN8OkrO0wjScOrZ843B+r1DSYd7B/cDwcj4fjI5Xg
waysVme6blJVLyfzrK6zsmhWCwx8++bTdypbVGe6qZZ1c7C/f7p/oExlDQ55
YZNllTWrHXVbVtezqlwu3NF31LVd4WF6pvSQ70b/vTL1lbbFjc3LhaUHi8pm
czPjz4kpyiJLTJ79yzTYn5517qH9PVTdmCK9NHlZ4IQrW6tFdqbvmjI500U5
0HVZNZWd1vwd/lzNw1/3Spllc1VWfK6swNOLkf4xu1JaayHpRWNvbOGfldXM
FO5EZ/o8of9iCGim/0r3Hei3RTKikXZushxEXNjkL4bH1TRsZLKw1flIXwib
2u3Oi4ZWbB93d/y0Sq4s9gABmmVjo40MTRw5tv+loXGjLIxTRVnNscaNxU31
x+9eHYzHp+7j8/HJM/fx+Pnhc/fx5ODoIAw4OPYfj8f7/uPJszDg9Jlf7HQ/
TDs9PT06Uyorpr29Tw9PD+nj2+HrUWab6TCZlNWwtlUWuE1fvz7/6/DVy/cf
6bPWXmkuQNBsCsEQgvhBOzLIVDPbnOmrplnUZ3t72SJPR1m5R1yo9yAu9J/U
zHhHfrrH81ot4D+DTPA/wx4P3n744bVSw+FQm0ndVGCuUucs1Pp7kug3TqJ1
nc2KWjdgWJrNbN3ocqpNEPIBhLPhb4PYZ01t8+lI/3IFiYu/0Zms40VeVsLm
y6RZVjbVNyZfYsV6mVxpU2ujiCZ0LaOzxs4HEI8UM25A42lmK31V5iktaRqZ
qifLJpxnsmqs+/LWVlaRntp0wN+1K2CbppQTWfmKFzIzkxWyX3Rz8B8CWauy
yFc6m+JQ2iwWeWblXjVkf4t203WEFGW6TGw1IgnSJHGYUCdVNsEa87KiM5hC
wwYIFcJ8sqZ+D5XAkNkC14Q1aw8ZyBx/rdMSKxNNshTPsulK315lWJm2uDW1
kgukI/3pCuyBDV7OaW5qp1mBmWaTSOAWjU0amw6vrEltpRamwrlwcaG328rT
xV9CjkobC5HZQxCH3YGZN6qxXxoSCrr1TtpU852BOzKbHsdSWvcV0WuzO1Ef
7T+XWWXpLjXJWSA3yYL2lxYFAHXs5Tv6V1NefuQb1Uq9LdLsJkuXJtet/xjA
5uGoKYTVc4Tp8wtcBR2Yzad+Sv7qL2QURlC6XWxzUS6rxLo5EZ1xtayBsGsY
cxyswBg7zxqiJNEqyCnzGCKobkD3soIDwCKmUX/7+1NvJWZYaDkZJeV8Tyz1
kOk1ZA+295AH3XV0mGdpmsPKPoFpblhQ2THcPcnoT3iZT/66XXG4u3N28v7+
EWtB91A96WD/aXJ4a1xgrp8eHD3fFS3tyDHW6Qg5xp3uDhRL1ILOafKcZNtW
tqcN0KeJBYEhUnCCKWYe7++O9HlLXZIo5Y1JbyoUPrluZa69VQbmOXVOhYv+
Nqq9TbhrCnukF2aVlwZag0FDDPKXdXZFNpcx0JVaxYRFWMLcOBodtiaDtBYH
kzMW1qak6jr4KgyfVuWcRU61Ikc0Azlg4UhkN1noOpsvcrrnrVmRfZyba3zX
qEUJLZjkdiSy0BWDxFSVZ6qQad058ObK0yEvxQEKS2hzz0q6WCQAxNUpaTtC
NKaUUZ55AzLEoAHYP5Dblsumzpw175yQlBcSYigWqkgXwZ/GWUB3EDAUOk8B
lpgcJzzrXkpXhk4l5jq4GxXcjRZ3070HrUZEurHs3lrPRpEUHdnonHy/mEU1
t3XtaaaXBRgixHXP9W1lFs4cukWwAJ3DmU8IVgke8lqIGUqya3QGYgr4v6wK
ur9zfqlzmE/v7h6IaO7v1fliAQOYJRj7/WjMZ/uP0ZgVql7VdA6+Zl6XOEbp
tNFTgI6I7UE5VVkIRY2HQnnYH7KO9osh0RsQyctpc4ugHJMQu2Kpldz12lpc
+1VZJFltYVndqLdO1bxIvSovfnn7ehfRFJIR0SREbNAkkL4CNSooC1OMuDAx
WApHiLlK+9AxMBZ3TMrFitSeBFDI7Vz6tjjDiVIqX/Vuy39UN5jI67WCgPsn
Tb5SYEPtEpH7exD3U+m0nMMCT04OU+qG2dgTdXKlvzbMYQ6BAqIfkHv1iBDE
1ggyUJtVvS2tmYB8cwpBbEJiCyaSxJDLdUSDtrHPYAMPEwA/iiCvIouPO+LW
8FxQsRICQ7ZWaFVn/7KDQEV8yG5MshogxoV2WNhnZqMsTdSiCBdeDAaT0zYa
E8VsZDlZ+oiO5S0yl2x2GTTe2QIlhnFWeHccx5HMRdkHk7rGoTJFPSdvAQ8w
zb4QUa7KW7l82ISMn1fEpyKtyEFaStf62egZ73sKafgOZzXMcRUFZd7E3hLJ
ut6TDhvbOVAVY2Dm2J3jVLBdRRm4Bvv+0YYAgYWXHV3PP/o4uEOKKCJWYYU4
9vXRl9g1vitFZrjrllB4pLy4PRsdkLghFcYQs4CKQvBIAW9hCphPudXx4ENn
LegwuS1mzdVwmlXkwCtYQx9UWFPlmbO6nOu2ZoSkgsLdMilzJ7AkLQraNCEa
zxcYB4/oIwDjlj7Tn+/G+/v7Z3o80DtmB3nZ/WcwWX02B3p8qvcPtX2u98f6
mP+3f/AZFj61ElKSa3JSRsP9kHjeZ9UOzw0FjOJqPG+Gjv1DZj8HS5ybCwfj
iCoE3y7tiv3hXn2bpd+SBWhdeZvSCBvJsJB0w96bXkg1W0Lle0mAd0CNzXNM
mOMhh0cuJWAHXtigC3JLozCKA2To1tLFH5vSFZraz050yE4GaksE7N19JzQF
Kx/IXNRa5qI3ZS70PKzqEgaaeOsSBo7OlT8+SVvXjnYML1kGWpc9wttGLwNx
v+AUNTuWMpOAac06OKJoRxSTI5ZKVyHiobWD5riMSULPM/X59/opLbunG1xv
V//xT6DH6vOuiFzgbCaJpsSBqYQ4c5tmhoUwShKx+gNyKqvGUkgCKCu5nNaR
qyjbRWtnNp0p8Vc5HR3usmyKdLeyAA4sc1DDwH2wMsO/zEBzWzlfQEHiKt51
g/CTV/WoxKvy/IN65W7zHQfguljOJ9jKR8ZsLyXID6cm25uS4yXfI0eoVjCc
+Le7EWFY0Y3GB/5K7HQWJqsclhKdlY4UXLDclCMy9nTey8npKHCDEEzJdLLQ
U7Dgh7RLin1QxNSIMzdFOmJ4ysNRsOcezLq/lyzVCVo3FQKjXwQcIzcTWAMS
mR7T2aFLhlzEX34jp+OrPmK2RChdwlInpTd8sfXA5358X7cwVBeEqiXn5CRn
Y8TjTIdXXJab+Uj/yJSMLI4nZ8PemhJK0odaxGmyzCgbxdMQBbNprAVH4DCO
Y6Ql5aKK7/WiGxviUhwxkjjTVGIpx6qUWuotqaVqU0vCAT7x/cq8nK303ZOm
/cuBAfC/ZMlw0p0ff7r4BHvH/9Xv3vPnj2/+86e3H9+8ps8X35//8EP4ICMU
/nj/0w/ue/rUznz1/scf37x7LZPxVPce/Xj+XzuSTe68//Dp7ft35z/skBp1
OUs0EldNuE0Fq9OIZfL3ZNV7+eqDHj+TdJsgZdBEbMn45Bk+317ZwnsAwRgk
Zl6RSCJ24DQC3iwxi6yBmnHuXl+RhFLiCkpK+WAgZYRLRJfFWA6vd/qGeYfP
LBaODxcFgy+w0OvXck854PF4H4/1Tif43/Eri4lthwu/R+q87j0axNCDQDbd
3D7jdNUl9U7+VQw41lCC2ocUvZTI5cLECBcDQhhHGxAEtgN1j4VeFQomzMHR
c/20j6PsDhTsCZ5vciq7cuCD4/12ogcedtcCCbaSwa9OyzwvbzmAhezXZ0pd
9OzEmTojJImjAjZULGcFgYZt/hAAbd0HtJlGRultsHGwIpy/JbCkjY3wNBzf
eRw9QdqEGXQegRwqJEcLZK4MKk5sc2tt0SaOfRCd6gBRCkH5BU61hnrQMA83
b5WWdWxNiykiCiTd81JuweE8BVcsPpVls8ZZ45lfB8nC1MBDpQNFxSSEhf4L
kOBn99HfvcXoutDTlYUbxOQKAsKUdJZxQw0Cu2zG9vRvxPaw0GZ0r59BTssl
58UQIKdOYNxKLJqV43QDOAQH0UAKCZX6jmnk6dBb2+Vg3VWi3Zr1JUkQsHfz
/4+ooazB1I1pCzL8FKSDSPHOZpyN+2eYVjlpiopUjzPCEeJxRgzEgjksVYAV
LhaxqmGZwp2ok0wXnNP3ifYintr5HuusF706OKveku2wNZ8QGCXs9eGpcQt2
yBEITZjZrKCAhoASAukETZYyCJ3GT3EZnrf1nRQo7VT/2tId5oOOskTiUKbd
F7wV378tY/mdN0gPFvk18iOhTT+Ai+jzvTD2Q8gV7p4Ir4ccuFPw8/L1f1+O
Sbq2rDFa36C9OQu/ZJwbrewtfEWw/Glk+bc7V6KfZ/5u7Gk7VmeWURcAe6I4
WY3SSqWQV3I6mXaDRFDTpMI3stQOp0eCwBkONiQhIDdw6d3A5QevKZeOoBS8
ENs3BZ/PILJ5Cco56F7JypITu8AAzBvCj7u084srxBEgAOkM1cFuQYq+VS04
486Lq5BxUP/+9791kqb5Iye//AULXPriov6jvuOq+p/1755Cqs70mHNiuP4B
P/+dDzQuiTmXPIQErzPoz9Ewz7lL5x0vpU+FURvMWbbJ9/pcH8ucaS6iYHh3
XEcGL4OAwkW8fH057k3YmOire6KTUj8QF7SIvkb8TWG1Q7Wdn9oAM8AM+ZQg
Gq/c+GXRnzGIgy5aMTeJ6DvzuVNrZI6rroBQBFEuZ1eaBYXNex6fG7bPnWGg
HgLL+NAcDUa3XPe5+lwFXDPcM8eA3q5yXaQcje6jUmoT3qsPR2PJ8iVE7AZU
rRUUUKFTKaTyCzIMQlApzFZPxNj9zKZFcCkYNFb4h2A0MUXQ1q2Yma/f+zz+
bAsKxlhVv3i/yeipLur3SI1f92v8Ef7TRYzFYBD86e/vfDPd87F611O/FPSX
7GctgGe/4NED6kJOvRuwRVfP7QFUAmnbL4ldNEzRd+YdlNOdE8/zZcqurxiC
pjfYg0cMlCs/raOJgYuQtadR+UBqdUejsaTNro73Rb8cHQ2EfA8SIpQdBCUH
7TmzkDudPDugLLJXzMpajpqEKm6s1OwqajLZLfugR9CHxperjdN2Tw8pZyVX
ZZZ4GdpGywOdW+O4ZAJ0z7kjByW0SzlVjr69MhsFBh9CmQLU+tlr3Ut7ZW4y
wreeTNzHe1YtPxze8om3BNSRx5bHtEUP8eC9AsqEIYR8xYjitmihKdWmLilw
12EmCFRJSLYrarAiqpP1iTN3kOSaPpIZCUF959hiVpU3o1E9kS1gaDTqAqZY
nFs0QsPReSCO6iJm9aZ6O7lwQru2kYlTFal8xd0MPjDuqufGxjNXglauBN0B
I0t4qGaIGdbMW9CfDG2bLxNAkVxRcX/IXaEET0dMDHSJOrZCgBki8hedcrlP
ksELKj9yL4IH9ZhzTl86ItUIePeESuQhfeEIaLO/u3sS+zQB9s7l7lTY8gDD
J4xlM+tUx1TrIP1A9Z/Aivxz0B1XUqmu/2R4bVe92e4pVmg2jP9ytH/ae3wr
2FRnlfkybzJSety5cmlRC2rXTBeu7Dq4+Nv20N/KSb/ldcHgb+t0iM+x3NSr
ojFfdL2cTrMvTi0eSLqCxvyqwEO1gYecm5xOpGeS+Qbc5EGmqY4uurr7lnOG
Ghji499DSwla84mhaQQKbMs64lY9xkHYKJ8zVCHq5YQ/D4cIMB2Uv4oLIPAA
5Y2vBnNBlShLWfMwK2oqa1HTbe6rIdTcC6+sY6O/SxoHb2KookjBl007lQsq
IviD+fNwgkPALZZyU7YxtrNzx9lwLrmNRptrQR1KSYRz/gFn6I5uS0EPFIGQ
yPl2u3Z9eAtNDKJtiNdRUYipX5RtO5Kv9beWuI1hqQ1xDQaWfD0rc+/KyI3D
Udc92zmQQqwrTTmDIcyPdPMfdVnEWKG4AcQuab1VOn0kvt2eKVEjMadRAanP
ow0I0roCqWD1YN473QzBkwZcBI6WqSeIZmzHlbfjcAoOxmz9WYNICdk0Q6Ek
/ktpEXINudL0w2Co4s4F5z3MtWViJFYA3pJa2voAilvDoamhZskZAxxSh7dO
iggLWm2j/ou1Cn8vD+mkZ5KD1F1P11oyfAXbXJMfUcsiuTLFjNFcOC6Oulae
0t6WvXREvHvSuSWJbzc52tDJKT3p601mddQXSr50W2siJjoEe5N77tbT1MZW
zTMK2Nwa0P2A/23DVT1Sqv5PSGkMPvu7bW4abav4bfeoK207sfGnBgFJbbbI
iIr9HIztP0AMin56mfNoG9tYjLYGZy3rQpmzUaQFGbsQbjhMWeml4TGVFj/u
9Sy7DZvrsqFcm9zmqJeo3PWgLhDnfjYi41bXjzXTElH4SF9IF0K4OBuMflte
y/Lf6rEHXbwFrHRSFnoBOGB8KPwgbNwHlW13mhNPPh7S+elDUU5keR9FltVD
yHJndOhb3cQbUi4Vrr1ugGNNbStKgVZuAjm8WrWlpU4bXzDdAiZw32CkGd0i
gvotEPiG3KvvTUP0IqJCTof0igiL9Fiko48YdEDd8/U3ONo6DLkhrli0+chw
6LJKJlqxas3RRBqxu+nLrfEBC7fP0OzaGYkpGcMb5lDdZweRCZfP8pwSm0D2
bUkNtWUWhuURZMpSJO0EMSwLM50KhEj5NA7rxdpz3TnAszUYTbK0RhF4PEEU
yFXqzfmXOydv7MWvDucRRqq2vE/y4joJ18r4DDO8Ed4SbODYXEvuhZBqif+/
8fD268zAkXKu+65sQh9YqP7rAOT8dXfg64V1s8rtVqh9NH4RnZ3UgBo5YPM5
SZamiQo+map5vnOmL6Kf73Ym1NXouhvH958HHhuam8UgNPAtIiBP/XYgr4eT
PfXNnvQqpnRaDhgi5jjT7Ggnnjjb7sDDddj9ZMgZfPuS2mdzcDwG/fD/44P9
g8++a/bi+/PhwdGxd8vcsLmfHprpqX1+bI+OxifTk4PTiUn3j49O7EFyPD2c
nKT7h89PT3Hg5Hl6PDk8PDk63T/BH6eHkyN7+FnqDGr8/Onf9BPdyggC9T/8
QSoJe+TY9aZ/9vT4TA9PBpj55gInc8N7wUA0HH4fE8bHNKO+MsN2TlAnNvfd
OadnIF8vd98ZuInbGp32pIbg0Uoafv+nPymaEgP7e/rufsBPfc+Au8M3nrSj
0chT6xs6t6O+mSCs5YmttMpETPhGY+DxM82Mheer9NevulZ/35ViRdzx701T
t3ctNIkJkC3vE2j/PoF68H0CqrlGlVEW3+0InuTfcwHibkNtrqIm5lW3U0wc
C/bgJqXQ9EpirzzmWsfYmUP2otcQf/VrcU5XSJQEgJQr8u41Ncg/FCcQKrmR
mA8VnhEIOTdF71pYBwkr320oAK+0GofTRDAxzXoAy5SePDE7dIfrorytNffa
bwvq2BT7N74FMINJMQKZ3z0J2LAYwRhYdC9q9Euy2zy9b6AfKLlcRca9amOA
OTvpLfLD/fldjzhlKF7quRveoC3lhR9ha/z2XTeJlRxMXgPZ1uUf3nYNK/rX
LtIoDPb0GEHyQiLhIfgZ4oQ5MTpHkrfEmt9AcfhdaofCkX/NyfymdPPClSw6
EXBqFwzZhFeF2ujINzdR69XMAfdT2BlKqofSEC3gSO27FVyGkrCLNArCMtKv
4uoC7kp1aKnctAWN8BZPCGnb5i7u49xa4onLEtK36ysT/E4o2RQ+NkXAcg2S
73pZ92/iu1MnlqrlrpqyQQQY+C7/V7gfmRdRRYcJcG7uUjN5dcW9iByXeqKO
hZYoYWvppt50FxqGOMtUq+NnA99o6OxewM/lPr6c2Ld+0G3qMa5d/teGbx0D
p1yyVS/7r4hmjXRRcPpCyjwUYiQIhhyB/UGk81gholwsm7VGt9bK1LHebWmI
UusdLy4fX9er/gvkIb7KmheKM1uKihywIjASvnR+lNRLaBrF1v1OtD5WJSXS
wiVH0jXrMiApk/ErV+s2072LxbiMBzdubO+9Bq4E+StEHctEJMbfpkuxAuI7
SQjDayplfH6alGfFNU/it39vXMDpV63IhteUtLrIuF/n4tfTHIvy8nZIvff0
sl+9MOSM2gpWkQZRAkVTyQNEH121LOGbZlzFwcGqrL4O/e/2C7fI+jN2SvYY
i5jfMcPXibyRjl7DIqS85krTfJLNluSzGIabZ7OrRt5lqHEFArBZAQsPLzLL
3p6/O1/nV2YKI6VMebW71/vkh7iXaTCSl6HbUTjCwDm7Vwmx+MRtB4e8x+C6
H3aiDVS7wU7Augdh5Ftnyh11mTsUlmOn46OjwyPMIZs0iN6C6vykhk8pkH+U
iFE8ik6/AdIxzMe7QsAZMc4j6bw0gvavSK4RjH3V0vjy1bVQECQc/vjoYfqv
cHwE9XFjFP76GF7o/4qF6PX6R/6NUdtM81ffRvKV+3Lwn4Lw9a+9KG/Tm1mb
gKwN/d1em772fgbiq8v+lrOZsLr95Ya2n+bgZCxgDYke1B0JORcmwnCXlP5a
rnpYZLM8qlAZMZwshl/9eeZ+xmBikmsS91fObfE2P2MmMWZ/X92diSJlRTVN
7ql+8ykI57YfJ2rLMVmoWPV+MgN5itOI6EUfNy1UnRnH7fX/kGyyEt5LNenT
1ePNN76BZb3ZRhopHfIjbOEK3WNv9MatLWv96J3Bo4iYbLYk6HW8Hcf9ALJW
xDAnFiSY8MzdH6ToeFP/js6NbIVVwM00d7Fp2Ex6Gf1mG5pVN/aVMpkf7bAR
WP/h5iDtm23gXwp/WNBl4M40ZmhsO57h4DduLab3DekwtEQQhG01Xd9V1G6p
4fK9/QzvkWmxwAPGdFyZk8GoPhj/+7VQ5tdDmBu7kn1f/xYUNkJZN/LniT5P
KH9DuDHjbBVqK0G8Tf+4MzV5bXdcVia/c8S2u7jW53OzhKhB+ZFbl0uXKKX0
cxf0hhl8b2bdy9dgpEhj/PMYCPCi95wG3LM6iH6MxfkXqXoyUB87cv51C0QP
pVcL1r11WZcVv7c48MusukYG+y93UndA/oGRWl7sot9xQLIUlWSiE47U/wDV
YTx/jU0AAA==

-->

</rfc>
