NewReno Modification for Smooth Recovery After Fast Retransmission
draft-nishida-newreno-modification-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Yoshifumi Nishida | ||
| Last updated | 2010-03-02 (Latest revision 2009-08-10) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-nishida-newreno-modification-02.txt
https://www.ietf.org/archive/id/draft-nishida-newreno-modification-02.txt
Abstract
This memo describes a feeble point in Fast Recovery algorithm in NewReno defined in RFC3782 and proposes a simple modification to solve the problem.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)