Failure (and Greatness)
This is part of a series of posts – The Lisp Papers.
So, we’ve pretty much run out of IPv4 addressing, right? And we’re anticipating a new release of the (Capital I) Internet – which will definitely be the greatest upheaval in the networking world. Why is this going to happen? A very simple and flippant answer is that we don’t have enough addresses. This has created all sorts of problems and will continue to have significant impact for between 10 and 20 years. And why don’t we have enough addresses?
The question is answered by Vint Cerf, arguably the most important man in the history and development of the Internet. It’s all his fault. As he explains, a temporary fix becomes long-term infrastructure. I will definitely be using this example the next time a “tactical” fix is proposed.
Of course, this doesn’t stop him being a legend. As I like to point out, importance is directly related to how many people your mistakes affect. Any time you affect 1.6 Billion people (and counting), you are important
Greatness (and Failure?)
This week I’m going to continue on my theme of the expanding Internet Routing Table that I delved into last week (the good, bad and ugly), particularly looking at some suggested solutions and cool technologies. Wednesday’s post is going to be around the concept of Location and Identification semantic overloading (what?) and the impact that has on the routing table. I really like this, as it’s a subtle concept with a large impact. Then, Friday and next week, I’ll be diving into the terribly named Location Identification Separation Protocol. LISP is already an acronym in widespread usage – as someone put it, we have a namespace conflict.
When I first learnt about MPLS Layer 3 VPNs, I remember thinking, “Wow, this is incredible.” It’s still early days but LISP might just be in that category. Of course, it might not, but Cisco has already released working code and I’m going to attempt to configure a number of network topologies with it.