From owner-cvs-all Wed Jul 17 19:47: 1 2002 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E02B37B400; Wed, 17 Jul 2002 19:46:54 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3E9D43E64; Wed, 17 Jul 2002 19:46:52 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 761F781499; Thu, 18 Jul 2002 12:16:49 +0930 (CST) Date: Thu, 18 Jul 2002 12:16:49 +0930 From: Greg 'groggy' Lehey To: Matthew Dillon Cc: Garrett Wollman , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Retransmission timeouts (was: cvs commit: src/sys/netinet tcp_timer.h) Message-ID: <20020718024649.GJ40633@wantadilla.lemis.com> References: <20020717185653.C82638-100000@patrocles.silby.com> <200207180102.g6I129Gw004350@apollo.backplane.com> <200207180206.g6I266ma000510@khavrinen.lcs.mit.edu> <200207180228.g6I2Scpv004823@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200207180228.g6I2Scpv004823@apollo.backplane.com> User-Agent: Mutt/1.3.99i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, 17 July 2002 at 19:28:38 -0700, Matthew Dillon wrote: > >> >> < said: >> >>> Actually, >>> I think the one second minimum is absurd anyway, so no, I am not >>> going to back it out. >> >> The standard says one second, period. It's not your choice to make. >> >> -GAWollman > > I've looked through five RFCs. I have been unable to locate any > lower bound requirement fro the retransmission timeout. The best > I've found is in RFC1122, 4.2.3.1: > > The recommended upper and lower bounds on the RTO are known > to be inadequate on large internets. The lower bound SHOULD > be measured in fractions of a second (to accommodate high > speed LANs) and the upper bound should be 2*MSL, i.e., 240 > seconds. > > All the other references I've found... New Reno and the two > congestion control RFCs (one being the fast-retransmit RFC) simply > state something on the order of 2*RTT or something similar. > > RFC793 has an eample of an RTO timeout calculation where it says > > "where UBOUND is an upper bound on the timeout (e.g., 1 minute), > LBOUND is a lower bound on the timeout (e.g., 1 second), ALPHA is > a smoothing factor (e.g., .8 to .9), and BETA is a delay variance > factor (e.g., 1.3 to 2.0)." > > This is obviously NOT a requirement of any sort, and besides it is in > RFC793... an extremely old RFC (1981). I'd put money on Garrett coming up with some reference somewhere. But that's not important. Things change, and we have to change with them. This change looks like a logical adaptation to changed network speeds. If it contravenes some standard, why not make it configurable? IMO the default should be "on". Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message