Exploring QUIC Connection Migration
draft-paulo-quic-migration-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
Stream (None)
Intended RFC status (None)
Formats plain text 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                                           R. Paulo
Internet-Draft                                                Apple Inc.
Intended status: Standards Track                          March 11, 2019
Expires: September 12, 2019

                  Exploring QUIC Connection Migration
                     draft-paulo-quic-migration-00

Abstract

   This document explores QUIC connection migration and suggests
   possible improvements.

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 12, 2019.

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.

Paulo                  Expires September 12, 2019               [Page 1]
Internet-Draft     Exploring QUIC Connection Migration        March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Connection migration strategies . . . . . . . . . . . . . . .   2
     2.1.  Failover mode . . . . . . . . . . . . . . . . . . . . . .   2
     2.2.  Standby mode  . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Improvements to connection migration  . . . . . . . . . . . .   3
     3.1.  Dealing with loss and congestion  . . . . . . . . . . . .   3
     3.2.  Keeping the alternate path alive  . . . . . . . . . . . .   4
     3.3.  Estimating RTT  . . . . . . . . . . . . . . . . . . . . .   4
     3.4.  Migrating without data to send  . . . . . . . . . . . . .   4
     3.5.  Path validation privacy . . . . . . . . . . . . . . . . .   4
     3.6.  Path MTU discovery  . . . . . . . . . . . . . . . . . . .   5
     3.7.  Interaction with loss recovery  . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   This document explores QUIC connection migration in detail and
   suggests improvements.  Familiarity with QUIC as defined in
   [QUIC-TRANSPORT] is necessary.  For reference, QUIC considers
   PATH_CHALLENGE, PATH_RESPONSE, NEW_CONNECTION_ID and PADDING frames
   as "probing frames".  All other frames are "non-probing frames"

2.  Connection migration strategies

   Protocols supporting multiple paths (such as MPTCP [RFC6824]) often
   have three modes of operation that we call failover, standby and
   aggregation.

   QUIC currently supports only the first two.

2.1.  Failover mode

   In failover mode, the networking stack monitors the quality of the
   connection or link and, when they are not operating normally, the
   QUIC connection is migrated to an alternative path.

   QUIC doesn't require any packets to be exchanged before migrating to
   a new path, so this migration is seamless.  However, if the new path
   hasn't been validated, there's less confidence that it will work.

Paulo                  Expires September 12, 2019               [Page 2]
Internet-Draft     Exploring QUIC Connection Migration        March 2019

2.2.  Standby mode

   In standby mode, the networking stack establishes and validates an
   alternative path shortly after establishing a connection on the main
   path.  When the link or the connection deteriorate, QUIC can switch
   to the alternative path.

   Even though QUIC connections can migrate without validation, this
   mode improves migration confidence and performance, as explained
Show full document text