Sandelman Software Works

mcr+ietf@sandelman.ca

Universität Bremen TZI

Postfach 330440 D-28359 Bremen Germany +49-421-218-63921 cabo@tzi.org

Internet CBOR Working Group Internet-Draft This document defines an on-disk format for CBOR data items that is friendly to common on-disk recognition systems such as the Unix file(1) command. About This Document Status information for this document may be found at . Discussion of this document takes place on the cbor Working Group mailing list (), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction Since very early in computing, operating systems have sought ways to mark which files could be processed by which programs. In Unix, everything is a stream of bytes (related to the TCP/IP socket model, where all network connectivity also is a stream of bytes); identifying the contents of a stream of bytes became a heuristic activity. For instance, the Unix file(1) command, which has existed since 1973 , has for decades been able to identify many file formats based upon the contents of the file. Many systems (Linux, macOS, Windows) will select the correct application based upon the file contents, if the system can not determine it by other means. For instance, in classical MacOS, a resource fork was maintained that includes media type ("MIME type") information and therefore ideally never needs to know anything about the file. But, many other systems do this by file extensions. Many common web servers derive the media-type information from file extensions. Having a media type associated with the file is a better solution in general. When files become disconnected from their type information, such as when attempting to do forensics on a damaged system, then being able to identify a file type can become very important. It is noted that in the media type registration template, a magic number is asked for, if available, as is a file extension. A challenge for the file(1) program is often that it can be confused by the encoding vs the content. For instance, an Android "apk" used to transfer and store an application may be identified as a ZIP file. Additionally, both OpenOffice and MSOffice files are ZIP files of XML files, and may also be identified as a ZIP file. As CBOR becomes a more and more common encoding for a wide variety of artifacts, identifying them as just "CBOR" is probably not sufficient. This document provides a way to encode a magic number into the beginning of a CBOR format file. As a CBOR format may use a single CBOR data item or a CBOR sequence of data items , two possible methods of enveloping data are presented: a CBOR Protocol designer will specify one. (A CBOR Protocol is a specification which uses CBOR as its encoding.) A third method is also proposed by which this CBOR format prepended tag is used to identify non-CBOR files. This third method has been placed in an appendix because it is not about identifying media types containing CBOR-encoded data items. This document also gives advice to designers of CBOR protocols on choosing one of these mechanisms for identifying their contents. This advice is informative. Examples of CBOR Protocols currently under development include Concise Software Identification Tags (CoSWID, ) and Entity Attestation Tokens (EAT, ). COSE itself is considered infrastructure. The encoding of public keys in CBOR as described in as C509 would benefit from being an identified CBOR Protocol. A major inspiration for this document is observing the disarray in certain ASN.1 based systems where most files are PEM encoded; these are then all identified by the extension "pem", confusing public keys, private keys, certificate requests, and S/MIME content. While the envelopes defined in this specification add information to how data conforming to CBOR Protocols are stored in files, there is no requirement that either type of envelope be transferred on the wire. In addition to the on-disk identification aspects, there are some protocols which may benefit from having such a magic number on the wire if they are presently using a different (legacy) encoding scheme. The presence of the identifiable magic sequence signals that CBOR is being used as opposed to a legacy scheme. In addition, for convenience, defines a simple way to retroactively add a magic number to content-formats as defined by , even if not in CBOR form.

Terminology Byte is a synonym for octet. The term "byte string" refers to the data item defined in . The term "diagnostic notation" refers to the human-readable notation for CBOR data items defined in and . The term CDDL (Concise Data Definition Language) refers to the language defined in .

Requirements for a Magic Number A magic number is ideally a fingerprint that is unique to a CBOR protocol, present in the first few (small multiple of 4) bytes of the file, which does not change when the contents change, and does not depend upon the length of the file. Less ideal solutions have a pattern that needs to be matched, but in which some bytes need to be ignored. While the Unix file(1) command can be told to ignore certain bytes, this can lead to ambiguities.

Protocol This Section presents two enveloping methods. Which one is to be used is up to the CBOR Protocol designer to determine. Both use CBOR Tags in a way that results in a deterministic first 8 to 12 bytes.

