Congestion Control Requirements For RMCAT

Document Type Replaced Internet-Draft (rmcat WG)
Author Randell Jesup 
Last updated 2013-07-22 (latest revision 2013-02-25)
Replaced by RFC 8836
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Adopted by a WG
Revised I-D Needed - Issue raised by WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-rmcat-cc-requirements
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


Congestion control is needed for all data transported across the Internet, in order to promote fair usage and prevent congestion collapse. The requirements for interactive, point-to-point real time multimedia, which needs by low-delay, semi-reliable data delivery, are different from the requirements for bulk transfer like FTP or bursty transfers like Web pages, and the TCP algorithms are not suitable for this traffic. This document attempts to describe a set of requirements that can be used to evaluate other congestion control mechanisms in order to figure out their fitness for this purpose, and in particular to provide a set of possible requirements for proposals coming out of the RMCAT Working Group. This document is derived from draft-jesup-rtp-congestion-reqs [I-D.jesup-rtp-congestion-reqs].


Randell Jesup (

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