Evaluation of RFC 4138
draft-kojo-tcpm-frto-eval-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Markku Kojo , Kazunori Yamamoto , Max Hata , Pasi Sarolahti | ||
| Last updated | 2007-11-19 | ||
| 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
Forward-RTO recovery (F-RTO) specified in RFC 4138 is an algorithm for detecting a spurious retransmission timeout with TCP and SCTP. This document describes the advantages of F-RTO and summarizes the experience in its implementations and the experiments conducted with it. By analyzing the implications of the spurious retransmission timeouts on the regular RTO recovery and Forward-RTO recovery algorithm, including a detailed corner case analysis, it shows that F-RTO does not have negative impact on the network when used with an appropriate response algorithm even in the rare cases where F-RTO falsely declares a retransmission timeout spurious. It concludes with a recommendation that F-RTO is to be advanced to the standards track.
Authors
Markku Kojo
Kazunori Yamamoto
Max Hata
Pasi Sarolahti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)