A new TCP transmission policy replacing Nagle mode
draft-doupnik-nagle-mode-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Joe Doupnik | ||
| Last updated | 1999-06-14 | ||
| 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
Both Nagle mode and delayed ACKs attempt to conserve network and host machine resources by delaying transmissions in the expectation that the current material can be piggybacked onto a future transmission. Unfortunately when both mechanisms are active at the same time on either end of a connection a deadlock can exist, which is broken by arrival of new data for transmission or firing of the delayed ACK timer. This produces classical timer based ACKing, which for the common 200ms ACK delay yields five exchanges per second.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)