Sending Multiple Types of Media in a Single RTP Session
RFC 8860, “Sending Multiple Types of Media in a Single RTP Session”, is a Proposed Standard document published in January 2021 by M. Westerlund, C. Perkins, J. Lennox. It updates RFC 3550, RFC 3551. The canonical text is published by the RFC Editor.
Abstract
This document specifies how an RTP session can contain RTP streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP specifications (RFCs 3550 and 3551), and thus this document updates RFCs 3550 and 3551 to enable this behaviour for applications that satisfy the applicability for using multiple media types in a single RTP session.
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 8860 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8859 A Framework for Session Description Protocol Attributes When Multiplexing
- RFC 8861 Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol Reception Statistics and Other Feedback
- RFC 8858 Indicating Exclusive Support of RTP and RTP Control Protocol Multiplexing Using the Session Description Protocol
- RFC 8862 Best Practices for Securing RTP Media Signaled with SIP
- RFC 8857 The WebSocket Protocol as a Transport for the Binary Floor Control Protocol
- RFC 8863 Interactive Connectivity Establishment Patiently Awaiting Connectivity
- RFC 8856 Session Description Protocol Format for Binary Floor Control Protocol Streams
- RFC 8864 Negotiation Data Channels Using the Session Description Protocol