In einer eMail vom 09.12.2008 21:41:59 Westeuropäische Normalzeit schreibt
[EMAIL PROTECTED]:
I've said this from the beginning but I'll try once more: I get much
less confused about LISP if I use different terminology, because the
LISP "EID" is not an EID. Think of it as a local locator (which also
happens to be globally unique) and call it LOC0 for example. Then the
LISP "RLOC" is a less local locator that just happens to be globally
routable as well as globally unique; call it LOC1 for example. As HAIR
points out (and I pointed out last year) the obvious conclusion is a
recursive model with any number of layers of locator scope.
GSE/ILNP and HIP are deeply different in that they genuinely separate
a unique *non-locator* ID from one or more locators. Trying to use the
phrase "loc/id split" to cover both of these models is certain to
lead to confusion.
Brian
Brian,
It is a general problem that problems are being delt with by using not
adequate language.
I guess I am the only one who pursues location based routing rather than LOC
based routing.
Or: Topology aggregating addressing. This term is - according to my
impression - used for PA addresses !!:-(
Or look at the root cause in the strategy overview list:
The root cause of the routing table growth problem is that we're using the
same element (IP address) to express three distinct concepts:
1. the globally unique identity (GUID) needed by the originating client
system to find the destination server,
2. a component of the session identity (SID) used by the layer 4 and
higher protocols to keep track of communications with other hosts, and
3. the node's present location or locations (LOC) within the network
topography.
Show just these 3 points to the smartest but non-IETF human being on earth:
If he/she concluded: "ooops, you must have a severe scalability problem" then
I will humble withdraw my critic that this 3-folded-ness is
rather defusing than clarifying the root cause.
Heiner
Heiner
_______________________________________________
rrg mailing list
[email protected]
https://www.irtf.org/mailman/listinfo/rrg
