Show 123 – LISP Use Cases with Dino Farinacci & Victor Moreno of Cisco – Sponsored

This week’s podcast features Cisco Fellow & Senior Software Engineer Dino Farinacci and Distinguished Engineer Victor Moreno in a discussion of LISP – Locator/ID Separation Protocol. Ethan Banks and Greg Ferro host.

The Packet Pushers talked with Victor back in show 54 about LISP. Show 123 is focused less on the mechanics of the protocol, and more on the use cases. In other words, what can we do with yet another routing protocol that hasn’t already been done with others? The answer is rather a lot. LISP isn’t simply a routing protocol; it’s a way of decoupling an endpoint (something you’re trying to communicate with) from a physical location. Therefore, an endpoint can be stationary or mobile, and LISP will sort that out in way that scales to Internet-size and beyond.

What We Discuss

  • Quick review: what is LISP?
  • How is LISP different from legacy tunneling protocols?
  • What Cisco platforms run LISP?
  • Where does a LISP mapping database run?
  • LISP Use Case: L2 DCI & vMotion.
  • LISP Use Case: Changing the Notion of Subnetting.
  • Explaining LISP RLOCs & EIDs.
  • The LISP future vs. current reality.
  • How extensible are the LISP forwarding tuples?
  • LISP Use Case: The Internet of Things.
  • LISP Use Case: Mobility Across Cloud Providers.
  • How does LISP scale?
  • Will LISP be standardized and adopted by other vendors?
  • Other LISP use cases (including IPv6 transition).
  • LISP as a programmable API.

 

Ethan Banks
Ethan Banks, CCIE #20655, has been managing networks for higher ed, government, financials and high tech since 1995. Ethan co-hosts the Packet Pushers Podcast, which has seen over 2M downloads and reaches over 10K listeners. With whatever time is left, Ethan writes for fun & profit, studies for certifications, and enjoys science fiction. @ecbanks
Ethan Banks
Ethan Banks
  • http://twitter.com/nkrypted Brandon Mangold

    Thanks for yet another great podcast. LISP definitely has mind melting potential, let’s see if it garners enough support to realize at least a portion of that potential. Definitely exciting stuff!

  • Fred

    great show – horrible audio quality

    • http://packetpushers.net/author/ecbanks Ethan Banks

      Fred, we record using Skype and recommend a USB headset to all of our guests in pre-show planning. Unfortunately, top-notch guys like Dino and Victor whose time is very hard to schedule (because they are in constant demand) just aren’t able to go that extra mile. In those cases, we make do with whatever microphone they have available because what they have to say makes for valuable content.

  • Cristian

    Hello. Great show, thank you.
    I have a question regarding the immediate usability of LISP. During the show the example given was a smart phone running a special client designed to register the user with the mapping database.
    All networks these days contain machines running Windows/Unix/Mac Os/mainframes. Lisp clients to not exist, and will not be supported natively in OS for a long time. How can Lisp be used with the existing end points?
    I would love to have the ability to move servers between datacenters (across different layer 3 networks), and hide the move of address from the end users. What protocol/mechanism does the conversion from the “old” ip addresses and dns resolution world to the new Lisp enabled networks?
    Many thanks, Cristian

  • http://twitter.com/networkstatic Brent Salisbury

    The concepts of abstraction using names like this is pretty powerful as related to IP mobility. Brilliant show guys.

  • Matt Nabors

    The LISP use cases are indeed compelling. However, I do wonder how the mobility aspect of the protocol will affect the ability to prevent DDoS attacks, from both the providers of the service and the enterprise itself. As I understand it, the providers of DDoS service essentially watch their version of the Internet BGP table. When they see an address originating from an AS to which it does not belong, they back it up to the source and shut it down. With the mobility of LISP, would that not trigger this mechanism to prevent spoofing? On a similar note, if LISP provides the ability to move around, would the black hat hackers be able to leverage that function to more effectively hide themselves by constantly moving around? Or would you just be able to block the locator?

    Excellent podcast. I appreciate the time and geek capital you had to spend to get those guys.