TCP Adaptive User TimeOut (AUTO) Option
draft-gont-tcpm-tcp-auto-option-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Fernando Gont | ||
| Last updated | 2004-05-19 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-gont-tcpm-tcp-auto-option-00.txt
Abstract
The original TCP specification (RFC 793) defines a "USER TIMEOUT" parameter that sets the policy as to when a user connection should be aborted. However, TCP provides no means of letting users suggest an abort policy to a remote peer dynamically. Even though a fixed policy may work well in many cases, there are a number of scenarios where a fixed USER TIMEOUT value may be inappropriate, and some means of setting the abort policy dynamically may be necessary for TCP to be used effectively in such scenarios. This document defines a new TCP option, which lets a TCP peer suggest a USER TIMEOUT value to a remote TCP during the connection-establishment phase, and modify it during the life of a connection, thus adapting TCP's connection-abort policy as necessary.
Authors
Fernando Gont (fernando@gont.com.ar)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)