The NewReno Modification to TCP's Fast Recovery Algorithm (RFC3782)
Original Publication Date: 2004-Apr-01
Included in the Prior Art Database: 2004-Apr-27
Internet Society Requests For Comment (RFCs)
S. Floyd: AUTHOR [+2]
The purpose of this document is to advance NewReno TCP's Fast Retransmit and Fast Recovery algorithms in RFC 2582 from Experimental to Standards Track status.
Network Working Group S. Floyd
Request for Comments: 3782 ICSI
Obsoletes: 2582 T. Henderson
Category: Standards Track Boeing
The NewReno Modification to TCP's Fast Recovery Algorithm
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2004). All Rights Reserved.
The purpose of this document is to advance NewReno TCP's Fast
Retransmit and Fast Recovery algorithms in RFC 2582 from Experimental
to Standards Track status.
The main change in this document relative to RFC 2582 is to specify
the Careful variant of NewReno's Fast Retransmit and Fast Recovery
algorithms. The base algorithm described in RFC 2582 did not attempt
to avoid unnecessary multiple Fast Retransmits that can occur after a
timeout. However, RFC 2582 also defined "Careful" and "Less Careful"
variants that avoid these unnecessary Fast Retransmits, and
recommended the Careful variant. This document specifies the
previously-named "Careful" variant as the basic version of NewReno
Floyd, et al. Standards Track [Page 1]
RFC 3782 NewReno Modification to Fast Recovery Algorithm April 2004
For the typical implementation of the TCP Fast Recovery algorithm
described in [RFC2581] (first implemented in the 1990 BSD Reno
release, and referred to as the Reno algorithm in [FF96]), the TCP
data sender only retransmits a packet after a retransmit timeout has
occurred, or after three duplicate acknowledgements have arrived
triggering the Fast Retransmit algorithm. A single retransmit
timeout might result in the retransmission of several data packets,
but each invocation of the Fast Retransmit algorithm in RFC 2581
leads to the retransmission of only a single...