Multipath TCP Extension for Robust Session Establishment
draft-amend-mptcp-robe-01

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Replaces draft-kang-mptcp-initial-path-selection
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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 Working Group                                     M. Amend
Internet-Draft                                          Deutsche Telekom
Intended status: Experimental                                    J. Kang
Expires: May 7, 2020                                              Huawei
                                                        November 4, 2019

        Multipath TCP Extension for Robust Session Establishment
                       draft-amend-mptcp-robe-01

Abstract

   Multipath TCP extends the plain, single-path limited, TCP towards the
   capability of multipath transmission.  This greatly improves the
   reliability and performance of TCP communication.  For backwards
   compatibility reasons the Multipath TCP was designed to setup
   successfully an initial path first, after which subsequent paths can
   be added for multipath transmission.  For that reason the Multipath
   TCP has the same limitations as the plain TCP during connection
   setup, in case the selected path is not functional.

   This document proposes a set of implementations and possible
   combinations thereof, that provide a more Robust Establishment (RobE)
   of MPTCP sessions.  It includes RobE_TIMER, RobE_SIM, RobE_eSIM and
   RobE_IPS.

   RobE_TIMER is designed to stay close to MPTCP in that standard
   functionality is used wherever possible.  Resiliency against network
   outages is achieved by modifying the SYN retransmission timer: If one
   path is defective, another path is used.

   RobE_SIM and RobE_eSIM provides the ability to simultaneously use
   multiple paths for connection setup.  They ensure connectivity if at
   least one functional path out of a bunch of paths is given and offers
   beside that the opportunity to significantly improve loading times of
   Internet services.

   RobE_IPS provides a heuristic to select properly an initial path for
   connection establishment with a remote host based on empirical data
   derived from previous connection information.

   In practice, these independent solutions can be complementary used.
   This document also presents the design and protocol procedure for
   those combinations in addition to the respective stand-alone
   solutions.

Amend & Kang               Expires May 7, 2020                  [Page 1]
Internet-Draft                 MPTCP RobE                  November 2019

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 https://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 7, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   6
   2.  Implementation without MPTCP protocol adaptation  . . . . . .   7
     2.1.  Re-transmission Timer(RobE_TIMER) . . . . . . . . . . . .   7
     2.2.  Simultaneous Initial Paths Simple Version (RobE_SIM)  . .   8
     2.3.  Heuristic Initial Path Selection (RobE_IPS) . . . . . . .   9
       2.3.1.  Architecture  . . . . . . . . . . . . . . . . . . . .   9
       2.3.2.  Typical Scenarios . . . . . . . . . . . . . . . . . .  10
       2.3.3.  Path decision information . . . . . . . . . . . . . .  13
       2.3.4.  Initial Path Selection use local RTT information  . .  14
     2.4.  Combination of RobE_SIM and RobE_IPS  . . . . . . . . . .  14
     2.5.  Combination of RobE_TIMER and RobE_IPS  . . . . . . . . .  15
   3.  Implementation with Bi-directional MPTCP Support  . . . . . .  16
     3.1.  Simultaneous Initial Paths Extended Version (RobE_eSIM) .  16

Amend & Kang               Expires May 7, 2020                  [Page 2]
Internet-Draft                 MPTCP RobE                  November 2019

       3.1.1.  RobE_eSIM implicit Negotiation and Procedure  . . . .  17
Show full document text