]> Blockchain Commons

wolf@wolfmcnally.com

Blockchain Commons

christophera@lifewithalacrity.com

Applications and Real-Time Network Working Group Internet-Draft CBOR (RFC 8949) defines "Deterministically Encoded CBOR" in its Section 4.2. The present document provides the application profile "dCBOR" that can be used to help achieve interoperable deterministic encoding. Discussion Venues Source for this draft and an issue tracker can be found at .

Introduction CBOR has many advantages over other data serialization formats. One of its strengths is specifications and guidelines for serializing data deterministically, such that multiple agents serializing the same data automatically achieve consensus on the exact byte-level form of that serialized data. This is particularly useful when data must be compared for semantic equivalence by comparing the hash of its contents. Nonetheless, determinism is an opt-in feature of CBOR, and most existing CBOR codecs put the primary burden of correct deterministic serialization and validation of deterministic encoding during deserialization on the engineer. This document specifies a set of requirements for the application profile "dCBOR" that MUST be implemented at the codec level. These requirements include but go beyond §4.2.

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Application Profile The dCBOR Application Profile specifies the use of Deterministic Encoding as defined in Section 4.2 of together with some application-level rules specified in this section. The application-level rules specified here do not "fork" CBOR. A dCBOR implementation produces well-formed, deterministically encoded CBOR according to , and existing generic CBOR decoders will therefore be able to decode it, including those that check for deterministic encoding. Similarly, generic CBOR encoders will be able to produce valid dCBOR if handed dCBOR conforming data model level information from an application. Note that the separation between standard CBOR processing and the processing required by the dCBOR application profile is a conceptual one: Both dCBOR processing and standard CBOR processing may be combined into a unified dCBOR/CBOR codec. The requirements in this document apply to encoding or decoding of dCBOR data, regardless of whether the codec is a unified dCBOR/CBOR codec operating in dCBOR-compliant modes, or a single-purpose dCBOR codec. Both of these are generically referred to as "dCBOR codecs" in this document. This application profile is intended to be used in conjunction with an application, which typically will use a subset of CBOR, which in turn influences which subset of the application profile is used. As a result, this application profile places no direct requirement on what subset of CBOR is implemented. For instance, there is no requirement that dCBOR implementations support floating point numbers (or any other kind of number, such as arbitrary precision integers or 64-bit negative integers) when they are used with applications that do not use them. However, this document does place requirements on dCBOR implementations that support negative 64-bit integers and 64-bit or smaller floating point numbers.

Base Requirements dCBOR encoders MUST only emit CBOR conforming to the requirements "Core Deterministic Encoding Requirements" of §4.2.1. To summarize, dCBOR encoders:

1. MUST encode variable-length integers using the shortest form possible.
2. MUST encode floating-point values using the shortest form that preserves the value.
3. MUST NOT encode indefinite-length arrays or maps.
4. MUST sort map keys in bytewise lexicographic order of their deterministic encodings.

In addition, dCBOR decoders:

5. MUST reject any variable length integers that are not encoded in the shortest form possible.

6. MUST reject any floating-point values that are not encoded in the shortest form that preserves the value.

7. MUST reject any indefinite-length arrays or maps.

8. MUST reject any maps whose keys are not sorted in bytewise lexicographic order of their deterministic encodings.

Duplicate Map Keys Standard CBOR defines maps with duplicate keys as invalid, but leaves how to handle such cases to the implementor (§2.2, §3.1, §5.4, §5.6). dCBOR encoders:

1. MUST NOT emit CBOR that contains duplicate map keys.

dCBOR decoders:

2. MUST reject encoded maps with duplicate keys.

Numeric Reduction dCBOR codecs that support floating point numbers (CBOR major type 7):

1. MUST support floating point binary16 as the most-preferred encoding for floating point values, followed by binary32, then binary64.

dCBOR encoders that support floating point numbers:

2. MUST reduce floating point values with no fractional part to the shortest integer encoding that can accurately represent them.

3. MUST reduce floating point values with a non-zero fractional part to the shortest floating point encoding that can accurately represent them.

dCBOR decoders that support floating point numbers:

4. MUST reject any encoded floating point values that are not encoded as the shortest encoding that can accurately represent them.

