Skip to main content

Representing Constrained RESTful Environments (CoRE) Link Format in JSON and CBOR
draft-ietf-core-links-json-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, jaime.jimenez@ericsson.com, core-chairs@ietf.org, Jaime Jimenez <jaime.jimenez@ericsson.com>, draft-ietf-core-links-json@ietf.org, core@ietf.org, alexey.melnikov@isode.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Representing CoRE Formats in JSON and CBOR' to Proposed Standard (draft-ietf-core-links-json-07.txt)

The IESG has approved the following document:
- 'Representing CoRE Formats in JSON and CBOR'
  (draft-ietf-core-links-json-07.txt) as Proposed Standard

This document is the product of the Constrained RESTful Environments
Working Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben
Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-links-json/


Ballot Text

Technical Summary

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.

Working Group Summary

The document has gone through multiple expert reviews and has been discussed on multiple IETF meetings.

Document Quality

   An example implementation is in Appendix A.
   Media Type Review was requested on March 15th 2017.

Personnel

Document Shepherd: Jaime Jiménez, <jaime.jimenez@ericsson.com>
Area Director: Alexey Melnikov.

RFC Editor Note