RFC 6464: A Real-time Transport Protocol (RTP) Header Extension for Client-to-Mixer Audio Level Indication
In plain English — editorial summary, not part of the RFC
This document defines a mechanism by which packets of Real-time Transport Protocol (RTP) audio streams can indicate, in an RTP header extension, the audio level of the audio sample carried in the RTP packet. In large conferences, this can reduce the load on an audio mixer or other middlebox that wants to forward only a few of the loudest audio streams, without requiring it to decode and measure every stream that is received. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6464
- Published
- December 2011
- Authors
- J. Lennox; E. Ivov; E. Marocco
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6465A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level IndicationCurrent
December 2011
- RFC 9071RTP-Mixer Formatting of Multiparty Real-Time TextCurrent
July 2021
- RFC 7104Duplication Grouping Semantics in the Session Description ProtocolCurrent
January 2014
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 8855The Binary Floor Control Protocol (BFCP)Current
January 2021
- RFC 5692Transmission of IP over Ethernet over IEEE 802.16 NetworksCurrent
October 2009
- RFC 4582The Binary Floor Control Protocol (BFCP)Obsoleted
November 2006
- RFC 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
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?