From owner-freebsd-isp Wed Jan 19 14:13:38 2000 Delivered-To: freebsd-isp@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id C935514A07 for ; Wed, 19 Jan 2000 14:13:24 -0800 (PST) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id LAA24987; Thu, 20 Jan 2000 11:13:05 +1300 (NZDT) Date: Thu, 20 Jan 2000 11:13:04 +1300 From: Joe Abley To: Damian Hasak Cc: David Wolfskill , freebsd-isp@FreeBSD.ORG, xiyuan@yahoo.com Subject: Re: net speed Message-ID: <20000120111303.B22700@patho.gen.nz> References: <20000119195314.A4167@patho.gen.nz> <003c01bf62a5$ec375b80$148190a9@dhasak-pc.fore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <003c01bf62a5$ec375b80$148190a9@dhasak-pc.fore.com>; from dhasak@fore.com on Wed, Jan 19, 2000 at 12:52:16PM -0500 X-Files: the Truth is Out There Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jan 19, 2000 at 12:52:16PM -0500, Damian Hasak wrote: > hmm but i would think jitter is more related to timing on a CBR connection Can't a noticable variation in delay in successive segments (with the timestamp option, for example) result in a wildly varying transmit window size on both sides? Somewhat implementation-specific, certainly, but in general TCP behaves much more efficiently if the round-trip time is reasonable predictable (or poorly measured, alternatively, as long as the poor measurement is reasonable :) Virtual-circuit concerns in ATM mirror session concerns in TCP to some degree, except that congestion conditions are identified (and remedied) in somewhat different ways. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message