2.1. <del> The HTTP/3 specification is split into seven parts: </del>  Connection Setup and Management (connection-setup) covers how an HTTP/3 endpoint is discovered and a connection is established. <del> Stream Mapping and Usage (stream-mapping) describes the way QUIC streams are used. HTTP Framing Layer (http-framing-layer) describes the frames used on most streams. </del> HTTP Request Lifecycle (http-request-lifecycle) describes how HTTP semantics are expressed using frames. Connection Closure (connection-closure) describes how connections are terminated, either gracefully or abruptly. <del> Extensions to HTTP/3 (extensions) describes how new capabilities can be added in future documents. </del>  Error Handling (errors) describes how error conditions are handled and expressed, either on a particular stream or for the connection as a whole. <del> A more detailed comparison between HTTP/2 and HTTP/3 can be found in h2-considerations. </del>  2.2. 4. <del> A QUIC stream provides reliable in-order delivery of bytes, but makes no guarantees about order of delivery with regard to bytes on other streams.  On the wire, data is framed into QUIC STREAM frames, but this framing is invisible to the HTTP framing layer.  The transport layer buffers and orders received QUIC STREAM frames, exposing the data contained within as a reliable byte stream to the application. Although QUIC permits out-of-order delivery within a stream HTTP/3 does not make use of this feature. QUIC streams can be either unidirectional, carrying data only from initiator to receiver, or bidirectional.  Streams can be initiated by either the client or the server.  For more detail on QUIC streams, see Section 2 of QUIC-TRANSPORT. </del>  <del> When HTTP headers and data are sent over QUIC, the QUIC layer handles most of the stream management.  HTTP does not need to do any separate multiplexing when using QUIC - data sent over a QUIC stream always maps to a particular HTTP transaction or connection context. </del>  <del> 4.1. </del>  <del> All client-initiated bidirectional streams are used for HTTP requests and responses.  A bidirectional stream ensures that the response can be readily correlated with the request.  This means that the client's first request occurs on QUIC stream 0, with subsequent requests on stream 4, 8, and so on.  In order to permit these streams to open, an HTTP/3 client SHOULD send non-zero values for the QUIC transport parameters "initial_max_stream_data_bidi_local".  An HTTP/3 server SHOULD send non-zero values for the QUIC transport parameters "initial_max_stream_data_bidi_remote" and "initial_max_bidi_streams". It is recommended that "initial_max_bidi_streams" be no smaller than 100, so as to not unnecessarily limit parallelism. </del>  <del> These streams carry frames related to the request/response (see request-response).  When a stream terminates cleanly, if the last frame on the stream was truncated, this MUST be treated as a connection error (see HTTP_MALFORMED_FRAME in http-error-codes). Streams which terminate abruptly may be reset at any point in the frame. </del>  <del> HTTP/3 does not use server-initiated bidirectional streams; clients MUST omit or specify a value of zero for the QUIC transport parameter "initial_max_bidi_streams". </del>  <del> 4.2. </del>  <del> Unidirectional streams, in either direction, are used for a range of purposes.  The purpose is indicated by a stream type, which is sent as a variable-length integer at the start of the stream.  The format and structure of data that follows this integer is determined by the stream type. </del>  <del> Some stream types are reserved (stream-grease).  Two stream types are defined in this document: control streams (control-streams) and push streams (push-streams).  Other stream types can be defined by extensions to HTTP/3; see extensions for more details. </del>  <del> The performance of HTTP/3 connections in the early phase of their lifetime is sensitive to the creation and exchange of data on unidirectional streams.  Endpoints that set low values for the QUIC transport parameters "initial_max_uni_streams" and "initial_max_stream_data_uni" will increase the chance that the remote peer reaches the limit early and becomes blocked.  In particular, the value chosen for "initial_max_uni_streams" should consider that remote peers may wish to exercise reserved stream behaviour (stream-grease).  To reduce the likelihood of blocking, both clients and servers SHOULD send a value of three or greater for the QUIC transport parameter "initial_max_uni_streams", and a value of 1,024 or greater for the QUIC transport parameter "initial_max_stream_data_uni". </del>  <del> If the stream header indicates a stream type which is not supported by the recipient, the remainder of the stream cannot be consumed as the semantics are unknown.  Recipients of unknown stream types MAY trigger a QUIC STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE, but MUST NOT consider such streams to be a connection error of any kind. </del>  <del> Implementations MAY send stream types before knowing whether the peer supports them.  However, stream types which could modify the state or semantics of existing protocol components, including QPACK or other extensions, MUST NOT be sent until the peer is known to support them. </del>  <del> A sender can close or reset a unidirectional stream unless otherwise specified.  A receiver MUST tolerate unidirectional streams being closed or reset prior to the reception of the unidirectional stream header. </del>  <del> 4.2.1. </del>  <del> A control stream is indicated by a stream type of "0x00".  Data on this stream consists of HTTP/3 frames, as defined in frames. </del>  <del> Each side MUST initiate a single control stream at the beginning of the connection and send its SETTINGS frame as the first frame on this stream.  If the first frame of the control stream is any other frame type, this MUST be treated as a connection error of type HTTP_MISSING_SETTINGS.  Only one control stream per peer is permitted; receipt of a second stream which claims to be a control stream MUST be treated as a connection error of type HTTP_WRONG_STREAM_COUNT.  The sender MUST NOT close the control stream, and the receiver MUST NOT request that the sender close the control stream.  If either control stream is closed at any point, this MUST be treated as a connection error of type HTTP_CLOSED_CRITICAL_STREAM. </del>  <del> A pair of unidirectional streams is used rather than a single bidirectional stream.  This allows either peer to send data as soon they are able.  Depending on whether 0-RTT is enabled on the connection, either client or server might be able to send stream data first after the cryptographic handshake completes. </del>  <del> 4.2.2. </del>  <del> A push stream is indicated by a stream type of "0x01", followed by the Push ID of the promise that it fulfills, encoded as a variable- length integer.  The remaining data on this stream consists of HTTP/3 frames, as defined in frames, and fulfills a promised server push. Server push and Push IDs are described in server-push. </del>  <del> Only servers can push; if a server receives a client-initiated push stream, this MUST be treated as a connection error of type HTTP_WRONG_STREAM_DIRECTION. </del>  <del> 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 stream header, the client MUST treat this as a connection error of type HTTP_DUPLICATE_PUSH. </del>  <del> 4.2.3. </del>  <del> Stream types of the format "0x1f * N + 0x21" for integer values of N are reserved to exercise the requirement that unknown types be ignored.  These streams have no semantics, and can be sent when application-layer padding is desired.  They MAY also be sent on connections where no data is currently being transferred.  Endpoints MUST NOT consider these streams to have any meaning upon receipt. </del>  <del> The payload and length of the stream are selected in any manner the implementation chooses. </del>  <del> 5. </del>  <del> HTTP frames are carried on QUIC streams, as described in stream- mapping.  HTTP/3 defines three stream types: control stream, request stream, and push stream.  This section describes HTTP/3 frame formats and the streams types on which they are permitted; see stream-frame- mapping for an overiew.  A comparison between HTTP/2 and HTTP/3 frames is provided in h2-frames. </del>  <del> Certain frames can only occur as the first frame of a particular stream type; these are indicated in stream-frame-mapping with a (1). Specific guidance is provided in the relevant section. </del>  <del> Note that, unlike QUIC frames, HTTP/3 frames can span multiple packets. </del>  <del> 5.1. </del>  <del> All frames have the following format: </del>  <del> A frame includes the following fields: </del>  <del> A variable-length integer that identifies the frame type. </del>  <del> A variable-length integer that describes the length of the Frame Payload. </del>  <del> A payload, the semantics of which are determined by the Type field. </del>  <del> Each frame's payload MUST contain exactly the fields identified in its description.  A frame payload that contains additional bytes after the identified fields or a frame payload that terminates before the end of the identified fields MUST be treated as a connection error of type HTTP_MALFORMED_FRAME. </del>  <del> 5.2. </del>  <del> 5.2.1. </del>  <del> DATA frames (type=0x0) convey arbitrary, variable-length sequences of bytes associated with an HTTP request or response payload. </del>  <del> DATA frames MUST be associated with an HTTP request or response.  If a DATA frame is received on either control stream, the recipient MUST respond with a connection error (errors) of type HTTP_WRONG_STREAM. </del>  <del> 5.2.2. </del>  <del> The HEADERS frame (type=0x1) is used to carry a header block, compressed using QPACK.  See QPACK for more details. </del>  <del> HEADERS frames can only be sent on request / push streams. </del>  <del> 5.2.3. </del>  <del> The PRIORITY (type=0x2) frame specifies the client-advised priority of a request, server push or placeholder. </del>  <del> A PRIORITY frame identifies an element to prioritize, and an element upon which it depends.  A Prioritized ID or Dependency ID identifies a client-initiated request using the corresponding stream ID, a server push using a Push ID (see frame-push-promise), or a placeholder using a Placeholder ID (see placeholders). </del>  <del> When a client initiates a request, a PRIORITY frame MAY be sent as the first frame of the stream, creating a dependency on an existing element.  In order to ensure that prioritization is processed in a consistent order, any subsequent PRIORITY frames for that request MUST be sent on the control stream.  A PRIORITY frame received after other frames on a request stream MUST be treated as a connection error of type HTTP_UNEXPECTED_FRAME. </del>  <del> If, by the time a new request stream is opened, its priority information has already been received via the control stream, the PRIORITY frame sent on the request stream MUST be ignored. </del>  <del> The PRIORITY frame payload has the following fields: </del>  <del> A two-bit field indicating the type of element being prioritized (see prioritized-element-types).  When sent on a request stream, this MUST be set to "11".  When sent on the control stream, this MUST NOT be set to "11". </del>  <del> A two-bit field indicating the type of element being depended on (see element-dependency-types). </del>  <del> A four-bit field which MUST be zero when sent and has no semantic value on receipt. </del>  <del> A variable-length integer that identifies the element being prioritized.  Depending on the value of Prioritized Type, this contains the Stream ID of a request stream, the Push ID of a promised resource, a Placeholder ID of a placeholder, or is absent. </del>  <del> A variable-length integer that identifies the element on which a dependency is being expressed.  Depending on the value of Dependency Type, this contains the Stream ID of a request stream, the Push ID of a promised resource, the Placeholder ID of a placeholder, or is absent.  For details of dependencies, see priority and HTTP2, Section 5.3. </del>  <del> An unsigned 8-bit integer representing a priority weight for the prioritized element (see HTTP2, Section 5.3).  Add one to the value to obtain a weight between 1 and 256. </del>  <del> The values for the Prioritized Element Type (prioritized-element- types) and Element Dependency Type (element-dependency-types) imply the interpretation of the associated Element ID fields. </del>  <del> Note that unlike in HTTP2, the root of the tree cannot be referenced using a Stream ID of 0, as in QUIC stream 0 carries a valid HTTP request.  The root of the tree cannot be reprioritized. </del>  <del> The PRIORITY frame can express relationships which might not be permitted based on the stream on which it is sent or its position in the stream.  These situations MUST be treated as a connection error of type HTTP_MALFORMED_FRAME.  The following situations are examples of invalid PRIORITY frames: </del>  <del> A PRIORITY frame sent on a request stream with the Prioritized Element Type set to any value other than "11" </del>  <del> A PRIORITY frame sent on a request stream which expresses a dependency on a request with a greater Stream ID than the current stream </del>  <del> A PRIORITY frame sent on a control stream with the Prioritized Element Type set to "11" </del>  <del> A PRIORITY frame which claims to reference a request, but the associated ID does not identify a client-initiated bidirectional stream </del>  <del> A PRIORITY frame with Empty bits not set to zero MAY be treated as a connection error of type HTTP_MALFORMED_FRAME. </del>  <del> A PRIORITY frame that references a non-existent Push ID, a Placeholder ID greater than the server's limit, or a Stream ID the client is not yet permitted to open MUST be treated as a connection error of type HTTP_LIMIT_EXCEEDED. </del>  <del> A PRIORITY frame received on any stream other than a request or control stream MUST be treated as a connection error of type HTTP_WRONG_STREAM. PRIORITY frames received by a client MUST be treated as a connection error of type HTTP_UNEXPECTED_FRAME. 5.2.4. 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 frame identifies a server push by Push ID (see frame-push-promise), encoded as a variable-length integer. When a server receives this frame, it aborts sending the response for 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 to avoid opening a push stream.  If the push stream has been opened by the server, the server SHOULD send a QUIC RESET_STREAM frame on that stream and cease transmission of the response. A server can send the CANCEL_PUSH frame to indicate that it will not be fulfilling a promise prior to creation of a push stream.  Once the push stream has been created, sending CANCEL_PUSH has no effect on the state of the push stream.  A QUIC RESET_STREAM frame SHOULD be used instead to abort transmission of the server push response. 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 treated as a connection error of type HTTP_WRONG_STREAM. The CANCEL_PUSH frame carries a Push ID encoded as a variable-length integer.  The Push ID identifies the server push that is being cancelled (see frame-push-promise). 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. 5.2.5. The SETTINGS frame (type=0x4) conveys configuration parameters that affect how endpoints communicate, such as preferences and constraints on peer behavior.  Individually, a SETTINGS parameter can also be referred to as a "setting"; the identifier and value of each setting parameter can be referred to as a "setting identifier" and a "setting value". SETTINGS frames always apply to a connection, never a single stream. A SETTINGS frame MUST be sent as the first frame of each control stream (see control-streams) by each peer, and MUST NOT be sent subsequently or on any other stream.  If an endpoint receives a SETTINGS frame on a different stream, the endpoint MUST respond with a connection error of type HTTP_WRONG_STREAM.  If an endpoint receives a second SETTINGS frame, the endpoint MUST respond with a connection error of type HTTP_UNEXPECTED_FRAME. SETTINGS parameters are not negotiated; they describe characteristics of the sending peer, which can be used by the receiving peer. However, a negotiation can be implied by the use of SETTINGS - each peer uses SETTINGS to advertise a set of supported values.  The definition of the setting would describe how each peer combines the two sets to conclude which choice will be used.  SETTINGS does not provide a mechanism to identify when the choice takes effect. Different values for the same parameter can be advertised by each peer.  For example, a client might be willing to consume a very large response header, while servers are more cautious about request size. Parameters MUST NOT occur more than once in the SETTINGS frame.  A receiver MAY treat the presence of the same parameter more than once as a connection error of type HTTP_MALFORMED_FRAME. </del>  <del> The payload of a SETTINGS frame consists of zero or more parameters. Each parameter consists of a setting identifier and a value, both encoded as QUIC variable-length integers. </del>  <del> An implementation MUST ignore the contents for any SETTINGS identifier it does not understand. </del>  <del> 5.2.5.1. </del>  <del> The following settings are defined in HTTP/3: </del>  <del> The default value is unlimited.  See header-formatting for usage. </del>  <del> The default value is 0.  However, this value SHOULD be set to a non-zero value by servers.  See placeholders for usage. </del>  <del> Setting identifiers of the format "0x1f * N + 0x21" for integer values of N are reserved to exercise the requirement that unknown identifiers be ignored.  Such settings have no defined meaning. Endpoints SHOULD include at least one such setting in their SETTINGS frame.  Endpoints MUST NOT consider such settings to have any meaning upon receipt. </del>  <del> Because the setting has no defined meaning, the value of the setting can be any value the implementation selects. </del>  <del> Additional settings can be defined by extensions to HTTP/3; see extensions for more details. </del>  <del> 5.2.5.2. </del>  <del> An HTTP implementation MUST NOT send frames or requests which would be invalid based on its current understanding of the peer's settings. All settings begin at an initial value, and are updated upon receipt of a SETTINGS frame.  For servers, the initial value of each client setting is the default value. </del>  <del> For clients using a 1-RTT QUIC connection, the initial value of each server setting is the default value.  When a 0-RTT QUIC connection is being used, the initial value of each server setting is the value used in the previous session.  Clients MUST store the settings the server provided in the session being resumed and MUST comply with stored settings until the current server settings are received. </del>  <del> A server can remember the settings that it advertised, or store an integrity-protected copy of the values in the ticket and recover the information when accepting 0-RTT data.  A server uses the HTTP/3 settings values in determining whether to accept 0-RTT data. </del>  <del> A server MAY accept 0-RTT and subsequently provide different settings in its SETTINGS frame.  If 0-RTT data is accepted by the server, its SETTINGS frame MUST NOT reduce any limits or alter any values that might be violated by the client with its 0-RTT data. </del>  <del> 5.2.6. </del>  <del> The PUSH_PROMISE frame (type=0x5) is used to carry a promised request header set from server to client on a request stream, as in HTTP/2. </del>  <del> The payload consists of: </del>  <del> A variable-length integer that identifies the server push operation.  A Push ID is used in push stream headers (server- push), CANCEL_PUSH frames (frame-cancel-push), DUPLICATE_PUSH frames (frame-duplicate-push), and PRIORITY frames (frame- priority). </del>  <del> QPACK-compressed request header fields for the promised response. See QPACK for more details. </del>  <del> A server MUST NOT use a Push ID that is larger than the client has provided in a MAX_PUSH_ID frame (frame-max-push-id) and MUST NOT use the same Push ID in multiple PUSH_PROMISE frames.  A client MUST treat receipt of a PUSH_PROMISE that contains a larger Push ID than the client has advertised or a Push ID which has already been promised as a connection error of type HTTP_MALFORMED_FRAME. </del>  <del> If a PUSH_PROMISE frame is received on either control stream, the recipient MUST respond with a connection error (errors) of type HTTP_WRONG_STREAM. </del>  <del> See server-push for a description of the overall server push mechanism. </del>  <del> 5.2.7. </del>  <del> The GOAWAY frame (type=0x7) is used to initiate graceful shutdown of a connection by a server.  GOAWAY allows a server to stop accepting new requests while still finishing processing of previously received requests.  This enables administrative actions, like server maintenance.  GOAWAY by itself does not close a connection. </del>  <del> The GOAWAY frame is always sent on the control stream.  It carries a QUIC Stream ID for a client-initiated bidirectional stream encoded as 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 of type HTTP_WRONG_STREAM. </del>  <del> Clients do not need to send GOAWAY to initiate a graceful shutdown; they simply stop making new requests.  A server MUST treat receipt of a GOAWAY frame on any stream as a connection error (errors) of type HTTP_UNEXPECTED_FRAME. </del>  <del> The GOAWAY frame applies to the connection, not a specific stream.  A client MUST treat a GOAWAY frame on a stream other than the control stream as a connection error (errors) of type HTTP_UNEXPECTED_FRAME. </del>  <del> See connection-shutdown for more information on the use of the GOAWAY frame. </del>  <del> 5.2.8. </del>  <del> 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 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 that the server can initiate in addition to the limit set by the QUIC MAX_STREAMS frame. </del>  <del> The MAX_PUSH_ID frame is always sent on the control stream.  Receipt of a MAX_PUSH_ID frame on any other stream MUST be treated as a connection error of type HTTP_WRONG_STREAM. </del>  <del> 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 HTTP_UNEXPECTED_FRAME. </del>  <del> 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 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 server fulfills or cancels server pushes. </del>  <del> 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 (see frame-push-promise).  A MAX_PUSH_ID frame cannot reduce the maximum 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 HTTP_MALFORMED_FRAME. </del>  <del> 5.2.9. </del>  <del> The DUPLICATE_PUSH frame (type=0xE) is used by servers to indicate that an existing pushed resource is related to multiple client requests. </del>  <del> The DUPLICATE_PUSH frame is always sent on a request stream.  Receipt of a DUPLICATE_PUSH frame on any other stream MUST be treated as a connection error of type HTTP_WRONG_STREAM. </del>  <del> 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 HTTP_UNEXPECTED_FRAME. </del>  <del> The DUPLICATE_PUSH frame carries a single variable-length integer that identifies the Push ID of a resource that the server has previously promised (see frame-push-promise), though that promise might 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 (frame-max-push-id).  A client MUST treat receipt of a DUPLICATE_PUSH that contains a larger Push ID than the client has advertised as a connection error of type HTTP_MALFORMED_FRAME. </del>  <del> This frame allows the server to use the same server push in response to multiple concurrent requests.  Referencing the same server push ensures that a promise can be made in relation to every response in which server push might be needed without duplicating request headers or pushed responses. </del>  <del> Allowing duplicate references to the same Push ID is primarily to reduce duplication caused by concurrent requests.  A server SHOULD avoid reusing a Push ID over a long period.  Clients are likely to consume server push responses and not retain them for reuse over time.  Clients that see a DUPLICATE_PUSH that uses a Push ID that they have since consumed and discarded are forced to ignore the DUPLICATE_PUSH. </del>  <del> 5.2.10. </del>  <del> Frame types of the format "0x1f * N + 0x21" for integer values of N </del>  are reserved to exercise the requirement that unknown types be <del> ignored (extensions).  These frames have no semantics, and can be sent when application-layer padding is desired.  They MAY also be sent on connections where no data is currently being transferred. Endpoints MUST NOT consider these frames to have any meaning upon receipt. </del>  <del> The payload and length of the frames are selected in any manner the </del>  implementation chooses. <del> 6. </del>  <del> 6.1. </del>  <del> A client sends an HTTP request on a client-initiated bidirectional QUIC stream.  A client MUST send only a single request on a given stream.  A server sends zero or more non-final HTTP responses on the same stream as the request, followed by a single final HTTP response, as detailed below. </del>  <del> An HTTP message (request or response) consists of: </del>  <del> the message header (see RFC7230, Section 3.2), sent as a single HEADERS frame (see frame-headers), </del>  <del> the payload body (see RFC7230, Section 3.3), sent as a series of DATA frames (see frame-data), </del>  <del> optionally, one HEADERS frame containing the trailer-part, if present (see RFC7230, Section 4.1.2). </del>  <del> A server MAY interleave one or more PUSH_PROMISE frames (see frame- push-promise) with the frames of a response message.  These PUSH_PROMISE frames are not part of the response; see server-push for more details. </del>  <del> The HEADERS and PUSH_PROMISE frames might reference updates to the QPACK dynamic table.  While these updates are not directly part of the message exchange, they must be received and processed before the message can be consumed.  See header-formatting for more details. </del>  <del> The "chunked" transfer encoding defined in Section 4.1 of RFC7230 MUST NOT be used. </del>  <del> Trailing header fields are carried in an additional HEADERS frame following the body.  Senders MUST send only one HEADERS frame in the trailers section; receivers MUST discard any subsequent HEADERS frames. </del>  <del> A response MAY consist of multiple messages when and only when one or more informational responses (1xx; see RFC7231, Section 6.2) precede a final response to the same request.  Non-final responses do not contain a payload body or trailers. </del>  <del> An HTTP request/response exchange fully consumes a bidirectional QUIC stream.  After sending a request, a client MUST close the stream for sending.  Unless using the CONNECT method (see the-connect-method), clients MUST NOT make stream closure dependent on receiving a response to their request.  After sending a final response, the server MUST close the stream for sending.  At this point, the QUIC stream is fully closed. </del>  <del> When a stream is closed, this indicates the end of an HTTP message. Because some messages are large or unbounded, endpoints SHOULD begin processing partial HTTP messages once enough of the message has been received to make progress.  If a client stream terminates without enough of the HTTP message to provide a complete response, the server SHOULD abort its response with the error code HTTP_INCOMPLETE_REQUEST. </del>  <del> 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 request that has not been sent and received.  When this is true, a server MAY request that the client abort transmission of a request without error by triggering a QUIC STOP_SENDING frame with error code HTTP_EARLY_RESPONSE, sending a complete response, and cleanly closing its stream.  Clients MUST NOT discard complete responses as a result of having their request terminated abruptly, though clients can always discard responses at their discretion for other reasons. </del>  <del> 6.1.1. </del>  <del> HTTP message headers carry information as a series of key-value pairs, called header fields.  For a listing of registered HTTP header fields, see the "Message Header Field" registry maintained at https://www.iana.org/assignments/message-headers [4]. </del>  <del> Just as in previous versions of HTTP, header field names are strings of ASCII characters that are compared in a case-insensitive fashion. Properties of HTTP header field names and values are discussed in more detail in Section 3.2 of RFC7230, though the wire rendering in HTTP/3 differs.  As in HTTP/2, header field names MUST be converted to lowercase prior to their encoding.  A request or response containing uppercase header field names MUST be treated as malformed. </del>  <del> As in HTTP/2, HTTP/3 uses special pseudo-header fields beginning with the ':' character (ASCII 0x3a) to convey the target URI, the method of the request, and the status code for the response.  These pseudo- header fields are defined in Section 8.1.2.3 and 8.1.2.4 of HTTP2. Pseudo-header fields are not HTTP header fields.  Endpoints MUST NOT generate pseudo-header fields other than those defined in HTTP2.  The restrictions on the use of pseudo-header fields in Section 8.1.2.1 of HTTP2 also apply to HTTP/3. </del>  <del> HTTP/3 uses QPACK header compression as described in QPACK, a variation of HPACK which allows the flexibility to avoid header- compression-induced head-of-line blocking.  See that document for additional details. </del>  <del> An HTTP/3 implementation MAY impose a limit on the maximum size of the header it will accept on an individual HTTP message; encountering a larger message header SHOULD be treated as a stream error of type "HTTP_EXCESSIVE_LOAD".  If an implementation wishes to advise its peer of this limit, it can be conveyed as a number of bytes in the "SETTINGS_MAX_HEADER_LIST_SIZE" parameter.  The size of a header list is calculated based on the uncompressed size of header fields, including the length of the name and value in bytes plus an overhead of 32 bytes for each header field. </del>  <del> 6.1.2. </del>  <del> Clients can cancel requests by aborting the stream (QUIC RESET_STREAM and/or STOP_SENDING frames, as appropriate) with an error code of HTTP_REQUEST_CANCELLED (http-error-codes).  When the client cancels a response, it indicates that this response is no longer of interest. Implementations SHOULD cancel requests by aborting both directions of a stream. </del>  <del> When the server rejects a request without performing any application processing, it SHOULD abort its response stream with the error code HTTP_REQUEST_REJECTED.  In this context, "processed" means that some data from the stream was passed to some higher layer of software that might have taken some action as a result.  The client can treat requests rejected by the server as though they had never been sent at all, thereby allowing them to be retried later on a new connection. Servers MUST NOT use the HTTP_REQUEST_REJECTED error code for requests which were partially or fully processed.  When a server abandons a response after partial processing, it SHOULD abort its response stream with the error code HTTP_REQUEST_CANCELLED. </del>  <del> When a client sends a STOP_SENDING with HTTP_REQUEST_CANCELLED, a server MAY send the error code HTTP_REQUEST_REJECTED in the corresponding RESET_STREAM if no processing was performed.  Clients MUST NOT reset streams with the HTTP_REQUEST_REJECTED error code except in response to a QUIC STOP_SENDING frame that contains the same code. </del>  <del> If a stream is cancelled after receiving a complete response, the client MAY ignore the cancellation and use the response.  However, if a stream is cancelled after receiving a partial response, the response SHOULD NOT be used.  Automatically retrying such requests is not possible, unless this is otherwise permitted (e.g., idempotent actions like GET, PUT, or DELETE). </del>  <del> 6.2. </del>  <del> The pseudo-method CONNECT (RFC7231, Section 4.3.6) is primarily used with HTTP proxies to establish a TLS session with an origin server for the purposes of interacting with "https" resources.  In 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 establish a tunnel over a single HTTP/2 stream to a remote host for similar purposes. </del>  <del> A CONNECT request in HTTP/3 functions in the same manner as in HTTP/2.  The request MUST be formatted as described in HTTP2, Section 8.3.  A CONNECT request that does not conform to these restrictions is malformed.  The request stream MUST NOT be closed at the end of the request. </del>  <del> A proxy that supports CONNECT establishes a TCP connection (RFC0793) to the server identified in the ":authority" pseudo-header field. Once this connection is successfully established, the proxy sends a HEADERS frame containing a 2xx series status code to the client, as defined in RFC7231, Section 4.3.6. </del>  <del> All DATA frames on the stream correspond to data sent or received on the TCP connection.  Any DATA frame sent by the client is transmitted by the proxy to the TCP server; data received from the TCP server is packaged into DATA frames by the proxy.  Note that the size and number of TCP segments is not guaranteed to map predictably to the size and number of HTTP DATA or QUIC STREAM frames. </del>  <del> The TCP connection can be closed by either peer.  When the client ends the request stream (that is, the receive stream at the proxy enters the "Data Recvd" state), the proxy will set the FIN bit on its 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 client.  TCP connections which remain half-closed in a single direction are not invalid, but are often handled poorly by servers, so clients SHOULD NOT close a stream for sending while they still expect to receive data from the target of the CONNECT. </del>  <del> A TCP connection error is signaled with QUIC RESET_STREAM frame.  A proxy treats any error in the TCP connection, which includes receiving a TCP segment with the RST bit set, as a stream error of type HTTP_CONNECT_ERROR (http-error-codes).  Correspondingly, a proxy MUST send a TCP segment with the RST bit set if it detects an error with the stream or the QUIC connection. </del>  <del> 6.3. </del>  <del> HTTP/3 uses a priority scheme similar to that described in HTTP2, Section 5.3.  In this priority scheme, a given element can be designated as dependent upon another element.  This information is expressed in the PRIORITY frame frame-priority which identifies the element and the dependency.  The elements that can be prioritized are: </del>  <del> Requests, identified by the ID of the request stream </del>  <del> Pushes, identified by the Push ID of the promised resource (frame- push-promise) </del>  <del> Placeholders, identified by a Placeholder ID </del>  <del> Taken together, the dependencies across all prioritized elements in a connection form a dependency tree.  An element can depend on another element or on the root of the tree.  A reference to an element which is no longer in the tree is treated as a reference to the root of the tree.  The structure of the dependency tree changes as PRIORITY frames modify the dependency links between prioritized elements. </del>  <del> Due to reordering between streams, an element can also be prioritized which is not yet in the tree.  Such elements are added to the tree with the requested priority. </del>  <del> When a prioritized element is first created, it has a default initial weight of 16 and a default dependency.  Requests and placeholders are dependent on the root of the priority tree; pushes are dependent on the client request on which the PUSH_PROMISE frame was sent. </del>  <del> Requests may override the default initial values by including a PRIORITY frame (see frame-priority) at the beginning of the stream. These priorities can be updated by sending a PRIORITY frame on the control stream. </del>  <del> 6.3.1. </del>  <del> In HTTP/2, certain implementations used closed or unused streams as placeholders in describing the relative priority of requests.  This created confusion as servers could not reliably identify which elements of the priority tree could be discarded safely.  Clients could potentially reference closed streams long after the server had discarded state, leading to disparate views of the prioritization the client had attempted to express. </del>  <del> In HTTP/3, a number of placeholders are explicitly permitted by the server using the "SETTINGS_NUM_"S" setting.  Because the server commits to maintaining these placeholders in the prioritization tree, clients can use them with confidence that the server will not have discarded the state.  Clients MUST NOT send the "SETTINGS_NUM_"S" setting; receipt of this setting by a server MUST be treated as a connection error of type "HTTP_WRONG_SETTING_DIRECTION". </del>  <del> Placeholders are identified by an ID between zero and one less than the number of placeholders the server has permitted. </del>  <del> Like streams, placeholders have priority information associated with them. </del>  <del> 6.3.2. </del>  <del> Because placeholders will be used to "root" any persistent structure of the tree which the client cares about retaining, servers can aggressively prune inactive regions from the priority tree.  For prioritization purposes, a node in the tree is considered "inactive" when the corresponding stream has been closed for at least two round- trip times (using any reasonable estimate available on the server). This delay helps mitigate race conditions where the server has pruned a node the client believed was still active and used as a Stream Dependency. </del>  <del> Specifically, the server MAY at any time: </del>  <del> Identify and discard branches of the tree containing only inactive nodes (i.e. a node with only other inactive nodes as descendants, along with those descendants) </del>  <del> Identify and condense interior regions of the tree containing only inactive nodes, allocating weight appropriately </del>  <del> In the example in fig-pruning, "P" represents a Placeholder, "A" represents an active node, and "I" represents an inactive node.  In the first step, the server discards two inactive branches (each a single node).  In the second step, the server condenses an interior inactive node.  Note that these transformations will result in no change in the resources allocated to a particular active stream. </del>  <del> Clients SHOULD assume the server is actively performing such pruning and SHOULD NOT declare a dependency on a stream it knows to have been closed. </del>  <del> 6.4. </del>  <del> HTTP/3 server push is similar to what is described in HTTP/2 HTTP2, but uses different mechanisms. </del>  <del> Each server push is identified by a unique Push ID.  This Push ID is used in a single PUSH_PROMISE frame (see frame-push-promise) which carries the request headers, possibly included in one or more DUPLICATE_PUSH frames (see frame-duplicate-push), then included with the push stream which ultimately fulfills those promises. </del>  <del> Server push is only enabled on a connection when a client sends a MAX_PUSH_ID frame (see frame-max-push-id).  A server cannot use server push until it receives a MAX_PUSH_ID frame.  A client sends additional MAX_PUSH_ID frames to control the number of pushes that a server can promise.  A server SHOULD use Push IDs sequentially, starting at 0.  A client MUST treat receipt of a push stream with a Push ID that is greater than the maximum Push ID as a connection error of type HTTP_LIMIT_EXCEEDED. </del>  <del> The header of the request message is carried by a PUSH_PROMISE frame (see frame-push-promise) on the request stream which generated the push.  This allows the server push to be associated with a client request.  Ordering of a PUSH_PROMISE in relation to certain parts of the response is important (see Section 8.2.1 of HTTP2).  Promised requests MUST conform to the requirements in Section 8.2 of HTTP2. </del>  <del> The same server push can be associated with additional client requests using a DUPLICATE_PUSH frame (see frame-duplicate-push). Ordering of a DUPLICATE_PUSH in relation to certain parts of the response is similarly important. </del>  <del> When a server later fulfills a promise, the server push response is conveyed on a push stream (see push-streams).  The push stream identifies the Push ID of the promise that it fulfills, then contains a response to the promised request using the same format described for responses in request-response. </del>  <del> Due to reordering, DUPLICATE_PUSH frames or push stream data can arrive before the corresponding PUSH_PROMISE frame.  When a client receives a DUPLICATE_PUSH frame for an as-yet-unknown Push ID, the request headers of the push are not immediately available.  The client can either delay generating new requests for content referenced following the DUPLICATE_PUSH frame until the request headers become available, or can initiate requests for discovered resources and cancel the requests if the requested resource is already being pushed.  When a client receives a new push stream with an as-yet-unknown Push ID, both the associated client request and the pushed request headers are unknown.  The client can buffer the stream data in expectation of the matching PUSH_PROMISE.  The client can use stream flow control (see section 4.1 of QUIC-TRANSPORT) to limit the amount of data a server may commit to the pushed stream. </del>  <del> 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 or opens after sending the CANCEL_PUSH frame, a QUIC STOP_SENDING frame with an appropriate error code can also be used (e.g., HTTP_PUSH_REFUSED, HTTP_PUSH_ALREADY_IN_CACHE; see errors).  This asks the server not to transfer additional data and indicates that it will be discarded upon receipt. </del>  <del> 7. </del>  <del> Once established, an HTTP/3 connection can be used for many requests and responses over time until the connection is closed.  Connection closure can happen in any of several different ways. </del>  <del> 7.1. </del>  <del> Each QUIC endpoint declares an idle timeout during the handshake.  If the connection remains idle (no packets received) for longer than this duration, the peer will assume that the connection has been closed.  HTTP/3 implementations will need to open a new connection for new requests if the existing connection has been idle for longer than the server's advertised idle timeout, and SHOULD do so if approaching the idle timeout. </del>  <del> HTTP clients are expected to request that the transport keep connections open while there are responses outstanding for requests or server pushes, as described in Section 19.2 of QUIC-TRANSPORT.  If the client is not expecting a response from the server, allowing an idle connection to time out is preferred over expending effort maintaining a connection that might not be needed.  A gateway MAY maintain connections in anticipation of need rather than incur the latency cost of connection establishment to servers.  Servers SHOULD NOT actively keep connections open. </del>  <del> 7.2. </del>  <del> Even when a connection is not idle, either endpoint can decide to stop using the connection and let the connection close gracefully. Since clients drive request generation, clients perform a connection shutdown by not sending additional requests on the connection; responses and pushed responses associated to previous requests will continue to completion.  Servers perform the same function by communicating with clients. </del>  <del> Servers initiate the shutdown of a connection by sending a GOAWAY frame (frame-goaway).  The GOAWAY frame indicates that client- initiated requests on lower stream IDs were or might be processed in this connection, while requests on the indicated stream ID and greater were rejected.  This enables client and server to agree on which requests were accepted prior to the connection shutdown.  This identifier MAY be lower than the stream limit identified by a QUIC MAX_STREAM_ID frame, and MAY be zero if no requests were processed. Servers SHOULD NOT increase the QUIC MAX_STREAM_ID limit after sending a GOAWAY frame. </del>  <del> Clients MUST NOT send new requests on the connection after receiving GOAWAY; a new connection MAY be established to send additional requests. </del>  <del> Some requests might already be in transit.  If the client has already sent requests on streams with a Stream ID greater than or equal to that indicated in the GOAWAY frame, those requests will not be processed and MAY be retried by the client on a different connection. The client MAY cancel these requests.  It is RECOMMENDED that the server explicitly reject such requests (see request-cancellation) in order to clean up transport state for the affected streams. </del>  <del> Requests on Stream IDs less than the Stream ID in the GOAWAY frame might have been processed; their status cannot be known until a response is received, the stream is reset individually, or the connection terminates.  Servers MAY reject individual requests on streams below the indicated ID if these requests were not processed. </del>  <del> Servers SHOULD send a GOAWAY frame when the closing of a connection is known in advance, even if the advance notice is small, so that the remote peer can know whether a request has been partially processed or not.  For example, if an HTTP client sends a POST at the same time that a server closes a QUIC connection, the client cannot know if the server started to process that POST request if the server does not send a GOAWAY frame to indicate what streams it might have acted on. </del>  <del> A client that is unable to retry requests loses all requests that are in flight when the server closes the connection.  A server MAY send multiple GOAWAY frames indicating different stream IDs, but MUST NOT increase the value they send in the last Stream ID, since clients might already have retried unprocessed requests on another connection.  A server that is attempting to gracefully shut down a connection SHOULD send an initial GOAWAY frame with the last Stream ID set to the current value of QUIC's MAX_STREAM_ID and SHOULD NOT increase the MAX_STREAM_ID thereafter.  This signals to the client that a shutdown is imminent and that initiating further requests is prohibited.  After allowing time for any in-flight requests (at least one round-trip time), the server MAY send another GOAWAY frame with an updated last Stream ID.  This ensures that a connection can be cleanly shut down without losing requests. </del>  <del> Once all accepted requests have been processed, the server can permit the connection to become idle, or MAY initiate an immediate closure of the connection.  An endpoint that completes a graceful shutdown SHOULD use the HTTP_NO_ERROR code when closing the connection. </del>  <del> If a client has consumed all available bidirectional stream IDs with requests, the server need not send a GOAWAY frame, since the client is unable to make further requests. </del>  <del> 7.3. </del>  <del> An HTTP/3 implementation can immediately close the QUIC connection at any time.  This results in sending a QUIC CONNECTION_CLOSE frame to the peer; the error code in this frame indicates to the peer why the connection is being closed.  See errors for error codes which can be used when closing a connection. </del>  <del> Before closing the connection, a GOAWAY MAY be sent to allow the client to retry some requests.  Including the GOAWAY frame in the same packet as the QUIC CONNECTION_CLOSE frame improves the chances of the frame being received by clients. </del>  <del> 7.4. </del>  <del> For various reasons, the QUIC transport could indicate to the application layer that the connection has terminated.  This might be due to an explicit closure by the peer, a transport-level error, or a change in network topology which interrupts connectivity. </del>  <del> If a connection terminates without a GOAWAY frame, clients MUST assume that any request which was sent, whether in whole or in part, might have been processed. </del>  <del> 8. </del>  <del> HTTP/3 permits extension of the protocol.  Within the limitations described in this section, protocol extensions can be used to provide additional services or alter any aspect of the protocol.  Extensions are effective only within the scope of a single HTTP/3 connection. </del>  <del> This applies to the protocol elements defined in this document.  This does not affect the existing options for extending HTTP, such as defining new methods, status codes, or header fields. </del>  <del> Extensions are permitted to use new frame types (frames), new settings (settings-parameters), new error codes (errors), or new unidirectional stream types (unidirectional-streams).  Registries are established for managing these extension points: frame types (iana- frames), settings (iana-settings), error codes (iana-error-codes), and stream types (iana-stream-types). </del>  <del> Implementations MUST ignore unknown or unsupported values in all extensible protocol elements.  Implementations MUST discard frames and unidirectional streams that have unknown or unsupported types. This means that any of these extension points can be safely used by extensions without prior arrangement or negotiation. </del>  <del> Extensions that could change the semantics of existing protocol components MUST be negotiated before being used.  For example, an extension that changes the layout of the HEADERS frame cannot be used until the peer has given a positive signal that this is acceptable. In this case, it could also be necessary to coordinate when the revised layout comes into effect. </del>  <del> This document doesn't mandate a specific method for negotiating the use of an extension but notes that a setting (settings-parameters) could be used for that purpose.  If both peers set a value that indicates willingness to use the extension, then the extension can be used.  If a setting is used for extension negotiation, the default value MUST be defined in such a fashion that the extension is disabled if the setting is omitted. </del>  <del> 9. </del>  QUIC allows the application to abruptly terminate (reset) individual streams or the entire connection when an error is encountered.  These This section describes HTTP/3-specific error codes which can be used to express the cause of a connection or stream error. <del> 9.1. </del>  The following error codes are defined for use in QUIC RESET_STREAM frames, STOP_SENDING frames, and CONNECTION_CLOSE frames when using with the code (0x10D).  The last byte "0xff" is used to indicate any frame type greater than "0xfe".  10. The security considerations of HTTP/3 should be comparable to those

