]> Cloudflare

lucaspardue.24.7@gmail.com

Transport MASQUE Internet-Draft Application protocols using the QUIC transport protocol rely on streams, and optionally the unreliable datagram extension, to carry application data. Streams and datagrams can be multiplexed in single connections but QUIC does not define an interoperable prioritization scheme or signaling mechanism. The HTTP Extensible Prioritization scheme describes an application-level scheme for the prioritization of streams in HTTP/2 and HTTP/3. This document defines how Extensible Priorities can be augmented to apply to the multiplexing of HTTP datagram flows with other flows or streams. Note to Readers RFC EDITOR: please remove this section before publication Source code and issues list for this draft can be found at https://github.com/LPardue/draft-pardue-masque-dgram-priority.

Introduction Application protocols using the QUIC transport protocol rely on streams, and optionally the unreliable datagram extension , to carry application data. Streams and datagrams can be multiplexed in single connections but QUIC does not define an interoperable prioritization scheme or signaling mechanism. The HTTP Extensible Prioritization scheme describes an application-level scheme for the prioritization of streams in HTTP/2 and HTTP/3. This document defines how Extensible Priorities can be applied to the multiplexing of HTTP datagram flows with other flows or streams. The Extensible Priorities scheme for HTTP describes how clients can send priority signals related to requests in order to suggest how a server allocates resources to serving responses. When the protocol is HTTP/2, responses are carried on streams. When the protocol is HTTP/3, responses are carries on QUIC streams. While QUIC streams support multiplexing natively via use of a stream identifier, the unreliable datagram extension does not provide any such multiplexing identifier. HTTP datagrams () defines how multiplexed, potentially unreliable datagrams can be sent inside an HTTP connection. All datagrams are always associated with a request stream. In HTTP/3, HTTP datagrams can map directly to QUIC datagrams, in which case they carry a Quarter Stream ID - an encoding of the request stream ID - that is used to demultiplex at the receiver; see . also defines the DATAGRAM capsule, which can be used for reliable delivery over all versions of HTTP; see . In all cases, the prioritization of datagrams is noted as unspecified and delegated to future extensions. This document describes how the Extensible Priorities scheme can be augmented to also apply to HTTP datagrams that are multiplexed with other flows or streams. It enhances the Priority signals sent by clients, with a new datagram-urgency (du) parameter () and explains how this input is to be considered in server scheduling decisions for HTTP datagrams mapped to QUIC datagrams; see . When HTTP datagrams are used for proxying UDP, additional use cases extending beyond UDP data transfer are supported by the use of context IDs; see . The CONTEXT_PRIORITY capsule type can be used to signal the datagram-priority of individual contexts; see .

Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The term Integer is imported from .

Signalling Datagram Priority The Extensible Prioritization scheme describes how clients can send priority signals related to requests. Signals are a set of parameters, encoded using . defines the urgency and incremental parameters and provides guidance about how implementers can act on these parameters, in combination with other inputs, to make resource allocation and scheduling choices. Urgency communicates the client-view of request importance, and incremental communicates how the client intends to process response data as it arrives. Parameters are communicated in HTTP headers or version-specific frames. A client omitting the urgency or incremental parameters can be interpreted by the server as a signal to apply default priorities. The core scheme is extensible, new parameters can be defined to augment the base ones. This specification defines the datagram-urgency (du) extension parameter that operates in addition to the base urgency. There is no extension to the base incremental behavior; individual datagrams, even if belonging to the same identifier, are messages that are expected to be processed individually as they arrive.

Datagram Urgency The datagram-urgency (du) parameter is Integer (see ), between 0 and 7, in descending order of priority. This range matches the base urgency (u) parameter range; see Section 4.1 of . However, there is no default value. This parameter indicates the sender's recommendation, based on the expectation that the server would transmit HTTP datagrams in the order of their datagram-urgency values if possible. The smaller the value, the higher the precedence. Omitting the datagram-urgency parameter is a signal to apply the value of the urgency parameter. The following example shows a request for a CSS file with the urgency set to 0, any associated datagrams have the lower datagram-urgency of 2: Note that when the urgency parameter is omitted, it's default value of 3 is applied. In the following example, the priority field is omitted entirely, invoking the default behaviour of urgency and datagram-urgency, causing them to both have the implicit value 3: Endpoints MUST NOT treat reception of the datagram-urgency parameter as an error, even if HTTP datagram support is not enabled. The datagram-urgency parameter applies only to HTTP datagrams mapped to QUIC datagrams. Datagram capsules are sent on streams, so the base urgency parameter applies to them.

Reprioritization Reprioritization behaves similarly to existing mechanisms defined in . CONTEXT_PRIORITY frames can be sent by clients to provide updated priority signals after the initial request has been sent.

Prioritization when Proxying UDP in HTTP describes how to proxy UDP using HTTP datagrams. Client make UDP proxying requests using Extended CONNECT, which initiates a UDP tunnel. HTTP datagrams related to this stream correspond to the UDP tunnel by default. In order support extension use cases, defines context IDs, that are sent within datagrams, in addition to the Quarter Stream ID. UDP payloads use context ID 0, forms of data use other IDs. Datagram priority applies to UDP proxying requests, as described in . By default the same datagram-urgency applies to all HTTP datagram contexts related to the request stream.

