Transport parameters for 0-RTT connections
draft-kuhn-quic-0rtt-bdp-02

Document Type Active Internet-Draft (individual)
Last updated 2019-05-21
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)
Internet Engineering Task Force                             N. Kuhn, Ed.
Internet-Draft                                                      CNES
Intended status: Informational                           E. Stephan, Ed.
Expires: November 22, 2019                                        Orange
                                                       G. Fairhurst, Ed.
                                                  University of Aberdeen
                                                            May 21, 2019

               Transport parameters for 0-RTT connections
                      draft-kuhn-quic-0rtt-bdp-02

Abstract

   The NewSessionTicket record carries a field that tells a client the
   volume of early data that it can include in the 0-RTT messages when
   reconnecting to the same peer.  There are cases where additional
   information can significantly improve the time-to-service.  This memo
   discusses a solution where path adaptation parameters are also shared
   between the peers.  There are use cases where this can accelerate the
   throughput of subsequent 0-RTT connections in both direction.

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 November 22, 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

Kuhn, et al.            Expires November 22, 2019               [Page 1]
Internet-Draft             Transport for 0-RTT                  May 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  QUIC connection establishment: differences between 1-RTT and
       0-RTT connections . . . . . . . . . . . . . . . . . . . . . .   3
   3.  End-to-end solution . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Description of the extension in the NewSessionTicket  . .   3
     3.2.  Usage of the extension in the NewSessionTicket  . . . . .   4
   4.  Best current practice . . . . . . . . . . . . . . . . . . . .   4
   5.  What happens when BDP is used incorrectly?  . . . . . . . . .   6
   6.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The 0-RTT mechanism is designed to accelerate the throughput when
   establishing a connection.  There are cases where 0-RTT alone does
   not improve the time-to-service, and additional information can
   therefore be beneficial.

   Some network paths result in a reduced time-to-service because the
   default parameters controlling the initialization of the transport
   and congestion control are not suitable for the path characteristics.
   QUIC's congestion control is based on TCP NewReno
   [I-D.ietf-quic-recovery] and the recommended initial window is
   defined by [RFC6928].  A path with a large bandwidth delay product
   can therefore significantly increase the time-to-service (e.g. a path
   using satellite communication [IJSCN19] could observe a much longer
   page load time for complex pages).

   This memo describes a solution where:

   1.  the server learns a fundamental characteristic of the path during
       the 1-RTT phase;

Kuhn, et al.            Expires November 22, 2019               [Page 2]
Internet-Draft             Transport for 0-RTT                  May 2019
Show full document text