Hypertext Transfer Protocol (HTTP) over QUIC
draft-ietf-quic-http-07
QUIC M. Bishop, Ed.
Internet-Draft Microsoft
Intended status: Standards Track October 13, 2017
Expires: April 16, 2018
Hypertext Transfer Protocol (HTTP) over QUIC
draft-ietf-quic-http-07
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 April 16, 2018.
Bishop Expires April 16, 2018 [Page 1]
Internet-Draft HTTP over QUIC October 2017
Copyright Notice
Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . 3
2. QUIC Advertisement . . . . . . . . . . . . . . . . . . . . . 4
2.1. QUIC Version Hints . . . . . . . . . . . . . . . . . . . 4
3. Connection Establishment . . . . . . . . . . . . . . . . . . 5
3.1. Draft Version Identification . . . . . . . . . . . . . . 5
4. Stream Mapping and Usage . . . . . . . . . . . . . . . . . . 5
4.1. Stream 1: Control Stream . . . . . . . . . . . . . . . . 6
4.2. HTTP Message Exchanges . . . . . . . . . . . . . . . . . 6
4.2.1. Header Compression . . . . . . . . . . . . . . . . . 7
4.2.2. The CONNECT Method . . . . . . . . . . . . . . . . . 8
4.3. Request Prioritization . . . . . . . . . . . . . . . . . 9
4.4. Server Push . . . . . . . . . . . . . . . . . . . . . . . 9
5. HTTP Framing Layer . . . . . . . . . . . . . . . . . . . . . 10
5.1. Frame Layout . . . . . . . . . . . . . . . . . . . . . . 11
5.2. Frame Definitions . . . . . . . . . . . . . . . . . . . . 11
5.2.1. DATA . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2.2. HEADERS . . . . . . . . . . . . . . . . . . . . . . . 11
5.2.3. PRIORITY . . . . . . . . . . . . . . . . . . . . . . 12
5.2.4. CANCEL_PUSH . . . . . . . . . . . . . . . . . . . . . 13
5.2.5. SETTINGS . . . . . . . . . . . . . . . . . . . . . . 14
5.2.6. PUSH_PROMISE . . . . . . . . . . . . . . . . . . . . 17
5.2.7. GOAWAY . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.8. MAX_PUSH_ID . . . . . . . . . . . . . . . . . . . . . 20
6. Connection Management . . . . . . . . . . . . . . . . . . . . 20
7. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 21
7.1. HTTP/QUIC Error Codes . . . . . . . . . . . . . . . . . . 21
8. Considerations for Transitioning from HTTP/2 . . . . . . . . 22
8.1. HTTP Frame Types . . . . . . . . . . . . . . . . . . . . 23
Show full document text