Multi-Session and Multi-Source Transmission in the Real-Time Transport Protocol (RTP)
draft-schierl-avt-rtp-multi-session-transmission-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Thomas Schierl , Jonathan Lennox | ||
| Last updated | 2008-10-26 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 this draft, we discuss problems related to multi-session and multi-source transmission using the Real-Time Transport Protocol (RTP). Most of the input to this draft is taken from email discussion. Multi-session and multi-source transmission is motivated by media data which allows for different transport layer treatment of parts of the media. This is typically the case for layered media. Multi-session transmission is when media data from a single media source is split over multiple RTP sessions. Single-session multi- source transmission (from now on just called "multi-source transmission") is when data from a single media source is sent as several RTP streams in the same RTP session. The main problems discussed are the mechanisms used for data alignment and source correlation. This draft gives further an overview of payload formats using multi-sessions/multi-source transmission and highlights other transport related issues. The draft concludes with recommendations for the discussed problems.
Authors
Thomas Schierl
Jonathan Lennox
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)