CBOR Equivalents of CoRE JSON Formats
draft-li-core-cbor-equivalents-00

Document Type Replaced Internet-Draft (individual)
Last updated 2015-03-09
Replaces draft-li-core-links-cbor
Replaced by draft-ietf-core-links-json
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-core-links-json
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-li-core-cbor-equivalents-00.txt

Abstract

JSON (RFC7159) is a text-based data format which is popular for Web based data exchanges. CBOR (RFC7049) is a binary data format which has been optimized for data exchanges for the Internet of Things. For many IoT scenarios, CBOR formats will be preferred since it can decrease transmission payload sizes compared to other data formats. This specification defines an approach for translating JSON objects, which are relevant for the CoRE WG and its related specifications, into CBOR format. Where applicable, mapping from other formats into JSON or CBOR is also described.

Authors

Kepeng Li (kepeng.lkp@alibaba-inc.com)
Ruinan Sun (sunruinan@huawei.com)
Akbar Rahman (Akbar.Rahman@InterDigital.com)

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