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

Document Type Active Internet-Draft (quic WG)
Last updated 2018-10-23
Replaces draft-hamilton-quic-transport-protocol
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Jul 2019 - Core Protocol docume... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
QUIC                                                     J. Iyengar, Ed.
Internet-Draft                                                    Fastly
Intended status: Standards Track                         M. Thomson, Ed.
Expires: April 26, 2019                                          Mozilla
                                                        October 23, 2018

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

Abstract

   This document defines the core of the QUIC transport protocol.  This
   document describes connection establishment, packet format,
   multiplexing, and reliability.  Accompanying documents describe the
   cryptographic handshake and loss detection.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (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 April 26, 2019.

Iyengar & Thomson        Expires April 26, 2019                 [Page 1]
Internet-Draft           QUIC Transport Protocol            October 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.1.  Document Structure  . . . . . . . . . . . . . . . . . . .   6
     1.2.  Conventions and Definitions . . . . . . . . . . . . . . .   7
     1.3.  Notational Conventions  . . . . . . . . . . . . . . . . .   8
   2.  Streams . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     2.1.  Stream Identifiers  . . . . . . . . . . . . . . . . . . .   9
     2.2.  Stream Concurrency  . . . . . . . . . . . . . . . . . . .  10
     2.3.  Sending and Receiving Data  . . . . . . . . . . . . . . .  11
     2.4.  Stream Prioritization . . . . . . . . . . . . . . . . . .  11
   3.  Stream States: Life of a Stream . . . . . . . . . . . . . . .  12
     3.1.  Send Stream States  . . . . . . . . . . . . . . . . . . .  13
     3.2.  Receive Stream States . . . . . . . . . . . . . . . . . .  15
     3.3.  Permitted Frame Types . . . . . . . . . . . . . . . . . .  18
     3.4.  Bidirectional Stream States . . . . . . . . . . . . . . .  18
     3.5.  Solicited State Transitions . . . . . . . . . . . . . . .  19
   4.  Flow Control  . . . . . . . . . . . . . . . . . . . . . . . .  20
     4.1.  Handling of Stream Cancellation . . . . . . . . . . . . .  21
     4.2.  Data Limit Increments . . . . . . . . . . . . . . . . . .  22
     4.3.  Stream Final Offset . . . . . . . . . . . . . . . . . . .  23
     4.4.  Flow Control for Cryptographic Handshake  . . . . . . . .  24
     4.5.  Stream Limit Increment  . . . . . . . . . . . . . . . . .  24
   5.  Connections . . . . . . . . . . . . . . . . . . . . . . . . .  24
     5.1.  Connection ID . . . . . . . . . . . . . . . . . . . . . .  24
       5.1.1.  Issuing Connection IDs  . . . . . . . . . . . . . . .  25
       5.1.2.  Consuming and Retiring Connection IDs . . . . . . . .  26
     5.2.  Matching Packets to Connections . . . . . . . . . . . . .  27
       5.2.1.  Client Packet Handling  . . . . . . . . . . . . . . .  27
       5.2.2.  Server Packet Handling  . . . . . . . . . . . . . . .  27
     5.3.  Life of a QUIC Connection . . . . . . . . . . . . . . . .  28
   6.  Version Negotiation . . . . . . . . . . . . . . . . . . . . .  28
     6.1.  Sending Version Negotiation Packets . . . . . . . . . . .  29
Show full document text