Re: [RAM] Ramblings about "locator"

Marshall Eubanks <tme@multicasttech.com> Thu, 14 June 2007 12:47 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 1HyojE-0005NV-PB; Thu, 14 Jun 2007 08:47:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyojD-0005NK-SK for ram@iab.org; Thu, 14 Jun 2007 08:47:07 -0400
Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyojC-0006zY-BY for ram@iab.org; Thu, 14 Jun 2007 08:47:07 -0400
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 7171628; Thu, 14 Jun 2007 08:47:04 -0400
In-Reply-To: <4671016C.7090200@gmail.com>
References: <4671016C.7090200@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <2D7BD830-65B2-44B8-8E70-D6A1955CE540@multicasttech.com>
Content-Transfer-Encoding: 7bit
From: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: [RAM] Ramblings about "locator"
Date: Thu, 14 Jun 2007 08:46:57 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ram@iab.org
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

Dear Brian;

On Jun 14, 2007, at 4:50 AM, Brian E Carpenter wrote:

> I was thinking about why we're having trouble being crisp about
> "locator".
>
> Maybe part of it is that in some contexts, as Noel hinted, a
> locator is loaded with topological significance. If the
> network topology in a given region is a strict binary
> hierarchy, then the locator may be very tightly mapped
> to the topology (and is in effect a route). But in other
> regions of the network where the topology is an arbitrary
> graph, the same locator has no mapping to topology and needs
> to be bound to a route by a routing protocol.
>
> Another thought is that on a classical broadcast Ethernet,
> an Ethernet address is a locator, but a rather strange one
> in that nobody except the receiver knows where the located
> interface is. But the same Ethernet address on a switched
> Ethernet or in a spanning tree becomes much more
> like a network-level locator; it's mapped to topology by
> the switching or bridging mechanism.
>

> Maybe the essential point is that a locator can at least in
> principle be mapped to topology and an identifier can't.
>

If in Ethernet what is essentially a random number (the MAC address)  
becomes
a locator then maybe the distinction will never be crisp.

Regards
Marshall



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


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