Negotiating the Maximum Number of Multipath TCP (MPTCP) Subflows
draft-boucadair-mptcp-max-subflow-03

Document Type Active Internet-Draft (individual)
Last updated 2016-11-24
Replaces draft-boucadair-mptcp-extensions
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
Internet-Draft                                              C. Jacquenet
Intended status: Experimental                                     Orange
Expires: May 28, 2017                                  November 24, 2016

    Negotiating the Maximum Number of Multipath TCP (MPTCP) Subflows
                  draft-boucadair-mptcp-max-subflow-03

Abstract

   This document specifies an experimental Multipath TCP (MPTCP) option
   that is meant to negotiate the maximum number of subflows that can be
   established and maintained for a given MPTCP connection.  The purpose
   is to minimize any possible performance degradation that can be
   induced by a possibly large number of establishment requests for
   additional subflows if the remote endpoint is not appropriately
   dimensioned to handle such requests.

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

   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 28, 2017.

Copyright Notice

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

Boucadair & Jacquenet     Expires May 28, 2017                  [Page 1]
Internet-Draft           MPTCP Maximum Subflows            November 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Experiment Goals  . . . . . . . . . . . . . . . . . . . .   3
   2.  Maximum Subflows MPTCP Option (MP_MAXSUBFLOW) . . . . . . . .   3
   3.  Behavior  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   This document specifies a Multipath TCP (MPTCP) [RFC6824] option that
   is meant to indicate to a remote peer the maximum number of subflows
   that can be established within a single MPTCP connection.  If the
   remote peer honors the indication provided in this option, any
   performance degradation induced by a possibly abusive setup of
   additional subflows that exceed the said maximum becomes unlikely.

   This option mainly targets MPTCP deployments within a single
   administrative domain such as those MPTCP designs meant to achieve
   load-balancing, for example.  The use of this option contributes to
   the harmonization of node configuration within an administrative
   domain, so that an optimal number of subflows is maintained by
   involved nodes independently of their actual performance
   capabilities.  This option can be used in other deployment scenarios.
   It is out of scope of this document to identify what are such
   scenarios.

   Section 3.4 of [I-D.ietf-mptcp-experience] includes a discussion on
   the MPTCP session manager issues.  That document states that creating
   subflows between multihomed clients and servers may sometimes lead to
   operational issues.  The present document targets to soften these
Show full document text