RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 13
- Abstract
- 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]
- Publication Date
- 2012-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC6642- Link
- https://doi.org/10.17487/RFC6642
- Author(s)
- Qin WuFrank XiaRoni Even
- Keyword(s)
- Feedback Suppression, NACK, Retransmission
Latest version of IETF RFC 6642
Document Versions — IETF RFC 6642
-
▶ IETF RFC 6642 (2012-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3711 [Active*]
- IETF RFC 4566 [Superseded*]
- IETF RFC 4585 [Active*]
- IETF RFC 4588 [Active*]
- IETF RFC 5104 [Active*]
- IETF RFC 5124 [Active*]
- IETF RFC 5234 [Active, Amended*]
Bibliographic Reference(s)
- Van Caenegem, T., Ver Steeg, B., and A. Begen, "Retransmission for Source-Specific Multicast (SSM) Sessions", Work in Progress, May 2011. EXTERNAL
- Wu, Q., Hunt, G., and P. Arden, "Monitoring Architectures for RTP", Work in Progress, May 2012. EXTERNAL
- IETF RFC 4587 [Active*]
- IETF RFC 5117 [Superseded*]
- IETF RFC 5760 [Active*]
- IETF RFC 6285 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6642.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6642, RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report. Available at https://doi.org/10.17487/RFC6642
Snippet:
IETF RFC 6642, RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report. Available at https://doi.org/10.17487/RFC6642
HTML (ISO 690 compliant)
Preview:
IETF RFC 6642, RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report. Available at https://doi.org/10.17487/RFC6642
Snippet:
<span class="citation"><cite>IETF RFC 6642</cite>, RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report. Available at <a href="https://doi.org/10.17487/RFC6642" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6642</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6642, RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report
doi: 10.17487/RFC6642
url: https://doi.org/10.17487/RFC6642
doi: 10.17487/RFC6642
url: https://doi.org/10.17487/RFC6642
Snippet:
<li> <cite id="bib-rfc6642">IETF RFC 6642</cite>, RTP Control Protocol (RTCP) Extension for a Third-Party Loss Report <span class="doi">10.17487/RFC6642</span> </li>
Referenced By
- IETF RFC 8859 [Active*]