The CBOR Protocol Specific Tag In both enveloping methods, CBOR Protocol designers need to obtain a CBOR tag for each kind of object that they might store on disk. As there are more than 4 billion available 4-byte tags, there should be little issue in allocating a few to each available CBOR Protocol. The IANA policy for 4-byte CBOR Tags is First Come First Served, so all that is required is an email to IANA, having filled in the small template provided in . In the template, it is suggested to include a reference to this specification (RFC XXXX) alongside the Description of semantics. (Note to RFC Editor: Please replace all occurrences of "RFC XXXX" with the RFC number of the present specification and remove this note.) This tag needs to be allocated by the author of the CBOR Protocol. In order to be in the four-byte range, and so that there are no leading zeros, the value needs to be in the range 0x01000000 (decimal 16777216) to 0xFFFFFFFF (decimal 4294967295). It is further suggested to avoid values that have an embedded zero byte in the four bytes of their binary representation (such as 0x12003456), as these may confuse implementations that treat the magic number as a C string. The use of a sequence of four US-ASCII codes which are mnemonic to the protocol is encouraged, but not required. For CBOR data items that form a representation that is described by a CoAP Content-Format Number (, Registry of ), a tag number has already been allocated in (see for details and examples).

Enveloping Method: CBOR Tag Wrapped The CBOR Tag Wrapped method is appropriate for use with CBOR protocols that encode a single CBOR data item. This data item is enveloped into two nested tags: The outer tag is a Self-described CBOR tag, 55799, as described in . The tag content of that tag is a second CBOR Tag that has been allocated to describe the specific Protocol involved, as described above. This method wraps the CBOR value as tags usually do. Applications that need to send the CBOR value across a constrained link may wish to remove the two tags if the use is implicitly understood. A CBOR Protocol specification may specify the use of two tags only for specific cases. For instance, it might use them when storing the representation in a local file or for Web access, but not when using them in protocol messages that already provide the necessary context.

Example To construct an example without registering a new tag, we use the technique described in to translate the Content-Format number registered for application/senml+cbor (as per Registry of ), the number 112, into the tag 1668546560+112 = 1668546672. With this tag, the SenML-CBOR pack [{0: "current", 6: 3, 2: 1.5}] would be enveloped as (in diagnostic notation): 55799(1668546672([{0: "current", 6: 3, 2: 1.5}])) Or in hex: d9 d9f7 # tag(55799) da 63740070 # tag(1668546672) 81 # array(1) a3 # map(3) 00 # unsigned(0) 67 # text(7) 63757272656e74 # "current" 06 # unsigned(6) 03 # unsigned(3) 02 # unsigned(2) f9 3e00 # primitive(15872) At the representation level, the unique fingerprint for application/senml+cbor is composed of the 8 bytes d9d9f7da63740070 hex, after which the unadorned CBOR data (81... for the SenML data) is appended.

Enveloping Method: Labeled CBOR Sequence The Labeled CBOR Sequence method is appropriate for use with CBOR Sequences as described in . This method prepends a newly constructed, separate data item to the CBOR Sequence, the label. The label is a nesting of two tags, similar to but distinct from the CBOR Tag Wrapped methods, with an inner tag content of a constant byte string. The total length of the label is 12 bytes.

1. The outer tag is the self-described CBOR Sequence tag, 55800.
2. The inner tag is a CBOR tag, from the First Come First Served space, that uniquely identifies the CBOR Protocol. As with CBOR Tag Wrapped, the use of a four-byte tag is encouraged that encodes without zero bytes.
3. The tag content is a three byte CBOR byte string containing 0x42_4F_52 ('BOR' in diagnostic notation).

The outer tag in the label identifies the file as being a CBOR Sequence, and does so with all the desirable properties explained in . Specifically, it does not appear to conflict with any known file types, and it is not valid Unicode in any Unicode encoding. The inner tag in the label identifies which CBOR Protocol is used, as described above. The inner tag content is a constant byte string which is represented as 0x43_42_4f_52, the ASCII characters "CBOR", which is the CBOR encoded data item for the three-byte string 0x42_4f_52 ('BOR' in diagnostic notation). The actual CBOR Protocol data then follow as the next data item(s) in the CBOR Sequence, without a need for any further specific tag. The use of a CBOR Sequence allows the application to trivially remove the first item with the two tags. Should this file be reviewed by a human (directly in an editor, or in a hexdump display), it will include the ASCII characters "CBOR" prominently. This value is also included simply because the inner nested tag needs to tag something.

