Constrained Application Protocol (CoAP)
draft-shelby-core-coap-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zach Shelby , Brian Frank , Don Sturek | ||
| Last updated | 2010-08-24 (Latest revision 2010-05-10) | ||
| Replaces | draft-shelby-6lowapp-coap | ||
| Replaced by | RFC 7252 | ||
| 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-ietf-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 specifies the Constrained Application Protocol (CoAP), a specialized transfer protocol for use with constrained networks and nodes for machine-to-machine applications such as smart energy and building automation. These constrained nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while networks such as 6LoWPAN often have high packet error rates and typical throughput of 10s of kbps. CoAP provides request/reply and subscribe/notify interaction models between appliciation end-points, supports built-in resource discovery, and includes key web concepts such as URIs and RESTful methods. CoAP easily translates to HTTP for integration with the web while meeting specialized requirements such as multicast support, very low overhead and simplicity for constrained environments.
Authors
Zach Shelby
Brian Frank
Don Sturek
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)