The CONTEXT_PRIORITY Capsule There might be cases where it is beneficial to prioritize individual contexts differently from one another. This document defines the CONTEXT_PRIORITY (TBD) capsule type to carry a priority signal related to individual contexts. Once a UDP proxy request converts to the capsule protocol (see , clients can send CONTEXT_PRIORITY capsules to signal the priority of the identified context. A CONTEXT_PRIORITY capsule communicates a complete set of all priority parameters in the Priority Field Value field. Omitting a priority parameter is a signal to derive a value from defaults; see . Failure to parse the Priority Field Value MAY be treated as a connection error. In HTTP/2, the error is of type PROTOCOL_ERROR; in HTTP/3, the error is of type H3_GENERAL_PROTOCOL_ERROR. TODO: describe what happens if capsules arrive before contexts exists. Buffer? Drop? TODO: consider if servers could send this capsule type

CONTEXT_PRIORITY Capsule Format

The CONTEXT_PRIORITY capsule has the following fields:

Context ID:

The context ID that is the target of the priority update.

Priority Field Value:

The priority update value in ASCII text, encoded using Structured Fields; see .

Client Scheduling A client MAY use datagram-urgency to make local processing or scheduling choices about HTTP datagrams related to the requests it initiates.

Server Scheduling Priority signals are input to a prioritization process. Expressing priority is only a suggestion. The datagram-urgency parameter introduces new scheduling considerations on top of those presented in . It is RECOMMENDED that, when possible, servers respect the datagram-urgency parameter, sending higher-urgency HTTP datagrams before lower-urgency datagrams. Where streams and datagrams have equal urgency and datagram-urgency respectively, a server needs to decide how to divide the available sending capacity between stream and datagram data. Strict or static preference for one type of data over another (e.g., datagrams first, then streams) could lead to suboptimal results at the client, depending on the nature of the data. This is a form of starvation, as defined in . It applies whether the streams are incremental or not. Similarly, if datagrams are used for HTTP proxying and there are multiple context IDs in use for different purposes, those purposes might interfere or starve each other if they have the equal datagram-urgency. It is RECOMMENDED that servers avoid such starvation where possible. The method for doing so is an implementation decision. One approach is to divide the available bandwidth between stream and datagram data in some fixed or dynamic ratio. For instance, a server could choose to generate two classes of application data QUIC packets: STREAM-frame-only packets and DATAGRAM-only-frame packets. The server can control the capacity ratio split by managing the frequency of the packet classes. A simple alternating strategy would result in a roughly 50/50 split, while other frequencies would produce different ratios. When HTTP datagrams are carried in DATAGRAM capsules. It is RECOMMENDED that servers schedule the capsules in the manner expected for response data; see .

Retransmission Scheduling provides guidance about scheduling of retransmission data vs. new data. Since QUIC datagrams are not retransmitted, endpoints that prioritize QUIC stream retransmission data could delay datagrams. Furthermore, since DATAGRAM capsules are sent as stream data, they are subject to retransmission and could also delay native QUIC datagrams.

Security Considerations There are believed to be no additional considerations to those presented in .

IANA Considerations This specification registers the following entry in the HTTP Priority Parameters Registry

Name:

du

Description:

The urgency of HTTP datagrams associated with a response.

Reference:

This document

References Normative References This document defines an extension to the QUIC transport protocol to add support for sending and receiving unreliable datagrams over a QUIC connection. This document describes a scheme that allows an HTTP client to communicate its preferences for how the upstream server prioritizes responses to its requests, and also allows a server to hint to a downstream intermediary how its responses should be prioritized when they are forwarded. This document defines the Priority header field for communicating the initial priority in an HTTP version-independent manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing responses. These share a common format structure that is designed to provide future extensibility. Google LLC Cloudflare This document describes HTTP Datagrams, a convention for conveying multiplexed, potentially unreliable datagrams inside an HTTP connection. In HTTP/3, HTTP Datagrams can be sent unreliably using the QUIC DATAGRAM extension. When the QUIC DATAGRAM frame is unavailable or undesirable, they can be sent using the Capsule Protocol, a more general convention for conveying data in HTTP connections. HTTP Datagrams and the Capsule Protocol are intended for use by HTTP extensions, not applications. Google LLC This document describes how to proxy UDP in HTTP, similar to how the HTTP CONNECT method allows proxying TCP in HTTP. More specifically, this document defines a protocol that allows an HTTP client to create a tunnel for UDP communications through an HTTP server that acts as a proxy. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields that wish to use a common syntax that is more restrictive than traditional HTTP field values. Informative References This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.

Change Log

• RFC Editor's Note: Please remove this section prior to publication of a final version of this document.

Since draft-pardue-masque-dgram-priority-01

• Realign with Extensible Priorities RFC
• Realign with latest HTTP datagram and capsule protocol draft
• Add CONTEXT_PRIORITY capsule for prioritizing individual contexts
• Better explain that competing stream and datagram flows should share bandwidth but refrain from requiring any specific ratios.

Acknowledgements This document is inspired by discussion by many people across HTTP, QUIC and MASQUE WGs.