Re: [RAM] Re: Ramblings about "locator"

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 14 June 2007 18:35 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyuAC-0000Yh-Rq; Thu, 14 Jun 2007 14:35:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyuAB-0000Yc-L5 for ram@iab.org; Thu, 14 Jun 2007 14:35:19 -0400
Received: from [2001:470:1:1:230:48ff:fe74:fd02] (helo=bender-mail.tigertech.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyuAA-0005Lj-9o for ram@iab.org; Thu, 14 Jun 2007 14:35:19 -0400
Received: from localhost (localhost [127.0.0.1]) by bender.tigertech.net (Postfix) with ESMTP id 828A77DDC for <ram@iab.org>; Thu, 14 Jun 2007 11:35:14 -0700 (PDT)
Received: from JMHLap3.joelhalpern.com (pool-71-240-234-175.fred.east.verizon.net [71.240.234.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bender.tigertech.net (Postfix) with ESMTP id 954D57DBE for <ram@iab.org>; Thu, 14 Jun 2007 11:35:13 -0700 (PDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 14 Jun 2007 14:35:08 -0400
To: ram@iab.org
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [RAM] Re: Ramblings about "locator"
In-Reply-To: <54A6A7F4-4055-48ED-A121-57B6CA0B778F@extremenetworks.com>
References: <534C54E7-21C9-4A2F-BC46-585EFCDF5101@extremenetworks.com> <C96A4A71-43B0-4CCE-BA12-4ECFB2747749@cisco.com> <54A6A7F4-4055-48ED-A121-57B6CA0B778F@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-Id: <20070614183513.954D57DBE@bender.tigertech.net>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at tigertech.net
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on bender.tigertech.net
X-Spam-Status: No, hits=-2.8 tagged_above=-999.0 required=7.0 tests=ALL_TRUSTED
X-Spam-Level:
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

This seems wrong to me.
Given any identifier we care to define, someone can later come along 
and decide to "route" to that over some scope.
If that changes the "identifier" into an "address" or a "locator" 
then the terms do not refer to the name but to the combination on the 
name and the way it happens to be used, at the moment.  That seems wrong.

I am driven more and more to a notion along the lines suggested by 
Mr. Lear, that a locator is a naming string (binary or otherwise) 
that changes when you change location, and an identifier is a naming 
string that does not change when one changes location.  (Obviously, 
there are still edge cases.)  Or, to paraphrase Noel's description 
(and to mangle some work from John Day) a locator is where given 
several such things some notions of distance (closeness, relative 
topological placement) can be applied to the entities based on those locators.

Yours,
Joel

At 02:21 PM 6/14/2007, RJ Atkinson wrote:
>>MAC addresses are used as serial numbers in many products. That is
>>an ID if I ever thought there was one. And a MAC address is
>>certainly used to find (that means "where", and "where" means
>>location) an ethernet attached station in a L2 switched network.
>
>Right.  Using my terminology proposal, that makes them "addresses"
>(i.e. objects with mixed semantics, depending on use).


_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram