Lisp

i’ve stumbled upon an article of Michael Leonard from Juniper. he decided to take a stab at LISP. i usually call such articles with the title of this post, and the article mentioned is all about it. while we’re discussing in open forums with engineers and architects from Juniper, and in most of them we actually do cooperate - including in LISP, which author doesn’t seem to even know about - it’s sad to look at people who believe attacking competition is everything they should do in life. his comments are misguided, and willingness to be visible sad. it also doesn’t show juniper as a company in good light. ...

i was stubborn - and while from the very first moment we’ve had a lot of challenges with the hotel infrastructure, i was able to run xTR routers during last PLNOG for LISP. no, it’s not about programming Cisco routers with LISP, but about new concept of Location/ID Split, that is new concept enabling you to treat traffic engineering in internet differently. in short - we still serve traffic like we always did (backward compatibility), but by assigning users and companies IPv4 and IPv6 addressing from special pools, we can treat this traffic in a different manner. LISP is de facto overlay network concept. this itself is nothing revolutionary, but on the other hand - it’s first such network that got wide adoption in world-wide internet. why would you like to use LISP? apart from ability to conserve IP addresses, LISP gives you ability to do traffic engineering without use of BGP or involving third parties. and in effect, adopting it may mean less FIB space needed on core internet routers. ...