QUIC: A UDP-Based Multiplexed and Secure Transport
draft-hamilton-quic-transport-protocol-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-07-08
Replaced by draft-ietf-quic-transport
Stream (None)
Intended RFC status (None)
Formats 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)
Network Working Group                                        R. Hamilton
Internet-Draft                                                J. Iyengar
Intended status: Informational                                  I. Swett
Expires: January 9, 2017                                         A. Wilk
                                                                  Google
                                                            July 8, 2016

           QUIC: A UDP-Based Multiplexed and Secure Transport
               draft-hamilton-quic-transport-protocol-00

Abstract

   QUIC (Quick UDP-based Internet Connection) is a multiplexed and
   secure transport protocol that runs on top of UDP.  QUIC builds on
   past transport experience, and implements mechanisms that make it
   useful as a modern general-purpose transport protocol.  Using UDP as
   the basis of QUIC is intended to address compatibility issues with
   legacy clients and middleboxes.  QUIC authenticates all of its
   headers, preventing third parties from from changing them.  QUIC
   encrypts most of its headers, thereby limiting protocol evolution to
   QUIC endpoints only.  Therefore, middleboxes, in large part, are not
   required to be updated as new protocol versions are deployed.  This
   document describes the core QUIC protocol, including the conceptual
   design, wire format, and mechanisms of the QUIC protocol for
   connection establishment, stream multiplexing, stream and connection-
   level flow control, and data reliability.  Accompanying documents
   describe QUIC's loss recovery and congestion control, and the use of
   TLS1.3 for key negotiation.

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 http://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 January 9, 2017.

Hamilton, et al.         Expires January 9, 2017                [Page 1]
Internet-Draft                    QUIC                         July 2016

Copyright Notice

   Copyright (c) 2016 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   4
   3.  A QUIC Overview . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Low-Latency Version Negotiation . . . . . . . . . . . . .   5
     3.2.  Low-Latency Connection Establishment  . . . . . . . . . .   5
     3.3.  Stream Multiplexing . . . . . . . . . . . . . . . . . . .   5
     3.4.  Rich Signaling for Congestion Control and Loss Recovery .   5
     3.5.  Stream and Connection Flow Control  . . . . . . . . . . .   6
     3.6.  Authenticated and Encrypted Header and Payload  . . . . .   6
     3.7.  Resilience to NAT Rebinding . . . . . . . . . . . . . . .   6
   4.  Connection Establishment  . . . . . . . . . . . . . . . . . .   7
     4.1.  Version Negotiation . . . . . . . . . . . . . . . . . . .   7
     4.2.  Combined Crypto and Transport Handshake . . . . . . . . .   8
       4.2.1.  Transport Parameters and Options  . . . . . . . . . .   8
       4.2.2.  Proof of Source Address Ownership . . . . . . . . . .   9
       4.2.3.  Crypto Handshake Protocol Features  . . . . . . . . .   9
   5.  Streams: QUIC's Data Structuring Abstraction  . . . . . . . .  10
     5.1.  Life of a Stream  . . . . . . . . . . . . . . . . . . . .  11
       5.1.1.  idle  . . . . . . . . . . . . . . . . . . . . . . . .  13
       5.1.2.  reserved  . . . . . . . . . . . . . . . . . . . . . .  13
       5.1.3.  open  . . . . . . . . . . . . . . . . . . . . . . . .  13
       5.1.4.  half-closed (local) . . . . . . . . . . . . . . . . .  14
       5.1.5.  half-closed (remote)  . . . . . . . . . . . . . . . .  14
       5.1.6.  closed  . . . . . . . . . . . . . . . . . . . . . . .  15
     5.2.  Stream Identifiers  . . . . . . . . . . . . . . . . . . .  15
Show full document text