On reducing the number of TimeOuts for short-lived TCP connections
draft-ayesta-to-short-tcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Urtzi Ayesta , Konstantin Avrachenkov | ||
| Last updated | 2002-10-21 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document shows that short TCP sessions are prone to timeout. In particular, one single segment loss will provoke TCP to timeout if the document size is below certain threshold. This document analyzes the benefit of TCP modifications such as Limited Transmit Algorithm [RFC3042] and Increasing Initial Window [RFC2414] in the context of short-lived TCP transfers. However TCP remains vulnerable to the losses at the very end of the transmission. Therefore we suggest complementary modifications to Limited Transmit Algorithm to recover effectively from losses at the end of the TCP transfer.
Authors
Urtzi Ayesta
Konstantin Avrachenkov
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)