CoAP Implementation Guidance
draft-kovatsch-lwig-coap-03

Document Type Replaced Internet-Draft (individual)
Last updated 2014-07-03 (latest revision 2014-03-03)
Replaced by draft-ietf-lwig-coap
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-lwig-coap
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kovatsch-lwig-coap-03.txt

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. In particular, it provides guidance on correct implementation of the CoAP specification [I-D.ietf-core-coap], memory optimizations, and customized protocol parameters.

Authors

Matthias Kovatsch (kovatsch@inf.ethz.ch)
Olaf Bergmann (bergmann@tzi.org)
Esko Dijk (esko.dijk@philips.com)
Xuan He (xhe@hitachi.cn)
Carsten Bormann (cabo@tzi.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)