Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!pioneer!lamaster From: lamaster@pioneer.arpa (Hugh LaMaster) Newsgroups: comp.protocols.tcp-ip Subject: Re: TCP performance limitations Message-ID: <2939@ames.arpa> Date: Wed, 30-Sep-87 15:32:29 EDT Article-I.D.: ames.2939 Posted: Wed Sep 30 15:32:29 1987 Date-Received: Sun, 4-Oct-87 22:45:07 EDT References: <[A.ISI.EDU]30-Sep-87.09:40:42.CERF> Sender: usenet@ames.arpa Reply-To: lamaster@ames.UUCP (Hugh LaMaster) Organization: NASA Ames Research Center, Moffett Field, Calif. Lines: 26 In article <[A.ISI.EDU]30-Sep-87.09:40:42.CERF> CERF@A.ISI.EDU writes: > >What these very sketchy and rough numbers suggest is that >window-based schemes won't be very satisfactory for long haul, >long delay, very high speed nets. Flow control based on rates is needed, >rather than on round-trip acks/permissions - of course, this is precisely >the kind of thinking that I believe underlies the work that >Dave Clark has been doing with NETBLT (Dave, holler if I >have put words/thoughts into your work inappropriately). > I have seen/heard references to rate based flow control before - but I haven't seen (or maybe remembered) what the idea is. Is there a summary somewhere or could someone summarize the basic idea? (Is there an RFC? etc.) Hugh LaMaster, m/s 233-9, UUCP {topaz,lll-crg,ucbvax}! NASA Ames Research Center ames!pioneer!lamaster Moffett Field, CA 94035 ARPA lamaster@ames-pioneer.arpa Phone: (415)694-6117 ARPA lamaster@pioneer.arc.nasa.gov (Disclaimer: "All opinions solely the author's responsibility")