An Improvement of MPTCP Initialization
draft-kien-mptcp-init-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
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)
Multipath TCP                                                  K. Nguyen
Internet-Draft                                                 K. Ishizu
Intended status: Standards Track                               M. Kibria
Expires: May 3, 2017                                           F. Kojima
         National Institute of Information and Communications Technology
                                                        October 30, 2016

                 An Improvement of MPTCP Initialization
                        draft-kien-mptcp-init-00

Abstract

   This draft describes a new method of connection initialization for
   Multipath TCP (MPTCP).  In the current implementation, the MPTCP's
   first subflow needs to be successfully initialized before an
   additional flow takes its turn.  This yields to a degradation of
   MPTCP benefit in many use cases (e.g., transferring short flows).  To
   overcome the problem, we propose to duplicate the first SYN packet
   and send the duplicating ones via multiple interfaces.

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 May 3, 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

Nguyen, et al.             Expires May 3, 2017                  [Page 1]
Internet-Draft   An Improvement of MPTCP Initialization     October 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Problem Description . . . . . . . . . . . . . . . . . . . . .   3
   3.  Proposal  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   MPTCP is an evolvable and efficient tool for link aggregation, e.g.,
   on multi-homing hosts in mobile wireless networks.  The flexibility
   of adding and deleting subflows introduce MPTCP benefits in
   aggregation and soft handover in many use cases.  In the current
   implementation, MPTCP shows several drawbacks including operations in
   a scenario with imbalanced paths, especially handling short flows.
   Since a large amount of Internet TCP traffic is short flows, MPTCP
   should be improved to be more suitable with the traffic pattern.  In
   the such scenario, the problem of selection of initialization path
   has big impacts on the MPTCP performance.  It has been proven by the
   theoretical analysis [analysis] and real measurements [measurement].
   However, there are limited works on solving the problem.

   In fact, MPTCP can not choose the initial path itself.  MPTCP relies
   on routing information to determine the destination for the
   initialization.  The routing is static in most cases.  The host is
   normally configured to route all the traffic through a default
   gateway.  As a result, the first SYN of initialization has to be sent
   to the gateway associated network regardless of its quality.  On the
   other hand, the routing information is available on a host for
   supporting beneficial operations of MPTCP.  To solve the mentioned
   problem, we propose to duplicate the first SYN packet.  The available
   routing information is leveraged in sending the duplications through
Show full document text