RFC 8083: Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
In plain English — editorial summary, not part of the RFC
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 these applications, then network congestion can lead to uncontrolled packet loss and a resulting deterioration of the user's multimedia experience. The congestion control algorithm acts as a safety measure by stopping RTP flows from using excessive resources and protecting the network from overload. At the time of this writing, however, while there are several proprietary solutions, there is no standard algorithm for congestion control of interactive RTP flows. This document does not propose a congestion control algorithm. It instead defines a minimal set of RTP circuit breakers: conditions under which an RTP sender needs to stop transmitting media data to protect the network from excessive congestion. It is expected that, in the absence of long-lived excessive congestion, RTP applications running on best-effort IP networks will be able to operate without triggering these circuit breakers. To avoid triggering the RTP circuit breaker, any Standards Track congestion control algorithms defined for RTP will need to operate within the envelope set by these RTP circuit breaker algorithms.
Document record
- Document ID
- RFC8083
- Published
- March 2017
- Authors
- C. Perkins; V. Singh
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 25
- Also known as
- —
- Updates:
- RFC 3550
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 8085UDP Usage GuidelinesUpdated
March 2017
- RFC 8086GRE-in-UDP EncapsulationCurrent
March 2017
- RFC 8075Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)Current
February 2017
- RFC 8095Services Provided by IETF Transport Protocols and Congestion Control MechanismsCurrent
March 2017
- RFC 8100Diffserv-Interconnection Classes and PracticeCurrent
March 2017
- RFC 8108Sending Multiple RTP Streams in a Single RTP SessionCurrent
March 2017
- RFC 8035Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP MultiplexingCurrent
November 2016
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?