The IESG has received a request from the QUIC WG (quic) to consider the
following document: - 'Hypertext Transfer Protocol Version 3 (HTTP/3)'
<draft-ietf-quic-http-32.txt> as Proposed Standard
This document is part of a combined 26-day last call for multiple
related documents that defines the QUIC protocol and the HTTP mapping
onto QUIC. The documents are:
- draft-ietf-quic-transport
- draft-ietf-quic-recovery
- draft-ietf-quic-tls
- draft-ietf-quic-invariants
- draft-ietf-quic-http
- draft-ietf-quic-qpack
Due to its GitHub-centric work style, the QUIC WG requests that LC review
comments are individually filed as issues in the WG repository at
https://github.com/quicwg/base-drafts if at all possible. A summary email may
with
URLs to the individual issue should then also be sent to the relevant mailing
list
(primarily [email protected] and [email protected]).
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
[email protected] mailing lists by 2020-11-16. Exceptionally, comments may
be sent to [email protected] instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
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.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-quic-http/
No IPR declarations have been submitted directly on this I-D.
The document contains these normative downward references.
See RFC 3967 for additional information:
draft-ietf-httpbis-semantics: HTTP Semantics (None - IETF stream)
draft-ietf-httpbis-cache: HTTP Caching (None - IETF stream)