Advice to Protocol Designer This document introduces a choice between wrapping a single CBOR data item into a (pair of) identifying CBOR tags, or prepending an identifying encoded CBOR data item (which in turn contains a pair of identifying CBOR tags) to a CBOR Sequence (which might be single data item). Which should a protocol designer use? In this discussion, one assumes that there is an object stored in a file, perhaps specified by a system operator in a configuration file. For example: a private key used in COSE operations, a public key/certificate in C509 () or CBOR format, a recorded sensor reading stored for later transmission, or a COVID vaccination certificate that needs to be displayed in QR code form. Both the Labeled CBOR Sequence and the wrapped tag can be trivially removed by an application before sending the CBOR content out on the wire. The Labeled CBOR Sequence can be slightly easier to remove as in most cases, CBOR parsers will return it as a unit, and then return the actual CBOR item, which could be anything at all, and could include CBOR tags that do need to be sent on wire. On the other hand, having the Labeled CBOR Sequence in the file requires that all programs that expect to examine that file are able to skip what appears to be a CBOR item with two tags nested around a three-byte byte string. The three byte entry is not of the format the program would normally have processed, so it may be a surprise. On the other hand, CBOR parsers are generally tolerant of tags that appear: many of them will process extra tags, making unknown tags available as meta information. A program that is not expecting those tags may just ignore those extra tags. As an example of where there was a problem with previous security systems, "PEM" format certificate files grew to be able to contain multiple certificates by simple concatenation. The PKCS1 format could also contain a private key object followed by a one or more certificate objects: but only when in PEM format. Annoyingly, when in binary DER format (, which like CBOR is self-delimiting), concatenation of certificates was not compatible with most programs as they did not expect to read more than one item in the file. The use of CBOR Tag Wrapped format is easier to retrofit to an existing format with existing and unchangeable on-disk format for a single CBOR data item. This new sequence of tags is expected to be trivially ignored by many existing programs when reading CBOR from disk, even if the program only supports decoding a single data item (and not a CBOR sequence). But, a naive program might also then transmit the additional tags across the network. Removing the CBOR Tag Wrapped format requires knowledge of the two tags involved. Other tags present might be needed. For a representation matching a specific media-type that is carried in a CBOR byte string, the byte string head will already have to be removed for use as such a representation, so it should be easy to remove the enclosing tag heads as well. This is of particular interest with the pre-defined tags provided by for media-types with CoAP Content-Format numbers. Here are some considerations in the form of survey questions:

Is the on-wire format new? If the on-wire format is new, then it could be specified with the CBOR Tag Wrapped format if the extra eight bytes are not a problem. The disk format is then identical to the on-wire format. If the eight bytes are a problem on the wire (and they often are if CBOR is being considered), then the Labeled CBOR Sequence format should be adopted for on-disk storage.

Can many items be trivially concatenated? If the programs that read the contents of the file already expect to process all of the CBOR data items in the file (not just the first), then the Labeled CBOR Sequence format may be easily retrofitted. The program involved may throw errors or warnings on the Labeled CBOR Sequence if they have not yet been updated, but this may not be a problem. There are situations where multiple objects may be concatenated into a single file. If each object is preceded by a Labeled CBOR Sequence label then there may be multiple such labels in the file. A protocol based on CBOR Sequences may specify that Labeled CBOR Sequence labels can occur within a CBOR Sequence, possibly even to switch to data items following in the sequence that are of a different type. If the CBOR Sequence based protocol does not define the semantics for or at least tolerate embedded labels, care must be taken when concatenating Labeled CBOR Sequences to remove the label from all but the first part. If only one item is ever expected in the file, the use of Labeled CBOR Sequence may present an implementation hurdle to programs that previously just read a single data item and used it.

Are there tags at the start? If the Protocol expects to use other tags values at the top-level, then the use of the tag wrapped format may be easier to explain in the protocol description.

