Multipath Extension for QUIC
draft-an-multipath-quic-00

Document Type Active Internet-Draft (individual)
Authors Qing An  , Yanmei Liu  , Yunfei Ma  , Zhenyu Li 
Last updated 2020-10-22
Stream (None)
Intended RFC status (None)
Formats plain text 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)
QUIC                                                               Q. An
Internet-Draft                                                    Y. Liu
Intended status: Standards Track                                   Y. Ma
Expires: April 25, 2021                                     Alibaba Inc.
                                                                   Z. Li
                                                                 ICT-CAS
                                                        October 22, 2020

                      Multipath Extension for QUIC
                       draft-an-multipath-quic-00

Abstract

   This document specifies multipath extension for the QUIC protocol to
   enable the simultaneous usage of multiple paths for a single
   connection.

   The extension is compliant with the single-path QUIC design.  The
   design principle is to support multipath by adding limited extension
   to QUIC-Transport [I-D.ietf-quic-transport].

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 April 25, 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

An, et al.               Expires April 25, 2021                 [Page 1]
Internet-Draft               multipath-quic                 October 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   3
   3.  Sub-Connection  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Enable Multipath QUIC - Handshake . . . . . . . . . . . . . .   5
   5.  Sub-connection Management . . . . . . . . . . . . . . . . . .   5
     5.1.  Multipath QUIC Interaction  . . . . . . . . . . . . . . .   5
     5.2.  Path validation and sub-connection ID negotiation . . . .   8
     5.3.  New sub-connection establishment  . . . . . . . . . . . .   9
     5.4.  Close sub-connection  . . . . . . . . . . . . . . . . . .   9
     5.5.  Sub-connection Lookup . . . . . . . . . . . . . . . . . .  10
     5.6.  Sub-connection migration  . . . . . . . . . . . . . . . .  10
     5.7.  Sub-connection state machine management . . . . . . . . .  10
     5.8.  Sender and Receiver Connection (Sub-connection) States  .  11
     5.9.  Use load balancer in Multipath QUIC . . . . . . . . . . .  11
   6.  Packet scheduling . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.2.  Basic Static Scheduling Strategy  . . . . . . . . . . . .  12
     6.3.  Dynamic (feedback-based) Scheduling Strategy  . . . . . .  13
     6.4.  Application Policy-Awareness  . . . . . . . . . . . . . .  14
       6.4.1.  Per-connection Policy . . . . . . . . . . . . . . . .  15
       6.4.2.  Per-stream Policy . . . . . . . . . . . . . . . . . .  17
   7.  Congestion control and loss detect  . . . . . . . . . . . . .  18
     7.1.  Congestion control  . . . . . . . . . . . . . . . . . . .  18
     7.2.  Packet number space and acknowledgements  . . . . . . . .  18
     7.3.  Flow control  . . . . . . . . . . . . . . . . . . . . . .  18
   8.  New frames  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  MP_SUB_CONN_NEW frame . . . . . . . . . . . . . . . . . .  19
     8.2.  MP_SUB_CONN_ACCEPT frame  . . . . . . . . . . . . . . . .  19
     8.3.  MP_SUB_CONN_CLOSE frame . . . . . . . . . . . . . . . . .  19
     8.4.  MP_ACK frame  . . . . . . . . . . . . . . . . . . . . . .  20
     8.5.  MP_ADD_ADDRESS frame  . . . . . . . . . . . . . . . . . .  21
     8.6.  MP_REMOVE_ADDRESS frame . . . . . . . . . . . . . . . . .  21
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   10. Informative References  . . . . . . . . . . . . . . . . . . .  21
Show full document text