Visual RFC.
ALL RFCs / RFC 9000
Read the RFC ↗
RFC 9000 / MECHANISMS

Recover data, not packets

05

Lost information can be carried again in new frames and new packets. A sent packet number is never reused in its number space.

Related RFCs and changes

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

RFC 9000 · § 13.3EXAMPLE
3 / 3
Recover data, not packetsPacket 31’s missing stream range is identified by ACK gaps and reappears inside packet 33.RECOVER THE STREAM RANGE, NOT THE PACKETPN 31STREAM offset 0× lostPN 32later stream dataACK ranges: 30 and 32PN 33STREAM offset 0Same stream bytes · a new packet number
03
Repackage the missing information.

The same stream offset can appear in a later packet with a new packet number.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A retransmission gets a new packet identity.

  • ACK frames describe received packet-number ranges in their own packet-number space.
  • QUIC does not retransmit a lost packet whole; it determines what information still needs delivery.
  • Initial, Handshake, and Application Data use separate packet-number spaces.
DETAILS

RFC 9002 defines loss detection and congestion response. FIN ends a stream; CONNECTION_CLOSE ends the connection, with closing and draining behavior in § 10.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. Streams progress independently
  2. Stream IDs describe direction
  3. Establish a protected connection
  4. Limit data and stream counts
  5. Recover data, not packets
  6. Move a connection to a new path
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