From owner-cvs-src@FreeBSD.ORG Fri Dec 15 14:57:02 2006 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E00E216A40F; Fri, 15 Dec 2006 14:57:02 +0000 (UTC) (envelope-from rodrigc@crodrigues.org) Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [206.18.177.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3551B43CA7; Fri, 15 Dec 2006 14:55:14 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from c-66-31-35-94.hsd1.ma.comcast.net ([66.31.35.94]) by comcast.net (alnrmhc14) with ESMTP id <20061215145655b1400mjjvre>; Fri, 15 Dec 2006 14:56:55 +0000 Received: from c-66-31-35-94.hsd1.ma.comcast.net (localhost.crodrigues.org [127.0.0.1]) by c-66-31-35-94.hsd1.ma.comcast.net (8.13.8/8.13.8) with ESMTP id kBFEutNh013950; Fri, 15 Dec 2006 09:56:55 -0500 (EST) (envelope-from rodrigc@c-66-31-35-94.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-66-31-35-94.hsd1.ma.comcast.net (8.13.8/8.13.8/Submit) id kBFEutRr013949; Fri, 15 Dec 2006 09:56:55 -0500 (EST) (envelope-from rodrigc) Date: Fri, 15 Dec 2006 09:56:55 -0500 From: Craig Rodrigues To: src-committers@FreeBSD.org Message-ID: <20061215145655.GA13912@crodrigues.org> References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A1E0.1050503@freebsd.org> <4582A6C9.8010009@FreeBSD.org> <20061215055704.A65183@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061215055704.A65183@xorpc.icir.org> User-Agent: Mutt/1.4.2.1i Cc: cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/net Makefile.inc sctp_sys_calls.c src/sys/sys param.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2006 14:57:03 -0000 On Fri, Dec 15, 2006 at 05:57:04AM -0800, Luigi Rizzo wrote: > i think Andre's question was this: > normally we use {set|get}sockopt() to configure the socket > as desired for special features (e.g. multicast is one). > > Why is it undesirable to use the same kind of overloading > for sctp ? I think some of the reasons for why a new sockets API was introduced for SCTP was outlined in: http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpsocket-14.txt ...but I'll let Randall chime in too. :) -- Craig Rodrigues rodrigc@crodrigues.org