Multipath TCP Subflow Rate Limit Option
draft-hoang-mptcp-sub-rate-limit-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
MPTCP Working Group                                              V. Tran
Internet-Draft                                            O. Bonaventure
Intended status: Informational          Universite catholique de Louvain
Expires: January 9, 2020                                   July 08, 2019

                Multipath TCP Subflow Rate Limit Option
                  draft-hoang-mptcp-sub-rate-limit-00

Abstract

   This document defines a new MPTCP Option that enables hosts to
   request their peers to limit the maximum transfer rate on a per-
   subflow basis.

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.

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.

Tran & Bonaventure       Expires January 9, 2020                [Page 1]
Internet-Draft          mptcp-sub-rate-limit-opt               July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The Multipath TCP Subflow Rate Limit (SRL) Option . . . . . .   3
     3.1.  Option Format . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  SRL Option and Local Policies . . . . . . . . . . . . . .   4
   4.  Implementation and Interoperability . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Multipath TCP [RFC6824] [I-D.ietf-mptcp-rfc6824bis] is used in
   various use cases [RFC8040].  In several situations, a Multipath TCP
   host would like its peer to limit the sending rate over a specific
   subflow.

   It is common for mobile clients to have limited cellular data
   subscription.  Even if this is not the case, mobile network operators
   may still silently throttle the networking capacity of the customers
   who have used up a large amount of cellular data.  A good LTE or 5G
   connection running at full speed during less than a few hours could
   consume the entire monthly budget cellular quota of many users.  This
   is even more important when the mobile clients are roaming abroad
   where the monetary cost for cellular data can be very high.  A common
   scenario is that mobile users want to limit the monetary cost of
   using cellular networks or to avoid running out of their mobile data
   quota.  Smartphones can easily rate limit their upstream bandwidth,
   but unfortunately, most smartphone applications mainly receive data.
   For these applications, a rate limit must happen on the server side.
   This rate limit could be enforced by the application, e.g. by
   selecting a specific video coding scheme, but applying it at the
   transport layer would be more generic and could be done from the
   system level automatically.

   As discussed on the multipathtcp IETF mailing list
   [paasch_mptcpwg_2019], this rate-control mechanism can also be used
   when a client wants to inform a server to close a subflow gracefully
   by requesting a zero transfer rate.  Though the client may send a
   TCP-RST on this subflow instead, in-flight data would be lost and
   must be reinjected over other subflows.  Another solution is to send
   an MP_PRIO option to the sender to put the cellular subflow into

Tran & Bonaventure       Expires January 9, 2020                [Page 2]
Show full document text