T-Mobile is pushing IPv6. Hard.

T-Mobile USA has launched an IPv6 web site — http://ipv6.t-mobile.com/. Only the front page (including images and CSS) is reachable over IPv6; most of the links are broken or redirect to the IPv4-only site. Clearly, it’s still a work-in-progress.


This appears to be a futher development in their IPv6 strategy announced at Google’s IPv6 Implementors Conference few weeks ago. (Btw, the conference was quite good; hats off to Erik, Lorenzo, and the rest of the Google team.)



T-Mobile USA makes heavy use of NAT44 and bogon addresses. Going forward, this isn’t sustainable. So they’ve decided that future cellular deployments will be IPv6-only, with NAT64 to access the “legacy” IPv4 Internet (slides | video). Yes, NAT is bad, but this approach is the least-bad of the alternatives. There’s still only one layer of NAT, it gets IPv6 on a large number of end nodes, and IPv6-enabled content (Google, Netflix, Facebook, etc) isn’t NAT’ed at all. Over time, less traffic should flow through the NAT64 boxes as more content is IPv6-enabled. T-Mobile USA suspects they can run 50% of their cellular data traffic over IPv6 by the end of 2011 (apparently they send a lot of traffic to Google and Facebook).


On a personal note, it was very entertaining to hear Cameron Byrne from T-Mobile USA repeatedly tell content providers, “Our users are going to access your content over IPv6. The only relevant question is ‘will we make the AAAA record or will you?’ Wouldn’t you rather be the one to do it so you have control?” After the fourth or fifth time it sunk in: These folks are serious.


This is an even gutsier move than Verizon. VZ is dual-stacking their LTE network and mandating IPv6 support on all devices. Let’s hope T-Mobile is really good at running large-scale NATs.


Source:  http://www.personal.psu.edu/dvm105/blogs/ipv6/2010/06/t-mobile-is-pushing-ipv6-hard.html

NTT and AT&T have Webinars on IPv6

Recently, both NTT and AT&T have had webinars on IPv6. AT&T’s webinar features Steve Stine, Vice President, IPv6 Transition, and Tom Siracusa, Executive Director, VPN Strategy, AT&T Laboratories. NTT’s webinar features Doug Junkins, CTO of NTT America.

New Poll: Would you pay extra for IPv6 support?

There is a new poll just on the right side of this post. The new Question i would like to ask you is.. Would you pay extra for IPv6 support? Be it for hardware or software. Perhaps vendor support or SLA options.


So tell me what you would do! The Other option can be used to vote blank, or you can comment here to explain.

RIPE working group chair awarded IPv6 award

Gert Döring, Co-Chair of the RIPE Address Policy Working Group, has been awarded the “IPv6 Ideenwettbewerb” from the Hasso-Plattner-Institut for his work on the OpenVPN software in Point-to-Multipoint-Mode, which facilitates the use of IPv6 addresses in dual-stack networks.

More on Heise Online… [in German]

‘Internet Crunch’ won’t impact defense networks, as department upgrades to IPv6

With reports and rumors of a big “internet crunch” circulating, the Department of Defense is looking ahead to discern how it can take advantage of more advanced web protocols to enhance its mission.

Kris Strance, the chief of internet protocol for the department, said today in a “DoDLive” Bloggers Roundtable that the crunch – the potential loss of available address space for devices to connect to internet networks – likely won’t affect the Defense Department. But upgrading from internet protocol version four (IPv4) to version six (IPv6), he said, will allow for better network mobility and allow certain groups within the Defense Department to expedite their missions.

More from Defense.gov…

I root server doing IPv6

Last week, the I root DNS server turned on IPv6. Currently, it’s only enabled at the Stockholm node.


Here’s a Google Map showing locations of IPv6-enable DNS root servers. Global nodes are in red; local nodes in blue:


View Larger Map


Almost all of the DNS roots now have at least some of their nodes IPv6-enabled. Unfortunately, they see very little traffic over IPv6. The H root, for example, sees only about 3% of their traffic over IPv6. This is an improvement over 2008, but it’s still depressing.