Hypertext Transfer Protocol Version 3 (HTTP/3)
draft-ietf-quic-http-34
- Versions
- 00
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
Document | Type | Active Internet-Draft (quic WG) | ||
---|---|---|---|---|
Author | Mike Bishop | |||
Last updated | 2021-02-26 (latest revision 2021-02-02) | |||
Replaces | draft-shade-quic-http2-mapping | |||
Stream | IETF | |||
Intended RFC status | Proposed Standard | |||
Formats | plain text html xml pdf htmlized (tools) htmlized bibtex | |||
Reviews | ||||
Stream | WG state | Submitted to IESG for Publication (wg milestone: Jul 2020 - HTTP/2 mapping docum... ) | ||
Document shepherd | Lucas Pardue | |||
Shepherd write-up | Show (last changed 2020-09-25) | |||
IESG | IESG state | RFC Ed Queue | ||
Action Holders |
(None)
|
|||
Consensus Boilerplate | Yes | |||
Telechat date | ||||
Responsible AD | Magnus Westerlund | |||
Send notices to | quic-chairs@ietf.org | |||
IANA | IANA review state | Version Changed - Review Needed | ||
IANA action state | Waiting on Authors | |||
IANA expert review state | Expert Reviews OK | |||
RFC Editor | RFC Editor state | MISSREF | ||
Details |
QUIC M. Bishop, Ed. Internet-Draft Akamai Intended status: Standards Track 2 February 2021 Expires: 6 August 2021 Hypertext Transfer Protocol Version 3 (HTTP/3) draft-ietf-quic-http-34 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. DO NOT DEPLOY THIS VERSION OF HTTP DO NOT DEPLOY THIS VERSION OF HTTP/3 UNTIL IT IS IN AN RFC. This version is still a work in progress. For trial deployments, please use earlier versions. 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. Working Group information can be found at https://github.com/quicwg; source code and issues list for this draft can be found at 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." Bishop Expires 6 August 2021 [Page 1] Internet-Draft HTTP/3 February 2021 This Internet-Draft will expire on 6 August 2021. Copyright Notice Copyright (c) 2021 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 . . . . . . . . . . . . . . . . . 5 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. Discovering an HTTP/3 Endpoint . . . . . . . . . . . . . 8 3.1.1. HTTP Alternative Services . . . . . . . . . . . . . . 9 3.1.2. Other Schemes . . . . . . . . . . . . . . . . . . . . 10 3.2. Connection Establishment . . . . . . . . . . . . . . . . 10 3.3. Connection Reuse . . . . . . . . . . . . . . . . . . . . 11 4. HTTP Request Lifecycle . . . . . . . . . . . . . . . . . . . 12 4.1. HTTP Message Exchanges . . . . . . . . . . . . . . . . . 12 4.1.1. Field Formatting and Compression . . . . . . . . . . 14 4.1.2. Request Cancellation and Rejection . . . . . . . . . 17 4.1.3. Malformed Requests and Responses . . . . . . . . . . 18 4.2. The CONNECT Method . . . . . . . . . . . . . . . . . . . 19 4.3. HTTP Upgrade . . . . . . . . . . . . . . . . . . . . . . 21 4.4. Server Push . . . . . . . . . . . . . . . . . . . . . . . 21 5. Connection Closure . . . . . . . . . . . . . . . . . . . . . 23 5.1. Idle Connections . . . . . . . . . . . . . . . . . . . . 23 5.2. Connection Shutdown . . . . . . . . . . . . . . . . . . . 24 5.3. Immediate Application Closure . . . . . . . . . . . . . . 26 5.4. Transport Closure . . . . . . . . . . . . . . . . . . . . 26 6. Stream Mapping and Usage . . . . . . . . . . . . . . . . . . 27 6.1. Bidirectional Streams . . . . . . . . . . . . . . . . . . 27 6.2. Unidirectional Streams . . . . . . . . . . . . . . . . . 28 6.2.1. Control Streams . . . . . . . . . . . . . . . . . . . 29Show full document text