RFC 9114 / MECHANISM GUIDE

HTTP over QUIC

HTTP/3 delegates transport reliability and multiplexing to QUIC.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 1.2 ↗

RFC 9114 · § 1.2EXAMPLE

3 / 3

Recover one lost range

One stream can wait while another has deliverable data.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references

WHAT CHANGED

HTTP/2 transport mappingRFC 9114 §1.2

HTTP/3 delegates flow control and stream lifetime to QUIC and relies on its per-stream reliable delivery. HTTP/2 remains a separate supported mapping.

Read the updated RFC section ↗

KEY POINT

QUIC provides encrypted transport and reliable in-order delivery per stream.

QUIC provides encrypted transport and reliable in-order delivery per stream.
Streams share congestion control and available network capacity.
Loss on one stream need not block delivery on another stream, unlike TCP-wide ordering.

DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy

All chapters in this RFC