RFC 8888: RTP Control Protocol (RTCP) Feedback for Congestion Control
In plain English — editorial summary, not part of the RFC
An effective RTP congestion control algorithm requires more fine-grained feedback on packet loss, timing, and Explicit Congestion Notification (ECN) marks than is provided by the standard RTP Control Protocol (RTCP) Sender Report (SR) and Receiver Report (RR) packets. This document describes an RTCP feedback message intended to enable congestion control for interactive real-time traffic using RTP. The feedback message is designed for use with a sender-based congestion control algorithm, in which the receiver of an RTP flow sends back to the sender RTCP feedback packets containing the information the sender needs to perform congestion control.
Document record
- Document ID
- RFC8888
- Published
- January 2021
- Authors
- Z. Sarker; C. Perkins; V. Singh; M. Ramalho
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8868Evaluating Congestion Control for Interactive Real-Time MediaCurrent
January 2021
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 8035Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP MultiplexingCurrent
November 2016
- RFC 6679Explicit Congestion Notification (ECN) for RTP over UDPUpdated
August 2012
- RFC 8869Evaluation Test Cases for Interactive Real-Time Media over Wireless NetworksCurrent
January 2021
- RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
- RFC 9392Sending RTP Control Protocol (RTCP) Feedback for Congestion Control in Interactive Multimedia ConferencesCurrent
April 2023
- RFC 8298Self-Clocked Rate Adaptation for MultimediaCurrent
December 2017
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?