Visual RFC.
ALL RFCs / RFC 9113
Read the RFC ↗
RFC 9113 / MECHANISM GUIDE

Receiver flow-control credit

04

DATA must fit both the stream window and the connection window.

Related RFCs and changes

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

DIAGRAM§ 5.2 ↗
RFC 9113 · § 5.2EXAMPLE
3 / 3
Receiver flow-control creditDATA must fit both the stream window and the connection window.Receiver flow-control creditIllustrative stream windowWINDOW_UPDATE +4 → window = 44 more bytes may be sent
03
Grant 4 more

WINDOW_UPDATE permits another 4 bytes, if connection credit also permits.

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

Flow control is directional, hop-by-hop, and receiver controlled.

  • Flow control is directional, hop-by-hop, and receiver controlled.
  • WINDOW_UPDATE grants additional credit; DATA consumes credit.
  • Only DATA is flow controlled; control frames must remain processable.
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
  1. Connection preface
  2. Multiplexed streams
  3. Frames and compressed fields
  4. Receiver flow-control credit
  5. Reset and graceful shutdown
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