Re: sockets APIs extensions for Host Identity Protocol

Keith Moore <moore@cs.utk.edu> Wed, 09 May 2007 14:23 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hln4Y-0007KZ-EP; Wed, 09 May 2007 10:23:18 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Hln4X-0007GF-Jn for discuss-confirm+ok@megatron.ietf.org; Wed, 09 May 2007 10:23:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hln4X-0007Ei-9s for discuss@apps.ietf.org; Wed, 09 May 2007 10:23:17 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hln4W-0001as-2c for discuss@apps.ietf.org; Wed, 09 May 2007 10:23:17 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 681331EE188; Wed, 9 May 2007 10:23:15 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (shu.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8yQ8SK68enhf; Wed, 9 May 2007 10:23:10 -0400 (EDT)
Received: from lust.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182]) by shu.cs.utk.edu (Postfix) with ESMTP id EF4F81EE1BD; Wed, 9 May 2007 10:23:09 -0400 (EDT)
Message-ID: <4641D94C.9070304@cs.utk.edu>
Date: Wed, 09 May 2007 10:23:08 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
Subject: Re: sockets APIs extensions for Host Identity Protocol
References: <Pine.SOL.4.64.0705041801060.14418@kekkonen.cs.hut.fi> <20070507082737.GB21759@nic.fr> <46413DD7.8020702@cs.utk.edu> <20070509121703.GA21070@nic.fr> <4641CA52.70504@cs.utk.edu> <Pine.LNX.4.64.0705091449360.26169@hermes-1.csi.cam.ac.uk>
In-Reply-To: <Pine.LNX.4.64.0705091449360.26169@hermes-1.csi.cam.ac.uk>
X-Enigmail-Version: 0.95.0
OpenPGP: id=E1473978
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

>> Fourth, for a variety of reasons, DNS names are not and have never been
>> adequate as general purpose endpoint identifiers, and this situation is
>> getting worse rather than better.  One reason is that DNS names are not
>> equivalent to host names, and emphatically not equivalent to
>> distinguished host names, and haven't been so at least since the web
>> came into existence.  A given DNS name might be bound to a single host,
>> multiple hosts having more-or-less equivalent function, a service, a
>> community of users, or whatever; the binding might be stable or
>> ephemeral; and the name might or might not be suitable as a
>> distinguished name (one chosen preferentially over others for use in
>> indicating that host, group of hosts, service, whatever).  There's no
>> way to tell.
>>     
>
> All of this is true for IP addresses as well.
>   

good point.  though if you collect multiple hosts under the same IP
address, without considering how this will affect the apps that run on
those hosts, you pretty much deserve to lose. 

neither DNS names nor IP addresses work very well as endpoint identifiers.

Keith