From owner-freebsd-current  Wed Jan 17 02:01:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA00821
          for current-outgoing; Wed, 17 Jan 1996 02:01:40 -0800 (PST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA00815
          for <current@freebsd.org>; Wed, 17 Jan 1996 02:01:35 -0800 (PST)
Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelayMX-SVR4_1.2/RBINF)
	id LAA13572; Wed, 17 Jan 1996 11:00:19 +0100
Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB)
	id LAA03241; Wed, 17 Jan 1996 11:00:16 +0100
Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4)
	id LAA06236; Wed, 17 Jan 1996 11:00:17 +0100
To: current@freebsd.org
Subject: Re: cvs commit: src/sys/netinet tcp_output.c 
In-reply-to: Your message of "Wed, 17 Jan 1996 01:35:31 PST."
             <199601170935.BAA28984@freefall.freebsd.org> 
Date: Wed, 17 Jan 1996 11:00:15 +0100
Message-ID: <6235.821872815@curie.cs.utwente.nl>
From: Andras Olah <olah@cs.utwente.nl>
Sender: owner-current@freebsd.org
Precedence: bulk

On Wed, 17 Jan 1996 01:35:31 PST, Andras Olah wrote:
> olah        96/01/17 01:35:28
> 
>   Modified:    sys/netinet  tcp_output.c
>   Log:
>   Be more conservative when T/TCP extensions are disabled.  In particular,
>   do not send data and/or FIN on SYN segments in this case.
>   
>   Revision  Changes    Path
>   1.18      +14 -1     src/sys/netinet/tcp_output.c

>From now on, people should have now problems when using our T/TCP
aware finger to query hosts with broken TCP implementations provided
that net.inet.tcp.rfc1644 is off.  I'd like to ask people, however,
not to switch it off by default.  If you encounter problems, please
send me a note so that I can collect information about
non-conformant TCP implementations and eventually find a way to make
vendors fix their TCPs.

For people, who want to know more about T/TCP, I recommend Rich
Stevens' TCP/IP Illustrated Vol. III.  Rich also maintains a T/TCP
homepage at http://www.noao.edu/~rstevens/ttcp.html.

Andras