Skip to main content

Congestion Control Principles for CoAP

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Carsten Bormann , Klaus Hartke
Last updated 2013-02-01 (Latest revision 2012-07-31)
RFC stream (None)
Intended RFC status (None)
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:


The CoAP protocol needs to be implemented in such a way that it does not cause persistent congestion on the network it uses. Congestion control is a complex issue -- the proper rationale for the congestion control mechanisms chosen in CoAP is probably more material than the CoAP protocol specification itself. This informational document attempts to pull out the background material and more extensive considerations behind the CoAP congestion control mechanisms, while leaving the basic MUSTs and MUST NOTs in the main spec.


Carsten Bormann
Klaus Hartke

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