Thanks for confirming my point:
LISP-DDT relies on globally unique Pv4 addresses and does not multiply the
IPv4's unicast address space by the number of LISP-Locators.
That would only be possible if a FQDN were mapped (of course by DNS) into a
unique pair {EID IPv4 unicast address; LISP Locator} which in return requires
the user side to be involved.
..."EIDs can be allocated more densely"... Well that is nothing compared with
64800 times 2^30 additional unicast addresses.Isn't it ?
..."Done: Proved that the solution can be purely network based".... If you
carry a letter to your post office, which is destined for Mr. Smith being the
receiver, you wouldn't ask the service man to add Mr. Smith'address all by
himself, right ?
But my email was questioning IPv6 in the first place. 16 Bytes address space
that do NOTHING for routing !!! Which would rather rely on LISP-in-LISP
locators (eventually)!
Having another huge multicast address space and yet relies on source unicast
address (according to PIM) in addition to the multicast address! Plus
LISP-Locator ???: (BTW: How is the LISP-multicast-locator designed (= info
question)? Is there some LISP-Multicast-Locator FIB ? certainly not) .
Furthermore: IPv6 defines anycast addresses without scopes !!! Why is LISP so
sensitive to IPv6 and doesn't try to abolish/replace it?
Heiner
-----Ursprüngliche Mitteilung-----
Von: Noel Chiappa <[email protected]>
An: lisp <[email protected]>
Cc: jnc <[email protected]>
Verschickt: Mo, 5 Aug 2013 5:00 pm
Betreff: Re: [lisp] All Things LISP materials
> From: [email protected]
> LISP ... does not buy us a single spare IPv4 address!
It does not expand the namespace, no. But it could allow more efficient and
complete use of it (which is almost as good as an expansion). EIDs can be
allocated more densely from a fixed-size namespace than addresses (which
necessarily cannot be tightly packed) can.
Noel
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp