Skip to main content

Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)
draft-ietf-tcpm-frto-02

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    tcpm mailing list <tcpm@ietf.org>, 
    tcpm chair <tcpm-chairs@tools.ietf.org>
Subject: Document Action: 'F-RTO: An Algorithm for Detecting 
         Spurious Retransmission Timeouts with TCP and SCTP' to 
         Experimental RFC 

The IESG has approved the following document:

- 'F-RTO: An Algorithm for Detecting Spurious Retransmission Timeouts 
   with TCP and SCTP '
   <draft-ietf-tcpm-frto-03.txt> as an Experimental RFC

This document is the product of the TCP Maintenance and Minor Extensions 
Working Group. 

The IESG contact persons are Jon Peterson and Magnus Westerlund.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tcpm-frto-03.txt

Ballot Text

Technical Summary
 
This document describes an algorithm for detecting spurious TCP retransmission
timeouts called F-RTO. In contrast to alternative algorithms proposed for
detecting unnecessary retransmissions, F-RTO does not require any TCP options
for its operation, and it can be implemented by modifying only the TCP sender;
however, F-RTO detects only unnecessary retransmissions after an RTO, not
retransmissions caused by events such as packet reordering.  This document does
not describe the response to spurious timeout, merely the detection algorithm.
The mechanisms described in this document are also applicable to SCTP.
 
Working Group Summary
 
This document is one of several approaches to the detection of spurious
retransmissions that have been considered in the TSVWG and TCPM working groups.
The community believes that the publication of more than one experimental
approach to this problem will help to expose the pros and cons of the respective
methods.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.

RFC Editor Note