Fine-Grained QoS Optimization for QUIC Based on Connection ID Priority Mapping

Introduction Vertical industry services (connected vehicles, remote healthcare, etc.) and AI-driven applications increasingly demand differentiated network service quality. QUIC , as a modern transport protocol, provides encryption, multiplexing, and connection migration, but currently lacks mechanisms for end-to-end QoS enforcement across the network path. QUIC's existing stream priority mechanism operates only at the endpoints. Intermediate network devices (routers, switches) do not inspect or act on QUIC priority markings because they are encrypted within the QUIC payload. Additionally, QUIC Datagrams are typically excluded from priority scheduling mechanisms. This document proposes a mechanism that bridges the gap between QUIC transport-layer priorities and network-layer QoS enforcement by leveraging the Destination Connection ID field, which remains visible in the QUIC header even under encryption, as a carrier for priority mapping table indices.

Requirements Language 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.

Terminology

DCID (Destination Connection ID):: The Connection ID field in QUIC packet headers used to identify the destination endpoint of a connection.
Stream:: A QUIC stream, an ordered byte-stream transport channel within a QUIC connection.
Datagram:: A QUIC unreliable datagram as defined in .
DSCP (Differentiated Services Code Point):: A field in the IP header for packet classification and per-hop behavior selection, defined in .
TE Policy:: Traffic Engineering policy, including MPLS TE, SRv6 TE , SDN-based TE, and cross-layer coordination TE.
Priority Mapping Table:: A lookup table that maps index Connection IDs to real Connection IDs and associated QoS parameters.
Index Prefix:: A specific byte pattern (e.g., AAB00000, configurable) used to identify that a DCID is a mapping table index rather than a real Connection ID.
Priority Controller:: A component responsible for generation, update, and management of the priority mapping table.

Problem Statement

QUIC Priorities Limited to Endpoints QUIC stream priorities are enforced through application-layer marking, transport-layer scheduling, and congestion control coordination. High-priority streams receive preferential packet encapsulation, loss retransmission, and potentially larger congestion windows. However, these priorities are effective only at the endpoints. Intermediate network devices do not process QUIC priority information, and the network layer has no awareness of QUIC-layer priorities, preventing end-to-end precise QoS enforcement.

Datagram Priority Gap Per and , QUIC priority mechanisms are primarily designed for streams. Datagrams, as an unreliable transport mode, are typically not included in priority scheduling mechanisms.

Missing Network-Layer QoS Integration QUIC transport-layer priority information cannot be directly mapped to network-layer DSCP/ToS mechanisms or traffic engineering policies, resulting in a broken end-to-end QoS enforcement chain.

Connection ID Priority Mapping Mechanism

Architecture Overview The core idea is to use the QUIC Destination Connection ID (DCID) as a carrier for priority information. Service priority is encoded as an index value in the DCID. A priority mapping table on the host NIC or user gateway translates this index into the real Connection ID and corresponding network-layer QoS parameters.

Destination Connection ID Encoding The DCID is structured as follows: DCID = Index_Prefix | Frame_Type | Stream_ID | Priority. Index Prefix: configurable byte pattern (e.g., 0xAAB00000) identifying this DCID as a mapping table index. Frame Type: 0 = STREAM frame, 1 = DATAGRAM frame. Stream ID: identifies the associated stream. Priority: optional application-specified fine-grained priority (e.g., differentiating CSS, JS, HTML objects within a web page).

Priority Mapping Table An implementation MUST construct a priority mapping table. The table deployment location depends on the deployment mode: on the host NIC for host-side deployment, or on the user gateway/router for network-side deployment. Each mapping table entry contains: Index (the DCID index value); Real DCID (the actual Connection ID used in network transmission); ToS/DSCP (network-layer QoS marking per ); TE Policy (traffic engineering policy identifier); Reserved (set to 0, reserved for future finer-grained QoS constraints).

Host-Side Workflow In host-side deployment mode: (1) The application issues a QUIC connection request via API, specifying service priority requirements. (2) Before the API request enters the host protocol stack, a mapping table index is generated and replaces the original DCID. This step MUST NOT intrude upon the host protocol stack. (3) The host QUIC stack processes the connection normally; outbound QUIC packets carry the index value as DCID. (4) The host NIC (or NIC driver) intercepts outbound packets, looks up the priority mapping table using the DCID index: replaces the DCID with the real Connection ID, sets the IP header ToS/DSCP field, and selects the corresponding TE Policy path. (5) Packets traverse the network with QoS and TE enforcement.

Priority Controller The Priority Controller is responsible for generation, update, and management of the priority mapping table. It MAY be deployed as: a standalone component; a functional module within a network controller (e.g., SDN controller); integrated within the NIC or user gateway/router. Applications MAY configure whether the ToS/TC/DSCP and TE Policy values in the mapping table are allowed to auto-adjust dynamically based on network quality feedback.

Deployment Modes Host-Side Deployment: Priority mapping table resides on the host NIC; no network-side changes required. Network-Side Deployment: Priority mapping table resides on the user gateway/router; no host-side changes required. Coordinated Deployment: Host-side and network-side collaborate on priority mapping.

Security Considerations Mapping Table Confidentiality: The priority mapping table contains real Connection IDs and QoS policy information, which constitute sensitive data. Storage and transmission of mapping table information MUST be encrypted. Index Prefix Collision: If a third party can guess the index prefix, non-mechanism traffic could be incorrectly intercepted and processed. The index prefix SHOULD have sufficient randomness or be negotiated out-of-band. Priority Escalation Attack: Malicious applications may attempt to forge high-priority identifiers to obtain unwarranted QoS treatment. The Priority Controller MUST authenticate and authorize application priority requests. Stack Non-Intrusion Safety: The DCID replacement at the API layer SHOULD NOT introduce new attack surfaces. Implementations SHOULD ensure the security of the index generation process.

IANA Considerations This document requests IANA consideration for: (1) If a standardized index prefix value is adopted, reserved space or a registered prefix within the QUIC Connection ID format may be needed. (2) If the DCID encoding format requires interoperation with the QUIC standard, registration of a new QUIC transport parameter type may be required.