CoAP Feature Analysis
draft-shelby-6lowapp-coap-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zach Shelby , Michael Stuber , Don Sturek , Brian Frank , Richard Kelsey | ||
| Last updated | 2009-12-23 | ||
| Replaced by | draft-shelby-core-coap | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-shelby-core-coap | |
| 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 document considers the requirements and resulting features needed for the design of the Constrained Application Protocol (CoAP). Starting from requirements for energy and building automation applications, the basic features are identified along with an analysis of possible realizations. The goal of the document is to provide a basis for protocol design and related discussion.
Authors
Zach Shelby
Michael Stuber
Don Sturek
Brian Frank
Richard Kelsey
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)