[RAM] Ramblings about "locator"

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 14 June 2007 08:50 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 1Hyl2g-000771-GZ; Thu, 14 Jun 2007 04:50:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyl2f-00074m-Nu for ram@iab.org; Thu, 14 Jun 2007 04:50:57 -0400
Received: from ug-out-1314.google.com ([66.249.92.174]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyl2e-0005F4-Em for ram@iab.org; Thu, 14 Jun 2007 04:50:57 -0400
Received: by ug-out-1314.google.com with SMTP id m2so657012uge for <ram@iab.org>; Thu, 14 Jun 2007 01:50:55 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=Nx/GUGRF71h1Q/+4ATy30Xh8MTdcPeEgn2MLAmTs/9JMyVeoBxj8uU4MOZ+J1+1YaDIe5+rjmuum7HrducicwEA3HIl0VVz23JwbpiFDGVLShy7FuYUmswihCKnlFiHIsf9QYBG5oJgOM/Xm6v3rpT0Ow5jQddW4pXfyetszdlQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=UbbHK5nSnDUHsv8CcPzokbXPTB9Gj2cWTClOAmRBcQBw4IKJLzgrU2xrLCsGEVveNUyxAsn8zELjdNKkNkravJ7saMJrNIHMIWQt3K9NaOz6t5ll5wBqEiUfUwPn3vwu11kIWLEYPf54joZuBhKk4Fm540CQkLRmoTtm6/2ftCk=
Received: by 10.67.26.6 with SMTP id d6mr1897774ugj.1181811055746; Thu, 14 Jun 2007 01:50:55 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1]) by mx.google.com with ESMTP id g30sm4263762ugd.2007.06.14.01.50.53 (version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 01:50:54 -0700 (PDT)
Message-ID: <4671016C.7090200@gmail.com>
Date: Thu, 14 Jun 2007 10:50:52 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ram@iab.org
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [RAM] Ramblings about "locator"
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

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.

    Brian



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