Re: [nbs] setsockopt() is bad.

Dave Thaler <dthaler@microsoft.com> Mon, 08 November 2010 10:05 UTC

Return-Path: <dthaler@microsoft.com>
X-Original-To: nbs@core3.amsl.com
Delivered-To: nbs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE55C28C131 for <nbs@core3.amsl.com>; Mon, 8 Nov 2010 02:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.628
X-Spam-Level:
X-Spam-Status: No, score=-108.628 tagged_above=-999 required=5 tests=[AWL=-2.017, BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5aM2b2Hk8ech for <nbs@core3.amsl.com>; Mon, 8 Nov 2010 02:05:21 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 137A228C12E for <nbs@ietf.org>; Mon, 8 Nov 2010 02:05:21 -0800 (PST)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 8 Nov 2010 02:05:36 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server (TLS) id 14.1.255.3; Mon, 8 Nov 2010 02:05:36 -0800
Received: from TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com ([169.254.5.9]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Mon, 8 Nov 2010 02:05:34 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: Javier Ubillos <jav@sics.se>, Name-based Sockets List nbs <nbs@ietf.org>
Thread-Topic: setsockopt() is bad.
Thread-Index: AQHLfyfev/ayXgsZcU6JZv7bHcM/jpNnWmog
Date: Mon, 8 Nov 2010 10:05:34 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653436B4AB@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <1289204028.1442.34.camel@asus1001px>
In-Reply-To: <1289204028.1442.34.camel@asus1001px>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [nbs] setsockopt() is bad.
X-BeenThere: nbs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Name based sockets discussion list <nbs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nbs>, <mailto:nbs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nbs>
List-Post: <mailto:nbs@ietf.org>
List-Help: <mailto:nbs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nbs>, <mailto:nbs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 10:05:22 -0000

> -----Original Message-----
> From: Javier Ubillos [mailto:jav@sics.se]
> Sent: Monday, November 08, 2010 4:14 PM
> To: Name-based Sockets List nbs; Dave Thaler
> Cc: Javier Ubillos
> Subject: setsockopt() is bad.
> 
> Dave.
> 
> You spoke during todays bof (and just now at the MPTCP group) about your
> previous experience where setsockopt()s where not a great way to go.
> 
> What did you end up doing (other than moving the setsockopt()s to the
> appendix).
> 
> What was the right way to do it then?

See RFC 3678, especially section 2.
Short answer: new functions

-Dave

> 
> // Javier