Representing CoRE Formats in JSON and CBOR
draft-ietf-core-links-json-06

The information below is for an old version of the document
Document Type Expired Internet-Draft (core WG)
Last updated 2017-01-09 (latest revision 2016-07-08)
Replaces draft-li-core-cbor-equivalents, draft-bormann-core-links-json
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Jaime Jimenez
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Jaime Jimenez" <jaime.jimenez@ericsson.com>

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-ietf-core-links-json-06.txt

Abstract

JavaScript Object Notation, JSON (RFC7159) is a text-based data format which is popular for Web based data exchange. Concise Binary Object Representation, CBOR (RFC7049) is a binary data format which has been optimized for data exchange for the Internet of Things (IoT). For many IoT scenarios, CBOR formats will be preferred since it can help decrease transmission payload sizes as well as implementation code sizes compared to other data formats. Web Linking (RFC5988) provides a way to represent links between Web resources as well as the relations expressed by them and attributes of such a link. In constrained networks, a collection of Web links can be exchanged in the CoRE link format (RFC6690). Outside of constrained environments, it may be useful to represent these collections of Web links in JSON, and similarly, inside constrained environments, in CBOR. This specification defines a common format for this.

Authors

Kepeng Li (kepeng.lkp@alibaba-inc.com)
Akbar Rahman (Akbar.Rahman@InterDigital.com)
Carsten Bormann (cabo@tzi.org)

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