CoAP Implementation Guidance
draft-kovatsch-lwig-coap-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Matthias Kovatsch , Olaf Bergmann , Esko Dijk , Xuan He , Carsten Bormann | ||
| Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
| Replaced by | draft-ietf-lwig-coap | ||
| 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
The Constrained Application Protocol (CoAP) is designed for resource- constrained nodes and networks, e.g., sensor nodes in a low-power lossy network (LLN). Yet to implement this Internet protocol on Class 1 devices (i.e., ~ 10 KiB of RAM and ~ 100 KiB of ROM) also lightweight implementation techniques are necessary. This document provides lessons learned from implementing CoAP for tiny, battery- operated networked embedded systems. The guidelines for transmission state management and developer APIs can also help with the implementation of CoAP for less constrained nodes.
Authors
Matthias Kovatsch
Olaf Bergmann
Esko Dijk
Xuan He
Carsten Bormann
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)