Skip to main content

Representing Constrained RESTful Environments (CoRE) Link Format in JSON and CBOR

Document Type Expired Internet-Draft (core WG)
Expired & archived
Authors Kepeng Li , Akbar Rahman , Carsten Bormann
Last updated 2018-10-13 (Latest revision 2018-02-26)
Replaces draft-bormann-core-links-json, draft-li-core-cbor-equivalents
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Jaime Jimenez
Shepherd write-up Show Last changed 2017-04-02
IESG IESG state Expired (IESG: Dead)
Action Holders
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Alexey Melnikov
Send notices to "Jaime Jimenez" <>
IANA IANA review state Version Changed - Review Needed

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


JavaScript Object Notation, JSON (RFC 8259) 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 (RFC 8288) 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 (RFC 6690). 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.


Kepeng Li
Akbar Rahman
Carsten Bormann

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