Multipath RTP (MPRTP)
draft-singh-avt-mprtp-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Varun Singh , Teemu Karkkainen , Joerg Ott , Saba Ahsan , Lars Eggert | ||
| Last updated | 2011-02-28 (Latest revision 2011-02-24) | ||
| Replaced by | draft-singh-avtcore-mprtp | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-singh-avtcore-mprtp | |
| 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
The Real-time Transport Protocol (RTP) is used to deliver real-time content and, along with the RTP Control Protocol (RTCP), forms the control channel between the sender and receiver. However, RTP and RTCP assume a single delivery path between the sender and receiver and make decisions based on the measured characteristics of this single path. Increasingly, endpoints are becoming multi-homed, which means that they are connected via multiple Internet paths. Network utilization can be improved when endpoints use multiple parallel paths for communication. The resulting increase in reliability and throughput can also enhance the user experience. This document extends the Real-time Transport Protocol (RTP) so that a single session can take advantage of the availability of multiple paths between two endpoints.
Authors
Varun Singh
Teemu Karkkainen
Joerg Ott
Saba Ahsan
Lars Eggert
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)