datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Multipath RTP (MPRTP)
draft-singh-avtcore-mprtp-08

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-01-13
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

AVT Core Working Group                                          V. Singh
Internet-Draft                                             T. Karkkainen
Intended status: Experimental                                     J. Ott
Expires: July 17, 2014                                          S. Ahsan
                                                        Aalto University
                                                               L. Eggert
                                                                  NetApp
                                                        January 13, 2014

                         Multipath RTP (MPRTP)
                      draft-singh-avtcore-mprtp-08

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 17, 2014.

Copyright Notice

Singh, et al.            Expires July 17, 2014                  [Page 1]
Internet-Draft               Multipath RTP                  January 2014

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Use-cases . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Functional goals  . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Compatibility goals . . . . . . . . . . . . . . . . . . .   5
   3.  RTP Topologies  . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  MPRTP Architecture  . . . . . . . . . . . . . . . . . . . . .   6
   5.  Example Media Flow Diagrams . . . . . . . . . . . . . . . . .   7
     5.1.  Streaming use-case  . . . . . . . . . . . . . . . . . . .   7
     5.2.  Conversational use-case . . . . . . . . . . . . . . . . .   8
   6.  MPRTP Functional Blocks . . . . . . . . . . . . . . . . . . .   9
   7.  Available Mechanisms within the Functional Blocks . . . . . .  10
     7.1.  Session Setup . . . . . . . . . . . . . . . . . . . . . .  10
       7.1.1.  Connectivity Checks . . . . . . . . . . . . . . . . .  10
       7.1.2.  Adding New or Updating Interfaces . . . . . . . . . .  10
       7.1.3.  In-band vs. Out-of-band Signaling . . . . . . . . . .  11
     7.2.  Expanding RTP . . . . . . . . . . . . . . . . . . . . . .  12
     7.3.  Expanding RTCP  . . . . . . . . . . . . . . . . . . . . .  12
     7.4.  Failure Handling and Teardown . . . . . . . . . . . . . .  12
   8.  MPRTP Protocol  . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .  14
       8.1.1.  Gather or Discovering Candidates  . . . . . . . . . .  14

[include full document text]