Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 3550

Authors:

C. Perkins
V. Singh

Stream:

IETF

Source:

avtcore (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8083

Discuss this RFC: Send questions or comments to the mailing listavt@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8083

Abstract

The Real-time Transport Protocol (RTP) is widely used in telephony,video conferencing, and telepresence applications. Such applicationsare often run on best-effort UDP/IP networks. If congestion controlis not implemented in these applications, then network congestion canlead to uncontrolled packet loss and a resulting deterioration of theuser's multimedia experience. The congestion control algorithm actsas a safety measure by stopping RTP flows from using excessiveresources and protecting the network from overload. At the time ofthis writing, however, while there are several proprietary solutions,there is no standard algorithm for congestion control of interactiveRTP flows.

This document does not propose a congestion control algorithm. Itinstead defines a minimal set of RTP circuit breakers: conditionsunder which an RTP sender needs to stop transmitting media data toprotect the network from excessive congestion. It is expected that,in the absence of long-lived excessive congestion, RTP applicationsrunning on best-effort IP networks will be able to operate withouttriggering these circuit breakers. To avoid triggering the RTPcircuit breaker, any Standards Track congestion control algorithmsdefined for RTP will need to operate within the envelope set by theseRTP circuit breaker algorithms.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.