Skip to main content

LEDBAT architecture framework consisting of pluggable components
draft-mayutan-ledbat-congestionarchitecture-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Mayutan Arumaithurai , Dr. K. K. Ramakrishnan , Xiaoming Fu
Last updated 2010-03-01
RFC stream (None)
Intended RFC status (None)
Formats
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:

Abstract

The Low Extra Delay Background Transport (LEDBAT) working group is considering protocols for an alternative congestion control protocol that enables a delay-insensitive networking application to minimize the extra queueing delay it causes to other applications because of additional queueing at the bottleneck, when these connections carrying traffic for such applications attempt to use the available bandwidth. This document proposes an architectural framework for LEDBAT congestion control mechanisms, based on existing work on congestion control protocols and the requirements of the LEDBAT working group. The architectural framework consists of a LEDBAT-congestion control (LEDBAT-CC) suite that provides flexibility in utilizing different components for providing congestion control for transport connections carrying delay-insensitive traffic. The LEDBAT-CC suite of protocols is envisioned to support the multiple alternative mechanisms for bandwidth estimation, congestion detection and indication and end- system flow control to comprise a network friendly congestion avoidance protocol. This document is inspired by the need to standardize the various components that constitute the network friendly congestion control protocol to avoid having to individually standardize a multitude of distinct and monolithic solutions.

Authors

Mayutan Arumaithurai
Dr. K. K. Ramakrishnan
Xiaoming Fu

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