RFC 9959: Careful Resume: Convergence of Congestion Control from Retained State
In plain English — editorial summary, not part of the RFC
This document specifies a cautious method for Internet transports that enables fast startup of Congestion Control (CC) for a wide range of connections, known as "Careful Resume". It reuses a set of computed CC parameters that are based on previously observed path characteristics between the same pair of transport endpoints. These parameters are saved, allowing them to be later used to modify the CC behaviour of a subsequent connection. This document describes the assumptions and defines the requirements for how a sender utilises these parameters to provide opportunities for a connection to more rapidly get up to speed and utilise available capacity. It discusses how the use of this method impacts the capacity at a shared network bottleneck and the safe response that is needed after any indication that the new rate is inappropriate.
Document record
- Document ID
- RFC9959
- Published
- May 2026
- Authors
- N. Kuhn; E. Stephan; G. Fairhurst; R. Secchi; C. Huitema
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 9114HTTP/3Current
June 2022
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 9743Specifying New Congestion Control AlgorithmsCurrent
March 2025
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 9438CUBIC for Fast and Long-Distance NetworksCurrent
August 2023
- RFC 9406HyStart++: Modified Slow Start for TCPCurrent
May 2023
- RFC 9368Compatible Version Negotiation for QUICCurrent
May 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?