Hypertext Transfer Protocol (HTTP) over QUIC
draft-ietf-quic-http-12

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12

QUIC                                                      M. Bishop, Ed.
Internet-Draft                                                    Akamai
Intended status: Standards Track                            May 22, 2018
Expires: November 23, 2018

              Hypertext Transfer Protocol (HTTP) over QUIC
                        draft-ietf-quic-http-12

Abstract

   The QUIC transport protocol has several features that are desirable
   in a transport for HTTP, such as stream multiplexing, per-stream flow
   control, and low-latency connection establishment.  This document
   describes a mapping of HTTP semantics over QUIC.  This document also
   identifies HTTP/2 features that are subsumed by QUIC, and describes
   how HTTP/2 extensions can be ported to QUIC.

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 [1].

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

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 23, 2018.

Bishop                  Expires November 23, 2018               [Page 1]
Internet-Draft               HTTP over QUIC                     May 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   4
   2.  Connection Setup and Management . . . . . . . . . . . . . . .   4
     2.1.  Discovering an HTTP/QUIC Endpoint . . . . . . . . . . . .   4
       2.1.1.  QUIC Version Hints  . . . . . . . . . . . . . . . . .   5
     2.2.  Connection Establishment  . . . . . . . . . . . . . . . .   5
       2.2.1.  Draft Version Identification  . . . . . . . . . . . .   6
     2.3.  Connection Reuse  . . . . . . . . . . . . . . . . . . . .   6
   3.  Stream Mapping and Usage  . . . . . . . . . . . . . . . . . .   7
     3.1.  Control Streams . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  HTTP Message Exchanges  . . . . . . . . . . . . . . . . .   8
       3.2.1.  Header Compression  . . . . . . . . . . . . . . . . .   9
       3.2.2.  The CONNECT Method  . . . . . . . . . . . . . . . . .   9
       3.2.3.  Request Cancellation  . . . . . . . . . . . . . . . .  10
     3.3.  Request Prioritization  . . . . . . . . . . . . . . . . .  11
     3.4.  Server Push . . . . . . . . . . . . . . . . . . . . . . .  11
   4.  HTTP Framing Layer  . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Frame Layout  . . . . . . . . . . . . . . . . . . . . . .  13
     4.2.  Frame Definitions . . . . . . . . . . . . . . . . . . . .  13
       4.2.1.  DATA  . . . . . . . . . . . . . . . . . . . . . . . .  13
       4.2.2.  HEADERS . . . . . . . . . . . . . . . . . . . . . . .  14
       4.2.3.  PRIORITY  . . . . . . . . . . . . . . . . . . . . . .  14
       4.2.4.  CANCEL_PUSH . . . . . . . . . . . . . . . . . . . . .  16
       4.2.5.  SETTINGS  . . . . . . . . . . . . . . . . . . . . . .  17
       4.2.6.  PUSH_PROMISE  . . . . . . . . . . . . . . . . . . . .  19
       4.2.7.  GOAWAY  . . . . . . . . . . . . . . . . . . . . . . .  20
       4.2.8.  MAX_PUSH_ID . . . . . . . . . . . . . . . . . . . . .  22
   5.  Connection Management . . . . . . . . . . . . . . . . . . . .  23
   6.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .  24
     6.1.  HTTP/QUIC Error Codes . . . . . . . . . . . . . . . . . .  24
   7.  Considerations for Transitioning from HTTP/2  . . . . . . . .  25