10 Comments

Summary:

AWS, Google, Microsoft et al. have a huge appetite for unique IP addresses, but except for Amazon’s ELB, they don’t support IPv6. Expect that to change in the near future.

As we enter the internet of things era, with millions; check that, billions of devices coming online, we’re going to need a lot more unique IP addresses. That means the big cloud providers need to get on the stick to support IPv6, the internet protocol that opens up billions of new addresses for just that purpose.

Thus far (and sort of surprising to me) MicrosoftAzure does not support IPv6 yet. Nor does Google Compute Engine although the company “is a major advocate of IPv6 and it is an important future direction.” (Maybe some news to come in the weeks running up to Google I/O?)

Public cloud leader Amazon Web Services is still on IPv4 except for its Elastic Load Balance (ELB)  service. IBM SoftLayer, on the other hand, has supported IPv6 for a few years and the upcoming Verizon Cloud, due the second half of this year, will as well.

The need is clear — Gartner estimates that 26 billion devices will be online by 2020 , a 30 times increase from the 900 million connected devices in 2009. The address registries, including the American Registry for Internet Numbers (ARIN), and its analogues in Asia, Europe and Latin America, have warned about impending “IPv4 address exhaustion.”

The challenges that the device population explosion pose to cloud providers and the very architecture of data centers will be a hot topic next week at Structure.

ipv6So how hard is it to move from IPv4 to IPv6? It doesn’t necessarily require a wholesale upgrade of networking hardware and software, but it’s still a bear.

“The challenge is that systems are complex and architectures and applications are often broadly interconnected. You have to turn over a lot of rocks in your own systems to see what is underneath – what equipment and software do you have, and what does/does not support IPv6?,” said David Belson, senior director of industry data and intelligence for Akamai. “You also need to consider all of the organizations, applications, and infrastructures that you connect to – where are your partners at with respect to IPv6 readiness and support in the hardware and software that they use within their business?”

As if that’s not enough, organizations also have to figure out which of their system components deal with IP addresses and “anything that does validation, geolocation, or handles log files may expect to get no more than 15 characters (the length of an IPv4 ‘dotted quad’ address), and now with IPv6 addresses, may get a string that can be much longer, or may vary in length depending on how it is written,” he added.

That affects now much storage space is needed for log files or database field definitions. The bottom line is companies need to plan this out in advance, but then again this is not an unforeseen event. My bet is in coming months we’ll see a spate of news from cloud providers.

This story was updated at 12:33 p.m. PDT with comment from Akamai’s David Belson for additional context.

 

  1. no more quickly rattling off the IPV4 addresses, 10.x.x.x , that was very human friendly. IPV6 is less so. Still it has to be done. Probably money to be made in an IPv4 – 6 natting device/service.

    Reply Share
  2. Wesley George Thursday, June 12, 2014

    While absolutely correct, GigaOM should take their own advice:

    HDCMAC:$ dig aaaa gigaom.com +short
    HDCMAC:$
    And yes, I know you’re hosted on WordPress. Doesn’t mean you shouldn’t be asking them, or trying to find an alternate hosting provider that does support IPv6.

    Reply Share
  3. It’s obvious you didn’t do your research on Google. Compute engine is the only main service at Google that doesn’t support IPv6. Google’s much older cloud service, app engine, has supported IPv6 for several years. Their cloud storage has had IPv6 since day one.

    Reply Share
    1. Per google site:

      https://developers.google.com/compute/docs/networking

      “All Google Compute Engine networks use the IPv4 protocol. Google Compute Engine currently does not support IPv6. However, Google is a major advocate of IPv6 and it is an important future direction.”

      A statement which Google PR confirmed to me yesterday. I’m still not exactly clear on how GAE fits into the broader Google Cloud platform, but there you have it.

      Reply Share
      1. Google app engine has long been Google’s main cloud product. It first became available in 2008. By contrast, compute engine only became generally available in late 2013. Google’s other cloud services, such as cloud files, cloud SQL, and cloud datastore, are also very recent additions to their platform.

        Compute engine is the *only* part of the Google cloud platform that doesn’t support IPv6. GAE, files, apps, and everything else has supported it for at least several years by default. In contrast, Amazon has almost no services that support IPv6, and those that do have only recently added it and sometimes require manual configurations (as is the case with their elastic load balancers).

        All in all, there is much more to cloud than just IaaS – Amazon and Google also have a lot of PaaS and SaaS.

        Reply Share
        1. no one is arguing otherwise. But given that all those cloud servers that spin up in IaaS need IP addresses, there is an issue in non-support by google cloud (and azure and aws) no?

          Reply Share
  4. Karen Bannan Friday, June 13, 2014

    Where are companies getting the expertise and knowledge to do this? That’s something that the article doesn’t address. Sure, you might know where you need to make a change, but do you have someone internally to help you make it happen? This is where IT-as-a-Service from a big player like EMC might make a difference.

    –KB

    Reply Share
  5. Jim C. Julson Jr. Tuesday, June 17, 2014

    Correction to the above. You state that Amazon “ELB” is “Elastic Block Service”, when in fact it is their “Elastic Load Balancer” Service. EBS is,”Elastic Block Service and only for attached storage to an EC2 instance. Please confirm which you meant.

    Reply Share
    1. thanks Jim. Oddly that correction was made earlier but copy reverted to my original mistake. Should be fixed now (again).

      Reply Share
      1. Jim C. Julson Jr. Tuesday, June 17, 2014

        You are fast! Thanks and great article. As a Network Engineer I can tell you the topic of IPv6 is a hot one!

        Reply Share