RFC 6817: Low Extra Delay Background Transport (LEDBAT)
In plain English — editorial summary, not part of the RFC
Low Extra Delay Background Transport (LEDBAT) is an experimental delay-based congestion control algorithm that seeks to utilize the available bandwidth on an end-to-end path while limiting the consequent increase in queueing delay on that path. LEDBAT uses changes in one-way delay measurements to limit congestion that the flow itself induces in the network. LEDBAT is designed for use by background bulk-transfer applications to be no more aggressive than standard TCP congestion control (as specified in RFC 5681) and to yield in the presence of competing flows, thus limiting interference with the network performance of competing flows. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6817
- Published
- December 2012
- Authors
- S. Shalunov; G. Hazel; J. Iyengar; M. Kuehlewind
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 6972Problem Statement and Requirements of the Peer-to-Peer Streaming Protocol (PPSP)Current
July 2013
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 6646DECoupled Application Data Enroute (DECADE) Problem StatementCurrent
July 2012
- RFC 6392A Survey of In-Network Storage SystemsCurrent
October 2011
- RFC 6356Coupled Congestion Control for Multipath Transport ProtocolsCurrent
October 2011
- RFC 6297A Survey of Lower-than-Best-Effort Transport ProtocolsCurrent
June 2011
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?