Re: [rrg] Locator
HeinerHummel@aol.com Wed, 13 May 2009 07:49 UTC
Return-Path: <HeinerHummel@aol.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 959E728C1CE for <rrg@core3.amsl.com>; Wed, 13 May 2009 00:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.621
X-Spam-Level:
X-Spam-Status: No, score=-0.621 tagged_above=-999 required=5 tests=[AWL=0.488, BAYES_05=-1.11, HTML_MESSAGE=0.001]
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 irN-AOH-zDOO for <rrg@core3.amsl.com>; Wed, 13 May 2009 00:49:08 -0700 (PDT)
Received: from imo-m12.mail.aol.com (imo-m12.mx.aol.com [64.12.143.100]) by core3.amsl.com (Postfix) with ESMTP id 896ED3A6F38 for <rrg@irtf.org>; Wed, 13 May 2009 00:49:08 -0700 (PDT)
Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imo-m12.mail.aol.com (v107.10) with ESMTP id RELAYIN2-34a0a7bc21af; Wed, 13 May 2009 03:50:26 -0400
Received: from HeinerHummel@aol.com by imo-da04.mx.aol.com (mail_out_v40_r1.5.) id 9.d59.4031ac99 (41811); Wed, 13 May 2009 03:50:20 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <d59.4031ac99.373bd5bc@aol.com>
Date: Wed, 13 May 2009 03:50:20 -0400
To: jnc@mercury.lcs.mit.edu, rrg@irtf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1242201020"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 205.188.169.202
Subject: Re: [rrg] Locator
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2009 07:49:10 -0000
In einer eMail vom 13.05.2009 02:13:52 Westeuropäische Normalzeit schreibt jnc@mercury.lcs.mit.edu: Ah, no. To quote RFC-1992: "A locator ... identifies a location in an internetwork. Nodes and endpoint are assigned locators. Different nodes have necessarily different locators. A node is assigned only one locator. Locators identify nodes and specify *where* a node is in the network. Locators do *not* specify a path to the node." I perfectly agree."Nodes and endpoint are assigned locators" can also be read: "Nodes and endpoints are assigned attributes (eventually in addition ?! to identifiers ) which are locators. One also needs to be aware that in this document, "node" means 'network region', not 'host/router', as it is commonly taken to mean in networking: "A node represents a region of the physical network. The region of the network represented by a node can be as large or as small as desired: a node can represent a continent or a process running inside a host. Moreover .. a region of the network can simultaneously be represented by more than one node." I perfectly agree. However I would like to caution not to do the same kind of node aggregation once again as known from PNNI. (In the next section of the document, "node" is very precisely defined to mean 'map element' - from the node/arc terminology of graph theory, since maps are graphs - the above is just a 'starter definition'.) it sounds like TARA :-) Heiner
- [rrg] Locator Toni Stoev
- Re: [rrg] Locator Fred Baker
- Re: [rrg] Locator Noel Chiappa
- Re: [rrg] Locator HeinerHummel
- [rrg] Locator: routing scalability Toni Stoev
- Re: [rrg] Locator: routing scalability Paul Jakma
- Re: [rrg] Locator: routing scalability Toni Stoev