RFC 5482: TCP User Timeout Option
In plain English — editorial summary, not part of the RFC
The TCP user timeout controls how long transmitted data may remain unacknowledged before a connection is forcefully closed. It is a local, per-connection parameter. This document specifies a new TCP option -- the TCP User Timeout Option -- that allows one end of a TCP connection to advertise its current user timeout value. This information provides advice to the other end of the TCP connection to adapt its user timeout accordingly. Increasing the user timeouts on both ends of a TCP connection allows it to survive extended periods without end-to-end connectivity. Decreasing the user timeouts allows busy servers to explicitly notify their clients that they will maintain the connection state only for a short time without connectivity. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5482
- Published
- March 2009
- Authors
- L. Eggert; F. Gont
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5682Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCPCurrent
September 2009
- RFC 5827Early Retransmit for TCP and Stream Control Transmission Protocol (SCTP)Current
April 2010
- RFC 5925The TCP Authentication OptionCurrent
June 2010
- RFC 5926Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)Current
June 2010
- RFC 4898TCP Extended Statistics MIBCurrent
May 2007
- RFC 6093On the Implementation of the TCP Urgent MechanismObsoleted
January 2011
- RFC 4653Improving the Robustness of TCP to Non-Congestion EventsCurrent
August 2006
- RFC 6675A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment (SACK) for TCPCurrent
August 2012
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?