no text changes outside the Document Organization section.
Wow, this is a fun diff to review :-)
That's why I pointed out that there are no actual text changes. But if it's easier, you could open and in side-by-side browser windows. :-) I'd like to land this fairly quickly; from some experiments, other HTTP PRs merge into this just fine if they come after, but risk being summarily wiped out if merged before it.
It's fine. The stream usage and request "lifecycle" sections are a bit too far apart, but I don't know that I have a suggestion there.
S 3.2.2. This isn't understandable without knowing what push is or what a PUSH promise is. Am I supposed to get that from 7540? In either case, you should clearly state that a push stream can only be used for a single push promise (this is implied by the formatting). Happy to supply a PR if we can agree on what's wanted?
Yes, as currently written, a push stream corresponds 1:1 with a PUSH_PROMISE. Which is consistent again with 7540 (we had a period where it was not).
Well. A push stream corresponds one-to-one with a push ID. You can duplicate promises using the DUPLICATE_PUSH frame. I think this is what was attempted to be described by the term "promised server push" as abstract from the frames that might get sent. If the language needs to improve to make this clearer then lets do it.
Does address this sufficiently, now that the description of push precedes this section? There's already a back-reference at the end of the paragraph if someone needs more details.
Closing; please reopen if you feel that does not sufficiently address this.
It would be a lot easier to read the spec if the lifecycle (which provides an overview of operation implicitly) came before the packet formats. Happy to provide a PR, but no point if the editors don't want it.
Thanks for the suggestion. I can see this either way. The ordering was intended to follow the HTTP/2 pattern of "framing layer, putting HTTP on the framing layer." The QUIC spec's new layout of successive layers of detail (concepts, then specific mechanisms, then wire format) would suggest putting frame specifics last. PR not necessary -- it's a straightforward change if we decide to reorder this way.
I just suggested this change the other day, because I had the same issue. In particular, talking about the multiple push frames before introducing what push is is very awkward.
I like this new layout.Thanks Mike, this works for me!

