CoAP Alive Message
draft-castellani-core-alive-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Angelo P. Castellani , Salvatore Loreto | ||
| Last updated | 2012-09-30 (Latest revision 2012-03-29) | ||
| 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
In the context of a Constrained RESTful Environment (CoRE), hosts could frequently be energy-constrained and be turned off the vast majority of time for energy-saving purposes. In the case of a CoAP server, while it is offline, it is neither available to serve requests. Clients desiring to access its resources have no way to understand when they will find it up again. This specification provides a simple new message that gives to a CoAP server the ability to signal its current availability in the network.
Authors
Angelo P. Castellani
Salvatore Loreto
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)