On Treating DUPACKs in TCP

Document Type Expired Internet-Draft (individual)
Author Andrei Gurtov 
Last updated 2002-11-01
Stream (None)
Intended RFC status (None)
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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


We suggest a more conservative management of TCP's retransmit timer and a more careful response of the TCP sender on duplicate ACKs. The former reduces the risk of triggering spurious timeouts, while the latter eliminates potentially unnecessary retransmits. Although, we believe that these suggestions are permitted (although not explicitly) by RFC2581 and RFC2988, they do not seem to be widely known nor deployed in existing TCP implementations. We therefore want to make implementers aware of these choices.


Andrei Gurtov (gurtov@cs.helsinki.fi)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)