LISP Works - Re: Facebook Issues/Outage in Southeast?
Job W. J. Snijders
job at instituut.net
Tue Sep 28 22:13:35 UTC 2010
On 24 sep 2010, at 02:56, Cameron Byrne wrote:
> On Thu, Sep 23, 2010 at 5:33 PM, Scott Weeks <surfer at mauigateway.com> wrote:
>> On Sep 23, 2010, at 5:50 PM, "Scott Weeks" <surfer at mauigateway.com> wrote:
>>> --- jared at puck.nether.net wrote:
>>> It's working over LISP:
>> Wow, that's cool. I didn't know LISP had progressed that far...
Yes, LISP is good for you! :-)
> I would have to agree, i am surprised that there is a single Cisco
> 3800 series router running test code of LISP at any content
> provider.... which is all this is. Facebook made it clear that LISP
> was an experiment, not a technology direction. I don't think this
> example represents anything in particular. As a network operator, i
> am afraid LISP is going to turn into the next 6to4 .. an interesting
> idea that causes more harm than good. Sorry to the fans of 6to4 and
> LISP, i just long for the day when real IPv6 restores the real e2e
> internet without strange trickery along the way.
There is a huge difference between using LISP and 6to4 that you're not considering here.
6to4 was specifically invented to solve the particular problem of IPv6/IPv4 transition. That is its sole purpose for existence.
LISP was not invented to solve this problem - it was invented to address a much broader set of problems that neither IPv4 or IPv6 address (e.g. overloaded address semantics, multi-homing simplicity, IP mobility, and address portability).
The fact that LISP does help in IPv6 Transition solutions (due to its inherent AF agnostic design), is compelling. As you say, real edge 2 edge is the goal - and LISP helps here, regardless of the AF. (you'll will still want to do multi-homing in IPv6, and ingress TE, and mobility, etc.).
So it won't have the the same fate as 6to4.
More information about the NANOG