Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ucbvax!tcp-ip
From: tcp-ip@ucbvax.ARPA
Newsgroups: fa.tcp-ip
Subject: Re: TCP Timer
Message-ID: <8132@ucbvax.ARPA>
Date: Thu, 13-Jun-85 15:48:50 EDT
Article-I.D.: ucbvax.8132
Posted: Thu Jun 13 15:48:50 1985
Date-Received: Fri, 14-Jun-85 04:47:54 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 20

From: "J. Noel Chiappa" <JNC@MIT-XX.ARPA>

	The TCP I did for Bridge (the one used in the CS-1/T terminal
concentrator) used the same strategy, and for exactly the same
reasons. It only kept a single timer on the oldest data. On timeout,
it sent up to one full packet of un-ack'd data. So yet another system
in that column. (I'm not sure if it still does this, since they
changed things around and ripped some stuff they didn't udnerstand the
use of, like subnet masks, out.)

	This discussion brings up an interesting point, which is that
on all except the slowest lines network traffic control wants to
deal in units of packets, not bytes, since most overhead is per
packet. Currently TCP is byte oriented because of the window and
flow control; we need to have 'conciousness raising' for higher level
protocol implementations to orient them to this aspect of IP (if
and when IP ever gets traffic control).

	Noel
-------