[Tsvwg] RFC 2988 on Computing TCP's Retransmission Timer
RFC Editor <rfc-ed@isi.edu> Tue, 07 November 2000 20:43 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20042 for <tsvwg-archive@odin.ietf.org>; Tue, 7 Nov 2000 15:43:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15367; Tue, 7 Nov 2000 15:35:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15336 for <tsvwg@ns.ietf.org>; Tue, 7 Nov 2000 15:35:50 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18321; Tue, 7 Nov 2000 15:35:47 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id MAA29392; Tue, 7 Nov 2000 12:35:45 -0800 (PST)
Message-Id: <200011072035.MAA29392@boreas.isi.edu>
To: IETF-Announce:;
Cc: rfc-ed@isi.edu, tsvwg@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 07 Nov 2000 12:35:45 -0800
From: RFC Editor <rfc-ed@isi.edu>
Subject: [Tsvwg] RFC 2988 on Computing TCP's Retransmission Timer
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
X-BeenThere: tsvwg@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 2988 Title: Computing TCP's Retransmission Timer Author(s): V. Paxson, M. Allman Status: Standards Track Date: November 2000 Mailbox: vern@aciri.org, mallman@grc.nasa.gov Pages: 8 Characters: 15280 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-paxson-tcp-rto-01.txt URL: ftp://ftp.isi.edu/in-notes/rfc2988.txt This document defines the standard algorithm that Transmission Control Protocol (TCP) senders are required to use to compute and manage their retransmission timer. It expands on the discussion in section 4.2.3.1 of RFC 1122 and upgrades the requirement of supporting the algorithm from a SHOULD to a MUST. This document is a product of the Transport Area Working Group Working Group of the IETF. This is now a Proposed Standard Protocol. 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. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.