CurrentPROPOSED STANDARDIETF stream

RFC 8853: Using Simulcast in Session Description Protocol (SDP) and RTP Sessions

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8853
Published
January 2021
Authors
B. Burman; M. Westerlund; S. Nandakumar; M. Zanaty
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
30
Also known as

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8853-using-simulcast-in-session-description-protocol-sdp-and-rtp-sessions