Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site wdl1.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!hao!hplabs!hpda!fortune!wdl1!jbn
From: jbn@wdl1.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Purge 4.2BSD TCP tasks in FIN_WAIT_2
Message-ID: <382@wdl1.UUCP>
Date: Mon, 22-Apr-85 23:19:17 EST
Article-I.D.: wdl1.382
Posted: Mon Apr 22 23:19:17 1985
Date-Received: Fri, 26-Apr-85 22:11:43 EST
Sender: notes@wdl1.UUCP
Organization: Ford Aerospace, Western Development Laboratories
Lines: 13
Nf-ID: #R:down:-49100:wdl1:17100079:000:631
Nf-From: wdl1!jbn    Apr 22 18:51:00 1985


      The timeout in FINWAIT2 does violate the TCP spec, but unless you use
some applications that like to close one side of a connection while using
the other for a long period thereafter, it shoudn't hurt.  Since UNIX lacks
an asymmetrical close, this is not much of a problem between UNIX sites.
      It is a known bug that most TOPS-20 systems don't perform the TCP
close handshake properly.  We first noticed this problem several years ago,
and it still hasn't been fixed everywhere; the machines at BBN are OK, but
expect some minor problems from TOPS-20 sites that got the code via DEC.
      On to TP-4.

						John Nagle