Skip to main content

Multipath RTP (MPRTP)

Document Type Expired Internet-Draft (avtcore WG)
Expired & archived
Authors Varun Singh , Teemu Karkkainen , Joerg Ott , Saba Ahsan , Lars Eggert
Last updated 2017-01-09 (Latest revision 2016-07-08)
Replaces draft-singh-avtcore-mprtp
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd Magnus Westerlund
IESG IESG state Expired
Consensus boilerplate Unknown
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:


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.


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.)