Resource Model Indication with CoAP
draft-jinchoe-resource-model-indication-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | JinHyeock Choi , Gabor Bajko , Darshak Thakore | ||
| Last updated | 2016-01-07 (Latest revision 2015-07-06) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
There is much interest in "Internet of Things (IoT)" and multiple standards following the REST architectural style are under development. In a RESTful interaction, IoT devices need to understand each other's resource representations, both the semantic meaning and the syntactic form, to interact properly. For interoperability among different standards, it is helpful for CoAP endpoints to indicate the resource models they support. This document presents a scheme for IoT devices to exchange their resource model information and requests from IANA new Internet media types and CoAP Content-Format identifier for resource model indication.
Authors
JinHyeock Choi
Gabor Bajko
Darshak Thakore
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)