RFC 8699: Coupled Congestion Control for RTP Media
In plain English — editorial summary, not part of the RFC
When multiple congestion-controlled Real-time Transport Protocol (RTP) sessions traverse the same network bottleneck, combining their controls can improve the total on-the-wire behavior in terms of delay, loss, and fairness. This document describes such a method for flows that have the same sender, in a way that is as flexible and simple as possible while minimizing the number of changes needed to existing RTP applications. This document also specifies how to apply the method for the Network-Assisted Dynamic Adaptation (NADA) congestion control algorithm and provides suggestions on how to apply it to other congestion control algorithms.
Document record
- Document ID
- RFC8699
- Published
- January 2020
- Authors
- S. Islam; M. Welzl; S. Gjessing
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8684TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 2020
- RFC 8548Cryptographic Protection of TCP Streams (tcpcrypt)Current
May 2019
- RFC 8547TCP-ENO: Encryption Negotiation OptionCurrent
May 2019
- RFC 8087The Benefits of Using Explicit Congestion Notification (ECN)Current
March 2017
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 6356Coupled Congestion Control for Multipath Transport ProtocolsCurrent
October 2011
- RFC 4850Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node ArchitectureObsoleted
April 2007
- RFC 4173Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) ProtocolUpdated
September 2005
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?