Deploy360 16 April 2012

Comcast Rolling Out Home Gateway Support for IPv6 – And Nothing's Controversial About a /64…

By Dan YorkDirector, Internet Technology

Outstanding news for Comcast subscribers last week at the North American IPv6 Summit! Comcast’s John Brzozowski, chief architect for IPv6 and distinguished engineer, indicated that Comcast was now moving its IPv6 support from just supporting single computers to supporting entire home networks. In a Network World article titled “Comcast is first U.S. ISP to offer IPv6 to home gateway users“, Carolyn Duffy Marson reports on Brzozowski’s comments, including the fact that the service is already available in two cities.

This step is critical for adoption of IPv6 by home users as most home users do typically have some type of home gateway providing Internet access to the many devices within their home.  Prior to this step, you could only connect a single computer for IPv6 access.  While this certainly made sense for Comcast as they started testing out their production IPv6 support, it is great to see them moving on to support the home gateway use case that the majority of Comcast customers will have.

Comcast also very helpfully is providing a website showing which home gateway devices will work with IPv6 (look for checkmarks in the IPv6 column):

My only real issue with the article is this sentence:

In a somewhat controversial move, Comcast is giving each of its home networking users what’s called a /64 block of IPv6 addresses, which represents more than 18 quintillion IPv6 addresses…

There’s actually nothing “controversial” about providing a /64 block as that’s the standard allocation of IPv6 addresses to a router.  This enables all devices within the router’s network to use “Stateless Address Autoconfiguration (SLAAC)” to automatically create their IPv6 addresses by combining the “router advertisement” with the devices own MAC address.   It’s what makes IPv6 “just work” for devices.

However, I completely understand why the author would write that.  When I first started digging into the details of IPv6 several years back I had the same reaction – aren’t we setting ourselves up for failure by starting out already giving up half our address space to the host portion?

Coming from the address-constrained IPv4 space – and just with an engineer’s view of efficiency, it seemed insanely wasteful!  And in some cases where there are always going to be a limited number of devices on a network, it certainly may be wasteful… but for the majority of networks using a /64 enables SLAAC and also makes room for innovation.  As we look at the sensor-based “Internet of Things”, we may find use for that very large address space.  Time will tell, but in the meantime the /64 allocation is just how things are done in IPv6 – welcome to the world of IP address abundance!

Aside from that minor note, it was great to see this article and congrats to Comcast for rolling out this support for IPv6 home gateways!  As World IPv6 Launch nears, this will definitely enable more people to get connected!

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

Related articles

Improving Technical Security 15 March 2019

DNS Privacy Frequently Asked Questions (FAQ)

We previously posted about how the DNS does not inherently employ any mechanisms to provide confidentiality for DNS transactions,...

Improving Technical Security 14 March 2019

Introduction to DNS Privacy

Almost every time we use an Internet application, it starts with a DNS (Domain Name System) transaction to map...

Improving Technical Security 13 March 2019

IPv6 Security for IPv4 Engineers

It is often argued that IPv4 practices should be forgotten when deploying IPv6, as after all IPv6 is a...