QUIC: A UDP-Based Multiplexed and Secure Transport
draft-ietf-quic-transport-32

Document Type Active Internet-Draft (quic WG)
Authors Jana Iyengar  , Martin Thomson 
Last updated 2020-10-21 (latest revision 2020-10-20)
Replaces draft-ietf-quic-spin-exp, draft-hamilton-quic-transport-protocol
Stream IETF
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jul 2020 - Core Protocol docume... )
Document shepherd Lars Eggert
Shepherd write-up Show (last changed 2020-09-25)
IESG IESG state In Last Call (ends 2020-11-16)
Consensus Boilerplate Yes
Telechat date
Responsible AD Magnus Westerlund
Send notices to quic-chairs@ietf.org
IANA IANA review state IANA - Review Needed
QUIC                                                     J. Iyengar, Ed.
Internet-Draft                                                    Fastly
Intended status: Standards Track                         M. Thomson, Ed.
Expires: 23 April 2021                                           Mozilla
                                                         20 October 2020

           QUIC: A UDP-Based Multiplexed and Secure Transport
                      draft-ietf-quic-transport-32

Abstract

   This document defines the core of the QUIC transport protocol.
   Accompanying documents describe QUIC's loss detection and congestion
   control and the use of TLS for key negotiation.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org (mailto:quic@ietf.org)), which is
   archived at https://mailarchive.ietf.org/arch/search/?email_list=quic

   Working Group information can be found at https://github.com/quicwg;
   source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-transport.

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 23 April 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Iyengar & Thomson         Expires 23 April 2021                 [Page 1]
Internet-Draft           QUIC Transport Protocol            October 2020

   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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     1.1.  Document Structure  . . . . . . . . . . . . . . . . . . .   8
     1.2.  Terms and Definitions . . . . . . . . . . . . . . . . . .   9
     1.3.  Notational Conventions  . . . . . . . . . . . . . . . . .  10
   2.  Streams . . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     2.1.  Stream Types and Identifiers  . . . . . . . . . . . . . .  12
     2.2.  Sending and Receiving Data  . . . . . . . . . . . . . . .  13
     2.3.  Stream Prioritization . . . . . . . . . . . . . . . . . .  13
     2.4.  Operations on Streams . . . . . . . . . . . . . . . . . .  14
   3.  Stream States . . . . . . . . . . . . . . . . . . . . . . . .  14
     3.1.  Sending Stream States . . . . . . . . . . . . . . . . . .  15
     3.2.  Receiving Stream States . . . . . . . . . . . . . . . . .  18
     3.3.  Permitted Frame Types . . . . . . . . . . . . . . . . . .  20
     3.4.  Bidirectional Stream States . . . . . . . . . . . . . . .  21
     3.5.  Solicited State Transitions . . . . . . . . . . . . . . .  22
   4.  Flow Control  . . . . . . . . . . . . . . . . . . . . . . . .  24
     4.1.  Data Flow Control . . . . . . . . . . . . . . . . . . . .  24
     4.2.  Increasing Flow Control Limits  . . . . . . . . . . . . .  25
     4.3.  Flow Control Performance  . . . . . . . . . . . . . . . .  26
     4.4.  Handling Stream Cancellation  . . . . . . . . . . . . . .  27
     4.5.  Stream Final Size . . . . . . . . . . . . . . . . . . . .  27
     4.6.  Controlling Concurrency . . . . . . . . . . . . . . . . .  28
   5.  Connections . . . . . . . . . . . . . . . . . . . . . . . . .  29
     5.1.  Connection ID . . . . . . . . . . . . . . . . . . . . . .  29
       5.1.1.  Issuing Connection IDs  . . . . . . . . . . . . . . .  31
       5.1.2.  Consuming and Retiring Connection IDs . . . . . . . .  32
     5.2.  Matching Packets to Connections . . . . . . . . . . . . .  33
       5.2.1.  Client Packet Handling  . . . . . . . . . . . . . . .  34
       5.2.2.  Server Packet Handling  . . . . . . . . . . . . . . .  34
       5.2.3.  Considerations for Simple Load Balancers  . . . . . .  35
     5.3.  Operations on Connections . . . . . . . . . . . . . . . .  36
   6.  Version Negotiation . . . . . . . . . . . . . . . . . . . . .  37
Show full document text