Security Considerations This document provides a way to identify CBOR Protocol objects. Clearly identifying CBOR contents on disk may have a variety of impacts. The most obvious is that it may allow malware to identify interesting objects on disk, and then exfiltrate or corrupt them.

IANA Considerations These IANA considerations are entirely about CBOR Tags, in the registry of . documents the allocation that was done for a CBOR tag to be used in a CBOR sequence to identify the sequence (an example for using this tag is found in ). allocates a CBOR tag for each actual or potential CoAP Content-Format number (examples are in ).

Labeled CBOR Sequence Tag IANA has allocated tag 55800 as the tag for the Labeled CBOR Sequence Enveloping Method from the CBOR Tags Registry. IANA is asked to update this tag registration to point to this document. This tag is from the First Come/First Served area. The value has been picked to have properties similar to the 55799 tag (). The hexadecimal representation of the encoded tag head is: 0xd9_d9_f8. This is not valid UTF-8: the first 0xd9 introduces a three-byte sequence in UTF-8, but the 0xd9 as the second value is not a valid second byte for UTF-8. This is not valid UTF-16: the byte sequence 0xd9d9 (in either endian order) puts this value into the UTF-16 high-half zone, which would signal that this a 32-bit Unicode value. However, the following 16-bit big-endian value 0xf8.. is not a valid second sequence according to . On a little-endian system, it would be necessary to examine the fourth byte to determine if it is valid. That next byte is determined by the subsequent encoding, and has already determined that no valid CBOR encodings result in valid UTF-16.

Data Item:

tagged byte string

Semantics:

indicates that the file contains CBOR Sequences

CBOR-Labeled Non-CBOR Data Tag IANA is requested to allocate tag 55801 as the tag for the CBOR-Labeled Non-CBOR Data Enveloping Method () from the CBOR Tags Registry. IANA is asked to update this tag registration to point to this document. This tag is from the First Come/First Served area. The value has been picked to have properties similar to the 55799 tag (). The hexadecimal representation of the encoded tag head is: 0xd9_d9_f9. This is not valid UTF-8: the first 0xd9 introduces a three-byte sequence in UTF-8, but the 0xd9 as the second value is not a valid second byte for UTF-8. This is not valid UTF-16: the byte sequence 0xd9d9 (in either endian order) puts this value into the UTF-16 high-half zone, which would signal that this a 32-bit Unicode value. However, the following 16-bit big-endian value 0xf9.. is not a valid second sequence according to . On a little-endian system, it would be necessary to examine the fourth byte to determine if it is valid. That next byte is determined by the subsequent encoding, and has already determined that no valid CBOR encodings result in valid UTF-16.

Data Item:

tagged byte string

Semantics:

indicates that the file starts with a CBOR-Labeled Non-CBOR Data label.

CBOR Tags for CoAP Content-Format Numbers IANA is requested to allocate the tag numbers 1668546560 (0x63740000) to 1668612095 (0x6374FFFF) as follows:

Data Item:

byte string

Semantics:

for each tag number NNNNNNNN, the representation of content-format NNNNNNNN-1668546560

Reference:

RFCthis

