Extended Socket APIs to control subflow priority in Multipath TCP
draft-samar-mptcp-socketapi-01

Document Type Active Internet-Draft (individual)
Last updated 2018-07-30
Stream (None)
Intended RFC status (None)
Formats plain text 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)
MPTCP Working Group                                     Samar Shailendra
Internet-Draft                                         Hemant Kumar Rath
Intended status: Informational                                 Arpan Pal
Expires: February 1, 2019                                        TCS R&I
                                                          Abhijit Mondal
                                                           IIT Kharagpur
                                                           July 31, 2018

   Extended Socket APIs to control subflow priority in Multipath TCP
                   draft-samar-mptcp-socketapi-01.txt

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on February 01, 2019.

Copyright Notice

   Copyright (c) 2018 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
 

Shailendra, et al.      Expires February 1, 2019                [Page 1]
Internet-Draft            Extended Socket API              July 31, 2018

   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.

Abstract

   This document provides the extended Socket APIs to control subflow
   priority for Multipath TCP. It also describes an additional data
   structure for MPTCP to make the subflow priority persistent across
   subflow disconnection.

Table of Contents

   1. Introduction...................................................2
   2. Socket APIs for subflow Priority...............................3
      2.1. Control Subflow Priority..................................4
      2.2. Remembering Subflow Priority..............................4
   3. Security Considerations........................................5
   4. IANA Considerations............................................5
   5. Conclusions....................................................5
   6. References.....................................................6
      6.1. Normative References......................................6
      6.2. Informative References....................................6
   7. Authors' Addresses.............................................7

1. Introduction

   Multipath TCP (MPTCP) [RFC6824, RFC6182] has been designed as a
   successor to TCP [RFC0793] with complete backward compatibility i.e.
   it is able to use the same TCP socket APIs as well as communicate
   with the non-MPTCP enabled hosts. MPTCP is included in the mainline
   Linux Kernel [MPLINUX]. It has also been used in various devices such
   as iPhone [I-PHONE] to improve the reliability by concurrently
   connecting the WiFi and the cellular interfaces. Currently, MPTCP has
   implemented four path managers to effectively use multiple paths
   between the source and the destination.

   o  Default: This path manager does nothing more than accepting the
      passive creation of subflows.

   o  Full Mesh: This creates a full-mesh of subflows between all
      available source and destination interfaces. Usually the subflows
      are created by the client.

   o  Ndiffports: This path manager creates multiple subflows between
      every source and destination pair. 

 

Shailendra, et al.      Expires February 1, 2019                [Page 2]
Internet-Draft            Extended Socket API              July 31, 2018

   o  Binder: This is a relatively newer path manager included in the
      list. It is based on Loose Source Routing [BOC2013].

   MPTCP is completely backward compatible with the TCP socket APIs.
   However, these socket APIs do not exploit the complete potential of
   MPTCP as these functionality are not available in TCP [RFC6824].
Show full document text