QUIC Multipath Requirements
draft-huitema-quic-mpath-req-01

Document Type Active Internet-Draft (individual)
Last updated 2018-01-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Working Group                                         C. Huitema
Internet-Draft                                      Private Octopus Inc.
Intended status: Informational                           January 7, 2018
Expires: July 11, 2018

                      QUIC Multipath Requirements
                    draft-huitema-quic-mpath-req-01

Abstract

   This document describes the requirement and plausible architecture of
   QUIC multipath extensions.  While the first version of QUIC is not
   scheduled to include multipath extensions, there are risks that
   decisions made in this first version might preclude some options that
   we may later find attractive.  An early review of multipath extension
   requirements and issues should minimize that risk.

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 11, 2018.

Copyright Notice

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

Huitema                   Expires July 11, 2018                 [Page 1]
Internet-Draft         QUIC Multipath Requirements          January 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  QUIC Multipath Scenarios  . . . . . . . . . . . . . . . . . .   3
   3.  Basic Architecture And Discussion Points  . . . . . . . . . .   4
   4.  QUIC Multipath Requirements . . . . . . . . . . . . . . . . .   5
     4.1.  Path Initiation . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Privacy . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  Security  . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.4.  Non Detectability . . . . . . . . . . . . . . . . . . . .   6
     4.5.  Error Detection . . . . . . . . . . . . . . . . . . . . .   7
     4.6.  Congestion Control  . . . . . . . . . . . . . . . . . . .   8
     4.7.  Flow Control  . . . . . . . . . . . . . . . . . . . . . .   9
     4.8.  Packet Encryption . . . . . . . . . . . . . . . . . . . .   9
     4.9.  Sequence Number Encryption  . . . . . . . . . . . . . . .  10
     4.10. Key Phases  . . . . . . . . . . . . . . . . . . . . . . .  11
     4.11. Key and sequence numbers per path . . . . . . . . . . . .  11
   5.  Next Steps  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   7.  Informative References  . . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   QUIC is a multiplexed and secure transport protocol that runs on top
   of UDP.  QUIC aims to provide a flexible set of features that allow
   it to be a general-purpose transport for multiple applications.  The
   QUIC working group is chartered to deliver a first version of the
   protocol in 2018.  The current version is defined in a set of drafts,
   describing the base transport [I-D.ietf-quic-transport], congestion
   and recovery [I-D.ietf-quic-recovery], use of TLS
   [I-D.ietf-quic-tls], and mapping of HTTP over QUIC
   [I-D.ietf-quic-http].

   According to its charter, the QUIC Working Group will first focus on
   delivering a first version of the protocol in 2018.  This first
   version will focus on the basic scenario: client connecting to server
   over a single path, for a single application, HTTP.  Multipath
   extensions will only be addressed later, once this first version is
   ready.  Focusing on a simple version and delivering it first is
   obviously a pretty reasonable way to manage a complex project like
   the development of QUIC.  However, there is a risk that decisions
   made during the development of the first version might preclude some
   options that we may later find attractive when developing the
Show full document text