The Registry for of has been defined in .

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. This document describes the Concise Binary Object Representation (CBOR) Sequence format and associated media type "application/cbor-seq". A CBOR Sequence consists of any number of encoded CBOR data items, simply concatenated in sequence. Structured syntax suffixes for media types allow other media types to build on them and make it explicit that they are built on an existing media type as their foundation. This specification defines and registers "+cbor-seq" as a structured syntax suffix for CBOR Sequences. Informative References Wikipedia 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. The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments. IANA IANA This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm, covering cryptographic primitives, encryption schemes, signature schemes with appendix, and ASN.1 syntax for representing keys and for identifying the schemes. This document represents a republication of PKCS #1 v2.2 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series. By publishing this RFC, change control is transferred to the IETF. This document also obsoletes RFC 3447. This document specifies alternative Constrained Application Protocol (CoAP) block-wise transfer options: Q-Block1 and Q-Block2. These options are similar to, but distinct from, the CoAP Block1 and Block2 options defined in RFC 7959. The Q-Block1 and Q-Block2 options are not intended to replace the Block1 and Block2 options but rather have the goal of supporting Non-confirmable (NON) messages for large amounts of data with fewer packet interchanges. Also, the Q-Block1 and Q-Block2 options support faster recovery should any of the blocks get lost in transmission. ITU-T Fraunhofer SIT National Security Agency The MITRE Corporation National Institute of Standards and Technology ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an extensible XML-based structure to identify and describe individual software components, patches, and installation bundles. SWID tag representations can be too large for devices with network and storage constraints. This document defines a concise representation of SWID tags: Concise SWID (CoSWID) tags. CoSWID supports a similar set of semantics and features as SWID tags, as well as new semantics that allow CoSWIDs to describe additional types of information, all in a more memory efficient format. Security Theory LLC Qualcomm Technologies Inc. Qualcomm Technologies Inc. An Entity Attestation Token (EAT) provides an attested claims set that describes state and characteristics of an entity, a device like a phone, IoT device, network equipment or such. This claims set is used by a relying party, server or service to determine how much it wishes to trust the entity. An EAT is either a CBOR Web Token (CWT) or JSON Web Token (JWT) with attestation-oriented claims. To a large degree, all this document does is extend CWT and JWT. Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need for the ability to have basic security services defined 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. Ericsson AB Ericsson AB RISE AB RISE AB Nexus Group This document specifies a CBOR encoding of X.509 certificates. The resulting certificates are called C509 Certificates. The CBOR encoding supports a large subset of RFC 5280 and all certificates compatible with the RFC 7925, IEEE 802.1AR (DevID), CNSA, RPKI, GSMA eUICC, and CA/Browser Forum Baseline Requirements profiles. When used to re-encode DER encoded X.509 certificates, the CBOR encoding can in many cases reduce the size of RFC 7925 profiled certificates with over 50%. The CBOR encoded structure can alternatively be signed directly ("natively signed"), which does not require re- encoding for the signature to be verified. The document also specifies C509 COSE headers, a C509 TLS certificate type, and a C509 file format. This document describes the UTF-16 encoding of Unicode/ISO-10646, addresses the issues of serializing UTF-16 as an octet stream for transmission over the Internet, discusses MIME charset naming as described in [CHARSET-REG], and contains the registration for three MIME charset parameter values: UTF-16BE (big-endian), UTF-16LE (little- endian), and UTF-16. This memo provides information for the Internet community.

CBOR Tags for CoAP Content Formats defines the concept of a Content-Format, which is a short 16-bit unsigned integer that identifies a specific content type (media type plus optionally parameters), optionally together with a content encoding. Outside of a transfer protocol that indicates the Content-Format for a representation, it may be necessary to identify the Content-Format of the representation when it is on disk, in firmware, or when debugging. This specification allocates CBOR tag numbers 1668546560 (0x63740000) to 1668612095 (0x6374FFFF) for the tagging of representations of specific content formats. The tag content tagged with tag number NNNNNNNN (in above range) is a byte string that is to be interpreted as a representation of the content format NNNNNNNN-1668546560. Exceptionally, when used immediately as tag content of one of the tags 55799, 55800, or 55801, the tag content is as follows:

Tag 55799 ():

One of:

1. The CBOR data item within the representation (without byte string wrapping). This only works for Content Formats that are represented by a single CBOR data item in identity content-coding.
2. The data items in the CBOR sequence within the representation, without byte string wrapping, but wrapped in a CBOR array. This works for Content Formats that are represented by a CBOR sequence in identity content-coding.

Tags 55800 () or 55801 ():

the byte string 'BOR', signifying that the representation of the given content-format follows in the file, in the way defined for these tags.

Content-Format Tag Examples Registry of defines content formats that can be used as examples:

• As discussed in , Content-Format 112 stands for media type application/senml+cbor (no parameters). The corresponding tag number is 1668546672 (i.e., 1668546560+112). So the following CDDL snippet can be used to identify application/senml+cbor representations: senml-cbor = #6.1668546672(bstr) Note that a byte string is used as the type of the tag content, because a media type representation in general can be any byte string.
• Content-Format 272 stands for media type application/missing-blocks+cbor-seq, a CBOR sequence . The corresponding tag number is 1668546832 (i.e., 1668546560+272). So the following CDDL snippet can be used to identify application/missing-blocks+cbor-seq representations as embedded in a CBOR byte string: missing-blocks = #6.1668546832(bstr)

