draft-ietf-quic-http-08.txt   draft-ietf-quic-http-09.txt 
QUIC M. Bishop, Ed. QUIC M. Bishop, Ed.
Internet-Draft Akamai Internet-Draft Akamai
Intended status: Standards Track December 5, 2017 Intended status: Standards Track January 28, 2018
Expires: June 8, 2018 Expires: August 1, 2018
Hypertext Transfer Protocol (HTTP) over QUIC Hypertext Transfer Protocol (HTTP) over QUIC
draft-ietf-quic-http-08 draft-ietf-quic-http-09
Abstract Abstract
The QUIC transport protocol has several features that are desirable The QUIC transport protocol has several features that are desirable
in a transport for HTTP, such as stream multiplexing, per-stream flow in a transport for HTTP, such as stream multiplexing, per-stream flow
control, and low-latency connection establishment. This document control, and low-latency connection establishment. This document
describes a mapping of HTTP semantics over QUIC. This document also describes a mapping of HTTP semantics over QUIC. This document also
identifies HTTP/2 features that are subsumed by QUIC, and describes identifies HTTP/2 features that are subsumed by QUIC, and describes
how HTTP/2 extensions can be ported to QUIC. how HTTP/2 extensions can be ported to QUIC.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 8, 2018. This Internet-Draft will expire on August 1, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. QUIC Advertisement . . . . . . . . . . . . . . . . . . . . . 4 2. Connection Setup and Management . . . . . . . . . . . . . . . 4
2.1. QUIC Version Hints . . . . . . . . . . . . . . . . . . . 4 2.1. Discovering an HTTP/QUIC Endpoint . . . . . . . . . . . . 4
3. Connection Establishment . . . . . . . . . . . . . . . . . . 5 2.1.1. QUIC Version Hints . . . . . . . . . . . . . . . . . 4
3.1. Draft Version Identification . . . . . . . . . . . . . . 5 2.2. Connection Establishment . . . . . . . . . . . . . . . . 5
4. Stream Mapping and Usage . . . . . . . . . . . . . . . . . . 6 2.2.1. Draft Version Identification . . . . . . . . . . . . 5
4.1. Control Streams . . . . . . . . . . . . . . . . . . . . . 7 2.3. Connection Reuse . . . . . . . . . . . . . . . . . . . . 6
4.2. HTTP Message Exchanges . . . . . . . . . . . . . . . . . 7 3. Stream Mapping and Usage . . . . . . . . . . . . . . . . . . 6
4.2.1. Header Compression . . . . . . . . . . . . . . . . . 8 3.1. Control Streams . . . . . . . . . . . . . . . . . . . . . 7
4.2.2. The CONNECT Method . . . . . . . . . . . . . . . . . 8 3.2. HTTP Message Exchanges . . . . . . . . . . . . . . . . . 7
4.3. Request Prioritization . . . . . . . . . . . . . . . . . 9 3.2.1. Header Compression . . . . . . . . . . . . . . . . . 9
4.4. Server Push . . . . . . . . . . . . . . . . . . . . . . . 10 3.2.2. The CONNECT Method . . . . . . . . . . . . . . . . . 9
5. HTTP Framing Layer . . . . . . . . . . . . . . . . . . . . . 11 3.3. Request Prioritization . . . . . . . . . . . . . . . . . 10
5.1. Frame Layout . . . . . . . . . . . . . . . . . . . . . . 11 3.4. Server Push . . . . . . . . . . . . . . . . . . . . . . . 10
5.2. Frame Definitions . . . . . . . . . . . . . . . . . . . . 12 4. HTTP Framing Layer . . . . . . . . . . . . . . . . . . . . . 11
5.2.1. DATA . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1. Frame Layout . . . . . . . . . . . . . . . . . . . . . . 12
5.2.2. HEADERS . . . . . . . . . . . . . . . . . . . . . . . 12 4.2. Frame Definitions . . . . . . . . . . . . . . . . . . . . 12
5.2.3. PRIORITY . . . . . . . . . . . . . . . . . . . . . . 12 4.2.1. DATA . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2.4. CANCEL_PUSH . . . . . . . . . . . . . . . . . . . . . 14 4.2.2. HEADERS . . . . . . . . . . . . . . . . . . . . . . . 13
5.2.5. SETTINGS . . . . . . . . . . . . . . . . . . . . . . 15 4.2.3. PRIORITY . . . . . . . . . . . . . . . . . . . . . . 13
5.2.6. PUSH_PROMISE . . . . . . . . . . . . . . . . . . . . 17 4.2.4. CANCEL_PUSH . . . . . . . . . . . . . . . . . . . . . 15
5.2.7. GOAWAY . . . . . . . . . . . . . . . . . . . . . . . 18 4.2.5. SETTINGS . . . . . . . . . . . . . . . . . . . . . . 15
5.2.8. MAX_PUSH_ID . . . . . . . . . . . . . . . . . . . . . 21 4.2.6. PUSH_PROMISE . . . . . . . . . . . . . . . . . . . . 18
6. Connection Management . . . . . . . . . . . . . . . . . . . . 22 4.2.7. GOAWAY . . . . . . . . . . . . . . . . . . . . . . . 19
7. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 22 4.2.8. MAX_PUSH_ID . . . . . . . . . . . . . . . . . . . . . 21
7.1. HTTP/QUIC Error Codes . . . . . . . . . . . . . . . . . . 22 5. Connection Management . . . . . . . . . . . . . . . . . . . . 22
8. Considerations for Transitioning from HTTP/2 . . . . . . . . 24 6. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Streams . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1. HTTP/QUIC Error Codes . . . . . . . . . . . . . . . . . . 23
8.2. HTTP Frame Types . . . . . . . . . . . . . . . . . . . . 24 7. Considerations for Transitioning from HTTP/2 . . . . . . . . 24
8.3. HTTP/2 SETTINGS Parameters . . . . . . . . . . . . . . . 26 7.1. Streams . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.4. HTTP/2 Error Codes . . . . . . . . . . . . . . . . . . . 27 7.2. HTTP Frame Types . . . . . . . . . . . . . . . . . . . . 24
9. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7.3. HTTP/2 SETTINGS Parameters . . . . . . . . . . . . . . . 26
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 7.4. HTTP/2 Error Codes . . . . . . . . . . . . . . . . . . . 27
10.1. Registration of HTTP/QUIC Identification String . . . . 28 8. Security Considerations . . . . . . . . . . . . . . . . . . . 28
10.2. Registration of QUIC Version Hint Alt-Svc Parameter . . 28 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
10.3. Frame Types . . . . . . . . . . . . . . . . . . . . . . 29 9.1. Registration of HTTP/QUIC Identification String . . . . . 28
10.4. Settings Parameters . . . . . . . . . . . . . . . . . . 30 9.2. Registration of QUIC Version Hint Alt-Svc Parameter . . . 28
10.5. Error Codes . . . . . . . . . . . . . . . . . . . . . . 31 9.3. Frame Types . . . . . . . . . . . . . . . . . . . . . . . 29
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 9.4. Settings Parameters . . . . . . . . . . . . . . . . . . . 30
11.1. Normative References . . . . . . . . . . . . . . . . . . 34 9.5. Error Codes . . . . . . . . . . . . . . . . . . . . . . . 31
11.2. Informative References . . . . . . . . . . . . . . . . . 35 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 35 10.1. Normative References . . . . . . . . . . . . . . . . . . 33
10.2. Informative References . . . . . . . . . . . . . . . . . 34
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 35 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 35
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 35 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 35
B.1. Since draft-ietf-quic-http-07 . . . . . . . . . . . . . . 35 B.1. Since draft-ietf-quic-http-08 . . . . . . . . . . . . . . 35
B.2. Since draft-ietf-quic-http-06 . . . . . . . . . . . . . . 35 B.2. Since draft-ietf-quic-http-07 . . . . . . . . . . . . . . 35
B.3. Since draft-ietf-quic-http-05 . . . . . . . . . . . . . . 36 B.3. Since draft-ietf-quic-http-06 . . . . . . . . . . . . . . 35
B.4. Since draft-ietf-quic-http-04 . . . . . . . . . . . . . . 36 B.4. Since draft-ietf-quic-http-05 . . . . . . . . . . . . . . 35
B.5. Since draft-ietf-quic-http-03 . . . . . . . . . . . . . . 36 B.5. Since draft-ietf-quic-http-04 . . . . . . . . . . . . . . 35
B.6. Since draft-ietf-quic-http-02 . . . . . . . . . . . . . . 36 B.6. Since draft-ietf-quic-http-03 . . . . . . . . . . . . . . 36
B.7. Since draft-ietf-quic-http-01 . . . . . . . . . . . . . . 36 B.7. Since draft-ietf-quic-http-02 . . . . . . . . . . . . . . 36
B.8. Since draft-ietf-quic-http-00 . . . . . . . . . . . . . . 37 B.8. Since draft-ietf-quic-http-01 . . . . . . . . . . . . . . 36
B.9. Since draft-shade-quic-http2-mapping-00 . . . . . . . . . 37 B.9. Since draft-ietf-quic-http-00 . . . . . . . . . . . . . . 36
B.10. Since draft-shade-quic-http2-mapping-00 . . . . . . . . . 37
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 37 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 37
1. Introduction 1. Introduction
The QUIC transport protocol has several features that are desirable The QUIC transport protocol has several features that are desirable
in a transport for HTTP, such as stream multiplexing, per-stream flow in a transport for HTTP, such as stream multiplexing, per-stream flow
control, and low-latency connection establishment. This document control, and low-latency connection establishment. This document
describes a mapping of HTTP semantics over QUIC, drawing heavily on describes a mapping of HTTP semantics over QUIC, drawing heavily on
the existing TCP mapping, HTTP/2. Specifically, this document the existing TCP mapping, HTTP/2. Specifically, this document
identifies HTTP/2 features that are subsumed by QUIC, and describes identifies HTTP/2 features that are subsumed by QUIC, and describes
skipping to change at page 4, line 12 skipping to change at page 4, line 15
Field definitions are given in Augmented Backus-Naur Form (ABNF), as Field definitions are given in Augmented Backus-Naur Form (ABNF), as
defined in [RFC5234]. defined in [RFC5234].
This document uses the variable-length integer encoding from This document uses the variable-length integer encoding from
[QUIC-TRANSPORT]. [QUIC-TRANSPORT].
Protocol elements called "frames" exist in both this document and Protocol elements called "frames" exist in both this document and
[QUIC-TRANSPORT]. Where frames from [QUIC-TRANSPORT] are referenced, [QUIC-TRANSPORT]. Where frames from [QUIC-TRANSPORT] are referenced,
the frame name will be prefaced with "QUIC." For example, "QUIC the frame name will be prefaced with "QUIC." For example, "QUIC
APPLICATION_CLOSE frames." References without this preface refer to APPLICATION_CLOSE frames." References without this preface refer to
frames defined in Section 5.2. frames defined in Section 4.2.
2. QUIC Advertisement 2. Connection Setup and Management
2.1. Discovering an HTTP/QUIC Endpoint
An HTTP origin advertises the availability of an equivalent HTTP/QUIC An HTTP origin advertises the availability of an equivalent HTTP/QUIC
endpoint via the Alt-Svc HTTP response header or the HTTP/2 ALTSVC endpoint via the Alt-Svc HTTP response header or the HTTP/2 ALTSVC
frame ([RFC7838]), using the ALPN token defined in Section 3. frame ([RFC7838]), using the ALPN token defined in Section 2.2.
For example, an origin could indicate in an HTTP/1.1 or HTTP/2 For example, an origin could indicate in an HTTP/1.1 or HTTP/2
response that HTTP/QUIC was available on UDP port 50781 at the same response that HTTP/QUIC was available on UDP port 50781 at the same
hostname by including the following header in any response: hostname by including the following header in any response:
Alt-Svc: hq=":50781" Alt-Svc: hq=":50781"
On receipt of an Alt-Svc header indicating HTTP/QUIC support, a On receipt of an Alt-Svc header indicating HTTP/QUIC support, a
client MAY attempt to establish a QUIC connection to the indicated client MAY attempt to establish a QUIC connection to the indicated
host and port and, if successful, send HTTP requests using the host and port and, if successful, send HTTP requests using the
skipping to change at page 4, line 40 skipping to change at page 4, line 45
Connectivity problems (e.g. firewall blocking UDP) can result in QUIC Connectivity problems (e.g. firewall blocking UDP) can result in QUIC
connection establishment failure, in which case the client SHOULD connection establishment failure, in which case the client SHOULD
continue using the existing connection or try another alternative continue using the existing connection or try another alternative
endpoint offered by the origin. endpoint offered by the origin.
Servers MAY serve HTTP/QUIC on any UDP port. Servers MUST use the Servers MAY serve HTTP/QUIC on any UDP port. Servers MUST use the
same port across all IP addresses that serve a single domain, and same port across all IP addresses that serve a single domain, and
SHOULD NOT change this port. SHOULD NOT change this port.
2.1. QUIC Version Hints 2.1.1. QUIC Version Hints
This document defines the "quic" parameter for Alt-Svc, which MAY be This document defines the "quic" parameter for Alt-Svc, which MAY be
used to provide version-negotiation hints to HTTP/QUIC clients. QUIC used to provide version-negotiation hints to HTTP/QUIC clients. QUIC
versions are four-octet sequences with no additional constraints on versions are four-octet sequences with no additional constraints on
format. Syntax: format. Syntax:
quic = version-number quic = version-number
version-number = 1*8HEXDIG; hex-encoded QUIC version version-number = 1*8HEXDIG; hex-encoded QUIC version
Leading zeros SHOULD be omitted for brevity. When multiple versions Leading zeros SHOULD be omitted for brevity. When multiple versions
skipping to change at page 5, line 15 skipping to change at page 5, line 22
could specify the following header: could specify the following header:
Alt-Svc: hq=":49288";quic=1;quic=51303334 Alt-Svc: hq=":49288";quic=1;quic=51303334
Where multiple versions are listed, the order of the values reflects Where multiple versions are listed, the order of the values reflects
the server's preference (with the first value being the most the server's preference (with the first value being the most
preferred version). Origins SHOULD list only versions which are preferred version). Origins SHOULD list only versions which are
supported by the alternative, but MAY omit supported versions for any supported by the alternative, but MAY omit supported versions for any
reason. reason.
3. Connection Establishment 2.2. Connection Establishment
HTTP/QUIC connections are established as described in HTTP/QUIC relies on QUIC as the underlying transport. The QUIC
[QUIC-TRANSPORT]. During connection establishment, HTTP/QUIC support version being used MUST use TLS version 1.3 or greater as its
is indicated by selecting the ALPN token "hq" in the crypto handshake protocol. The Server Name Indication (SNI) extension
[RFC6066] MUST be included in the TLS handshake.
QUIC connections are established as described in [QUIC-TRANSPORT].
During connection establishment, HTTP/QUIC support is indicated by
selecting the ALPN token "hq" in the TLS handshake. Support for
other application-layer protocols MAY be offered in the same
handshake. handshake.
While connection-level options pertaining to the core QUIC protocol While connection-level options pertaining to the core QUIC protocol
are set in the initial crypto handshake, HTTP-specific settings are are set in the initial crypto handshake, HTTP-specific settings are
conveyed in the SETTINGS frame. After the QUIC connection is conveyed in the SETTINGS frame. After the QUIC connection is
established, a SETTINGS frame (Section 5.2.5) MUST be sent by each established, a SETTINGS frame (Section 4.2.5) MUST be sent by each
endpoint as the initial frame of their respective HTTP control stream endpoint as the initial frame of their respective HTTP control stream
(Stream ID 2 or 3, see Section 4). The server MUST NOT send data on (Stream ID 2 or 3, see Section 3). The server MUST NOT send data on
any other stream until the client's SETTINGS frame has been received. any other stream until the client's SETTINGS frame has been received.
3.1. Draft Version Identification 2.2.1. Draft Version Identification
*RFC Editor's Note:* Please remove this section prior to *RFC Editor's Note:* Please remove this section prior to
publication of a final version of this document. publication of a final version of this document.
Only implementations of the final, published RFC can identify Only implementations of the final, published RFC can identify
themselves as "hq". Until such an RFC exists, implementations MUST themselves as "hq". Until such an RFC exists, implementations MUST
NOT identify themselves using this string. NOT identify themselves using this string.
Implementations of draft versions of the protocol MUST add the string Implementations of draft versions of the protocol MUST add the string
"-" and the corresponding draft number to the identifier. For "-" and the corresponding draft number to the identifier. For
skipping to change at page 6, line 5 skipping to change at page 6, line 19
Non-compatible experiments that are based on these draft versions Non-compatible experiments that are based on these draft versions
MUST append the string "-" and an experiment name to the identifier. MUST append the string "-" and an experiment name to the identifier.
For example, an experimental implementation based on draft-ietf-quic- For example, an experimental implementation based on draft-ietf-quic-
http-09 which reserves an extra stream for unsolicited transmission http-09 which reserves an extra stream for unsolicited transmission
of 1980s pop music might identify itself as "hq-09-rickroll". Note of 1980s pop music might identify itself as "hq-09-rickroll". Note
that any label MUST conform to the "token" syntax defined in that any label MUST conform to the "token" syntax defined in
Section 3.2.6 of [RFC7230]. Experimenters are encouraged to Section 3.2.6 of [RFC7230]. Experimenters are encouraged to
coordinate their experiments on the quic@ietf.org mailing list. coordinate their experiments on the quic@ietf.org mailing list.
4. Stream Mapping and Usage 2.3. Connection Reuse
Once a connection exists to a server endpoint, this connection MAY be
reused for requests with multiple different URI authority components.
The client MAY send any requests for which the client considers the
server authoritative.
An authoritative HTTP/QUIC endpoint is typically discovered because
the client has received an Alt-Svc record from the request's origin
which nominates the endpoint as a valid HTTP Alternative Service for
that origin. As required by [RFC7838], clients MUST check that the
nominated server can present a valid certificate for the origin
before considering it authoritative. Clients MUST NOT assume that an
HTTP/QUIC endpoint is authoritative for other origins without an
explicit signal.
A server that does not wish clients to reuse connections for a
particular origin can indicate that it is not authoritative for a
request by sending a 421 (Misdirected Request) status code in
response to the request (see Section 9.1.2 of [RFC7540]).
3. Stream Mapping and Usage
A QUIC stream provides reliable in-order delivery of bytes, but makes A QUIC stream provides reliable in-order delivery of bytes, but makes
no guarantees about order of delivery with regard to bytes on other no guarantees about order of delivery with regard to bytes on other
streams. On the wire, data is framed into QUIC STREAM frames, but streams. On the wire, data is framed into QUIC STREAM frames, but
this framing is invisible to the HTTP framing layer. A QUIC receiver this framing is invisible to the HTTP framing layer. A QUIC receiver
buffers and orders received STREAM frames, exposing the data buffers and orders received STREAM frames, exposing the data
contained within as a reliable byte stream to the application. contained within as a reliable byte stream to the application.
QUIC reserves the first client-initiated, bidirectional stream QUIC reserves the first client-initiated, bidirectional stream
(Stream 0) for cryptographic operations. HTTP over QUIC reserves the (Stream 0) for cryptographic operations. HTTP over QUIC reserves the
skipping to change at page 6, line 37 skipping to change at page 7, line 23
bidirectional stream. A bidirectional stream ensures that the bidirectional stream. A bidirectional stream ensures that the
response can be readily correlated with the request. This means that response can be readily correlated with the request. This means that
the client's first request occurs on QUIC stream 4, with subsequent the client's first request occurs on QUIC stream 4, with subsequent
requests on stream 8, 12, and so on. requests on stream 8, 12, and so on.
Server push uses server-initiated, unidirectional streams. Thus, the Server push uses server-initiated, unidirectional streams. Thus, the
server's first push consumes stream 7 and subsequent pushes use server's first push consumes stream 7 and subsequent pushes use
stream 11, 15, and so on. stream 11, 15, and so on.
These streams carry frames related to the request/response (see These streams carry frames related to the request/response (see
Section 5.2). When a stream terminates cleanly, if the last frame on Section 4.2). When a stream terminates cleanly, if the last frame on
the stream was truncated, this MUST be treated as a connection error the stream was truncated, this MUST be treated as a connection error
(see HTTP_MALFORMED_* in Section 7.1). Streams which terminate (see HTTP_MALFORMED_FRAME in Section 6.1). Streams which terminate
abruptly may be reset at any point in the frame. abruptly may be reset at any point in the frame.
Streams SHOULD be used sequentially, with no gaps. Streams SHOULD be used sequentially, with no gaps.
HTTP does not need to do any separate multiplexing when using QUIC - HTTP does not need to do any separate multiplexing when using QUIC -
data sent over a QUIC stream always maps to a particular HTTP data sent over a QUIC stream always maps to a particular HTTP
transaction. Requests and responses are considered complete when the transaction. Requests and responses are considered complete when the
corresponding QUIC stream is closed in the appropriate direction. corresponding QUIC stream is closed in the appropriate direction.
4.1. Control Streams 3.1. Control Streams
Since most connection-level concerns will be managed by QUIC, the Since most connection-level concerns will be managed by QUIC, the
primary use of Streams 2 and 3 will be for the SETTINGS frame when primary use of Streams 2 and 3 will be for the SETTINGS frame when
the connection opens and for PRIORITY frames subsequently. the connection opens and for PRIORITY frames subsequently.
A pair of unidirectional streams is used rather than a single A pair of unidirectional streams is used rather than a single
bidirectional stream. This allows either peer to send data as soon bidirectional stream. This allows either peer to send data as soon
they are able. Depending on whether 0-RTT is enabled on the they are able. Depending on whether 0-RTT is enabled on the
connection, either client or server might be able to send stream data connection, either client or server might be able to send stream data
first after the cryptographic handshake completes. first after the cryptographic handshake completes.
4.2. HTTP Message Exchanges 3.2. HTTP Message Exchanges
A client sends an HTTP request on a client-initiated, bidirectional A client sends an HTTP request on a client-initiated, bidirectional
QUIC stream. A server sends an HTTP response on the same stream as QUIC stream. A server sends an HTTP response on the same stream as
the request. the request.
An HTTP message (request or response) consists of: An HTTP message (request or response) consists of:
1. one header block (see Section 5.2.2) containing the message 1. one header block (see Section 4.2.2) containing the message
headers (see [RFC7230], Section 3.2), headers (see [RFC7230], Section 3.2),
2. the payload body (see [RFC7230], Section 3.3), sent as a series 2. the payload body (see [RFC7230], Section 3.3), sent as a series
of DATA frames (see Section 5.2.1), of DATA frames (see Section 4.2.1),
3. optionally, one header block containing the trailer-part, if 3. optionally, one header block containing the trailer-part, if
present (see [RFC7230], Section 4.1.2). present (see [RFC7230], Section 4.1.2).
In addition, prior to sending the message header block indicated In addition, prior to sending the message header block indicated
above, a response may contain zero or more header blocks containing above, a response may contain zero or more header blocks containing
the message headers of informational (1xx) HTTP responses (see the message headers of informational (1xx) HTTP responses (see
[RFC7230], Section 3.2 and [RFC7231], Section 6.2). [RFC7230], Section 3.2 and [RFC7231], Section 6.2).
PUSH_PROMISE frames MAY be interleaved with the frames of a response PUSH_PROMISE frames MAY be interleaved with the frames of a response
message indicating a pushed resource related to the response. These message indicating a pushed resource related to the response. These
PUSH_PROMISE frames are not part of the response, but carry the PUSH_PROMISE frames are not part of the response, but carry the
headers of a separate HTTP request message. See Section 4.4 for more headers of a separate HTTP request message. See Section 3.4 for more
details. details.
The "chunked" transfer encoding defined in Section 4.1 of [RFC7230] The "chunked" transfer encoding defined in Section 4.1 of [RFC7230]
MUST NOT be used. MUST NOT be used.
Trailing header fields are carried in an additional header block Trailing header fields are carried in an additional header block
following the body. Such a header block is a sequence of HEADERS following the body. Such a header block is a sequence of HEADERS
frames with End Header Block set on the last frame. Senders MUST frames with End Header Block set on the last frame. Senders MUST
send only one header block in the trailers section; receivers MUST send only one header block in the trailers section; receivers MUST
discard any subsequent header blocks. discard any subsequent header blocks.
skipping to change at page 8, line 22 skipping to change at page 9, line 5
request that has not been sent and received. When this is true, a request that has not been sent and received. When this is true, a
server MAY request that the client abort transmission of a request server MAY request that the client abort transmission of a request
without error by triggering a QUIC STOP_SENDING with error code without error by triggering a QUIC STOP_SENDING with error code
HTTP_EARLY_RESPONSE, sending a complete response, and cleanly closing HTTP_EARLY_RESPONSE, sending a complete response, and cleanly closing
its streams. Clients MUST NOT discard complete responses as a result its streams. Clients MUST NOT discard complete responses as a result
of having their request terminated abruptly, though clients can of having their request terminated abruptly, though clients can
always discard responses at their discretion for other reasons. always discard responses at their discretion for other reasons.
Servers MUST NOT abort a response in progress as a result of Servers MUST NOT abort a response in progress as a result of
receiving a solicited RST_STREAM. receiving a solicited RST_STREAM.
4.2.1. Header Compression 3.2.1. Header Compression
HTTP/QUIC uses HPACK header compression as described in [RFC7541]. HTTP/QUIC uses HPACK header compression as described in [RFC7541].
HPACK was designed for HTTP/2 with the assumption of in-order HPACK was designed for HTTP/2 with the assumption of in-order
delivery such as that provided by TCP. A sequence of encoded header delivery such as that provided by TCP. A sequence of encoded header
blocks must arrive (and be decoded) at an endpoint in the same order blocks must arrive (and be decoded) at an endpoint in the same order
in which they were encoded. This ensures that the dynamic state at in which they were encoded. This ensures that the dynamic state at
the two endpoints remains in sync. the two endpoints remains in sync.
QUIC streams provide in-order delivery of data sent on those streams, QUIC streams provide in-order delivery of data sent on those streams,
but there are no guarantees about order of delivery between streams. but there are no guarantees about order of delivery between streams.
QUIC anticipates moving to a modified version of HPACK without this QUIC anticipates moving to a modified version of HPACK without this
assumption. In the meantime, by fixing the size of the dynamic table assumption. In the meantime, by fixing the size of the dynamic table
at zero, HPACK can be used in an unordered environment. at zero, HPACK can be used in an unordered environment.
4.2.2. The CONNECT Method 3.2.2. The CONNECT Method
The pseudo-method CONNECT ([RFC7231], Section 4.3.6) is primarily The pseudo-method CONNECT ([RFC7231], Section 4.3.6) is primarily
used with HTTP proxies to establish a TLS session with an origin used with HTTP proxies to establish a TLS session with an origin
server for the purposes of interacting with "https" resources. In server for the purposes of interacting with "https" resources. In
HTTP/1.x, CONNECT is used to convert an entire HTTP connection into a HTTP/1.x, CONNECT is used to convert an entire HTTP connection into a
tunnel to a remote host. In HTTP/2, the CONNECT method is used to tunnel to a remote host. In HTTP/2, the CONNECT method is used to
establish a tunnel over a single HTTP/2 stream to a remote host for establish a tunnel over a single HTTP/2 stream to a remote host for
similar purposes. similar purposes.
A CONNECT request in HTTP/QUIC functions in the same manner as in A CONNECT request in HTTP/QUIC functions in the same manner as in
HTTP/2. The request MUST be formatted as described in [RFC7540], HTTP/2. The request MUST be formatted as described in [RFC7540],
Section 8.3. A CONNECT request that does not conform to these Section 8.3. A CONNECT request that does not conform to these
restrictions is malformed. The message data stream MUST NOT be restrictions is malformed. The request stream MUST NOT be half-
closed at the end of the request. closed at the end of the request.
A proxy that supports CONNECT establishes a TCP connection A proxy that supports CONNECT establishes a TCP connection
([RFC0793]) to the server identified in the ":authority" pseudo- ([RFC0793]) to the server identified in the ":authority" pseudo-
header field. Once this connection is successfully established, the header field. Once this connection is successfully established, the
proxy sends a HEADERS frame containing a 2xx series status code to proxy sends a HEADERS frame containing a 2xx series status code to
the client, as defined in [RFC7231], Section 4.3.6. the client, as defined in [RFC7231], Section 4.3.6.
All DATA frames on the request stream correspond to data sent on the All DATA frames on the request stream correspond to data sent on the
TCP connection. Any DATA frame sent by the client is transmitted by TCP connection. Any DATA frame sent by the client is transmitted by
skipping to change at page 9, line 31 skipping to change at page 10, line 13
connection to the TCP server. When the proxy receives a packet with connection to the TCP server. When the proxy receives a packet with
the FIN bit set, it will terminate the send stream that it sends to the FIN bit set, it will terminate the send stream that it sends to
client. TCP connections which remain half-closed in a single client. TCP connections which remain half-closed in a single
direction are not invalid, but are often handled poorly by servers, direction are not invalid, but are often handled poorly by servers,
so clients SHOULD NOT cause send a STREAM frame with a FIN bit for so clients SHOULD NOT cause send a STREAM frame with a FIN bit for
connections on which they are still expecting data. connections on which they are still expecting data.
A TCP connection error is signaled with RST_STREAM. A proxy treats A TCP connection error is signaled with RST_STREAM. A proxy treats
any error in the TCP connection, which includes receiving a TCP any error in the TCP connection, which includes receiving a TCP
segment with the RST bit set, as a stream error of type segment with the RST bit set, as a stream error of type
HTTP_CONNECT_ERROR (Section 7.1). Correspondingly, a proxy MUST send HTTP_CONNECT_ERROR (Section 6.1). Correspondingly, a proxy MUST send
a TCP segment with the RST bit set if it detects an error with the a TCP segment with the RST bit set if it detects an error with the
stream or the QUIC connection. stream or the QUIC connection.
4.3. Request Prioritization 3.3. Request Prioritization
HTTP/QUIC uses the priority scheme described in [RFC7540], HTTP/QUIC uses the priority scheme described in [RFC7540],
Section 5.3. In this priority scheme, a given request can be Section 5.3. In this priority scheme, a given request can be
designated as dependent upon another request, which expresses the designated as dependent upon another request, which expresses the
preference that the latter stream (the "parent" request) be allocated preference that the latter stream (the "parent" request) be allocated
resources before the former stream (the "dependent" request). Taken resources before the former stream (the "dependent" request). Taken
together, the dependencies across all requests in a connection form a together, the dependencies across all requests in a connection form a
dependency tree. The structure of the dependency tree changes as dependency tree. The structure of the dependency tree changes as
PRIORITY frames add, remove, or change the dependency links between PRIORITY frames add, remove, or change the dependency links between
requests. requests.
HTTP/2 defines its priorities in terms of streams whereas HTTP over The PRIORITY frame Section 4.2.3 identifies a request either by
QUIC identifies requests. The PRIORITY frame Section 5.2.3 identifying the stream that carries a request or by using a Push ID
identifies a request either by identifying the stream that carries a (Section 4.2.6).
request or by using a Push ID (Section 5.2.6). Other than the means
of identifying requests, the prioritization system is identical to
that in HTTP/2.
Only a client can send PRIORITY frames. A server MUST NOT send a Only a client can send PRIORITY frames. A server MUST NOT send a
PRIORITY frame. PRIORITY frame.
4.4. Server Push 3.4. Server Push
HTTP/QUIC supports server push as described in [RFC7540]. During HTTP/QUIC supports server push as described in [RFC7540]. During
connection establishment, the client enables server push by sending a connection establishment, the client enables server push by sending a
MAX_PUSH_ID frame (see Section 5.2.8). A server cannot use server MAX_PUSH_ID frame (see Section 4.2.8). A server cannot use server
push until it receives a MAX_PUSH_ID frame. push until it receives a MAX_PUSH_ID frame.
As with server push for HTTP/2, the server initiates a server push by As with server push for HTTP/2, the server initiates a server push by
sending a PUSH_PROMISE frame that includes request header fields sending a PUSH_PROMISE frame that includes request header fields
attributed to the request. The PUSH_PROMISE frame is sent on the attributed to the request. The PUSH_PROMISE frame is sent on the
client-initiated, bidirectional stream that carried the request that client-initiated, bidirectional stream that carried the request that
generated the push. This allows the server push to be associated generated the push. This allows the server push to be associated
with a request. Ordering of a PUSH_PROMISE in relation to certain with a request. Ordering of a PUSH_PROMISE in relation to certain
parts of the response is important (see Section 8.2.1 of [RFC7540]). parts of the response is important (see Section 8.2.1 of [RFC7540]).
Unlike HTTP/2, the PUSH_PROMISE does not reference a stream; when a Unlike HTTP/2, the PUSH_PROMISE does not reference a stream; it
server fulfills a promise, the stream that carries the stream headers contains a Push ID. The Push ID uniquely identifies a server push
references a Push ID. This allows a server to fulfill promises in (see Section 4.2.6). This allows a server to fulfill promises in the
the order that best suits its needs. order that best suits its needs.
The server push response is conveyed on a push stream. A push stream When a server later fulfills a promise, the server push response is
is a server-initiated, unidirectional stream. A push stream includes conveyed on a push stream. A push stream is a server-initiated,
a header (see Figure 1) that identifies the PUSH_PROMISE that it unidirectional stream. A push stream always begins with a header
fulfills. This header consists of a Push ID, encoded as a variable- (see Figure 1) that identifies the Push ID of the promise that it
length integer. The Push ID identifies a server push (see fulfills, encoded as a variable-length integer.
Section 5.2.6).
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Push ID (i) | | Push ID (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Push Stream Header Figure 1: Push Stream Header
A push stream always starts with a Push ID. A client MUST treat
receiving a push stream that contains a truncated variable-length
integer as a connection error of type HTTP_MALFORMED_PUSH.
A server SHOULD use Push IDs sequentially, starting at 0. A client A server SHOULD use Push IDs sequentially, starting at 0. A client
uses the MAX_PUSH_ID frame (Section 5.2.8) to limit the number of uses the MAX_PUSH_ID frame (Section 4.2.8) to limit the number of
pushes that a server can promise. A client MUST treat receipt of a pushes that a server can promise. A client MUST treat receipt of a
push stream with a Push ID that is greater than the maximum Push ID push stream with a Push ID that is greater than the maximum Push ID
as a connection error of type HTTP_MALFORMED_PUSH. as a connection error of type HTTP_PUSH_LIMIT_EXCEEDED.
Each Push ID MUST only be used once in a push stream header. If a Each Push ID MUST only be used once in a push stream header. If a
push stream header includes a Push ID that was used in another push push stream header includes a Push ID that was used in another push
stream header, the client MUST treat this as a connection error of stream header, the client MUST treat this as a connection error of
type HTTP_MALFORMED_PUSH. The same Push ID can be used in multiple type HTTP_DUPLICATE_PUSH. The same Push ID can be used in multiple
PUSH_PROMISE frames (see Section 5.2.6). PUSH_PROMISE frames (see Section 4.2.6).
After the push stream header, a push contains a response After the push stream header, a push contains a response
(Section 4.2), with response headers, a response body (if any) (Section 3.2), with response headers, a response body (if any)
carried by DATA frames, then trailers (if any) carried by HEADERS carried by DATA frames, then trailers (if any) carried by HEADERS
frames. frames.
If a promised server push is not needed by the client, the client If a promised server push is not needed by the client, the client
SHOULD send a CANCEL_PUSH frame; if the push stream is already open, SHOULD send a CANCEL_PUSH frame; if the push stream is already open,
a QUIC STOP_SENDING frame with an appropriate error code can be used a QUIC STOP_SENDING frame with an appropriate error code can be used
instead (e.g., HTTP_PUSH_REFUSED, HTTP_PUSH_ALREADY_IN_CACHE; see instead (e.g., HTTP_PUSH_REFUSED, HTTP_PUSH_ALREADY_IN_CACHE; see
Section 7). This asks the server not to transfer the data and Section 6). This asks the server not to transfer the data and
indicates that it will be discarded upon receipt. indicates that it will be discarded upon receipt.
5. HTTP Framing Layer 4. HTTP Framing Layer
Frames are used on each stream. This section describes HTTP framing Frames are used on each stream. This section describes HTTP framing
in QUIC and highlights some differences from HTTP/2 framing. For in QUIC and highlights some differences from HTTP/2 framing. For
more detail on differences from HTTP/2, see Section 8.2. more detail on differences from HTTP/2, see Section 7.2.
5.1. Frame Layout 4.1. Frame Layout
All frames have the following format: All frames have the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length (i) ... | Length (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (8) | Flags (8) | Frame Payload (*) ... | Type (8) | Flags (8) | Frame Payload (*) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: HTTP/QUIC frame format Figure 2: HTTP/QUIC frame format
A frame includes the following fields: A frame includes the following fields:
Length: A variable-length integer that describes the length of the Length: A variable-length integer that describes the length of the
Frame Payload. This length does not include the frame header. Frame Payload. This length does not include the frame header.
Type: An 8-bit type for the frame. Type: An 8-bit type for the frame.
Flags: An 8-bit field containing flags. The Type field determines Flags: An 8-bit field containing flags. The Type field determines
the semantics of flags. the semantics of flags.
Frame Payload: A payload, the semantics of which are determined by Frame Payload: A payload, the semantics of which are determined by
the Type field. the Type field.
5.2. Frame Definitions 4.2. Frame Definitions
5.2.1. DATA 4.2.1. DATA
DATA frames (type=0x0) convey arbitrary, variable-length sequences of DATA frames (type=0x0) convey arbitrary, variable-length sequences of
octets associated with an HTTP request or response payload. octets associated with an HTTP request or response payload.
The DATA frame defines no flags. The DATA frame defines no flags.
DATA frames MUST be associated with an HTTP request or response. If DATA frames MUST be associated with an HTTP request or response. If
a DATA frame is received on either control stream, the recipient MUST a DATA frame is received on either control stream, the recipient MUST
respond with a connection error (Section 7) of type respond with a connection error (Section 6) of type
HTTP_WRONG_STREAM. HTTP_WRONG_STREAM.
DATA frames MUST contain a non-zero-length payload. If a DATA frame DATA frames MUST contain a non-zero-length payload. If a DATA frame
is received with a payload length of zero, the recipient MUST respond is received with a payload length of zero, the recipient MUST respond
with a stream error (Section 7) of type HTTP_MALFORMED_DATA. with a stream error (Section 6) of type HTTP_MALFORMED_FRAME.
5.2.2. HEADERS 4.2.2. HEADERS
The HEADERS frame (type=0x1) is used to carry a header block, The HEADERS frame (type=0x1) is used to carry a header block,
compressed using HPACK Section 4.2.1. compressed using HPACK Section 3.2.1.
No flags are defined for the HEADERS frame. No flags are defined for the HEADERS frame.
A HEADERS frame with any flags set MUST be treated as a connection A HEADERS frame with any flags set MUST be treated as a connection
error of type HTTP_MALFORMED_HEADERS. error of type HTTP_MALFORMED_FRAME.
5.2.3. PRIORITY 4.2.3. PRIORITY
The PRIORITY (type=0x02) frame specifies the sender-advised priority The PRIORITY (type=0x02) frame specifies the sender-advised priority
of a stream and is substantially different in format from [RFC7540]. of a stream and is substantially different in format from [RFC7540].
In order to ensure that prioritization is processed in a consistent In order to ensure that prioritization is processed in a consistent
order, PRIORITY frames MUST be sent on the control stream. A order, PRIORITY frames MUST be sent on the control stream. A
PRIORITY frame sent on any other stream MUST be treated as a PRIORITY frame sent on any other stream MUST be treated as a
HTTP_WRONG_STREAM error. HTTP_WRONG_STREAM error.
The format has been modified to accommodate not being sent on a The format has been modified to accommodate not being sent on a
request stream, to allow for identification of server pushes, and the request stream, to allow for identification of server pushes, and the
skipping to change at page 13, line 13 skipping to change at page 13, line 39
The flags defined are: The flags defined are:
PUSH_PRIORITIZED (0x04): Indicates that the Prioritized Stream is a PUSH_PRIORITIZED (0x04): Indicates that the Prioritized Stream is a
server push rather than a request. server push rather than a request.
PUSH_DEPENDENT (0x02): Indicates a dependency on a server push. PUSH_DEPENDENT (0x02): Indicates a dependency on a server push.
E (0x01): Indicates that the stream dependency is exclusive (see E (0x01): Indicates that the stream dependency is exclusive (see
[RFC7540], Section 5.3). [RFC7540], Section 5.3).
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prioritized Request ID (i) | | Prioritized Request ID (i) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Dependency ID (i) | | Stream Dependency ID (i) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Weight (8) | | Weight (8) |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure 3: PRIORITY frame payload Figure 3: PRIORITY frame payload
The PRIORITY frame payload has the following fields: The PRIORITY frame payload has the following fields:
Prioritized Request ID: A variable-length integer that identifies a Prioritized Request ID: A variable-length integer that identifies a
request. This contains the Stream ID of a request stream when the request. This contains the Stream ID of a request stream when the
PUSH_PRIORITIZED flag is clear, or a Push ID when the PUSH_PRIORITIZED flag is clear, or a Push ID when the
PUSH_PRIORITIZED flag is set. PUSH_PRIORITIZED flag is set.
Stream Dependency ID: A variable-length integer that identifies a Stream Dependency ID: A variable-length integer that identifies a
dependent request. This contains the Stream ID of a request dependent request. This contains the Stream ID of a request
stream when the PUSH_DEPENDENT flag is clear, or a Push ID when stream when the PUSH_DEPENDENT flag is clear, or a Push ID when
the PUSH_DEPENDENT flag is set. A request Stream ID of 0 the PUSH_DEPENDENT flag is set. A request Stream ID of 0
indicates a dependency on the root stream. For details of indicates a dependency on the root stream. For details of
dependencies, see Section 4.3 and [RFC7540], Section 5.3. dependencies, see Section 3.3 and [RFC7540], Section 5.3.
Weight: An unsigned 8-bit integer representing a priority weight for Weight: An unsigned 8-bit integer representing a priority weight for
the stream (see [RFC7540], Section 5.3). Add one to the value to the stream (see [RFC7540], Section 5.3). Add one to the value to
obtain a weight between 1 and 256. obtain a weight between 1 and 256.
A PRIORITY frame identifies a request to prioritize, and a request A PRIORITY frame identifies a request to prioritize, and a request
upon which that request is dependent. A Prioritized Request ID or upon which that request is dependent. A Prioritized Request ID or
Stream Dependency ID identifies a client-initiated request using the Stream Dependency ID identifies a client-initiated request using the
corresponding stream ID when the corresponding PUSH_PRIORITIZED or corresponding stream ID when the corresponding PUSH_PRIORITIZED or
PUSH_DEPENDENT flag is not set. Setting the PUSH_PRIORITIZED or PUSH_DEPENDENT flag is not set. Setting the PUSH_PRIORITIZED or
PUSH_DEPENDENT flag causes the Prioritized Request ID or Stream PUSH_DEPENDENT flag causes the Prioritized Request ID or Stream
Dependency ID (respectively) to identify a server push using a Push Dependency ID (respectively) to identify a server push using a Push
ID (see Section 5.2.6 for details). ID (see Section 4.2.6 for details).
A PRIORITY frame MAY identify a Stream Dependency ID using a Stream A PRIORITY frame MAY identify a Stream Dependency ID using a Stream
ID of 0; as in [RFC7540], this makes the request dependent on the ID of 0; as in [RFC7540], this makes the request dependent on the
root of the dependency tree. root of the dependency tree.
A PRIORITY frame MUST identify a client-initiated, bidirectional A PRIORITY frame MUST identify a client-initiated, bidirectional
stream. A server MUST treat receipt of PRIORITY frame with a Stream stream. A server MUST treat receipt of PRIORITY frame with a Stream
ID of any other type as a connection error of type ID of any other type as a connection error of type
HTTP_MALFORMED_PRIORITY. HTTP_MALFORMED_FRAME.
Stream ID 0 cannot be reprioritized. A Prioritized Request ID that Stream ID 0 cannot be reprioritized. A Prioritized Request ID that
identifies Stream 0 MUST be treated as a connection error of type identifies Stream 0 MUST be treated as a connection error of type
HTTP_MALFORMED_PRIORITY. HTTP_MALFORMED_FRAME.
A PRIORITY frame that does not reference a request MUST be treated as A PRIORITY frame that does not reference a request MUST be treated as
a HTTP_MALFORMED_PRIORITY error, unless it references Stream ID 0. A a HTTP_MALFORMED_FRAME error, unless it references Stream ID 0. A
PRIORITY that sets a PUSH_PRIORITIZED or PUSH_DEPENDENT flag, but PRIORITY that sets a PUSH_PRIORITIZED or PUSH_DEPENDENT flag, but
then references a non-existent Push ID MUST be treated as a then references a non-existent Push ID MUST be treated as a
HTTP_MALFORMED_PRIORITY error. HTTP_MALFORMED_FRAME error.
A PRIORITY frame MUST contain only the identified fields. A PRIORITY A PRIORITY frame MUST contain only the identified fields. A PRIORITY
frame that contains more or fewer fields, or a PRIORITY frame that frame that contains more or fewer fields, or a PRIORITY frame that
includes a truncated integer encoding MUST be treated as a connection includes a truncated integer encoding MUST be treated as a connection
error of type HTTP_MALFORMED_PRIORITY. error of type HTTP_MALFORMED_FRAME.
5.2.4. CANCEL_PUSH 4.2.4. CANCEL_PUSH
The CANCEL_PUSH frame (type=0x3) is used to request cancellation of The CANCEL_PUSH frame (type=0x3) is used to request cancellation of
server push prior to the push stream being created. The CANCEL_PUSH server push prior to the push stream being created. The CANCEL_PUSH
frame identifies a server push request by Push ID (see Section 5.2.6) frame identifies a server push request by Push ID (see Section 4.2.6)
using a variable-length integer. using a variable-length integer.
When a server receives this frame, it aborts sending the response for When a server receives this frame, it aborts sending the response for
the identified server push. If the server has not yet started to the identified server push. If the server has not yet started to
send the server push, it can use the receipt of a CANCEL_PUSH frame send the server push, it can use the receipt of a CANCEL_PUSH frame
to avoid opening a stream. If the push stream has been opened by the to avoid opening a stream. If the push stream has been opened by the
server, the server SHOULD sent a QUIC RST_STREAM frame on those server, the server SHOULD sent a QUIC RST_STREAM frame on those
streams and cease transmission of the response. streams and cease transmission of the response.
A server can send this frame to indicate that it won't be sending a A server can send this frame to indicate that it won't be sending a
skipping to change at page 15, line 9 skipping to change at page 15, line 33
cancel transmission of the server push response. cancel transmission of the server push response.
A CANCEL_PUSH frame is sent on the control stream. Sending a A CANCEL_PUSH frame is sent on the control stream. Sending a
CANCEL_PUSH frame on a stream other than the control stream MUST be CANCEL_PUSH frame on a stream other than the control stream MUST be
treated as a stream error of type HTTP_WRONG_STREAM. treated as a stream error of type HTTP_WRONG_STREAM.
The CANCEL_PUSH frame has no defined flags. The CANCEL_PUSH frame has no defined flags.
The CANCEL_PUSH frame carries a Push ID encoded as a variable-length The CANCEL_PUSH frame carries a Push ID encoded as a variable-length
integer. The Push ID identifies the server push that is being integer. The Push ID identifies the server push that is being
cancelled (see Section 5.2.6). cancelled (see Section 4.2.6).
If the client receives a CANCEL_PUSH frame, that frame might identify If the client receives a CANCEL_PUSH frame, that frame might identify
a Push ID that has not yet been mentioned by a PUSH_PROMISE frame. a Push ID that has not yet been mentioned by a PUSH_PROMISE frame.
A server MUST treat a CANCEL_PUSH frame payload does not contain An endpoint MUST treat a CANCEL_PUSH frame which does not contain
exactly one variable-length integer as a connection error of type exactly one properly-formatted variable-length integer as a
HTTP_MALFORMED_CANCEL_PUSH. connection error of type HTTP_MALFORMED_FRAME.
5.2.5. SETTINGS 4.2.5. SETTINGS
The SETTINGS frame (type=0x4) conveys configuration parameters that The SETTINGS frame (type=0x4) conveys configuration parameters that
affect how endpoints communicate, such as preferences and constraints affect how endpoints communicate, such as preferences and constraints
on peer behavior, and is different from [RFC7540]. Individually, a on peer behavior, and is different from [RFC7540]. Individually, a
SETTINGS parameter can also be referred to as a "setting". SETTINGS parameter can also be referred to as a "setting".
SETTINGS parameters are not negotiated; they describe characteristics SETTINGS parameters are not negotiated; they describe characteristics
of the sending peer, which can be used by the receiving peer. of the sending peer, which can be used by the receiving peer.
However, a negotiation can be implied by the use of SETTINGS - a peer However, a negotiation can be implied by the use of SETTINGS - a peer
uses SETTINGS to advertise a set of supported values. The recipient uses SETTINGS to advertise a set of supported values. The recipient
skipping to change at page 15, line 40 skipping to change at page 16, line 15
proceed with the value it has chosen. (This choice could be proceed with the value it has chosen. (This choice could be
announced in a field of an extension frame, or in its own value in announced in a field of an extension frame, or in its own value in
SETTINGS.) SETTINGS.)
Different values for the same parameter can be advertised by each Different values for the same parameter can be advertised by each
peer. For example, a client might be willing to consume very large peer. For example, a client might be willing to consume very large
response headers, while servers are more cautious about request size. response headers, while servers are more cautious about request size.
Parameters MUST NOT occur more than once. A receiver MAY treat the Parameters MUST NOT occur more than once. A receiver MAY treat the
presence of the same parameter more than once as a connection error presence of the same parameter more than once as a connection error
of type HTTP_MALFORMED_SETTINGS. of type HTTP_MALFORMED_FRAME.
The SETTINGS frame defines no flags. The SETTINGS frame defines no flags.
The payload of a SETTINGS frame consists of zero or more parameters, The payload of a SETTINGS frame consists of zero or more parameters,
each consisting of an unsigned 16-bit setting identifier and a each consisting of an unsigned 16-bit setting identifier and a
length-prefixed binary value. length-prefixed binary value.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier (16) | Length (i) ... | Identifier (16) | Length (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Contents (?) ... | Contents (?) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: SETTINGS value format Figure 4: SETTINGS value format
A zero-length content indicates that the setting value is a Boolean A zero-length content indicates that the setting value is a Boolean
and true. False is indicated by the absence of the setting. and true. False is indicated by the absence of the setting.
Non-zero-length values MUST be compared against the remaining length Non-zero-length values MUST be compared against the remaining length
of the SETTINGS frame. Any value which purports to cross the end of of the SETTINGS frame. Any value which purports to cross the end of
the frame MUST cause the SETTINGS frame to be considered malformed the frame MUST cause the SETTINGS frame to be considered malformed
and trigger a connection error of type HTTP_MALFORMED_SETTINGS. and trigger a connection error of type HTTP_MALFORMED_FRAME.
An implementation MUST ignore the contents for any SETTINGS An implementation MUST ignore the contents for any SETTINGS
identifier it does not understand. identifier it does not understand.
SETTINGS frames always apply to a connection, never a single stream. SETTINGS frames always apply to a connection, never a single stream.
A SETTINGS frame MUST be sent as the first frame of either control A SETTINGS frame MUST be sent as the first frame of either control
stream (see Section 4) by each peer, and MUST NOT be sent stream (see Section 3) by each peer, and MUST NOT be sent
subsequently or on any other stream. If an endpoint receives an subsequently or on any other stream. If an endpoint receives an
SETTINGS frame on a different stream, the endpoint MUST respond with SETTINGS frame on a different stream, the endpoint MUST respond with
a connection error of type HTTP_WRONG_STREAM. If an endpoint a connection error of type HTTP_WRONG_STREAM. If an endpoint
receives a second SETTINGS frame, the endpoint MUST respond with a receives a second SETTINGS frame, the endpoint MUST respond with a
connection error of type HTTP_MULTIPLE_SETTINGS. connection error of type HTTP_MALFORMED_FRAME.
The SETTINGS frame affects connection state. A badly formed or The SETTINGS frame affects connection state. A badly formed or
incomplete SETTINGS frame MUST be treated as a connection error incomplete SETTINGS frame MUST be treated as a connection error
(Section 7) of type HTTP_MALFORMED_SETTINGS. (Section 6) of type HTTP_MALFORMED_FRAME.
5.2.5.1. Integer encoding 4.2.5.1. Integer encoding
Settings which are integers use the QUIC variable-length integer Settings which are integers use the QUIC variable-length integer
encoding. encoding.
5.2.5.2. Defined SETTINGS Parameters 4.2.5.2. Defined SETTINGS Parameters
The following settings are defined in HTTP/QUIC: The following settings are defined in HTTP/QUIC:
SETTINGS_HEADER_TABLE_SIZE (0x1): An integer with a maximum value of SETTINGS_HEADER_TABLE_SIZE (0x1): An integer with a maximum value of
2^30 - 1. This value MUST be zero. 2^30 - 1. This value MUST be zero.
SETTINGS_MAX_HEADER_LIST_SIZE (0x6): An integer with a maximum value SETTINGS_MAX_HEADER_LIST_SIZE (0x6): An integer with a maximum value
of 2^30 - 1 of 2^30 - 1
5.2.5.3. Usage in 0-RTT 4.2.5.3. Usage in 0-RTT
When a 0-RTT QUIC connection is being used, the client's initial When a 0-RTT QUIC connection is being used, the client's initial
requests will be sent before the arrival of the server's SETTINGS requests will be sent before the arrival of the server's SETTINGS
frame. Clients SHOULD cache at least the following settings about frame. Clients SHOULD cache at least the following settings about
servers: servers:
o SETTINGS_HEADER_TABLE_SIZE o SETTINGS_HEADER_TABLE_SIZE
o SETTINGS_MAX_HEADER_LIST_SIZE o SETTINGS_MAX_HEADER_LIST_SIZE
skipping to change at page 17, line 38 skipping to change at page 18, line 8
If the connection is closed because these or other constraints were If the connection is closed because these or other constraints were
violated during the 0-RTT flight (e.g. with violated during the 0-RTT flight (e.g. with
HTTP_HPACK_DECOMPRESSION_FAILED), clients MAY establish a new HTTP_HPACK_DECOMPRESSION_FAILED), clients MAY establish a new
connection and retry any 0-RTT requests using the settings sent by connection and retry any 0-RTT requests using the settings sent by
the server on the closed connection. (This assumes that only the server on the closed connection. (This assumes that only
requests that are safe to retry are sent in 0-RTT.) If the requests that are safe to retry are sent in 0-RTT.) If the
connection was closed before the SETTINGS frame was received, clients connection was closed before the SETTINGS frame was received, clients
SHOULD discard any cached values and use the defaults above on the SHOULD discard any cached values and use the defaults above on the
next connection. next connection.
5.2.6. PUSH_PROMISE 4.2.6. PUSH_PROMISE
The PUSH_PROMISE frame (type=0x05) is used to carry a request header The PUSH_PROMISE frame (type=0x05) is used to carry a request header
set from server to client, as in HTTP/2. The PUSH_PROMISE frame set from server to client, as in HTTP/2. The PUSH_PROMISE frame
defines no flags. defines no flags.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Push ID (i) ... | Push ID (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Header Block (*) ... | Header Block (*) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: PUSH_PROMISE frame payload Figure 5: PUSH_PROMISE frame payload
The payload consists of: The payload consists of:
Push ID: A variable-length integer that identifies the server push Push ID: A variable-length integer that identifies the server push
request. A push ID is used in push stream header (Section 4.4), request. A push ID is used in push stream header (Section 3.4),
CANCEL_PUSH frames (Section 5.2.4), and PRIORITY frames CANCEL_PUSH frames (Section 4.2.4), and PRIORITY frames
(Section 5.2.3). (Section 4.2.3).
Header Block: HPACK-compressed request headers for the promised Header Block: HPACK-compressed request headers for the promised
response. response.
A server MUST NOT use a Push ID that is larger than the client has A server MUST NOT use a Push ID that is larger than the client has
provided in a MAX_PUSH_ID frame (Section 5.2.8). A client MUST treat provided in a MAX_PUSH_ID frame (Section 4.2.8). A client MUST treat
receipt of a PUSH_PROMISE that contains a larger Push ID than the receipt of a PUSH_PROMISE that contains a larger Push ID than the
client has advertised as a connection error of type client has advertised as a connection error of type
HTTP_MALFORMED_PUSH_PROMISE. HTTP_MALFORMED_FRAME.
A server MAY use the same Push ID in multiple PUSH_PROMISE frames. A server MAY use the same Push ID in multiple PUSH_PROMISE frames.
This allows the server to use the same server push in response to This allows the server to use the same server push in response to
multiple concurrent requests. Referencing the same server push multiple concurrent requests. Referencing the same server push
ensures that a PUSH_PROMISE can be made in relation to every response ensures that a PUSH_PROMISE can be made in relation to every response
in which server push might be needed without duplicating pushes. in which server push might be needed without duplicating pushes.
A server that uses the same Push ID in multiple PUSH_PROMISE frames A server that uses the same Push ID in multiple PUSH_PROMISE frames
MUST include the same header fields each time. The octets of the MUST include the same header fields each time. The octets of the
header block MAY be different due to differing encoding, but the header block MAY be different due to differing encoding, but the
header fields and their values MUST be identical. Note that ordering header fields and their values MUST be identical. Note that ordering
of header fields is significant. A client MUST treat receipt of a of header fields is significant. A client MUST treat receipt of a
PUSH_PROMISE with conflicting header field values for the same Push PUSH_PROMISE with conflicting header field values for the same Push
ID as a connection error of type HTTP_MALFORMED_PUSH_PROMISE. ID as a connection error of type HTTP_MALFORMED_FRAME.
Allowing duplicate references to the same Push ID is primarily to Allowing duplicate references to the same Push ID is primarily to
reduce duplication caused by concurrent requests. A server SHOULD reduce duplication caused by concurrent requests. A server SHOULD
avoid reusing a Push ID over a long period. Clients are likely to avoid reusing a Push ID over a long period. Clients are likely to
consume server push responses and not retain them for reuse over consume server push responses and not retain them for reuse over
time. Clients that see a PUSH_PROMISE that uses a Push ID that they time. Clients that see a PUSH_PROMISE that uses a Push ID that they
have since consumed and discarded are forced to ignore the have since consumed and discarded are forced to ignore the
PUSH_PROMISE. PUSH_PROMISE.
5.2.7. GOAWAY 4.2.7. GOAWAY
The GOAWAY frame (type=0x7) is used to initiate graceful shutdown of The GOAWAY frame (type=0x7) is used to initiate graceful shutdown of
a connection by a server. GOAWAY allows a server to stop accepting a connection by a server. GOAWAY allows a server to stop accepting
new requests while still finishing processing of previously received new requests while still finishing processing of previously received
requests. This enables administrative actions, like server requests. This enables administrative actions, like server
maintenance. GOAWAY by itself does not close a connection. maintenance. GOAWAY by itself does not close a connection.
The GOAWAY frame does not define any flags, and the payload is a QUIC The GOAWAY frame does not define any flags, and the payload is a QUIC
Stream ID for a client-initiated, bidirectional stream encoded as a Stream ID for a client-initiated, bidirectional stream encoded as a
variable-length integer. variable-length integer.
Clients do not need to send GOAWAY to initiate a graceful shutdown; Clients do not need to send GOAWAY to initiate a graceful shutdown;
they simply stop making new requests. A server MUST treat receipt of they simply stop making new requests. A server MUST treat receipt of
a GOAWAY frame as a connection error (Section 7) of type a GOAWAY frame as a connection error (Section 6) of type
HTTP_UNEXPECTED_GOAWAY. HTTP_UNEXPECTED_GOAWAY.
A client MUST treat receipt of a GOAWAY frame containing a Stream ID A client MUST treat receipt of a GOAWAY frame containing a Stream ID
of any other type as a connection error of type of any other type as a connection error of type HTTP_MALFORMED_FRAME.
HTTP_MALFORMED_GOAWAY.
The GOAWAY frame applies to the connection, not a specific stream. The GOAWAY frame applies to the connection, not a specific stream.
An endpoint MUST treat a GOAWAY frame on a stream other than the An endpoint MUST treat a GOAWAY frame on a stream other than the
control stream as a connection error (Section 7) of type control stream as a connection error (Section 6) of type
HTTP_WRONG_STREAM. HTTP_WRONG_STREAM.
New client requests might already have been sent before the client New client requests might already have been sent before the client
receives the server's GOAWAY frame. The GOAWAY frame contains the receives the server's GOAWAY frame. The GOAWAY frame contains the
Stream ID of the last client-initiated request that was or might be Stream ID of the last client-initiated request that was or might be
processed in this connection, which enables client and server to processed in this connection, which enables client and server to
agree on which requests were accepted prior to the connection agree on which requests were accepted prior to the connection
shutdown. This identifier MAY be lower than the stream limit shutdown. This identifier MAY be lower than the stream limit
identified by a QUIC MAX_STREAM_ID frame, and MAY be zero if no identified by a QUIC MAX_STREAM_ID frame, and MAY be zero if no
requests were processed. Servers SHOULD NOT increase the requests were processed. Servers SHOULD NOT increase the
skipping to change at page 21, line 17 skipping to change at page 21, line 38
losing requests. losing requests.
Once all requests on streams at or below the identified stream number Once all requests on streams at or below the identified stream number
have been completed or cancelled, and all promised server push have been completed or cancelled, and all promised server push
responses associated with those requests have been completed or responses associated with those requests have been completed or
cancelled, the connection can be closed using an Immediate Close (see cancelled, the connection can be closed using an Immediate Close (see
[QUIC-TRANSPORT]). An endpoint that completes a graceful shutdown [QUIC-TRANSPORT]). An endpoint that completes a graceful shutdown
SHOULD use the QUIC APPLICATION_CLOSE frame with the HTTP_NO_ERROR SHOULD use the QUIC APPLICATION_CLOSE frame with the HTTP_NO_ERROR
code. code.
5.2.8. MAX_PUSH_ID 4.2.8. MAX_PUSH_ID
The MAX_PUSH_ID frame (type=0xD) is used by clients to control the The MAX_PUSH_ID frame (type=0xD) is used by clients to control the
number of server pushes that the server can initiate. This sets the number of server pushes that the server can initiate. This sets the
maximum value for a Push ID that the server can use in a PUSH_PROMISE maximum value for a Push ID that the server can use in a PUSH_PROMISE
frame. Consequently, this also limits the number of push streams frame. Consequently, this also limits the number of push streams
that the server can initiate in addition to the limit set by the QUIC that the server can initiate in addition to the limit set by the QUIC
MAX_STREAM_ID frame. MAX_STREAM_ID frame.
The MAX_PUSH_ID frame is always sent on a control stream. Receipt of The MAX_PUSH_ID frame is always sent on a control stream. Receipt of
a MAX_PUSH_ID frame on any other stream MUST be treated as a a MAX_PUSH_ID frame on any other stream MUST be treated as a
connection error of type HTTP_WRONG_STREAM. connection error of type HTTP_WRONG_STREAM.
A server MUST NOT send a MAX_PUSH_ID frame. A client MUST treat the A server MUST NOT send a MAX_PUSH_ID frame. A client MUST treat the
receipt of a MAX_PUSH_ID frame as a connection error of type receipt of a MAX_PUSH_ID frame as a connection error of type
HTTP_MALFORMED_MAX_PUSH_ID. HTTP_MALFORMED_FRAME.
The maximum Push ID is unset when a connection is created, meaning The maximum Push ID is unset when a connection is created, meaning
that a server cannot push until it receives a MAX_PUSH_ID frame. A that a server cannot push until it receives a MAX_PUSH_ID frame. A
client that wishes to manage the number of promised server pushes can client that wishes to manage the number of promised server pushes can
increase the maximum Push ID by sending a MAX_PUSH_ID frame as the increase the maximum Push ID by sending a MAX_PUSH_ID frame as the
server fulfills or cancels server pushes. server fulfills or cancels server pushes.
The MAX_PUSH_ID frame has no defined flags. The MAX_PUSH_ID frame has no defined flags.
The MAX_PUSH_ID frame carries a single variable-length integer that The MAX_PUSH_ID frame carries a single variable-length integer that
identifies the maximum value for a Push ID that the server can use identifies the maximum value for a Push ID that the server can use
(see Section 5.2.6). A MAX_PUSH_ID frame cannot reduce the maximum (see Section 4.2.6). A MAX_PUSH_ID frame cannot reduce the maximum
Push ID; receipt of a MAX_PUSH_ID that contains a smaller value than Push ID; receipt of a MAX_PUSH_ID that contains a smaller value than
previously received MUST be treated as a connection error of type previously received MUST be treated as a connection error of type
HTTP_MALFORMED_MAX_PUSH_ID. HTTP_MALFORMED_FRAME.
A server MUST treat a MAX_PUSH_ID frame payload that does not contain A server MUST treat a MAX_PUSH_ID frame payload that does not contain
a single variable-length integer as a connection error of type a single variable-length integer as a connection error of type
HTTP_MALFORMED_MAX_PUSH_ID. HTTP_MALFORMED_FRAME.
6. Connection Management 5. Connection Management
QUIC connections are persistent. All of the considerations in QUIC connections are persistent. All of the considerations in
Section 9.1 of [RFC7540] apply to the management of QUIC connections. Section 9.1 of [RFC7540] apply to the management of QUIC connections.
HTTP clients are expected to use QUIC PING frames to keep connections HTTP clients are expected to use QUIC PING frames to keep connections
open. Servers SHOULD NOT use PING frames to keep a connection open. open. Servers SHOULD NOT use PING frames to keep a connection open.
A client SHOULD NOT use PING frames for this purpose unless there are A client SHOULD NOT use PING frames for this purpose unless there are
responses outstanding for requests or server pushes. If the client responses outstanding for requests or server pushes. If the client
is not expecting a response from the server, allowing an idle is not expecting a response from the server, allowing an idle
connection to time out (based on the idle_timeout transport connection to time out (based on the idle_timeout transport
parameter) is preferred over expending effort maintaining a parameter) is preferred over expending effort maintaining a
connection that might not be needed. A gateway MAY use PING to connection that might not be needed. A gateway MAY use PING to
maintain connections in anticipation of need rather than incur the maintain connections in anticipation of need rather than incur the
latency cost of connection establishment to servers. latency cost of connection establishment to servers.
7. Error Handling 6. Error Handling
QUIC allows the application to abruptly terminate (reset) individual QUIC allows the application to abruptly terminate (reset) individual
streams or the entire connection when an error is encountered. These streams or the entire connection when an error is encountered. These
are referred to as "stream errors" or "connection errors" and are are referred to as "stream errors" or "connection errors" and are
described in more detail in [QUIC-TRANSPORT]. described in more detail in [QUIC-TRANSPORT].
This section describes HTTP-specific error codes which can be used to This section describes HTTP-specific error codes which can be used to
express the cause of a connection or stream error. express the cause of a connection or stream error.
7.1. HTTP/QUIC Error Codes 6.1. HTTP/QUIC Error Codes
The following error codes are defined for use in QUIC RST_STREAM, The following error codes are defined for use in QUIC RST_STREAM,
STOP_SENDING, and CONNECTION_CLOSE frames when using HTTP/QUIC. STOP_SENDING, and CONNECTION_CLOSE frames when using HTTP/QUIC.
STOPPING (0x00): This value is reserved by the transport to be used STOPPING (0x00): This value is reserved by the transport to be used
in response to QUIC STOP_SENDING frames. in response to QUIC STOP_SENDING frames.
HTTP_NO_ERROR (0x01): No error. This is used when the connection or HTTP_NO_ERROR (0x01): No error. This is used when the connection or
stream needs to be closed, but there is no error to signal. stream needs to be closed, but there is no error to signal.
skipping to change at page 23, line 17 skipping to change at page 23, line 40
HTTP_CONNECT_ERROR (0x07): The connection established in response to HTTP_CONNECT_ERROR (0x07): The connection established in response to
a CONNECT request was reset or abnormally closed. a CONNECT request was reset or abnormally closed.
HTTP_EXCESSIVE_LOAD (0x08): The endpoint detected that its peer is HTTP_EXCESSIVE_LOAD (0x08): The endpoint detected that its peer is
exhibiting a behavior that might be generating excessive load. exhibiting a behavior that might be generating excessive load.
HTTP_VERSION_FALLBACK (0x09): The requested operation cannot be HTTP_VERSION_FALLBACK (0x09): The requested operation cannot be
served over HTTP/QUIC. The peer should retry over HTTP/2. served over HTTP/QUIC. The peer should retry over HTTP/2.
HTTP_MALFORMED_HEADERS (0x0A): A HEADERS frame has been received HTTP_WRONG_STREAM (0x0A): A frame was received on stream where it is
with an invalid format.
HTTP_MALFORMED_PRIORITY (0x0B): A PRIORITY frame has been received
with an invalid format.
HTTP_MALFORMED_SETTINGS (0x0C): A SETTINGS frame has been received
with an invalid format.
HTTP_MALFORMED_PUSH_PROMISE (0x0D): A PUSH_PROMISE frame has been
received with an invalid format.
HTTP_MALFORMED_DATA (0x0E): A DATA frame has been received with an
invalid format.
HTTP_INTERRUPTED_HEADERS (0x0F): A HEADERS frame without the End
Header Block flag was followed by a frame other than HEADERS.
HTTP_WRONG_STREAM (0x10): A frame was received on stream where it is
not permitted. not permitted.
HTTP_MULTIPLE_SETTINGS (0x11): More than one SETTINGS frame was HTTP_PUSH_LIMIT_EXCEEDED (0x0B): A Push ID greater than the current
received. maximum Push ID was referenced.
HTTP_MALFORMED_PUSH (0x12): A push stream header was malformed or
included an invalid Push ID.
HTTP_MALFORMED_MAX_PUSH_ID (0x13): A MAX_PUSH_ID frame has been
received with an invalid format.
HTTP_UNEXPECTED_GOAWAY (0x14): A GOAWAY frame has been received by a HTTP_DUPLICATE_PUSH (0x0C): A Push ID was referenced in two
server. different stream headers.
HTTP_MALFORMED_GOAWAY (0x15): A GOAWAY frame was malformed or HTTP_MALFORMED_FRAME (0x01XX): An error in a specific frame type.
contained an invalid Stream ID. The frame type is included as the last octet of the error code.
For example, an error in a MAX_PUSH_ID frame would be indicated
with the code (0x10D).
8. Considerations for Transitioning from HTTP/2 7. Considerations for Transitioning from HTTP/2
HTTP/QUIC is strongly informed by HTTP/2, and bears many HTTP/QUIC is strongly informed by HTTP/2, and bears many
similarities. This section describes the approach taken to design similarities. This section describes the approach taken to design
HTTP/QUIC, points out important differences from HTTP/2, and HTTP/QUIC, points out important differences from HTTP/2, and
describes how to map HTTP/2 extensions into HTTP/QUIC. describes how to map HTTP/2 extensions into HTTP/QUIC.
HTTP/QUIC begins from the premise that HTTP/2 code reuse is a useful HTTP/QUIC begins from the premise that HTTP/2 code reuse is a useful
feature, but not a hard requirement. HTTP/QUIC departs from HTTP/2 feature, but not a hard requirement. HTTP/QUIC departs from HTTP/2
primarily where necessary to accommodate the differences in behavior primarily where necessary to accommodate the differences in behavior
between QUIC and TCP (lack of ordering, support for streams). We between QUIC and TCP (lack of ordering, support for streams). We
intend to avoid gratuitous changes which make it difficult or intend to avoid gratuitous changes which make it difficult or
impossible to build extensions with the same semantics applicable to impossible to build extensions with the same semantics applicable to
both protocols at once. both protocols at once.
These departures are noted in this section. These departures are noted in this section.
8.1. Streams 7.1. Streams
HTTP/QUIC permits use of a larger number of streams (2^62-1) then HTTP/QUIC permits use of a larger number of streams (2^62-1) than
HTTP/2. The considerations about exhaustion of stream identifier HTTP/2. The considerations about exhaustion of stream identifier
space apply, though the space is significantly larger such that it is space apply, though the space is significantly larger such that it is
likely that other limits in QUIC are reached first, such as the limit likely that other limits in QUIC are reached first, such as the limit
on the connection flow control window. on the connection flow control window.
8.2. HTTP Frame Types 7.2. HTTP Frame Types
Many framing concepts from HTTP/2 can be elided away on QUIC, because Many framing concepts from HTTP/2 can be elided away on QUIC, because
the transport deals with them. Because frames are already on a the transport deals with them. Because frames are already on a
stream, they can omit the stream number. Because frames do not block stream, they can omit the stream number. Because frames do not block
multiplexing (QUIC's multiplexing occurs below this layer), the multiplexing (QUIC's multiplexing occurs below this layer), the
support for variable-maximum-length packets can be removed. Because support for variable-maximum-length packets can be removed. Because
stream termination is handled by QUIC, an END_STREAM flag is not stream termination is handled by QUIC, an END_STREAM flag is not
required. required.
Frame payloads are largely drawn from [RFC7540]. However, QUIC Frame payloads are largely drawn from [RFC7540]. However, QUIC
skipping to change at page 25, line 21 skipping to change at page 25, line 21
must apply them in the same order to ensure that both sides have a must apply them in the same order to ensure that both sides have a
consistent view of the stream dependency tree. HTTP/2 specifies consistent view of the stream dependency tree. HTTP/2 specifies
priority assignments in PRIORITY frames and (optionally) in HEADERS priority assignments in PRIORITY frames and (optionally) in HEADERS
frames. To achieve in-order delivery of priority changes in HTTP/ frames. To achieve in-order delivery of priority changes in HTTP/
QUIC, PRIORITY frames are sent on the control stream and the PRIORITY QUIC, PRIORITY frames are sent on the control stream and the PRIORITY
section is removed from the HEADERS frame. section is removed from the HEADERS frame.
Frame type definitions in HTTP/QUIC often use the QUIC variable- Frame type definitions in HTTP/QUIC often use the QUIC variable-
length integer encoding. In particular, Stream IDs use this length integer encoding. In particular, Stream IDs use this
encoding, which allow for a larger range of possible values than the encoding, which allow for a larger range of possible values than the
encoding used in HTTP/2. Redefinition of the encoding of extension encoding used in HTTP/2. Some frames in HTTP/QUIC use an identifier
frame types might be necessary if the encoding includes a Stream ID. rather than a Stream ID (e.g. Push IDs in PRIORITY frames).
Redefinition of the encoding of extension frame types might be
necessary if the encoding includes a Stream ID.
Other than this issue, frame type HTTP/2 extensions are typically Other than this issue, frame type HTTP/2 extensions are typically
portable to QUIC simply by replacing Stream 0 in HTTP/2 with Stream 2 portable to QUIC simply by replacing Stream 0 in HTTP/2 with Stream 2
or 3 in HTTP/QUIC. HTTP/QUIC extensions will not assume ordering, or 3 in HTTP/QUIC. HTTP/QUIC extensions will not assume ordering,
but would not be harmed by ordering, and would be portable to HTTP/2 but would not be harmed by ordering, and would be portable to HTTP/2
in the same manner. in the same manner.
Below is a listing of how each HTTP/2 frame type is mapped: Below is a listing of how each HTTP/2 frame type is mapped:
DATA (0x0): Padding is not defined in HTTP/QUIC frames. See DATA (0x0): Padding is not defined in HTTP/QUIC frames. See
Section 5.2.1. Section 4.2.1.
HEADERS (0x1): As described above, the PRIORITY region of HEADERS is HEADERS (0x1): As described above, the PRIORITY region of HEADERS is
not supported. A separate PRIORITY frame MUST be used. Padding not supported. A separate PRIORITY frame MUST be used. Padding
is not defined in HTTP/QUIC frames. See Section 5.2.2. is not defined in HTTP/QUIC frames. See Section 4.2.2.
PRIORITY (0x2): As described above, the PRIORITY frame is sent on PRIORITY (0x2): As described above, the PRIORITY frame is sent on
the control stream. See Section 5.2.3. the control stream and can reference either a Stream ID or a Push
ID. See Section 4.2.3.
RST_STREAM (0x3): RST_STREAM frames do not exist, since QUIC RST_STREAM (0x3): RST_STREAM frames do not exist, since QUIC
provides stream lifecycle management. The same code point is used provides stream lifecycle management. The same code point is used
for the CANCEL_PUSH frame (Section 5.2.4). for the CANCEL_PUSH frame (Section 4.2.4).
SETTINGS (0x4): SETTINGS frames are sent only at the beginning of SETTINGS (0x4): SETTINGS frames are sent only at the beginning of
the connection. See Section 5.2.5 and Section 8.3. the connection. See Section 4.2.5 and Section 7.3.
PUSH_PROMISE (0x5): The PUSH_PROMISE does not reference a stream; PUSH_PROMISE (0x5): The PUSH_PROMISE does not reference a stream;
instead the push stream references the PUSH_PROMISE frame using a instead the push stream references the PUSH_PROMISE frame using a
Push ID. See Section 5.2.6. Push ID. See Section 4.2.6.
PING (0x6): PING frames do not exist, since QUIC provides equivalent PING (0x6): PING frames do not exist, since QUIC provides equivalent
functionality. functionality.
GOAWAY (0x7): GOAWAY is sent only from server to client and does not GOAWAY (0x7): GOAWAY is sent only from server to client and does not
contain an error code. See Section 5.2.7. contain an error code. See Section 4.2.7.
WINDOW_UPDATE (0x8): WINDOW_UPDATE frames do not exist, since QUIC WINDOW_UPDATE (0x8): WINDOW_UPDATE frames do not exist, since QUIC
provides flow control. provides flow control.
CONTINUATION (0x9): CONTINUATION frames do not exist; instead, CONTINUATION (0x9): CONTINUATION frames do not exist; instead,
larger HEADERS/PUSH_PROMISE frames than HTTP/2 are permitted, and larger HEADERS/PUSH_PROMISE frames than HTTP/2 are permitted, and
HEADERS frames can be used in series. HEADERS frames can be used in series.
Frame types defined by extensions to HTTP/2 need to be separately Frame types defined by extensions to HTTP/2 need to be separately
registered for HTTP/QUIC if still applicable. The IDs of frames registered for HTTP/QUIC if still applicable. The IDs of frames
defined in [RFC7540] have been reserved for simplicity. See defined in [RFC7540] have been reserved for simplicity. See
Section 10.3. Section 9.3.
8.3. HTTP/2 SETTINGS Parameters 7.3. HTTP/2 SETTINGS Parameters
An important difference from HTTP/2 is that settings are sent once, An important difference from HTTP/2 is that settings are sent once,
at the beginning of the connection, and thereafter cannot change. at the beginning of the connection, and thereafter cannot change.
This eliminates many corner cases around synchronization of changes. This eliminates many corner cases around synchronization of changes.
Some transport-level options that HTTP/2 specifies via the SETTINGS Some transport-level options that HTTP/2 specifies via the SETTINGS
frame are superseded by QUIC transport parameters in HTTP/QUIC. The frame are superseded by QUIC transport parameters in HTTP/QUIC. The
HTTP-level options that are retained in HTTP/QUIC have the same value HTTP-level options that are retained in HTTP/QUIC have the same value
as in HTTP/2. as in HTTP/2.
Below is a listing of how each HTTP/2 SETTINGS parameter is mapped: Below is a listing of how each HTTP/2 SETTINGS parameter is mapped:
SETTINGS_HEADER_TABLE_SIZE: See Section 5.2.5.2. SETTINGS_HEADER_TABLE_SIZE: See Section 4.2.5.2.
SETTINGS_ENABLE_PUSH: This is removed in favor of the MAX_PUSH_ID SETTINGS_ENABLE_PUSH: This is removed in favor of the MAX_PUSH_ID
which provides a more granular control over server push. which provides a more granular control over server push.
SETTINGS_MAX_CONCURRENT_STREAMS: QUIC controls the largest open SETTINGS_MAX_CONCURRENT_STREAMS: QUIC controls the largest open
Stream ID as part of its flow control logic. Specifying Stream ID as part of its flow control logic. Specifying
SETTINGS_MAX_CONCURRENT_STREAMS in the SETTINGS frame is an error. SETTINGS_MAX_CONCURRENT_STREAMS in the SETTINGS frame is an error.
SETTINGS_INITIAL_WINDOW_SIZE: QUIC requires both stream and SETTINGS_INITIAL_WINDOW_SIZE: QUIC requires both stream and
connection flow control window sizes to be specified in the connection flow control window sizes to be specified in the
initial transport handshake. Specifying initial transport handshake. Specifying
SETTINGS_INITIAL_WINDOW_SIZE in the SETTINGS frame is an error. SETTINGS_INITIAL_WINDOW_SIZE in the SETTINGS frame is an error.
SETTINGS_MAX_FRAME_SIZE: This setting has no equivalent in HTTP/ SETTINGS_MAX_FRAME_SIZE: This setting has no equivalent in HTTP/
QUIC. Specifying it in the SETTINGS frame is an error. QUIC. Specifying it in the SETTINGS frame is an error.
SETTINGS_MAX_HEADER_LIST_SIZE: See Section 5.2.5.2. SETTINGS_MAX_HEADER_LIST_SIZE: See Section 4.2.5.2.
Settings need to be defined separately for HTTP/2 and HTTP/QUIC. The Settings need to be defined separately for HTTP/2 and HTTP/QUIC. The
IDs of settings defined in [RFC7540] have been reserved for IDs of settings defined in [RFC7540] have been reserved for
simplicity. See Section 10.4. simplicity. See Section 9.4.
8.4. HTTP/2 Error Codes 7.4. HTTP/2 Error Codes
QUIC has the same concepts of "stream" and "connection" errors that QUIC has the same concepts of "stream" and "connection" errors that
HTTP/2 provides. However, because the error code space is shared HTTP/2 provides. However, because the error code space is shared
between multiple components, there is no direct portability of HTTP/2 between multiple components, there is no direct portability of HTTP/2
error codes. error codes.
The HTTP/2 error codes defined in Section 7 of [RFC7540] map to the The HTTP/2 error codes defined in Section 7 of [RFC7540] map to the
HTTP over QUIC error codes as follows: HTTP over QUIC error codes as follows:
NO_ERROR (0x0): HTTP_NO_ERROR in Section 7.1. NO_ERROR (0x0): HTTP_NO_ERROR in Section 6.1.
PROTOCOL_ERROR (0x1): No single mapping. See new HTTP_MALFORMED_* PROTOCOL_ERROR (0x1): No single mapping. See new
error codes defined in Section 7.1. HTTP_MALFORMED_FRAME error codes defined in Section 6.1.
INTERNAL_ERROR (0x2): HTTP_INTERNAL_ERROR in Section 7.1. INTERNAL_ERROR (0x2): HTTP_INTERNAL_ERROR in Section 6.1.
FLOW_CONTROL_ERROR (0x3): Not applicable, since QUIC handles flow FLOW_CONTROL_ERROR (0x3): Not applicable, since QUIC handles flow
control. Would provoke a QUIC_FLOW_CONTROL_RECEIVED_TOO_MUCH_DATA control. Would provoke a QUIC_FLOW_CONTROL_RECEIVED_TOO_MUCH_DATA
from the QUIC layer. from the QUIC layer.
SETTINGS_TIMEOUT (0x4): Not applicable, since no acknowledgement of SETTINGS_TIMEOUT (0x4): Not applicable, since no acknowledgement of
SETTINGS is defined. SETTINGS is defined.
STREAM_CLOSED (0x5): Not applicable, since QUIC handles stream STREAM_CLOSED (0x5): Not applicable, since QUIC handles stream
management. Would provoke a QUIC_STREAM_DATA_AFTER_TERMINATION management. Would provoke a QUIC_STREAM_DATA_AFTER_TERMINATION
from the QUIC layer. from the QUIC layer.
FRAME_SIZE_ERROR (0x6) No single mapping. See new error codes FRAME_SIZE_ERROR (0x6) No single mapping. See new error codes
defined in Section 7.1. defined in Section 6.1.
REFUSED_STREAM (0x7): Not applicable, since QUIC handles stream REFUSED_STREAM (0x7): Not applicable, since QUIC handles stream
management. Would provoke a QUIC_TOO_MANY_OPEN_STREAMS from the management. Would provoke a QUIC_TOO_MANY_OPEN_STREAMS from the
QUIC layer. QUIC layer.
CANCEL (0x8): HTTP_REQUEST_CANCELLED in Section 7.1. CANCEL (0x8): HTTP_REQUEST_CANCELLED in Section 6.1.
COMPRESSION_ERROR (0x9): HTTP_HPACK_DECOMPRESSION_FAILED in COMPRESSION_ERROR (0x9): HTTP_HPACK_DECOMPRESSION_FAILED in
Section 7.1. Section 6.1.
CONNECT_ERROR (0xa): HTTP_CONNECT_ERROR in Section 7.1. CONNECT_ERROR (0xa): HTTP_CONNECT_ERROR in Section 6.1.
ENHANCE_YOUR_CALM (0xb): HTTP_EXCESSIVE_LOAD in Section 7.1. ENHANCE_YOUR_CALM (0xb): HTTP_EXCESSIVE_LOAD in Section 6.1.
INADEQUATE_SECURITY (0xc): Not applicable, since QUIC is assumed to INADEQUATE_SECURITY (0xc): Not applicable, since QUIC is assumed to
provide sufficient security on all connections. provide sufficient security on all connections.
HTTP_1_1_REQUIRED (0xd): HTTP_VERSION_FALLBACK in Section 7.1. HTTP_1_1_REQUIRED (0xd): HTTP_VERSION_FALLBACK in Section 6.1.
Error codes need to be defined for HTTP/2 and HTTP/QUIC separately. Error codes need to be defined for HTTP/2 and HTTP/QUIC separately.
See Section 10.5. See Section 9.5.
9. Security Considerations 8. Security Considerations
The security considerations of HTTP over QUIC should be comparable to The security considerations of HTTP over QUIC should be comparable to
those of HTTP/2. those of HTTP/2.
The modified SETTINGS format contains nested length elements, which The modified SETTINGS format contains nested length elements, which
could pose a security risk to an uncautious implementer. A SETTINGS could pose a security risk to an uncautious implementer. A SETTINGS
frame parser MUST ensure that the length of the frame exactly matches frame parser MUST ensure that the length of the frame exactly matches
the length of the settings it contains. the length of the settings it contains.
10. IANA Considerations 9. IANA Considerations
10.1. Registration of HTTP/QUIC Identification String 9.1. Registration of HTTP/QUIC Identification String
This document creates a new registration for the identification of This document creates a new registration for the identification of
HTTP/QUIC in the "Application Layer Protocol Negotiation (ALPN) HTTP/QUIC in the "Application Layer Protocol Negotiation (ALPN)
Protocol IDs" registry established in [RFC7301]. Protocol IDs" registry established in [RFC7301].
The "hq" string identifies HTTP/QUIC: The "hq" string identifies HTTP/QUIC:
Protocol: HTTP over QUIC Protocol: HTTP over QUIC
Identification Sequence: 0x68 0x71 ("hq") Identification Sequence: 0x68 0x71 ("hq")
Specification: This document Specification: This document
10.2. Registration of QUIC Version Hint Alt-Svc Parameter 9.2. Registration of QUIC Version Hint Alt-Svc Parameter
This document creates a new registration for version-negotiation This document creates a new registration for version-negotiation
hints in the "Hypertext Transfer Protocol (HTTP) Alt-Svc Parameter" hints in the "Hypertext Transfer Protocol (HTTP) Alt-Svc Parameter"
registry established in [RFC7838]. registry established in [RFC7838].
Parameter: "quic" Parameter: "quic"
Specification: This document, Section 2.1 Specification: This document, Section 2.1.1
10.3. Frame Types 9.3. Frame Types
This document establishes a registry for HTTP/QUIC frame type codes. This document establishes a registry for HTTP/QUIC frame type codes.
The "HTTP/QUIC Frame Type" registry manages an 8-bit space. The The "HTTP/QUIC Frame Type" registry manages an 8-bit space. The
"HTTP/QUIC Frame Type" registry operates under either of the "IETF "HTTP/QUIC Frame Type" registry operates under either of the "IETF
Review" or "IESG Approval" policies [RFC8126] for values between 0x00 Review" or "IESG Approval" policies [RFC8126] for values between 0x00
and 0xef, with values between 0xf0 and 0xff being reserved for and 0xef, with values between 0xf0 and 0xff being reserved for
Experimental Use. Experimental Use.
While this registry is separate from the "HTTP/2 Frame Type" registry While this registry is separate from the "HTTP/2 Frame Type" registry
defined in [RFC7540], it is preferable that the assignments parallel defined in [RFC7540], it is preferable that the assignments parallel
skipping to change at page 30, line 8 skipping to change at page 30, line 8
Specification: A reference to a specification that includes a Specification: A reference to a specification that includes a
description of the frame layout, its semantics, and flags that the description of the frame layout, its semantics, and flags that the
frame type uses, including any parts of the frame that are frame type uses, including any parts of the frame that are
conditionally present based on the value of flags. conditionally present based on the value of flags.
The entries in the following table are registered by this document. The entries in the following table are registered by this document.
+--------------+------+---------------+ +--------------+------+---------------+
| Frame Type | Code | Specification | | Frame Type | Code | Specification |
+--------------+------+---------------+ +--------------+------+---------------+
| DATA | 0x0 | Section 5.2.1 | | DATA | 0x0 | Section 4.2.1 |
| | | | | | | |
| HEADERS | 0x1 | Section 5.2.2 | | HEADERS | 0x1 | Section 4.2.2 |
| | | | | | | |
| PRIORITY | 0x2 | Section 5.2.3 | | PRIORITY | 0x2 | Section 4.2.3 |
| | | | | | | |
| CANCEL_PUSH | 0x3 | Section 5.2.4 | | CANCEL_PUSH | 0x3 | Section 4.2.4 |
| | | | | | | |
| SETTINGS | 0x4 | Section 5.2.5 | | SETTINGS | 0x4 | Section 4.2.5 |
| | | | | | | |
| PUSH_PROMISE | 0x5 | Section 5.2.6 | | PUSH_PROMISE | 0x5 | Section 4.2.6 |
| | | | | | | |
| Reserved | 0x6 | N/A | | Reserved | 0x6 | N/A |
| | | | | | | |
| GOAWAY | 0x7 | Section 5.2.7 | | GOAWAY | 0x7 | Section 4.2.7 |
| | | | | | | |
| Reserved | 0x8 | N/A | | Reserved | 0x8 | N/A |
| | | | | | | |
| Reserved | 0x9 | N/A | | Reserved | 0x9 | N/A |
| | | | | | | |
| MAX_PUSH_ID | 0xD | Section 5.2.8 | | MAX_PUSH_ID | 0xD | Section 4.2.8 |
+--------------+------+---------------+ +--------------+------+---------------+
10.4. Settings Parameters 9.4. Settings Parameters
This document establishes a registry for HTTP/QUIC settings. The This document establishes a registry for HTTP/QUIC settings. The
"HTTP/QUIC Settings" registry manages a 16-bit space. The "HTTP/QUIC "HTTP/QUIC Settings" registry manages a 16-bit space. The "HTTP/QUIC
Settings" registry operates under the "Expert Review" policy Settings" registry operates under the "Expert Review" policy
[RFC8126] for values in the range from 0x0000 to 0xefff, with values [RFC8126] for values in the range from 0x0000 to 0xefff, with values
between and 0xf000 and 0xffff being reserved for Experimental Use. between and 0xf000 and 0xffff being reserved for Experimental Use.
The designated experts are the same as those for the "HTTP/2 The designated experts are the same as those for the "HTTP/2
Settings" registry defined in [RFC7540]. Settings" registry defined in [RFC7540].
While this registry is separate from the "HTTP/2 Settings" registry While this registry is separate from the "HTTP/2 Settings" registry
skipping to change at page 31, line 13 skipping to change at page 31, line 13
Code: The 16-bit code assigned to the setting. Code: The 16-bit code assigned to the setting.
Specification: An optional reference to a specification that Specification: An optional reference to a specification that
describes the use of the setting. describes the use of the setting.
The entries in the following table are registered by this document. The entries in the following table are registered by this document.
+----------------------+------+-----------------+ +----------------------+------+-----------------+
| Setting Name | Code | Specification | | Setting Name | Code | Specification |
+----------------------+------+-----------------+ +----------------------+------+-----------------+
| HEADER_TABLE_SIZE | 0x1 | Section 5.2.5.2 | | HEADER_TABLE_SIZE | 0x1 | Section 4.2.5.2 |
| | | | | | | |
| Reserved | 0x2 | N/A | | Reserved | 0x2 | N/A |
| | | | | | | |
| Reserved | 0x3 | N/A | | Reserved | 0x3 | N/A |
| | | | | | | |
| Reserved | 0x4 | N/A | | Reserved | 0x4 | N/A |
| | | | | | | |
| Reserved | 0x5 | N/A | | Reserved | 0x5 | N/A |
| | | | | | | |
| MAX_HEADER_LIST_SIZE | 0x6 | Section 5.2.5.2 | | MAX_HEADER_LIST_SIZE | 0x6 | Section 4.2.5.2 |
+----------------------+------+-----------------+ +----------------------+------+-----------------+
10.5. Error Codes 9.5. Error Codes
This document establishes a registry for HTTP/QUIC error codes. The This document establishes a registry for HTTP/QUIC error codes. The
"HTTP/QUIC Error Code" registry manages a 16-bit space. The "HTTP/ "HTTP/QUIC Error Code" registry manages a 16-bit space. The "HTTP/
QUIC Error Code" registry operates under the "Expert Review" policy QUIC Error Code" registry operates under the "Expert Review" policy
[RFC8126]. [RFC8126].
Registrations for error codes are required to include a description Registrations for error codes are required to include a description
of the error code. An expert reviewer is advised to examine new of the error code. An expert reviewer is advised to examine new
registrations for possible duplication with existing error codes. registrations for possible duplication with existing error codes.
Use of existing registrations is to be encouraged, but not mandated. Use of existing registrations is to be encouraged, but not mandated.
skipping to change at page 32, line 5 skipping to change at page 32, line 5
Code: The 16-bit error code value. Code: The 16-bit error code value.
Description: A brief description of the error code semantics, longer Description: A brief description of the error code semantics, longer
if no detailed specification is provided. if no detailed specification is provided.
Specification: An optional reference for a specification that Specification: An optional reference for a specification that
defines the error code. defines the error code.
The entries in the following table are registered by this document. The entries in the following table are registered by this document.
+-----------------------------+-----+-------------+-----------------+ +----------------------------+--------+------------+----------------+
| Name | Cod | Description | Specification | | Name | Code | Descriptio | Specification |
| | e | | | | | | n | |
+-----------------------------+-----+-------------+-----------------+ +----------------------------+--------+------------+----------------+
| STOPPING | 0x0 | Reserved by | [QUIC-TRANSPORT | | STOPPING | 0x0000 | Reserved | [QUIC-TRANSPOR |
| | 0 | QUIC | ] | | | | by QUIC | T] |
| | | | | | | | | |
| HTTP_NO_ERROR | 0x0 | No error | Section 7.1 | | HTTP_NO_ERROR | 0x0001 | No error | Section 6.1 |
| | 1 | | | | | | | |
| | | | | | HTTP_PUSH_REFUSED | 0x0002 | Client | Section 6.1 |
| HTTP_PUSH_REFUSED | 0x0 | Client | Section 7.1 | | | | refused | |
| | 2 | refused | | | | | pushed | |
| | | pushed | | | | | content | |
| | | content | | | | | | |
| | | | | | HTTP_INTERNAL_ERROR | 0x0003 | Internal | Section 6.1 |
| HTTP_INTERNAL_ERROR | 0x0 | Internal | Section 7.1 | | | | error | |
| | 3 | error | | | | | | |
| | | | | | HTTP_PUSH_ALREADY_IN_CACHE | 0x0004 | Pushed | Section 6.1 |
| HTTP_PUSH_ALREADY_IN_CACHE | 0x0 | Pushed | Section 7.1 | | | | content | |
| | 4 | content | | | | | already | |
| | | already | | | | | cached | |
| | | cached | | | | | | |
| | | | | | HTTP_REQUEST_CANCELLED | 0x0005 | Data no | Section 6.1 |
| HTTP_REQUEST_CANCELLED | 0x0 | Data no | Section 7.1 | | | | longer | |
| | 5 | longer | | | | | needed | |
| | | needed | | | | | | |
| | | | | | HTTP_HPACK_DECOMPRESSION_F | 0x0006 | HPACK | Section 6.1 |
| HTTP_HPACK_DECOMPRESSION_FA | 0x0 | HPACK | Section 7.1 | | AILED | | cannot | |
| ILED | 6 | cannot | | | | | continue | |
| | | continue | | | | | | |
| | | | | | HTTP_CONNECT_ERROR | 0x0007 | TCP reset | Section 6.1 |
| HTTP_CONNECT_ERROR | 0x0 | TCP reset | Section 7.1 | | | | or error | |
| | 7 | or error on | | | | | on CONNECT | |
| | | CONNECT | | | | | request | |
| | | request | | | | | | |
| | | | | | HTTP_EXCESSIVE_LOAD | 0x0008 | Peer | Section 6.1 |
| HTTP_EXCESSIVE_LOAD | 0x0 | Peer | Section 7.1 | | | | generating | |
| | 8 | generating | | | | | excessive | |
| | | excessive | | | | | load | |
| | | load | | | | | | |
| | | | | | HTTP_VERSION_FALLBACK | 0x0009 | Retry over | Section 6.1 |
| HTTP_VERSION_FALLBACK | 0x0 | Retry over | Section 7.1 | | | | HTTP/2 | |
| | 9 | HTTP/2 | | | | | | |
| | | | | | HTTP_WRONG_STREAM | 0x000A | A frame | Section 6.1 |
| HTTP_MALFORMED_HEADERS | 0x0 | Invalid | Section 7.1 | | | | was sent | |
| | A | HEADERS | | | | | on the | |
| | | frame | | | | | wrong | |
| | | | | | | | stream | |
| HTTP_MALFORMED_PRIORITY | 0x0 | Invalid | Section 7.1 | | | | | |
| | B | PRIORITY | | | HTTP_PUSH_LIMIT_EXCEEDED | 0x000B | Maximum | Section 6.1 |
| | | frame | | | | | Push ID | |
| | | | | | | | exceeded | |
| HTTP_MALFORMED_SETTINGS | 0x0 | Invalid | Section 7.1 | | | | | |
| | C | SETTINGS | | | HTTP_DUPLICATE_PUSH | 0x000C | Push ID | Section 6.1 |
| | | frame | | | | | was | |
| | | | | | | | fulfilled | |
| HTTP_MALFORMED_PUSH_PROMISE | 0x0 | Invalid PUS | Section 7.1 | | | | multiple | |
| | D | H_PROMISE | | | | | times | |
| | | frame | | | | | | |
| | | | | | HTTP_MALFORMED_FRAME | 0x01XX | Error in | Section 6.1 |
| HTTP_MALFORMED_DATA | 0x0 | Invalid | Section 7.1 | | | | frame | |
| | E | DATA frame | | | | | formatting | |
| | | | | | | | or use | |
| HTTP_INTERRUPTED_HEADERS | 0x0 | Incomplete | Section 7.1 | +----------------------------+--------+------------+----------------+
| | F | HEADERS | |
| | | block | |
| | | | |
| HTTP_WRONG_STREAM | 0x1 | A frame was | Section 7.1 |
| | 0 | sent on the | |
| | | wrong | |
| | | stream | |
| | | | |
| HTTP_MULTIPLE_SETTINGS | 0x1 | Multiple | Section 7.1 |
| | 1 | SETTINGS | |
| | | frames | |
| | | | |
| HTTP_MALFORMED_PUSH | 0x1 | Invalid | Section 7.1 |
| | 2 | push stream | |
| | | header | |
| | | | |
| HTTP_MALFORMED_MAX_PUSH_ID | 0x1 | Invalid | Section 7.1 |
| | 3 | MAX_PUSH_ID | |
| | | frame | |
| | | | |
| HTTP_UNEXPECTED_GOAWAY | 0x1 | A server | Section 7.1 |
| | 4 | received | |
| | | GOAWAY | |
| | | | |
| HTTP_MALFORMED_GOAWAY | 0x1 | Invalid | Section 7.1 |
| | 5 | GOAWAY | |
| | | frame | |
+-----------------------------+-----+-------------+-----------------+
11. References 10. References
11.1. Normative References 10.1. Normative References
[QUIC-TRANSPORT] [QUIC-TRANSPORT]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", draft-ietf-quic- Multiplexed and Secure Transport", draft-ietf-quic-
transport-00 (work in progress), December 2017. transport-09 (work in progress), January 2018.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, DOI 10.17487/RFC0793, September 1981, RFC 793, DOI 10.17487/RFC0793, September 1981,
<https://www.rfc-editor.org/info/rfc793>. <https://www.rfc-editor.org/info/rfc793>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
[RFC6066] Eastlake 3rd, D., "Transport Layer Security (TLS)
Extensions: Extension Definitions", RFC 6066,
DOI 10.17487/RFC6066, January 2011,
<https://www.rfc-editor.org/info/rfc6066>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing", Protocol (HTTP/1.1): Message Syntax and Routing",
RFC 7230, DOI 10.17487/RFC7230, June 2014, RFC 7230, DOI 10.17487/RFC7230, June 2014,
<https://www.rfc-editor.org/info/rfc7230>. <https://www.rfc-editor.org/info/rfc7230>.
[RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Semantics and Content", RFC 7231, Protocol (HTTP/1.1): Semantics and Content", RFC 7231,
DOI 10.17487/RFC7231, June 2014, DOI 10.17487/RFC7231, June 2014,
<https://www.rfc-editor.org/info/rfc7231>. <https://www.rfc-editor.org/info/rfc7231>.
skipping to change at page 35, line 9 skipping to change at page 34, line 32
<https://www.rfc-editor.org/info/rfc7541>. <https://www.rfc-editor.org/info/rfc7541>.
[RFC7838] Nottingham, M., McManus, P., and J. Reschke, "HTTP [RFC7838] Nottingham, M., McManus, P., and J. Reschke, "HTTP
Alternative Services", RFC 7838, DOI 10.17487/RFC7838, Alternative Services", RFC 7838, DOI 10.17487/RFC7838,
April 2016, <https://www.rfc-editor.org/info/rfc7838>. April 2016, <https://www.rfc-editor.org/info/rfc7838>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
11.2. Informative References 10.2. Informative References
[RFC7301] Friedl, S., Popov, A., Langley, A., and E. Stephan, [RFC7301] Friedl, S., Popov, A., Langley, A., and E. Stephan,
"Transport Layer Security (TLS) Application-Layer Protocol "Transport Layer Security (TLS) Application-Layer Protocol
Negotiation Extension", RFC 7301, DOI 10.17487/RFC7301, Negotiation Extension", RFC 7301, DOI 10.17487/RFC7301,
July 2014, <https://www.rfc-editor.org/info/rfc7301>. July 2014, <https://www.rfc-editor.org/info/rfc7301>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
11.3. URIs 10.3. URIs
[1] https://mailarchive.ietf.org/arch/search/?email_list=quic [1] https://mailarchive.ietf.org/arch/search/?email_list=quic
[2] https://github.com/quicwg [2] https://github.com/quicwg
[3] https://github.com/quicwg/base-drafts/labels/-http [3] https://github.com/quicwg/base-drafts/labels/-http
Appendix A. Contributors Appendix A. Contributors
The original authors of this specification were Robbie Shade and Mike The original authors of this specification were Robbie Shade and Mike
Warres. Warres.
A substantial portion of Mike's contribution was supported by A substantial portion of Mike's contribution was supported by
Microsoft during his employment there. Microsoft during his employment there.
Appendix B. Change Log Appendix B. Change Log
*RFC Editor's Note:* Please remove this section prior to *RFC Editor's Note:* Please remove this section prior to
publication of a final version of this document. publication of a final version of this document.
B.1. Since draft-ietf-quic-http-07 B.1. Since draft-ietf-quic-http-08
o Clarified connection coalescing rules (#940, #1024)
B.2. Since draft-ietf-quic-http-07
o Changes for integer encodings in QUIC (#595,#905) o Changes for integer encodings in QUIC (#595,#905)
B.2. Since draft-ietf-quic-http-06 o Use unidirectional streams as appropriate (#515, #240, #281, #886)
o Improvement to the description of GOAWAY (#604, #898)
o Improve description of server push usage (#947, #950, #957)
B.3. Since draft-ietf-quic-http-06
o Track changes in QUIC error code usage (#485) o Track changes in QUIC error code usage (#485)
B.3. Since draft-ietf-quic-http-05 B.4. Since draft-ietf-quic-http-05
o Made push ID sequential, add MAX_PUSH_ID, remove o Made push ID sequential, add MAX_PUSH_ID, remove
SETTINGS_ENABLE_PUSH (#709) SETTINGS_ENABLE_PUSH (#709)
o Guidance about keep-alive and QUIC PINGs (#729) o Guidance about keep-alive and QUIC PINGs (#729)
o Expanded text on GOAWAY and cancellation (#757) o Expanded text on GOAWAY and cancellation (#757)
B.4. Since draft-ietf-quic-http-04 B.5. Since draft-ietf-quic-http-04
o Cite RFC 5234 (#404) o Cite RFC 5234 (#404)
o Return to a single stream per request (#245,#557) o Return to a single stream per request (#245,#557)
o Use separate frame type and settings registries from HTTP/2 (#81) o Use separate frame type and settings registries from HTTP/2 (#81)
o SETTINGS_ENABLE_PUSH instead of SETTINGS_DISABLE_PUSH (#477) o SETTINGS_ENABLE_PUSH instead of SETTINGS_DISABLE_PUSH (#477)
o Restored GOAWAY (#696) o Restored GOAWAY (#696)
o Identify server push using Push ID rather than a stream ID o Identify server push using Push ID rather than a stream ID
(#702,#281) (#702,#281)
o DATA frames cannot be empty (#700) o DATA frames cannot be empty (#700)
B.5. Since draft-ietf-quic-http-03 B.6. Since draft-ietf-quic-http-03
None. None.
B.6. Since draft-ietf-quic-http-02 B.7. Since draft-ietf-quic-http-02
o Track changes in transport draft o Track changes in transport draft
B.7. Since draft-ietf-quic-http-01 B.8. Since draft-ietf-quic-http-01
o SETTINGS changes (#181): o SETTINGS changes (#181):
* SETTINGS can be sent only once at the start of a connection; no * SETTINGS can be sent only once at the start of a connection; no
changes thereafter changes thereafter
* SETTINGS_ACK removed * SETTINGS_ACK removed
* Settings can only occur in the SETTINGS frame a single time * Settings can only occur in the SETTINGS frame a single time
skipping to change at page 37, line 18 skipping to change at page 36, line 47
o Closing the connection control stream or any message control o Closing the connection control stream or any message control
stream is a fatal error (#176) stream is a fatal error (#176)
o HPACK Sequence counter can wrap (#173) o HPACK Sequence counter can wrap (#173)
o 0-RTT guidance added o 0-RTT guidance added
o Guide to differences from HTTP/2 and porting HTTP/2 extensions o Guide to differences from HTTP/2 and porting HTTP/2 extensions
added (#127,#242) added (#127,#242)
B.8. Since draft-ietf-quic-http-00 B.9. Since draft-ietf-quic-http-00
o Changed "HTTP/2-over-QUIC" to "HTTP/QUIC" throughout (#11,#29) o Changed "HTTP/2-over-QUIC" to "HTTP/QUIC" throughout (#11,#29)
o Changed from using HTTP/2 framing within Stream 3 to new framing o Changed from using HTTP/2 framing within Stream 3 to new framing
format and two-stream-per-request model (#71,#72,#73) format and two-stream-per-request model (#71,#72,#73)
o Adopted SETTINGS format from draft-bishop-httpbis-extended- o Adopted SETTINGS format from draft-bishop-httpbis-extended-
settings-01 settings-01
o Reworked SETTINGS_ACK to account for indeterminate inter-stream o Reworked SETTINGS_ACK to account for indeterminate inter-stream
order (#75) order (#75)
o Described CONNECT pseudo-method (#95) o Described CONNECT pseudo-method (#95)
skipping to change at page 37, line 37 skipping to change at page 37, line 19
o Reworked SETTINGS_ACK to account for indeterminate inter-stream o Reworked SETTINGS_ACK to account for indeterminate inter-stream
order (#75) order (#75)
o Described CONNECT pseudo-method (#95) o Described CONNECT pseudo-method (#95)
o Updated ALPN token and Alt-Svc guidance (#13,#87) o Updated ALPN token and Alt-Svc guidance (#13,#87)
o Application-layer-defined error codes (#19,#74) o Application-layer-defined error codes (#19,#74)
B.9. Since draft-shade-quic-http2-mapping-00 B.10. Since draft-shade-quic-http2-mapping-00
o Adopted as base for draft-ietf-quic-http o Adopted as base for draft-ietf-quic-http
o Updated authors/editors list o Updated authors/editors list
Author's Address Author's Address
Mike Bishop (editor) Mike Bishop (editor)
Akamai Akamai
 End of changes. 160 change blocks. 
378 lines changed or deleted 367 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/