Streams progress independently
01A connection multiplexes ordered byte streams. A gap in one stream does not inherently block delivery on another.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 2.2 ↗
RFC 9000 · § 2.2EXAMPLE
3 / 3
03
Deliver another stream’s contiguous bytes.
Stream 4 does not wait for stream 0’s missing byte range.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Order belongs within each stream.
- STREAM frames carry a stream ID, an offset, and data.
- Ordered delivery requires buffering out-of-order bytes within the affected stream.
- Independent delivery does not remove shared connection flow control or congestion constraints.
Applications can still introduce dependencies between streams. QUIC does not promise that all streams have independent network capacity.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy