Re: [nbs] First draft agenda

Lars Eggert <lars.eggert@nokia.com> Wed, 27 October 2010 12:57 UTC

Return-Path: <lars.eggert@nokia.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 1F5F83A694A for <nbs@core3.amsl.com>; Wed, 27 Oct 2010 05:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.953
X-Spam-Level:
X-Spam-Status: No, score=-102.953 tagged_above=-999 required=5 tests=[AWL=-0.654, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 25msDz3HAV+M for <nbs@core3.amsl.com>; Wed, 27 Oct 2010 05:57:40 -0700 (PDT)
Received: from mgw-sa02.nokia.com (mgw-sa02.nokia.com [147.243.1.48]) by core3.amsl.com (Postfix) with ESMTP id 0DFDC3A69F8 for <nbs@ietf.org>; Wed, 27 Oct 2010 05:57:39 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-sa02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o9RCxPAf024942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Oct 2010 15:59:26 +0300
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.4 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/signed; boundary=Apple-Mail-63-639511413; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <EBA3CA08-905F-4CAE-86E4-E05FD398FB20@free.fr>
Date: Wed, 27 Oct 2010 15:59:16 +0300
Message-Id: <116CC7E2-56EF-4FC9-8B8B-295C20E3563F@nokia.com>
References: <E84E7B8FF3F2314DA16E48EC89AB49F0752719@PALLENE.office.hd> <722633D9-BA33-498E-A2A3-3194B6020806@nokia.com> <EBA3CA08-905F-4CAE-86E4-E05FD398FB20@free.fr>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
X-Mailer: Apple Mail (2.1081)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Wed, 27 Oct 2010 15:59:17 +0300 (EEST)
X-Nokia-AV: Clean
Cc: "nbs@ietf.org" <nbs@ietf.org>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [nbs] First draft agenda
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: Wed, 27 Oct 2010 12:57:41 -0000

HI,

On 2010-10-27, at 15:33, Rémi Després wrote:
> Yes, knowing whether some OS or application implementers already are, at this early stage, interested in Name Based Sockets  can be a useful third issue.
> 
> But even if there is none today, this IMHO doesn't mean that those that are ready to spend energy to make a sound proposal should be discouraged: 
> - We know we need referrals that don't depend on addresses (addresses may be dynamic or subject to renumbering).
> - Using names for this is an alternative to other locator/identifier separation approaches.
> - It has the distinct advantage leveraging existing Internet specifications such as the DNS and IPv6 address formats, rather than departing from them.

I'm with you until here.

> For OS and Application vendors to make their an opinion, clearly explaining first what is meant by named based sockets seems a quite reasonable approach.

Here I have to disagree. We don't (normally) charter WGs in the IETF to explain technologies. We charter WGs to produce specifications so that interoperable implementations can be built. A specification is not a good way to explain a technology or motivate its adoption, that needs to come *first*.

Lars