My last post reviewed some of the building blocks of SDN (Software Defined Networking) and positioned the protocols and APIs (Application Programming Interface) into categories so that the multitude of technologies associated with SDN can be positioned in a coherent framework. This month I’d like to start looking at some use cases where some of these things are used to deliver benefit in a service provider network.
I will review a consumer oriented offering and next month, one targeted at enterprise services.
As always, it is important to define the business outcome we are trying to affect when making a change to the network infrastructure. This case will consider an operator Read More »
For those that are not closely involved with IPv6, it may seem like the emphasis on migration to the new addressing scheme is waning. But while the hue and cry over IPv6 may appear to have quieted down to a background noise since 2010-2011; a closer inspection would prove that perception to be quite false.
What is IPv6 and why does it even matter? Simply put, when a device is on the Internet, it has its own specific address that it uses to communicate with other devices and the Internet and to define its location. With the non-stop growth of devices connecting to the Internet and the “Internet of Everything” (IoE) becoming a reality, the need for unique addresses for each personal device and machine-to-machine (M2M) connections has increased exponentially. To put this in perspective, the Cisco Visual Networking Index (VNI) 2013-2018 forecast estimates that there will be about 4 billion Internet users by 2018, which is 52% of the world’s projected population (7.6 billion people). And for every person on the Earth in 2018, there will be about 3 global Internet connections — that’s more than 21 billion devices/connections by 2018.The current communication and address format IPv4 was just not equipped for this explosive growth of devices and connections and the need to define addresses for each device. Hence the need for a new communication protocol, IPv6.
It’s that time of the year again -- time for some computer and human networking at Cisco Live Milan! This year I’m taking the unusual and somewhat risky step of blogging about the network infrastructure before the event. This is because we’re going to try something interesting for the networking folks. We are going to try and get rid of the Legacy IP, otherwise known as IPv4.
Before you get too worried -- no, the dual stack network setup does not disappear. Lots of critical parts of our everyday lives still need the old and proven protocol to successfully operate, so removing it would be irresponsible to say the least. But some of you may be interested to try (in a controlled fashion) exactly how strong the ties to the old good legacy. If you are one of these people, this post is for you -- because this blog entry is one of the few places, if not the only one, to find the IPv6-only SSID name and access credentials.
First of all, what’s the big deal with IPv6-only access network, wasn’t this tried before?
Sure, it is not all new. The first time we tried an IPv6-only network was at IPv6 World Congress conference in Paris, early spring 2012. We also had an IPv6-only SSID in one of the Cisco Live US conferences. We discovered that the subset of the operating systems that could successfully operate in this kind of environment was pretty small. But as time passed, evidence suggests the situation was slowly improving. Read More »
Within the coming decade, Internet Protocol version 6 (IPv6) will be key to enabling 50 billion connections among people, processes, data, and things in the Internet of Everything (IoE). But how we get there from here is not a simple matter.
I’m very pleased to invite Mark Townsley, Cisco Fellow and recognized industry expert on IP, to discuss this important transition in the second of our three-part blog series on IPv6. The first blog in Mark’s series was “Demystifying IPv6”.
Three years ago, I organized a conference in Paris where I thought it would be fascinating to bring together the original designers of IPv6 alongside the engineers who were finally deploying it at scale more than a decade later. During this discussion, Steve Deering, one of the “fathers” of IPv6 in the 1990s, was asked one of the most common questions about IPv6: Why wasn’t it designed for backward compatibility with IPv4? After all, wouldn’t it be easier to make the transition if the two versions could transparently coexist? Steve answered that the problem is not that IPv6 wasn’t designed to be backward-compatible—the real problem is that IPv4 wasn’t designed to be forward-compatible.
Steve was making the point that IPv4 was designed with a fixed address space. Given the number of computers connected to the Arpanet throughout the 1970s, this fixed-length address field seemed to be sufficient—at least for that version of IP. IP had been replaced before, and it seemed perfectly reasonable at the time that it might be replaced again. Read More »
Version 6 of the Internet protocol (IPv6) is a key enabler of the Internet of Everything (IoE). People, data, and things all need IP addresses to connect to the Internet. But we’ve already run out of IP addresses under IPv4, which dictates almost all (98.5 percent) of Internet traffic today. Even with all of the attention IPv6 has received, confusion and misinformation abound.
I’m extremely pleased to have Mark Townsley, Cisco Fellow and recognized industry expert on IP, explore IPv6 over a series of three blogs.
In these posts, Mark will demystify IPv6, discuss how to best make the transition from IPv4 to IPv6, and take a look “under the hood” of IP so that companies and industries can get the most value from IoE. Read More »