Questions for Multiple Paths In QUIC
draft-dawkins-quic-multipath-questions-01

Document Type Active Internet-Draft (individual)
Author Spencer Dawkins 
Last updated 2021-01-17
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 Working Group                                       S. Dawkins, Ed.
Internet-Draft                                           Tencent America
Intended status: Informational                          January 17, 2021
Expires: July 21, 2021

                  Questions for Multiple Paths In QUIC
               draft-dawkins-quic-multipath-questions-01

Abstract

   The IETF QUIC working group has been chartered to produce extensions
   that would "enable ... multipath capabilities" since the working
   group was formed in 2016, but because multipath was an extension,
   work on multipath, and the other extensions named in the charter,
   waited while work proceeded on the core QUIC protocol specifications.

   After the QUIC working group chairs requested publication for the
   core QUIC protocol specifications, they scheduled a virtual interim
   meeting to understand the use cases that various groups inside and
   outside the IETF were envisioning for multipath with QUIC.

   As part of that discussion, it became obvious that people had a
   variety of ideas about how multiple paths would be used, because they
   weren't looking at the same use cases, and so had different
   assumptions about how applications might use QUIC over multiple
   paths.

   This document is intended to capture questions that have come up in
   discussions, with some suggested answers, to inform further
   discussion in the working group.

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 July 21, 2021.

Dawkins                   Expires July 21, 2021                 [Page 1]
Internet-Draft          QUIC Multipath Questions            January 2021

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  A 2500-year Side Trip . . . . . . . . . . . . . . . . . .   3
     1.2.  Back to the Introduction  . . . . . . . . . . . . . . . .   4
     1.3.  Notes for Readers . . . . . . . . . . . . . . . . . . . .   4
     1.4.  Contribution and Discussion Venues for this draft.  . . .   5
   2.  Metaquestions About QUIC Multipath  . . . . . . . . . . . . .   5
     2.1.  MQ-Need Do We Need Multipath in QUIC? . . . . . . . . . .   5
     2.2.  MQ-Have Do We Already Have Multipath in QUIC? . . . . . .   6
   3.  Questions about Multipath in QUIC . . . . . . . . . . . . . .   6
     3.1.  Q-HowMany Is There One "Multipath"? . . . . . . . . . . .   6
     3.2.  Q-Transport Do Transport Protocols Need to Support
           Multipath?  . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Q-HTTP3 Does Multipath for QUIC Imply Multipath for
           HTTP/3-QUIC?  . . . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Q-Symmetric Do Applications Need Symmetric Multipath
           QUIC? . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.5.  Q-Reorder What are the Expectations about Reordering? . .   9
     3.6.  Q-CB How Will We Measure the Benefits and Costs of
           Multipath?  . . . . . . . . . . . . . . . . . . . . . . .  10
     3.7.  Q-Goals What Are the Goals for using Multiple Paths?  . .  10
     3.8.  Q-API What are the API Considerations for Multipath?  . .  11
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Informative References  . . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

Dawkins                   Expires July 21, 2021                 [Page 2]
Internet-Draft          QUIC Multipath Questions            January 2021
Show full document text