IPv6 Deployments Need To Be Planned, But It ‘Just Works’ – Lessons from Broadband World Forum Thumbnail
Internet of Things (IoT) 29 October 2014

IPv6 Deployments Need To Be Planned, But It ‘Just Works’ – Lessons from Broadband World Forum

By Olaf KolkmanPrincipal - Internet Technology, Policy, and Advocacy
P. Guedes
P. GuedesGuest Author

Last week I had the pleasure to visit the Broadband World Forum in Amsterdam. It gathers fixed and mobile access providers and vendors that sell the equipment that these providers use to bring us the Internet. Walking around the exhibition floor I got the impression that the hottest areas are home automation, as the consumer-facing pieces of the Internet of Things, and virtualization that seems to sneak closer and closer to the edge.

While home networking and the Internet of Things were being marketed everywhere, in only two or three hard-to-find places did I see any mention of IPv6. If the Internet is supposed to connect a significant fraction of the predicted 20 billion Things by 2020, it is somewhat amazing that the addressing scheme that allows for end-to-end connectivity is not prominently mentioned. We had to ask, and in our statistically insignificant sample we did assess that IPv6 is part of many product offerings.

Still, while IPv6 may be in the products, most of us are not being offered IPv6 when we connect to the Internet. Hoping to inspire other access providers to deploy IPv6, we organized an IPv6-dedicated session with participation from Hans Thienpondt from Telenet Belgium, Bjørn Netland from Telenor, Nick Heatley from EE UK, and Timo Hilbrink from XS4ALL.

Hans gave an introductory presentation describing the experience of deploying IPv6 in Telenet. Telenet has a huge deployment. In our measurements at World IPv6 Launch we show that 40% of the traffic coming from their network uses IPv6. Hans explained that the choice for IPv6 was a strategic one: with the IPv4 address shortage there will be a point that while continuing to use carrier grade NATS (CGNs) the complexity and brittleness, and hence the cost, will continue to grow, and additionally, the risk of bad user experience will continue to grow. By introducing IPv6, one allows for a growth path whereby the CGNs keep having reasonable headroom and the user experience remains acceptable. Hans told us that their experience with using IPv6 so far is entirely positive.

During the panel discussion with all the network operators, we realized that the deployment experience for these service providers was similar: The strategic vision was developed by the engineers and sold to upper management about five years ago and the deployment followed a relatively careful and slow path, in bottom-up fashion, so to speak. One of the audience members made clear that bottom-up is not the only way: he had been told by upper management to deploy about three years ago.

Another similarity is that when users are offered IPv6, the traffic patterns demonstrate a significant fraction of their traffic being over IPv6: 20-30% being somewhat typical for an IPv6-enabled user, and all that without increased helpdesk pressure.

The holy grail of IPv6 transition techniques is to be able to run a single stack IPv6 network, but still allow a state-of-the-art user experience for applications and services that have not transitioned to IPv6 and only run over IPv4. We talked about two hurdles getting to IPv6 only networks.

While IPv6 deployment is ramping up in the mobile environment there are still hurdles to overcome for mobile operators to run IPv6 exclusively: during inter-provider roaming one cannot rely on ubiquitous availability of IPv6 on each network and there remains a need to configure two profiles: an IPv6 profile for home and an IPv4-only profile for the roaming user. That seems to be a complexity that is not going to go away soon.

Another challenge for IPv6-only deployments in the mobile space is the availability of the client component of 464XLAT (RFC6887) in terminal equipment. Support for that technology is not yet ubiquitous and not yet on the roadmap of all mobile device producers. In spite of this we see significant deployments of IPv6 in at least two large mobile networks in North America – Verizon Wireless and T-mobile USA. So it is quite possible and we look forward to seeing more deployment in this space.

When the Internet Society first began discussing IPv6 deployments with operators at the Broadband World Forum, there was very little experience to share. Now, just four years after our first participation in a similar panel at BBWF in Paris, we can point to massive deployments of IPv6 in networks such as Comcast, Deutsche Telekom, and KDDI. And now IPv6 is used by the most-visited websites in the world: Google, Facebook, YouTube, Yahoo!, and Wikipedia. It’s great to see this kind of progress towards a better and more robust Internet.

Disclaimer: Viewpoints expressed in this post are those of the author and may or may not reflect official Internet Society positions.

Related articles

Building Trust 5 December 2019

Rural Development Special Interest Group Organizes Internet Connectivity Tag 2019

In November, the Internet Society Rural Development Special Interest Group (RD SIG) organized an event called the Internet Connectivity Tag 2019 in Bangalore,...

Building Trust 14 November 2019

IoT Security Policy Platform Wants to Raise the Bar On Global IoT Security

By next year, five Internet of Things (IoT) devices are projected to be in use for every person on...

Building Trust 2 October 2019

Celebrating National Cybersecurity Awareness Month

Every October, we mark National Cybersecurity Awareness Month. From the U.S. Department of Homeland Security website, “Held every October,...