CoAP Implementation Guidance
draft-ietf-lwig-coap-05
| Document | Type | Expired Internet-Draft (lwig WG) | |
|---|---|---|---|
| Last updated | 2018-05-03 (latest revision 2017-10-30) | ||
| Replaces | draft-kovatsch-lwig-coap | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-lwig-coap-05.txt
Abstract
The Constrained Application Protocol (CoAP) is designed for resource- constrained nodes and networks such as sensor nodes in a low-power lossy network (LLN). Yet to implement this Internet protocol on Class 1 devices (as per RFC 7228, ~ 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. In particular, it provides guidance on correct implementation of the CoAP specification RFC 7252, memory optimizations, and customized protocol parameters.
Authors
Matthias Kovatsch
(kovatsch@inf.ethz.ch)
Olaf Bergmann
(bergmann@tzi.org)
Carsten Bormann
(cabo@tzi.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)