TCP User TimeOut (UTO) Option
draft-eggert-gont-tcpm-tcp-uto-option-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Lars Eggert , Fernando Gont | ||
| Last updated | 2004-10-22 | ||
| 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-eggert-gont-tcpm-tcp-uto-option-01.txt
Abstract
The TCP user timeout controls how long transmitted data may remain unacknowledged before a connection is aborted. TCP implementations typically use a single, system-wide user timeout value. The TCP User Timeout Option allows conforming TCP implementations to exchange requests for individual, per-connection user timeouts. Lengthening the system-wide default user timeout allows established TCP connections to survive extended periods of disconnection. On the other hand, shortening the default user timeout allows busy servers to explicitly notify their clients they will maintain the connection state information only accross short periods of disconnection.
Authors
Lars Eggert
(lars@netapp.com)
Fernando Gont
(fernando@gont.com.ar)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)