Example from Openswan The Openswan IPsec project has a daemon ("pluto"), and two control programs ("addconn", and "whack"). They communicate via a Unix-domain socket, over which a C-structure containing pointers to strings is serialized using a bespoke mechanism. This is normally not a problem as the structure is compiled by the same compiler; but when there are upgrades it is possible for the daemon and the control programs to get out of sync by the bespoke serialization. As a result, there are extra compensations to deal with shutting the daemon down. During testing it is sometimes the case that upgrades are backed out. In addition, when doing unit testing, the easiest way to load policy is to use the normal policy reading process, but that is not normally loaded in the daemon. Instead the IPC that is normally sent across the wire is compiled/serialized and placed in a file. The above magic number is included in the file, and also on the IPC in order to distinguish the "shutdown" command CBOR operation. In order to reduce the problems due to serialization, the serialization is being changed to CBOR. Additionally, this change allows the IPC to be described by CDDL, and for any language that encode to CBOR can be used. IANA has allocated the tag 1330664270, or 0x4f_50_53_4e for this purpose. As a result, each file and each IPC is prefixed with a CBOR TAG Sequence. In diagnostic notation: 55800(1330664270(h'424F52')) Or in hex: D9 D9F8 # tag(55800) DA 4F50534E # tag(1330664270) 43 # bytes(3) 424F52 # "BOR"

Using CBOR Labels for non-CBOR data The CBOR-Labeled non-CBOR data method is appropriate for adding a magic number to a non-CBOR data format, particularly one that can be described by a Content-Format tag (). This method prepends a CBOR data item to the non-CBOR data; this data item is called the "header" and, similarly to the Labeled CBOR-Sequence label, consists of two nested tags around a constant byte string for a total of 12 bytes.

1. The outer tag is the CBOR-Labeled Non-CBOR Data tag, 55801.
2. The inner tag is a CBOR tag, from the First Come First Served space, that uniquely identifies the CBOR Protocol. As with CBOR Tag Wrapped, the use of a four-byte tag is encouraged that encodes without zero bytes.
3. The tag content is a three byte CBOR byte string containing 0x42_4F_52 ('BOR' in diagnostic notation).

The outer tag in the label identifies the file as being file as being prefixed by a non-CBOR data label, and does so with all the desirable properties explained in . Specifically, it does not appear to conflict with any known file types, and it is not valid Unicode in any Unicode encoding. The inner tag in the label identifies which non-CBOR Protocol is used. The inner tag content is a constant byte string which is represented as 0x43_42_4f_52, the ASCII characters "CBOR", which is the CBOR encoded data item for the three-byte string 0x42_4f_52 ('BOR' in diagnostic notation). The actual non-CBOR Protocol data then follow directly appended to the CBOR representation of the header. This allows the application to trivially remove the header item with the two nested tags and the byte string. Should this file be reviewed by a human (directly in an editor, or in a hexdump display), it will include the ASCII characters "CBOR" prominently to indicate the nature of the header. This value is also included simply because the two tags need to tag something.

Content-Format Tag Examples Registry of defines content formats that can be used as examples:

• Content-Format 432 stands for media type application/td+json (no parameters). The corresponding tag number is 1668546992 (i.e., 1668546560+432). So the following CDDL snippet can be used to identify a CBOR-Labeled non-CBOR data for application/td+json representations: td-json-header = #6.55801(#6.1668546992('BOR'))
• Content-Format 11050 stands for media type application/json in deflate content-coding. The corresponding tag number is 1668557610 (i.e., 1668546560+11050). So the following CDDL snippet can be used to identify a CBOR-Labeled non-CBOR data for application/json representations compressed in deflate content-coding: json-deflate-header = #6.55801(#6.1668557610('BOR'))

Changelog

Acknowledgements The CBOR WG brainstormed this protocol on January 20, 2021 via a number of productive email exchanges on the mailing list.

Contributors

jeffpc@josefsipek.net