Skip to main content

The BinaryPack1pre2 JSON-like representation format

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Carsten Bormann
Last updated 2013-08-29 (Latest revision 2013-02-25)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


JSON (RFC 4627) is an extremely successful format for the representation of structured information, supporting Boolean values, numbers, strings, arrays, and tables. Recently, a number of applications have started to look for binary representation formats that solve a similar problem. In particular, constrained node networks can benefit from such a binary representation format. A very successful binary representation that is otherwise comparable to JSON is MessagePack. Recently, a number of implementations have modified or extended MessagePack such that it allows for distinguishing UTF-8 strings from binary data. Further discussion on the MessagePack repository has resulted in proposals how to integrate such an addition back into the MessagePack community. This draft, as an independent effort, documents one such format, tentatively calling it BinaryPack1pre2 while the MessagePack extension proposals make their way through the MessagePack community. The current version -01 of this document is a snapshot that demonstrates a general direction. The details may change in future versions based on the development of the MessagePack specification.


Carsten Bormann

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)