Re: [rrg] Constraints due to the need for widespread voluntary adoption

Florin Coras <fcoras@ac.upc.edu> Fri, 04 December 2009 01:14 UTC

Return-Path: <fcoras@ac.upc.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 83C533A68E7 for <rrg@core3.amsl.com>; Thu, 3 Dec 2009 17:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.764
X-Spam-Level:
X-Spam-Status: No, score=-1.764 tagged_above=-999 required=5 tests=[AWL=-0.835, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, SARE_SXLIFE=1.07]
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 3EiMaWOX7KpW for <rrg@core3.amsl.com>; Thu, 3 Dec 2009 17:14:06 -0800 (PST)
Received: from gw.ac.upc.edu (gw.ac.upc.edu [147.83.30.3]) by core3.amsl.com (Postfix) with ESMTP id 52E9C3A6403 for <rrg@irtf.org>; Thu, 3 Dec 2009 17:14:06 -0800 (PST)
Received: from [192.168.0.14] (81.184.58.60.dyn.user.ono.com [81.184.58.60]) by gw.ac.upc.edu (Postfix) with ESMTP id 9B7386B02E8; Fri, 4 Dec 2009 02:13:55 +0100 (CET)
Message-ID: <4B18624F.9050906@ac.upc.edu>
Date: Fri, 04 Dec 2009 02:13:51 +0100
From: Florin Coras <fcoras@ac.upc.edu>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Dae Young KIM <dykim@cnu.kr>
References: <20091203232331.AD34D6BE56E@mercury.lcs.mit.edu> <3938a04d0912031620x36ba313je041f35d097833d0@mail.gmail.com> <3938a04d0912031633u74a9b8e5lfbb54425a969648d@mail.gmail.com>
In-Reply-To: <3938a04d0912031633u74a9b8e5lfbb54425a969648d@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: rrg@irtf.org, Noel Chiappa <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:14:07 -0000

Hello,

Dae Young KIM wrote:
> Put it in another way using the terms in this community:
>
>     - Do routing with ID.
>     - Do away with Locator. It's redundant. It should belong to the layer
> below. And locator's change in every segment of networks.
>
> On Fri, Dec 4, 2009 at 9:20 AM, Dae Young KIM <dykim@cnu.kr> wrote:
>
>   
Well, then, speaking in IEN-19 terminology your doing name/address
separation through DNS, no? Or, considering the previous example you are
using DNS for mapping between the name (Noel) and what you call ID (the
mentioned address). I now suppose that in order to provide mobility the
name (Noel) will be used in sockets instead of what you call ID. If this
is the case the first foreseeable problem is that you break all the
current applications.

Also I think that "locator" would better describe what you call an "ID"
for the simple reason that it indicates a fixed destination in the
network ( in your example was the address of a house).
>> On Fri, Dec 4, 2009 at 8:23 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:
>>
>>     
>>> Since "address" to most people does mean a 'name' (in the generic sense of
>>> "name") with some location information in it, I am going to assume that
>>> your
>>> "ID" means a name which is location dependent.
>>>
>>>       
>> No, my 'ID' means a name which is location 'independent'.
>>
>>     
Correct me if I'm wrong but your example with the mail considered the
address of the house as the ID so how can it be location independent?
>>
>>>    > To me, they're one and the same thing. There's no routing without
>>>    > identifying your partner. There's no identifying your partner without
>>>    > routing to, i.e., without locating it. The two are one and the same.
>>>
>>> Ah, no. 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?). Noel is the 'DNS' name which,
>> of course, is unique independently of whatsovever.
>>
>> Then, we said DNS name should be mapped to ID. (Noel to 234 Madison Ave.).
>> There's no routing (or better said locating?) without identifying your
>> house. There's no identifying your house without successfully locating it.
>>
>>     
I'm inclined to believing that your statement here agrees with my
assertion from above

Regards,
Florin
>>
>> --
>> Regards,
>>
>> DY
>> http://cnu.kr/~dykim <http://cnu.kr/%7Edykim>
>>
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>