Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol Reception Statistics and Other Feedback
RFC 8861, “Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol Reception Statistics and Other Feedback”, is a Proposed Standard document published in January 2021 by J. Lennox, M. Westerlund, Q. Wu, C. Perkins. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8861 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8860 Sending Multiple Types of Media in a Single RTP Session
- RFC 8862 Best Practices for Securing RTP Media Signaled with SIP
- RFC 8859 A Framework for Session Description Protocol Attributes When Multiplexing
- RFC 8863 Interactive Connectivity Establishment Patiently Awaiting Connectivity
- RFC 8858 Indicating Exclusive Support of RTP and RTP Control Protocol Multiplexing Using the Session Description Protocol
- RFC 8864 Negotiation Data Channels Using the Session Description Protocol
- RFC 8857 The WebSocket Protocol as a Transport for the Binary Floor Control Protocol
- RFC 8865 T.140 Real-Time Text Conversation over WebRTC Data Channels