> From: Dae Young KIM <[email protected]>
> 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.
"[email protected]" 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 mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
