Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!cbosgd!ulysses!ucbvax!maccs.UUCP!gordan
From: gordan@maccs.UUCP.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Submission for mod-protocols-tcp-ip
Message-ID: <8704040348.AA22877@maccs.UUCP>
Date: Fri, 3-Apr-87 22:48:51 EST
Article-I.D.: maccs.8704040348.AA22877
Posted: Fri Apr  3 22:48:51 1987
Date-Received: Sun, 5-Apr-87 08:42:00 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 32
Approved: tcp-ip@sri-nic.arpa

Path: maccs!gordan
From: gordan@maccs.UUCP (Gordan Palameta)
Newsgroups: mod.protocols.tcp-ip
Subject: TCP retransmission
Keywords: retransmission algorithm
Message-ID: <519@maccs.UUCP>
Date: 4 Apr 87 03:48:50 GMT
Reply-To: gordan@maccs.UUCP (Gordan Palameta)
Distribution: world
Organization: DCSS, McMaster University, Hamilton, Ontario, Canada
Lines: 20

Hello...

I'm currently writing some TCP-IP code (for a PDP-11 running RT-11), and am
looking to do retransmissions correctly.

From what I've read here, poor retransmission behavior is a major source
of congestion... although my code is intended for a very lightly loaded
Ethernet and I can get away with being sloppy, if there's a painless way to
do it right for the general case, it would be nice to put it in.

I understand the idea of exponential backoff, and know of the RTT-based
algorithm suggested in the RFC (which I believe is what BSD 4.2 uses (?))...
is this the proper algorithm to use, or is there a better one?

Thanks for any info...

-- 
UUCP:  ... !seismo!mnetor!lsuc!maccs!gordan   (note ..dAn or mail may bounce)
BITNET: GP@TANDEM                        ^  <---' 
                    Gordan Palameta