Using Simulcast in Session Description Protocol and RTP Sessions
RFC 8853, “Using Simulcast in Session Description Protocol and RTP Sessions”, is a Proposed Standard document published in January 2021 by B. Burman, M. Westerlund, S. Nandakumar, M. Zanaty. The canonical text is published by the RFC Editor.
Abstract
In some application scenarios, it may be desirable to send multiple differently encoded versions of the same media source in different RTP streams. This is called simulcast. This document describes how to accomplish simulcast in RTP and how to signal it in the Session Description Protocol (SDP). The described solution uses an RTP/RTCP identification method to identify RTP streams belonging to the same media source and makes an extension to SDP to indicate that those RTP streams are different simulcast formats of that media source. The SDP extension consists of a new media-level SDP attribute that expresses capability to send and/or receive simulcast RTP streams.
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 8853 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8852 RTP Stream Identifier Source Description
- RFC 8854 WebRTC Forward Error Correction Requirements
- RFC 8851 RTP Payload Format Restrictions
- RFC 8855 The Binary Floor Control Protocol
- RFC 8850 Controlling Multiple Streams for Telepresence Protocol Data Channel
- RFC 8856 Session Description Protocol Format for Binary Floor Control Protocol Streams
- RFC 8849 Mapping RTP Streams to Controlling Multiple Streams for Telepresence Media Captures
- RFC 8857 The WebSocket Protocol as a Transport for the Binary Floor Control Protocol