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

The information below is for an old version of the document
Document Type Active Internet-Draft (quic WG)
Last updated 2016-11-28
Replaces draft-shade-quic-http2-mapping
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
QUIC                                                      M. Bishop, Ed.
Internet-Draft                                                 Microsoft
Intended status: Standards Track                       November 28, 2016
Expires: June 1, 2017

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

Abstract

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

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 June 1, 2017.

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

Bishop                    Expires June 1, 2017                  [Page 1]
Internet-Draft               HTTP over QUIC                November 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   2
   2.  QUIC advertisement  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Connection establishment  . . . . . . . . . . . . . . . . . .   3
   4.  Sending a request on an HTTP/2-over-QUIC connection . . . . .   4
     4.1.  Terminating a stream  . . . . . . . . . . . . . . . . . .   4
   5.  Writing data to QUIC streams  . . . . . . . . . . . . . . . .   5
   6.  Stream Mapping  . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Reserved Streams  . . . . . . . . . . . . . . . . . . . .   5
       6.1.1.  Stream 3: headers . . . . . . . . . . . . . . . . . .   6
       6.1.2.  Stream states . . . . . . . . . . . . . . . . . . . .   6
   7.  Stream Priorities . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Flow Control  . . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Server Push . . . . . . . . . . . . . . . . . . . . . . . . .   8
   10. Error Codes . . . . . . . . . . . . . . . . . . . . . . . . .   8
   11. Other HTTP/2 frames . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  GOAWAY frame . . . . . . . . . . . . . . . . . . . . . .   9
     11.2.  PING frame . . . . . . . . . . . . . . . . . . . . . . .  10
     11.3.  PADDING frame  . . . . . . . . . . . . . . . . . . . . .  10
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   14. Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Appendix A.  Contributors . . . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

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

   QUIC is described in [QUIC-TRANSPORT].  For a full description of
   HTTP/2, see [RFC7540].

1.1.  Notational Conventions

   The words "MUST", "MUST NOT", "SHOULD", and "MAY" are used in this
   document.  It's not shouting; when they are capitalized, they have
   the special meaning defined in [RFC2119].

Bishop                    Expires June 1, 2017                  [Page 2]
Internet-Draft               HTTP over QUIC                November 2016
Show full document text