Reusable Interface Definitions for Constrained RESTful Environments

The information below is for an old version of the document
Document Type Expired Internet-Draft (core WG)
Last updated 2016-04-21 (latest revision 2015-10-19)
Replaces draft-shelby-core-interfaces
Stream IETF
Intended RFC status Informational
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Dec 2099 - CoRE Interfaces subm... )
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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


This document defines a set of reusable REST resource design patterns suitable for use in constrained environments, based on IETF CoRE standards for information representation and information exchange. Interface types for Sensors, Actuators, Parameters, and resource Collections are defined using the "if" link attribute defined by CoRE Link Format [RFC6690]. Clients may use the "if" attribute to determine how to consume resources. Dynamic linking of state updates between resources, either on an endpoint or between endpoints, is defined with the concept of Link Bindings. We also define conditional observation attributes that work with Link Bindings or with simple CoAP Observe [RFC7641].


Zach Shelby (
Matthieu Vial (
Michael Koster (

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