Re: [nbs] NBS and TCP connection identification

Javier Ubillos <jav@sics.se> Tue, 28 September 2010 12:50 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 2A7B33A6DCE for <nbs@core3.amsl.com>; Tue, 28 Sep 2010 05:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[AWL=0.041, 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 89NL+-ss8obm for <nbs@core3.amsl.com>; Tue, 28 Sep 2010 05:50:38 -0700 (PDT)
Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by core3.amsl.com (Postfix) with ESMTP id 9BC023A6DC7 for <nbs@ietf.org>; Tue, 28 Sep 2010 05:50:37 -0700 (PDT)
Received: from [193.10.66.36] (bit.sics.se [193.10.66.36]) (Authenticated sender: jav@sics.se) by letter.sics.se (Postfix) with ESMTPSA id D9E1740008; Tue, 28 Sep 2010 14:51:16 +0200 (CEST)
From: Javier Ubillos <jav@sics.se>
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <EBB53DE6-2EEB-43C2-9451-0A38EBD10BAA@free.fr>
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> <DC2EB1A1-B9BE-49B0-B443-B513873B9AF2@ericsson.com> <EBB53DE6-2EEB-43C2-9451-0A38EBD10BAA@free.fr>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-79fBrR5ZgiEAgwEEc9Yy"
Date: Tue, 28 Sep 2010 14:51:15 +0200
Message-ID: <1285678275.1185.92.camel@bit>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3
Cc: Christian Vogt <christian.vogt@ericsson.com>, "nbs@ietf.org" <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, 28 Sep 2010 12:50:40 -0000

On Tue, 2010-09-28 at 11:40 +0200, Rémi Després wrote:
> Hi Christian,
> 
> In my understanding NBS and address changes can remain independent, and therefore should remain so.
> - A connection initiation starts with the source and destination names chosen by the initiator (and with valid addresses for them at that time).
> The acceptor advertises at the NBS the names it received.
> It may have before that checked, with a direct a DNS query, that source address and source name are consistent, or do it after signaling the incoming connection, or never, at its own choice. 
> - Shim6, if present, works as before.
> 
> Does this make sense to you?

Not being Christian, I'm still taking the liberty to comment ;)

I think this makes perfect sense.

It would be nice if one could verify the name immediately, but not to
have it as a requirement.

If the verification of the name is important for some feature, it could
very well be done by that feature whenever it kicks-in. E.g. shim6 does
begin to negotiate until 50(?) packets have been exchanged.


// Javier