# Drive QUIC loss detection from acknowledgments without conflating congestion control > Use RFC 9002 — QUIC Loss Detection and Congestion Control to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/drive-quic-loss-detection-from-acknowledgments-without-conflating-congestion-control/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:15:56+00:00 - Modified: 2026-08-27T12:53:58+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Playbook - DSE priority: Advisory - Topics: Cybersecurity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use RFC 9002 — QUIC Loss Detection and Congestion Control to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of RFC 9002 — QUIC Loss Detection and Congestion Control ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Drive QUIC loss detection from acknowledgments without conflating congestion control. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [RFC 9002 — QUIC Loss Detection and Congestion Control](https://www.rfc-editor.org/rfc/rfc9002.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements: - QUIC declares an in-flight packet lost only after a later packet is acknowledged and either the packet threshold or time threshold is met. The research record locates this support at Section 6.1 (Acknowledgment-Based Detection). - A Probe Timeout sends one or two probe datagrams, but expiration alone does not indicate loss and must not mark prior unacknowledged packets lost. The research record locates this support at Section 6.2 (Probe Timeout). - ACK-only packets do not count toward bytes in flight and are not congestion controlled, even though QUIC can detect when they are lost. The research record locates this support at Section 7 (Congestion Control). These statements are the factual basis for this document. Do not extend them into a broader assurance. Review clients, origin services, intermediaries, caches, proxies, gateways, protocol versions, and security-policy enforcement points only where the source and recorded environment align. ## 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 6.1 (Acknowledgment-Based Detection), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Section 6.2 (Probe Timeout), which observable configuration, record, or test can confirm applicability here? - For source statement 3 at Section 7 (Congestion Control), 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. Start with applicability, then compare the observed state with the cited source. 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. Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify DNS, certificates, identity providers, time, content delivery, network paths, and application ownership. Handle credentials, keys, recovery data, and personal information through approved secure channels. ## Verification and evidence Build a reproducible chain from Section 6.1 (Acknowledgment-Based Detection); Section 6.2 (Probe Timeout); Section 7 (Congestion Control) to the observed environment. Useful domain evidence includes request and response captures, negotiated protocol details, headers, cache behavior, certificate state, and server or proxy logs; label every item with scope, timestamp, collector, and stable identifier. 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 9002 — QUIC Loss Detection and Congestion Control](https://www.rfc-editor.org/rfc/rfc9002.html) — RFC Editor / Internet Engineering Task Force ## Primary reference - Name: RFC 9002 — QUIC Loss Detection and Congestion Control - Authority: www.rfc-editor.org - URL: https://www.rfc-editor.org/rfc/rfc9002.html - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Drive QUIC loss detection from acknowledgments without conflating congestion control,” DSE Security, https://update.dsesecurity.com/updates/drive-quic-loss-detection-from-acknowledgments-without-conflating-congestion-control/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.