CoAP Implementation Guidance
draft-ietf-lwig-coap-06
| Document | Type | Expired Internet-Draft (lwig WG) | |
|---|---|---|---|
| Authors | Matthias Kovatsch , Olaf Bergmann , Carsten Bormann | ||
| Last updated | 2019-01-03 (Latest revision 2018-07-02) | ||
| Replaces | draft-kovatsch-lwig-coap | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-lwig-coap-06.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
Olaf Bergmann
Carsten Bormann
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)