Using Simulcast in RTP Sessions
draft-westerlund-avtcore-rtp-simulcast-04

 
Document Type Expired Internet-Draft (individual)
Last updated 2015-01-05 (latest revision 2014-07-04)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR 4 References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-westerlund-avtcore-rtp-simulcast-04.txt

Abstract

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.

Authors

Magnus Westerlund (magnus.westerlund@ericsson.com)
Bo Burman (bo.burman@ericsson.com)
Suhas Nandakumar (snandaku@cisco.com)

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