Indicating Exclusive Support of RTP and RTP Control Protocol Multiplexing Using the Session Description Protocol
RFC 8858, “Indicating Exclusive Support of RTP and RTP Control Protocol Multiplexing Using the Session Description Protocol”, is a Proposed Standard document published in January 2021 by C. Holmberg. It updates RFC 5761. The canonical text is published by the RFC Editor.
Abstract
This document defines a new Session Description Protocol (SDP) media-level attribute, 'rtcp-mux-only', that can be used by an endpoint to indicate exclusive support of RTP and RTP Control Protocol (RTCP) multiplexing. The document also updates RFC 5761 by clarifying that an offerer can use a mechanism to indicate that it is not able to send and receive RTCP on separate ports.
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 8858 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8857 The WebSocket Protocol as a Transport for the Binary Floor Control Protocol
- RFC 8859 A Framework for Session Description Protocol Attributes When Multiplexing
- RFC 8856 Session Description Protocol Format for Binary Floor Control Protocol Streams
- RFC 8860 Sending Multiple Types of Media in a Single RTP Session
- RFC 8855 The Binary Floor Control Protocol
- RFC 8861 Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol Reception Statistics and Other Feedback
- RFC 8854 WebRTC Forward Error Correction Requirements
- RFC 8862 Best Practices for Securing RTP Media Signaled with SIP