Re: [rrg] Constraints due to the need for widespread voluntary adoption
jnc@mercury.lcs.mit.edu (Noel Chiappa) Fri, 04 December 2009 01:42 UTC
Return-Path: <jnc@mercury.lcs.mit.edu>
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 130EF3A683B for <rrg@core3.amsl.com>; Thu, 3 Dec 2009 17:42:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level:
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_MED=-4]
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 grc72jPHrAVg for <rrg@core3.amsl.com>; Thu, 3 Dec 2009 17:42:30 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 3256D3A6403 for <rrg@irtf.org>; Thu, 3 Dec 2009 17:42:30 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A7D1F6BE56E; Thu, 3 Dec 2009 20:42:20 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20091204014220.A7D1F6BE56E@mercury.lcs.mit.edu>
Date: Thu, 03 Dec 2009 20:42:20 -0500
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] Constraints due to the need for widespread voluntary adoption
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: Fri, 04 Dec 2009 01:42:31 -0000
> From: Dae Young KIM <dykim@cnu.kr> > No, my 'ID' means a name which is location 'independent'. OK, so apparently you have two kinds of names: "IDs", which are location independent; and "locators", which are location dependent, but have local scope only. In other words, you have no names which are i) location dependent, and ii) have global scope. So here is the problem: how do you compute paths across the entire internetwork when you do not have any location-dependent names with global scope for places in the network? The path-selection algorithm _has_ to have such names to be able to compute paths across the internetwork. >> I am "J. Noel Chiappa" no matter where I am, and you can identify me >> without knowing either i) where I am, or ii) how to get there. > OK, you're talking about DNS name(or URI?). No, you need to think separately about i) the characteristics of the name, and ii) what it being named. "J. Noel Chiappa" is the name of a person, me. I do not have a permanent location, and my name has no location information in it. "jnc@lcs.mit.edu" is a name - but the _kind of thing_ it is the name of, is an email-box. "123 Main Street" is the name of a place - and maybe sometimes the person named "J. Noel Chiappa" is at the place named "123 Main Street". But that does not make the name of that person "123 Main Street". > Then, we said DNS name should be mapped to ID. (Noel to 234 Madison > Ave.) ?? You just said (above) that the "ID ... is location 'independent'". > There's no routing (or better said locating?) without identifying your > house. My current house does not have a location-independent name. The only name it has it a name that is location dependent (i.e. something like "123 Main Street"). > There's no identifying your house without successfully locating it. I am from Bermuda. When I was young, houses in Bermuda had names - but the names were not location dependent. Our house was named "Parquito". Even though the house had a name which uniquely identified it (it was the only house in Bermuda with that name), I guarantee you that that name would not really help you locate it. > Put it in another way using the terms in this community: > - Do routing with ID. We call that 'flat' routing (i.e. the names used for path selection are not aggregatable, since they contain no location information - like Ethernet MACs in a large, bridged Ethernet network). That does not scale to very large (Internet-sized) networks. Noel
- [rrg] TARA and voluntary adoption Robin Whittle
- [rrg] Constraints due to the need for widespread … Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… HeinerHummel
- Re: [rrg] Constraints due to the need for widespr… Patrick Frejborg
- Re: [rrg] Constraints due to the need for widespr… HeinerHummel
- Re: [rrg] Constraints due to the need for widespr… Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… Noel Chiappa
- Re: [rrg] Constraints due to the need for widespr… Patrick Frejborg
- Re: [rrg] Constraints due to the need for widespr… Tom Vest
- Re: [rrg] Constraints due to the need for widespr… Noel Chiappa
- Re: [rrg] Constraints due to the need for widespr… HeinerHummel
- Re: [rrg] Constraints due to the need for widespr… Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… Patrick Frejborg
- Re: [rrg] Constraints due to the need for widespr… Noel Chiappa
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Noel Chiappa
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Florin Coras
- Re: [rrg] Constraints due to the need for widespr… Noel Chiappa
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Patrick Frejborg
- Re: [rrg] Constraints due to the need for widespr… Noel Chiappa
- Re: [rrg] Constraints due to the need for widespr… HeinerHummel
- Re: [rrg] Constraints due to the need for widespr… Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Robin Whittle
- Re: [rrg] Constraints due to the need for widespr… Dae Young KIM
- Re: [rrg] Constraints due to the need for widespr… Patrick Frejborg
- Re: [rrg] Constraints due to the need for widespr… sunletong