RFC 9040: TCP Control Block Interdependence
In plain English — editorial summary, not part of the RFC
This memo provides guidance to TCP implementers that is intended to help improve connection convergence to steady-state operation without affecting interoperability. It updates and replaces RFC 2140's description of sharing TCP state, as typically represented in TCP Control Blocks, among similar concurrent or consecutive connections.
Document record
- Document ID
- RFC9040
- Published
- July 2021
- Authors
- J. Touch; M. Welzl; S. Islam
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 29
- Also known as
- —
- Obsoletes:
- RFC 2140
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9039Uniform Resource Names for Device IdentifiersCurrent
June 2021
- RFC 9065Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport ProtocolsCurrent
July 2021
- RFC 9071RTP-Mixer Formatting of Multiparty Real-Time TextCurrent
July 2021
- RFC 9002QUIC Loss Detection and Congestion ControlCurrent
May 2021
- RFC 9001Using TLS to Secure QUICCurrent
May 2021
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 8999Version-Independent Properties of QUICUpdated
May 2021
- RFC 8985The RACK-TLP Loss Detection Algorithm for TCPCurrent
February 2021
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?