Practices for TCP Senders in the Face of Segment Reordering
draft-blanton-tcp-reordering-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ethan Blanton , Robert Dimond , Mark Allman | ||
Last updated | 2003-02-11 | ||
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 actions a TCP sender can take after determining that a spurious fast retransmission has been sent due to packet reordering. The document outlines the method a TCP connection can use to 'undo' needless changes made to the congestion control state. In addition, several methods to help prevent future fast retransmits are outlined.
Authors
Ethan Blanton
Robert Dimond
Mark Allman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)