Separate QUIC connection IDs, packet numbers, and stream flow control

Treat this document as a focused evidence review: Separate QUIC connection IDs, packet numbers, and stream flow control. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 9000 — QUIC: A UDP-Based Multiplexed and Secure Transport from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• Each QUIC endpoint selects connection IDs that route packets back to itself and identify the connection despite lower-layer address changes; externally correlatable information MUST NOT be encoded in those IDs. The research record locates this support at Section 5.1 (Connection ID).
• QUIC uses Initial, Handshake, and application-data packet-number spaces; numbers increase within each space and an endpoint MUST NOT reuse a number in the same space on one connection. The research record locates this support at Section 12.3 (Packet Numbers).
• MAX_DATA limits data across the whole connection, while MAX_STREAM_DATA limits data on the identified stream; both limits participate in QUIC flow control. The research record locates this support at Sections 19.9 (MAX_DATA Frames) and 19.10 (MAX_STREAM_DATA Frames).

The source support ends with the statements listed above. Use them to examine clients, origin services, intermediaries, caches, proxies, gateways, protocol versions, and security-policy enforcement points in the applicable environment, not to imply a wider guarantee.

What the source does not establish

This RFC evidence supports only the named web or transport decision; it does not prove browser, intermediary, library, or service compatibility. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that DNS, certificates, identity providers, time, content delivery, network paths, and application ownership are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at Section 5.1 (Connection ID), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 12.3 (Packet Numbers), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Sections 19.9 (MAX_DATA Frames) and 19.10 (MAX_STREAM_DATA Frames), which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of clients, origin services, intermediaries, caches, proxies, gateways, protocol versions, and security-policy enforcement points are in and out of scope?
• Which condition in DNS, certificates, identity providers, time, content delivery, network paths, and application ownership must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of clients, origin services, intermediaries, caches, proxies, gateways, protocol versions, and security-policy enforcement points, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for DNS, certificates, identity providers, time, content delivery, network paths, and application ownership and sanitize protected material before retention.

Verification and evidence

Tie each conclusion back to Section 5.1 (Connection ID); Section 12.3 (Packet Numbers); Sections 19.9 (MAX_DATA Frames) and 19.10 (MAX_STREAM_DATA Frames) and to observable material such as request and response captures, negotiated protocol details, headers, cache behavior, certificate state, and server or proxy logs. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• RFC 9000 — QUIC: A UDP-Based Multiplexed and Secure Transport — RFC Editor / Internet Engineering Task Force