Adjusting the Duplicate ACK Threshold to Avoid Spurious Retransmits
draft-blanton-dupack-thresh-adjust-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ethan Blanton , Mark Allman | ||
| Last updated | 2001-07-16 | ||
| 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 outlines steps TCP and SCTP senders can take after the determine that a spurious retransmission has been sent to revert a needless change of the congestion control state. In addition, we present several methods to prevent or mitigate unnecessary TCP and SCTP fast retransmits in the face of segment reordering.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)