draft-ietf-quic-http-24.txt   draft-ietf-quic-http-latest.txt 
QUIC Working Group M. Bishop, Ed. QUIC Working Group M. Bishop, Ed.
Internet-Draft Akamai Internet-Draft Akamai
Intended status: Standards Track November 4, 2019 Intended status: Standards Track December 9, 2019
Expires: May 7, 2020 Expires: June 11, 2020
Hypertext Transfer Protocol Version 3 (HTTP/3) Hypertext Transfer Protocol Version 3 (HTTP/3)
draft-ietf-quic-http-24 draft-ietf-quic-http-latest
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 HTTP/3. how HTTP/2 extensions can be ported to HTTP/3.
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 May 7, 2020. This Internet-Draft will expire on June 11, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
skipping to change at page 3, line 25 skipping to change at page 3, line 25
8. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 34 8. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 34
8.1. HTTP/3 Error Codes . . . . . . . . . . . . . . . . . . . 34 8.1. HTTP/3 Error Codes . . . . . . . . . . . . . . . . . . . 34
9. Extensions to HTTP/3 . . . . . . . . . . . . . . . . . . . . 35 9. Extensions to HTTP/3 . . . . . . . . . . . . . . . . . . . . 35
10. Security Considerations . . . . . . . . . . . . . . . . . . . 36 10. Security Considerations . . . . . . . . . . . . . . . . . . . 36
10.1. Traffic Analysis . . . . . . . . . . . . . . . . . . . . 36 10.1. Traffic Analysis . . . . . . . . . . . . . . . . . . . . 36
10.2. Frame Parsing . . . . . . . . . . . . . . . . . . . . . 37 10.2. Frame Parsing . . . . . . . . . . . . . . . . . . . . . 37
10.3. Early Data . . . . . . . . . . . . . . . . . . . . . . . 37 10.3. Early Data . . . . . . . . . . . . . . . . . . . . . . . 37
10.4. Migration . . . . . . . . . . . . . . . . . . . . . . . 37 10.4. Migration . . . . . . . . . . . . . . . . . . . . . . . 37
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
11.1. Registration of HTTP/3 Identification String . . . . . . 37 11.1. Registration of HTTP/3 Identification String . . . . . . 37
11.2. Frame Types . . . . . . . . . . . . . . . . . . . . . . 37 11.2. New Registries . . . . . . . . . . . . . . . . . . . . . 38
11.3. Settings Parameters . . . . . . . . . . . . . . . . . . 39 11.2.1. Frame Types . . . . . . . . . . . . . . . . . . . . 38
11.4. Error Codes . . . . . . . . . . . . . . . . . . . . . . 40 11.2.2. Settings Parameters . . . . . . . . . . . . . . . . 39
11.5. Stream Types . . . . . . . . . . . . . . . . . . . . . . 42 11.2.3. Error Codes . . . . . . . . . . . . . . . . . . . . 40
11.2.4. Stream Types . . . . . . . . . . . . . . . . . . . . 42
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
12.1. Normative References . . . . . . . . . . . . . . . . . . 43 12.1. Normative References . . . . . . . . . . . . . . . . . . 43
12.2. Informative References . . . . . . . . . . . . . . . . . 45 12.2. Informative References . . . . . . . . . . . . . . . . . 45
12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 45 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Appendix A. Considerations for Transitioning from HTTP/2 . . . . 45 Appendix A. Considerations for Transitioning from HTTP/2 . . . . 45
A.1. Streams . . . . . . . . . . . . . . . . . . . . . . . . . 46 A.1. Streams . . . . . . . . . . . . . . . . . . . . . . . . . 46
A.2. HTTP Frame Types . . . . . . . . . . . . . . . . . . . . 46 A.2. HTTP Frame Types . . . . . . . . . . . . . . . . . . . . 46
A.2.1. Prioritization Differences . . . . . . . . . . . . . 47 A.2.1. Prioritization Differences . . . . . . . . . . . . . 47
A.2.2. Header Compression Differences . . . . . . . . . . . 47 A.2.2. Header Compression Differences . . . . . . . . . . . 47
A.2.3. Guidance for New Frame Type Definitions . . . . . . . 48 A.2.3. Guidance for New Frame Type Definitions . . . . . . . 47
A.2.4. Mapping Between HTTP/2 and HTTP/3 Frame Types . . . . 48 A.2.4. Mapping Between HTTP/2 and HTTP/3 Frame Types . . . . 48
A.3. HTTP/2 SETTINGS Parameters . . . . . . . . . . . . . . . 49 A.3. HTTP/2 SETTINGS Parameters . . . . . . . . . . . . . . . 49
A.4. HTTP/2 Error Codes . . . . . . . . . . . . . . . . . . . 50 A.4. HTTP/2 Error Codes . . . . . . . . . . . . . . . . . . . 50
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 51 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 51
B.1. Since draft-ietf-quic-http-23 . . . . . . . . . . . . . . 51 B.1. Since draft-ietf-quic-http-24 . . . . . . . . . . . . . . 51
B.2. Since draft-ietf-quic-http-22 . . . . . . . . . . . . . . 51 B.2. Since draft-ietf-quic-http-23 . . . . . . . . . . . . . . 51
B.3. Since draft-ietf-quic-http-21 . . . . . . . . . . . . . . 52 B.3. Since draft-ietf-quic-http-22 . . . . . . . . . . . . . . 51
B.4. Since draft-ietf-quic-http-20 . . . . . . . . . . . . . . 52 B.4. Since draft-ietf-quic-http-21 . . . . . . . . . . . . . . 52
B.5. Since draft-ietf-quic-http-19 . . . . . . . . . . . . . . 53 B.5. Since draft-ietf-quic-http-20 . . . . . . . . . . . . . . 52
B.6. Since draft-ietf-quic-http-18 . . . . . . . . . . . . . . 53 B.6. Since draft-ietf-quic-http-19 . . . . . . . . . . . . . . 53
B.7. Since draft-ietf-quic-http-17 . . . . . . . . . . . . . . 54 B.7. Since draft-ietf-quic-http-18 . . . . . . . . . . . . . . 53
B.8. Since draft-ietf-quic-http-16 . . . . . . . . . . . . . . 54 B.8. Since draft-ietf-quic-http-17 . . . . . . . . . . . . . . 54
B.9. Since draft-ietf-quic-http-15 . . . . . . . . . . . . . . 54 B.9. Since draft-ietf-quic-http-16 . . . . . . . . . . . . . . 54
B.10. Since draft-ietf-quic-http-14 . . . . . . . . . . . . . . 55 B.10. Since draft-ietf-quic-http-15 . . . . . . . . . . . . . . 54
B.11. Since draft-ietf-quic-http-13 . . . . . . . . . . . . . . 55 B.11. Since draft-ietf-quic-http-14 . . . . . . . . . . . . . . 55
B.12. Since draft-ietf-quic-http-12 . . . . . . . . . . . . . . 55 B.12. Since draft-ietf-quic-http-13 . . . . . . . . . . . . . . 55
B.13. Since draft-ietf-quic-http-11 . . . . . . . . . . . . . . 56 B.13. Since draft-ietf-quic-http-12 . . . . . . . . . . . . . . 55
B.14. Since draft-ietf-quic-http-10 . . . . . . . . . . . . . . 56 B.14. Since draft-ietf-quic-http-11 . . . . . . . . . . . . . . 56
B.15. Since draft-ietf-quic-http-09 . . . . . . . . . . . . . . 56 B.15. Since draft-ietf-quic-http-10 . . . . . . . . . . . . . . 56
B.16. Since draft-ietf-quic-http-08 . . . . . . . . . . . . . . 56 B.16. Since draft-ietf-quic-http-09 . . . . . . . . . . . . . . 56
B.17. Since draft-ietf-quic-http-07 . . . . . . . . . . . . . . 56 B.17. Since draft-ietf-quic-http-08 . . . . . . . . . . . . . . 56
B.18. Since draft-ietf-quic-http-06 . . . . . . . . . . . . . . 56 B.18. Since draft-ietf-quic-http-07 . . . . . . . . . . . . . . 56
B.19. Since draft-ietf-quic-http-05 . . . . . . . . . . . . . . 56 B.19. Since draft-ietf-quic-http-06 . . . . . . . . . . . . . . 56
B.20. Since draft-ietf-quic-http-04 . . . . . . . . . . . . . . 57 B.20. Since draft-ietf-quic-http-05 . . . . . . . . . . . . . . 56
B.21. Since draft-ietf-quic-http-03 . . . . . . . . . . . . . . 57 B.21. Since draft-ietf-quic-http-04 . . . . . . . . . . . . . . 57
B.22. Since draft-ietf-quic-http-02 . . . . . . . . . . . . . . 57 B.22. Since draft-ietf-quic-http-03 . . . . . . . . . . . . . . 57
B.23. Since draft-ietf-quic-http-01 . . . . . . . . . . . . . . 57 B.23. Since draft-ietf-quic-http-02 . . . . . . . . . . . . . . 57
B.24. Since draft-ietf-quic-http-00 . . . . . . . . . . . . . . 58 B.24. Since draft-ietf-quic-http-01 . . . . . . . . . . . . . . 57
B.25. Since draft-shade-quic-http2-mapping-00 . . . . . . . . . 58 B.25. Since draft-ietf-quic-http-00 . . . . . . . . . . . . . . 58
B.26. Since draft-shade-quic-http2-mapping-00 . . . . . . . . . 58
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 58 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 58
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 58
1. Introduction 1. Introduction
HTTP semantics are used for a broad range of services on the HTTP semantics are used for a broad range of services on the
Internet. These semantics have commonly been used with two different Internet. These semantics have commonly been used with two different
TCP mappings, HTTP/1.1 and HTTP/2. HTTP/3 supports the same TCP mappings, HTTP/1.1 and HTTP/2. HTTP/3 supports the same
semantics over a new transport protocol, QUIC. semantics over a new transport protocol, QUIC.
skipping to change at page 5, line 43 skipping to change at page 5, line 43
endpoint can be discovered using HTTP Alternative Services; this endpoint can be discovered using HTTP Alternative Services; this
process is described in greater detail in Section 3.2. process is described in greater detail in Section 3.2.
Within each stream, the basic unit of HTTP/3 communication is a frame Within each stream, the basic unit of HTTP/3 communication is a frame
(Section 7.2). Each frame type serves a different purpose. For (Section 7.2). Each frame type serves a different purpose. For
example, HEADERS and DATA frames form the basis of HTTP requests and example, HEADERS and DATA frames form the basis of HTTP requests and
responses (Section 4.1). responses (Section 4.1).
Multiplexing of requests is performed using the QUIC stream Multiplexing of requests is performed using the QUIC stream
abstraction, described in Section 2 of [QUIC-TRANSPORT]. Each abstraction, described in Section 2 of [QUIC-TRANSPORT]. Each
request and response consumes a single QUIC stream. Streams are request-response pair consumes a single QUIC stream. Streams are
independent of each other, so one stream that is blocked or suffers independent of each other, so one stream that is blocked or suffers
packet loss does not prevent progress on other streams. packet loss does not prevent progress on other streams.
Server push is an interaction mode introduced in HTTP/2 [HTTP2] which Server push is an interaction mode introduced in HTTP/2 [HTTP2] which
permits a server to push a request-response exchange to a client in permits a server to push a request-response exchange to a client in
anticipation of the client making the indicated request. This trades anticipation of the client making the indicated request. This trades
off network usage against a potential latency gain. Several HTTP/3 off network usage against a potential latency gain. Several HTTP/3
frames are used to manage server push, such as PUSH_PROMISE, frames are used to manage server push, such as PUSH_PROMISE,
DUPLICATE_PUSH, MAX_PUSH_ID, and CANCEL_PUSH. DUPLICATE_PUSH, MAX_PUSH_ID, and CANCEL_PUSH.
As in HTTP/2, request and response headers are compressed for As in HTTP/2, request and response headers are compressed for
transmission. Because HPACK [HPACK] relies on in-order transmission transmission. Because HPACK [HPACK] relies on in-order transmission
of compressed header blocks (a guarantee not provided by QUIC), of compressed header blocks (a guarantee not provided by QUIC),
HTTP/3 replaces HPACK with QPACK [QPACK]. QPACK uses separate HTTP/3 replaces HPACK with QPACK [QPACK]. QPACK uses separate
unidirectional streams to modify and track header table state, while unidirectional streams to modify and track header table state, while
header blocks refer to the state of the table without modifying it. header blocks refer to the state of the table without modifying it.
2.1. Document Organization 2.1. Document Organization
The HTTP/3 specification is split into seven parts. The document The following sections provide a detailed overview of the connection
begins with a detailed overview of the connection lifecycle and key lifecycle and key concepts:
concepts:
o Connection Setup and Management (Section 3) covers how an HTTP/3 o Connection Setup and Management (Section 3) covers how an HTTP/3
endpoint is discovered and a connection is established. endpoint is discovered and a connection is established.
o HTTP Request Lifecycle (Section 4) describes how HTTP semantics o HTTP Request Lifecycle (Section 4) describes how HTTP semantics
are expressed using frames. are expressed using frames.
o Connection Closure (Section 5) describes how connections are o Connection Closure (Section 5) describes how connections are
terminated, either gracefully or abruptly. terminated, either gracefully or abruptly.
skipping to change at page 11, line 40 skipping to change at page 11, line 40
Because some messages are large or unbounded, endpoints SHOULD begin Because some messages are large or unbounded, endpoints SHOULD begin
processing partial HTTP messages once enough of the message has been processing partial HTTP messages once enough of the message has been
received to make progress. If a client stream terminates without received to make progress. If a client stream terminates without
enough of the HTTP message to provide a complete response, the server enough of the HTTP message to provide a complete response, the server
SHOULD abort its response with the error code H3_REQUEST_INCOMPLETE. SHOULD abort its response with the error code H3_REQUEST_INCOMPLETE.
A server can send a complete response prior to the client sending an A server can send a complete response prior to the client sending an
entire request if the response does not depend on any portion of the entire request if the response does not depend on any portion of the
request that has not been sent and received. When the server does request that has not been sent and received. When the server does
not need to receive the remainder of the request, it MAY abort not need to receive the remainder of the request, it MAY abort
reading the request stream with error code H3_EARLY_RESPONSE, send a reading the request stream, send a complete response, and cleanly
complete response, and cleanly close the sending part of the stream. close the sending part of the stream. The error code H3_NO_ERROR
Clients MUST NOT discard complete responses as a result of having SHOULD be used when requesting that the client stop sending on the
their request terminated abruptly, though clients can always discard request stream. Clients MUST NOT discard complete responses as a
responses at their discretion for other reasons. If the server sends result of having their request terminated abruptly, though clients
a partial or complete response but does not abort reading, clients can always discard responses at their discretion for other reasons.
SHOULD continue sending the body of the request and close the stream If the server sends a partial or complete response but does not abort
normally. reading, clients SHOULD continue sending the body of the request and
close the stream normally.
4.1.1. Header Formatting and Compression 4.1.1. Header Formatting and Compression
HTTP message headers carry information as a series of key-value HTTP message headers carry information as a series of key-value
pairs, called header fields. For a listing of registered HTTP header pairs, called header fields. For a listing of registered HTTP header
fields, see the "Message Header Field" registry maintained at fields, see the "Message Header Field" registry maintained at
https://www.iana.org/assignments/message-headers [4]. https://www.iana.org/assignments/message-headers [4].
Just as in previous versions of HTTP, header field names are strings Just as in previous versions of HTTP, header field names are strings
of ASCII characters that are compared in a case-insensitive fashion. of ASCII characters that are compared in a case-insensitive fashion.
skipping to change at page 24, line 37 skipping to change at page 24, line 37
| MAX_PUSH_ID | Yes | No | No | Section 7. | | MAX_PUSH_ID | Yes | No | No | Section 7. |
| | | | | 2.7 | | | | | | 2.7 |
| | | | | | | | | | | |
| DUPLICATE_PUSH | No | Yes | No | Section 7. | | DUPLICATE_PUSH | No | Yes | No | Section 7. |
| | | | | 2.8 | | | | | | 2.8 |
| | | | | | | | | | | |
| Reserved | Yes | Yes | Yes | Section 7. | | Reserved | Yes | Yes | Yes | Section 7. |
| | | | | 2.9 | | | | | | 2.9 |
+----------------+------------+------------+-----------+------------+ +----------------+------------+------------+-----------+------------+
Table 1: HTTP/3 frames and stream type overview Table 1: HTTP/3 Frames and Stream Type Overview
Certain frames can only occur as the first frame of a particular Certain frames can only occur as the first frame of a particular
stream type; these are indicated in Table 1 with a (1). Specific stream type; these are indicated in Table 1 with a (1). Specific
guidance is provided in the relevant section. guidance is provided in the relevant section.
Note that, unlike QUIC frames, HTTP/3 frames can span multiple Note that, unlike QUIC frames, HTTP/3 frames can span multiple
packets. packets.
7.1. Frame Layout 7.1. Frame Layout
skipping to change at page 25, line 15 skipping to change at page 25, line 15
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (i) ... | Type (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length (i) ... | Length (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Frame Payload (*) ... | Frame Payload (*) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: HTTP/3 frame format Figure 3: HTTP/3 Frame Format
A frame includes the following fields: A frame includes the following fields:
Type: A variable-length integer that identifies the frame type. Type: A variable-length integer that identifies the frame type.
Length: A variable-length integer that describes the length in bytes Length: A variable-length integer that describes the length in bytes
of the Frame Payload. of the Frame Payload.
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.
skipping to change at page 26, line 11 skipping to change at page 26, line 11
a DATA frame is received on a control stream, the recipient MUST a DATA frame is received on a control stream, the recipient MUST
respond with a connection error (Section 8) of type respond with a connection error (Section 8) of type
H3_FRAME_UNEXPECTED. H3_FRAME_UNEXPECTED.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Payload (*) ... | Payload (*) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: DATA frame payload Figure 4: DATA Frame Payload
7.2.2. HEADERS 7.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 QPACK. See [QPACK] for more details. compressed using QPACK. See [QPACK] for more details.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Header Block (*) ... | Header Block (*) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: HEADERS frame payload Figure 5: HEADERS Frame Payload
HEADERS frames can only be sent on request / push streams. If a HEADERS frames can only be sent on request / push streams. If a
HEADERS frame is received on a control stream, the recipient MUST HEADERS frame is received on a control stream, the recipient MUST
respond with a connection error (Section 8) of type respond with a connection error (Section 8) of type
H3_FRAME_UNEXPECTED. H3_FRAME_UNEXPECTED.
7.2.3. CANCEL_PUSH 7.2.3. CANCEL_PUSH
The CANCEL_PUSH frame (type=0x3) is used to request cancellation of a The CANCEL_PUSH frame (type=0x3) is used to request cancellation of a
server push prior to the push stream being received. The CANCEL_PUSH server push prior to the push stream being received. The CANCEL_PUSH
skipping to change at page 27, line 18 skipping to change at page 27, line 18
A CANCEL_PUSH frame is sent on the control stream. Receiving a A CANCEL_PUSH frame is sent on the control stream. Receiving 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 connection error of type H3_FRAME_UNEXPECTED. treated as a connection error of type H3_FRAME_UNEXPECTED.
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 6: CANCEL_PUSH frame payload Figure 6: CANCEL_PUSH Frame Payload
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 7.2.5). If a CANCEL_PUSH frame is received cancelled (see Section 7.2.5). If a CANCEL_PUSH frame is received
which references a Push ID greater than currently allowed on the which references a Push ID greater than currently allowed on the
connection, this MUST be treated as a connection error of type connection, this MUST be treated as a connection error of type
H3_ID_ERROR. H3_ID_ERROR.
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 due a Push ID that has not yet been mentioned by a PUSH_PROMISE frame due
skipping to change at page 28, line 35 skipping to change at page 28, line 35
encoded as QUIC variable-length integers. encoded as QUIC variable-length integers.
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 (i) ... | Identifier (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (i) ... | Value (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: SETTINGS parameter format Figure 7: SETTINGS Parameter Format
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.
7.2.4.1. Defined SETTINGS Parameters 7.2.4.1. Defined SETTINGS Parameters
The following settings are defined in HTTP/3: The following settings are defined in HTTP/3:
SETTINGS_MAX_HEADER_LIST_SIZE (0x6): The default value is unlimited. SETTINGS_MAX_HEADER_LIST_SIZE (0x6): The default value is unlimited.
See Section 4.1.1 for usage. See Section 4.1.1 for usage.
skipping to change at page 30, line 37 skipping to change at page 30, line 37
header set from server to client on a request stream, as in HTTP/2. header set from server to client on a request stream, as in HTTP/2.
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 8: PUSH_PROMISE frame payload Figure 8: 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
operation. A Push ID is used in push stream headers operation. A Push ID is used in push stream headers
(Section 4.4), CANCEL_PUSH frames (Section 7.2.3), and (Section 4.4), CANCEL_PUSH frames (Section 7.2.3), and
DUPLICATE_PUSH frames (Section 7.2.8). DUPLICATE_PUSH frames (Section 7.2.8).
Header Block: QPACK-compressed request header fields for the Header Block: QPACK-compressed request header fields for the
promised response. See [QPACK] for more details. promised response. See [QPACK] for more details.
skipping to change at page 31, line 36 skipping to change at page 31, line 36
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.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream ID (i) ... | Stream ID (i) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: GOAWAY frame payload Figure 9: GOAWAY Frame Payload
The GOAWAY frame is always sent on the control stream. It carries a The GOAWAY frame is always sent on the control stream. It carries a
QUIC Stream ID for a client-initiated bidirectional stream encoded as QUIC Stream ID for a client-initiated bidirectional stream encoded as
a variable-length integer. A client MUST treat receipt of a GOAWAY a variable-length integer. A client MUST treat receipt of a GOAWAY
frame containing a Stream ID of any other type as a connection error frame containing a Stream ID of any other type as a connection error
of type H3_ID_ERROR. of type H3_ID_ERROR.
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 on any stream as a connection error (Section 8) of a GOAWAY frame on any stream as a connection error (Section 8) of
skipping to change at page 32, line 36 skipping to change at page 32, line 36
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 MAX_PUSH_ID frames as the increase the maximum Push ID by sending MAX_PUSH_ID frames as the
server fulfills or cancels server pushes. server fulfills or cancels server pushes.
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 10: MAX_PUSH_ID frame payload Figure 10: MAX_PUSH_ID Frame Payload
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 7.2.5). A MAX_PUSH_ID frame cannot reduce the maximum (see Section 7.2.5). 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
H3_ID_ERROR. H3_ID_ERROR.
7.2.8. DUPLICATE_PUSH 7.2.8. DUPLICATE_PUSH
skipping to change at page 33, line 19 skipping to change at page 33, line 19
A client MUST NOT send a DUPLICATE_PUSH frame. A server MUST treat A client MUST NOT send a DUPLICATE_PUSH frame. A server MUST treat
the receipt of a DUPLICATE_PUSH frame as a connection error of type the receipt of a DUPLICATE_PUSH frame as a connection error of type
H3_FRAME_UNEXPECTED. H3_FRAME_UNEXPECTED.
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 11: DUPLICATE_PUSH frame payload Figure 11: DUPLICATE_PUSH Frame Payload
The DUPLICATE_PUSH frame carries a single variable-length integer The DUPLICATE_PUSH frame carries a single variable-length integer
that identifies the Push ID of a resource that the server has that identifies the Push ID of a resource that the server has
previously promised (see Section 7.2.5), though that promise might previously promised (see Section 7.2.5), though that promise might
not be received before this frame. A server MUST NOT use a Push ID not be received before this frame. A server MUST NOT use a Push ID
that is larger than the client has provided in a MAX_PUSH_ID frame that is larger than the client has provided in a MAX_PUSH_ID frame
(Section 7.2.7). A client MUST treat receipt of a DUPLICATE_PUSH (Section 7.2.7). A client MUST treat receipt of a DUPLICATE_PUSH
that contains a larger Push ID than the client has advertised as a that contains a larger Push ID than the client has advertised as a
connection error of type H3_ID_ERROR. connection error of type H3_ID_ERROR.
skipping to change at page 34, line 9 skipping to change at page 34, line 9
ignored (Section 9). These frames have no semantics, and can be sent ignored (Section 9). These frames have no semantics, and can be sent
on any open stream when application-layer padding is desired. They on any open stream when application-layer padding is desired. They
MAY also be sent on connections where no data is currently being MAY also be sent on connections where no data is currently being
transferred. Endpoints MUST NOT consider these frames to have any transferred. Endpoints MUST NOT consider these frames to have any
meaning upon receipt. meaning upon receipt.
The payload and length of the frames are selected in any manner the The payload and length of the frames are selected in any manner the
implementation chooses. implementation chooses.
Frame types which were used in HTTP/2 where there is no corresponding Frame types which were used in HTTP/2 where there is no corresponding
HTTP/3 frame have also been reserved (Section 11.2). These frame HTTP/3 frame have also been reserved (Section 11.2.1). These frame
types MUST NOT be sent, and receipt MAY be treated as an error of types MUST NOT be sent, and receipt MAY be treated as an error of
type H3_FRAME_UNEXPECTED. type H3_FRAME_UNEXPECTED.
8. Error Handling 8. 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]. An endpoint MAY choose described in more detail in [QUIC-TRANSPORT]. An endpoint MAY choose
to treat a stream error as a connection error. to treat a stream error as a connection error.
skipping to change at page 35, line 32 skipping to change at page 35, line 32
H3_REQUEST_REJECTED (0x10B): A server rejected a request without H3_REQUEST_REJECTED (0x10B): A server rejected a request without
performing any application processing. performing any application processing.
H3_REQUEST_CANCELLED (0x10C): The request or its response (including H3_REQUEST_CANCELLED (0x10C): The request or its response (including
pushed response) is cancelled. pushed response) is cancelled.
H3_REQUEST_INCOMPLETE (0x10D): The client's stream terminated H3_REQUEST_INCOMPLETE (0x10D): The client's stream terminated
without containing a fully-formed request. without containing a fully-formed request.
H3_EARLY_RESPONSE (0x10E): The remainder of the client's request is
not needed to produce a response. For use in STOP_SENDING only.
H3_CONNECT_ERROR (0x10F): The connection established in response to H3_CONNECT_ERROR (0x10F): The connection established in response to
a CONNECT request was reset or abnormally closed. a CONNECT request was reset or abnormally closed.
H3_VERSION_FALLBACK (0x110): The requested operation cannot be H3_VERSION_FALLBACK (0x110): The requested operation cannot be
served over HTTP/3. The peer should retry over HTTP/1.1. served over HTTP/3. The peer should retry over HTTP/1.1.
9. Extensions to HTTP/3 9. Extensions to HTTP/3
HTTP/3 permits extension of the protocol. Within the limitations HTTP/3 permits extension of the protocol. Within the limitations
described in this section, protocol extensions can be used to provide described in this section, protocol extensions can be used to provide
skipping to change at page 36, line 9 skipping to change at page 36, line 4
are effective only within the scope of a single HTTP/3 connection. are effective only within the scope of a single HTTP/3 connection.
This applies to the protocol elements defined in this document. This This applies to the protocol elements defined in this document. This
does not affect the existing options for extending HTTP, such as does not affect the existing options for extending HTTP, such as
defining new methods, status codes, or header fields. defining new methods, status codes, or header fields.
Extensions are permitted to use new frame types (Section 7.2), new Extensions are permitted to use new frame types (Section 7.2), new
settings (Section 7.2.4.1), new error codes (Section 8), or new settings (Section 7.2.4.1), new error codes (Section 8), or new
unidirectional stream types (Section 6.2). Registries are unidirectional stream types (Section 6.2). Registries are
established for managing these extension points: frame types established for managing these extension points: frame types
(Section 11.2), settings (Section 11.3), error codes (Section 11.4), (Section 11.2.1), settings (Section 11.2.2), error codes
and stream types (Section 11.5). (Section 11.2.3), and stream types (Section 11.2.4).
Implementations MUST ignore unknown or unsupported values in all Implementations MUST ignore unknown or unsupported values in all
extensible protocol elements. Implementations MUST discard frames extensible protocol elements. Implementations MUST discard frames
and unidirectional streams that have unknown or unsupported types. and unidirectional streams that have unknown or unsupported types.
This means that any of these extension points can be safely used by This means that any of these extension points can be safely used by
extensions without prior arrangement or negotiation. However, where extensions without prior arrangement or negotiation. However, where
a known frame type is required to be in a specific location, such as a known frame type is required to be in a specific location, such as
the SETTINGS frame as the first frame of the control stream (see the SETTINGS frame as the first frame of the control stream (see
Section 6.2.1), an unknown frame type does not satisfy that Section 6.2.1), an unknown frame type does not satisfy that
requirement and SHOULD be treated as an error. requirement and SHOULD be treated as an error.
skipping to change at page 37, line 33 skipping to change at page 37, line 31
Certain HTTP implementations use the client address for logging or Certain HTTP implementations use the client address for logging or
access-control purposes. Since a QUIC client's address might change access-control purposes. Since a QUIC client's address might change
during a connection (and future versions might support simultaneous during a connection (and future versions might support simultaneous
use of multiple addresses), such implementations will need to either use of multiple addresses), such implementations will need to either
actively retrieve the client's current address or addresses when they actively retrieve the client's current address or addresses when they
are relevant or explicitly accept that the original address might are relevant or explicitly accept that the original address might
change. change.
11. IANA Considerations 11. IANA Considerations
This document registers a new ALPN protocol ID (Section 11.1) and
creates new registries that manage the assignment of codepoints in
HTTP/3.
11.1. Registration of HTTP/3 Identification String 11.1. Registration of HTTP/3 Identification String
This document creates a new registration for the identification of This document creates a new registration for the identification of
HTTP/3 in the "Application Layer Protocol Negotiation (ALPN) Protocol HTTP/3 in the "Application Layer Protocol Negotiation (ALPN) Protocol
IDs" registry established in [RFC7301]. IDs" registry established in [RFC7301].
The "h3" string identifies HTTP/3: The "h3" string identifies HTTP/3:
Protocol: HTTP/3 Protocol: HTTP/3
Identification Sequence: 0x68 0x33 ("h3") Identification Sequence: 0x68 0x33 ("h3")
Specification: This document Specification: This document
11.2. Frame Types 11.2. New Registries
This document establishes a registry for HTTP/3 frame type codes. New registries created in this document operate under the QUIC
The "HTTP/3 Frame Type" registry governs a 62-bit space. This space registration policy documented in Section 22.1 of [QUIC-TRANSPORT].
is split into three spaces that are governed by different policies. These registries all include the common set of fields listed in
Section 22.1.1 of [QUIC-TRANSPORT].
Values between "0x00" and "0x3f" (in hexadecimal) are assigned via The initial allocations in these registries created in this document
the Standards Action or IESG Review policies [RFC8126]. Values from are all assigned permanent status and list as contact both the IESG
"0x40" to "0x3fff" operate on the Specification Required policy (iesg@ietf.org) and the HTTP working group (ietf-http-wg@w3.org).
[RFC8126]. All other values are assigned to Private Use [RFC8126].
11.2.1. Frame Types
This document establishes a registry for HTTP/3 frame type codes.
The "HTTP/3 Frame Type" registry governs a 62-bit space. This
registry follows the QUIC registry policy; see Section 11.2.
Permanent registrations in this registry are assigned using the
Specification Required policy [RFC8126], except for values between
0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using
Standards Action or IESG Approval as defined in Section 4.9 and 4.10
of [RFC8126].
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 [HTTP2], it is preferable that the assignments parallel defined in [HTTP2], it is preferable that the assignments parallel
each other where the code spaces overlap. If an entry is present in each other where the code spaces overlap. If an entry is present in
only one registry, every effort SHOULD be made to avoid assigning the only one registry, every effort SHOULD be made to avoid assigning the
corresponding value to an unrelated operation. corresponding value to an unrelated operation.
New entries in this registry require the following information: In addition to common fields as described in Section 11.2, permanent
registrations in this registry MUST include the following field:
Frame Type: A name or label for the frame type. Frame Type: A name or label for the frame type.
Code: The 62-bit code assigned to the frame type. Specifications of frame types MUST include a description of the frame
layout and its semantics, including any parts of the frame that are
conditionally present.
Specification: A reference to a specification that includes a The entries in Table 2 are registered by this document.
description of the frame layout and its semantics, including any
parts of the frame that are conditionally present.
The entries in the following table are registered by this document. +----------------+-------+----------------+
| Frame Type | Value | Specification |
+----------------+-------+----------------+
| DATA | 0x0 | Section 7.2.1 |
| | | |
| HEADERS | 0x1 | Section 7.2.2 |
| | | |
| Reserved | 0x2 | N/A |
| | | |
| CANCEL_PUSH | 0x3 | Section 7.2.3 |
| | | |
| SETTINGS | 0x4 | Section 7.2.4 |
| | | |
| PUSH_PROMISE | 0x5 | Section 7.2.5 |
| | | |
| Reserved | 0x6 | N/A |
| | | |
| GOAWAY | 0x7 | Section 7.2.6 |
| | | |
| Reserved | 0x8 | N/A |
| | | |
| Reserved | 0x9 | N/A |
| | | |
| MAX_PUSH_ID | 0xD | Section 7.2.7 |
| | | |
| DUPLICATE_PUSH | 0xE | Section 7.2.8 |
+----------------+-------+----------------+
+----------------+------+----------------+ Table 2: Initial HTTP/3 Frame Types
| Frame Type | Code | Specification |
+----------------+------+----------------+
| DATA | 0x0 | Section 7.2.1 |
| | | |
| HEADERS | 0x1 | Section 7.2.2 |
| | | |
| Reserved | 0x2 | N/A |
| | | |
| CANCEL_PUSH | 0x3 | Section 7.2.3 |
| | | |
| SETTINGS | 0x4 | Section 7.2.4 |
| | | |
| PUSH_PROMISE | 0x5 | Section 7.2.5 |
| | | |
| Reserved | 0x6 | N/A |
| | | |
| GOAWAY | 0x7 | Section 7.2.6 |
| | | |
| Reserved | 0x8 | N/A |
| | | |
| Reserved | 0x9 | N/A |
| | | |
| MAX_PUSH_ID | 0xD | Section 7.2.7 |
| | | |
| DUPLICATE_PUSH | 0xE | Section 7.2.8 |
+----------------+------+----------------+
Additionally, each code of the format "0x1f * N + 0x21" for integer Additionally, each code of the format "0x1f * N + 0x21" for integer
values of N (that is, "0x21", "0x40", ..., through values of N (that is, "0x21", "0x40", ..., through
"0x3FFFFFFFFFFFFFFE") MUST NOT be assigned by IANA. "0x3FFFFFFFFFFFFFFE") MUST NOT be assigned by IANA.
11.3. Settings Parameters 11.2.2. Settings Parameters
This document establishes a registry for HTTP/3 settings. The This document establishes a registry for HTTP/3 settings. The
"HTTP/3 Settings" registry governs a 62-bit space. This space is "HTTP/3 Settings" registry governs a 62-bit space. This registry
split into three spaces that are governed by different policies. follows the QUIC registry policy; see Section 11.2. Permanent
Values between "0x00" and "0x3f" (in hexadecimal) are assigned via registrations in this registry are assigned using the Specification
the Standards Action or IESG Review policies [RFC8126]. Values from Required policy [RFC8126], except for values between 0x00 and 0x3f
"0x40" to "0x3fff" operate on the Specification Required policy (in hexadecimal; inclusive), which are assigned using Standards
[RFC8126]. All other values are assigned to Private Use [RFC8126]. Action or IESG Approval as defined in Section 4.9 and 4.10 of
The designated experts are the same as those for the "HTTP/2 [RFC8126].
Settings" registry defined in [HTTP2].
While this registry is separate from the "HTTP/2 Settings" registry While this registry is separate from the "HTTP/2 Settings" registry
defined in [HTTP2], it is preferable that the assignments parallel defined in [HTTP2], it is preferable that the assignments parallel
each other. If an entry is present in only one registry, every each other. If an entry is present in only one registry, every
effort SHOULD be made to avoid assigning the corresponding value to effort SHOULD be made to avoid assigning the corresponding value to
an unrelated operation. an unrelated operation.
New registrations are advised to provide the following information: In addition to common fields as described in Section 11.2, permanent
registrations in this registry MUST include the following fields:
Name: A symbolic name for the setting. Specifying a setting name is
optional.
Code: The 62-bit code assigned to the setting. Setting Name: A symbolic name for the setting. Specifying a setting
name is optional.
Specification: An optional reference to a specification that Default: The value of the setting unless otherwise indicated. A
describes the use of the setting. default SHOULD be the most restrictive possible value.
Default: The value of the setting unless otherwise indicated. The entries in Table 3 are registered by this document.
SHOULD be the most restrictive possible value.
The entries in the following table are registered by this document. +----------------------+-------+------------------+-----------+
| Setting Name | Value | Specification | Default |
+----------------------+-------+------------------+-----------+
| Reserved | 0x2 | N/A | N/A |
| | | | |
| Reserved | 0x3 | N/A | N/A |
| | | | |
| Reserved | 0x4 | N/A | N/A |
| | | | |
| Reserved | 0x5 | N/A | N/A |
| | | | |
| MAX_HEADER_LIST_SIZE | 0x6 | Section 7.2.4.1 | Unlimited |
+----------------------+-------+------------------+-----------+
+----------------------+------+------------------+-----------+ Table 3: Initial HTTP/3 Settings
| Setting Name | Code | Specification | Default |
+----------------------+------+------------------+-----------+
| Reserved | 0x2 | N/A | N/A |
| | | | |
| Reserved | 0x3 | N/A | N/A |
| | | | |
| Reserved | 0x4 | N/A | N/A |
| | | | |
| Reserved | 0x5 | N/A | N/A |
| | | | |
| MAX_HEADER_LIST_SIZE | 0x6 | Section 7.2.4.1 | Unlimited |
+----------------------+------+------------------+-----------+
Additionally, each code of the format "0x1f * N + 0x21" for integer Additionally, each code of the format "0x1f * N + 0x21" for integer
values of N (that is, "0x21", "0x40", ..., through values of N (that is, "0x21", "0x40", ..., through
"0x3FFFFFFFFFFFFFFE") MUST NOT be assigned by IANA. "0x3FFFFFFFFFFFFFFE") MUST NOT be assigned by IANA.
11.4. Error Codes 11.2.3. Error Codes
This document establishes a registry for HTTP/3 error codes. The This document establishes a registry for HTTP/3 error codes. The
"HTTP/3 Error Code" registry manages a 62-bit space. The "HTTP/3 "HTTP/3 Error Code" registry manages a 62-bit space. This registry
Error Code" registry operates under the "Expert Review" policy follows the QUIC registry policy; see Section 11.2. Permanent
registrations in this registry are assigned using the Specification
Required policy [RFC8126], except for values between 0x00 and 0x3f
(in hexadecimal; inclusive), which are assigned using Standards
Action or IESG Approval as defined in Section 4.9 and 4.10 of
[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.
New registrations are advised to provide the following information: In addition to common fields as described in Section 11.2, permanent
registrations in this registry MUST include the following fields:
Name: A name for the error code. Specifying an error code name is Name: A name for the error code. Specifying an error code name is
optional. optional.
Code: The 62-bit error code value. Description: A brief description of the error code semantics.
Description: A brief description of the error code semantics, longer
if no detailed specification is provided.
Specification: An optional reference for a specification that
defines the error code.
The entries in the following table are registered by this document. The entries in the Table 4 are registered by this document.
+---------------------------+--------+--------------+---------------+ +---------------------------+--------+--------------+---------------+
| Name | Code | Description | Specification | | Name | Value | Description | Specification |
+---------------------------+--------+--------------+---------------+ +---------------------------+--------+--------------+---------------+
| H3_NO_ERROR | 0x0100 | No error | Section 8.1 | | H3_NO_ERROR | 0x0100 | No error | Section 8.1 |
| | | | | | | | | |
| H3_GENERAL_PROTOCOL_ERROR | 0x0101 | General | Section 8.1 | | H3_GENERAL_PROTOCOL_ERROR | 0x0101 | General | Section 8.1 |
| | | protocol | | | | | protocol | |
| | | error | | | | | error | |
| | | | | | | | | |
| H3_INTERNAL_ERROR | 0x0102 | Internal | Section 8.1 | | H3_INTERNAL_ERROR | 0x0102 | Internal | Section 8.1 |
| | | error | | | | | error | |
| | | | | | | | | |
skipping to change at page 42, line 32 skipping to change at page 42, line 30
| | | processed | | | | | processed | |
| | | | | | | | | |
| H3_REQUEST_CANCELLED | 0x010C | Data no | Section 8.1 | | H3_REQUEST_CANCELLED | 0x010C | Data no | Section 8.1 |
| | | longer | | | | | longer | |
| | | needed | | | | | needed | |
| | | | | | | | | |
| H3_REQUEST_INCOMPLETE | 0x010D | Stream | Section 8.1 | | H3_REQUEST_INCOMPLETE | 0x010D | Stream | Section 8.1 |
| | | terminated | | | | | terminated | |
| | | early | | | | | early | |
| | | | | | | | | |
| H3_EARLY_RESPONSE | 0x010E | Remainder of | Section 8.1 |
| | | request not | |
| | | needed | |
| | | | |
| H3_CONNECT_ERROR | 0x010F | TCP reset or | Section 8.1 | | H3_CONNECT_ERROR | 0x010F | TCP reset or | Section 8.1 |
| | | error on | | | | | error on | |
| | | CONNECT | | | | | CONNECT | |
| | | request | | | | | request | |
| | | | | | | | | |
| H3_VERSION_FALLBACK | 0x0110 | Retry over | Section 8.1 | | H3_VERSION_FALLBACK | 0x0110 | Retry over | Section 8.1 |
| | | HTTP/1.1 | | | | | HTTP/1.1 | |
+---------------------------+--------+--------------+---------------+ +---------------------------+--------+--------------+---------------+
11.5. Stream Types Table 4: Initial HTTP/3 Error Codes
11.2.4. Stream Types
This document establishes a registry for HTTP/3 unidirectional stream This document establishes a registry for HTTP/3 unidirectional stream
types. The "HTTP/3 Stream Type" registry governs a 62-bit space. types. The "HTTP/3 Stream Type" registry governs a 62-bit space.
This space is split into three spaces that are governed by different This registry follows the QUIC registry policy; see Section 11.2.
policies. Values between "0x00" and 0x3f (in hexadecimal) are Permanent registrations in this registry are assigned using the
assigned via the Standards Action or IESG Review policies [RFC8126]. Specification Required policy [RFC8126], except for values between
0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using
Values from "0x40" to "0x3fff" operate on the Specification Required Standards Action or IESG Approval as defined in Section 4.9 and 4.10
policy [RFC8126]. All other values are assigned to Private Use of [RFC8126].
[RFC8126].
New entries in this registry require the following information: In addition to common fields as described in Section 11.2, permanent
registrations in this registry MUST include the following fields:
Stream Type: A name or label for the stream type. Stream Type: A name or label for the stream type.
Code: The 62-bit code assigned to the stream type.
Specification: A reference to a specification that includes a
description of the stream type, including the layout semantics of
its payload.
Sender: Which endpoint on a connection may initiate a stream of this Sender: Which endpoint on a connection may initiate a stream of this
type. Values are "Client", "Server", or "Both". type. Values are "Client", "Server", or "Both".
Specifications for permanent registrations MUST include a description
of the stream type, including the layout semantics of the stream
contents.
The entries in the following table are registered by this document. The entries in the following table are registered by this document.
+----------------+------+----------------+--------+ +----------------+-------+----------------+--------+
| Stream Type | Code | Specification | Sender | | Stream Type | Value | Specification | Sender |
+----------------+------+----------------+--------+ +----------------+-------+----------------+--------+
| Control Stream | 0x00 | Section 6.2.1 | Both | | Control Stream | 0x00 | Section 6.2.1 | Both |
| | | | | | | | | |
| Push Stream | 0x01 | Section 4.4 | Server | | Push Stream | 0x01 | Section 4.4 | Server |
+----------------+------+----------------+--------+ +----------------+-------+----------------+--------+
Additionally, each code of the format "0x1f * N + 0x21" for integer Additionally, each code of the format "0x1f * N + 0x21" for integer
values of N (that is, "0x21", "0x40", ..., through values of N (that is, "0x21", "0x40", ..., through
"0x3FFFFFFFFFFFFFFE") MUST NOT be assigned by IANA. "0x3FFFFFFFFFFFFFFE") MUST NOT be assigned by IANA.
12. References 12. References
12.1. Normative References 12.1. Normative References
[ALTSVC] Nottingham, M., McManus, P., and J. Reschke, "HTTP [ALTSVC] Nottingham, M., McManus, P., and J. Reschke, "HTTP
skipping to change at page 44, line 7 skipping to change at page 43, line 51
Data in HTTP", RFC 8470, DOI 10.17487/RFC8470, September Data in HTTP", RFC 8470, DOI 10.17487/RFC8470, September
2018, <https://www.rfc-editor.org/info/rfc8470>. 2018, <https://www.rfc-editor.org/info/rfc8470>.
[HTTP2] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext [HTTP2] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext
Transfer Protocol Version 2 (HTTP/2)", RFC 7540, Transfer Protocol Version 2 (HTTP/2)", RFC 7540,
DOI 10.17487/RFC7540, May 2015, DOI 10.17487/RFC7540, May 2015,
<https://www.rfc-editor.org/info/rfc7540>. <https://www.rfc-editor.org/info/rfc7540>.
[QPACK] Krasic, C., Bishop, M., and A. Frindell, Ed., "QPACK: [QPACK] Krasic, C., Bishop, M., and A. Frindell, Ed., "QPACK:
Header Compression for HTTP over QUIC", draft-ietf-quic- Header Compression for HTTP over QUIC", draft-ietf-quic-
qpack-11 (work in progress). qpack-latest (work in progress).
[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-24 (work in progress). transport-latest (work in progress).
[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>.
skipping to change at page 49, line 16 skipping to change at page 49, line 10
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. larger HEADERS/PUSH_PROMISE frames than HTTP/2 are permitted.
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/3 if still applicable. The IDs of frames defined registered for HTTP/3 if still applicable. The IDs of frames defined
in [HTTP2] have been reserved for simplicity. Note that the frame in [HTTP2] have been reserved for simplicity. Note that the frame
type space in HTTP/3 is substantially larger (62 bits versus 8 bits), type space in HTTP/3 is substantially larger (62 bits versus 8 bits),
so many HTTP/3 frame types have no equivalent HTTP/2 code points. so many HTTP/3 frame types have no equivalent HTTP/2 code points.
See Section 11.2. See Section 11.2.1.
A.3. HTTP/2 SETTINGS Parameters A.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,
as the first frame of the control stream, and thereafter cannot as the first frame of the control stream, and thereafter cannot
change. This eliminates many corner cases around synchronization of change. This eliminates many corner cases around synchronization of
changes. 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/3. The frame are superseded by QUIC transport parameters in HTTP/3. The
skipping to change at page 50, line 4 skipping to change at page 49, line 47
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/3. SETTINGS_MAX_FRAME_SIZE: This setting has no equivalent in HTTP/3.
Specifying it in the SETTINGS frame is an error. Specifying it in the SETTINGS frame is an error.
SETTINGS_MAX_HEADER_LIST_SIZE: See Section 7.2.4.1. SETTINGS_MAX_HEADER_LIST_SIZE: See Section 7.2.4.1.
In HTTP/3, setting values are variable-length integers (6, 14, 30, or In HTTP/3, setting values are variable-length integers (6, 14, 30, or
62 bits long) rather than fixed-length 32-bit fields as in HTTP/2. 62 bits long) rather than fixed-length 32-bit fields as in HTTP/2.
This will often produce a shorter encoding, but can produce a longer This will often produce a shorter encoding, but can produce a longer
encoding for settings which use the full 32-bit space. Settings encoding for settings which use the full 32-bit space. Settings
ported from HTTP/2 might choose to redefine the format of their ported from HTTP/2 might choose to redefine their value to limit it
settings to avoid using the 62-bit encoding. to 30 bits for more efficient encoding, or to make use of the 62-bit
space if more than 30 bits are required.
Settings need to be defined separately for HTTP/2 and HTTP/3. The Settings need to be defined separately for HTTP/2 and HTTP/3. The
IDs of settings defined in [HTTP2] have been reserved for simplicity. IDs of settings defined in [HTTP2] have been reserved for simplicity.
Note that the settings identifier space in HTTP/3 is substantially Note that the settings identifier space in HTTP/3 is substantially
larger (62 bits versus 16 bits), so many HTTP/3 settings have no larger (62 bits versus 16 bits), so many HTTP/3 settings have no
equivalent HTTP/2 code point. See Section 11.3. equivalent HTTP/2 code point. See Section 11.2.2.
As QUIC streams might arrive out-of-order, endpoints are advised to As QUIC streams might arrive out-of-order, endpoints are advised to
not wait for the peers' settings to arrive before responding to other not wait for the peers' settings to arrive before responding to other
streams. See Section 7.2.4.2. streams. See Section 7.2.4.2.
A.4. HTTP/2 Error Codes A.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, there is no direct portability of HTTP/2 HTTP/2 provides. However, there is no direct portability of HTTP/2
error codes to HTTP/3 error codes; the values are shifted in order to error codes to HTTP/3 error codes; the values are shifted in order to
skipping to change at page 51, line 24 skipping to change at page 51, line 18
CONNECT_ERROR (0xa): H3_CONNECT_ERROR in Section 8.1. CONNECT_ERROR (0xa): H3_CONNECT_ERROR in Section 8.1.
ENHANCE_YOUR_CALM (0xb): H3_EXCESSIVE_LOAD in Section 8.1. ENHANCE_YOUR_CALM (0xb): H3_EXCESSIVE_LOAD in Section 8.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.
H3_1_1_REQUIRED (0xd): H3_VERSION_FALLBACK in Section 8.1. H3_1_1_REQUIRED (0xd): H3_VERSION_FALLBACK in Section 8.1.
Error codes need to be defined for HTTP/2 and HTTP/3 separately. See Error codes need to be defined for HTTP/2 and HTTP/3 separately. See
Section 11.4. Section 11.2.3.
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-23 B.1. Since draft-ietf-quic-http-24
o Removed H3_EARLY_RESPONSE error code; H3_NO_ERROR is recommended
instead (#3130,#3208)
B.2. Since draft-ietf-quic-http-23
o Removed "quic" Alt-Svc parameter (#3061,#3118) o Removed "quic" Alt-Svc parameter (#3061,#3118)
o Clients need not persist unknown settings for use in 0-RTT o Clients need not persist unknown settings for use in 0-RTT
(#3110,#3113) (#3110,#3113)
o Clarify error cases around CANCEL_PUSH (#2819,#3083) o Clarify error cases around CANCEL_PUSH (#2819,#3083)
B.2. Since draft-ietf-quic-http-22 B.3. Since draft-ietf-quic-http-22
o Removed priority signaling (#2922,#2924) o Removed priority signaling (#2922,#2924)
o Further changes to error codes (#2662,#2551): o Further changes to error codes (#2662,#2551):
* Error codes renumbered * Error codes renumbered
* HTTP_MALFORMED_FRAME replaced by HTTP_FRAME_ERROR, * HTTP_MALFORMED_FRAME replaced by HTTP_FRAME_ERROR,
HTTP_ID_ERROR, and others HTTP_ID_ERROR, and others
skipping to change at page 52, line 33 skipping to change at page 52, line 33
o Clarify that Upgrade and the 101 status code are prohibited o Clarify that Upgrade and the 101 status code are prohibited
(#2898,#2889) (#2898,#2889)
o Clarify that frame types reserved for greasing can occur on any o Clarify that frame types reserved for greasing can occur on any
stream, but frame types reserved due to HTTP/2 correspondence are stream, but frame types reserved due to HTTP/2 correspondence are
prohibited (#2997,#2692,#2693) prohibited (#2997,#2692,#2693)
o Unknown error codes cannot be treated as errors (#2998,#2816) o Unknown error codes cannot be treated as errors (#2998,#2816)
B.3. Since draft-ietf-quic-http-21 B.4. Since draft-ietf-quic-http-21
No changes No changes
B.4. Since draft-ietf-quic-http-20 B.5. Since draft-ietf-quic-http-20
o Prohibit closing the control stream (#2509, #2666) o Prohibit closing the control stream (#2509, #2666)
o Change default priority to use an orphan node (#2502, #2690) o Change default priority to use an orphan node (#2502, #2690)
o Exclusive priorities are restored (#2754, #2781) o Exclusive priorities are restored (#2754, #2781)
o Restrict use of frames when using CONNECT (#2229, #2702) o Restrict use of frames when using CONNECT (#2229, #2702)
o Close and maybe reset streams if a connection error occurs for o Close and maybe reset streams if a connection error occurs for
skipping to change at page 53, line 32 skipping to change at page 53, line 32
* Specified error code for receiving DATA before HEADERS (#2715) * Specified error code for receiving DATA before HEADERS (#2715)
* Describe malformed messages and their handling (#2410, #2764) * Describe malformed messages and their handling (#2410, #2764)
* Remove HTTP_PUSH_ALREADY_IN_CACHE error (#2812, #2813) * Remove HTTP_PUSH_ALREADY_IN_CACHE error (#2812, #2813)
* Refactor Push ID related errors (#2818, #2820) * Refactor Push ID related errors (#2818, #2820)
* Rationalize HTTP/3 stream creation errors (#2821, #2822) * Rationalize HTTP/3 stream creation errors (#2821, #2822)
B.5. Since draft-ietf-quic-http-19 B.6. Since draft-ietf-quic-http-19
o SETTINGS_NUM_PLACEHOLDERS is 0x9 (#2443,#2530) o SETTINGS_NUM_PLACEHOLDERS is 0x9 (#2443,#2530)
o Non-zero bits in the Empty field of the PRIORITY frame MAY be o Non-zero bits in the Empty field of the PRIORITY frame MAY be
treated as an error (#2501) treated as an error (#2501)
B.6. Since draft-ietf-quic-http-18 B.7. Since draft-ietf-quic-http-18
o Resetting streams following a GOAWAY is recommended, but not o Resetting streams following a GOAWAY is recommended, but not
required (#2256,#2457) required (#2256,#2457)
o Use variable-length integers throughout (#2437,#2233,#2253,#2275) o Use variable-length integers throughout (#2437,#2233,#2253,#2275)
* Variable-length frame types, stream types, and settings * Variable-length frame types, stream types, and settings
identifiers identifiers
* Renumbered stream type assignments * Renumbered stream type assignments
* Modified associated reserved values * Modified associated reserved values
o Frame layout switched from Length-Type-Value to Type-Length-Value o Frame layout switched from Length-Type-Value to Type-Length-Value
(#2395,#2235) (#2395,#2235)
o Specified error code for servers receiving DUPLICATE_PUSH (#2497) o Specified error code for servers receiving DUPLICATE_PUSH (#2497)
o Use connection error for invalid PRIORITY (#2507, #2508) o Use connection error for invalid PRIORITY (#2507, #2508)
B.7. Since draft-ietf-quic-http-17 B.8. Since draft-ietf-quic-http-17
o HTTP_REQUEST_REJECTED is used to indicate a request can be retried o HTTP_REQUEST_REJECTED is used to indicate a request can be retried
(#2106, #2325) (#2106, #2325)
o Changed error code for GOAWAY on the wrong stream (#2231, #2343) o Changed error code for GOAWAY on the wrong stream (#2231, #2343)
B.8. Since draft-ietf-quic-http-16 B.9. Since draft-ietf-quic-http-16
o Rename "HTTP/QUIC" to "HTTP/3" (#1973) o Rename "HTTP/QUIC" to "HTTP/3" (#1973)
o Changes to PRIORITY frame (#1865, #2075) o Changes to PRIORITY frame (#1865, #2075)
* Permitted as first frame of request streams * Permitted as first frame of request streams
* Remove exclusive reprioritization * Remove exclusive reprioritization
* Changes to Prioritized Element Type bits * Changes to Prioritized Element Type bits
skipping to change at page 54, line 45 skipping to change at page 54, line 45
(#1809, #1846, #2038) (#1809, #1846, #2038)
o Clarify message processing rules for streams that aren't closed o Clarify message processing rules for streams that aren't closed
(#1972, #2003) (#1972, #2003)
o Removed reservation of error code 0 and moved HTTP_NO_ERROR to o Removed reservation of error code 0 and moved HTTP_NO_ERROR to
this value (#1922) this value (#1922)
o Removed prohibition of zero-length DATA frames (#2098) o Removed prohibition of zero-length DATA frames (#2098)
B.9. Since draft-ietf-quic-http-15 B.10. Since draft-ietf-quic-http-15
Substantial editorial reorganization; no technical changes. Substantial editorial reorganization; no technical changes.
B.10. Since draft-ietf-quic-http-14 B.11. Since draft-ietf-quic-http-14
o Recommend sensible values for QUIC transport parameters o Recommend sensible values for QUIC transport parameters
(#1720,#1806) (#1720,#1806)
o Define error for missing SETTINGS frame (#1697,#1808) o Define error for missing SETTINGS frame (#1697,#1808)
o Setting values are variable-length integers (#1556,#1807) and do o Setting values are variable-length integers (#1556,#1807) and do
not have separate maximum values (#1820) not have separate maximum values (#1820)
o Expanded discussion of connection closure (#1599,#1717,#1712) o Expanded discussion of connection closure (#1599,#1717,#1712)
o HTTP_VERSION_FALLBACK falls back to HTTP/1.1 (#1677,#1685) o HTTP_VERSION_FALLBACK falls back to HTTP/1.1 (#1677,#1685)
B.11. Since draft-ietf-quic-http-13 B.12. Since draft-ietf-quic-http-13
o Reserved some frame types for grease (#1333, #1446) o Reserved some frame types for grease (#1333, #1446)
o Unknown unidirectional stream types are tolerated, not errors; o Unknown unidirectional stream types are tolerated, not errors;
some reserved for grease (#1490, #1525) some reserved for grease (#1490, #1525)
o Require settings to be remembered for 0-RTT, prohibit reductions o Require settings to be remembered for 0-RTT, prohibit reductions
(#1541, #1641) (#1541, #1641)
o Specify behavior for truncated requests (#1596, #1643) o Specify behavior for truncated requests (#1596, #1643)
B.12. Since draft-ietf-quic-http-12 B.13. Since draft-ietf-quic-http-12
o TLS SNI extension isn't mandatory if an alternative method is used o TLS SNI extension isn't mandatory if an alternative method is used
(#1459, #1462, #1466) (#1459, #1462, #1466)
o Removed flags from HTTP/3 frames (#1388, #1398) o Removed flags from HTTP/3 frames (#1388, #1398)
o Reserved frame types and settings for use in preserving o Reserved frame types and settings for use in preserving
extensibility (#1333, #1446) extensibility (#1333, #1446)
o Added general error code (#1391, #1397) o Added general error code (#1391, #1397)
o Unidirectional streams carry a type byte and are extensible o Unidirectional streams carry a type byte and are extensible
(#910,#1359) (#910,#1359)
o Priority mechanism now uses explicit placeholders to enable o Priority mechanism now uses explicit placeholders to enable
persistent structure in the tree (#441,#1421,#1422) persistent structure in the tree (#441,#1421,#1422)
B.13. Since draft-ietf-quic-http-11 B.14. Since draft-ietf-quic-http-11
o Moved QPACK table updates and acknowledgments to dedicated streams o Moved QPACK table updates and acknowledgments to dedicated streams
(#1121, #1122, #1238) (#1121, #1122, #1238)
B.14. Since draft-ietf-quic-http-10 B.15. Since draft-ietf-quic-http-10
o Settings need to be remembered when attempting and accepting 0-RTT o Settings need to be remembered when attempting and accepting 0-RTT
(#1157, #1207) (#1157, #1207)
B.15. Since draft-ietf-quic-http-09 B.16. Since draft-ietf-quic-http-09
o Selected QCRAM for header compression (#228, #1117) o Selected QCRAM for header compression (#228, #1117)
o The server_name TLS extension is now mandatory (#296, #495) o The server_name TLS extension is now mandatory (#296, #495)
o Specified handling of unsupported versions in Alt-Svc (#1093, o Specified handling of unsupported versions in Alt-Svc (#1093,
#1097) #1097)
B.16. Since draft-ietf-quic-http-08 B.17. Since draft-ietf-quic-http-08
o Clarified connection coalescing rules (#940, #1024) o Clarified connection coalescing rules (#940, #1024)
B.17. Since draft-ietf-quic-http-07 B.18. Since draft-ietf-quic-http-07
o Changes for integer encodings in QUIC (#595,#905) o Changes for integer encodings in QUIC (#595,#905)
o Use unidirectional streams as appropriate (#515, #240, #281, #886) o Use unidirectional streams as appropriate (#515, #240, #281, #886)
o Improvement to the description of GOAWAY (#604, #898) o Improvement to the description of GOAWAY (#604, #898)
o Improve description of server push usage (#947, #950, #957) o Improve description of server push usage (#947, #950, #957)
B.18. Since draft-ietf-quic-http-06 B.19. 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.19. Since draft-ietf-quic-http-05 B.20. 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.20. Since draft-ietf-quic-http-04 B.21. 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.21. Since draft-ietf-quic-http-03 B.22. Since draft-ietf-quic-http-03
None. None.
B.22. Since draft-ietf-quic-http-02 B.23. Since draft-ietf-quic-http-02
o Track changes in transport draft o Track changes in transport draft
B.23. Since draft-ietf-quic-http-01 B.24. 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 58, line 7 skipping to change at page 58, line 7
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.24. Since draft-ietf-quic-http-00 B.25. 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)
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.25. Since draft-shade-quic-http2-mapping-00 B.26. 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
Acknowledgements Acknowledgements
The original authors of this specification were Robbie Shade and Mike The original authors of this specification were Robbie Shade and Mike
Warres. Warres.
 End of changes. 84 change blocks. 
207 lines changed or deleted 219 lines changed or added

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