RFC 8949: Concise Binary Object Representation (CBOR)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8949
- Published
- December 2020
- Authors
- C. Bormann; P. Hoffman
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 66
- Also known as
- STD94
- Obsoletes:
- RFC 7049
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8746Concise Binary Object Representation (CBOR) Tags for Typed ArraysCurrent
February 2020
- RFC 8742Concise Binary Object Representation (CBOR) SequencesCurrent
February 2020
- RFC 9090Concise Binary Object Representation (CBOR) Tags for Object IdentifiersCurrent
July 2021
- RFC 9164Concise Binary Object Representation (CBOR) Tags for IPv4 and IPv6 Addresses and PrefixesCurrent
December 2021
- RFC 9165Additional Control Operators for the Concise Data Definition Language (CDDL)Current
December 2021
- RFC 8610Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data StructuresUpdated
June 2019
- RFC 9639Free Lossless Audio Codec (FLAC)Current
December 2024
- RFC 8984JSCalendar: A JSON Representation of Calendar DataCurrent
July 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?