RFC 8853

Using Simulcast in Session Description Protocol (SDP) and RTP Sessions, January 2021

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
PROPOSED STANDARD
Authors:
B. Burman
M. Westerlund
S. Nandakumar
M. Zanaty
Stream:
IETF
Source:
mmusic (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8853

Discuss this RFC: Send questions or comments to the mailing list mmusic@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8853


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search