Visual RFC.
ALL RFCs / RFC 9293
Read the RFC ↗
RFC 9293 / CONTROLLING THE RATE

Flow control

07

The advertised window limits how far the sender may send beyond acknowledged data, protecting the receiving endpoint.

Related RFCs and changes

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

RFC 9293 · § 3.8.6EXAMPLE
4 / 4
Flow controlOccupied buffer slots become free after an application read, and the advertised sending allowance reopens.RECEIVE BUFFER · illustrative slotsEFGHfreefreefreefreeRead A–D → four slots become freeSenderReceiverqueued byteswindow = 4window opensprobedata resumesApplication reads free capacity; a window update reports it
04
Allow transmission to resume.

The next window report tells the sender that space is available.

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

A zero window pauses ordinary new data.

  • The advertised window represents the sequence range the receiver is prepared to accept.
  • Zero-window probing must be supported so a lost reopening update cannot deadlock the connection.
  • Resource-management policy can still reclaim a stalled connection.
DETAILS

Flow control protects receiver capacity. Congestion control separately limits pressure on the network.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. A reliable byte stream
  2. Headers & connections
  3. Three-way handshake
  4. Sequence & acknowledgment
  5. Initial sequence numbers
  6. Loss & retransmission
  7. Flow control
  8. Congestion control
  9. Segments & small writes
  10. Graceful close
  11. Resets & idle probes
  12. Security & the consolidated spec
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