The above rules still produce well-formed CBOR according to the standard, and all existing generic decoders will be able to read it. It does exclude a map such as the following from being validated as dCBOR, even though it would be allowed in standard CBOR because:

• 10.0 is an invalid numeric value in dCBOR, and
• using the unsigned integer value 10 more than once as a map key is not allowed.

Reduction of Negative Zero defines a negative zero value -0.0. dCBOR encoders that support floating point:

1. MUST reduce all negative zero values to the integer value 0.

dCBOR decoders that support floating point:

2. MUST reject any encoded negative zero values.

Therefore with dCBOR, 0.0, -0.0, and 0 all encode to the same canonical single-byte value 0x00.

Reduction of NaNs and Infinities defines the NaN (Not a Number) value . This is usually divided into two types: quiet NaNs and signalling NaNs, and the sign bit is used to distinguish between these two types. The specification also includes a range of "payload" bits. These bit fields have no definite purpose and could be used to break determinism or exfiltrate data. dCBOR encoders that support floating point:

1. MUST reduce all NaN values to the binary16 quiet NaN value having the canonical bit pattern 0x7e00.
2. MUST reduce all +INF values to the binary16 +INF having the canonical bit pattern 0x7c00.
3. MUST reduce all -INF values to the binary16 -INF having the canonical bit pattern 0xfc00.

dCBOR decoders that support floating point:

4. MUST reject any encoded NaN values not having the canonical bit pattern 0x7e00.

5. MUST reject any encoded +INF values not having the canonical bit pattern 0x7c00.

6. MUST reject any encoded -INF values not having the canonical bit pattern 0xfc00.

65-bit Negative Integers The largest negative integer that can be represented in 64-bit two's complement (STANDARD_NEGATIVE_INT_MAX) is -2⁶³ (0x8000000000000000). However, standard CBOR major type 1 can encode negative integers as low as CBOR_NEGATIVE_INT_MAX, which is -2⁶⁴ (two's complement: 0x10000000000000000, CBOR: 0x3BFFFFFFFFFFFFFFFF). Negative integers in the range [CBOR_NEGATIVE_INT_MAX ... STANDARD_NEGATIVE_INT_MAX - 1] require 65 bits of precision, and are thus not representable in typical machine-sized integers. Because of this incompatibility between standard CBOR and typical machine-size representations, dCBOR disallows encoding negative integer values in the range [CBOR_NEGATIVE_INT_MAX ... STANDARD_NEGATIVE_INT_MAX - 1]. dCBOR encoders:

1. MUST NOT encode these values as CBOR major type 1.

dCBOR decoders:

2. MUST reject these encoded major type 1 CBOR values.

Simple Values CBOR Major Type 7 includes the floating point values (0xf7, 0xfa, 0xfb) and also the "simple values" false (0xf4), true (0xf5), and null (0xf6). dCBOR encoders:

1. MUST NOT encode major type 7 values other than false, true, null, and the floating point values.

dCBOR decoders:

2. MUST reject any encoded major type 7 values other than false, true, null, and the floating point values.

Reference Implementations This section is informative. These are single-purpose dCBOR codecs that conform to these specifications:

• Swift implementation
• Rust implementation
• TypeScript implementation

Security Considerations This document inherits the security considerations of CBOR . Vulnerabilities regarding dCBOR will revolve around whether an attacker can find value in producing semantically equivalent documents that are nonetheless serialized into non-identical byte streams. Such documents could be used to contain malicious payloads or exfiltrate sensitive data. The ability to create such documents could indicate the failure of a dCBOR decoder to correctly validate according to this document, or the failure of the developer to properly specify or implement application protocol requirements using dCBOR. Whether these possibilities present an identifiable attack surface is a question that developers should consider.

IANA Considerations This document makes no requests of IANA.

Other Approaches As of this writing the specification of deterministic CBOR beyond is an active item before the CBOR working group. and are other approaches to deterministic CBOR.

References Normative References 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. 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. n.d. 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. 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. Informative References n.d. n.d. n.d. n.d. n.d. n.d.

Acknowledgments The authors are grateful for the contributions of Carsten Bormann and Anders Rundgren in the CBOR working group.