Accurate Data Scheduling by Server in MPTCP
draft-kang-tcpm-accurate-data-scheduling-by-server-01

Document Type Active Internet-Draft (individual)
Authors Jiao Kang  , liangqiandeng 
Last updated 2020-11-02
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) 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)
TCP Maintenance and Minor Extensions                        J. Kang, Ed.
Internet-Draft                                                  Q. Liang
Intended status: Informational                                    Huawei
Expires: 6 May 2021                                      2 November 2020

              Accurate Data Scheduling by Server in MPTCP
         draft-kang-tcpm-accurate-data-scheduling-by-server-01

Abstract

   This document defines a new mechanism that enables MPTCP server to
   send request to MPTCP client for data scheduling between specified
   subflows during a MPTCP session.

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 6 May 2021.

Copyright Notice

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

Kang & Liang               Expires 6 May 2021                   [Page 1]
Internet-Draft     Accurate Data Scheduling by Server      November 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Typical flows for accurate data scheduling by server  . . . .   3
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Traffic switching to a newly-added network interface  . .   5
     3.2.  Traffic switching to a network interface already in the
           session . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  MP_Navigation Option  . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Option Format . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Data Scheduling on client when receiving MP_Navigation  . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   MPTCP protocol is now being deployed in more and more networks.  In
   most scenarios, MPTCP scheduling strategies for these subflows are
   implemented on client considering RTT and congestion, or sending
   packets redundantly.  MPTCP server cannot participate in such
   decision-making.

   However, in actual deployment, MPTCP server is configured with
   multiple network interfaces from different operators.  There are some
   scenarios that MPTCP server wants to set scheduling on these network
   interfaces to MPTCP client based on its own rules, network planning
   and operating policies during a MPTCP session.  Requirements for
   these use cases are listed below:

   *  Network fault prevention.  Server tools can help detect quality of
      deployed network interfaces such as packet loss, delay and jitter.
      If key performance indicators (KPI) of one network interface
      becomes worse, MPTCP server hopes to indicate MPTCP client to
      switch the traffic into another network interface with better KPI.

Kang & Liang               Expires 6 May 2021                   [Page 2]
Internet-Draft     Accurate Data Scheduling by Server      November 2020

   *  A new entrance is deployed or an emergency entrance of 5G card is
      added during a MPTCP session.  In this case, MPTCP server may hope
      to lead the traffic on some subflows to the additional network
      interface.  One purpose is to test new network in trial operation.
      Other purposes include avoiding congestion and improving
      transmission reliability on existing networks.  For example, MPTCP
      server is using network of Operator A for data transmission and a
      network of operator B is added when data traffic increases.  At
      this time, MPTCP server wants to arrange traffic from network of
Show full document text