<?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.29 (Ruby 2.6.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-cbor-serialization-13" category="std" consensus="true" submissionType="IETF" updates="8949" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.25.0 -->
  <front>
    <title abbrev="CBOR Serialization">CBOR Serialization and Determinism</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-cbor-serialization-13"/>
    <author initials="L." surname="Lundblade" fullname="Laurence Lundblade">
      <organization>Security Theory LLC</organization>
      <address>
        <email>lgl@securitytheory.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>Applications and Real-Time</area>
    <workgroup>CBOR</workgroup>
    <keyword>cbor</keyword>
    <abstract>
      <?line 112?>

<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.</t>
      <t>This document introduces the term “general serialization” for the full set of encodings permitted by RFC 8949, and formally defines two specific serializations:
preferred-plus serialization, which differs from preferred serialization only in cases rarely encountered in practice and is recommended for broad use;
and deterministic serialization, which likewise differs only in rarely encountered cases from core deterministic encoding defined in RFC 8949.</t>
      <t>This document updates RFC 8949 with a new rule that limits how new tag definitions can affect the CBOR data model.</t>
      <t>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>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-cbor-serialization/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        CBOR Working Group mailing list (<eref target="mailto:cbor@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/cbor/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/cbor/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/cbor-wg/draft-ietf-cbor-serialization"/>.</t>
    </note>
  </front>
  <middle>
    <?line 126?>

<section anchor="Introduction">
      <name>Introduction</name>
      <section anchor="models">
        <name>Information Model, Data Model and Serialization</name>
        <t>To understand CBOR serialization and determinism, it's helpful to distinguish between the general concepts of an information model, a data model, and serialization.
These are broad concepts that can be applied to other serialization schemes like JSON and ASN.1.</t>
        <table anchor="tab-models">
          <name>Information Model, Data Model and Serialization</name>
          <thead>
            <tr>
              <th align="left"> </th>
              <th align="left">Information Model</th>
              <th align="left">Data Model</th>
              <th align="left">Serialization</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Abstraction Level</td>
              <td align="left">Top level; conceptual</td>
              <td align="left">Realization of information in data structures and data types</td>
              <td align="left">Actual bytes encoded for transmission</td>
            </tr>
            <tr>
              <td align="left">Example</td>
              <td align="left">The temperature of something</td>
              <td align="left">A floating-point number representing the temperature</td>
              <td align="left">Encoded CBOR of a floating-point number</td>
            </tr>
            <tr>
              <td align="left">Standards</td>
              <td align="left">e.g., <xref target="UML"/></td>
              <td align="left">CDDL <xref target="RFC8610"/></td>
              <td align="left">CBOR <xref target="RFC8949"/></td>
            </tr>
            <tr>
              <td align="left">Implementation Representation</td>
              <td align="left">Application semantics (names, units, constraints)</td>
              <td align="left">API input to CBOR encoder library, output from CBOR decoder library</td>
              <td align="left">Encoded CBOR in memory or for transmission</td>
            </tr>
          </tbody>
        </table>
        <t>CBOR doesn't provide facilities for information models.
They are mentioned here for completeness and context.</t>
        <t>CBOR defines a palette of basic types, including the usual integers, floating-point numbers, strings, arrays, and maps.
Extended types may be constructed from these basic types.
These basic and extended types are used to construct the data model of a CBOR protocol.
While not required, CDDL may be used to describe the data model of a protocol.</t>
        <t>The types in the data model are serialized per <xref target="RFC8949"/> to create encoded CBOR.</t>
      </section>
      <section anchor="flexible-serialization">
        <name>Flexible Serialization</name>
        <t>CBOR intentionally allows multiple valid serializations of the same data item.
For example, the array [1, 2] can be serialized in more than one way:</t>
        <table anchor="tab-array-ser">
          <name>[1, 2] definite-length and indefinite-length serializations</name>
          <thead>
            <tr>
              <th align="left">Type</th>
              <th align="left">Description</th>
              <th align="left">Encoded Bytes</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Definite-length</td>
              <td align="left">The array length (2) is encoded at the beginning</td>
              <td align="left">0x820102</td>
            </tr>
            <tr>
              <td align="left">Indefinite-length</td>
              <td align="left">The array is terminated by the break byte (0xff)</td>
              <td align="left">0x9f0102ff</td>
            </tr>
          </tbody>
        </table>
        <t>Similar flexibility exists for most other CBOR data types.</t>
        <t>This flexibility is deliberate: CBOR is designed to allow encodings to be selected according to the constraints and requirements of a particular environment.
For example, indefinite-length serialization is suited for streaming large arrays in constrained environments, where the total length is not known in advance.
Conversely, definite-length serialization makes it easier to decode small arrays in constrained environments.
(CBOR is not unique in this regard; compare ASN.1's BER encoding rules.)</t>
        <t>Crucially, CBOR allows — and even expects — that some implementations will not support all serialization variants.
JSON also permits variation (1, 1.0, and 0.1e1 represent the same number), but expects every parser to handle all of it, since the variation is there for human readability rather than for ease of implementation in constrained environments.</t>
        <t>However, CBOR's flexibility introduces two challenges: interoperability and determinism.</t>
        <section anchor="interoperability">
          <name>Interoperability</name>
          <t>The interoperability challenge arises because partial implementations are both permitted and expected.
For example, an encoder may produce an indefinite-length array that is sent to a decoder that supports only definite-length arrays.
Both this encoder and decoder are allowed by <xref target="RFC8949"/>.</t>
          <t>Decoders in particular often support only a subset of serialization forms — typically because handling indefinite lengths is more complex and usually requires dynamic allocation and copying.
This is especially true in C and in Rust’s no_std environments, where resizable strings and arrays aren’t readily available.</t>
          <t>From many years of CBOR deployment, we know that some serialization variants like indefinite-lengths are not commonly used.
This makes it both feasible and beneficial to define a common serialization suitable for general use.</t>
          <t>Protocol specifications can reference this serialization; library implementations can prioritize support for it.</t>
          <t><xref target="PreferredPlusSerialization"/> defines that serialization: preferred-plus serialization.</t>
        </section>
        <section anchor="determinism">
          <name>Determinism</name>
          <t>The determinism challenge arises because there are multiple ways to serialize the same data item.
The example serialization of the array [1,2] above shows this.
This is a problem in some protocols that hash or sign encoded CBOR.</t>
          <t>Many approaches to deterministic serialization are possible, each optimized for different environmental constraints or application requirements.
However, as noted above, some serialization variants like indefinite-lengths are not commonly used.
It is therefore practical to define a single deterministic serialization suitable for general use.</t>
          <t>Protocol specifications can reference this serialization instead of defining their own deterministic encoding rules; library implementations can prioritize support for it.</t>
          <t><xref target="DeterministicSerialization"/> defines that serialization: deterministic serialization.</t>
        </section>
      </section>
      <section anchor="unspecified-serialization">
        <name>Unspecified Serialization</name>
        <t>Many CBOR-based protocols, such as CWT <xref target="RFC8392"/>, state no serialization requirements, which leaves open what an implementation needs to support.
Is a CWT decoder required to accept indefinite-length items, for example?</t>
        <t>One interpretation of <xref target="RFC8949"/> is that, absent any specification, a decoder is expected to accept every serialization variant, so that it can decode anything it receives.
<xref target="RFC8949"/> defines this full set of variants without naming it; this document introduces the name "general serialization" for it in <xref target="GeneralSerialization"/>.</t>
        <t>In practice, however, decoders for CWT and other CBOR-based protocols often omit support for indefinite lengths and other variations because of the added complexity, and encoders accordingly avoid them.
An encoder emitting indefinite lengths would still be fully conforming, yet could fail against such a decoder.
This practice has rarely caused problems, but it means interoperability rests on convention rather than on the specifications themselves.
<xref target="Recommendations"/> addresses this.</t>
      </section>
      <section anchor="relation-to-rfc-8949">
        <name>Relation to RFC 8949</name>
        <section anchor="serialization">
          <name>Serialization</name>
          <t>This document defines new serializations rather than updating those in <xref target="RFC8949"/>.
This approach enables the serialization requirements to be expressed directly in normative <xref target="RFC2119"/> language and to be defined entirely in this document.
This approach provides clarity and simplicity for implementers and the CBOR community over the long term.</t>
          <t>The serializations defined here are formally new, but they differ little in practice from what CBOR libraries already implement.
For example, the shortest-length argument encoding described in <xref section="4.1" sectionFormat="of" target="RFC8949"/> is widely implemented for both encoding and decoding, and is the same as that required by the serializations defined here.
See <xref target="RelationToPreferred"/>.</t>
        </section>
        <section anchor="tags-and-data-models">
          <name>Tags and Data Models</name>
          <t>This document updates <xref target="RFC8949"/> in one way: it limits how new tag definitions can affect data models.
The definitions of tags 2 and 3 (bignums) in <xref section="3.4.3" sectionFormat="of" target="RFC8949"/> modifies the integer type in the CBOR basic generic data model; this is allowed as a one-time exception.
The new rule preserves data model definitions against later modification by unrelated tag definitions, which might undermine their semantics and upset their previous use.</t>
        </section>
      </section>
      <section anchor="conventions-and-definitions">
        <name>Conventions and Definitions</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" 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>
        <?line -18?>

</section>
    </section>
    <section anchor="Recommendations">
      <name>Recommendations Summary</name>
      <section anchor="ProtocolSpecifications">
        <name>Protocol Specifications</name>
        <section anchor="FrameworkProtocols">
          <name>Framework Protocols</name>
          <t>Framework protocols are those that offer options and alternatives, with interoperability depending on the sender and receiver making compatible choices.
These protocols sometimes make use of profiles to define interoperability requirements for specific uses.
Framework protocols are sometimes described as toolbox or building-block protocols, reflecting their role as collections of reusable mechanisms rather than end-to-end protocols.
CWT, COSE, EAT, and CBOR itself are examples of framework protocols.</t>
          <t>It is <bcp14>RECOMMENDED</bcp14> that new CBOR-based framework protocols not impose serialization requirements and include a statement such as:</t>
          <ul empty="true">
            <li>
              <t>This protocol intentionally specifies no serialization requirements so that serialization can be adapted to individual environments.
End-to-end protocols (or profiles) that use this protocol are expected to specify serialization.</t>
            </li>
          </ul>
          <t>It is <bcp14>RECOMMENDED</bcp14> that extant framework protocols that are silent about serialization (e.g., CWT) be interpreted as if they contained this statement.</t>
          <t>Alternatively, new CBOR-based framework protocols <bcp14>MAY</bcp14> impose serialization requirements.
For example, if a protocol is never expected to be deployed in constrained environments where map sorting is too expensive, it may mandate deterministic serialization for all implementations in order to eliminate all serialization variability.</t>
          <t>One scenario in particular calls for deterministic serialization in a framework protocol: a design in which the parties independently construct and serialize the data to be hashed or signed, rather than transmitting those exact bytes.
See <xref target="WhenDeterministic"/>.
For such a design to function correctly, the framework protocol must require deterministic serialization, possibly only for a subset of the protocol.
COSE is an example, elaborated upon in <xref target="COSESerialization"/>.</t>
        </section>
        <section anchor="EndToEndProtocols">
          <name>End-to-End Protocols</name>
          <t>End-to-end protocols are specified such that interoperability is assured when they are implemented in accordance with their specification.
When such a protocol includes optional features, they are typically selected through real-time negotiation.
Such protocols often have formal interoperability compliance programs or organize multi-vendor interop testing events.
TLS, HTTP, and FIDO are examples of end-to-end protocols.</t>
          <t>New end-to-end protocols <bcp14>MUST</bcp14> define a serialization strategy that ensures the sender and receiver use interoperable serialization.</t>
          <t>The primary <bcp14>RECOMMENDED</bcp14> strategy is to normatively require preferred-plus serialization — conformance with <xref target="PreferredPlusEncoding"/> and <xref target="PreferredPlusDecoding"/>.
Requiring deterministic serialization — conformance with <xref target="DeterministicEncoding"/> and <xref target="DeterministicDecoding"/> — is also <bcp14>RECOMMENDED</bcp14> when the protocol is targeted only at environments where map sorting is inexpensive.</t>
          <t>An end-to-end protocol <bcp14>MAY</bcp14> instead define its own specialized serialization (see <xref target="SpecialSerializations"/>).
In such cases, it <bcp14>MUST</bcp14> explicitly specify the permitted serialization behaviors necessary to ensure interoperability.
For example, if a sender is permitted to use indefinite-length serialization, the protocol <bcp14>MUST</bcp14> require that receivers be capable of decoding indefinite-length items.</t>
          <t>As with framework protocols, deterministic serialization may be required for parts of the protocol using hashing or signing.
See <xref target="WhenDeterministic"/>.</t>
          <t>An end-to-end protocol with no serialization requirements is ambiguous.
Implementations of such a protocol <bcp14>SHOULD</bcp14> use preferred-plus serialization unless existing deployments of it have established a different practice.
Implementations that follow neither an established practice nor this recommendation risk failing to interoperate.</t>
        </section>
      </section>
      <section anchor="libraries">
        <name>Libraries</name>
        <t>For the following sections on libraries, implementing preferred-plus serialization means making <xref target="PreferredPlusEncoding"/> the default or primary behavior for encoding and fulfilling <xref target="PreferredPlusDecoding"/> for decoding.
Similarly, implementing deterministic serialization means making <xref target="DeterministicEncoding"/> the default or primary behavior for encoding and fulfilling <xref target="DeterministicDecoding"/> for decoding.</t>
        <section anchor="cbor-libraries">
          <name>CBOR Libraries</name>
          <t>It is <bcp14>RECOMMENDED</bcp14> that CBOR libraries implement preferred-plus serialization.</t>
          <t>Preferred-plus serialization is recommended because it is suitable for the majority of CBOR-based protocols.
Also, in practice, preferred-plus serialization is equivalent to preferred serialization (<xref section="4.1" sectionFormat="of" target="RFC8949"/>) for most use cases.</t>
          <t>It is also <bcp14>RECOMMENDED</bcp14> that CBOR libraries offer deterministic serialization either as a selectable option or as the default, as some protocols (for example, COSE) require it.
Relative to preferred-plus serialization, the only additional requirement for deterministic serialization is that encoded maps be sorted.
This recommendation is stronger for environments in which map sorting is easy to implement (for example, Python, Go, and Ruby).</t>
          <t>Deterministic serialization requirements are a superset of those for preferred-plus; a CBOR library that implements only deterministic serialization therefore satisfies the recommendation for preferred-plus serialization.</t>
          <t>A CBOR library <bcp14>MAY</bcp14> also implement some or all aspects of general serialization (see <xref target="GeneralSerialization"/>) thereby enabling support for protocols that use specialized serializations (see <xref target="SpecialSerializations"/>).</t>
        </section>
        <section anchor="libraries-for-framework-protocols">
          <name>Libraries for Framework Protocols</name>
          <t>When a framework protocol specification does not mandate a specific serialization, libraries for it <bcp14>SHOULD</bcp14> implement preferred-plus serialization.
For example, CWT does not mandate a serialization, so this recommendation applies to CWT libraries.
Alternatively, a framework protocol library <bcp14>MAY</bcp14> implement only deterministic serialization if this aligns with its deployment environment and design goals.
Libraries that implement neither risk failing to interoperate with other implementations of the protocol.</t>
          <t>When a framework protocol mandates serialization requirements, conforming libraries follow them.
For instance, small parts of COSE require deterministic serialization to function correctly.
See <xref target="COSESerialization"/>, which shows how COSE requires deterministic serialization for some parts and, as a framework protocol should, leaves others unconstrained.</t>
        </section>
        <section anchor="libraries-for-end-to-end-protocols">
          <name>Libraries for End-to-End Protocols</name>
          <t>End-to-end protocols are expected to state serialization requirements to ensure interoperability, and conforming libraries follow them.</t>
          <t>If an end-to-end protocol specification does not state serialization requirements, the recommendation in <xref target="EndToEndProtocols"/> applies to libraries for it: implement preferred-plus serialization unless existing deployments have established a different practice.
Libraries that follow neither an established practice nor this recommendation risk failing to interoperate.</t>
        </section>
      </section>
    </section>
    <section anchor="GeneralSerialization">
      <name>General Serialization</name>
      <t>This section assigns the name "general serialization" to the complete set of encodings standardized in <xref section="3" sectionFormat="of" target="RFC8949"/>.
<xref target="RFC8949"/> does not name this set, though it alludes to it in passing as "variant-tolerant decoding".
Any serialization, whether defined in this document or elsewhere, permits only encodings drawn from this set.
General serialization is therefore a superset of them all.
It is described as follows:</t>
      <ul spacing="normal">
        <li>
          <t>CBOR arguments of any length (for example, the integer 0 may be encoded as 0x00, 0x1800, 0x190000, and so on).</t>
        </li>
        <li>
          <t>Floating-point values encoded at any length (for example, 0.0 can be encoded as half-, single-, or double-precision).</t>
        </li>
        <li>
          <t>Both definite- and indefinite-length strings, arrays, and maps.</t>
        </li>
        <li>
          <t>Maps with keys in any order.</t>
        </li>
        <li>
          <t>Bignum representation of values that are also representable using major types 0 and 1 (for example, 0 can be encoded as the bignum 0xc24100).</t>
        </li>
      </ul>
      <t>A decoder claiming to support general serialization <bcp14>MUST</bcp14> accept and decode all the various encodings for the data types it supports.</t>
      <section anchor="default-serialization">
        <name>Default Serialization</name>
        <t><xref target="RFC8949"/> does not explicitly specify default encoding or decoding requirements.
Nothing in it says what a CBOR library needs to support, or what an implementation of a protocol that gives no serialization requirements needs to do.</t>
        <t>Some readers take <xref target="RFC8949"/> to imply that a decoder has to support general serialization and that an encoder is free to use any variant.
This document does not adopt that interpretation, and many implementers have not either.
For example, CWT and COSE decoders typically do not support indefinite lengths, and their encoders do not produce them.</t>
        <t>This document therefore does not treat general serialization, or any other serialization, as a default.
<xref target="ProtocolSpecifications"/> describes how protocol specifications are expected to address serialization, including how to interpret framework and end-to-end protocols that are silent about it.</t>
      </section>
      <section anchor="WhenGeneral">
        <name>When To Use General Serialization</name>
        <t>General serialization is rarely necessary, and support for it is not universal.
Preferred-plus serialization (<xref target="PreferredPlusSerialization"/>) is compact and supports the full CBOR data model (except non-trivial NaNs; see <xref target="NaNBasics"/>), satisfying the vast majority of CBOR use cases.</t>
        <t>The main scenario where general serialization is warranted is a protocol that has to accommodate highly constrained encoders,
at the cost of requiring decoders — assumed to be unconstrained — to support every possible serialization option.</t>
        <t>A protocol that requires general serialization needs to state so explicitly; see Section <xref target="EndToEndProtocols"/>.</t>
        <t>See also special serializations (<xref target="SpecialSerializations"/>), which enable optimization and efficiency for specific use cases without requiring full general serialization support in the decoder.</t>
        <t>CBOR libraries may nonetheless wish to support general serialization, as a complete set of serialization forms, to be useful to a broader range of protocols.</t>
      </section>
    </section>
    <section anchor="PreferredPlusSerialization">
      <name>Preferred-Plus Serialization</name>
      <t>This section defines a serialization named "preferred-plus serialization."</t>
      <t>Preferred-plus serialization specifies how each data type is encoded.
Like the rest of CBOR, it does not specify which data types an implementation supports, nor which range of values it supports for a given type.
An implementation is free to support as much or as little of CBOR as its protocol requires; preferred-plus constrains only the encoding of what it does support.</t>
      <t>For example, a very small CBOR library might support only the integers 0 to 10 and arrays of length 0 to 10.
Preferred-plus allows this, but requires that those arrays be definite-length and that, over this range, the integer value and the array length each be encoded in the initial byte.</t>
      <t>Similarly, preferred-plus places no requirement on the range or precision of floating-point values, but requires that each value it does encode be encoded in exactly one way — for example, 5.9604644775390625E-8 is always encoded as a half-precision subnormal.</t>
      <t>Many protocols use only some data types, and only part of the range of those they use.
Implementers need to ensure that the library they use supports the data types, ranges, and precision their protocol requires, and that its encoding and decoding meet the requirements in this section.
A library intended for general use will typically support most or all data types and values.</t>
      <section anchor="PreferredPlusEncoding">
        <name>Encoder Requirements</name>
        <ol spacing="normal" type="1"><li>
            <t>The shortest form of the CBOR argument (see <xref section="3" sectionFormat="of" target="RFC8949"/>) <bcp14>MUST</bcp14> be used.
This does not apply when the CBOR item is a floating-point value.
The following describes how an argument in each range is encoded.
"ai" is the additional information, the low-order 5 bits of the initial byte.  </t>
            <ul spacing="normal">
              <li>
                <t>0..23 is encoded in the same byte as the major type.</t>
              </li>
              <li>
                <t>24..255 is encoded with one additional byte (ai = 0x18).</t>
              </li>
              <li>
                <t>256..65535 is encoded with two additional bytes (ai = 0x19).</t>
              </li>
              <li>
                <t>65536..4294967295 is encoded with four additional bytes (ai = 0x1a).</t>
              </li>
              <li>
                <t>4294967296..18446744073709551615 is encoded with eight additional bytes (ai = 0x1b).</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Definite-length encoding <bcp14>MUST</bcp14> be used for text and byte strings.</t>
          </li>
          <li>
            <t>Definite-length encoding <bcp14>MUST</bcp14> be used for maps and arrays.</t>
          </li>
          <li>
            <t>Floating-point:  </t>
            <ul spacing="normal">
              <li>
                <t>Values <bcp14>MUST</bcp14> be encoded in the shortest of double, single, or half-precision that represents the value exactly.
For example, 0.0 can always be reduced to half-precision so it <bcp14>MUST</bcp14> be encoded as 0xf90000.
For another example, 0.1 would lose precision if not encoded as double-precision so it <bcp14>MUST</bcp14> be encoded as 0xfb3fb999999999999a.
Subnormal numbers <bcp14>MUST</bcp14> be used where they give the shortest exact encoding.</t>
              </li>
              <li>
                <t>Encoders <bcp14>MUST NOT</bcp14> output any NaN other than the half-precision NaN 0xf97e00 (sign bit clear, most significant significand bit set, all remaining significand bits clear).
When a signaling NaN, a NaN with a non-zero payload, or a NaN with the sign bit set is presented to an application or library for encoding, the encoder <bcp14>MUST</bcp14> either reject it or encode it as 0xf97e00.
Consequently, the floating-point values that can be encoded are the finite numbers, positive and negative infinity, and one NaN.</t>
              </li>
              <li>
                <t>Aside from the requirement allowing only the half-precision quiet NaN, these are the same floating-point requirements as <xref section="4.1" sectionFormat="of" target="RFC8949"/> and also as <xref section="4.2.1" sectionFormat="of" target="RFC8949"/>.</t>
              </li>
              <li>
                <t>Note that this implies that most preferred-plus implementations have to support encoding as single and half-precision.
Specifically, if the numbers presented for encoding are double-precision, then conversion to single and half-precision is required.
If the numbers presented for encoding are only single-precision, then conversion to half-precision is required.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Bignums (tags 2 and 3):  </t>
            <ul spacing="normal">
              <li>
                <t>Leading zeros <bcp14>MUST NOT</bcp14> be encoded.</t>
              </li>
              <li>
                <t>If a value can be encoded using major type 0 or 1, then it <bcp14>MUST</bcp14> be encoded with major type 0 or 1, never as a bignum.</t>
              </li>
            </ul>
          </li>
        </ol>
      </section>
      <section anchor="PreferredPlusDecoding">
        <name>Decoder Requirements</name>
        <t>If a decoder claims to support preferred-plus serialization it <bcp14>MUST</bcp14> meet these requirements for the data types and ranges it has chosen to support.
A preferred-plus decoder <bcp14>MAY</bcp14> accept non-preferred-plus input.
See <xref target="CheckingDecoder"/>.
A decoder <bcp14>SHOULD</bcp14> support the same types and ranges as its corresponding encoder, if it has one.</t>
        <ol spacing="normal" type="1"><li>
            <t>The shortest-form argument <bcp14>MUST</bcp14> be accepted for all major types.</t>
          </li>
          <li>
            <t>If arrays or maps are accepted, definite-length arrays or maps <bcp14>MUST</bcp14> be accepted.</t>
          </li>
          <li>
            <t>If text or byte strings are accepted, definite-length text or byte strings <bcp14>MUST</bcp14> be accepted.</t>
          </li>
          <li>
            <t>If floating-point numbers are accepted, the following apply:  </t>
            <ul spacing="normal">
              <li>
                <t>If the range of double-precision is supported, finite double-, single-, and half-precision values <bcp14>MUST</bcp14> be accepted.</t>
              </li>
              <li>
                <t>If the range of single-precision is supported, finite single- and half-precision values <bcp14>MUST</bcp14> be accepted.</t>
              </li>
              <li>
                <t>Half-precision NaN (0xf97e00), Infinity (0xf97c00), and -Infinity (0xf9fc00) <bcp14>MUST</bcp14> be accepted.
These are the only forms of these values a preferred-plus encoder can produce, so accepting their single- and double-precision forms is allowed, but not required.</t>
              </li>
              <li>
                <t>No requirement is made on how a decoded floating-point value is represented to the layer(s) above the decoder; conversion from double, single, or half-precision into that representation may be necessary.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>If bignums (tags 2 and 3) are accepted, the following apply. (This is a maximally permissive acceptance mode, adopted to compensate for ambiguity in <xref section="3.4.3" sectionFormat="of" target="RFC8949"/>.)  </t>
            <ul spacing="normal">
              <li>
                <t>Bignums described in <xref section="3.4.3" sectionFormat="of" target="RFC8949"/> <bcp14>MUST</bcp14> be accepted. This includes:
                </t>
                <ul spacing="normal">
                  <li>
                    <t>Leading zeros <bcp14>MUST</bcp14> be ignored.</t>
                  </li>
                </ul>
              </li>
              <li>
                <t>For full interoperability, an empty byte string <bcp14>MUST</bcp14> be accepted and treated as the value 0 for a positive bignum and the value -1 for a negative bignum.</t>
              </li>
            </ul>
          </li>
        </ol>
        <t>See  <xref target="BigNumbersDataModel"/> and <xref target="BigNumberStrategies"/> for further background on bignums, <xref target="BigNumbersCDDL"/> for the CDDL specification, and <xref target="CheckingDecoder"/> for overrides to the above decoding rules for serialization-checking decoders.</t>
      </section>
      <section anchor="when-to-use-preferred-plus-serialization">
        <name>When to use preferred-plus serialization</name>
        <t>Preferred-plus is the recommended choice for most protocols.
It can serialize all CBOR data types and value ranges (except non-trivial NaNs), encodes compactly, is straightforward to implement, and is widely supported by CBOR libraries.
It provides strong serialization interoperability because (1) decoders are required to accept all encodings that a preferred-plus encoder is permitted to produce, and (2) the requirements are formally specified.</t>
        <t>Choose a different serialization only when you have a specific need: deterministic serialization when determinism is required, a special serialization with indefinite lengths when streaming is required,
or another special serialization for capabilities beyond what preferred-plus provides (see <xref target="SpecialSerializations"/>).
Note that preferred-plus is equivalent to the deterministic serialization of <xref target="DeterministicSerialization"/> when maps are not in use.</t>
      </section>
      <section anchor="RelationToPreferred">
        <name>Relation To Preferred Serialization</name>
        <t>Preferred-plus serialization is defined to be the long-term replacement for preferred serialization (<xref section="4.1" sectionFormat="of" target="RFC8949"/>).</t>
        <t>The differences are:</t>
        <ul spacing="normal">
          <li>
            <t>Encoders use only definite lengths; this is a requirement, not a preference.</t>
          </li>
          <li>
            <t>Encoders emit only the half-precision quiet NaN.</t>
          </li>
          <li>
            <t>Decoders ignore leading zeros in bignums and accept the empty byte string as zero.</t>
          </li>
        </ul>
        <t>These differences are unlikely to affect real-world implementations and many implementations are already close to conforming.</t>
        <t><xref section="3" sectionFormat="of" target="RFC8949"/> states that in preferred serialization the use of definite-length encoding is a "preference", not a requirement.
Technically that means preferred serialization decoders must support indefinite lengths, but in reality many do not.
Indefinite lengths, particularly for strings, are often not supported because they are more complex to implement than other parts of CBOR.
Because of this, the implementation of most CBOR protocols use only definite lengths.</t>
        <t>Further, much of the CBOR community didn't notice the use of the word "preference" and realize its implications for decoder implementations.
It was somewhat assumed that preferred serialization didn't allow indefinite lengths.
That preferred serialization decoders are technically required to support indefinite lengths wasn't noticed by many implementers until several years after the publication of <xref target="RFC8949"/>.</t>
        <t>Briefly stated, the reason that the divergence on NaNs is not of consequence in the real world, is that their non-trivial forms are used extremely rarely and support for them in programming environments and CBOR libraries is unreliable.
See <xref target="NaNCompatibility"/> for a detailed discussion.</t>
        <t>Thus preferred-plus serialization is largely interchangeable with preferred serialization in the real world.</t>
      </section>
    </section>
    <section anchor="DeterministicSerialization">
      <name>Deterministic Serialization</name>
      <t>This section defines a serialization named "deterministic serialization"</t>
      <t>Deterministic serialization is the same as described in <xref section="4.2.1" sectionFormat="of" target="RFC8949"/> except for the encoding of floating-point NaNs.
See <xref target="PreferredPlusSerialization"/> and <xref target="NaN"/> for details on, and the rationale for NaN encoding.</t>
      <t>Note that in deterministic serialization, any bignum that can be represented as an integer must be encoded as an integer.
This rule is inherited from preferred-plus serialization (<xref target="PreferredPlusSerialization"/>), just as <xref section="4.2.1" sectionFormat="of" target="RFC8949"/> inherits this requirement from preferred serialization.</t>
      <t>See also <xref target="DeterministicConsiderations"/> for considerations involved in designing a deterministic protocol that extend beyond serialization.</t>
      <section anchor="DeterministicEncoding">
        <name>Encoder Requirements</name>
        <ol spacing="normal" type="1"><li>
            <t>All of preferred-plus serialization defined in <xref target="PreferredPlusEncoding"/> <bcp14>MUST</bcp14> be used.</t>
          </li>
          <li>
            <t>If a map is encoded, the items in it <bcp14>MUST</bcp14> be sorted in the bytewise lexicographic order of their deterministic encodings of the map keys.
(Note that this is the same as the sorting in <xref section="4.2.1" sectionFormat="of" target="RFC8949"/> and not the same as <xref section="3.9" sectionFormat="of" target="RFC7049"/> / <xref section="4.2.3" sectionFormat="of" target="RFC8949"/>.)</t>
          </li>
        </ol>
      </section>
      <section anchor="DeterministicDecoding">
        <name>Decoder Requirements</name>
        <ol spacing="normal" type="1"><li>
            <t>Decoders <bcp14>MUST</bcp14> meet the decoder requirements described in <xref target="PreferredPlusDecoding"/>.
That is, deterministic encoding imposes no requirements over and above the requirements for decoding preferred-plus serialization.</t>
          </li>
        </ol>
      </section>
      <section anchor="WhenDeterministic">
        <name>When to use Deterministic Serialization</name>
        <section anchor="not-commonly-needed-for-hashing-and-signing">
          <name>Not Commonly Needed for Hashing and Signing</name>
          <t>Most applications do not require deterministic encoding — even those that employ signing or hashing to authenticate or protect the integrity of data.
For example, the payload of a COSE_Sign message (See <xref target="RFC9052"/>) does not need to be encoded deterministically because it is transmitted with the message.
The recipient receives the exact same bytes that were signed.</t>
          <t>Deterministic encoding becomes necessary only when the protected data is not transmitted as the exact bytes that are used for authenticity or integrity verification.
In such cases, both the sender and the receiver must independently construct the exact same sequence of bytes.
To guarantee this, the encoding must eliminate all variability and ambiguity.
The Sig_structure, defined in <xref section="4.4" sectionFormat="of" target="RFC9052"/>, is an example of this requirement.
Such designs are often chosen to reduce data size, preserve privacy, or meet other design constraints.</t>
          <t>See the more detailed, COSE-based example in <xref target="COSESerialization"/>.</t>
        </section>
        <section anchor="decoding-deterministic-serialization-and-relation-to-preferred-plus-serialization">
          <name>Decoding Deterministic Serialization and Relation to Preferred-Plus Serialization</name>
          <t>The only difference between preferred-plus and deterministic serialization is that in deterministic serialization, maps are required to be sorted by their keys.
Preferred-plus serialization exists as a separate mode solely because map sorting can be too expensive in some constrained environments.</t>
          <t>Preferred-plus is deterministic if no maps are encoded.</t>
          <t>The decoders are identical (except for a checking decoder for deterministic serialization).</t>
          <t>However, note that deterministic serialization is never a substitute for general serialization where use cases may require indefinite lengths, separate bignums from integers in the data model, or need non-trivial NaNs.</t>
        </section>
      </section>
      <section anchor="map-ordering">
        <name>Map Ordering</name>
        <t>Map ordering in the serialization layer is only to provide determinism and is entirely orthogonal to map ordering at the data model and application layer.</t>
        <section anchor="ordering-at-the-serialization-layer">
          <name>Ordering at the Serialization Layer</name>
          <t>For maps to be encoded deterministically, two independent entities must encode them exactly the same.
The only way to do this for maps is to sort each map's key-value pairs by key.
Thus, for deterministic encoding, maps are sorted.</t>
          <t>While not stated explicitly in <xref target="RFC8949"/>, it does imply that map decoding must never depend on map ordering.
All CBOR map decoding must succeed regardless of the map order.</t>
          <t>There is one exception to this: checking decoders (see <xref target="CheckingDecoder"/>) for deterministic or other serializations that order maps.
Their purpose is to make sure the received CBOR is encoded exactly as specified.
A checking decoder for deterministic serialization therefore rejects unordered maps.</t>
        </section>
        <section anchor="ordering-at-the-data-model-layer">
          <name>Ordering at the Data Model Layer</name>
          <t>Essentially there is no map ordering at the data model layer; applications and implementations can not rely on it.</t>
          <t>The CBOR data model for maps clearly indicates that they are not ordered (see <xref section="5.6" sectionFormat="of" target="RFC8949"/>).
This is the same as for JSON objects.</t>
          <t>Some programming environments, like the Go programming language, provide no ordering guarantees for maps.
A CBOR decoder is under no obligation to present a map in the order it was received.
Even if a map is deterministically encoded, it may not be presented at the application layer in map key order.</t>
          <t>A particular CBOR library or a particular programming environment may present sorted maps to the CBOR application if it wishes, but this is a feature of the library or programming environment only; protocols or system designs can not expect it at the application layer, even when deterministic serialization is required.</t>
        </section>
      </section>
    </section>
    <section anchor="SpecialSerializations">
      <name>Special Serializations</name>
      <t>When needed, protocols may define special serializations beyond the three described above.
The main capabilities they enable are:</t>
      <ul spacing="normal">
        <li>
          <t>Streaming encoding of text strings, byte strings, arrays, and maps using indefinite lengths, for use when the encoded item(s) exceeds the memory available on the encoding device.</t>
        </li>
        <li>
          <t>Fixed-size integer encoding, allowing values to be copied directly to and from hardware registers.
CBOR is simple enough that encoders and decoders for some protocols can be implemented entirely in hardware.</t>
        </li>
        <li>
          <t>Fixed-width floating-point encoding, relieving the encoder from performing floating-point reduction to the shortest representable form.</t>
        </li>
        <li>
          <t>In-place length updates for strings, arrays, and maps, by encoding their lengths in a fixed number of bits.
For example, if a string length is always encoded in 32 bits, increasing its length from 2^16-1 to 2^16 requires only overwriting the length field rather than shifting all 2^16 bytes of content.</t>
        </li>
        <li>
          <t>Transmission of non-trivial NaN floating-point values (see <xref target="NaN"/>).</t>
        </li>
        <li>
          <t>Use of a bignum for shorter encoding of 33- to 56-bit integers (a 40-bit value with implied tag takes 6 bytes rather than 9).</t>
        </li>
        <li>
          <t>Deterministic serialization with any or all of the above.</t>
        </li>
      </ul>
      <t>All of these except determinism are also available with general serialization, but a targeted special serialization will usually be substantially easier to implement.</t>
      <t>A recommended approach is to define a special serialization as preferred-plus or deterministic serialization with additional constraints or extensions.
For example, a protocol requiring deterministic streaming of maps and arrays could be specified as:</t>
      <ul empty="true">
        <li>
          <t>Deterministic serialization <bcp14>MUST</bcp14> be used, except that maps and arrays <bcp14>MUST</bcp14> be encoded with indefinite lengths.
Strings retain definite-length encoding, and map ordering <bcp14>MUST</bcp14> follow the rules of deterministic serialization.</t>
        </li>
      </ul>
    </section>
    <section anchor="TagDataModelRule">
      <name>New Tag Data Model Rule</name>
      <t><xref section="2" sectionFormat="of" target="RFC8949"/> states that each new CBOR tag definition introduces a new and distinct data type.
In contrast, the definitions of Tags 2 and 3 (bignums) in <xref section="3.4.3" sectionFormat="of" target="RFC8949"/> do not introduce a separate data type; instead, they attach directly to the integer type and extend its numeric range.
As a result, the generic data model's integer type is modified rather than augmented with a new, independent type (see <xref target="BigNumbersDataModel"/>).</t>
      <t>This document establishes a new rule that prohibits future tag definitions from having such effects:</t>
      <t>All future CBOR tag definitions <bcp14>MUST NOT</bcp14> incorporate, modify, or otherwise affect any data types other than the type defined by the tag itself.
A set of tags <bcp14>MAY</bcp14> affect each other, provided that all defining authorities for those tags explicitly agree.</t>
      <t>Tags 2 and 3 are exempt from this rule, as they were defined prior to the establishment of this requirement.</t>
    </section>
    <section anchor="CDDL-Operators">
      <name>CDDL Serialization Control Operator</name>
      <t>The ".serial" control operator specifies the serialization of any type in CDDL, including the serialization of the top-level data item or byte-string-wrapped sub-parts.</t>
      <t>The controller (the right-hand side) is a text string and <bcp14>MUST</bcp14> be either "prefp" or "dtrm", specifying preferred-plus (<xref target="PreferredPlusSerialization"/>) or deterministic (<xref target="DeterministicSerialization"/>) serialization, respectively.</t>
      <t>The scope of .serial extends recursively through nested arrays, maps, and tag content, but does not extend into byte strings or other data items that happen to contain encoded CBOR.
Every instance of embedded CBOR that requires specific serialization must specify it explicitly.
See also <xref target="ByteStringWrapping"/>.</t>
      <t>For example, the following specifies that a message or protocol described by "stuff" is deterministically serialized and wrapped in a byte string:</t>
      <sourcecode type="cddl"><![CDATA[
stuff = ...
deterministic-stuff = stuff .serial "dtrm"
wrapped-deterministic-stuff = #6.24(bytes .cbor deterministic-stuff)
]]></sourcecode>
      <t>For another example, the first lines of a CDDL document as follows specify that "my-protocol" be serialized with preferred-plus:</t>
      <sourcecode type="cddl"><![CDATA[
my-prefp-protocol = my-protocol .serial "prefp"
my-protocol = ...
]]></sourcecode>
      <t>As with filtering control operators such as .size, .serial constraints intersect when nested, whether through direct nesting or because a type with its own .serial appears within the scope of another.
Since deterministic serialization is a subset of preferred-plus, wherever both apply the effective requirement is deterministic, regardless of which one is outermost.</t>
      <t>New controller values for new serializations are possible but are highly discouraged.
Standards action is required to add them.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The security considerations in <xref section="10" sectionFormat="of" target="RFC8949"/> apply.</t>
      <section anchor="CovertChannels">
        <name>Covert Channel</name>
        <t>CBOR's serialization variants can be used as a covert channel <xref target="LAM73"/> to steganographically exfiltrate data.</t>
        <t>For example, a CBOR argument (such as an integer encoding or a string length) can be encoded in up to five different ways (e.g., the value 1 can be encoded as 0x01, 0x1801, 0x190001, 0x1A00000001, or 0x1B0000000000000001).
This variability can be used to encode about 2 hidden bits per argument.
Since every CBOR item carries an argument, even moderately complex protocols may accumulate sufficient bits to exfiltrate sensitive material (e.g., cryptographic keys) or to generate persistent identifiers for tracking users or devices.</t>
        <t>Techniques that may be used to establish a covert channel include:</t>
        <ul spacing="normal">
          <li>
            <t>Varying the encoding of CBOR arguments (as above)</t>
          </li>
          <li>
            <t>Varying the encoding of floating-point values (half-, single-, or double-precision)</t>
          </li>
          <li>
            <t>Representing text or byte strings as indefinite-length encodings, and encoding information in the segmentation structure (e.g., segment lengths or insertion of empty segments)</t>
          </li>
          <li>
            <t>Encoding data within NaN payloads</t>
          </li>
          <li>
            <t>Manipulating the ordering of map entries</t>
          </li>
          <li>
            <t>Varying the Unicode representation of text strings</t>
          </li>
        </ul>
        <t>These channels are covert because some CBOR decoders accept all such representations without raising errors or warnings.</t>
        <t>The primary safeguard is to ensure the CBOR encoding library used is trustworthy and does not exfiltrate data.</t>
        <t>Checking for preferred-plus or deterministic serialization as described in <xref target="CheckingDecoder"/> can reveal unexpected variation, and so expose an attack, but cannot prevent one.</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t><cref anchor="to-be-removed">RFC Editor: please replace RFCXXXX with the RFC
number of this RFC and remove this note.</cref></t>
      <t>This document requests IANA to register the ".serial" control operator into the registry "<xref section="CDDL Control Operators" relative="#cddl-control-operators" sectionFormat="bare" target="IANA.cddl"/>" of the <xref target="IANA.cddl"/> registry group.</t>
      <t>IANA is requested to add a reference to <xref target="TagDataModelRule"/> to the CBOR tag registry <xref target="IANA.cbor-tags"/>.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <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="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="IEEE754" target="https://ieeexplore.ieee.org/document/8766229">
          <front>
            <title>IEEE Standard for Floating-Point Arithmetic</title>
            <author>
              <organization>IEEE</organization>
            </author>
            <date/>
          </front>
          <seriesInfo name="IEEE Std" value="754-2019"/>
          <seriesInfo name="DOI" value="10.1109/IEEESTD.2019.8766229"/>
        </reference>
        <reference anchor="IANA.cddl" target="https://www.iana.org/assignments/cddl">
          <front>
            <title>Concise Data Definition Language (CDDL)</title>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="IANA.cbor-tags" target="https://www.iana.org/assignments/cbor-tags">
          <front>
            <title>Concise Binary Object Representation (CBOR) Tags</title>
            <author>
              <organization>IANA</organization>
            </author>
          </front>
        </reference>
        <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>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC8392">
          <front>
            <title>CBOR Web Token (CWT)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="E. Wahlstroem" initials="E." surname="Wahlstroem"/>
            <author fullname="S. Erdtman" initials="S." surname="Erdtman"/>
            <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
            <date month="May" year="2018"/>
            <abstract>
              <t>CBOR Web Token (CWT) is a compact means of representing claims to be transferred between two parties. The claims in a CWT are encoded in the Concise Binary Object Representation (CBOR), and CBOR Object Signing and Encryption (COSE) is used for added application-layer security protection. A claim is a piece of information asserted about a subject and is represented as a name/value pair consisting of a claim name and a claim value. CWT is derived from JSON Web Token (JWT) but uses CBOR rather than JSON.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8392"/>
          <seriesInfo name="DOI" value="10.17487/RFC8392"/>
        </reference>
        <reference anchor="RFC9413">
          <front>
            <title>Maintaining Robust Protocols</title>
            <author fullname="M. Thomson" initials="M." surname="Thomson"/>
            <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
            <date month="June" year="2023"/>
            <abstract>
              <t>The main goal of the networking standards process is to enable the long-term interoperability of protocols. This document describes active protocol maintenance, a means to accomplish that goal. By evolving specifications and implementations, it is possible to reduce ambiguity over time and create a healthy ecosystem.</t>
              <t>The robustness principle, often phrased as "be conservative in what you send, and liberal in what you accept", has long guided the design and implementation of Internet protocols. However, it has been interpreted in a variety of ways. While some interpretations help ensure the health of the Internet, others can negatively affect interoperability over time. When a protocol is actively maintained, protocol designers and implementers can avoid these pitfalls.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9413"/>
          <seriesInfo name="DOI" value="10.17487/RFC9413"/>
        </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="RFC7049">
          <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="October" year="2013"/>
            <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>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7049"/>
          <seriesInfo name="DOI" value="10.17487/RFC7049"/>
        </reference>
        <reference anchor="Examples-Repo" target="https://github.com/cbor-wg/draft-ietf-cbor-serialization/tree/main/examples">
          <front>
            <title>draft-ietf-cbor-serialization</title>
            <author>
              <organization>IETF CBOR WG</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="CTAP2" target="https://fidoalliance.org/specs/fido-v2.0-ps-20190130/fido-client-to-authenticator-protocol-v2.0-ps-20190130.html">
          <front>
            <title>Client To Authenticator Protocol v2</title>
            <author>
              <organization>W3C</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="NaNBoxing" target="https://craftinginterpreters.com/optimization.html#nan-boxing">
          <front>
            <title>Crafting Interpreters</title>
            <author fullname="Robert Nystrom">
              <organization/>
            </author>
            <date year="2021" month="July"/>
          </front>
        </reference>
        <reference anchor="I-D.mcnally-deterministic-cbor">
          <front>
            <title>dCBOR: Deterministic CBOR</title>
            <author fullname="Wolf McNally" initials="W." surname="McNally">
              <organization>Blockchain Commons</organization>
            </author>
            <author fullname="Christopher Allen" initials="C." surname="Allen">
              <organization>Blockchain Commons</organization>
            </author>
            <author fullname="Carsten Bormann" initials="C." surname="Bormann">
              <organization>Universität Bremen TZI</organization>
            </author>
            <author fullname="Laurence Lundblade" initials="L." surname="Lundblade">
              <organization>Security Theory LLC</organization>
            </author>
            <date day="10" month="August" year="2026"/>
            <abstract>
              <t>   The purpose of determinism is to ensure that semantically equivalent
   data items are encoded into identical byte streams.  CBOR (RFC 8949)
   defines "Deterministically Encoded CBOR" in its Section 4.2, but
   leaves some important choices up to the application developer.  The
   present document specifies dCBOR, a set of narrowing rules for CBOR
   that can be used to help achieve interoperable deterministic encoding
   for a variety of applications desiring a narrow and clearly defined
   set of choices.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-mcnally-deterministic-cbor-18"/>
        </reference>
        <reference anchor="UML" target="https://www.omg.org/spec/UML/2.5.1/PDF">
          <front>
            <title>OMG Unified Modeling Language (OMG UML) Version 2.5.1</title>
            <author>
              <organization/>
            </author>
            <date year="2017" month="December"/>
          </front>
        </reference>
        <reference anchor="LAM73">
          <front>
            <title>A note on the confinement problem</title>
            <author fullname="Butler W. Lampson" initials="B." surname="Lampson">
              <organization>Xerox Palo Alto Research Center, Palo Alto, CA</organization>
            </author>
            <date month="October" year="1973"/>
          </front>
          <seriesInfo name="Communications of the ACM" value="vol. 16, no. 10, pp. 613-615"/>
          <seriesInfo name="DOI" value="10.1145/362375.362389"/>
          <refcontent>Association for Computing Machinery (ACM)</refcontent>
        </reference>
        <reference anchor="UNICODE-NORM" target="https://www.unicode.org/reports/tr15/">
          <front>
            <title>Unicode Normalization Forms</title>
            <author initials="K." surname="Whistler" fullname="Ken Whistler">
              <organization/>
            </author>
            <date year="2025" month="July" day="30"/>
          </front>
          <seriesInfo name="Unicode Standard Annex" value="#15"/>
        </reference>
      </references>
    </references>
    <?line 726?>

<section anchor="DeterministicConsiderations">
      <name>Specifying a Fully Deterministic Protocol</name>
      <t>While deterministic serialization (<xref target="DeterministicSerialization"/>) is sufficient to make most protocols fully deterministic, it is not sufficient for all.
This appendix describes some issues that may need further requirements.
Note that these issues occur for parts of the protocol that the sender and receiver construct independently.
See <xref target="WhenDeterministic"/>.</t>
      <section anchor="protocol-data-definition">
        <name>Protocol Data Definition</name>
        <t>For a protocol to be deterministic, its definition at the data model layer must be deterministic.</t>
        <t>Here's an example definition:</t>
        <ul empty="true">
          <li>
            <t>At the sender's convenience, the birth date <bcp14>MAY</bcp14> be encoded either as an integer epoch date or string date. The receiver <bcp14>MUST</bcp14> decode both formats.</t>
          </li>
        </ul>
        <t>While this definition is interoperable, it lacks determinism.
The definition leaves a choice open, just as CBOR leaves encoding choices open when deterministic serialization is not required.</t>
        <t>To make this example definition deterministic, specify one date format and prohibit the other.</t>
        <t>A more interesting source of variability is CBOR's variety of number types.
For instance, the number 2 can be represented as an integer, float, bignum, decimal fraction and others defined by tags in the CBOR tag registry.
Most protocol designs will just specify one number type to use, and that will give determinism, but here's an example specification that doesn’t:</t>
        <ul empty="true">
          <li>
            <t>At the sender's convenience, the fluid level measurement <bcp14>MAY</bcp14> be encoded as an integer or a floating-point number. This allows for minimal encoding size while supporting a large range. The receiver <bcp14>MUST</bcp14> be able to accept both integers and floating-point numbers for the measurement.</t>
          </li>
        </ul>
        <t>Again, this ensures interoperability but not determinism — identical fluid level measurements can be represented in more than one way.
Determinism can be achieved by allowing only floating-point, though that doesn't minimize encoding size.</t>
        <t>A better solution requires the fluid level always be encoded using the smallest representation.
For example, a fluid level of 2 is always encoded as an integer, never as a floating-point number; and a level of 2.000001 is always encoded as a floating-point number so as not to lose precision.
See the numeric reduction defined by <xref target="I-D.mcnally-deterministic-cbor"/>.</t>
      </section>
      <section anchor="text-strings-and-unicode">
        <name>Text Strings and Unicode</name>
        <t>CBOR's text string type (major type 3) carries UTF-8, which is itself unambiguous.
Unicode is not: the same text may be written as different sequences of code points, since a character with a diacritic can appear either precomposed or as a base character plus combining marks.
"é" is either U+00E9 or U+0065 plus U+0301.
As with the number types above, a deterministic protocol must choose one representation — typically by requiring a Unicode normalization form like Unicode Normalization Form C (NFC) <xref target="UNICODE-NORM"/>.</t>
      </section>
      <section anchor="cbor-tags">
        <name>CBOR Tags</name>
        <t>Some tags allow their content to be represented in more than one way.
For example, the epoch date (tag 1) allows either integer or floating-point representation.
A deterministic protocol using tags should examine each tag's definition for such variability and define a deterministic rule for selecting among the alternatives it finds.</t>
      </section>
    </section>
    <section anchor="NaN">
      <name>IEEE 754 NaN</name>
      <t>This section provides background information on <xref target="IEEE754"/> NaN (Not a Number) and its use in CBOR.</t>
      <section anchor="NaNBasics">
        <name>Basics</name>
        <t><xref target="IEEE754"/> defines the most widely used representation for floating-point numbers.
It includes special values for infinity and NaN (Not a Number).
NaN is designed to represent the result of invalid operations, such as the square root of a negative number.</t>
        <t>A NaN is not a single value the way positive infinity is.
It has a sign bit and a trailing significand field — 10 bits in half precision, 23 in single, 52 in double — whose use is not formally defined.
The design intent is that these bits distinguish NaN types and hold diagnostic detail about a local computation.</t>
        <t>IEEE 754 formally defines the notions of quiet and signaling NaN, but the bit pattern distinguishing them is only a recommendation, directed at CPU designers:</t>
        <ul spacing="normal">
          <li>
            <t>A quiet NaN has the most significant significand bit set.</t>
          </li>
          <li>
            <t>A signaling NaN has that bit clear and at least one other significand bit set, to distinguish it from infinity.</t>
          </li>
          <li>
            <t>Either can have a non-zero payload, which is the bits other than the most significant significand bit.</t>
          </li>
          <li>
            <t>No recommendation is made for the sign bit.</t>
          </li>
        </ul>
        <t>This recommendation is not universally followed (e.g., PA-RISC and pre-R6 MIPS).</t>
        <t>An arithmetic operation on a signaling NaN raises the invalid operation exception and does not preserve it, whereas quiet NaNs are usually propagated with the payload intact.
Implementations vary, but this makes quiet NaNs usable for application-defined purposes in a way signaling NaNs are not.</t>
        <t>For this discussion, a non-trivial NaN is a signaling NaN, a NaN with a non-zero payload, or a NaN with the sign bit set, as the host represents it.
A trivial NaN is one that passively indicates that the value is not a number, and nothing more.</t>
      </section>
      <section anchor="implementation-support-for-non-trivial-nans">
        <name>Implementation Support for Non-Trivial NaNs</name>
        <t>This section discusses the extent of programming language and CPU support for NaN payloads.</t>
        <t>Although <xref target="IEEE754"/> has existed for decades, support for manipulating non-trivial NaNs has historically been limited and inconsistent.
Some key points:</t>
        <ul spacing="normal">
          <li>
            <t>Programming languages:  </t>
            <ul spacing="normal">
              <li>
                <t>The programming languages C, C++, Java, JavaScript, Python and Rust do not provide APIs to set or extract NaN payloads.</t>
              </li>
              <li>
                <t>IEEE 754 is over thirty years old, enough time for support to be added if there was need.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>CPU hardware:  </t>
            <ul spacing="normal">
              <li>
                <t>CPUs use the distinction between signaling and quiet NaNs to determine whether to raise exceptions.</t>
              </li>
              <li>
                <t>A non-trivial NaN matching the CPU's signaling NaN pattern may either trigger an exception or be converted into a quiet NaN.</t>
              </li>
              <li>
                <t>Instructions converting between single and double precision sometimes discard or alter NaN payloads.</t>
              </li>
            </ul>
          </li>
        </ul>
        <t>As a result, applications that rely on non-trivial NaNs generally cannot depend on CPU instructions, floating-point libraries, or programming environments.
Instead, they usually need their own software implementation of IEEE 754 to encode and decode the full bit patterns to reliably process non-trivial NaNs.</t>
      </section>
      <section anchor="use-and-non-use-for-non-trivial-nans">
        <name>Use and Non-use for Non-Trivial NaNs</name>
        <t>Non-trivial NaNs, excluding signaling NaNs, are not produced by standard floating-point operations.
They are typically created at the application level, where software may take advantage of unused bits in the NaN payload.
Such uses are rare and unusual, but they do exist.</t>
        <t>One example is the R programming language, which is designed for statistical computing and therefore operates heavily on numeric data.
R uses NaN payloads to distinguish various error or missing-data conditions beyond standard computational exceptions such as division by zero.</t>
        <t>Another example is NaNboxing (see <xref target="NaNBoxing"/>), a technique used by some language runtimes — such as certain JavaScript engines — to efficiently represent multiple data types within a single 64-bit word by storing type tags or pointers in the NaN payload.
(CBOR can represent such payloads, but NaNboxed pointers are generally not meaningful or portable across machines, and therefore are usually unsuitable for network transmission or file storage.)</t>
        <t>CBOR's NaN-payload support can be leveraged if data from these systems must be transmitted over a network or written to persistent storage.</t>
        <t>A designer of a new protocol that makes extensive use of floating-point values might be tempted to use NaN payloads to encode out-of-band information such as error conditions.
For example, NaN payloads could be used to distinguish situations such as sensor offline, sensor absent, sensor error, or sensor out of calibration.
While this is technically possible in CBOR, it comes with significant drawbacks:</t>
        <ul spacing="normal">
          <li>
            <t>Preferred-plus and deterministic serialization cannot be used for this protocol.</t>
          </li>
          <li>
            <t>Support for NaN payloads is unreliable across programming environments and CBOR libraries.</t>
          </li>
          <li>
            <t>Values cannot be translated directly to JSON, which does not support NaNs of any kind.</t>
          </li>
        </ul>
      </section>
      <section anchor="clarification-of-rfc-8949">
        <name>Clarification of RFC 8949</name>
        <t>This is a clarifying restatement of how NaNs are to be treated according to <xref target="RFC8949"/>.</t>
        <t>NaNs represented in floating-point values of different lengths are considered equivalent in the basic generic data model if:</t>
        <ul spacing="normal">
          <li>
            <t>Their sign bits are identical, and</t>
          </li>
          <li>
            <t>Their significands are identical after both significands are zero-extended on the right to 64 bits</t>
          </li>
        </ul>
        <t>This equivalence is established for the entire CBOR basic generic data model.
A NaN encoded as half-, single-, or double-precision is equivalent whenever it satisfies the rules above.
This remains true regardless of how a CBOR library accepts, stores, or presents a NaN in its API.
At the application layer, the equivalence still holds.
The only way to avoid this equivalence is by using a tag specifically designed to carry NaNs without these equivalence rules, since tags extend the data model unless otherwise specified.</t>
        <t>The equivalence is similar to how the floating-point value 1.0 is treated as the same value regardless of the precision used to encode it.
Some floating-point values cannot be represented in shorter formats (e.g., 2.0e+50 cannot be encoded in half-precision).
The same is true for some NaNs.</t>
        <t>In preferred serialization, this equivalence <bcp14>MUST</bcp14> be used to shorten encoding length.
If a NaN can be represented equivalently in a shorter form (e.g., half-precision rather than single-precision), then the shorter representation <bcp14>MUST</bcp14> be used.</t>
        <t>This equivalence also applies when floating-point values are used as map keys.
A map key encoded as half-precision <bcp14>MUST</bcp14> be considered a duplicate of one encoded as double-precision if they meet the equivalence rules above.</t>
        <t>However, this equivalence does not apply to map sorting.
Sorting operates on the fully encoded and serialized representation, not on the abstract data model.</t>
        <t>It is <xref section="2" sectionFormat="of" target="RFC8949"/> that establishes this equivalence by stating that the number of bytes used to encode a floating-point value is not visible in the data model.
<xref section="4.1" sectionFormat="of" target="RFC8949"/> defines preferred serialization.
It requires shortest-length encoding of NaNs including instructions on how to do it.
<xref section="5.6.1" sectionFormat="of" target="RFC8949"/> describes how NaNs are treated as equivalent when used as map keys.
These three parts of <xref target="RFC8949"/> are consistent and are the basis of this restatement.</t>
        <t>Since <xref section="4.2.1" sectionFormat="of" target="RFC8949"/>, (Core Deterministic Encoding Requirements), explicitly requires preferred serialization, compliant deterministic encodings must use the shortest equivalent representation of NaNs.</t>
        <t>Finally, <xref section="4.2.2" sectionFormat="of" target="RFC8949"/> discusses alternative approaches to deterministic encoding.
It suggests, for example, that all NaNs may be encoded as a half-precision quiet NaN.
This section is distinct from the Core Deterministic Encoding Requirements and represents an optional alternative for handling NaNs.</t>
      </section>
      <section anchor="NaNCompatibility">
        <name>Divergence from RFC 8949</name>
        <t>Non-trivial NaNs are not permitted in either preferred-plus or deterministic serializations.
This is in contrast to preferred serialization and <xref section="4.2.1" sectionFormat="of" target="RFC8949"/>.</t>
        <t>Note that the prohibition of non-trivial NaNs is the sole difference between deterministic serialization (<xref target="DeterministicSerialization"/>) and <xref section="4.2.1" sectionFormat="of" target="RFC8949"/>.</t>
        <t>The divergence is justified by the following:</t>
        <ul spacing="normal">
          <li>
            <t>Encoding and equivalence of non-trivial NaNs was a little unclear <xref target="RFC8949"/>.</t>
          </li>
          <li>
            <t>IEEE 754 doesn't set requirements for their handling.</t>
          </li>
          <li>
            <t>Non-trivial NaNs are not well-supported across CPUs and programming environments.</t>
          </li>
          <li>
            <t>Because preferred serialization of non-trivial NaNs is difficult and error-prone to implement, many CBOR implementations don't encode and/or decode non-trivial NaNs, or don't encode or decode them correctly.</t>
          </li>
          <li>
            <t>Practical use cases for non-trivial NaNs are extremely rare.</t>
          </li>
          <li>
            <t>Reducing non-trivial NaNs to a half-precision quiet NaN is simple and supported by programming environments (e.g., <tt>isnan()</tt> can be used to detect all NaNs).</t>
          </li>
          <li>
            <t>Non-trivial NaNs remain supported by general serialization; the divergence is only for preferred-plus and deterministic serialization.</t>
          </li>
          <li>
            <t>A new CBOR tag can be defined in the future to explicitly support them.</t>
          </li>
        </ul>
      </section>
      <section anchor="recommendations-for-use-of-non-trivial-nans">
        <name>Recommendations for Use of Non-Trivial NaNs</name>
        <t>While non-trivial NaNs are excluded from preferred-plus and deterministic serialization, they are supported by <xref target="GeneralSerialization"/>.</t>
        <t>New protocol designs <bcp14>SHOULD</bcp14> avoid non-trivial NaNs.
Support for them is unreliable, and it is straightforward to design CBOR-based protocols that do not depend on them.
In many cases, the use of NaN can be replaced entirely with null.
JSON requires use of null as it does not support NaNs at all.</t>
        <t>The primary use case for non-trivial NaNs is existing systems that already use them.
For example, a program that relies on non-trivial NaNs internally may need to serialize its data to run across machines connected by a network.</t>
      </section>
    </section>
    <section anchor="code-for-encoding-preferred-plus-floating-point-values">
      <name>Code for Encoding Preferred-Plus Floating-Point Values</name>
      <t>Preferred-plus (<xref target="PreferredPlusEncoding"/>) and deterministic serialization require that floating-point values fitting in single-precision and half-precision be encoded as such.
This C code implements that conversion.
While conversion between single and double is widely supported, conversion to half-precision is not.
<xref section="D" sectionFormat="of" target="RFC8949"/> provides example code for decoding half-precision values; this appendix provides corresponding code for encoding them.</t>
      <t>Two functions are provided: one to convert from double to single, and another from single to half.
Used together, they cover all possible cases.
If the input is a double, pref_plus_double_to_single() must be called first;
if it succeeds, pref_plus_single_to_half() is then called to complete the conversion from double to half.
If the input is already a single, only pref_plus_single_to_half() need be called.</t>
      <t>(The two functions have identical structure.
Because the constants are difficult to compute and verify, both are provided.)</t>
      <t>Both functions return an integer with the bit pattern for the resulting floating-point value, or a negative value on failure.
-1 indicates the conversion can't be performed because the input is out of range or precision would be lost.
-2 indicates a non-trivial NaN was given for encoding which should either be rejected or output as a half-precision quiet NaN.</t>
      <figure anchor="half-encode">
        <name>Example C Code for Preferred-Plus Floating-Point Encoding</name>
        <sourcecode type="c" markers="true" name="prefp-float-encode.c"><![CDATA[
/* Constants based on IEEE 754; _LEN is in bits */

/* Half-precision */
#define HLF_MANT_LEN          10
#define HLF_EXP_LEN           5
#define HLF_MANT_BITS         0x3ffUL /* 10 bits */
#define HLF_SIGN_BIT         (0x01UL << (HLF_EXP_LEN + HLF_MANT_LEN))
#define HLF_NAN_INF_EXP_BITS  0x7c00
#define HLF_QUIET_NAN        (0x1UL << (HLF_MANT_LEN-1))

/* Single-precision */
#define SGL_MANT_LEN          23
#define SGL_EXP_LEN           8
#define SGL_MANT_BITS         0x7fffffUL /* 23 bits */
#define SGL_SIGN_BIT         (0x01UL << (SGL_EXP_LEN + SGL_MANT_LEN))
#define SGL_EXP_BITS          0xffUL /* 8 bits */
#define SGL_QUIET_NAN        (0x1UL << (SGL_MANT_LEN - 1))
#define SGL_ZERO_SUBNORM_EXP  0
#define SGL_NAN_INF_EXP       255
#define SGL_NAN_INF_EXP_BITS (SGL_NAN_INF_EXP << SGL_MANT_LEN)
#define SGL_MANT_ADD_ONE     (0x01UL << SGL_MANT_LEN)

/* Double-precision */
#define DBL_MANT_LEN          52
#define DBL_EXP_LEN           11
#define DBL_MANT_BITS         0xfffffffffffffULL /* 52 bits */
#define DBL_EXP_BITS          0x7ffULL /* 11 bits */
#define DBL_QUIET_NAN        (0x1ULL << (DBL_MANT_LEN-1))
#define DBL_ZERO_SUBNORM_EXP  0
#define DBL_NAN_INF_EXP       2047
#define DBL_MANT_ADD_ONE     (0x01ULL << (DBL_MANT_LEN))

/* Converting single to half; _EXP are biased single exponents */
#define S2H_SIGN_SHIFT       16
#define S2H_BIAS_DIFF_EXP   (127 - 15)
#define S2H_MIN_NORM_EXP     113
#define S2H_MIN_SUBNORM_EXP  103
#define S2H_SUBNORM_SHIFT    126
#define S2H_MAX_NORM_EXP     142
#define S2H_LOST_BITS        0x1fffUL /* 23 - 10 bits */

/* Converting double to single; _EXP are biased double exponents */
#define D2S_SIGN_SHIFT       32
#define D2S_BIAS_DIFF_EXP   (1023 - 127)
#define D2S_MIN_NORM_EXP     898
#define D2S_MIN_SUBNORM_EXP  874
#define D2S_SUBNORM_SHIFT    926
#define D2S_MAX_NORM_EXP     1150
#define D2S_LOST_BITS        0x1fffffffULL /* 52 - 23 bits */


long pref_plus_single_to_half(unsigned long single) {
  const unsigned long sign = single >> S2H_SIGN_SHIFT & HLF_SIGN_BIT;
  const unsigned long mant = single & SGL_MANT_BITS;
  const unsigned long exp  = single >> SGL_MANT_LEN & SGL_EXP_BITS;

  if (exp == SGL_ZERO_SUBNORM_EXP) {
    if (mant == 0) {
      return (long)sign; /* +/- 0.0 */
    } else {
      return -1; /* single subnormals are out of range for half */
    }
  } else if (exp >= S2H_MIN_SUBNORM_EXP && exp < S2H_MIN_NORM_EXP) {
    if (mant & ((1UL << (S2H_SUBNORM_SHIFT - exp)) - 1)) {
      return -1;   /* bits lost in conversion to half subnormal */
    } else {
      return (long)(sign + /* converts to half subnormal */
           ((mant + SGL_MANT_ADD_ONE) >> (S2H_SUBNORM_SHIFT - exp)));
    }
  } else if (exp >= S2H_MIN_NORM_EXP && exp <= S2H_MAX_NORM_EXP) {
    if (mant & S2H_LOST_BITS) {
      return -1; /* bits lost in conversion */
    } else {
      return (long)(sign + /* Converts to normal */
                   ((exp - S2H_BIAS_DIFF_EXP) << HLF_MANT_LEN) +
                   (mant >> (SGL_MANT_LEN - HLF_MANT_LEN)));
    }
  } else if (exp == SGL_NAN_INF_EXP) {
    if (mant == 0) {
      return (long)(sign + HLF_NAN_INF_EXP_BITS); /* +/- infinity */
    } else if (mant == SGL_QUIET_NAN && sign == 0) {
       return HLF_QUIET_NAN + HLF_NAN_INF_EXP_BITS; /* trivial NaN */
    } else {
       return -2; /* non-trivial NaN */
    }
  } else {
     return -1; /* large exponent -- out of range for half */
  }
}


long long pref_plus_double_to_single(unsigned long long dbl) {
  const unsigned long long sign = 
                                dbl >> D2S_SIGN_SHIFT & SGL_SIGN_BIT;
  const unsigned long long mant = dbl & DBL_MANT_BITS;
  const unsigned long long exp  = dbl >> DBL_MANT_LEN & DBL_EXP_BITS;

  if (exp == DBL_ZERO_SUBNORM_EXP) {
    if (mant == 0) {
      return (long long)sign; /* +/- 0.0 */
    } else {
      return -1; /* double subnormals are out of range for single */
    }
  } else if (exp >= D2S_MIN_SUBNORM_EXP && exp < D2S_MIN_NORM_EXP) {
    if (mant & ((1ULL << (D2S_SUBNORM_SHIFT - exp)) - 1)) {
      return -1; /* bits lost in conversion to single subnormal */
    } else {
      return (long long)(sign + /* converts to single subnormal */
           ((mant + DBL_MANT_ADD_ONE) >> (D2S_SUBNORM_SHIFT - exp)));
     }
  } else if (exp >= D2S_MIN_NORM_EXP && exp <= D2S_MAX_NORM_EXP) {
    if (mant & D2S_LOST_BITS) {
      return -1; /* bits lost in conversion */
    } else {
       return (long long)(sign + /* Converts to normal */
                        ((exp - D2S_BIAS_DIFF_EXP) << SGL_MANT_LEN) +
                         (mant >> (DBL_MANT_LEN - SGL_MANT_LEN)));
    }
  } else if (exp == DBL_NAN_INF_EXP) {
    if (mant == 0) {
      /* +/- infinity */
      return (long long)(sign + SGL_NAN_INF_EXP_BITS); 
    } else if (mant == DBL_QUIET_NAN && sign == 0) {
       return SGL_QUIET_NAN + SGL_NAN_INF_EXP_BITS; /* quiet NaN */
    } else {
       return -2; /* non-trivial NaN */
    }
  } else {
     return -1; /* large exponent -- out of range for single */
  }
}
]]></sourcecode>
      </figure>
    </section>
    <section anchor="BigNumbersDataModel">
      <name>Bignums and the CBOR Data Model</name>
      <t>The primary purpose of this document is to define preferred-plus and deterministic serialization.
Accordingly, <xref target="PreferredPlusSerialization"/> describes CBOR's unified integer space in terms of serialization behavior.
This is an effective and clear way to describe what implementors must do.
An implementation that follows the requirements in <xref target="PreferredPlusSerialization"/> will be complete and correct with respect to serialization.</t>
      <t>From a conceptual perspective, however, additional discussion is warranted regarding the CBOR data model itself.
That discussion is provided in this appendix.
(Please review <xref target="models"/> for background on the difference between serialization and the data model).</t>
      <t>In the basic, generic CBOR data model, each tag represents a distinct data type (<xref section="2" sectionFormat="of" target="RFC8949"/>).
Tags are also distinct from the major types, such as numbers and strings.
By this, an integer value such as 0 or 1 encoded as major type 0 is clearly distinct in the data model from the same integer value encoded as tag 2.</t>
      <t>However, the text in <xref section="3.4.3" sectionFormat="of" target="RFC8949"/> overrides this by defining these encodings to be equivalent rather than distinct.
This text therefore modifies the CBOR data model.
No other serialization requirement in <xref target="RFC8949"/> or in this document alters the data model; this equivalence is the sole exception.
This is unusual because the data model is otherwise orthogonal to serialization.</t>
      <t>Further, <xref section="3.4.3" sectionFormat="of" target="RFC8949"/>  along with text in <xref section="2" sectionFormat="of" target="RFC8949"/> are interpreted such that there is never a CBOR data model where there is a distinction between these integer representations.
That is, the equivalence applies regardless of the serialization even though much of the relevant text appears in proximity to discussions of serialization.</t>
      <t>This document does not attempt to update or revise the text of <xref section="3.4.3" sectionFormat="of" target="RFC8949"/>.
Rather, it records the commonly accepted interpretation of that text and its implications for the CBOR data model.</t>
      <t>This document does create a new rule for future tag definitions.
See <xref target="TagDataModelRule"/>.</t>
    </section>
    <section anchor="BigNumbersCDDL">
      <name>CDDL for Bignums</name>
      <t>The types bigint and biguint in the CDDL Standard Prelude (<xref section="D" sectionFormat="of" target="RFC8610"/>) do NOT describe the bignums described in this document or in <xref section="3.4.3" sectionFormat="of" target="RFC8949"/>, not even for general serialization.
The types integer and unsigned can be used, but note that they do not fully express the rules that govern the choice between major types 0 and 1 and the bignum tags.
CDDL-described protocols <bcp14>SHOULD</bcp14> use integer and unsigned and in prose state that these values correspond to either <xref target="PreferredPlusSerialization"/> of this document or <xref section="3.4.3" sectionFormat="of" target="RFC8949"/>.
<xref target="BigNumbersDataModel"/> explains the reasons for this.</t>
      <t>The following CDDL can be used:</t>
      <sourcecode type="cddl"><![CDATA[
; bignum byte strings are of unlimited size, but that 
; can't be expressed in CDDL, so a limit of 1,000
bnmax = 1000
bnbstr = bstr .size (8..bnmax)

pplus-tag2bstr = #6.2(bnbstr)
pplus-biguint  = #0 / pplus-tag2bstr

pplus-tag3bstr = #6.3(bnbstr)
pplus-bignint  = #1 / pplus-tag3bstr

pplus-bigint = pplus-biguint / pplus-bignint

]]></sourcecode>
    </section>
    <section anchor="BigNumberStrategies">
      <name>Bignum Implementation Strategies</name>
      <t><xref target="BigNumbersDataModel"/> describes how CBOR defines a single integer number space, in which bignums are not distinct from values encoded using major types 0 and 1.
This appendix discusses approaches for implementers to support that model.</t>
      <t>Some programming environments provide strong native support for bignums (e.g., JavaScript, Python, Ruby, and Go), while others do not (e.g., C, C++, and Rust).
Even in environments that support bignums, operations on native-sized integers (e.g., 64-bit integers) are typically much more efficient.
It is therefore reasonable for a CBOR library to expose separate APIs for native-sized integers and for bignums.</t>
      <t>When a CBOR library provides a bignum API, values that fall within the range of major types 0 and 1 must be encoded using those major types rather than tags 2 or 3.
Similarly, decoding facilities that return bignums must accept values encoded using major types 0 and 1, even though the returned representation is a bignum.</t>
      <t>Alternatively, some CBOR libraries may choose to return tags 2 and 3 as raw byte strings, as this approach is simpler than implementing full bignum support.
When a library adopts this approach, it should clearly document that the application layer is responsible for performing the integer unification.
The application is also responsible for handling CBOR's offset-by-one encoding of negative values and the extended negative integer range permitted by major type 1.</t>
      <t>In most cases, these additional processing steps are straightforward when the application already uses a bignum library.</t>
      <t>Another acceptable approach is for a CBOR library to provide a generic mechanism that allows applications to register handlers for specific tags.
In this case, handlers for tags 2 and 3 <bcp14>MUST</bcp14> perform the required unification with major types 0 and 1.</t>
      <t>Finally, note that bignums are not a widely used feature of CBOR.
Some CBOR libraries may entirely omit support for tags 2 and 3.</t>
    </section>
    <section anchor="CheckingDecoder">
      <name>Serialization Checking</name>
      <t>Serialization checking rejects input that, while well-formed CBOR, does not conform to a serialization rule set it is enforcing.
For example, a decoder checking for deterministic serialization will error out if map keys are not in the required sorted order.
Likewise, a decoder checking for preferred-plus serialization will reject, for instance, any CBOR data item that is not encoded in its shortest form.</t>
      <t>To align with long-settled security practice and defend against malformed input attacks, every CBOR decoder must reject all input that is not well-formed.
Serialization checking goes beyond that.
The data rejected by serialization checking is well-formed; it is rejected only because of additional serialization constraints.</t>
      <section anchor="serialization-checking-use-cases">
        <name>Serialization Checking Use Cases</name>
        <t>Some protocol environments may use serialization checking to minimize representational variants as a strategy to improve interoperability.
Discouraging variants early prevents them from compounding.
See <xref target="RFC9413"/> on maintaining robust protocols.</t>
        <t>Serialization checking helps defend against covert channels described in <xref target="CovertChannels"/>.</t>
        <t>Applications that rely on deterministic serialization may use serialization checking to ensure that the data they consume is truly deterministic and that the assumptions their logic makes about determinism hold.</t>
        <t>A protocol that depends on deterministic serialization may recommend or require its decoders to perform serialization checking.
CBOR libraries may offer serialization checking as a selectable option, at some cost in code size and processing.</t>
        <t>Serialization checking may enhance security in certain contexts, but such checking is never a substitute for complete well-formedness checking.
All CBOR decoders — regardless of their capabilities, modes, or optional features — must perform full well-formedness checking.
They must also reject well-formed input that uses features they do not support.
For example, a decoder that does not support indefinite-length items rejects them because they are unsupported, not because it is acting as a checking decoder.</t>
        <t>A decoder that fails to perform well-formedness checking is unsafe, whatever else it does.
The appropriate remedy is to fix it, not to add the serialization checking described here.</t>
      </section>
      <section anchor="bignum-leading-zero-exception">
        <name>Bignum Leading Zero Exception</name>
        <t><xref section="3.4.3" sectionFormat="of" target="RFC8949"/> requires that decoders supporting tags 2 and 3 be able to decode bignums that have leading zeros, even though preferred serialization never produces them.
This conflicts with the goal of a decoder that checks for preferred or deterministic serialization: such a decoder needs to reject a bignum with leading zeros as non-conformant.</t>
        <t>This document recommends that decoders performing serialization checking reject bignums containing leading zeros, notwithstanding the <bcp14>MUST</bcp14> in <xref section="3.4.3" sectionFormat="of" target="RFC8949"/>.
Serialization checking is optional.
When a protocol selects it — for example, because it depends on deterministic encoding — decoders are expected to perform the check, including rejecting non-preferred bignum encodings such as those with leading zeros.</t>
        <t>Note that serialization-checking decoders always reject the empty byte string, because it always represents a value (0 for tag 2, -1 for tag 3) that can be encoded directly using major type 0 or 1.</t>
      </section>
    </section>
    <section anchor="ByteStringWrapping">
      <name>CBOR Byte String Wrapping</name>
      <t>This appendix provides non-normative guidance on byte-string wrapping of CBOR.
It applies primarily to tag 24 and the CDDL .cbor and .cborseq control operators, but also to the serialization-specifying control operators described in <xref target="CDDL-Operators"/>.
It also applies when prose states the byte-string wrapping requirement, such as for the COSE protected headers.
See also <xref target="COSEPayload"/>.</t>
      <section anchor="purpose">
        <name>Purpose</name>
        <dl>
          <dt>Error isolation:</dt>
          <dd>
            <t>Wrapping CBOR in a byte string prevents encoding errors in the wrapped data from causing the enclosing CBOR to fail during decoding.
(CBOR decoding generally halts at the first error and lacks internal length redundancy found in formats like ASN.1/DER.)</t>
          </dd>
          <dt>CBOR library support for signing and hashing:</dt>
          <dd>
            <t>When wrapped CBOR needs to be signed or hashed, its original encoded bytes must be available.
Most CBOR libraries cannot directly extract the raw bytes of substructures, but byte-string wrapping provides direct access to the exact bytes for signing or hashing.</t>
          </dd>
          <dt>Protocol embedding:</dt>
          <dd>
            <t>Byte-string wrapping is generally useful when messages from one CBOR-based protocol need to be embedded within another CBOR protocol.</t>
          </dd>
          <dt>Special map keys:</dt>
          <dd>
            <t>Some CBOR libraries only support simple, non-aggregate map keys (e.g., integers or strings).
To use complex data types like arrays and maps as map keys, they can be wrapped in a byte string.</t>
          </dd>
        </dl>
      </section>
      <section anchor="wrapping-recommendations">
        <name>Wrapping Recommendations</name>
        <t>The serialization requirements for the wrapping CBOR may differ from those for the wrapped CBOR.
CBOR itself imposes no universal rule that they must match; this is determined by the design of the wrapping protocol.</t>
        <t>The wrapping protocol should not impose serialization requirements on the wrapped message.
The two should be treated as independent entities.
This approach avoids potential conflicts between serialization rules.</t>
        <t>For example, assume protocol XYZ wraps protocol ABC.
If protocol ABC requires Canonical CBOR as specified in <xref section="3.9" sectionFormat="of" target="RFC7049"/> (e.g., <xref target="CTAP2"/> from WebAuthn) while protocol XYZ requires deterministic serialization, <xref target="DeterministicSerialization"/>, a conflict would arise.</t>
        <t>Most CBOR data to be signed or hashed does not require a specific serialization.
CBOR, being a modern, fully specified, binary protocol, does not need canonicalization, wrapping, or armoring like other data representation formats such as JSON.
See the discussion in <xref target="WhenDeterministic"/>.</t>
      </section>
      <section anchor="cbor-library-implementation-suggestion">
        <name>CBOR Library Implementation Suggestion</name>
        <t>A straightforward implementation strategy is to instantiate a second CBOR encoder or decoder for the wrapped message.
However, this may be suboptimal in memory-constrained environments, as it may require both a duplicate copy of the wrapped data and an additional encoder/decoder instance.</t>
        <t>A more efficient approach can be for the CBOR library to treat the wrapped CBOR like a container (similar to arrays or maps).
Many CBOR implementations already handle arrays and maps as containers without requiring a separate instance.
Similarly, a byte-string wrapping encoded CBOR can be treated as a container that always contains exactly one item.</t>
      </section>
    </section>
    <section anchor="signing-and-hashing-encoded-cbor">
      <name>Signing and Hashing Encoded CBOR</name>
      <t>CBOR protocols are generally described as a collection of data items, often using CDDL.
Signing or hashing is performed over some range of the encoded CBOR, possibly all of it.
For signing or hashing to work, the sender/encoder and the receiver/verifier must operate on exactly the same range of encoded bytes, so a protocol definition <bcp14>MUST</bcp14> define that range unambiguously.
There are several ways to specify it:</t>
      <ul spacing="normal">
        <li>
          <t>Name an existing data item (e.g., a CDDL type)</t>
        </li>
        <li>
          <t>Name a data item created specifically for this purpose (e.g., a CDDL type)</t>
        </li>
        <li>
          <t>Describe the input data items in prose</t>
        </li>
        <li>
          <t>Wrap the input in a byte string</t>
        </li>
      </ul>
      <t>Typically, a named data item is an array or a map, but non-aggregate items can be named as well.
When naming an item, the specification should state explicitly whether the input is the full encoded item (head, contents, and trailing "break" if indefinite-length) or only its contents.
Covering the full encoded item is recommended, as it is clearer.
If the item might be tag content (i.e., preceded by one or more tag numbers), the specification should state whether the tag numbers are included in the input; including them is recommended.</t>
      <t>It is also possible to specify a slice of a map or array as the input.
A good way to do this is to define a CDDL type that represents the slice as a CBOR sequence.</t>
      <t>Another practice is to wrap the bytes to be signed or hashed in a byte string, following the pattern of tag 24 (the tag number itself is typically unnecessary and omitted).
This makes the input to the signature or hash — the contents of the byte string — entirely unambiguous: there are no concerns about definite versus indefinite lengths, serialization variants, or tagging; any or all of these work.</t>
      <t>The choice of input bytes also affects implementations and their use of CBOR libraries.</t>
      <t>Byte-string wrapping is guaranteed to work with even simple, basic libraries, although it will probably require two instances of the encoder or decoder: one for the wrapped (signed/hashed) CBOR and one for the wrapping CBOR. See <xref target="ByteStringWrapping"/>.</t>
      <t>If byte-string wrapping is not used, the CBOR library must provide an additional feature that gives access to the undecoded CBOR.
For example, it may offer a "tell()" operation that reports the byte offset of the start of the first covered item and of the end of the last covered item (which is more complicated when indefinite lengths are involved), or it may offer an API that directly returns the undecoded bytes of an item.</t>
      <t>Another tactic is to require deterministic encoding.
The receiver then reconstructs the signed/hashed bytes from the decoded data items rather than accessing the received encoded CBOR.</t>
      <t>In summary, byte-string wrapping is the most reliable approach because it clearly delineates what is signed or hashed and works with every decoder, but the other designs can also be made to work.</t>
    </section>
    <section anchor="COSESerialization">
      <name>Serialization for COSE</name>
      <t>This appendix highlights how the topics in this document apply to CBOR Object Signing and Encryption  (COSE <xref target="RFC9052"/>).</t>
      <t>It focuses on the COSE_Sign1 message (<xref section="4.2" sectionFormat="of" target="RFC9052"/>), which is sufficient for illustrating the relevant considerations.
COSE_Sign1 is a simple structure for signing a payload.
Its serialization can be described in three parts:</t>
      <ul spacing="normal">
        <li>
          <t>The payload</t>
        </li>
        <li>
          <t>The Sig_structure</t>
        </li>
        <li>
          <t>The encoded message (the header parameters and the array of four that is the COSE_Sign1)</t>
        </li>
      </ul>
      <section anchor="COSEPayload">
        <name>COSE Payload Serialization</name>
        <t>The signed payload may or may not be CBOR, but assume that it is, perhaps a CWT or EAT.
The payload is transmitted from the signer/sender fully intact all the way to the verifier/receiver.
Because it is transmitted fully intact, CBOR is a binary protocol and intermediaries do not do things like wrap long lines or add base 64 encoding or such, it is not special in any way and COSE imposes no serialization restrictions on it at all.
That is, it can use any serialization it wants.
The serialization is selected by the protocol that defines the payload, not by COSE.</t>
        <t>This highlights the principle that determinism is often NOT needed for signing and hashing described in <xref target="WhenDeterministic"/>.</t>
        <t>It is also worth noting that the payload is a byte string wrapped.
This is not for determinism, armoring or canonicalization.
It is so that the payload can be any data format, including not CBOR.
It is also so CBOR libraries can return the CBOR-encoded payload for processing by the verification algorithms.
Most CBOR libraries decoders do not provide access to any arbitrary chunk of encoded CBOR in the middle of a message.
This is an example of byte string wrapping described in <xref target="ByteStringWrapping"/>.</t>
      </section>
      <section anchor="COSESigStructure">
        <name>COSE Sig_structure</name>
        <t>The Sig_structure <xref section="4.4" sectionFormat="of" target="RFC9052"/> is used to aggregate all the items that are input to the signature algorithm — the payload, protected headers and other.</t>
        <t>The Sig_structure is not transmitted from the sender to the receiver; instead, it is constructed independently by both parties.
COSE therefore explicitly requires deterministic encoding so that both the sender and receiver produce identical encoded CBOR representations.
This requirement is specified in <xref section="9" sectionFormat="of" target="RFC9052"/>.</t>
        <t>This COSE requirement is effectively equivalent to the deterministic serialization defined in <xref target="DeterministicSerialization"/>, since no floating-point NaNs are involved.
It is also effectively equivalent to preferred-plus serialization as defined in <xref target="PreferredPlusSerialization"/>, because the Sig_structure contains no maps.</t>
        <t>The determinism requirement does not apply to the protected headers incorporated into the Sig_structure.
Deterministic encoding of the headers is unnecessary because they are transmitted in the exact encoded form in which they are included in the Sig_structure.</t>
        <t>Furthermore, determinism requirements do not extend into CBOR inside of byte strings.
Once CBOR data is wrapped in a byte string, its internal encoding is treated as opaque and is not subject to surrounding serialization constraints.</t>
        <t>This illustrates the general need for deterministic serialization when signed data is reconstructed rather than transmitted in the exact form that was signed.
See <xref target="WhenDeterministic"/>.</t>
      </section>
      <section anchor="COSEMessage">
        <name>The Encoded Message</name>
        <t>A COSE_Sign1 message is an array of four elements containing two header parameter chunks, the payload, and the signature.
The two header parameter chunks are maps that hold the various header parameters.
COSE places no serialization requirements on these elements.
The COSE protocol functions correctly regardless of the CBOR serialization used, as long as the decoder can decode what the encoder sends.</t>
        <t>In this respect, the serialization of the COSE_Sign1 message is no different from that of any other CBOR-based protocol message.
Indefinite-length items may be used, and non-shortest CBOR arguments are permitted.
The only requirement is that the serialization used by the encoder be decodable by the receiver.</t>
        <t>Strictly speaking, COSE is a framework protocol intended for incorporation into an end-to-end protocol, which should explicitly define its serialization requirements.
See <xref target="FrameworkProtocols"/> and <xref target="EndToEndProtocols"/>.</t>
        <t>In practice, some COSE libraries have implicitly implemented only the preferred (or preferred-plus) serialization, and end-to-end protocols have often defaulted to whatever behavior the underlying COSE library provides.
While this generally works — particularly because the preferred serialization aligns with the recommendations here — it is more robust for an end-to-end protocol to state its serialization requirements explicitly.</t>
      </section>
    </section>
    <section anchor="examples">
      <name>Examples</name>
      <t>This appendix provides examples of the serializations described in this document.
Each example is a single data item.
Collectively, the examples cover the major CBOR data types and some special cases.
<xref target="tab-example"/> describes the five fields provided for each example.</t>
      <table anchor="tab-example">
        <name>Example Data Item Fields</name>
        <thead>
          <tr>
            <th align="left">field</th>
            <th align="left">description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">description</td>
            <td align="left">Text describing the item</td>
          </tr>
          <tr>
            <td align="left">edn-representations</td>
            <td align="left">Unencoded value(s) for the data item</td>
          </tr>
          <tr>
            <td align="left">general-serializations</td>
            <td align="left">Encoded representation(s) for general serialization</td>
          </tr>
          <tr>
            <td align="left">preferred-plus-serializations</td>
            <td align="left">Encoded representation(s) for preferred-plus serialization</td>
          </tr>
          <tr>
            <td align="left">deterministic-serialization</td>
            <td align="left">Encoded representation for deterministic serialization</td>
          </tr>
        </tbody>
      </table>
      <section anchor="use-for-testing">
        <name>Use for Testing</name>
        <t>These examples are designed to support testing of CBOR libraries.
They cover only what is defined in this document and therefore do not provide complete or general CBOR test coverage.
All examples are well-formed and valid.</t>
        <t>While the CBOR-encoded serializations for each item can be used directly as test input, the EDN representation usually must be incorporated into the test manually.
For example, the EDN string "-5.0e-324" will likely need to be passed as a value of type double to the API of a C-language CBOR library that encodes double-precision numbers.</t>
        <t>Not all CBOR libraries support every data type represented in these examples.
This is acceptable: tests for unsupported types may be skipped, or used to verify that an appropriate “unsupported” error is returned.</t>
        <section anchor="encode-test">
          <name>Encode Test</name>
          <t>To test encoding, invoke the encoder for each example data item.
The encoder input is the item's EDN representations.
If an example provides multiple EDN representations, each of them should be tested.</t>
          <t>The encoder should be either configured for, or to default to, one of the three serialization types described in this document.
A test succeeds if the encoder produces any of the encoded representations given in the example for that serialization type.</t>
          <t>If an encoder supports multiple serialization types, each type can be tested in turn.</t>
        </section>
        <section anchor="decode-test">
          <name>Decode Test</name>
          <t>To test decoding, invoke the decoder for each example data.</t>
          <t>The decoder should be either to be configured for, or to default to, one of the three serialization types described in this document.
For the selected serialization type, process every encoded representation defined for the target type.
A test passes if the decoded output matches the value specified by the corresponding EDN representation.</t>
          <t>If a decoder supports multiple serialization types, each type can be tested in turn.</t>
        </section>
        <section anchor="checking-decoder-test">
          <name>Checking Decoder Test</name>
          <t>Checking decoders are described in <xref target="CheckingDecoder"/>.</t>
          <t>This test verifies that a checking decoder rejects encodings allowed by general serialization but non-conforming for the target serialization type.
It applies only to CBOR libraries that implement serialization conformance checking.</t>
          <t>Testing a checking decoder for a target serialization type is typically performed as follows: for each example, supply the decoder with every representation permitted under general serialization except those allowed for the target serialization type.
Decoding each such input must result in a conformance-checking error.</t>
          <t>General-serialization decoders are not tested in this way, since they must accept all valid serialization forms.</t>
        </section>
        <section anchor="NonChecking">
          <name>Non-Checking Decoder Test</name>
          <t>A non-checking decoder may accept encodings beyond what is required for the target serialization type.
For example, a preferred-plus decoder will often accept non-shortest-length arguments, even though it is not required to do so, and such encodings are not permitted under preferred-plus.
These examples can be used to test such extended decoding.</t>
          <t>Testing proceeds similarly to that for a checking decoder: inputs outside the target serialization type are supplied to the decoder.
The difference is that, for a non-checking decoder, many of these inputs may successfully decode rather than producing a conformance error.
When decoding does fail, the expected error is typically “unsupported.”</t>
          <t>Which encoding forms are accepted and which are rejected as unsupported is entirely dependent on the additional capabilities a CBOR library chooses to support and therefore not specified here.</t>
          <t>Note the following:</t>
          <ul spacing="normal">
            <li>
              <t>It is common for preferred-plus and deterministic decoders to accept non-shortest-length arguments.</t>
            </li>
            <li>
              <t>If the floating-point data type is supported, all serialization types described in this document require support for decoding half-precision representations and subnormals.</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="example-data-items">
        <name>Example Data Items</name>
        <t>These are available as individual files at <xref target="Examples-Repo"/>.</t>
        <t>All general serialization examples of strings, arrays and maps include indefinite-length encodings so as to provide full test cases.
CBOR libraries that don't support indefinite-length decoding can not claim to support general serialization even if they support most of the rest of general serialization.
For the purpose of classification by this document they are preferred-plus libraries with extra decoding features.
The extra decoding features can be tested as described in <xref target="NonChecking"/>.</t>
        <t>File: zero.edn</t>
        <artwork><![CDATA[
{
   "description": "The integer 0" ,
   "edn-representations" : ["0"] ,
   "general-serializations": [h'00',
                              h'1800',
                              h'190000',
                              h'1a00000000',
                              h'1b0000000000000000',
                              h'c2420000',
                              h'c240'],
   "preferred-plus-serializations": [h'00'],
   "deterministic-serialization": [h'00']
}
]]></artwork>
        <t>File: three.edn</t>
        <artwork><![CDATA[
{
   "description": "The integer 3" ,
   "edn-representations" : ["3"] ,
   "general-serializations": [h'03',
                              h'1803',
                              h'190003',
                              h'1a00000003',
                              h'1b0000000000000003',
                              h'c2420003' ],
   "preferred-plus-serializations": [h'03'],
   "deterministic-serialization": [h'03']
}
]]></artwork>
        <t>File: minus_twenty_five.edn</t>
        <artwork><![CDATA[
{
   "description": "The integer -25",
   "edn-representations" : ["-25"],
   "general-serializations": [h'3818',
                              h'390018',
                              h'3a00000018',
                              h'3b0000000000000018',
                              h'c3420018' ],
   "preferred-plus-serializations": [h'3818'],
   "deterministic-serialization": [h'3818']
}
]]></artwork>
        <t>File: 65_bit_neg.edn</t>
        <artwork><![CDATA[
{
   "description": "Largest negative integer" ,
   "edn-representations" : ["-18446744073709551616"] ,
   "general-serializations": [h'3bffffffffffffffff',
                              h'c348ffffffffffffffff'],
   "preferred-plus-serializations": [h'3bffffffffffffffff'],
   "deterministic-serialization": [h'3bffffffffffffffff']
}
]]></artwork>
        <t>File: byte_string.edn</t>
        <artwork><![CDATA[
{
   "description": "The byte string of length 3: 0x010203",
   "edn-representations" : ["h'010203'"],
   "general-serializations": [h'43010203',
                              h'5f4101420203ff',
                              h'5f5801015a000000020203ff'],
   "preferred-plus-serializations": [h'43010203'],
   "deterministic-serialization": [h'43010203']
}
]]></artwork>
        <t>File: text_string.edn</t>
        <artwork><![CDATA[
{
   "description": "The text string 'hi there'",
   "edn-representations" : ["\"hi there\""],
   "general-serializations": [
     h'686869207468657265',
     h'7f686869207468657265ff',
     h'7f64686920746468657265ff',
     h'7f790004686920747b000000000000000468657265ff'],
   "preferred-plus-serializations": [
     h'686869207468657265'],
   "deterministic-serialization": [
     h'686869207468657265']
}
]]></artwork>
        <t>File: array.edn</t>
        <artwork><![CDATA[
{
   "description": "The array [1, 2, 3]",
   "edn-representations" : ["[1, 2, 3]"],
   "general-serializations": [h'83010203',
                              h'9f010203ff' ],
   "preferred-plus-serializations": [h'83010203'],
   "deterministic-serialization": [h'83010203']
}
]]></artwork>
        <t>File: map.edn</t>
        <t>Note that map order is not significant in the CBOR data model.
Maps are only sorted to provide deterministic encoding.</t>
        <artwork><![CDATA[
{
  "description": "Map with three items using integer map keys",
  "edn-representations" : [
    "{1:\"x\", 2:\"y\", 3:\"z\"}",
    "{1:\"x\", 3:\"z\", 2:\"y\"}",
    "{2:\"y\", 3:\"z\", 1:\"x\"}",
    "{2:\"y\", 1:\"x\", 3:\"z\"}",
    "{3:\"z\", 1:\"x\", 2:\"y\"}",
    "{3:\"z\", 2:\"y\", 1:\"x\"}" ],
  "general-serializations": [
     h'a301617802617903617a',
     h'a301617803617a026179',
     h'a302617903617a016178',
     h'a302617901617803617a',
     h'a303617a016178026179',
     h'a303617a026179016178',
     h'bf03617a026179016178ff',
     h'a31a00000003617a19000261791b00000000000000016178'],
  "preferred-plus-serializations": [ 
     h'a301617802617903617a',
     h'a301617803617a026179',
     h'a302617903617a016178',
     h'a302617901617803617a',
     h'a303617a016178026179',
     h'a303617a026179016178'],
  "deterministic-serialization": [
    h'a301617802617903617a']
}
]]></artwork>
        <t>File: map_strings.edn</t>
        <artwork><![CDATA[
{
  "description": "Three item map with string keys",
  "edn-representations" : [
     "{\"abc\": 1, \"def\": 2, \"ghi\": 3}",
     "{\"abc\": 1, \"ghi\": 3, \"def\": 2}",
     "{\"def\": 2, \"abc\": 1, \"ghi\": 3}",
     "{\"def\": 2, \"ghi\": 3, \"abc\": 1}",
     "{\"ghi\": 3, \"abc\": 1, \"def\": 2}",
     "{\"ghi\": 3, \"def\": 2, \"abc\": 1}" ],
  "general-serializations": [
     h'a3636162630163646566026367686903',
     h'a3636162630163676869036364656602',
     h'a3636465660263616263016367686903',
     h'a3636465660263676869036361626301',
     h'a3636768690363616263016364656602',
     h'a3636768690363646566026361626301',
     h'bf636162630163646566026367686903ff',
     h'bf7f6161626263ff017f6264656166ff027f63676869ff03ff'],
  "preferred-plus-serializations": [ 
    h'a3636162630163646566026367686903',
    h'a3636162630163676869036364656602',
    h'a3636465660263616263016367686903',
    h'a3636465660263676869036361626301',
    h'a3636768690363616263016364656602',
    h'a3636768690363646566026361626301'],
  "deterministic-serialization": [
    h'a3636162630163646566026367686903' ]
}
]]></artwork>
        <t>File: positive_bignum.edn</t>
        <t>Note that bignums are included in the test data because preferred-plus serialization requires their unification with integers.</t>
        <artwork><![CDATA[
{
  "description": "A positive bignum",
  "edn-representations" : ["79228162514264337593543950335"],
  "general-serializations": [h'c24cffffffffffffffffffffffff',
                             h'c24e0000ffffffffffffffffffffffff' ],
  "preferred-plus-serializations": [h'c24cffffffffffffffffffffffff'],
  "deterministic-serialization":  [h'c24cffffffffffffffffffffffff']
}
]]></artwork>
        <t>File: negative_bignum.edn</t>
        <t>Note that this is the value closest that can be represented as a bignum, not a type 1 integer for preferred-plus serialization.</t>
        <artwork><![CDATA[
{
   "description": "Negative bignum on boundary with type 1 integer",
   "edn-representations" : ["-18446744073709551617"],
   "general-serializations": [
     h'c349010000000000000000',
     h'c34c000000010000000000000000',
     h'c35f450000000001480000000000000000ff'],
   "preferred-plus-serializations": [
     h'c349010000000000000000'],
   "deterministic-serialization":  [
    h'c349010000000000000000']
}
]]></artwork>
        <t>File: date_epoch_tag.edn</t>
        <t>Note that this is provided as a test case for tags.
There are no requirements for dates in this document.
The tag content in this example does vary by serialization type.</t>
        <artwork><![CDATA[
{
   "description": "An epoch date tag" ,
   "edn-representations" : ["1(1776614355)"] ,
   "general-serializations": [h'c11a69e4fbd3',
                              h'd8011a69e4fbd3',
                              h'd900011a69e4fbd3',
                              h'da000000011a69e4fbd3',
                              h'db00000000000000011a69e4fbd3',
                              h'c11b0000000069e4fbd3'],
   "preferred-plus-serializations": [h'c11a69e4fbd3'],
   "deterministic-serialization":   [h'c11a69e4fbd3']
}

]]></artwork>
        <t>File: date_string_tag.edn</t>
        <t>Note that this is provided as a test case for tags.
There are no requirements for dates in this document.
The tag content in this example does vary by serialization type.</t>
        <artwork><![CDATA[
{
  "description": "A date string tag" ,
  "edn-representations" : ["0(\"2026-04-19T03:59:15Z\")"] ,
  "general-serializations": [
    h'c074323032362d30342d31395430333a35393a31355a',
    h'd80074323032362d30342d31395430333a35393a31355a',
    h'd9000074323032362d30342d31395430333a35393a31355a',
    h'da0000000074323032362d30342d31395430333a35393a31355a',
    h'db000000000000000074323032362d30342d31395430333a35393a31355a',
    h'c07f74323032362d30342d31395430333a35393a31355aff',
    h'c07f6232307232362d30342d31395430333a35393a31355aff'],
  "preferred-plus-serializations": [
    h'c074323032362d30342d31395430333a35393a31355a'],
  "deterministic-serialization":  [
    h'c074323032362d30342d31395430333a35393a31355a']
}

]]></artwork>
        <t>File: true.edn</t>
        <artwork><![CDATA[
{
   "description": "The simple value 'true'" ,
   "edn-representations" : ["true"] ,
   "general-serializations": [h'f5'],
   "preferred-plus-serializations": [h'f5'],
   "deterministic-serialization": [h'f5']
}
]]></artwork>
        <t>File: simple111.edn</t>
        <t>Note that the simple value 111 is of not particular significance.
It was selected because it is an unassigned simple value.</t>
        <artwork><![CDATA[
{
   "description": "The simple value 111" ,
   "edn-representations" : ["simple(111)"] ,
   "general-serializations": [h'f86f'],
   "preferred-plus-serializations": [h'f86f'],
   "deterministic-serialization": [h'f86f']
}
]]></artwork>
        <t>File: float_zero.edn</t>
        <artwork><![CDATA[
{
   "description": "Floating-point positive zero",
   "edn-representations" : ["0.0"] ,
   "general-serializations": [h'f90000',
                              h'fa00000000',
                              h'fb0000000000000000'],
   "preferred-plus-serializations": [h'f90000'],
   "deterministic-serialization": [h'f90000']
}
]]></artwork>
        <t>File: float_double.edn</t>
        <artwork><![CDATA[
{
   "description": "Double-precision normal float" ,
   "edn-representations" : ["1.7976931348623157e+308"] ,
   "general-serializations": [h'fb7fefffffffffffff'],
   "preferred-plus-serializations": [h'fb7fefffffffffffff'],
   "deterministic-serialization": [h'fb7fefffffffffffff']
}
]]></artwork>
        <t>File: float_double_subnormal.edn</t>
        <t>Note that full subnormal support is required for all serializations defined in this document.</t>
        <artwork><![CDATA[
{
   "description": "Double-precision negative subnormal float",
   "edn-representations": ["-5.0e-324"],
   "general-serializations": [h'fb8000000000000001' ],
   "preferred-plus-serializations": [h'fb8000000000000001' ],
   "deterministic-serialization": [h'fb8000000000000001']
}
]]></artwork>
        <t>File: float_single.edn</t>
        <artwork><![CDATA[
{
   "description": "Single-precision normal float" ,
   "edn-representations" : ["-16777216.0"] ,
   "general-serializations": [h'fbc170000000000000',
                              h'facb800000'],
   "preferred-plus-serializations": [h'facb800000'],
   "deterministic-serialization": [h'facb800000']
}
]]></artwork>
        <t>File: float_single_subnormal.edn</t>
        <artwork><![CDATA[
{
   "description": "Single-precision subnormal float" ,
   "edn-representations" : ["5.8774717541114375E-39"] ,
   "general-serializations": [h'fb3800000000000000',
                              h'fa00400000' ],
   "preferred-plus-serializations": [h'fa00400000'],
   "deterministic-serialization": [h'fa00400000']
}
]]></artwork>
        <t>File: float_half.edn</t>
        <artwork><![CDATA[
{
   "description": "half-precision normal float" ,
   "edn-representations" : ["65504.0"] ,
   "general-serializations": [h'fb40effc0000000000',
                              h'fa477fe000',
                              h'f97bff' ],
   "preferred-plus-serializations": [h'f97bff'],
   "deterministic-serialization": [h'f97bff']
}

]]></artwork>
        <t>File: float_half_subnormal.edn</t>
        <artwork><![CDATA[
{
   "description": "Half-precision subnormal float" ,
   "edn-representations" : ["3.0517578125E-5"] ,
   "general-serializations": [h'fb3f00000000000000',
                              h'fa38000000',
                              h'f90200' ],
   "preferred-plus-serializations": [h'f90200'],
   "deterministic-serialization": [h'f90200']
}
]]></artwork>
        <t>File: float_neg_infinity.edn</t>
        <artwork><![CDATA[
{
  "description": "Negative Infinity",
  "edn-representations" : ["-Infinity"] ,
  "general-serializations": [h'f9fc00',
                             h'faff800000',
                             h'fbfff0000000000000'],
  "preferred-plus-serializations": [h'f9fc00'],
  "deterministic-serialization": [h'f9fc00']
}
]]></artwork>
        <t>File: float_quiet_nan.edn</t>
        <artwork><![CDATA[
{
  "description": "Floating-point quiet NaN",
  "edn-representations" : ["NaN"] ,
  "general-serializations": [h'f97e00',
                             h'fa7fc00000',
                             h'fb7ff8000000000000'],
  "preferred-plus-serializations": [h'f97e00'],
  "deterministic-serialization": [h'f97e00']
}
]]></artwork>
        <t>File: float_nan_payload.edn</t>
        <t>The NaN payload is a special case.
For preferred-plus and deterministic serialization, the decode should fail.
For general serialization a NaN with a payload should be returned, but there is no EDN representation for that.</t>
        <artwork><![CDATA[
{
  "description": " Floating-point NaN payload/significand is 0x1ff",
  "edn-representations" : [] ,
  "general-serializations": [h'f97dff',
                             h'fa7fbfe000',
                             h'fb7ff7fc0000000000'],
  "preferred-plus-serializations": [],
  "deterministic-serialization": []
}
]]></artwork>
      </section>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
      <name>Contributors</name>
      <contact initials="J." surname="Hildebrand" fullname="Joe Hildebrand">
        <organization/>
        <address>
          <email>hildjj@cursive.net</email>
        </address>
      </contact>
      <contact initials="V." surname="Goncharov" fullname="Vadim Goncharov">
        <organization/>
        <address>
          <email>vadimnuclight@gmail.com</email>
        </address>
      </contact>
      <contact initials="K." surname="Takayama" fullname="Ken Takayama">
        <organization/>
        <address>
          <email>ken.takayama.ietf@gmail.com</email>
        </address>
      </contact>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIALeY+moAA9W923LbWJYg+s6vwJEjylImSZO6WnJldcuynKkeW/ZYcmd3
V9Z4QBIUUSYBFgFKZjvdUb8xETMR5/X8xpk/qS+Zdd03ACSV3XNOjKoiLZHA
vqy99rpfOp1O6/4sOmi1yrScJmfRxct3H6KbZJHG0/Rf4zLNsyjORtGrpEwW
szRLi1krHgwWyX3do61RPsziGQwzWsTjspMm5bgzHOSLTuE+1pnGZVKUrWFc
nkVFOWot5yP85Cx6fnp42mq18K+z1jDPiiQrlvB5uVgmraJcJPHsLLq6vH3d
SucL+rgo93u9095+K4Yvz6Jo53w+n6ZDmqegpX9I4mnnNp0lO62HfPH5bpEv
57z41udkBR+NziJcY+s+yZYwbQQ/7kP4d7maw6Z+htfT7C76Eb+lz2dxOuW3
/x732s0Xd/R5vBhOzqKdSVnOi7Nnz/Ax/Ci9T7r63DP84NlgkT8UyTMc4dkO
T52Wk+UAXia4Pdw9WwvKHYBWK16Wk3xx1upEaQbAetON3iyz0WAajxIYkg/k
TbxcJNkw8b6CZZzBCQ6Xi7RcRbeTJF+sojdvLuCrhLc2vZv+fSEPlPR9d5jP
YE44nHKRDpYlT8yT/EOeRD+l01EyWADk7SgT+OzPf/57GKZAEGRJaV75x3iU
zqIf82w4iRf5vX3nHr/IlsNpejcp//4OP6Sp9cX/lGTRbfw5XsWz2L71Ocm6
pXxKoHbebGX5YgZQu6dD/vD6ArFNzl4+OO734IPRaIofXF1eXp4cHTJGlPHi
LgF01SNNkyT5Mp/mCzzRJKETBexfzpKsfPb85Ph4f/+UX+R7hYNFNyWAJV6M
onG+iF5Pc1hMdtd5n6dZGZ0DiCezpEyHjEFypvh7hw8Kh6C/6XpE43haJPQ3
YkRSpNk45+cjnQ0wGzbQ2e/1T+WLV++uzqJ+r9vv906f4VM3t6+6+H1X14wb
P78+7yIUzuxfiHllfFfARy2cyYEkQe7gdB/uy8+3Lfng9LB/cGb+6B3ht+9u
LvWTkx6Anv64/BLP5tOk6HxI5rp+gdlazOcnXTBZON2+ZuL084/8RQiwymny
pUMsebbVtXsGpCjBa509S2T9tJmL2/P3+/4mLqYpoER0m0fnsFb4FYkTHP/7
RV7mw3wa3e/Xr2mcjvJ4Ok1juLWEXsU8GRb0ced+v9vrzAs62V7/oMefDmmq
Tpl3YneqzlymqrzWnZSzaTMgfz64qMIPP7mOr1/mXwB3g60iyJBAXmXALeYL
5BlFzfBRR/6NovFyOuX7/CEfJIsyul4BmYfL6sz7D8vpqh3t9/b79YAayrSp
MysdZT4v05mcGG31SRZnnQGtnPZx1XnVnQHHmk5XnZHhcAA2OnLGz49v3/i7
fPf2x+hjlo7TZBS9zUfJFHf8Js7ulvFdEu3S12/f7EX/CMtA9rnfPer23f28
SobJDDaLe+qf1O/p4eGhm8/uzLk/gyGf0UjP3r96TQt7c/725OAMb3SXLvTh
0bOD4/2Dk6Mu/vP8lFd/fXXx7tVl5/rdh7dnLj2CHQxh8dE13mTD6l/DX0WF
/iBCEGf5T93o5wkAaJoszAlaaux9xVuFQzvq9E46B71aIoq7XPJCaKcLIAGL
soDb1T961kDadOGGlp5nWfIF+OWT/hFww06nE8UDwKF4WLZaQGlIpohGyTjN
koLIQjuKQepwKLFebTxIWHdM7L6IiuVwEsVFhHh1B4fZhrcW8Az8gnJFvFjE
K/o2j4CzwppG0WAFYky3RcTHIxhRWkTjafIlHUwTeH06zR+C2WCUQWIGSrNo
tpyWKVCW6AGnga/jISD1LEfIwn6A96yQ2eCjKCnBjmGHIxjhPl3kGX4FK2nd
wqFEyphwsYt8tBzifJMkQoyP/vbX/36XZMkinvpL/ttf/wdBBx/EawrfllE+
5iUiGKI5XpiypH1HCmoGDjEIuFYG8OVDHiEiw70Z+vMAS4FLO04Wi2TUmU+X
hf91O3qYpHAQo3QMzwAUgTpE5oUAynkGUyJA4gLmXIBMCH/jgpdIGxiuc0SN
FCQhXCcAZ5EgWJMMwY77BZEsHkXLInnRwic8ulC/tGn6OXlIi8SsUZdRswBe
GW1iCMJDMLzCVsBG61XAVg5TpGbzQPQAXAxwO0seosUSEKecxCUsDs6oiCb5
A30BPJwHT1lCHsYg4MOqhyUdNGEuYeUMSVtlTmAl9+kIJh2CQItnKYI2oKdZ
xiK5g5uFuxikd9lyxmL4WMWdOYk7wEKiCXyO1BMvRA6P0/oVFwfxkGR1PCSV
N+iEwzOwEJwx7tEe8CZ2+L5GD4t4PodfYDdEH2YpyDbAyZ4go6L7QEN/feL+
+Q2+xwfs1ETs29ErhA79TrP5utLXJwS3At4Gjg+LB3QozaKKil7lLT4tn8JB
JdM5XDeE6AiRAvhKWkyANpQPCRBZPCQFEVz7YTKHw4VbCcfogmnGa42ds2Tg
eEvowukmgLeApoL2ZkjCHUQOIEoxqlSAjLCkHOZfBPsohpNkBiiB1yD6h5t3
1zTR+c11tw8Qj36N4P8VOMJnDiB/DcD4K752LmQcP3iT3NNjt/k8muLvL3Sp
yxg/RyXPEIGxBwq4QgQEGAxOFrQgxkeH9MJUQxqHyLehwUT8QJEpZmlRmFWJ
vIprIQo6AyoY47A4b5GDBD9BnIMxQ5SHqwBcH64HUK8CpTN4rAzGgPFldkIY
PNiGYWgxygRxD0n3rtuOvn4FSeHbN/j74tWrN/BnBwV5/gBHxA9AtsEPcIAr
3AvebIbVB12bHEPkaNNw6rMYZcoi2kWmD2wQeHcJ/xj2UxZ7+M77KwD6fFki
wtCkDNEFYAgohgsQ5vJlid8TGWSSk3hPhHBAdpjMUDuFM6k7l69n0ZMyHnT4
9rGQ88POI2/vDtxaXk2eFNlTQ+1A8h2mUyCYSLlh8spFK+giregeITDhC1g5
3JSEngf+AlAu4dYWjHuoPCdfyq5OJzwyjuYxPFcSKg3iAhgCIShQhmw4XY4U
YZYFIqsVS2oRxBNXSFRhAjCL57Dcyy8lczy+AbN4hRedDxJuCWI/nk1J5MFZ
ilIM/gjHS/yREATAO4lYmOFo1ZYSMVrT1lU16bZAeoRbleUlXJC/LFPglW1G
YVmbDgrMZ7hIB0ntmHa4Ft1OWlKahc/iIpWGwahw+5x7gQtfJChkJQ4KIu8A
fvBaZLjA7tUSLC358EnyISGvsGLcPTwe0F+i3Li2Au4TLzAFatBtgRweiWLZ
pgfoBKNf/tgHpeGXPylhdvaANwTlCaDbyCRJagQFBqgUwCDyfoDyEgznhMBb
/djr+JJIpH7c+rVT/an7bMNPwyswPqyVhJWkM02yO5APIqG8DBH5cHd/D0U5
PbCYMW6QgE6YMTXufXkO2lZv399WCznTKJjBHR8GZQYdi5hL4wJ6fCZmEe32
vozHezT+6RjHH4+98ZUu0WhoQ1DSRCf5pyicm2TSyop8pEEydQNSHUhgolMg
cQIx8wvIC0yhZnlRCq+2Ep1cYJbo3BdRwAM1doBMSE3A9FkB8hvfOkJmR/Rn
baVIpgkRC1RNWOSDLxBEDkugPcmdJq1Ermq8AF6yxE04KkuA+htAgasslmkp
zJoNxLiKKSqaVkNrVJBQgk8WTEvKvASqKtPAwEiKPmf5A0kQ8eie7DCtizy7
B+KaoEli/dpm8WckPmWUAK3Eg8+Fy0UFqkZbrK7b2tWzwMUAt/3LMmFyRnoL
itkviLsgQSOBCwTIl5cfrB6BekDR3QMCBXQ4RbrU5vMV6vS72SguJi+Ykt+D
fJl8ASWttF+QHIhiTZR6okIB0jpsAtdVLOeotuOQAQjuQUeIaSMsFk6LXJTG
gr+jp3bhKvS7PWZPvW4/6VsZyVJH5mp77WgAgoOuEpYMMgFsv2AAk0aR0EpQ
CiyBB6Zo9MZR7IQpab/CnCdLkGpgwngUy3WAW4AXhygpPgHnRxzZB8AGvfun
/AEXx9B+Gtw3RwsHtXg4gfUCBqEDhGxYOYqD8mygJDAbesIWNuc55neVt83Q
gG0pKp6DZBgDJ+Xbh0JEcKikCQDhcHR7ZvJzuujB9QQAqWiHXHrOu2JdpELZ
iJ4SOuGtpbPNUUERyY8RjVFJNOjaIQC4L3GBdAd0doaS/L5IGLuZYBvGDqB7
xY/QpXPoTz4Gvm3QmKYGdWE5EIOHj9Mo+jnXYzUH8RjZvUJWlVoHBEJUCtw4
MWkWCL/QskmYg/eFQgLZXYF0jcIV7GFoNcVhPl+RDkvkG/dO5hR6F91juKcL
4R/Rh2VR/u2v/w3pxqeirKd5MBfsCWUZkRNdqxYAMYMBSroYKQLkHn1Y8DSA
8TWKhnBrVtEqiRdEz0WOVaMUzJEQ8XToRz1pYK2xgi6MiUhdyOaFR4ICoOze
kFZC1TESWNwHrn8AUvY4RbgwwUXJGk6TRwkVV2AdBAC85apUwzSwRWOdV5tV
bM0lZHtKmKykgbXqhdFgwpuFb84Xab4APeJfE4NtpE+gJvD163s1ar2fLgtP
vgSp1NjRCJ7ul2fROvOZEgzXgUu0wiEqzWSCySSpNaE10sietQIsziBkIjTR
jQOBFuXZeJDfw4MTZEkIVIvlJNPDGc0QrQmPVMYXWEzgHqJWiLJKKLG/RRyN
5/BGPJywjXWNOY/2Oc+Lgo20CbwTiQtBBAy27yHpci4UG2KMtAOPxY7S7Ao+
XcsVYmLpSF1x5+3/yBtyVRoGN0ZiI/bO4EIAX7ybhubH/+3XA90IJVAUxALe
D6u0KRBhELQajKEkxPx7btYrd9zH3Kw14BGF8GMmIEhGoU5I2IeY2AFtGdVM
Rdy2cS1c/HyLDAr++fYN9XXUOrM8gJmLQsbknMT3sGbg9Rl8AgtHnuvLJ1mS
jPimMkAAM/A64ZTKKlXTFu9CMi9rGDdeaDQyWMb/d63Wu0ykDfS3mYttleiU
4dlGXwzeFwSFhytth/UjMxMBw1kJy3a1dwLvi4gSbKQUwRpmYetbioxrmKT3
qPDYVdmjRg3I8WmYu4Ym6BwEzIz1iLR8wQ83eVDQEBbt1PpPdgQDkXB9/foj
PxIgHyDRlfVItNFKz/RhpJIKjoFHhrzNKnQhRokIk4PI5uN/VQaxAxmB2NJ7
Jc4jJKIipYAcyaK5CFuF1fZILsjTEb4ERP/cioMJCo8NUtBDvpyOANlRfxiw
b2mFJBQlK/IGrBIkavjQGISOKL6LkWzIpVHQCIsw3hzgA+pvob2MlHEUrDIA
ZGZJnBVVIRkEIZI4cQ33bMDxdICc7UcBqcMtgxooGPZBnUj8LeAawBAGLhJl
aEQtPiRTRmTHX8L8OaAdvtdF8RYdOIEByV0oOYSYouZFwnhnhF8aUXkhnBNS
dsbhZmqjTskvc9oKyNjwzbBk55aJpoFZYC/7/f4pbHuqjnDEGH5dfVkIWjof
1WB1f+HifCeTKEEFkjcQ7OBPwmwldoSQ2ch6r/Ag0DC9ioCzsvuSvEtIycUu
GMBQF2iEHeO9BIAz9pRo3mX2D3yoLKeJ50okYynRYVoCcyo0F8dTFKAdnlVj
2wOxZ4HxcFbNueNjd7yBbPMc8ZneJOwUOez28cY6NPcBwDZ1ZlOXJorJZjSj
LLHrjb2gRoiLhRMa3iBGrzUw67ZuEsICwe7b3IiyROIIwW9j0TCsBb5o8mg6
fMQaM/EGb+/MtNZetll7zyGZw+Xs04IOol1xVO758D3oHnYPXAjDeMjpGVpi
fyezmtqY2fVItnHiCfCvXYiwEsR0UU9jZMiwvw4ImXjNkO+pW866cckUskB2
75iw3e0ogcSwyoUsUsRPOLxltsBzQd7qg0tliRlG2LGvcobCIctj1ttDWuoc
OSV/A+u5T3NQNFgWRLp2YSinnLGdhW/cZ7g+GGpZRDtvP97c7rT53+j6Hf3+
4fI/f7z6cPkKf7/56fzNG/NLS564+endxzev7G/2zYt3b99eXr/il+HTyPuo
tfP2/J93GM133r2/vXp3ff5mp0KC6NozubJhRHhALe/uvbx4///+3/1DwJH/
y5I8/uN5/+QQ/gDdOuPZSCTnP5F6tIC8gbZMxkRgfMN4DtI1yoKABKj4ZHKV
Wt/9ESHzp7Po94PhvH/4B/kAN+x9qDDzPiSYVT+pvMxArPmoZhoDTe/zANL+
es//2ftb4e58+Pu/myKudfrP/+4PGMOKvNFjodHNcjZDcf/rk5C5EsoZFeTG
58tfn+g3/hffmAy9XgCRwzhgMwC+Yj41H35DM4c+auUsQhPirkQkc2II+dxi
fjwF7MmIL+IFw4iGisAxSkBsJ1KsogV60BZiKCexFQ1qFGtM1t2SzBvDSQ68
xrjg7KLI65zOEjaMRCLIwffjdKpaL6l9NaKPw+zJhK4hOjAIzNQEAjujvR7I
OPJ8Osi/oA48WKZT3GJnMM2Hn13dB1gDeg2s5rfIp8R24OspU16i0ItkWZD6
OUuGIN2kxcyXdgBmGOoI/9jRuy2QldsUadqOLs9vnYAQ4BvJdEyr15BNnGVc
3SEK5aRDO+jNx40k2RG/a94lhRzYL2LIGrmKzXTo0004GK2kL1QvPGu1/hCJ
eCtY7vsWVecs1muLRk3yH9GwjlE8F5ULpPQURC50K/t27D9ElzVgjnbzhcGv
PZ6CzUXukhnUVq/jRa8qanQDsJMvJTCgWiDT94SHsAAk3gPU2fxN7nI8BODD
XpWqR+mYRTr0xLP9no0VehKwrHN7k9FrssXZA9nbfPahh8t1W5OnBxVAD24D
DfdjHtTkdBCz7iyew7EvWPmiK0mDZRh53yYtKF6h8VbCCJvNP0gOkFOF5hYU
yRYj9rckKJChb7TJ+cN0pssGg2IIascizQPzO9rPmfqsWw7yzRqon5FGSMa/
NBOBBkkqjU/Of6a2sH7WMiUiwY2FcmIJGNxoUwToilURIxFcwiOxJ6WjasFx
wpgS/cnC8M/A+T27E4rCePRGjaVFw4TjZcbyJmjVrF6xXlDdbDRbFkYyXx+Z
KHbMFYshdJaOS4MgZGIlkFySWJpZvASREWReEhuXcwb/16/4YNWCQXxVyAT8
4zFW+Ps2h/+4fLWWotBtNpY0ghEbeEKWhessiiVqJihc8TXGt12lB5GFjBTo
tGUuLFKtKxNg0Ak5fuhAHFJLhLkQvg40cZxQdFbRtrNZx49xgpeTRb68m6DL
ZMoSfZbc5WUqc90sWbX1LDaT+F7VzRrvHRpgKP4f37sDdCDzcr64A3b4r2KT
74DgPSJTD70doSaJiIneXKQ2t29u2tFPt7fvmRe+vnr1rsIE61lp6zp5qP0q
InnUmpJ9q3GJWHMnrj7M31oYO0NVylkWnlQSegtEX58vUhIFXR5h5iEiZ60R
1pW21i9iPHhieLKIEjhiLkVtRpMOrDz49lWi33ZbH2ha1teb6diaeT1yUZnX
+9bOawYkvRIYvgskvSEeh+Eo/EQ0lLjcgovAQSsPQc5YK3wx+xP7vgqcaFgD
1UZcleRICdh0QdTyhh/wiEvx7dteF+2jdEEpcJoYGGEfJl+hNcgIQ2ylsG5r
f5pBAjctzRfIX0GGLhCbKG4f0bNy8+p4tGBv6oa9wwiMwGsjQdr+CdDyFUXF
1MK3oaAYvHhO94A8JGKxaTDK41GwybpOHGmvRUOJqjNWHuQQyDOLkD3ADnEJ
yBJJY2GeSJ7oNYyuCUdosetlVsTj2SC9W+ZL2OFVIH2gPz6g16K4UljDuhu/
zKYYgElhUnxL1V1dcLQIU2Ogn3AAKUkAsePyU2NfdU10iOOcQqSyJCVJAXmp
M5CxFGaUUeGmHQgI0uIzmbsliMqiZKlGljdqVWwRepKIkGsmSWE0p8yaH9uW
KeIza6HDxnHROptpYMmmtBhYT0RKAFNmvV/sJnItjePlFNSEac2oDg1j4Y//
7GpwG8pB3vrX4rO//CZS+u9bfhMJ9pfPAhEpnc6RNWg5gb3Y7HeTU//9urMM
slrUu5OWGjBn3LoIj1n855zM7BLHETqXuqAKFXnbNXi31+MSOvTgRt/HUwnz
acrX2W0yZu/ZMEZcORF/oypW2FwdJNk0sw5l9KYWRN1RiGPCy3Gx+YJN4QZf
2FLnRyDsjl0+geLxniHt6Htmi/h94sGgNskJJ2J+PBqlInY6ZHGzelSowMUR
EBjmTSGa6FvQuJmA5pDCC4wfrdiM+I4cYLSpQBRI4oJYp8VUHwjvV6ASwYZ+
zFng/LAcrPYo9qp58b5tZEFC5XKOYZairaCORRzKg+ELjSLXyADWGHRhJoqs
eWIbJVHAB4Wx7QeAqk5duY/n/kpQFiI0tWAi1BGdOi44fhE2V+s7VrGo3mu8
x+serNiNR+TfcfoGdhK8P43yV7FZACNqZggZp65Xjagt1qXqVHRf6aLkCjKT
qREibkgMbDu3WVzpwuq3pZKeFEeBDzVz+1OSxax6VTgFijQNHMcsrBuaiWoB
4GKFXftG7CQjFdE7kLhE0EOJ2kn+dK6s+PXIqnCXx0i37an5N8NIKeukDp6P
QwVCG1DFhLDm9AXUIY/wo1qs+987dBKpOLjgNem4mEyH7IdDqI3AShaMLewi
9eYWlWRrzBvqI+PQNPQ7ulMVGw1ozC9omQCGNjObuisywXiHtonrQagXILE6
xj4VLPyrWGd3WWNi8eyxFG603vvfoCC1NY1pw6G1rsZRvam+iShsWlS7jj6T
capqavrmXtuQlpxtSUXWqg1bKgzBPfzfrSpEwjYquam17ESc8KJAoHGNqM3G
6CaT6cHJbdX0cM2x1/wkx7HuSHpefJZiAU0s4YMlHjkZ1lLKMSDTHG67ZDty
QfopXKwdieICVJvCgiluhteyg7FJq5DUP0wSgr+Ta+37hJF7TIuELCJtk7hA
ZNvucrSIHzLNluMFd1s/1jJ1LywzFHGSGW5Owzc9txrjC3qFvpPkDYkQkcxf
mwblSWJukEJPFX6TIlVEvS+9Xhv+238u/572ej1JwwA2mGfA/L+zZWo4uRBk
+mXiZVo1zt/r9tTV5Mw6iafjTlviT+EXlGvzJQjeHbiFwxQTOmleCvI3Zo+m
xKjmDMfvorcoAhMT+5xwog0ulXwXNAHFfNhUExPFKFs0TiaS4+xjqCOwTYQU
J0ky7NHU/RAENQCgDDKeu/dluH/Y7/X2SIDUcMjhNE5ncrdVrquXEsmUJOGS
NgWCJEzNeME4DYusqvI5yc82YlCD1F6JfhyEpNVc0xojnCrXRol2VOPAD3ad
S7BmRovAuHIOZfVF6TCOlVCmIebVSwLlE7xDT/wGk5OZYpQDDG6QZ2PYFrLg
Ej3qXnIoTimqhg1hncTF5uPiMDVeuAZKYiDqIknUlIgYKmSsGwYBKtTjEaio
jnfEhOAq+mcrPzyOuBSdFzGcGrmYvOQo2Ji4U+vfGOVellc1oLOt8XfpwsaI
yluaEiTigL8jSwzN3jCDrwF8dO50g6s1CESwEuTrUjJFbRDIN0NZWZqrF0eq
spJEc4az2rxsHEx5MR6II+Rx7GyNQFbvxqaYdbyHJFLf5tFHwIsmjo7PyHfA
yBvZjgTGGtu3EHkvUt5JM0RbdAy8aK2RaXd9xgol5FL0inpbNbfLFJQJio1E
uxwBB6vIOkDY7zGJ5zq+Bj2fdVQsO4WxdaiXtkVjX2lS/H1clBVTlmc8uiVb
F6aRqB+afR31lxWjKZGrsD+xqNAVufFuUZ5JejcxTmZ10PN9aLckJ3lImblj
oT8sT8qVMbmYRQH3Q13/ng5g884srZEcSMlbCbNt5sY+4S/faDD1u7dEl+Xx
3KH1fBwqy9UK3khFE+GcYnuo2B2abQ6qdHGQcuSW8eLLNMYMLwDtqhKzJPV1
NIzfQpkQrn6vlrKJuU/iy1uBRRElKEBNFBpJI3jAuiybiL5QplBKrskpbOuB
F4nUf4m5KAvq6TEmZ3FQl3HPtjAITi8o3sAKdVhzPwOp35agCPAgRkzcWWtm
2dlgjbbBSkgkKa3KyB9O1j6qSZ8TUe/4knC1rtThfSpmSE0oK8ZUZQGlN21S
pPgFA0eR8RzhR2IkUFzIaEzKZwhzfi23NlnPWOJhOBF7scSGK/nBSKPSCYnS
W/ciVDnNHRf9AqFgRagxyzsKCJPQE2TjRpwxQ6YRT4TiCF8vwdVRDlB4hQ31
e24CKMwpMrZ8WeEGkkGOSg/HyBuSQgSGjbYy2iCJQtFdhaG2hukTm4Lj8RUX
OigT4O8VfSBM8mum8ZsppTZjNE635TqTApjPp/GQRUPX0C4hmYIpZPdlrYSi
BeuUobrd09p47XpqvMxgwRQ4RFE6FORu6LunRRx1T497h8eHhycnRwenveP9
o8vOc3aEUDamo1zErF/ZRRfLAYVGTDUd0oofFCeKuEBGKnuXnPBltFypsc/c
HY1/TVYcAX7lyprIOBzDkaBC4pjo+TVfHHAnp3lkEXYfGnoeXKS2FarxotXm
OESzhGPXAz9zpgr7kHnkuc0wzEpbD87JfOSaB07oj9woLrfBpn2PJo0ERUSi
uxSh/4O7joBMG2dlq9XvUiUSzQ8hNqGn4dkBjBG/xr6yx1qiVNDpYhVFkcJV
nZjPJVDdDozhBSz01GG8DOK6n32pGtMwdGmI5LEhvS65h0F24nRHs08cx5dT
YKktCTwPHQ46PALd2QYpBHcdRvwu6nW7+wduNRihC5TdQkVbRAm36nuX39w/
hFePjtx32Qaeeavjwi9xGv1AxpM9ffvouNs9Pjo6qA6AVR6CAQo7wqmOgC/D
GIf7p4enxyf7p9WBxvlysWakWEcyQ8Bw/eeHh8cnh4e9k4OT3unRUf+4Xx04
IQ7RPPIATRSAj2E1HnPhXCRjM0PyheV+ApcYah47CHkxLVfi132L1Jkc+z8y
R9chwsPXO4RhNWRuUhMUqZUB0RQJWSw+hegXSMyFXne5GOnrOnOXEGUKrkHd
d8SFSXyqnJtAptAmNyYrnDNBnLHC60zUlxzKac4xLzJqOmYt3w4XWtbWTjw4
GA9OnZ9YFnGjLEQri/nnZCrorEh48sHNgbF6wIKdl2ok0LwWrQeH/AkLQ+ZO
sO0kCYGHTyCcTpJeDygf+rsGmAc8TeJFm2kxhSihNp+5v4/oObIoI6VeYM1w
ykAPHil4rD3Zv7i28KGYbO6wAJS2cB1achM01n9NFjkwzBVg54htFfYJgoku
FFUAipMn7BL7QuZVDchtJTw3IqVt5UKAD8fBiSMv+TNmvaVstGZJIy0VoxBS
spkLLKr/lyWFQ0uYca2B163/aNBEKiWJ+cfUmQPdM6UoB4RfltxxyAMQcXxu
peJEguAQDDgvqKyelJjz5C9TG9eIqcHxw6NJyWdQmuqVhsAHu/EjC4rm5EnO
3YHrETy07z0my7/OSyPapBy0Y5w7hH+BpBm6T8kg56rwRmwptDADrsffuN5G
NVRRLSfOYzAX0+KUH8hEJjafFBD0JOeZC1Xjgpom55AijhWUhVxtPTULmWzw
Xz//ukmR9L+UgrK7bvrmnrKAN1irBubEm+gQF4vBcnzolBR6HmB4aNcH5Qd+
68taaygn3e6a5zmLgwRytvUb2/pmCdAElrH71PcLeGbm9UFYslqVfotA/q3x
BVBoNonfHA1ZYM5ZkWReFYnzcFpdH8W8DI0FL7wDWBHUeNonyRAj9QQceLGs
/0OCPHST5mpX1ijaNfnxi3nOKXVCHelqyCaA9nQr0nSHpGkjpurB8gYEi5FL
OE4eHgTPRHRkFVAW9r1qVbjg4XAiMygJTJg558hLG4aufaVxgvoyocEUflQp
6QZ6va4CPbAiXKTGNIEjCZeQpxyPXw11ufeFN7v02olDUlI/sTz1+Ol+qoob
u8pF99pYypj4mnw4pA9xko7/zRi/qZ+DtCeHc2mOzkwVmyLRNcbhbVPuz1Vv
yLtCUUs8gc2qdLdfOSmey2aiswnDLb5qOJ3HnKn21ggXzHqe3NlKdW+xfBRW
iGYxh3S5eJUsdos9KfrkmFxfuNyAhIPNojqV3/fldS/A3bg8zDUY1PKQzdeg
G+3aolSz+EvKJSIoLKAoSPyh1ymjAx0abfbUaS3cGSZQoDGdKAtFuHMxwDUV
B7p7fAzK9xoKQVQKFVSwjnV+zWzSXgr1PBOzJe9A4jdIgFoI2c/rwoCiZDaH
bTgkqEpLyUZDNXWNB5wxpCdWVyNBimNc7X38VKcvjxnZ0vBUZCcACIDPNZMz
rC5BxSVM3oz57oYzhkBSk5Dt8XJBwrNTah5TRRjWbW9YrEQsb5GRBAsTh/WM
aLYKZ6N30MS5SCVwhYwdhPvWMY4VrrxeFDRoZyijGSeR6xoUl/E6IaBimU+D
+FYs80Np5Tbe2nExXLEKYPMkY89rF1i5lC03ufGATDLxMn5BkmApCDlG+wMs
4QF7crjRxaZAiZQ2MXQeS1v4Dhpar6kdw5HNlSTSIMVOQ+N3+3vWERcvnMQY
W5AKN+9UwOUAgAbqHKYJGUqNu8FqxRVzpFd3xmRCohdqkpMl3YksC3x8Wmgi
WuVL1i2ckFo0yK4tZMavuuUAHbG7rUNVvGZS2qBa3YlSKk0lXneslmPNqB+U
qqVjApSWWx8kK5Dr2P0Rmu/1pDdGMFt1LZRJwzyFcrI+fJRqnK2tJkfbN1Ih
VQPInEIppgDUbW6ddxW/XV0hnc0pHxrHxm7EUuoedajJCzBH9HaYVILHJ2SI
A12RcMi13ikmzdhzjEchxAqn9I2L9W02QMtqEiqw7AyHRcQ2mwHwFVvYlRgX
htE6XC3NvE4kcp3JlFLhXcCe8CXebVHZL0aDpp+RECFd4FJDlO/7kC+mo2o5
3Uo8jhNforWhhmTG43r5Ek9LVQvrrPnsj9d47qzxHMuJqQMSKg1GNafT2LGw
39HjcE6o27pNhpNM/B1s4KBMq6aJDRGlVPV1QUNUlI0qLxMlJjBx1BAmfVaf
txUDJKHdCf5LJJ3aCVRy8p5M0rZXfNfLYeFCb0SZbFA5FRF96ZbGSyX+uBp2
RqzTa2mw5jqg55Zlj7Y4jx2njq1fNkpH2IUCNpVKDWunRh9WU/JOTxKrmVGj
XswF0wThTIpaNZqf+OaDJDdxYJ1GoHg0MzxpXh1Xhq8eMIavrXvbZbalg2Mu
421GH1yvhQ0JA9W4t2VWpshh7sl/x7WK43EpReHmoFoYe6tTuxIO5yWIE2Nk
w3jZRhpyHhfqGiA2gVFSd1TnlJXEQgOoYLChWlmHpjQYnkxEVKJtkrVYU3Pl
JFbMTBMN0O/xHiJYOIIrDNuiuGGiA1QfYMYWECeNy9S/cXIMC64JlnI55xuN
rbqQUkMkGYngihpeGadTqv1XDJcFWyLhbJfFBvNTwVX4p+xOXWANn7uEAnpI
dGhCjAq4ONLFTx8LGeYalvy4QJc1zH9nfQ5bUEOvsWSfb1CWom9GsXBjPqod
s0xxkbWlolkRgcdNZiqeIJrBTKQm1jMhPx/L/WjisD4aR15Kw5q8YWwTXDlR
2VyHgav1xxybI+EcxBV8z5P9VrMUsegdaatAIFPTi2Yttm0KRmxHf8aZ1xr3
dUKpD+tlX65pOufGugXCITpbQERdmOBT7gbkfgiT3ufTe8YTzt4iMSSAux+8
xz13VDiulCVeE2pQnxdNppFzbpqwFsxOqkRzirgfb6AmU8ojtW5n4aNYxkAC
wPU1zlhVOoCyGfXWw0q0QyRy8wnAg4MBmBWmYWasVdKEV+LUmANA9ozd0HsT
Fr9MbLrr2qtL3q689N52bTKn+LD0uoXHnwVjBXaeNd6B+rRzcaW7rlQT6BIU
eOaBApLUWMfklns0hPUjrNxIJa7CwKmC47hIwDaGvYrDwVg8NqTTBjaO9dS/
WoGCM+XgoKMLLY5+DXqwmPV/kloW1ACML1yr9RYFuNhtHi4h7PVphQYaGrFF
3VOc0oCgWkzzlRbLYMslT4uag+3PK0FmgJPSJ4uIoQYxo52lpmSsuJmlkda7
m8tPuA84/6KgJrTMJTr4DUYA2byqxOiHSoG9bXmdLDgk3FS7MsEseKF4Ii5U
iirZnJoca81tZmXk+jdRNyLyPCSLRKpqVZLCDUwHaJ5K3Fot1sZRSt4ph+Zz
ywHNHbArjd01ONMbyYqEGz0FAvbCgTxgslMlKihBM8jVo28LGolRTUo3Iqtp
KjwWgMaIidjyjeuH3ebR3TKmyPPE0TkMdGh4v/KaU2uNb6Cal/mEADk+mfaH
bZ+KW5J0SASJcabt1wNT7cdXDamiFfOswlHCrM+QA2Ck/SKoJW1TyxYrb9zH
wxWZ9IlssfIl+ctOQwVhr4R10jCV5FEutyC1KnSZa6qUPVH6iiBcR0+oaIFT
p3tdjDXbRFjHM4YC06szoHEbuskarWCT0GWsS66qZBkn12sGpsgcb63VSFqG
SQkM0HwRoWbUoyqfJg4tcItAiJDnVRY03TnWtESqmqL9bVL4kt2d8dlL+WZH
X0xHTDxtygjrKqG5fFPVjD23UVNmxIINhyS+fSqnV6blsvQ7ZFSMq0xyJDMB
3VKmQkiNlcOcglqsSPQ0kdqVXoZ0gYish+Z2sTi+hZN7h9ISczn4K5e/TGyc
t2Byz+E22fCWq53VsxCLTd5UdAfMmOR3FDhY0hHaSeJK90ciUE6wE80oN/Rd
8Jp/Nd/gkxz1TmiygZO1KfDSIcS0YLIrMw3lOCnSoTUQW4W5rr3ZGJdNuYFM
Ak1cIheeKyiAJ+ZCKU8LvHUddofM4xRLeq3woy5pzO0ahLSxXQbztWaL0xOT
LRFuwqVb3d/mSDjJiXgKNgQa98uIy9CIyEVqzwkLWYhvp/oicL8hohi3nKPk
F0eyloxaBNgiYcxxipmzWT0tziq301juKz6zvRo4oRetrCT+CclkdYATf285
Uny5oEKsfEhUF1kC0g2j1sLANhRWkQBtYdYDc/5ouoKzSGYjB+ahxYXWmGh6
ci22O81pBdUvC+oULNZXgW+28YrRlXrhi7N0Z2ta57CMSzkInHt4O6n0AbdI
T5GRhH4jkl6tJWtlPB660yAq/ah77DsUbmvUL5yImgXmAwKc5uM2Gbja3B4J
h/gx957SThRtQ8EAbgZmRsKyF7qrRXycvjRUFZ9eHEzTOyMTaHdC0WqZjjIS
pmxLVRzrti5RMUgdDbgqcRudWMrzIhAHiRNSJydcoZo4tSi35hqeu7V1vTQg
drXbLxtgKr38eIciVCi5takHzlI40grT4TQZxnp7pHSq0gtnKU2zI8194RZK
hSu/KjAhQUVNxVpO0KU41wb4tFktCzyctVzdCTRsPYnEmejzH9TF672MUv8m
Ix2z7SweQSm1MBvyIMWIg8svJ5hb5pR+QD26a/NWPc8o3TjJkGRHXOu76Mb4
XV1DIoWJGW+JGyxWLZwgIZB1ogneE0qCUTXMxNjD4WBAD9J8ShslDZHadZu2
gZpX5fQ0uafaKFhiIv0CQmFBfguxE1quaOKBNTA5507V8zRx+tFQCLUYCifA
ox5YPr6Dw6aoCaX01EUGV0EFRZyKaQuVz4e271JQ7E3kXrfOsNvSRqd1tvSQ
jjBpw7fj2q2hDR6gIAnMGjrAtsZkoaV1KhHNoFNZxurE2vslKvB1WspV1iHf
r6bNaZOVwIXmowGiiT0r1idMF0sq9IQb1F70qLum9aXNxa1q2+oGOWsw2ME+
vU3Z9OhlIfzDvnf8DsFj/7/0jzt93DL+ZpPtSEBDw9MDdn8TSOqLaTIdeZW7
i0k6pqdQZ6aB2DTAHpuS675/F926zeXzcShZN0TM75okdfaWf0eJ+2ShERM5
QZxOa+Hdz4ODDu7s6LgzSEsr6+/G0WGPPmJ5kiMuKNace7mU1AZTN+Fu9JQX
sM5fwZkL2Urz1rT1F9Oc1rn5qFBhztcAtDCKveE0YkMSNDKF2FYebgopmU5N
P1RUaFHBilX8sW2UnWZKwO3cWCbTQip12140hbDEFRfWBrGOYWaTpIK+j2SW
L9ilGmTmBomLabWaqaHc6Ez2056kGdrArZAuTSLWnbBrh2/rGapq4I1fG9Ve
59L9A3IYsqxjzZE0awwuMJTESlw0ia0OJjFvFKCwvslihHXIbwHfHfH4A/qI
vj6BT03AH370zY2b2G+KmyBtTfs5BF2RIqfBX0wPEVug2l/aVopTBq/ITAXH
X5RtMbp7HaZuf0uHKbE5m0W4dhkz9wsts6316MuSkuodZmgMydqgirs4k9sI
aSusJcHuVBSy18Uy0hj2UVCZU3y32r3qaRF0vCq0HZZPY+PlnTBHzY3CHmqu
Ek6vC7WsDdzcq1SKsfXR9FTISSjxCfkkpayt8ZJEzbArmAgFxGjJjptQ3A5e
IKRy8lYNLjg5JHD4OSiUeA5t3jebLkklJf+UBANRFIsNjgwy2Wjran6Vxmo4
JzenQQVE64Eh8lBCBQ/LzWg5YkTUGa0lNNVmYMjXluWE+qAmmt9B/ggczDEd
xHcgZyKMXQzlijcYEOUUM0Mot8WYvmLbva6eOq4qqpnzYQm+zliMF5nCZn2T
zgVeIaCL76h+HYz49Qk+1dG/i2+skO50mTDs8KWDN3J9w9aXqFqzpD6a9mjD
od2qPbUv0KHkcyBp98nUNjXWRIsOizSdhwV29MJwjEGHYoZEdZb1TeHcd4nO
YWhrZ8I9DEfJHutFjkxOB2BIMOfzUWDPfAfn3BmVi9lOW0tf1DjPNlbiqbC1
3fVRjHsh+15Qs3Gucao9FEEEJ/FGDkaoC2m+y0XBnRi0JUYGCJKMjJTJEib5
TeI7Fb1YSHBqizGxwvh+L7/FGILMyZhO0PM5+x2kq0/QDvqSymNoDVGqVQiU
Z6QPRH5dnPqatGIPkyokqVsCreuGAbyEFTOr/BnRRDyrVUeeU8DdwWKKLFZn
nlPR19ENgXjsFOVyPN6pNymYmG2OvldkJdndASfQwH/7t3+LhqPRtEXDRT9E
3W635Q3Y0W/4Xz1wRsyWDN2pf+XJcXf/cJcl1C4yuajmuT1cBEOnku1MUEoX
2N6QAnfY5YmExPbuMyUSnV4QAMOd2aqjoNsh8ckCxY9BonvkwoLehBto3oet
OKNZGPA9bbnfMQRpR6Y9Q4pVgsl5ElCvwvSC7rKHTEd2ZUsKoMIIJta9+TbZ
ApZ6y1gAoK/F5azuGym2YyoIY08OnYj7EvJC1SOgd1tOA0vy45XZYEJxOwz5
oG2zHwTNz+Q95ZoTxDmIv6EHKcgz8uZqB6ZnruaDdmY0Ny/xybwopWWNQ4BF
NRuTj6TSO9ft984aysIU8cJot3y5gAs4gt1LJVNsfRzai6Q6HHkRxHaEBBA9
sX74j7aelS8rYUCOWNjveXEmlH0kfTYBhGV0AdwkA94EvJI+kL+RVyIlexq6
+Ux7azFhkAdc6lLRgEMd8Oub87cnB1zoEJDsDhBAQm5YB/uCmGyk0WoForAs
ieC2EwHmFoYMzAN7YTouhs7PqWYzIojNfyALgjR4K02aUL+m2GbvS68vNU77
psYp/3be458+CXLwwcue/9NXE7XrXXchSGVuuOImVe7bB+QBdpJxDYE5OgkF
EnqBuFabLbEyBI6YcvUqfVRMlihzI5ynKxOw7FsV4yFQv+WUqrMtpSBayTPj
uuxBFaiT0g2bYX/YlLymBLrhYjUvTUgVuotJVIDXWYsvqZ9OgTY0vJPkdAUO
JdYxGJ2dIgCLhajO99ygUoLG/2IKCUgynoGaiotVDJQUNcor+Md4sfKsY6Ie
BzVwdxHB0Gyxt+adBpvNNtVoYdQPalqjoWsTdYua8rQmEM1poM7WVVPfxjph
75zSZRqroScl3xoTHNdCB7iJyMp5DPJUsadJFGRmQClJaDsaryR0qKACuVk6
RxRSgBldnW0QaN6k5iU+WD9mKSF9tXKua2jWBAo5WKa2ctjKlsjA6rpcCjfX
ioiHP4lT2S9OyVAIPCZn7HuIF6gDqRiurV2KeJygs2ckNiFTmEpmNoeirglC
Ugp8AlHvAT3bK0miNZJpSATVgVnXKGKDSakaKlzNIESag8wTi1BlpiopUSWb
esglGilTLGOLwGeWqOFtrsRKHeEkGR7Y1NX59XmFRf3xv5R5Z5B0gA/DUY3+
VP3kjBrXX45SEF7OIiBMMRUWYBMzfPVP8GMDxeADyjW1hmLSDHEITleYcagg
h3AlFcUfuWyCISq0WgopYps+jb5GKZS8YHUCwLnufP2Kol1HHu1YCWyXxMlQ
Ey32fo+TdvGlb992VDP8+tX51I6O+aNzLHiP6xTxgJUekQ/QvqIBQiWqCBXb
1TfPwYaakRldJwWBoIPaPCkTnU6HUletw4q1wzh6vURm7dsGTb/kIJ40iFHW
oIN1OLtRe6R8fMOT1P/uZ5dSRvEqFPNsGVpnACnFINyYtLxR+sWpOUZ0JC0K
j99QUIym+FYqT9vSdIV5NQeWuljTCc3kftR1MrQRfl7k3/ouaW4fa7Ju2sbp
og45s0sn2ABehWu8bIgEMGH33tsY/AQI+dQL9LODkX353N3w04IT9DOsvSqq
2SBdlFSIMyFzlSN9Oe2VHOlvng/lceN+oj+5OIeBpnSY5IqJOVU+Q4ZZmKAY
rtTvmG0Lv48koRLQpM+uJjHrSiyZeU36bcSaBQ2vZzZXgL3n/IjhE9KGmx7d
yrPsl1XA8E66DrSDKtjDE1aNFpWdkZQPmMWllEdk0yczb9bUWuccJ0nQEE2w
AE1mKHVPrSib8gafsoCbcMCxEGqpd+I3XSlNuR8QdTelerRZ5GqL8wujTodY
MgELYw9NoKU0OnFNomiUTLN6QtjlMG3XHiKtcUBe+LNrmkFwOXuRQHKnXCS9
QgXLHPxgjjmp3Aq/WQkHCYI4kP3tr/+t3O6ejKfLdBSxSXEGPHMpmm5wafzb
QgSgtmyLFHSQGqwUwQIbmMU2Q50CblFRnppam8wcKCtLDP81lw7rNqA+bPPe
6f4ZryS52esryZiGcnZ/iI93cUrVnijQitvBVvPwpfyI62I0jU1NtGcDEIs6
ZMTImJwrkGZaXrXrBJzPTBv04SRN7hn5/OJj/jZNGxJ7/E9LBjtC2oM7XcNB
UqKgUuTTJaGNUyHWxwdbMdCvQ0UYhQUBfO8+O8YCxdsdD67xfkN5WOd6OiWq
as/zBXsInTG7rBY3VZ6tHSXikmoUn58HBQu7JrLbuKNMcINDEUD46bzqzoYZ
miACM6NJ2URWeovqhzoocfGiqRiriGt0Zy+UU7rrYM+o4x9vX3eeaxXytBD3
DAjfTmNS1YKYwJ/ZIDaaRBRejErAkHiU8p3qDRzyL3EHIzRCpRTKVpCRAJlR
jEQSoCc+tFEaD9GtM+QKk2SxUwY7Jwc4Sv4jKUIdRxgV74wiJaZh8eQlAr3o
M+xg53/+P2Q8lnE+ft/rXZ7iEPjb8RG/Bb8f9PpdY8l0eICU/0DNu92csEai
x5BrWOA1DLRGU9DeFNUdaIA0kyuFM5egdCumc+Sffn/tff8av7+Idq9fX+wB
An28vrp49+qyc/3uw1uDLsRd0AcmIYbEeWL1T6cLdUyI5LWZuFSs+460g9WG
ov6eUmyBuUPoK2E+/nU/b4KvkApcOzcRoyVg2AP5DOGLp56gREEoS6pO7eeM
mGAJfyJytHJlGmyRSYcyy4U6xbb5HZWMgxFGUpr+6vLyMjo5OiSjw9cnGBYT
pOKaAh5O/R3XMoK5XV9xGBgFlCOqw3VNBQrYZbzHIa1lIU2Yxc1DZ8t9Inhe
6RmBoQF2NM0D5rySotT6MqT9Bzg6rh6PsDxu16T94jXKxLE6axFMWmp1B6CK
wGfc74lyoljF1eBL1l8LalY7xkxRQPCR6LiorbWN84Coz1+WFPWWcw66Uy5J
ZAZkSjIfF3qQco9sPsUhMNTd1GIya095nxNOE9Eypswd0EXBHSidGqoceaVX
u99jsyTFyE3Hlv63IyzUnJnqXkf7lPtC9jfz9gO5sJeFUlpbJEdYhMr0tLCU
b6yTYF8kPDuHcNwt0eqIQLDFiyb5FCM84rssJ4znDCOx6QL/y4fkjpnNl3oZ
Wwa5g8VI27TcBIFwlRL2/XrlYzlKltYG2iYKCpm7RGH/M5OIEQdd4Nri7eHg
4Iv3HxWFFujH6kTntkAKtypRPN9QGrdL73qLlffj0pbZ5cNHeyR2XUECKLH5
dbV2MRDLAX5aak4LoxfOeMnkEJmb1C+qVtQ13FjAVgmu2LQ9nIjq2YVNcKmk
nQqvit9qiqo+7jXJoVokXERPjbXvzzsfrm4utIB958Nx9Pbq/c0ed0UHqltO
ZgmlNOhFRlIXFBgmA6fgU+XiO9kVnmXSZNelpXjc4OQMHmhdCY6vA+o7j+9i
L61T00rhFoHgUG10fk+tg0yA94ziD53xl4VpLO2EYndMyAjnZEgEKdIab8um
ZFJXG5ynhVN1oi1Y4UZipkUIt39nYWYNdgGiUHglwFOqfBrMjYjPMUhxIREP
1bwIWwyRiS4T47amj9NVR2FCOJcP8+jGKfZxDZu5dTK8wtIWDCqTfltKLE5d
UgTXBQGq4RYTcd0DFAIqCo/LN5EWUNag5NCCVg+3hziRHWjmOhbCvDQaAtZd
5guTcJxg0/pZqrUCU+p5xH6nLgtnmOHAYjKRt/c1eyqoUGknYut/zffRRTu6
+P77dvQP8X3M/70BsXpeatdqzv1EgdW2L6PMkfP3V5zslZQS6ImSdQAwnNsw
hrQwfU0WwEK5+EyOxV809jydiVyldW5JyowpHoXLOi8SSiVBQyaae+m8NMpc
9gofsfhDZj+JUkRk0BxUezlwb85dpfBYFvQSG0mQM92xBEb2dV65eiCkDZVN
4TLQ6ewRMOVqqAqJuAvv391Jx1NDwShMQSp/smxNrY+c+l4EWLGuctoSP8yp
4rpPU7laBAi36D3SW0woxyuCriAyKKNmFKK8GwfpZU9JcBCnSVVQWqKepyv1
ttgkOzy01Fl8OxQlTWGe9pqsGJTAvJhPJeOc0U/qCgZ1FPm4pNyHaoUqg5qO
29r2jCSbBNb4dASSgqVRKhREDAOz8ZvyTD8WPB4SqaW0a68SrOvgZYpLlmA8
nxm0TTqZ1E4kW4D2lA2BaGViEgc5F83qlEMtPlqTJ4TmDeGWFnyItNT6MR7d
gygRc+HhZUbqgUqzOJSDQJIQvyykVNyCYuQBJPganJYR+qjOGRFRgN07SpaU
9HUm3R8a8tiMBGS0Bc7hgI1w3JdIqXrbS5OFKN2Bge4m8X0qSCw2F/ZhfuB1
u/chFNxMO1F0uVLefkq9dzvkbhhi/W0vpcmclSM7U5ygkhajvYwAIeimwglL
9b1zPw4Mdw1rG+RfcHM21eIlfUAFfmIpI/aXpQQaDKSzkeF5CywIhmRAdQud
fwjEBOMFLUeAG3JH8rzTcE/bzpVUpUx1tBnQipRM+DbqV9ztRsE6PqQ0DirZ
RkicWxMUae548XOO8qpFrF2uDEd+YJOZh4vXs2LcYgihpKWDxba/4ZTzCrF8
H0yOLeZo1gWnC8XDRV6gSIdE3fZVMt2KHclxmRXL1CQZAQUqqc1l6WXNLDDm
LaGtYqGQPWODgzV2VM5U1ieW2ClVartj/kfg1A4RGCtAOYCFcWW51T648oxZ
CQYDiOENczVtCIuuhrvtsrqkqvJD4Odj4VZSOu5N6b36OBJusIarwkgMVuPx
hfA6Cd0FxbKTjzuDOLB4KD7yDbM3KjAteaOa3BANrnGvLGjyy9i/axgOhNd3
PMZ4yrb+HQ8KCj6SP2kFxJD0+SUXtouJXbEa7HjikHI5RfxMVJ1YZcgbxzVd
SOx2tTRsoI0WIBXsHlUzQ9it13hoktqOe6jz3TSIuH4hPL0Bj6ikh4NL2yG7
DsLLKXEbNyEDc5qVgttuhrIykiEkVP0zaBBqoJzGtgyNFJOKnp8enrZM6nSM
XSEW4vhHdx9MrDH4WKHdqFVSFFb54HAItCjlYkRu5UN6PrB01qM8Ju4Yk7bG
JXGMDwcUoAvYFtfVcl5oi6vJLoEbjxItCe/pwqhkQbkPokr+U6Lfh3VBuMwj
ea4qTyGH6XB4eTIy/f7oBgM0jg9pYgGx2cGQe5eZPJSRMRhwDiijRtP2umJ5
e1wf9KA+MfqayWdD3bKx+a3mPHAqlUkXJqvFjJpJgtiZBLGzXLjfSwxnRx8q
cUAgjSAqmi9ry1SjrUBFCPbSmG1N8HBABjcWREo0sBXVghrxfZ6OxC/og3mw
ErN2TN7fwml541lK0V+zYhzXuDBJWHTGI+Cob0VSYSi1IIiUWGYMIZPR4xbh
vg02xqnE2FiS2tZISlttF4R+t8fhZF79e3IVSdn0SlUNiwFBnGmq6nD9nbRU
KLjCmnUqURRqqdrv9pLvj3rOe07krV9veY/Pj5adCl6ZHGlRA64a6xG3q8fs
9RBD1ZqWmDnxeERTutwDB1GwxslrbwfnYMfeTnWbQeVoLyM49VuJ7Emrn9Ik
Vi9Cb0BQ3rBCJjgrds4toSg+pP6wTCky7CBrChSem3oOIa2wG9AVOJQ2jkZL
vo0kpVAFljVt4Ni+sLIFAysXxiQCm/pIlRMMOkhK4R+pEoV4yhq60T2E0nLc
l1mdU8Cy4nnhgtTyHkgobHVxySr5X9yyi17SJ2d7OrmDlT2wSikBsKIdOknt
lLYSxno3NjvBxaIiI4KPT1+6rcbeY+o7aCwweuXmJWn/orCcNwzIVYhNdptr
dtCWLVzICOmIV5glXJDbzdPKEJaEBWypBpE5+pdLWphwOiNqWEmBJXNORk6M
jFA4SYRGqKFuvnhqzUU529HuBeorfuyjCYZ2C2tiOwqbE2ng20jBKAw/JYm1
odooqSZqjLMtEC2oqhHTQjlfpxkXrPJ35iGzNe86XleT8Z54Fj1/ZYRAxfLu
DiNp235vYZNDSqcsYQvrGgo7djnP+pwWNkvaNPbb9iwklNLKHNq5HkU5Z7dj
KqOZjYyVSNuq2WLcNLcKyuwA9gtbV41Q1tJkWnZg8qAJr9g+nLuwRY1Smx4u
FYNqy11zsebmfoN+rKqJ+KuvTGGrKeXTpK4i4b8rqnfjUskPa08C1oIheZwi
LsnOJt+RlD2DC5Qd4ZDluq09EDZKg/Vlxn5IR3dxjO8anIXm+rqed6nFInYK
NuDDQzKddmw/AdEQyeYu4ZcNttpOpG0Dms694fDwzLA6E1NE0sIxsTBLgqY4
VOye84gCH90ox51bA+8zU/i/MqEoHc7z9llyPlNnPe53i5o5xm0OpRM2VzMk
+08d9PzC9fj6BwztqvUHkbm/ico4RXuc2veMUI2qush9/zUtsjjb3fuvYdYW
XoOhJXt7tUjAKpQ/Y211kxfifHERXzu6PbIGKHvfvdIUsnSnZisLUVzqIHd5
mNMxUftNfvC813xgUpamapzXcoO150kxLvWl2DdsSqtULBIfmF+//sjgrBZr
vXbNcRrkK30hWW2seiFuKm0RXPOO9JEqG/pNSfgIQl1KytpEBYn3jHy/DgP5
KuOrKKWB8WjEUOhrLJgd45SLIiNYtsScBip2Z6QPeRm/4vaWDcYiZtpBqpPe
y/prmYrjllwtYkwV7s99aERymdUVr8F7ZnxgKQvz1Rky4tQo3psEDHKaavsw
isMhM3mOxvjQ6IwMM+OYFozFVXuu1I7IJUjDMI2gMK9pC/6epHI2zFWqzoa1
Emzd+r2Nxkat20pwqFfqxsCeWPSudqmsaUTpy1poohUB4oIDQw1x14bMpj+i
Wl+djonNrtC02j6tvbHzLgVifP16ruk2r1xh1MTuqX9mqMdjKofW9tyURlAm
h8eM4zdxNaO5JciQpt0+5ED7sqGTwC3VUM4i4ZLiHHYbSNrWxkwGtMgAPSLg
Ehh0Wx+ZSdyRR1xo15A9DHApjWWbbjxZJzhEB/uXk0FWe1YikfyEOPeJP/lU
5p94rt0948VAmxZSVSxw8KLFhRSl2mrhDsEv4hC4yN09EfQyHUA6TE6TkrWP
+kaadpOVZQsNiA2ciIOtWQDdbrMDOJpdJEWldz4Uy2WNsiat1XZVkrVSmS8+
TysByZ6wvjL1GMSa7Cspv+6ePDqXXlKOkJl4kcA0mZtKYaJ93IA7NeGyxz+t
FtsjpJWYIRNNyfo+QjZOp7SbTt+L+/HADzzgKVfz5JJ+ideXyp6AOFikye3C
sQE+qIdnSjUOOvvOZNWQKBSTMa0l8+8Pex40QphVm4GWp+XIcVgBrmWD0sc1
MlrPvqPcUT435pjwnErgL6JPby6vRQ0iO/53z1r4TtBbFz59InHHP715/ent
+fUtvWh++j3vgct/eu9/Hx1VB3h5dXtjvu99ORiPP76JYG6NQw0mvbn68Rrf
Ma/sYtEAeOX3v4923Um/99a4t+eNcn1+/enqmh/mBfS+YG9g76H//PHq8hYf
daZyZ9KxO30YHcF1E/IQZ+03P76pAdj+gfdAFWDPqwMEADsZ4w/DbP+gAjN8
bS3M3Hm/95bpwEwf8uaGyXXi57XzrgOgB49O1A8m+5fLD+8+3Xx8iSkAODNM
5n3vHKCC8uio6Qle9m74HizD224V1OevXn16d30Zwsx/C0/+VWiydSDx6mXd
yR/tew9UT77fr44QHP3Y/fn4hk7iaL9yFDp+eHgn5qV+v/alhvPjA3S31XGP
D79Yd3z4fc3x9Q5PqhuuOYDq7HL7LmyYmS8kAHnDeZAJDVKiffI9ZuBnJK65
iLv/E1+Ym5+uXuuV6R9737+8Or/59OrqtW5gt79/gkh8tOc99vbq+pOFAJ3p
QeUBD0r9nv+AfmnW0t/3V/L2/J+CKQ73vQfevLvx8QaO0KUXHZfQBmAMxbEq
IOWJWkC+2r+pAvJg3/u+Csger2n/ZM97sALK56fPKw94oHx+cugvJQTlqQNK
GqECyv5Rz3uiAZb+7eu4VLjVwqauzYLZMhP3KD3GX+5FX1sRi1lR+D0ovT8o
9v7hDyGu/s7jkC8aRpmhUdyM8jufsTS9BCcc+VO79Pt3HoN4gcGuIBzv4ks/
/FBLz3mT/Bgv6Ieopx9GKhHu4tx7uI4XCN3vn3WiXreHgMWHvkXJFOSy4J1O
n56VlRbLAaeiScsbV2xj8/R0bMZrmTF19X/4ofae/u53BJDfV255ZVu/i3Z3
DcurXOgODrO3x/yvbiMRboWQCaVJsVIHeqDd43rAMDB3CYm+x3FF9SqaB1Ky
z3v5vsIY9xATmve192ILuFaA+kOFsNVA1SNttaBbA7jHgenCAVMteCyYcP2d
KofYw+P3pNHo+9oBaHMEUl868iXZZrDKZXO462Pume65TkDeMxfQ5Jn5UHQn
8GU/OFcmXN7MOrUvaNdPTnO7WlP9AZrT36cXQlWresvlRR9pOOFeOVrU6awj
Gt9a35TGB4S+YkXw6Sn9ZzSYNhN7l+LXIYv3AyMh3gQs93ee9N9E2l2mgOP8
zpc3174mbEGnf+nxBFfuDHlCnZD4CFyNfjtjEJFlE2MQ/rGWNdTJHYY1hFJL
E2sQebYioWzkDes5Q8j/tiB60ToG0TSeoX3CIkLRnVlE4/aElm0AcA2PCCW2
GvB6Itt/DI9YD6+tOYWAjNlFRQ7eq+iY9exChjFMw7t+nUCVX8s0ApVsw0Vs
YATrgFOnkANLaWIgvvK5noH4zKZ+Kjpp66T8/5l9uKQFGQjWnv16Fj0hK552
OUvLafLDzqXY6y+sQ2W9H0UdJDtSRQgH62AFCUDrH3YwDtD7Bvto/8BVcTtk
TJX5u8Odb+THeSl97bRrJjk6ncr+X5/U1YT3HV3a3EtjhEy5OK/tw2Ndr+ca
FM2BOGt7bNsIKUlrWGYc56D25mIeS+/3BDu6w0p9X9IgwYr0+cIGjGBSnCmG
i4vlCAftPicTRg/UIlL9Qli+bsYJi13MLg7SvthTJbWR2dLtRENU2wCH26Qi
SRRpKL4FWhdHBbBJXSqDu34+TZJ/jY4HSgzC6OIlYD2mYkgd8TaGlnFgodNQ
w2b7ks8K64VTnCeHyJpsw6A5mVbPp8bF/hCmVj75zR3PU7e1+15rF96nyQNA
ggbTLt1OTQqJP6wJp6mG8vgxf3scFGsC39smNDzYQtsU6/CioGr6TqADsy7W
EeNzqX6J9mWpBmPZWjdO4Qit3UTBFVw6p9t6uYq476zjQGGvh77WQ4dB33Ve
OpV0KN5ZG8WZdVQiIu3KOKrYm8gZGaGy70eiSpWd9b000Ge3IOcinfxgZfsk
SJS4idyTRpJOpJ4TI6w7kKtKM9vMKGmCUdRhJlYarOta6Ne6dho5cmHXgKhR
AFwRAO9FbeC8if0ySXaWvkgWoud9ci+RG/ru9/OsXGwuqtheB3xYNfJsdrtV
zsoLbIy1Wh0gPjUHQhzTiDfpeCgtV8Obz1mb5rG4NgWaD1vRKygo67Q7D+Og
NYa7Gp8fNNGVzt+Y1T3DtctTi2SaYPIo71/LrKdU+OYLZruvJF1L6FWVS1TK
odqQ65IyzSjPbK7lFJGSycFyjeLxmhPqtj7EfIopNe7OFyP1XUrHdM4KEZ5G
h+O0yIh1W1KCh/pSDZ0oo9rrULcdzs1127pQvZ3aXi5aTbNaO9VpMIKvq5Th
ShP4pQgSnKY5SO9SiT2mdtk2TYkblWj+KrBIDH5C0htGQ1AVWGywTl1iDJNm
RzMvwSvv699svu3NZ8Tx74k6c2ujz7rOhhTHOelYdGsn9q2tdfZsROlKI5sk
LP8L3g43q4gevENayqCRQpl6uRymAnQfJ+4bRihtzzDnptuiri4WFja8SsK6
ls4d9dbPSZL4AubkYCx45NT20cwXEz5CMXHs394g3FSkR+w+s+a+NHQrogg8
TraiSx8X9gqkWo3a9vkg1HLOhLtOSNuJFwozv7b4QrLPtUYGd4rgbHKABLxm
ogzkABnbuN0NpqNweQ0cpd/u9XqtQTaLv0Q/RH3+A1Mr4C/6h/pQRLvPu116
aK/VmqP8jHWH9+U5bOqxy2/tybd6gfDbXvQs8t9xxjiwYxxUx8h0jL47xoE7
htzaHyJ/4meRNwhD1dE4KoVVqIL3HRJ4h0jYT6leWP2B++kRUr+cUzhMyrei
slZBRHUAOw9JIIYSB4009qU1QWq/GmTNTatURLYpAjYtgMqQmZ6VC7a9mEhR
zHQW2ry2z64phQIngYxdAvLdqi+6J4m+rZZXaUcfloMVh2D9mO+1pTqp1oBl
OiRva6kWrciyp410M39ZtANdhayg7ZSDoEBFWis1GDUKmlmm5Obrx3tB5Qhi
6FTrz6T/dyXpyMqAfOlt7SM/u7I0ldlNKzeqJ0NRmrVLoxpqFqJdaS8bjGti
50yDSRi2bfqkkuqHIWtOYxeJLhrXkm2NSQuLkOLK3edd2bjkFmLw3QH2uKCM
SFSfTRTgOB7ajrUUPkq2DcUVmlPqzG6L9W1P4mKii4NWC/elFjZcz0gTSXCJ
tvmASeimsFWpVUmlT2itpdcmDff/EDbRLYxyadpPctC6gMncPwIJl1mhExPM
7eoBm4zcUT4vg1FJUpMILqNdKe8yGSI1PaIpiWqOyVaKoU57WQ5CY2K1zEy6
OYsVXpfnghXLcCyTjyOWkHw8LpKyM1h1TBaipKf5EXTWBGRysc0DRlgnfLVp
OYOVq2f2Wb2mum82ALtIXIuCVK2hGI4ymTPFDQPATUdjd79OWLRzxeSAnAol
jL1cQsA5/3pCoFQ0NpaAWYIdMrAesaZioa3Grz3ktD0gaJsGxdqjjEWsK5Ev
ERZt/0kPhyl/VFDAtQqNXARg1a2W6dh0NStKhgwt9gpqOl3AuUjnTcPlMxHy
+SwtPe7i7kD7LHmNBLUHx9cnYQcNYG1+0Qh9lKMfCwnCxH0oT6LMHwnX5AIW
RvUa5hkDLqfmnJ5aj9oLJh1xnkGCDw4pySiIqNcO80O3ccj6zrNAM6TwDsaL
jk2mpYG4kng9S+ncLm3h36SfE1TtG2cPrKU10zO02lLXVIvCm0Qk2yixZI2a
lRebUI5qosmKlPbUtwDEKZriCdvQZNAB+JVTypeSTllzTjzSclVjTMCIsah4
gVVapnJKfIbc+KRou52WdLvEa3gTFMptT10X65x6twln7hAPTNP2uJTyo7h5
E0w7WIVlSvRttGraSV4Iotgo3IzK4bGBBguCWEIWDGi7w0mmT8NtwGSfC6SN
Vr7jrBpPisKrRw156leNqd1a59xnsVTtVpqLcXlYFqBXkq+2yIWau9Xeu61X
2l0NRzcDMEuTRjUFJ/GQPEz1rZcZ57KyBeDD64vTwz52KstRCU2p4SPd6Xyw
dPuMdBtv/ySZzosQofx2VNXmPH6/NTQ7nDeWiVt3oTdD3DQqcpt6SDYCfGXq
MIRNVGyLA+JoBTw618VRG/f8DtkOlTfiGrdu0X2s1UH1kfxqSJz3VGyzK1Mw
lU1SnDLDfUqkxxMXZSIiWr/9bquGNeRofm+CF+MeVagmTszZw23MkyI5b2j8
sajCIB5LAqcIB81YwlxpQi1DDUnCkaRmGBUJ/1JKBS6yXbq3XS2X1Ms8LZfc
wMM6VBxqkKHhxYIAexP7vbG0FlnFIIm1yuM53y4qJIgqHad3mjRqYcF2FCKH
eg4kkzav5ZaKRZCsziIgEVGXSTrElAQmM51rYzLSbgM7NJ0VvIS3al81bvqq
3JvohGPV5lRDrFJmcp24ugk/wSQ3llLm3PtFzkvWIfXBnDVhpoeHt02gYkM7
9hxrk6eOTp+90bwzI1cDQcT+XUhQYZCVuC7HoMVj8V7plyCNJZuw3hInVEW1
9DkLqm9AeMVn/gWr316qO8Dtj16x2TsNKujKC9o53UM8MdLpFKKdekQIlHa8
91jSjVeBNZcKX3FryozmGzPXJuyc+EV2DpS8gNSWTiuCuzyecgU377wIQoUv
12xI3T8T35YZCBOcRPZmkUFVABZV3I1xh4usI6JhnJUVU7ehiiF0HVWs4ZRl
fgWuNDfmEjkedAFpcG1Ud1FVO5L11xqZGyUd9AgJ9TD6qeEKTGspQ1UJildX
wrltjbzD6IY6gu0CSCnH0ujOuXZsgE6wtZ0tc8Lw0dRye95yXNbLZ4vlo4Jf
PUav2oJ3GJ2QRJgOKHI4pMZSE0bHMuBBwTzvuHfZ1bnbUwUn2m9Hnb7562BP
sNlva2rKyoUWEvHKiisEWQe2oZaOKJE2okZzZ7U7dSswJRrjEsI04wqFcJ/v
lumIu2dnbjN07i8taj5reFelcaBx2EbKNYJom4c2/APN4dwYGj+i34rkL9U+
ycxfif1Imzz/hJz26NUey6EU53eY/8arrdRtclwOUnW+bseOL9e61Y0H7N3N
JV0aRuUJoBu1jXBaheMj77kkoekJx/EtrdYlaXxpkU+ZRrVaZ/YcufxD0NDb
is/mdkmLTNEPtRO4ra+JKKrkAl6a5oUZHTkS9kIYLRcG+Ukg2LWSCSlFpsTo
JJ6WhdbZ5b7drLbi6XI/Nk0Tlwpf1PQnQ6zCigncBMQUKqMWL+c3193+s1eX
H7SMqLGouAYCqvMntUQmMbVQYHjhUequ6W1D2Qdc/J15A76DsgJ1Fligk0G7
aZFGhzigFtL4HoCCvE/6kQXSqtaA1nuq5cLZAvsgg+VjFgolJ1YQvBbFzGWU
Dt9ocioKvQdAc4elDOoCQvbE0q1pM8g97xU4L+umS92C1kC+sFYsXQhpSV8w
3qB5r6Zggsn7R5JFk0mLAURVsZkRwGyNztaNdE5Rowatrc5GRAqynjqbWNtE
ouK7OxSLy8QaRsTAb6zquTYcxIIft1ygVXsrO8V7CeUw8mjFFkoYr3BLW2lK
OBNlRazwHvJFNnc1qMOhvcAbYkIs/XjwLjvqIhyGpLEzeZH4zwqOiwYljavS
GfddyHLbuIKNVdYNTLhNRd0ltCS1nRNt/R6pkyERDi6C6lHe1n2uZmuyU83E
F9K4+dynVIJ14uh+yHUwt55p4XbdJCtimSaF9Y+xWZZKhwA/yrHmWEr1slWi
rA/pIhd4pct5Qdq32ds//fO/0Fpt1dno/OUF5di7H1jx+gKuAVXKlU7WhS01
GYpqp1L29aR3eAoSuqA0MI3b8/f7GKqGaPBzMjhflpNsT4yX3srMrGsrtKyv
/dTmMD4ClaSjw3UsUOOw9E8Le9QQVavTqT0gtrbrIJqBra2DhEg5t0GH9XF0
ggETdpXMxAdGW3Xss0R+hgpis0PFSc7mX8y4BDdddqZJYsILOz8RG1K2jsVa
bNc6N9QwW9fjleDzRnhWpcEH1WUj3ey84pkI4jmNdY21RbbClinHzxQJVox2
ulpzYzHVZ0IyYa6VX+FRSsABa0LhHyPOsdlZAvBadYzVkWrZWPthW2rVsPmH
T5jLNDhlKYf5fOURDhVCuCKHa+uU1T/Tpau12XY3Nc5Ye7mFIHuxR47nhUhF
hU4KtVelCubadeq6ChegjiZz5BpvG8tuqbeIvS51/MNM4TQxd/rcGd+w3azj
T43rBQMVT0x5eJ8muvsS7xIpIfJpwaLDlLulolFFHCuOJPUTSxAcBi4ziRBm
Q3j8KvNW2JYlTKdCz/Kx9RKgeWpcUulIDYvBHYeiCwXxmsoZVIaFDHrGky1S
q1lcW0u0UDdP6psmBqeqXIRnjBWG2qJPYPPWZ3p1VEPR9qjPqABJqo4EKWsa
UTcmhqIJZTWL88RHicRx6lqZpnzS7pjC1tmETCM4DSexBtstxTmSA5Mq5U8j
Ok2M55Cut2lJdfWucRHUZEXqPVnfjHCQmBUvlHj2zAvOY9owwyu9bKurS/x9
/WCv3Cg4tgvaUzehXPAgSkfOQ6EIBbKEhmFQ76d4phSDlsgh83TRuEALXDQN
cHPlQZ5WLgcPErMXRqwaWTxjbKdHBRe8hr8icHDwmVNwzbTNcQu5lNpJxbi+
CO4T6t0iLSW1v4I2z9sZALw/76Bfr2Lt3CMzLsq9qJnoAMAo8TKo3lad0G1d
hgyTKbQGZqORU2sA4dO2gUF8Z/pe7qbdpEtViIYJYzG3eltI80t4VMLH9zZC
zQWV86IE/0pxOVFRCZQvHAtPOalsyJT+JS3aVGVy7gKQ1GnKtSQJN5jvI7bE
hZ0GKy7f5fnI5FnkRvq1mSQOgquHx1hxaN80EVE7ooza4dWJEjBOTB74QVGf
1bYGsSm8EW0njhBf1jpGSAbZrLLrw9coAIUT0rTEImvI/BfcljLn4Io9kZbZ
M2RRWq0t2J2Hnfi8PtsahQselSy7j8221CKhzxnfvkPWzjiKSpzYnCuCjYfU
McU3AWs/FcvCuRvacaAdCOzqSyQpD+CADsYX5KPOF8oPOEZEKsvd2pBWarE5
X6oqzfYgysgpquw+065L4qkNO0O0GjXrZUxJLawjU78SskSSaVw1Wu4j4HSG
irUXWyqdy4GGDqgtkylK95Ab0aHwGaMrBnKZtFAW3GXUe8Z4tyd6CeW+JPW6
aDdiP2yNKRGF3qtxvcCi7RMpGLkips3Ec8shMp5IqBEkHI5M/WZ9K8gy4x2q
/uupbCKbsgsxjnZKoP67eztOR0W91vmitLY+iWUyYf9lvDB/sG2L3MVKcglg
Cnjz6zQOn9s1jZyIjnJh6SG3YpxQjGOI5kIm7/PpPRwPIbe/pQxj/8SzoGYn
Dl8rAugY45PwO4dGlUSihEIpXjWVlL51RCOcIiPqLBXHC0MyDFKpgUpzfnQ9
jmjgBhby4Sqhk4lGnqTH0V+gi8+4LWUDvuH7M+7mqJ1eVGVwzPMmoC7Btjhk
8X2QyJAKWcZzxotbmJu7WOn9sp1dRauU4qXUtxspyiDhfqNy+etCmfDCkeH4
6xP8x1fGQ0P9BDj3FLl3YdpQlPkcmx9XE4m0Tj9duncD8ly4wj4I+YsVd+WL
dnkFXzv4L+WXIcMdw1iFreWP333CEfqqTrr5aYdSwFxGcBqYFUujv1E00XS6
JNXWnrekzmiLA03WcSaU3p+UzWqsqL4l2DbQuirDkCZTV9fLzjDV6kmOvp2Y
nqjyF0z9yUwmnylOGgjgDtjSj2OBxFlqUC9FZLDEOkZj98KEH/nQ3GOzAZ6A
uAYCFGHMULeBmBMZT7W51ozlYqrEys09xLRCNf7IhMWTc/YTUMIJaarRxc+3
+OLl+S3fctMVtvCabtnsPeqj9YzVJ7HUcAdZ4rjEOli4wl9Vi3qmxMMWg2T5
1JvDGawtijcHY3rWH8kRQUKVjFK2FGvBXpLn0PtHmj7JXZxNTvH6KBWMRlTA
EDv/2GhVbpLeljVROILYqMmMzU1sqCUUHpJjYA3tmkiRbAsGdARK6V6Td5ay
h29JDRTDyDHk9zHJ+1WLMVXfn5qQM5IIg6gd25TaNMAlZFjRutVL7dAQHgRE
b+ppJ6PY8CBqzIBaO6Y7oaUtGTU5X0KnW711zBHiHzDrkJpnZ043Dgf7fEeX
yC42wVGag7vrbVtLX76oGAU1kB9diuF0Qh7wQNhTRpZA1+2M0xlXp+6hyGuc
QSaQXOSdjlIMnYzjFEygspwl3xQTjXyXU+foot7nZPzSQedaKyThVuLFIC1J
1BpOltln10Sh3kRil+kIjVisOVnru81TlyIC0iIlCrlucPINMqJSOI+mKs9L
7270IyFvwWMOlzl0uAwF4EiZd2sDUDqUOlWvF40KjoG1p+KYC1Rx57Lgh+y+
W7dUQc162slEU5agJPEFSfJkMBCdXQUrAqlxdGCw6Iotrci0SPEgkJYmNaWu
xUlDFIZeAxrPWRz35hBJT+JynKq+HgLVZNeS3u6kOzd6O06dY1TKRLsJXjdV
EtC1alO2BYbrwhOdIvqbHB7cLgzoeVAR2FTEV2ncu/7NS1sbXh0X/tLWpS22
3VC3ANOMXTejXkyafOgScBeW1QZOykJ89MZ23AvQjGLTnrkydbf1qh6pRAky
QxWe+aEStedeEiFG7N5WLKMwIJNGZ94LTUjB4jRlHfWtdhM8DO2U/nC0UyGL
KIQG5A6g+w5xxAl+LxrdwRxWYCIfDHhSrzFcPo+xey1JMxoDyVI65ewtFhIE
vTYYnOm0StTC/TV1mJxjG5MNJtI43KhnhavcYZ6VmwLWdGQSsRWXVJOax9Pw
7XphAFkCIqw6G96KRM08Qf76hk6gGsXDsweLdJ1o9XwnaA4NJaF0zuxQagAY
Qq8Su+EM1gXdMEDEvaPnGgKZT3kEbZ1c0QqEXlN/iFrxseIWx7oVsitejgkx
IrnP1kA3zVtqChiIldKdik0yccHSsZhITaYIlsHgGM8HlZTUtoRcotBCJ5Jr
RnkiZUVg1dlrDy/LnYaiwiDjUtui2riRMNzECChXDXHC4tGUDWbcO8QkorCp
a3G3lEZUCyffzOlZGfAgIy9Wgajim8JnIGAk04N8Z3Wf1g3pB+zcjj8TqWCV
AuXdMeIJ2QjNdpGGZCp2W8rMTmgS89D41CnzTpKNHP+4XwDeSgVi4k4rCrKL
e3ptX+t6NJwIy+VwX6jLbHSbw3+cb7QlJFu+NeMSN2flVm4RMDPLsZnKkg3D
LEljOncrmUp7YSgDNU6qQkCmYu0FNh0vpxJcauK0tSaTsZgtphRP6CzZZt16
7Y+t85PtQio3klQ2XJIT1+Pbje3ApmQtMvHNCz9uiOK8zegsG5INUbJeKOmw
FgGIg5TsD1t30g5qsGlKCoYVjQGiogzUF0dZV/6i27pEI5zT4d1kzxujILq5
2H3MSbvCXXhC7spBCgvFwDphKBTJRTWNEOdUdZeeHV+/lvGgI8N4+fxs2MVG
c2kyHTnloyi22VktwOZXfij6Vd5nu9mvrV878L+W9+mv0S3WSpF51MhFtmB8
MhllnUBwhlE/ZirzUJjwLmC6WuKtExRfF+TrBID/1bBRf2wdqLaaCA3oX7DH
jrtW0o0YMg7j7wTzN4y+UWj5lSreOQcbVryjGnNXCLTXdLhcj+4JZcjh4LcJ
+cpb0rnSYBk1JXGaDpvaCfx8nfPn1vaM4YbHYuTzmnh5llmWNERnC1R4kyvk
HBpH5ybqWSD+hwlD3qrd/BzqoALQot7iSrkCc0Rw0AbnOSLAaaFmXAwoJiSU
WQWKNN/Oy1fX4dFR3anpyoTP1usTNNAszujZwH+jA4uhYadz1O0lnYP9wx32
hqFtb7pyI0/ncVFoBIo0bBmzA9fWoMdR0W1Cdo6LzjTO7pYojPihQ9RDliBU
00hX3NicOUBmhsAuo9giTgJTxi1o0Fx6OOcYW0xy+RkBiE/FyW0SUqdRW59T
VD/IQaRWEO6bI0aPzEs9+ttf/7sz1N/++j8kVjvVDjqJtKJ/IreSLgll7XJr
U1Fj2qQNf048uSckmS5Rv3We8wIn8OunRQ0Scaslx/Zk+M8MW/fgJzUvSV09
5kwzN3AUlm8be6ska76WAkIY85jeLRfMANinnKvwAL+2OR6C+R47D3yixIez
jgWeMyS155N0ZjZLMmlQJAP70U4hy+CuP1YFIzAxywjzWWhh7KaNM7t/xgQH
pDW70VKFiMQacUbApJkBZxRjOPs+wBjNGPAwxo1QrGCMsWE0nBFf9/8PTuq1
MF9jcq8O0FYrrlz3+pMybEDZeYkVXks5E0EIol8GHdRZKi2aKExbxBWpy2hM
aqJh+P3UqldDDt/C9T/07E36uZRgECy4qGZRLQIX3NevYfUGYwskuIj7SI24
ldxNkxVq076opEbS3L/TxIxJ+l4qFRGco6m7PE6CEysqFdN/6ZVqrRptOFdw
mDiJti2RQup2xhVFGlfkB/nYmEnKRqKqImeVG9amc5+uvGvoOLUDxLWFWEg7
agAn156MODlBgb8FQF9pNhGtkEKumTdI4Qbs0caGNQd2NjOPWBdA8Mc6cdjH
ODLHW8SdUK3ZlRp9S5vszIWJkK2T7BQsG9dQKMpjO9VatMce1HmmX5H1KqvJ
KCQWLhNa3JVCEypAmuIeW4Cz0sTTE8vtYVNQFCrFMrlrHVFDirGP+Cm81jlq
FsYhdEXelna9w4l7Eyt9thmP/LV1Qwk86N6rDHNiCwfZxDRzgYgSI0ctNIqa
Rb5YtOTK/TpjbKNOfGTuXQtf0852msqq7A2SkiC2XrAYjNoyc93xS0tnE54m
a0GkINmgKNgXLlY41wDLMoIQDYeqyIWgGFeTqUc2f8zpU11akmyN4GdJiC8d
dkE8JM3BOVG+AVxzWIuFUnAMPRUvnP6CceFJrVQdR8IBbd6ORJU4YV9uWYOw
nBIX6vLq2fl6lPHaE2OUFHnJ8A1bkV+Jnw1rn27XuNktZ7HN1aEO5RI75vuU
rFaQGoWBbJXTkLRuklJM1JabGNnUkTWUH/nCahMLMcdXtOdCFWQ6dU2ElAys
FERyrDE8TkkHLdEuKLe48yGZ51wwBbbVxDmsKckWVwtSKcTVU1MWwsn0zkk1
tfW2KD6a9WW2AdWxam6F3lx2wgASCRKVgprG6czFv4ZtkVw+Zsaij1JImqkU
zL83FHhVydMpew8zF4WNDhisAjwwjrEAje2OmctjZqpTrE+KdoiCVv9lIPnF
lexql9t9o2phqL1ihn03GWVSmJNaHew4NrKds2jndmJLv/V2ojY9U2Md24nO
oj/u9Hb+JI/UW8BgxD9OnvZ6T9sbut1Mnvafb/fYaa+33YNxT362eXjQC362
eGm4f7i//aO9p39iSK017RmAycNr7HT2UW438W96zKRbPeacDzae88F253yw
3Tlv9Rie81YP6jlv9XB4ztu8JOd88DR6xAkebH+CB5UThMeXxafyAU5h9QmN
4Y85zc7+0c6G48RH/rT5PA+e959vAZ8DOKrtHpSj2u7h4Ki2eml4gEcFjz7i
qGiX2x4WPxwc1/HRp0FafsqSu03n9AZl2aKsVNnceAE7/eeHh8cnh4e9k4OT
3unRUf+4f7zVpTwYjIOf7eD4vPLaI0BanXNrANe8GoAbYzo+SYr/FvfCDY8D
ti2CxMFZhK1ne/u9g023Ba4oPfd0mztzeCAPbwby0fiw3+sDwsLjW53K0fjo
OYzeP1KSp69ufzJmedueh30h5DIgmzziFKhTgZzC00nKKsLTTaD/ZUcf/WVn
M/RbAqfj5/C/0/3eySH8e3Syf3ykwJ08PRlXv7XAp+8PzfcNT5wgbzJPnYQ8
xX1r25NZs/TtTmrdAMHJkTS/zZlxIM8f+20sinTwp02HZR/c4p483/6enI75
UQDnI8j688di+vMmTAeVh6FlK1NxLuOIKzuTjovB16gLOA0sws4bb2OpfcwV
VMR3ZBWkpjQfe0rhIcGIGqeA5nSOteFkbpUGtGQKHV7j2dEZ7Hztn/2y8+WX
HThG+GWFvxzAL//6y843Pnv3EfnGPGsfCV9uR/JSzSPhcPaR8OWaicIlOBMx
omxBK2I49eP+yfPePvz3tHcA/43tXTff0uf8jPet8xY/WfOtM4L3rfNWzcjO
jOHIg3H1W5dCxQdWKMbnSJamZyvyL4/MwNp4qaL/A4HGW9uGeDZsq4YafNLo
U5+GVkmoXkq6hXRRhQNueSMBx3/ZiQfDX2A4IK6/wAxj/H0ff7+bpPj7gd6H
ysP6gPui97A7Wt2LjQ+7I+uL3sN1DzQuo26d/siPuM3HcGrH+8d4kgfAv4+O
j+E0D45PkCtablN5Ur637wRP2pEq7zQ+aceUd4InK983zl5ZXd2Yg/H6vbsU
YjAGOadPT8MTY2Cw8Pc+vdM/Poa/90/G+ib8ZWTMbWnE1iex9UFsfQ5bH8PW
p7DFITyOymyATBSSnHlepKgtfpI+GoEw4tb9D4Pw2eOPQoiGPq6NDXPKz1Ji
fdiLQAu5rRNKzs16ZWXrCd3Oyen+/nOAxxGoQseHBwcnR6cHR4cHp0e9gwMx
U6yVJIf7h8NQZ9xW1aW3E2SEjSNEWyL+hoVsgyGbBwkQQ80IDYhhqmiYGAWs
LIkY4dY0dcOgYttmoy09JLjNh5EnN4UXdtcpFddq9pC6sGg2x3wKdCWxHOtN
ttGMVWMUOdleTRweHIKU0GT4pe+HKiatewr0+CMrUB0+D5/9DWpgw9K2UmUM
oWkaJEAibF34KZnnw8mnMr5rwiEThksoYtw4pi+IWxopy6NKJcUR5cFUQ3rI
NuAUvNEnTPwROkvvKVEpzMuVAKpmdDvPItoXTY6zbDSz9Xf7JyfHx/3Dg6Oj
va3Ma8N+Pz4+TQ7Hg9E2uuzoee+RL6Ds/shXVPh/5GsV3eBRrwMgzADmte3V
dQ+O2+F59TXA7Cpqs8j9fzhuV5ks4bSoEwa113jqdn/Z2Qcxo9M77PRPb3sH
Z0enZ/2jf/llR/F8E8UEYPdODg/2QcvaPzjeH8G/h/DfPnDqQ/j94CA+ODo4
hf/24fLERnYCjP9Nr5Gf77e8aPx+v+Xlih/wNwwCYBpv/5oRUvjF43188WR/
y1e3FE5+ywFuJ7H8ppHDe4ot7LcxSEqpEZZlnuJbTzeSdHxqK0o+PnoEuRpv
a5flRwOWy/vo9/tVihRsEp7hgg8ctGVymRyD45ADISnB05Si8BttZFjvq5D8
CXf8teyzAnFYzEZw8wu78Oh2/HP8/Pgx/gv38c2Qp4cD2FPgz6dtQiFe+yFC
RqvBdzeJpr3udqER423DGcaPCWcYV8MZHgHi0+1lTefxWjBzssYmQL+qpHRQ
/BOPsVlm656cnhyfAm05fA7Us390knx/0Hu+HfgHJ+Pkt3o5m1/eDLSaV9cA
8JOJCQsJBgVVmW9t4FQQp1oJY2tOhFpLEqonpRqdXQOfWvOhkeZmkoe2cBWN
B4FK1X+MH2jN21scU+Xd+mPinMlNeH5DT/1WPO/0j09OTvb7x9uSlsGwf+IT
gW3IzFD2/JiLUHlpM2SdV9ZANET8R8A2RMhN4D3qPj85OTzpnxwdAvM6PDg5
uuwcnG4J6YMAT7Yk6If88GOw2b61PajtK7WgxpjUTeAN4lYfBdnjo6Pe4dZI
e9gDwjh8JCgPT4Cebvnw6cngcZ5keWN7hsiPh0KuBfb2WP2TD/bH4vRBt3cE
CH3yvL8P2Hy0LTKPfwMy6w3Y6gR6+4/Een7jESLJfiO2A8f6lGYUVRwGQTSa
K6/k+Q2W7I55bqNGjYtELN9soB6Dmvd8K9Di2YEkUSP3bQdjWs9Wngz7dC2I
QfBIANBxtgG+gYBNr2F1pw1gxie2AvBJsh2AT4TebAPgEz2N3wBgWs/WAOan
63E4zj5pXU0CMapqABa/Up9bcoEj2DcmVAR1PGxCjSZ9YtoKj1UfZx/TMsiW
b0p/OgmjmtJsSrRqbba6nHXNm11nB4teV2qD6bTPrIpMAOl96Y/H61FrO6wa
beNXQqwabMWTBKtOPKa3JVZthUwWh/jnfwE1tUp7cYIBAA==

-->

</rfc>
