RFC 5760: RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the Real-time Transport Control Protocol (RTCP) to use unicast feedback to a multicast sender. The proposed extension is useful for single-source multicast sessions such as Source-Specific Multicast (SSM) communication where the traditional model of many-to-many group communication is either not available or not desired. In addition, it can be applied to any group that might benefit from a sender-controlled summarized reporting mechanism. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5760
- Published
- February 2010
- Authors
- J. Ott; J. Chesterfield; E. Schooler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 66
- Also known as
- —
- Updated by:
- RFC 6128
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 5968Guidelines for Extending the RTP Control Protocol (RTCP)Current
September 2010
- RFC 5993RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)Current
October 2010
- RFC 6051Rapid Synchronisation of RTP FlowsCurrent
November 2010
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5391RTP Payload Format for ITU-T Recommendation G.711.1Current
November 2008
- RFC 5372Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header RecoveryCurrent
October 2008
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
- RFC 5285A General Mechanism for RTP Header ExtensionsObsoleted
July 2008
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?