RFC 8382: Shared Bottleneck Detection for Coupled Congestion Control for RTP Media
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to detect whether end-to-end data flows share a common bottleneck. This mechanism relies on summary statistics that are calculated based on continuous measurements and used as input to a grouping algorithm that runs wherever the knowledge is needed.
Document record
- Document ID
- RFC8382
- Published
- June 2018
- Authors
- D. Hayes; S. Ferlin; M. Welzl; K. Hiorth
- 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 9625EVPN Optimized Inter-Subnet Multicast (OISM) ForwardingCurrent
August 2024
- RFC 8298Self-Clocked Rate Adaptation for MultimediaCurrent
December 2017
- RFC 8290The Flow Queue CoDel Packet Scheduler and Active Queue Management AlgorithmCurrent
January 2018
- RFC 8289Controlled Delay Active Queue ManagementCurrent
January 2018
- RFC 8489Session Traversal Utilities for NAT (STUN)Current
February 2020
- RFC 8547TCP-ENO: Encryption Negotiation OptionCurrent
May 2019
- RFC 8548Cryptographic Protection of TCP Streams (tcpcrypt)Current
May 2019
- RFC 8593Video Traffic Models for RTP Congestion Control EvaluationsCurrent
May 2019
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?