Re: [nbs] I-D Action:draft-ubillos-name-based-sockets-03.txt

Javier Ubillos <jav@sics.se> Tue, 19 October 2010 14:13 UTC

Return-Path: <jav@sics.se>
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 E0B473A6832 for <nbs@core3.amsl.com>; Tue, 19 Oct 2010 07:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.859
X-Spam-Level:
X-Spam-Status: No, score=-1.859 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3]
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 Ez+d-E2RI9jg for <nbs@core3.amsl.com>; Tue, 19 Oct 2010 07:13:57 -0700 (PDT)
Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by core3.amsl.com (Postfix) with ESMTP id 42CF03A6809 for <nbs@ietf.org>; Tue, 19 Oct 2010 07:13:57 -0700 (PDT)
Received: from [193.10.66.63] (bit.sics.se [193.10.66.63]) (Authenticated sender: jav@sics.se) by letter.sics.se (Postfix) with ESMTPSA id A493840008; Tue, 19 Oct 2010 16:15:27 +0200 (CEST)
From: Javier Ubillos <jav@sics.se>
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <23ACFA24-8FE7-4E74-8289-493AF9F12A4A@free.fr>
References: <20100917140001.E64E93A69BA@core3.amsl.com> <4CBA725A.30702@gmail.com> <1287493383.2189.89.camel@bit> <23ACFA24-8FE7-4E74-8289-493AF9F12A4A@free.fr>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-g5vENKMefG+wBmYp0cQh"
Date: Tue, 19 Oct 2010 16:15:26 +0200
Message-ID: <1287497726.2189.113.camel@bit>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3
Cc: nbs@ietf.org
Subject: Re: [nbs] I-D Action:draft-ubillos-name-based-sockets-03.txt
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, 19 Oct 2010 14:13:59 -0000

On Tue, 2010-10-19 at 16:03 +0200, Rémi Després wrote:
> Le 19 oct. 2010 à 15:03, Javier Ubillos a écrit :
> >>> ...
> >>>   o  ip6.arpa.  Using one of the hosts interfaces addresses as a name.
> >> 
> >> Why would I want to use this?
> > 
> > Another thing I should be more explicit about.
> > This is a construct for when a host does not have a name associated with
> > it. Then a name can be synthesized for it.
> 
> Since translations from addresses to names are generally time consuming, and not necessarily as up to date as those from names to addresses, this should, as  minimum, be an option that applications would have to request.

The whole reverse-resolution/ip6.arpa infrastructure is not very broadly
deployed.

The way I see it, it's comparable with a nonce, but which _might_
contain some valuable extra information (the IP the communication was
started with).

Also, i6.arpa -> name could very well generate multiple answers. How do
you know which one is right.

In other words, this is not a huge deal, the intention is to _maybe_
provide something that _might_ be more informative than an arbitrary
label.
If too many finds that it is just confusing and an eye-sore, we'll have
to reconsider that possibility.

// Javier