Motivation for a Multi-Flow Real-time Transport Protocol
draft-narayanan-mrtp-motivation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sathya Narayanan | ||
| Last updated | 2004-10-19 | ||
| 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
We proposed a new multi-flow real time protocol (MRTP) in our earlier internet-draft [1] for carrying real-time data through multiple paths between the source and the destination. There are a various advantages in multipath data transport as demonstrated by [2][3] [5][8]. MRTP would provide an end-to-end transport services over multiple flows and paths to real time data. In this draft we discuss the motivation for needing such a standardized protocol to encourage further discussion on the requirement for a multi-path transport protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)