Using Simulcast in RTP sessions
draft-westerlund-avtcore-rtp-simulcast-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Magnus Westerlund , Bo Burman , Morgan Lindqvist , Fredrik Jansson | ||
Last updated | 2012-04-26 (Latest revision 2011-10-24) | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In some applications it may be necessary to send multiple media streams derived from the same media source. This is called Simulcast. This document discusses the best way of accomplishing this in RTP. It is concluded that a session based solution provides best support for simulcast, and a solution for that is defined. There are two necessary extensions. The first extension is how to group RTP sessions belonging to the same simulcast source using the grouping framework, and the second is how to identify which SSRCs that are the same media source by using a new RTCP SDES item SRCNAME.
Authors
Magnus Westerlund
Bo Burman
Morgan Lindqvist
Fredrik Jansson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)