RFC 6642

RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report, June 2012

Canonical URL:
File formats:
Plain TextPDF
Q. Wu, Ed.
F. Xia
R. Even
avtcore (rai)

Cite this RFC: TXT  |  XML

DOI:  http://dx.doi.org/10.17487/RFC6642

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


In a large RTP session using the RTP Control Protocol (RTCP) feedback mechanism defined in RFC 4585, a feedback target may experience transient overload if some event causes a large number of receivers to send feedback at once. This overload is usually avoided by ensuring that feedback reports are forwarded to all receivers, allowing them to avoid sending duplicate feedback reports. However, there are cases where it is not recommended to forward feedback reports, and this may allow feedback implosion. This memo discusses these cases and defines a new RTCP Third-Party Loss Report that can be used to inform receivers that the feedback target is aware of some loss event, allowing them to suppress feedback. Associated Session Description Protocol (SDP) signaling is also defined. [STANDARDS-TRACK]

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.

Download PDF Reader

Search RFCs
Advanced Search