RFC 4585: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)
In plain English — editorial summary, not part of the RFC
Real-time media streams that use RTP are, to some degree, resilient against packet losses. Receivers may use the base mechanisms of the Real-time Transport Control Protocol (RTCP) to report packet reception statistics and thus allow a sender to adapt its transmission behavior in the mid-term. This is the sole means for feedback and feedback-based error repair (besides a few codec-specific mechanisms). This document defines an extension to the Audio-visual Profile (AVP) that enables receivers to provide, statistically, more immediate feedback to the senders and thus allows for short-term adaptation and efficient feedback-based repair mechanisms to be implemented. This early feedback profile (AVPF) maintains the AVP bandwidth constraints for RTCP and preserves scalability to large groups. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4585
- Published
- July 2006
- Authors
- J. Ott; S. Wenger; N. Sato; C. Burmeister; J. Rey
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 51
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5484Associating Time-Codes with RTP StreamsCurrent
March 2009
- RFC 4574The Session Description Protocol (SDP) Label AttributeCurrent
August 2006
- RFC 5432Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)Current
March 2009
- RFC 4587RTP Payload Format for H.261 Video StreamsCurrent
August 2006
- RFC 4588RTP Retransmission Payload FormatCurrent
July 2006
- RFC 4582The Binary Floor Control Protocol (BFCP)Obsoleted
November 2006
- RFC 4589Location Types RegistryCurrent
July 2006
- RFC 4579Session Initiation Protocol (SIP) Call Control - Conferencing for User AgentsCurrent
August 2006
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?