Network-Assisted MPTCP: Use Cases, Deployment Scenarios and Operational Considerations
draft-nam-mptcp-deployment-considerations-01

Document Type Active Internet-Draft (individual)
Last updated 2016-12-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                  M. Boucadair, Ed.
Internet-Draft                                         C. Jacquenet, Ed.
Intended status: Informational                                    Orange
Expires: June 10, 2017                               O. Bonaventure, Ed.
                                                                Tessares
                                                      W. Henderickx, Ed.
                                                    Nokia/Alcatel-Lucent
                                                            R. Skog, Ed.
                                                                Ericsson
                                                        December 7, 2016

Network-Assisted MPTCP: Use Cases, Deployment Scenarios and Operational
                             Considerations
              draft-nam-mptcp-deployment-considerations-01

Abstract

   Network-Assisted MPTCP deployment models are designed to facilitate
   the adoption of MPTCP for the establishment of multi-path
   communications without making any assumption about the support of
   MPTCP by the communicating peers.  MPTCP Conversion Points (MCPs)
   located in the network are responsible for establishing multi-path
   communications on behalf of endpoints, thereby taking advantage of
   MPTCP capabilities to achieve different goals that include (but are
   not limited to) optimization of resource usage (e.g., bandwidth
   aggregation), of resiliency (e.g., primary/backup communication
   paths), and traffic offload management.

   This document describes Network-Assisted MPTCP uses cases, deployment
   scenarios, and operational considerations.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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

Boucadair, et al.         Expires June 10, 2017                 [Page 1]
Internet-Draft           Network-Assisted MPTCP            December 2016

   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 June 10, 2017.

Copyright Notice

   Copyright (c) 2016 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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Network-Assisted MPTCP Use Cases  . . . . . . . . . . . . . .   4
   4.  Deployment Scenarios  . . . . . . . . . . . . . . . . . . . .   5
     4.1.  LTE/WLAN Aggregation  . . . . . . . . . . . . . . . . . .   6
     4.2.  Fixed/Wireless Access Aggregation . . . . . . . . . . . .   6
     4.3.  Data Center . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Deployment & Operational Considerations . . . . . . . . . . .   7
     5.1.  MCP Location  . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  MCP Insertion in a Multipath Communication  . . . . . . .   8
       5.2.1.  Explicit Mode (Off-path)  . . . . . . . . . . . . . .   8
       5.2.2.  Implicit Mode (On-path) . . . . . . . . . . . . . . .  10
     5.3.  Authorization . . . . . . . . . . . . . . . . . . . . . .  14
     5.4.  MCP Behaviors . . . . . . . . . . . . . . . . . . . . . .  15
       5.4.1.  Transparent MCP . . . . . . . . . . . . . . . . . . .  15
       5.4.2.  Non-Transparent MCP . . . . . . . . . . . . . . . . .  17
     5.5.  Address Family Considerations . . . . . . . . . . . . . .  19
Show full document text