Publish Option for CoAP
draft-fossati-core-publish-option-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Thomas Fossati , Pierpaolo Giacomin, Salvatore Loreto | ||
| Last updated | 2013-01-10 (Latest revision 2012-07-09) | ||
| RFC stream | (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
This memo defines the Publish Option for the Constrained Application Protocol (CoAP). The Publish Option is used by a sleepy node to temporarily delegate the authority of one of its resources to another, always on, node which is typically a proxy but doesn't need to be necessarily. The sleepy node is given a simple RESTful messaging protocol that enables the setup, renew and removal of the authority transfer. The whole process is driven by the (sleepy) origin, which may actually never need to listen or to keep any state.
Authors
Thomas Fossati
Pierpaolo Giacomin
Salvatore Loreto
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)