Using Simulcast in SDP and RTP Sessions

Document Type Replaced Internet-Draft (individual)
Authors Magnus Westerlund  , Bo Burman  , Suhas Nandakumar  , Mo Zanaty 
Last updated 2014-10-27
Replaced by RFC 8853
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mmusic-sdp-simulcast
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In some application scenarios it may be desirable to send multiple differently encoded versions of the same media source in independent RTP streams. This is called simulcast. This document discusses the best way of accomplishing simulcast in RTP and how to signal it in SDP. A solution is defined by making an extension to SDP, and using RTP/RTCP identification methods to relate RTP streams belonging to the same media source. The SDP extension consists a new media level SDP attribute that express capability to send and/or receive simulcast RTP streams. One part of the RTP/RTCP identification method is included as a reference to a separate document, since it is useful also for other purposes.


Magnus Westerlund (
Bo Burman (
Suhas Nandakumar (
Mo Zanaty (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)