Congestion Control Principles for CoAP
draft-bormann-core-congestion-control-02

 
Document
Type Expired Internet-Draft (individual)
Last updated 2013-02-01 (latest revision 2012-07-31)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

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-bormann-core-congestion-control-02.txt

Abstract

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.

Authors

Carsten Bormann (cabo@tzi.org)
Klaus Hartke (hartke@tzi.org)

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