Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!caip!nike!ucbcad!ucbvax!MONET.BERKELEY.EDU!karels
From: karels@MONET.BERKELEY.EDU (Mike Karels)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: TCP retransmission efficiency
Message-ID: <8607280259.AA21383@monet.Berkeley.EDU>
Date: Sun, 27-Jul-86 22:59:17 EDT
Article-I.D.: monet.8607280259.AA21383
Posted: Sun Jul 27 22:59:17 1986
Date-Received: Mon, 28-Jul-86 04:34:56 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: tcp-ip@sri-nic.arpa

Phil:

I'm not sure you're up to date on TCP either.  The Nagle algorithm allows
only one *small* packet in flight (one of less than the maximum
segment size).  Essentially all applications other than telnet/remote
terminal use more than one segment per round-trip interval.  Very few
applications are satisfied with "stop and wait" mode, nor do they refrain
from sending additional data once a maximum segment sized packet has been
sent.

I don't want to think about ACKing ACKs; new data segments are sufficient
acknowledgement, and retransmitted data segments are good enough NAKs.

		Mike