Multipath TCP extension for Robust Session Establishment
draft-amend-mptcp-robe-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
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 Working Group                                     M. Amend
Internet-Draft                                          Deutsche Telekom
Intended status: Experimental                               July 8, 2019
Expires: January 9, 2020

        Multipath TCP extension for Robust Session Establishment
                       draft-amend-mptcp-robe-00

Abstract

   Multipath TCP extends the plain, singlepath limited, TCP towards the
   capability of multipath transmission.  This greatly improves the
   reliability and performance of TCP communication.  For backwards
   compatiblity reason the Multipath TCP was designed to setup
   successfully an inital 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.

   RobE provides the ability to simultaneously use multiple paths for
   connection setup.  This document presents with RobE a set of
   extensions to Multipath TCP to overcome its singlepath limitation
   during connection initialisation and extends it to a full fledged
   multipath protocol.  RobE ensures connecitivity 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.

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 January 9, 2020.

Amend                    Expires January 9, 2020                [Page 1]
Internet-Draft                 MPTCP RobE                      July 2019

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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Comparison of RobE and traditional MPTCP  . . . . . . . .   4
     1.3.  Simple RobE (RobE_SIM)  . . . . . . . . . . . . . . . . .   6
     1.4.  Extended RobE (RobE_EXT)  . . . . . . . . . . . . . . . .   6
   2.  Operation Overview  . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  MP_JOIN_CAP option  . . . . . . . . . . . . . . . . . . .   7
     2.2.  RobE_EXT negotiation  . . . . . . . . . . . . . . . . . .   7
     2.3.  States of operation . . . . . . . . . . . . . . . . . . .   7
       2.3.1.  RobE_SIM  . . . . . . . . . . . . . . . . . . . . . .   7
       2.3.2.  RobE_EXT  . . . . . . . . . . . . . . . . . . . . . .   7
     2.4.  Fallback mechanism  . . . . . . . . . . . . . . . . . . .   8
     2.5.  TFO support . . . . . . . . . . . . . . . . . . . . . . .   8
   3.  Practical implications  . . . . . . . . . . . . . . . . . . .   9
     3.1.  Performance compared to MP-TCP  . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Multipath TCP Robust session Establishment (MPTCP RobE) is a set of
   extensions to regular MPTCP [RFC6824] and its next upcoming version
   [I-D.ietf-mptcp-rfc6824bis], which releases single path limitations
   during the initial connection setup.  Several scenarios requires and
   benefit from a reliable and in time connection setup which is not
   covered by [RFC6824] and [I-D.ietf-mptcp-rfc6824bis] so far.  MPTCP
   was designed to be compliant with the TCP standard [RFC0793] and
   introduced therefore the concept of an inital TCP flow and adding
Show full document text