[tcpm] I-D Action:draft-ietf-tcpm-rfc4138bis-01.txt

Internet-Drafts@ietf.org Sun, 18 November 2007 16:20 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Itmsu-0007vK-EO; Sun, 18 Nov 2007 11:20:36 -0500
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1Itmss-0007vC-Gg for tcpm-confirm+ok@megatron.ietf.org; Sun, 18 Nov 2007 11:20:34 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Itmss-0007v0-75; Sun, 18 Nov 2007 11:20:34 -0500
Received: from ns0.neustar.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Itmsq-0007xj-00; Sun, 18 Nov 2007 11:20:34 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com []) by ns0.neustar.com (Postfix) with ESMTP id EDD0D328E7; Sun, 18 Nov 2007 16:20:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1ItmsL-000104-Se; Sun, 18 Nov 2007 11:20:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ItmsL-000104-Se@stiedprstage1.ietf.org>
Date: Sun, 18 Nov 2007 11:20:01 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: tcpm@ietf.org
Subject: [tcpm] I-D Action:draft-ietf-tcpm-rfc4138bis-01.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Errors-To: tcpm-bounces@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the TCP Maintenance and Minor Extensions Working Group of the IETF.

	Title           : Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP
	Author(s)       : P. Sarolahti, et al.
	Filename        : draft-ietf-tcpm-rfc4138bis-01.txt
	Pages           : 20
	Date            : 2007-11-18

Spurious retransmission timeouts cause suboptimal TCP performance
 because they often result in unnecessary retransmission of the last
 window of data.  This document describes the F-RTO detection
 algorithm for detecting spurious TCP retransmission timeouts.  F-RTO
 is a TCP sender-only algorithm that does not require any TCP options
 to operate.  After retransmitting the first unacknowledged segment
 triggered by a timeout, the F-RTO algorithm of the TCP sender
 monitors the incoming acknowledgments to determine whether the
 timeout was spurious.  It then decides whether to send new segments
 or retransmit unacknowledged segments.  The algorithm effectively
 helps to avoid additional unnecessary retransmissions and thereby
 improves TCP performance in the case of a spurious timeout.

A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-tcpm-rfc4138bis-01.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-tcpm-rfc4138bis-01.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
tcpm mailing list