Hypertext Transfer Protocol Version 3 (HTTP/3)
draft-ietf-quic-http-27
QUIC M. Bishop, Ed.
Internet-Draft Akamai
Intended status: Standards Track 21 February 2020
Expires: 24 August 2020
Hypertext Transfer Protocol Version 3 (HTTP/3)
draft-ietf-quic-http-27
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 HTTP/3.
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
(https://mailarchive.ietf.org/arch/search/?email_list=quic).
Working Group information can be found at https://github.com/quicwg
(https://github.com/quicwg); source code and issues list for this
draft can be found at https://github.com/quicwg/base-drafts/labels/-
http (https://github.com/quicwg/base-drafts/labels/-http).
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 24 August 2020.
Bishop Expires 24 August 2020 [Page 1]
Internet-Draft HTTP/3 February 2020
Copyright Notice
Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Prior versions of HTTP . . . . . . . . . . . . . . . . . 4
1.2. Delegation to QUIC . . . . . . . . . . . . . . . . . . . 5
2. HTTP/3 Protocol Overview . . . . . . . . . . . . . . . . . . 5
2.1. Document Organization . . . . . . . . . . . . . . . . . . 6
2.2. Conventions and Terminology . . . . . . . . . . . . . . . 7
3. Connection Setup and Management . . . . . . . . . . . . . . . 8
3.1. Draft Version Identification . . . . . . . . . . . . . . 8
3.2. Discovering an HTTP/3 Endpoint . . . . . . . . . . . . . 9
3.3. Connection Establishment . . . . . . . . . . . . . . . . 9
3.4. Connection Reuse . . . . . . . . . . . . . . . . . . . . 10
4. HTTP Request Lifecycle . . . . . . . . . . . . . . . . . . . 10
4.1. HTTP Message Exchanges . . . . . . . . . . . . . . . . . 10
4.1.1. Header Formatting and Compression . . . . . . . . . . 12
4.1.2. Request Cancellation and Rejection . . . . . . . . . 15
4.1.3. Malformed Requests and Responses . . . . . . . . . . 16
4.2. The CONNECT Method . . . . . . . . . . . . . . . . . . . 17
4.3. HTTP Upgrade . . . . . . . . . . . . . . . . . . . . . . 18
4.4. Server Push . . . . . . . . . . . . . . . . . . . . . . . 18
5. Connection Closure . . . . . . . . . . . . . . . . . . . . . 20
5.1. Idle Connections . . . . . . . . . . . . . . . . . . . . 20
5.2. Connection Shutdown . . . . . . . . . . . . . . . . . . . 20
5.3. Immediate Application Closure . . . . . . . . . . . . . . 22
5.4. Transport Closure . . . . . . . . . . . . . . . . . . . . 22
6. Stream Mapping and Usage . . . . . . . . . . . . . . . . . . 22
6.1. Bidirectional Streams . . . . . . . . . . . . . . . . . . 23
6.2. Unidirectional Streams . . . . . . . . . . . . . . . . . 23
6.2.1. Control Streams . . . . . . . . . . . . . . . . . . . 24
6.2.2. Push Streams . . . . . . . . . . . . . . . . . . . . 25
Show full document text