From owner-freebsd-net@FreeBSD.ORG  Tue Aug 31 21:32:56 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F0E301065674;
	Tue, 31 Aug 2010 21:32:56 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id C8F2E8FC13;
	Tue, 31 Aug 2010 21:32:56 +0000 (UTC)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
	by cyrus.watson.org (Postfix) with ESMTPS id 6FBEC46B51;
	Tue, 31 Aug 2010 17:32:56 -0400 (EDT)
Date: Tue, 31 Aug 2010 22:32:56 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Andre Oppermann <andre@freebsd.org>
In-Reply-To: <4C7D0089.1020104@freebsd.org>
Message-ID: <alpine.BSF.2.00.1008312228540.90811@fledge.watson.org>
References: <4C7A7B25.9040300@freebsd.org>
	<alpine.BSF.2.00.1008311102220.22661@fledge.watson.org>
	<4C7D0089.1020104@freebsd.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-net@freebsd.org
Subject: Re: Removal of deprecated implied connect for TCP
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2010 21:32:57 -0000


On Tue, 31 Aug 2010, Andre Oppermann wrote:

>> I'm not entirely comfortable with this change, and would like a chance to 
>> cogitate on it a bit more. While I'm not aware of any applications 
>> depending on the semantic for TCP, I know that we do use it for UNIX domain 
>> sockets.
>
> I don't have any plans to remove the implied connect support from the socket 
> layer or other protocols, only from TCP.

Right -- the implicit question is: why should TCP be the only stream protocol 
in our stack *not* to support implied connection, when we plan to continue to 
support it for all other protocols?

> For deprecating this part of the TCP API there is no documentation to the 
> implied connect in tcp(4).  In sendto(2) it doesn't differentiate between 
> protocols and simply says: "... sendto() and sendmsg() may be used at any 
> time."  For MSG_EOF it says that is only supported for SOCK_STREAM sockets 
> in the PF_INET protocol family. These sentences have to be corrected.

In general, deprecating is taken to mean providing significant and explicit 
advance warning of removal -- for example, updating the 8.x man page to point 
out that the feature is deprecated and it will not appear in future releases 
of FreeBSD.

Robert