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

Document Type Active Internet-Draft (individual)
Last updated 2019-12-23
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
Internet Engineering Task Force                             N. Kuhn, Ed.
Internet-Draft                                                      CNES
Intended status: Informational                           E. Stephan, Ed.
Expires: June 25, 2020                                            Orange
                                                       G. Fairhurst, Ed.
                                                  University of Aberdeen
                                                       December 23, 2019

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

Abstract

   QUIC 0-RTT relies on the sharing of the "initial_max_data" transport
   parameter between peers.  It indicates to the client the number of
   bytes it is allowed to send in the first packet of the 0-RTT
   connection.  This allows a faster startup of flows and enables
   adaptated buffer sizes at the server.  The traffic that the client
   sends, i.e. the egress trafic, is improved.  This memo proposes the
   sharing of additional transport parameters to provide a faster
   startup of flows and a better buffer management for the data that the
   client receives, i.e. the ingress traffic.

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 June 25, 2020.

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

Kuhn, et al.              Expires June 25, 2020                 [Page 1]
Internet-Draft             Transport for 0-RTT             December 2019

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  BDP metadata parameters . . . . . . . . . . . . . . . . . . .   3
   4.  Extension activation  . . . . . . . . . . . . . . . . . . . .   4
   5.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Example of server solution . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   QUIC 0-RTT relies on the sharing of the "initial_max_data" transport
   parameter between peers.  It indicates to the client the number of
   bytes it is allowed to send in the first packet of the 0-RTT
   connection.  This allows a faster startup of flows and enables
   adaptated buffer sizes at the server.  The traffic that the client
   sends, i.e. the egress trafic, is improved.  This memo proposes the
   sharing of additional transport parameters to provide a faster
   startup of flows and a better buffer management for the data that the
   client receives, i.e. the ingress traffic.

   The optimization of the time-to-service duration depends on both
   direction optimization.  QUIC may not be used for the sole use of
   HTTP3 services [I-D.ietf-quic-http], but also for symmetrical
   services.  The client device should be able to adapt to the path
   adaptation chosen by the server.  Since there are more and more
   exchange based on subscription where the server sends data first,
   with regard to ossification, it is central to dissociate the
   signalling (aka the initiator of the connection) from the peer which
   first sends application data.

   The memo focuses on cases with high Bandwidth Delay Product (BDP) and
   constrained situations (e.g. situations where buffer management at
   the client is an issue).  The extension name is 'BDP metadata'.
Show full document text