Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!BRL.ARPA!jcp
From: jcp@BRL.ARPA (Joe Pistritto, JHU|mike)
Newsgroups: mod.protocols.tcp-ip
Subject: Re:  overly short RTT's
Message-ID: <8611031459.aa09631@SEM.BRL.ARPA>
Date: Mon, 3-Nov-86 14:59:10 EST
Article-I.D.: SEM.8611031459.aa09631
Posted: Mon Nov  3 14:59:10 1986
Date-Received: Tue, 4-Nov-86 10:44:59 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12
Approved: tcp-ip@sri-nic.arpa


	No, it is clearly inappropriate for Gateways to assume that TCP
is being transmitted, or to have knowledge of everything in them.  However,
(and I agree that this greatly complicates building gateways), I think the
gateways SHOULD have some knowledge of what the 'real' bandwidth available
into another gateway (and hopefully beyond that gateway to the final
destination) is, and try actively not to exceed it.  It seems that ICMP
source quenches when appropriate would greatly alleviate the problem.
(assuming of course that all implementations reacted intelligently to
a source quench....)

						-jcp-