RTP Congestion Control: Circuit Breakers for Unicast Sessions
draft-perkins-avtcore-rtp-circuit-breakers-01
Document | Type |
Replaced Internet-Draft
(candidate for avtcore WG)
Expired & archived
|
|
---|---|---|---|
Authors | Colin Perkins , Varun Singh | ||
Last updated | 2012-10-12 (Latest revision 2012-07-16) | ||
Replaced by | draft-ietf-avtcore-rtp-circuit-breakers | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | Magnus Westerlund | ||
IESG | IESG state | Replaced by draft-ietf-avtcore-rtp-circuit-breakers | |
Consensus boilerplate | Unknown | ||
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:
Abstract
The Real-time Transport Protocol (RTP) is widely used in telephony, video conferencing, and telepresence applications. Such applications are often run on best-effort UDP/IP networks. If congestion control is not implemented in the applications, then network congestion will deteriorate the user's multimedia experience. This document does not propose a congestion control algorithm; rather, it defines a minimal set of "circuit-breakers". Circuit-breakers are conditions under which an RTP flow is expected to stop transmiting media to protect the network from excessive congestion. It is expected that all RTP applications running on best-effort networks will be able to run without triggering these circuit breakers in normal operation. Any future RTP congestion control specification is expected to operate within the envelope defined by these circuit breakers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)