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

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
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: 14 January 2021                                    13 July 2020

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

Abstract

   This document defines a new mechanism that enables server to send
   request to client for data scheduling between the 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 14 January 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 14 January 2021                [Page 1]
Internet-Draft     Accurate Data Scheduling by Server          July 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Typical flows for accurate data scheduling by server  . . . .   3
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     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  . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Option Format . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
   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 side considering RTT and congestion, or sending
   packets redundantly.  Application server cannot actively participate
   in such decision-making.

   However in real deployment, application server supports multiple
   network interfaces from different operators when MPTCP protocol is
   adopted.  There are such scenarios that the server wants to set
   scheduling to the client on these network interfaces based on server-
   side rules in a MPTCP session.  The requirements for these use cases
   are listed below:

   *  Network fault prevention.  Server tools can detect network quality
      of deployed network interfaces such as packet Loss, delay and
      jitter.  When the key performance indicators (KPI) become worse,
      the server hope to switch the traffic to a network interface with
      better KPI.

   *  Broadband entrances from different operators or the emergency
      entrance of 5G card are added.  This change is dynamic throughout
      the session and the operator hope to reduce the load on some
      subflows and lead them to the additional subflow, such as for
      test.  This is the trial operation scenario for new network.

   *  Value-added services.  Operator wants to provide customers with
      diversified services to satisfy individual demand.  For example,
      for VIP users, it should be possible to switch their traffic to
      network interface with better network KPIs.

Kang & Liang             Expires 14 January 2021                [Page 2]
Internet-Draft     Accurate Data Scheduling by Server          July 2020

   *  Another typical scenario is that operator hope to adjust traffic
      to a specific subflow for the changes in network cost, for
Show full document text