Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!UXC.CSO.UIUC.EDU!krol
From: krol@UXC.CSO.UIUC.EDU (Ed Krol)
Newsgroups: comp.protocols.tcp-ip
Subject: Life after source quench
Message-ID: <8711091137.AA13007@uxc.cso.uiuc.edu>
Date: Mon, 9-Nov-87 06:37:57 EST
Article-I.D.: uxc.8711091137.AA13007
Posted: Mon Nov  9 06:37:57 1987
Date-Received: Sun, 15-Nov-87 10:16:41 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12


The following is an excerpt from a paper by Charlie Kline 
(kline@uxc.cso.uiuc.edu) given at this summers Sigcom in Stowe describing
the Cray CTSS source quenched algorithm which Dave seems impressed
by:

  CTSS TCP/IP treats quenches as IP events rather than TCP events. Berkeley
  responds to quenches by reducing the size of the TCP window. We respond, as
  suggested by Postel in a draft RFC, by introducing a delay between the
  sending of IP packets to the host which is producing the quenches. The delay
  increases linearly as more quenches are received. If no quenches are
  received in a certain interval, the interval is decreased exponentially.