Re: [nbs] NBS and TCP connection identification

"David Harrington" <ietfdbh@comcast.net> Tue, 05 October 2010 11:21 UTC

Return-Path: <ietfdbh@comcast.net>
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 B262A3A6F33 for <nbs@core3.amsl.com>; Tue, 5 Oct 2010 04:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.571
X-Spam-Level:
X-Spam-Status: No, score=-101.571 tagged_above=-999 required=5 tests=[AWL=-0.461, BAYES_05=-1.11, 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 Ym6EGJGxTi0k for <nbs@core3.amsl.com>; Tue, 5 Oct 2010 04:21:19 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id B0E613A6F2F for <nbs@ietf.org>; Tue, 5 Oct 2010 04:21:19 -0700 (PDT)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta01.westchester.pa.mail.comcast.net with comcast id EyjR1f0020ldTLk51zNHKD; Tue, 05 Oct 2010 11:22:17 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta04.westchester.pa.mail.comcast.net with comcast id EzNH1f0062JQnJT3QzNHQk; Tue, 05 Oct 2010 11:22:17 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Christian Vogt'" <christian.vogt@ericsson.com>, "'Erik Nordmark'" <erik.nordmark@oracle.com>
References: <4C97D9A8.2050001@oracle.com><ACE9611A-9107-46EC-ADD2-56E553DC1C3A@ericsson.com><4C9826D0.2060703@oracle.com> <1285067950.2068.59.camel@bit><4C98D525.1030808@oracle.com> <1285148838.2211.60.camel@bit><4C9A38A1.9060307@oracle.com> <1285251552.2225.109.camel@bit><4CA60E4B.9050803@oracle.com> <0AEEB537-CAF7-4A14-9BCA-2EE5480CB0B5@ericsson.com>
Date: Tue, 5 Oct 2010 07:21:00 -0400
Message-ID: <83CCCA1E81D748E7A87A6544C7E8EFF7@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <0AEEB537-CAF7-4A14-9BCA-2EE5480CB0B5@ericsson.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-Index: ActkE8pEf9puOydISaGCFzCMHtQMfAAaR+kg
Cc: nbs@ietf.org
Subject: Re: [nbs] NBS and TCP connection identification
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: Tue, 05 Oct 2010 11:21:20 -0000

Hi,

If consensus is that this is the goal, then the BOF should have
participation from OS vendors indicating an interest in taking on this
burden. 

The BOF will also need to explain why this work belongs in IETF,
rather than in other SDOs.

Christian's paper proposed changes to protocols, such as transport
protocol handshakes.
The BOF should explain in detail how the changes proposed would happen
only on hosts, not on routers, switches, etc.

dbh

> And I think the plan is fairly simple:  Operating system 
> vendors will take on the burden, since they will need to add 
> name-based sockets to their operating systems.  But they will 
> be incentivized:  Name-based sockets will simplify 
> application development, which has always been an objective 
> of operating system vendors.
> 
> Once operating systems support name-based sockets, we are 
> good.  Of course, we want applications to adopt the new API 
> -- and they eventually will because this will make the life 
> of application developers simpler.  But there is no time pressure.
> 
> Finally, we won't change routers, neither will be require new 
> infrastructure.
> 
> - Christian
> 
> _______________________________________________
> nbs mailing list
> nbs@ietf.org
> https://www.ietf.org/mailman/listinfo/nbs
>