Key Components for Multipath QUIC Traffic Distribution
draft-an-multipath-quic-traffic-distribution-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-05
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)
QUIC                                                               Q. An
Internet-Draft                                                    D. Liu
Intended status: Standards Track                                  Y. Liu
Expires: September 6, 2020                                  Alibaba Inc.
                                                           March 5, 2020

         Key Components for Multipath QUIC Traffic Distribution
            draft-an-multipath-quic-traffic-distribution-00

Abstract

   This document describes several key components for Multipath QUIC
   traffic distribution.  The key components remain compliant with the
   current Multipath Extensions for QUIC (MP-QUIC) design.

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 September 6, 2020.

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.

An, et al.              Expires September 6, 2020               [Page 1]
Internet-Draft     multipath-quic-traffic-distribution        March 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   2
   3.  Packet Scheduling . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Stream Management . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Congestion Control  . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The QUIC connection migration feature, described in more details in
   [I-D.ietf-quic-transport], enables QUIC to sustain a connection over
   multiple paths, but still there is a void to specify simultaneous
   usage of available paths for a single connection.
   [I-D.deconinck-quic-multipath] describes how to use multiple paths
   simultaneously for a single QUIC connection, but how to spread
   packets over multiple paths following a traffic distribution policy,
   and how to receive packets from multiple paths, are not specified.
   If not standardized, implementers would still not know how to
   transmit data over multipath QUIC.

   There are several use scenarios about traffic distribution over
   multipath QUIC.  One would be stream media transmission.  A typical
   example is Internet live video broadcasting.  It has high requirement
   on data transmission speed but packet loss rate is lowly prioritized.
   In this case, multipath QUIC can provide a better utilization of
   multiple path bandwidth.  Another use scenario is highly reliable
   real-time data transmission, which is sensitive to packet loss.  In
   this case, redundancy data can be transmitted over multipath QUIC.
   To support the requirements of these use scenarios, multipath QUIC
   traffic distribution needs to be standardized.

   In this document, it focuses on the description of several key
   components which are necessary to support the implementation of
   Multipath QUIC traffic distribution.  The key components include
   packet scheduling, congestion control and stream management.

2.  Notational Conventions

   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 [RFC2119].

An, et al.              Expires September 6, 2020               [Page 2]
Internet-Draft     multipath-quic-traffic-distribution        March 2020

3.  Packet Scheduling

   Given the established multiple QUIC paths, packet scheduling
   determines which path(s) to deliver packets, how many packets are
Show full document text