Skip to main content

Concise Binary Object Representation Maintenance and Extensions
charter-ietf-cbor-00-01

The information below is for an older proposed charter
Document Proposed charter Concise Binary Object Representation Maintenance and Extensions WG (cbor) Snapshot
Title Concise Binary Object Representation Maintenance and Extensions
Last updated 2016-11-29
State Start Chartering/Rechartering (Internal Steering Group/IAB Review) Rechartering
WG State Proposed
IESG Responsible AD Orie Steele
Charter edit AD Alexey Melnikov
Send notices to (None)

charter-ietf-cbor-00-01

Concise Binary Object Representation (CBOR, RFC 7049) extends the JavaScript Object Notation (JSON, RFC 7159) data model to include binary data and an extensibility model, using a binary representation format that is easy to parse correctly. It has been picked up by a number of IETF efforts (e.g., COSE, GRASP) as a message format.

The CBOR working group will update RFC 7049 to fix verified errata. Security issues and clarifications may be addressed, but changes to the document will ensure backward compatibility for popular deployed codebases. The resulting document will be targeted at becoming an Internet Standard.

Similar to the way ABNF (RFC 5234/7405) can be used to describe the set of valid messages in a text representation, it would be useful if protocol specifications could use a description format for the data in CBOR-encoded messages. The CBOR data definition language (CDDL) is a proposal for such a description technique that has already been used successfully in COSE, GRASP, and efforts outside the IETF. The CBOR WG will complete the development of this specification by creating an RFC that can be used as a normative reference in a protocol specification.

In parallel to the work on CDDL, the WG will examine the CBOR extension for tagging of Typed Arrays (based on draft-jroatch-cbor-tags) and the CBOR extension for tagging of Object Identifiers and UUIDs (based on draft-bormann-cbor-tags-oid) that use CBOR's extensibility mechanisms to provide additional data types as used in certain applications. Where these proposals are deemed useful and do not require significant new development, the CBOR WG will complete these specifications as well.