RFC 8861: Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other Feedback
In plain English — editorial summary, not part of the RFC
RTP allows multiple RTP streams to be sent in a single session but requires each Synchronization Source (SSRC) to send RTP Control Protocol (RTCP) reception quality reports for every other SSRC visible in the session. This causes the number of RTCP reception reports to grow with the number of SSRCs, rather than the number of endpoints. In many cases, most of these RTCP reception reports are unnecessary, since all SSRCs of an endpoint are normally co-located and see the same reception quality. This memo defines a Reporting Group extension to RTCP to reduce the reporting overhead in such scenarios.
Document record
- Document ID
- RFC8861
- Published
- January 2021
- Authors
- J. Lennox; M. Westerlund; Q. Wu; C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9134RTP Payload Format for ISO/IEC 21122 (JPEG XS)Current
October 2021
- RFC 8697Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)Updated
January 2020
- RFC 7643System for Cross-domain Identity Management: Core SchemaUpdated
September 2015
- RFC 6990RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG-2 Transport Stream (TS) Program Specific Information (PSI) Independent Decodability Statistics Metrics ReportingCurrent
August 2013
- RFC 6692Source Ports in Abuse Reporting Format (ARF) ReportsCurrent
July 2012
- RFC 3611RTP Control Protocol Extended Reports (RTCP XR)Current
November 2003
- RFC 3177IAB/IESG Recommendations on IPv6 Address Allocations to SitesObsoleted
September 2001
- RFC 2727IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
February 2000
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?