CoAP Implementation Guidance

The information below is for an old version of the document
Document Type Expired Internet-Draft (lwig WG)
Authors Matthias Kovatsch  , Olaf Bergmann  , Esko Dijk  , Xuan He  , Carsten Bormann 
Last updated 2015-01-05 (latest revision 2014-07-04)
Replaces draft-kovatsch-lwig-coap
Stream Internet Engineering Task Force (IETF)
Expired & archived
pdf htmlized 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 (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.


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.)