Path: utzoo!attcan!uunet!samsung!olivea!orc!inews!iwarp.intel.com!ogicse!mintaka!mit-eddie!uw-beaver!zephyr.ens.tek.com!tektronix!sequent!sequent.uucp!djk
From: djk@sequent.uucp (Darin Klaas)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: connect "collisions" in TCP
Message-ID: <52067@sequent.UUCP>
Date: 1 Feb 91 01:54:28 GMT
Sender: djk@sequent.UUCP
Organization: The Hard Rock Cubicle
Lines: 13

calvert@cs.utexas.edu (Kenneth L. Calvert) writes:


>0.  My impression is that the Berkeley Unix sockets interface (to TCP)
>precludes deliberate use of this "feature".  Have I missed something?
>(The implementation does the right thing when SYN is received in state
>SYN_SENT).

In fact it doesn't do the right thing (at least 4.3-tahoe doesn't) --
follow the incoming SYN ACK and you'll see that the two sides of the connection
eventually SYN ACK each other for ever and ever...

-- darin