RFC 6679: Explicit Congestion Notification (ECN) for RTP over UDP
In plain English — editorial summary, not part of the RFC
This memo specifies how Explicit Congestion Notification (ECN) can be used with the Real-time Transport Protocol (RTP) running over UDP, using the RTP Control Protocol (RTCP) as a feedback mechanism. It defines a new RTCP Extended Report (XR) block for periodic ECN feedback, a new RTCP transport feedback message for timely reporting of congestion events, and a Session Traversal Utilities for NAT (STUN) extension used in the optional initialisation method using Interactive Connectivity Establishment (ICE). Signalling and procedures for negotiation of capabilities and initialisation methods are also defined. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6679
- Published
- August 2012
- Authors
- M. Westerlund; I. Johansson; C. Perkins; P. O'Hanlon; K. Carlberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 58
- Also known as
- —
- Updated by:
- RFC 8311
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 9392Sending RTP Control Protocol (RTCP) Feedback for Congestion Control in Interactive Multimedia ConferencesCurrent
April 2023
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 8257Data Center TCP (DCTCP): TCP Congestion Control for Data CentersCurrent
October 2017
- RFC 8888RTP Control Protocol (RTCP) Feedback for Congestion ControlCurrent
January 2021
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
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?