Allways-online Requirement for Sleeping CoAP Node
draft-cao-core-aol-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Zehn Cao | ||
| Last updated | 2011-07-04 | ||
| 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
CoAP is to enable a concept of web of sensors, but there are many cases that the sensors are not always online and hence the requests from the web client cannot reach them in timely manner. This document analyzes this problem and describes the requirements for a CoAP enabled sensor to behave always online.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)