2.1.  <ins> The HTTP/3 specification is split into seven parts.  The document begins with a detailed overview of the connection lifecycle and key concepts: </ins> Connection Setup and Management (connection-setup) covers how an HTTP/3 endpoint is discovered and a connection is established.  HTTP Request Lifecycle (http-request-lifecycle) describes how HTTP semantics are expressed using frames. Connection Closure (connection-closure) describes how connections are terminated, either gracefully or abruptly.  <ins> The details of the wire protocol and interactions with the transport are described in subsequent sections: Stream Mapping and Usage (stream-mapping) describes the way QUIC streams are used. HTTP Framing Layer (http-framing-layer) describes the frames used on most streams. </ins> Error Handling (errors) describes how error conditions are handled and expressed, either on a particular stream or for the connection as a whole.  <ins> Additional resources are provided in the final sections: Extensions to HTTP/3 (extensions) describes how new capabilities can be added in future documents. A more detailed comparison between HTTP/2 and HTTP/3 can be found in h2-considerations. </ins> 2.2. 4.  <ins> 4.1. </ins>  <ins> A client sends an HTTP request on a client-initiated bidirectional QUIC stream.  A client MUST send only a single request on a given stream.  A server sends zero or more non-final HTTP responses on the same stream as the request, followed by a single final HTTP response, as detailed below. </ins>  <ins> An HTTP message (request or response) consists of: </ins>  <ins> the message header (see RFC7230, Section 3.2), sent as a single HEADERS frame (see frame-headers), </ins>  <ins> the payload body (see RFC7230, Section 3.3), sent as a series of DATA frames (see frame-data), </ins>  <ins> optionally, one HEADERS frame containing the trailer-part, if present (see RFC7230, Section 4.1.2). </ins>  <ins> A server MAY interleave one or more PUSH_PROMISE frames (see frame- push-promise) with the frames of a response message.  These PUSH_PROMISE frames are not part of the response; see server-push for more details. </ins>  <ins> The HEADERS and PUSH_PROMISE frames might reference updates to the QPACK dynamic table.  While these updates are not directly part of the message exchange, they must be received and processed before the message can be consumed.  See header-formatting for more details. </ins>  <ins> The "chunked" transfer encoding defined in Section 4.1 of RFC7230 MUST NOT be used. </ins>  <ins> Trailing header fields are carried in an additional HEADERS frame following the body.  Senders MUST send only one HEADERS frame in the trailers section; receivers MUST discard any subsequent HEADERS frames. </ins>  <ins> A response MAY consist of multiple messages when and only when one or more informational responses (1xx; see RFC7231, Section 6.2) precede a final response to the same request.  Non-final responses do not contain a payload body or trailers. </ins>  <ins> An HTTP request/response exchange fully consumes a bidirectional QUIC stream.  After sending a request, a client MUST close the stream for sending.  Unless using the CONNECT method (see the-connect-method), clients MUST NOT make stream closure dependent on receiving a response to their request.  After sending a final response, the server MUST close the stream for sending.  At this point, the QUIC stream is fully closed. </ins>  <ins> When a stream is closed, this indicates the end of an HTTP message. Because some messages are large or unbounded, endpoints SHOULD begin processing partial HTTP messages once enough of the message has been received to make progress.  If a client stream terminates without enough of the HTTP message to provide a complete response, the server SHOULD abort its response with the error code HTTP_INCOMPLETE_REQUEST. </ins>  <ins> 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 request that has not been sent and received.  When this is true, a server MAY request that the client abort transmission of a request without error by triggering a QUIC STOP_SENDING frame with error code HTTP_EARLY_RESPONSE, sending a complete response, and cleanly closing its stream.  Clients MUST NOT discard complete responses as a result of having their request terminated abruptly, though clients can always discard responses at their discretion for other reasons. </ins>  <ins> 4.1.1. </ins>  <ins> HTTP message headers carry information as a series of key-value pairs, called header fields.  For a listing of registered HTTP header fields, see the "Message Header Field" registry maintained at https://www.iana.org/assignments/message-headers [4]. </ins>  <ins> Just as in previous versions of HTTP, header field names are strings of ASCII characters that are compared in a case-insensitive fashion. Properties of HTTP header field names and values are discussed in more detail in Section 3.2 of RFC7230, though the wire rendering in HTTP/3 differs.  As in HTTP/2, header field names MUST be converted to lowercase prior to their encoding.  A request or response containing uppercase header field names MUST be treated as malformed. </ins>  <ins> As in HTTP/2, HTTP/3 uses special pseudo-header fields beginning with the ':' character (ASCII 0x3a) to convey the target URI, the method of the request, and the status code for the response.  These pseudo- header fields are defined in Section 8.1.2.3 and 8.1.2.4 of HTTP2. Pseudo-header fields are not HTTP header fields.  Endpoints MUST NOT generate pseudo-header fields other than those defined in HTTP2.  The restrictions on the use of pseudo-header fields in Section 8.1.2.1 of HTTP2 also apply to HTTP/3. </ins>  <ins> HTTP/3 uses QPACK header compression as described in QPACK, a variation of HPACK which allows the flexibility to avoid header- compression-induced head-of-line blocking.  See that document for additional details. </ins>  <ins> An HTTP/3 implementation MAY impose a limit on the maximum size of the header it will accept on an individual HTTP message; encountering a larger message header SHOULD be treated as a stream error of type "HTTP_EXCESSIVE_LOAD".  If an implementation wishes to advise its peer of this limit, it can be conveyed as a number of bytes in the "SETTINGS_MAX_HEADER_LIST_SIZE" parameter.  The size of a header list is calculated based on the uncompressed size of header fields, including the length of the name and value in bytes plus an overhead of 32 bytes for each header field. </ins>  <ins> 4.1.2. </ins>  <ins> Clients can cancel requests by aborting the stream (QUIC RESET_STREAM and/or STOP_SENDING frames, as appropriate) with an error code of HTTP_REQUEST_CANCELLED (http-error-codes).  When the client cancels a response, it indicates that this response is no longer of interest. Implementations SHOULD cancel requests by aborting both directions of a stream. </ins>  <ins> When the server rejects a request without performing any application processing, it SHOULD abort its response stream with the error code HTTP_REQUEST_REJECTED.  In this context, "processed" means that some data from the stream was passed to some higher layer of software that might have taken some action as a result.  The client can treat requests rejected by the server as though they had never been sent at all, thereby allowing them to be retried later on a new connection. Servers MUST NOT use the HTTP_REQUEST_REJECTED error code for requests which were partially or fully processed.  When a server abandons a response after partial processing, it SHOULD abort its response stream with the error code HTTP_REQUEST_CANCELLED. </ins>  <ins> When a client sends a STOP_SENDING with HTTP_REQUEST_CANCELLED, a server MAY send the error code HTTP_REQUEST_REJECTED in the corresponding RESET_STREAM if no processing was performed.  Clients MUST NOT reset streams with the HTTP_REQUEST_REJECTED error code except in response to a QUIC STOP_SENDING frame that contains the same code. </ins>  <ins> If a stream is cancelled after receiving a complete response, the client MAY ignore the cancellation and use the response.  However, if a stream is cancelled after receiving a partial response, the response SHOULD NOT be used.  Automatically retrying such requests is not possible, unless this is otherwise permitted (e.g., idempotent actions like GET, PUT, or DELETE). </ins>  <ins> 4.2. </ins>  <ins> The pseudo-method CONNECT (RFC7231, Section 4.3.6) is primarily used with HTTP proxies to establish a TLS session with an origin server for the purposes of interacting with "https" resources.  In 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 establish a tunnel over a single HTTP/2 stream to a remote host for similar purposes. </ins>  <ins> A CONNECT request in HTTP/3 functions in the same manner as in HTTP/2.  The request MUST be formatted as described in HTTP2, Section 8.3.  A CONNECT request that does not conform to these restrictions is malformed.  The request stream MUST NOT be closed at the end of the request. </ins>  <ins> A proxy that supports CONNECT establishes a TCP connection (RFC0793) to the server identified in the ":authority" pseudo-header field. Once this connection is successfully established, the proxy sends a HEADERS frame containing a 2xx series status code to the client, as defined in RFC7231, Section 4.3.6. </ins>  <ins> All DATA frames on the stream correspond to data sent or received on the TCP connection.  Any DATA frame sent by the client is transmitted by the proxy to the TCP server; data received from the TCP server is packaged into DATA frames by the proxy.  Note that the size and number of TCP segments is not guaranteed to map predictably to the size and number of HTTP DATA or QUIC STREAM frames. </ins>  <ins> The TCP connection can be closed by either peer.  When the client ends the request stream (that is, the receive stream at the proxy enters the "Data Recvd" state), the proxy will set the FIN bit on its 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 client.  TCP connections which remain half-closed in a single direction are not invalid, but are often handled poorly by servers, so clients SHOULD NOT close a stream for sending while they still expect to receive data from the target of the CONNECT. </ins>  <ins> A TCP connection error is signaled with QUIC RESET_STREAM frame.  A proxy treats any error in the TCP connection, which includes receiving a TCP segment with the RST bit set, as a stream error of type HTTP_CONNECT_ERROR (http-error-codes).  Correspondingly, a proxy MUST send a TCP segment with the RST bit set if it detects an error with the stream or the QUIC connection. </ins>  <ins> 4.3. </ins>  <ins> HTTP/3 uses a priority scheme similar to that described in HTTP2, Section 5.3.  In this priority scheme, a given element can be designated as dependent upon another element.  This information is expressed in the PRIORITY frame frame-priority which identifies the element and the dependency.  The elements that can be prioritized are: </ins>  <ins> Requests, identified by the ID of the request stream </ins>  <ins> Pushes, identified by the Push ID of the promised resource (frame- push-promise) </ins>  <ins> Placeholders, identified by a Placeholder ID </ins>  <ins> Taken together, the dependencies across all prioritized elements in a connection form a dependency tree.  An element can depend on another element or on the root of the tree.  A reference to an element which is no longer in the tree is treated as a reference to the root of the tree.  The structure of the dependency tree changes as PRIORITY frames modify the dependency links between prioritized elements. </ins>  <ins> Due to reordering between streams, an element can also be prioritized which is not yet in the tree.  Such elements are added to the tree with the requested priority. </ins>  <ins> When a prioritized element is first created, it has a default initial weight of 16 and a default dependency.  Requests and placeholders are dependent on the root of the priority tree; pushes are dependent on the client request on which the PUSH_PROMISE frame was sent. </ins>  <ins> Requests may override the default initial values by including a PRIORITY frame (see frame-priority) at the beginning of the stream. These priorities can be updated by sending a PRIORITY frame on the control stream. </ins>  <ins> 4.3.1. </ins>  <ins> In HTTP/2, certain implementations used closed or unused streams as placeholders in describing the relative priority of requests.  This created confusion as servers could not reliably identify which elements of the priority tree could be discarded safely.  Clients could potentially reference closed streams long after the server had discarded state, leading to disparate views of the prioritization the client had attempted to express. </ins>  <ins> In HTTP/3, a number of placeholders are explicitly permitted by the server using the "SETTINGS_NUM_"S" setting.  Because the server commits to maintaining these placeholders in the prioritization tree, clients can use them with confidence that the server will not have discarded the state.  Clients MUST NOT send the "SETTINGS_NUM_"S" setting; receipt of this setting by a server MUST be treated as a connection error of type "HTTP_WRONG_SETTING_DIRECTION". </ins>  <ins> Placeholders are identified by an ID between zero and one less than the number of placeholders the server has permitted. </ins>  <ins> Like streams, placeholders have priority information associated with them. </ins>  <ins> 4.3.2. </ins>  <ins> Because placeholders will be used to "root" any persistent structure of the tree which the client cares about retaining, servers can aggressively prune inactive regions from the priority tree.  For prioritization purposes, a node in the tree is considered "inactive" when the corresponding stream has been closed for at least two round- trip times (using any reasonable estimate available on the server). This delay helps mitigate race conditions where the server has pruned a node the client believed was still active and used as a Stream Dependency. </ins>  <ins> Specifically, the server MAY at any time: </ins>  <ins> Identify and discard branches of the tree containing only inactive nodes (i.e. a node with only other inactive nodes as descendants, along with those descendants) </ins>  <ins> Identify and condense interior regions of the tree containing only inactive nodes, allocating weight appropriately </ins>  <ins> In the example in fig-pruning, "P" represents a Placeholder, "A" represents an active node, and "I" represents an inactive node.  In the first step, the server discards two inactive branches (each a single node).  In the second step, the server condenses an interior inactive node.  Note that these transformations will result in no change in the resources allocated to a particular active stream. </ins>  <ins> Clients SHOULD assume the server is actively performing such pruning and SHOULD NOT declare a dependency on a stream it knows to have been closed. </ins>  <ins> 4.4. </ins>  <ins> HTTP/3 server push is similar to what is described in HTTP/2 HTTP2, but uses different mechanisms. </ins>  <ins> Each server push is identified by a unique Push ID.  This Push ID is used in a single PUSH_PROMISE frame (see frame-push-promise) which carries the request headers, possibly included in one or more DUPLICATE_PUSH frames (see frame-duplicate-push), then included with the push stream which ultimately fulfills those promises. </ins>  <ins> Server push is only enabled on a connection when a client sends a MAX_PUSH_ID frame (see frame-max-push-id).  A server cannot use server push until it receives a MAX_PUSH_ID frame.  A client sends additional MAX_PUSH_ID frames to control the number of pushes that a server can promise.  A server SHOULD use Push IDs sequentially, starting at 0.  A client MUST treat receipt of a push stream with a Push ID that is greater than the maximum Push ID as a connection error of type HTTP_LIMIT_EXCEEDED. </ins>  <ins> The header of the request message is carried by a PUSH_PROMISE frame (see frame-push-promise) on the request stream which generated the push.  This allows the server push to be associated with a client request.  Ordering of a PUSH_PROMISE in relation to certain parts of the response is important (see Section 8.2.1 of HTTP2).  Promised requests MUST conform to the requirements in Section 8.2 of HTTP2. </ins>  <ins> The same server push can be associated with additional client requests using a DUPLICATE_PUSH frame (see frame-duplicate-push). Ordering of a DUPLICATE_PUSH in relation to certain parts of the response is similarly important. </ins>  <ins> When a server later fulfills a promise, the server push response is conveyed on a push stream (see push-streams).  The push stream identifies the Push ID of the promise that it fulfills, then contains a response to the promised request using the same format described for responses in request-response. </ins>  <ins> Due to reordering, DUPLICATE_PUSH frames or push stream data can arrive before the corresponding PUSH_PROMISE frame.  When a client receives a DUPLICATE_PUSH frame for an as-yet-unknown Push ID, the request headers of the push are not immediately available.  The client can either delay generating new requests for content referenced following the DUPLICATE_PUSH frame until the request headers become available, or can initiate requests for discovered resources and cancel the requests if the requested resource is already being pushed.  When a client receives a new push stream with an as-yet-unknown Push ID, both the associated client request and the pushed request headers are unknown.  The client can buffer the stream data in expectation of the matching PUSH_PROMISE.  The client can use stream flow control (see section 4.1 of QUIC-TRANSPORT) to limit the amount of data a server may commit to the pushed stream. </ins>  <ins> 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 or opens after sending the CANCEL_PUSH frame, a QUIC STOP_SENDING frame with an appropriate error code can also be used (e.g., HTTP_PUSH_REFUSED, HTTP_PUSH_ALREADY_IN_CACHE; see errors).  This asks the server not to transfer additional data and indicates that it will be discarded upon receipt. </ins>  <ins> 5. </ins>  <ins> Once established, an HTTP/3 connection can be used for many requests and responses over time until the connection is closed.  Connection closure can happen in any of several different ways. </ins>  <ins> 5.1. </ins>  <ins> Each QUIC endpoint declares an idle timeout during the handshake.  If the connection remains idle (no packets received) for longer than this duration, the peer will assume that the connection has been closed.  HTTP/3 implementations will need to open a new connection for new requests if the existing connection has been idle for longer than the server's advertised idle timeout, and SHOULD do so if approaching the idle timeout. </ins>  <ins> HTTP clients are expected to request that the transport keep connections open while there are responses outstanding for requests or server pushes, as described in Section 19.2 of QUIC-TRANSPORT.  If the client is not expecting a response from the server, allowing an idle connection to time out is preferred over expending effort maintaining a connection that might not be needed.  A gateway MAY maintain connections in anticipation of need rather than incur the latency cost of connection establishment to servers.  Servers SHOULD NOT actively keep connections open. </ins>  <ins> 5.2. </ins>  <ins> Even when a connection is not idle, either endpoint can decide to stop using the connection and let the connection close gracefully. Since clients drive request generation, clients perform a connection shutdown by not sending additional requests on the connection; responses and pushed responses associated to previous requests will continue to completion.  Servers perform the same function by communicating with clients. </ins>  <ins> Servers initiate the shutdown of a connection by sending a GOAWAY frame (frame-goaway).  The GOAWAY frame indicates that client- initiated requests on lower stream IDs were or might be processed in this connection, while requests on the indicated stream ID and greater were rejected.  This enables client and server to agree on which requests were accepted prior to the connection shutdown.  This identifier MAY be lower than the stream limit identified by a QUIC MAX_STREAM_ID frame, and MAY be zero if no requests were processed. Servers SHOULD NOT increase the QUIC MAX_STREAM_ID limit after sending a GOAWAY frame. </ins>  <ins> Clients MUST NOT send new requests on the connection after receiving GOAWAY; a new connection MAY be established to send additional requests. </ins>  <ins> Some requests might already be in transit.  If the client has already sent requests on streams with a Stream ID greater than or equal to that indicated in the GOAWAY frame, those requests will not be processed and MAY be retried by the client on a different connection. The client MAY cancel these requests.  It is RECOMMENDED that the server explicitly reject such requests (see request-cancellation) in order to clean up transport state for the affected streams. </ins>  <ins> Requests on Stream IDs less than the Stream ID in the GOAWAY frame might have been processed; their status cannot be known until a response is received, the stream is reset individually, or the connection terminates.  Servers MAY reject individual requests on streams below the indicated ID if these requests were not processed. </ins>  <ins> Servers SHOULD send a GOAWAY frame when the closing of a connection is known in advance, even if the advance notice is small, so that the remote peer can know whether a request has been partially processed or not.  For example, if an HTTP client sends a POST at the same time that a server closes a QUIC connection, the client cannot know if the server started to process that POST request if the server does not send a GOAWAY frame to indicate what streams it might have acted on. </ins>  <ins> A client that is unable to retry requests loses all requests that are in flight when the server closes the connection.  A server MAY send multiple GOAWAY frames indicating different stream IDs, but MUST NOT increase the value they send in the last Stream ID, since clients might already have retried unprocessed requests on another connection.  A server that is attempting to gracefully shut down a connection SHOULD send an initial GOAWAY frame with the last Stream ID set to the current value of QUIC's MAX_STREAM_ID and SHOULD NOT increase the MAX_STREAM_ID thereafter.  This signals to the client that a shutdown is imminent and that initiating further requests is prohibited.  After allowing time for any in-flight requests (at least one round-trip time), the server MAY send another GOAWAY frame with an updated last Stream ID.  This ensures that a connection can be cleanly shut down without losing requests. </ins>  <ins> Once all accepted requests have been processed, the server can permit the connection to become idle, or MAY initiate an immediate closure of the connection.  An endpoint that completes a graceful shutdown SHOULD use the HTTP_NO_ERROR code when closing the connection. </ins>  <ins> If a client has consumed all available bidirectional stream IDs with requests, the server need not send a GOAWAY frame, since the client is unable to make further requests. </ins>  <ins> 5.3. </ins>  <ins> An HTTP/3 implementation can immediately close the QUIC connection at any time.  This results in sending a QUIC CONNECTION_CLOSE frame to the peer; the error code in this frame indicates to the peer why the connection is being closed.  See errors for error codes which can be used when closing a connection. </ins>  <ins> Before closing the connection, a GOAWAY MAY be sent to allow the client to retry some requests.  Including the GOAWAY frame in the same packet as the QUIC CONNECTION_CLOSE frame improves the chances of the frame being received by clients. </ins>  <ins> 5.4. </ins>  <ins> For various reasons, the QUIC transport could indicate to the application layer that the connection has terminated.  This might be due to an explicit closure by the peer, a transport-level error, or a change in network topology which interrupts connectivity. </ins>  <ins> If a connection terminates without a GOAWAY frame, clients MUST assume that any request which was sent, whether in whole or in part, might have been processed. </ins>  <ins> 6. </ins>  <ins> A QUIC stream provides reliable in-order delivery of bytes, but makes no guarantees about order of delivery with regard to bytes on other streams.  On the wire, data is framed into QUIC STREAM frames, but this framing is invisible to the HTTP framing layer.  The transport layer buffers and orders received QUIC STREAM frames, exposing the data contained within as a reliable byte stream to the application. Although QUIC permits out-of-order delivery within a stream HTTP/3 does not make use of this feature. </ins>  <ins> QUIC streams can be either unidirectional, carrying data only from initiator to receiver, or bidirectional.  Streams can be initiated by either the client or the server.  For more detail on QUIC streams, see Section 2 of QUIC-TRANSPORT. </ins>  <ins> When HTTP headers and data are sent over QUIC, the QUIC layer handles most of the stream management.  HTTP does not need to do any separate multiplexing when using QUIC - data sent over a QUIC stream always maps to a particular HTTP transaction or connection context. </ins>  <ins> 6.1. </ins>  <ins> All client-initiated bidirectional streams are used for HTTP requests and responses.  A bidirectional stream ensures that the response can be readily correlated with the request.  This means that the client's first request occurs on QUIC stream 0, with subsequent requests on stream 4, 8, and so on.  In order to permit these streams to open, an HTTP/3 client SHOULD send non-zero values for the QUIC transport parameters "initial_max_stream_data_bidi_local".  An HTTP/3 server SHOULD send non-zero values for the QUIC transport parameters "initial_max_stream_data_bidi_remote" and "initial_max_bidi_streams". It is recommended that "initial_max_bidi_streams" be no smaller than 100, so as to not unnecessarily limit parallelism. </ins>  <ins> These streams carry frames related to the request/response (see request-response).  When a stream terminates cleanly, if the last frame on the stream was truncated, this MUST be treated as a connection error (see HTTP_MALFORMED_FRAME in http-error-codes). Streams which terminate abruptly may be reset at any point in the frame. </ins>  <ins> HTTP/3 does not use server-initiated bidirectional streams; clients MUST omit or specify a value of zero for the QUIC transport parameter "initial_max_bidi_streams". </ins>  <ins> 6.2. </ins>  <ins> Unidirectional streams, in either direction, are used for a range of purposes.  The purpose is indicated by a stream type, which is sent as a variable-length integer at the start of the stream.  The format and structure of data that follows this integer is determined by the stream type. </ins>  <ins> Some stream types are reserved (stream-grease).  Two stream types are defined in this document: control streams (control-streams) and push streams (push-streams).  Other stream types can be defined by extensions to HTTP/3; see extensions for more details. </ins>  <ins> The performance of HTTP/3 connections in the early phase of their lifetime is sensitive to the creation and exchange of data on unidirectional streams.  Endpoints that set low values for the QUIC transport parameters "initial_max_uni_streams" and "initial_max_stream_data_uni" will increase the chance that the remote peer reaches the limit early and becomes blocked.  In particular, the value chosen for "initial_max_uni_streams" should consider that remote peers may wish to exercise reserved stream behaviour (stream-grease).  To reduce the likelihood of blocking, both clients and servers SHOULD send a value of three or greater for the QUIC transport parameter "initial_max_uni_streams", and a value of 1,024 or greater for the QUIC transport parameter "initial_max_stream_data_uni". </ins>  <ins> If the stream header indicates a stream type which is not supported by the recipient, the remainder of the stream cannot be consumed as the semantics are unknown.  Recipients of unknown stream types MAY trigger a QUIC STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE, but MUST NOT consider such streams to be a connection error of any kind. </ins>  <ins> Implementations MAY send stream types before knowing whether the peer supports them.  However, stream types which could modify the state or semantics of existing protocol components, including QPACK or other extensions, MUST NOT be sent until the peer is known to support them. </ins>  <ins> A sender can close or reset a unidirectional stream unless otherwise specified.  A receiver MUST tolerate unidirectional streams being closed or reset prior to the reception of the unidirectional stream header. </ins>  <ins> 6.2.1. </ins>  <ins> A control stream is indicated by a stream type of "0x00".  Data on this stream consists of HTTP/3 frames, as defined in frames. </ins>  <ins> Each side MUST initiate a single control stream at the beginning of the connection and send its SETTINGS frame as the first frame on this stream.  If the first frame of the control stream is any other frame type, this MUST be treated as a connection error of type HTTP_MISSING_SETTINGS.  Only one control stream per peer is permitted; receipt of a second stream which claims to be a control stream MUST be treated as a connection error of type HTTP_WRONG_STREAM_COUNT.  The sender MUST NOT close the control stream, and the receiver MUST NOT request that the sender close the control stream.  If either control stream is closed at any point, this MUST be treated as a connection error of type HTTP_CLOSED_CRITICAL_STREAM. </ins>  <ins> A pair of unidirectional streams is used rather than a single bidirectional stream.  This allows either peer to send data as soon they are able.  Depending on whether 0-RTT is enabled on the connection, either client or server might be able to send stream data first after the cryptographic handshake completes. </ins>  <ins> 6.2.2. </ins>  <ins> A push stream is indicated by a stream type of "0x01", followed by the Push ID of the promise that it fulfills, encoded as a variable- length integer.  The remaining data on this stream consists of HTTP/3 frames, as defined in frames, and fulfills a promised server push. Server push and Push IDs are described in server-push. </ins>  <ins> Only servers can push; if a server receives a client-initiated push stream, this MUST be treated as a connection error of type HTTP_WRONG_STREAM_DIRECTION. 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 stream header, the client MUST treat this as a connection error of type HTTP_DUPLICATE_PUSH. </ins>  <ins> 6.2.3. </ins>  <ins> Stream types of the format "0x1f * N + 0x21" for integer values of N </ins> are reserved to exercise the requirement that unknown types be  <ins> ignored.  These streams have no semantics, and can be sent when application-layer padding is desired.  They MAY also be sent on connections where no data is currently being transferred.  Endpoints MUST NOT consider these streams to have any meaning upon receipt. </ins>  <ins> The payload and length of the stream are selected in any manner the </ins> implementation chooses.  <ins> 7. </ins>  <ins> HTTP frames are carried on QUIC streams, as described in stream- mapping.  HTTP/3 defines three stream types: control stream, request stream, and push stream.  This section describes HTTP/3 frame formats and the streams types on which they are permitted; see stream-frame- mapping for an overiew.  A comparison between HTTP/2 and HTTP/3 frames is provided in h2-frames. </ins>  <ins> Certain frames can only occur as the first frame of a particular stream type; these are indicated in stream-frame-mapping with a (1). Specific guidance is provided in the relevant section. </ins>  <ins> Note that, unlike QUIC frames, HTTP/3 frames can span multiple packets. </ins>  <ins> 7.1. </ins>  <ins> All frames have the following format: </ins>  <ins> A frame includes the following fields: </ins>  <ins> A variable-length integer that identifies the frame type. </ins>  <ins> A variable-length integer that describes the length of the Frame Payload. </ins>  <ins> A payload, the semantics of which are determined by the Type field. </ins>  <ins> Each frame's payload MUST contain exactly the fields identified in its description.  A frame payload that contains additional bytes after the identified fields or a frame payload that terminates before the end of the identified fields MUST be treated as a connection error of type HTTP_MALFORMED_FRAME. </ins>  <ins> 7.2. </ins>  <ins> 7.2.1. </ins>  <ins> DATA frames (type=0x0) convey arbitrary, variable-length sequences of bytes associated with an HTTP request or response payload. </ins>  <ins> DATA frames MUST be associated with an HTTP request or response.  If a DATA frame is received on either control stream, the recipient MUST respond with a connection error (errors) of type HTTP_WRONG_STREAM. </ins>  <ins> 7.2.2. </ins>  <ins> The HEADERS frame (type=0x1) is used to carry a header block, compressed using QPACK.  See QPACK for more details. </ins>  <ins> HEADERS frames can only be sent on request / push streams. </ins>  <ins> 7.2.3. </ins>  <ins> The PRIORITY (type=0x2) frame specifies the client-advised priority of a request, server push or placeholder. </ins>  <ins> A PRIORITY frame identifies an element to prioritize, and an element upon which it depends.  A Prioritized ID or Dependency ID identifies a client-initiated request using the corresponding stream ID, a server push using a Push ID (see frame-push-promise), or a placeholder using a Placeholder ID (see placeholders). </ins>  <ins> When a client initiates a request, a PRIORITY frame MAY be sent as the first frame of the stream, creating a dependency on an existing element.  In order to ensure that prioritization is processed in a consistent order, any subsequent PRIORITY frames for that request MUST be sent on the control stream.  A PRIORITY frame received after other frames on a request stream MUST be treated as a connection error of type HTTP_UNEXPECTED_FRAME. </ins>  <ins> If, by the time a new request stream is opened, its priority information has already been received via the control stream, the PRIORITY frame sent on the request stream MUST be ignored. </ins>  <ins> The PRIORITY frame payload has the following fields: </ins>  <ins> A two-bit field indicating the type of element being prioritized (see prioritized-element-types).  When sent on a request stream, this MUST be set to "11".  When sent on the control stream, this MUST NOT be set to "11". </ins>  <ins> A two-bit field indicating the type of element being depended on (see element-dependency-types). </ins>  <ins> A four-bit field which MUST be zero when sent and has no semantic value on receipt. </ins>  <ins> A variable-length integer that identifies the element being prioritized.  Depending on the value of Prioritized Type, this contains the Stream ID of a request stream, the Push ID of a promised resource, a Placeholder ID of a placeholder, or is absent. </ins>  <ins> A variable-length integer that identifies the element on which a dependency is being expressed.  Depending on the value of Dependency Type, this contains the Stream ID of a request stream, the Push ID of a promised resource, the Placeholder ID of a placeholder, or is absent.  For details of dependencies, see priority and HTTP2, Section 5.3. </ins>  <ins> An unsigned 8-bit integer representing a priority weight for the prioritized element (see HTTP2, Section 5.3).  Add one to the value to obtain a weight between 1 and 256. </ins>  <ins> The values for the Prioritized Element Type (prioritized-element- types) and Element Dependency Type (element-dependency-types) imply the interpretation of the associated Element ID fields. Note that unlike in HTTP2, the root of the tree cannot be referenced using a Stream ID of 0, as in QUIC stream 0 carries a valid HTTP request.  The root of the tree cannot be reprioritized. The PRIORITY frame can express relationships which might not be permitted based on the stream on which it is sent or its position in the stream.  These situations MUST be treated as a connection error of type HTTP_MALFORMED_FRAME.  The following situations are examples of invalid PRIORITY frames: A PRIORITY frame sent on a request stream with the Prioritized Element Type set to any value other than "11" A PRIORITY frame sent on a request stream which expresses a dependency on a request with a greater Stream ID than the current stream A PRIORITY frame sent on a control stream with the Prioritized Element Type set to "11" </ins>  <ins> A PRIORITY frame which claims to reference a request, but the associated ID does not identify a client-initiated bidirectional stream </ins>  <ins> A PRIORITY frame with Empty bits not set to zero MAY be treated as a connection error of type HTTP_MALFORMED_FRAME. </ins>  <ins> A PRIORITY frame that references a non-existent Push ID, a Placeholder ID greater than the server's limit, or a Stream ID the client is not yet permitted to open MUST be treated as a connection error of type HTTP_LIMIT_EXCEEDED. </ins>  <ins> A PRIORITY frame received on any stream other than a request or control stream MUST be treated as a connection error of type HTTP_WRONG_STREAM. </ins>  <ins> PRIORITY frames received by a client MUST be treated as a connection error of type HTTP_UNEXPECTED_FRAME. </ins>  <ins> 7.2.4. </ins>  <ins> 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 frame identifies a server push by Push ID (see frame-push-promise), encoded as a variable-length integer. </ins>  <ins> When a server receives this frame, it aborts sending the response for 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 to avoid opening a push stream.  If the push stream has been opened by the server, the server SHOULD send a QUIC RESET_STREAM frame on that stream and cease transmission of the response. </ins>  <ins> A server can send the CANCEL_PUSH frame to indicate that it will not be fulfilling a promise prior to creation of a push stream.  Once the push stream has been created, sending CANCEL_PUSH has no effect on the state of the push stream.  A QUIC RESET_STREAM frame SHOULD be used instead to abort transmission of the server push response. </ins>  <ins> 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 treated as a connection error of type HTTP_WRONG_STREAM. </ins>  <ins> The CANCEL_PUSH frame carries a Push ID encoded as a variable-length integer.  The Push ID identifies the server push that is being cancelled (see frame-push-promise). </ins>  <ins> 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. </ins>  <ins> 7.2.5. </ins>  <ins> The SETTINGS frame (type=0x4) conveys configuration parameters that affect how endpoints communicate, such as preferences and constraints on peer behavior.  Individually, a SETTINGS parameter can also be referred to as a "setting"; the identifier and value of each setting parameter can be referred to as a "setting identifier" and a "setting value". </ins>  <ins> SETTINGS frames always apply to a connection, never a single stream. A SETTINGS frame MUST be sent as the first frame of each control stream (see control-streams) by each peer, and MUST NOT be sent subsequently or on any other stream.  If an endpoint receives a SETTINGS frame on a different stream, the endpoint MUST respond with a connection error of type HTTP_WRONG_STREAM.  If an endpoint receives a second SETTINGS frame, the endpoint MUST respond with a connection error of type HTTP_UNEXPECTED_FRAME. </ins>  <ins> SETTINGS parameters are not negotiated; they describe characteristics of the sending peer, which can be used by the receiving peer. However, a negotiation can be implied by the use of SETTINGS - each peer uses SETTINGS to advertise a set of supported values.  The definition of the setting would describe how each peer combines the two sets to conclude which choice will be used.  SETTINGS does not provide a mechanism to identify when the choice takes effect. </ins>  <ins> Different values for the same parameter can be advertised by each peer.  For example, a client might be willing to consume a very large response header, while servers are more cautious about request size. </ins>  <ins> Parameters MUST NOT occur more than once in the SETTINGS frame.  A receiver MAY treat the presence of the same parameter more than once as a connection error of type HTTP_MALFORMED_FRAME. </ins>  <ins> The payload of a SETTINGS frame consists of zero or more parameters. Each parameter consists of a setting identifier and a value, both encoded as QUIC variable-length integers. </ins>  <ins> An implementation MUST ignore the contents for any SETTINGS identifier it does not understand. </ins>  <ins> 7.2.5.1. </ins>  <ins> The following settings are defined in HTTP/3: </ins>  <ins> The default value is unlimited.  See header-formatting for usage. </ins>  <ins> The default value is 0.  However, this value SHOULD be set to a non-zero value by servers.  See placeholders for usage. </ins>  <ins> Setting identifiers of the format "0x1f * N + 0x21" for integer values of N are reserved to exercise the requirement that unknown identifiers be ignored.  Such settings have no defined meaning. Endpoints SHOULD include at least one such setting in their SETTINGS frame.  Endpoints MUST NOT consider such settings to have any meaning upon receipt. </ins>  <ins> Because the setting has no defined meaning, the value of the setting can be any value the implementation selects. </ins>  <ins> Additional settings can be defined by extensions to HTTP/3; see extensions for more details. </ins>  <ins> 7.2.5.2. </ins>  <ins> An HTTP implementation MUST NOT send frames or requests which would be invalid based on its current understanding of the peer's settings. All settings begin at an initial value, and are updated upon receipt of a SETTINGS frame.  For servers, the initial value of each client setting is the default value. </ins>  <ins> For clients using a 1-RTT QUIC connection, the initial value of each server setting is the default value.  When a 0-RTT QUIC connection is being used, the initial value of each server setting is the value used in the previous session.  Clients MUST store the settings the server provided in the session being resumed and MUST comply with stored settings until the current server settings are received. </ins>  <ins> A server can remember the settings that it advertised, or store an integrity-protected copy of the values in the ticket and recover the information when accepting 0-RTT data.  A server uses the HTTP/3 settings values in determining whether to accept 0-RTT data. </ins>  <ins> A server MAY accept 0-RTT and subsequently provide different settings in its SETTINGS frame.  If 0-RTT data is accepted by the server, its SETTINGS frame MUST NOT reduce any limits or alter any values that might be violated by the client with its 0-RTT data. </ins>  <ins> 7.2.6. </ins>  <ins> The PUSH_PROMISE frame (type=0x5) is used to carry a promised request header set from server to client on a request stream, as in HTTP/2. </ins>  <ins> The payload consists of: </ins>  <ins> A variable-length integer that identifies the server push operation.  A Push ID is used in push stream headers (server- push), CANCEL_PUSH frames (frame-cancel-push), DUPLICATE_PUSH frames (frame-duplicate-push), and PRIORITY frames (frame- priority). </ins>  <ins> QPACK-compressed request header fields for the promised response. See QPACK for more details. </ins>  <ins> A server MUST NOT use a Push ID that is larger than the client has provided in a MAX_PUSH_ID frame (frame-max-push-id) and MUST NOT use the same Push ID in multiple PUSH_PROMISE frames.  A client MUST treat receipt of a PUSH_PROMISE that contains a larger Push ID than the client has advertised or a Push ID which has already been promised as a connection error of type HTTP_MALFORMED_FRAME. </ins>  <ins> If a PUSH_PROMISE frame is received on either control stream, the recipient MUST respond with a connection error (errors) of type HTTP_WRONG_STREAM. </ins>  <ins> See server-push for a description of the overall server push mechanism. </ins>  <ins> 7.2.7. </ins>  <ins> The GOAWAY frame (type=0x7) is used to initiate graceful shutdown of a connection by a server.  GOAWAY allows a server to stop accepting new requests while still finishing processing of previously received requests.  This enables administrative actions, like server maintenance.  GOAWAY by itself does not close a connection. </ins>  <ins> The GOAWAY frame is always sent on the control stream.  It carries a QUIC Stream ID for a client-initiated bidirectional stream encoded as 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 of type HTTP_WRONG_STREAM. </ins>  <ins> Clients do not need to send GOAWAY to initiate a graceful shutdown; they simply stop making new requests.  A server MUST treat receipt of a GOAWAY frame on any stream as a connection error (errors) of type HTTP_UNEXPECTED_FRAME. </ins>  <ins> The GOAWAY frame applies to the connection, not a specific stream.  A client MUST treat a GOAWAY frame on a stream other than the control stream as a connection error (errors) of type HTTP_UNEXPECTED_FRAME. </ins>  <ins> See connection-shutdown for more information on the use of the GOAWAY frame. </ins>  <ins> 7.2.8. </ins>  <ins> 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 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 that the server can initiate in addition to the limit set by the QUIC MAX_STREAMS frame. </ins>  <ins> The MAX_PUSH_ID frame is always sent on the control stream.  Receipt of a MAX_PUSH_ID frame on any other stream MUST be treated as a connection error of type HTTP_WRONG_STREAM. </ins>  <ins> 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 HTTP_UNEXPECTED_FRAME. 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 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 server fulfills or cancels server pushes. </ins>  <ins> 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 (see frame-push-promise).  A MAX_PUSH_ID frame cannot reduce the maximum 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 HTTP_MALFORMED_FRAME. </ins>  <ins> 7.2.9. </ins>  <ins> The DUPLICATE_PUSH frame (type=0xE) is used by servers to indicate that an existing pushed resource is related to multiple client requests. </ins>  <ins> The DUPLICATE_PUSH frame is always sent on a request stream.  Receipt of a DUPLICATE_PUSH frame on any other stream MUST be treated as a connection error of type HTTP_WRONG_STREAM. </ins>  <ins> 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 HTTP_UNEXPECTED_FRAME. </ins>  <ins> The DUPLICATE_PUSH frame carries a single variable-length integer that identifies the Push ID of a resource that the server has previously promised (see frame-push-promise), though that promise might 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 (frame-max-push-id).  A client MUST treat receipt of a DUPLICATE_PUSH that contains a larger Push ID than the client has advertised as a connection error of type HTTP_MALFORMED_FRAME. </ins>  <ins> This frame allows the server to use the same server push in response to multiple concurrent requests.  Referencing the same server push ensures that a promise can be made in relation to every response in which server push might be needed without duplicating request headers or pushed responses. </ins>  <ins> Allowing duplicate references to the same Push ID is primarily to reduce duplication caused by concurrent requests.  A server SHOULD avoid reusing a Push ID over a long period.  Clients are likely to consume server push responses and not retain them for reuse over time.  Clients that see a DUPLICATE_PUSH that uses a Push ID that they have since consumed and discarded are forced to ignore the DUPLICATE_PUSH. </ins>  <ins> 7.2.10. </ins>  <ins> Frame types of the format "0x1f * N + 0x21" for integer values of N are reserved to exercise the requirement that unknown types be ignored (extensions).  These frames have no semantics, and can be sent when application-layer padding is desired.  They MAY also be sent on connections where no data is currently being transferred. Endpoints MUST NOT consider these frames to have any meaning upon receipt. </ins>  <ins> The payload and length of the frames are selected in any manner the implementation chooses. 8. </ins> QUIC allows the application to abruptly terminate (reset) individual streams or the entire connection when an error is encountered.  These This section describes HTTP/3-specific error codes which can be used to express the cause of a connection or stream error.  <ins> 8.1. </ins> The following error codes are defined for use in QUIC RESET_STREAM frames, STOP_SENDING frames, and CONNECTION_CLOSE frames when using with the code (0x10D).  The last byte "0xff" is used to indicate any frame type greater than "0xfe". <ins> 9. HTTP/3 permits extension of the protocol.  Within the limitations described in this section, protocol extensions can be used to provide additional services or alter any aspect of the protocol.  Extensions are effective only within the scope of a single HTTP/3 connection. This applies to the protocol elements defined in this document.  This does not affect the existing options for extending HTTP, such as defining new methods, status codes, or header fields. Extensions are permitted to use new frame types (frames), new settings (settings-parameters), new error codes (errors), or new unidirectional stream types (unidirectional-streams).  Registries are established for managing these extension points: frame types (iana- frames), settings (iana-settings), error codes (iana-error-codes), and stream types (iana-stream-types). Implementations MUST ignore unknown or unsupported values in all extensible protocol elements.  Implementations MUST discard frames and unidirectional streams that have unknown or unsupported types. This means that any of these extension points can be safely used by extensions without prior arrangement or negotiation. Extensions that could change the semantics of existing protocol components MUST be negotiated before being used.  For example, an extension that changes the layout of the HEADERS frame cannot be used until the peer has given a positive signal that this is acceptable. In this case, it could also be necessary to coordinate when the revised layout comes into effect. This document doesn't mandate a specific method for negotiating the use of an extension but notes that a setting (settings-parameters) could be used for that purpose.  If both peers set a value that indicates willingness to use the extension, then the extension can be used.  If a setting is used for extension negotiation, the default value MUST be defined in such a fashion that the extension is disabled if the setting is omitted. </ins> 10. The security considerations of HTTP/3 should be comparable to those