Path: utzoo!dciem!array!colin
From: colin@array.UUCP (Colin Plumb)
Newsgroups: comp.dcom.modems
Subject: Re: Looking for a few good terminal servers ... (summary) (long!)
Keywords: terminal server, TCP/IP, EIA232, flow control, high speed modems
Message-ID: <469@array.UUCP>
Date: 10 Aug 90 02:19:57 GMT
References: <65225@lll-winken.LLNL.GOV> <66116@lll-winken.LLNL.GOV>
Organization: Array Systems Computing, Inc., Toronto, Ontario, CANADA
Lines: 18

In article <66116@lll-winken.LLNL.GOV> casey@gauss.llnl.gov (Casey Leedom) writes:
>[[Some of our people will be dialing in to the terminal server and then
>connecting up to hosts all across the InterNet (one of the reasons we
>want passworded logins.)  If we're doing file up loading, won't slow start
>be applicable?  I'm very vague in this area, so I might be totally out to
>lunch.]]

No; slow start is only necessary if you are talking through a network
substantially slower your packet generation capabilities.  This applies
to gatewaying between ethernets with an ARPAnet 57.6kbaud line, but
not to a connection limited to 38.4kbaud, as you have.

See Van Jacobsen's paper, "Congestion Avoidance and Control," Proceedings
of the ACM SIGCOMM '88, August 1988 for pretty pictures.  Basically,
if you send all of a large window really fast, then the fast->slow gateway
starts dropping packets really fast.
-- 
	-Colin