T-Mobile's journey to IPv6

Channel:NANOG · Length:28:21 · Published:2018-06-27 · Views:1499

Watch on YouTube

Summary

Stephan Lagerholm of T-Mobile explains at NANOG how T-Mobile turned off IPv4 for over 10 million handsets using DNS64 and related technologies. He shares advice on finding and handling broken applications.

Why HN recommends it

Cited as the primary source for T-Mobile US running IPv6-only mobile clients in IPv6 adoption debates.

2018 NANOG presentation "T-Mobile's journey to IPv6" — HN, 2025

Networking & internet infrastructure

Subtitles (excerpt)

Thanks everybody. Can you have everybody hear me okay? Yeah, it sounds good. Well, it's great to be here in Denver, sunny day and we're going to talk about IPv6 here indoors, so that feels great. Some background on me, I'm going to talk about how our path to going IPv6 only at T-Mobile. Uh I was born and raised in Sweden. I moved to the US in 2007. In 2009, I I remember attending an ARIN conference in San Antonio. Uh I lived in Dallas at that time and and I met with Stan Barber, who some of you guys might be familiar with and we were talking about the deployment of IPv4 versus IPv6 in the Europe and versus US and kind of came to the conclusion that, you know, it's it's we're we're a little behind here in the US and maybe we should do something. So, we founded the Texas IPv6 Task Force uh back in 2009. We were inspired by the Rocky Mountain Task Force here in Denver, who by the way, they're a sponsor and there's some events going on tonight if anybody's up for a free beer. Uh anybody who's doing IPv6. Uh nevertheless, uh I started work for a company called Secure64, also based here in Denver, a DNS company and one day this sales guy comes, you know, comes into my office and says, "Hey, you got to talk to this guy Cameron at T-Mobile.

On Hacker News

> Meanwhile T-Mobile/Odido in the Netherlands is still not supporting IPv6 despite promising to have been working on it for years. While T-Mobile US has been IPv6-only since ~2018: * [VIDEO] — throw0101a, 2026-06
> NAT / CGNAT has been doing the heavy lifting extending the life of the Internet; ipv6 has done jack shit. Given they made the transition to IPv6 on handsets, T-Mobile US, which has 140 million subscribers, would disagree: * [VIDEO] > As for telco addressing handsets, they could use any addressing scheme to be honest. When people talk about averting address exhaustion, they're not talking about … — throw0101a, 2026-06
> IPv6 feels like we just can't admit to ourselves that it has been a failed transition. What would it take to come up with IPv7 which takes in the lessons of IPv6 and produces something better that we can all agree is worth transitioning to over IPv4. Per Google, quite a few countries (including the US) are at >50%: * [LINK] Every handset on T-Mobile US's network gets IPv6 (and they're not the o… — throw0101c, 2026-04
> Outdated beliefs probably. When I talk about v6 support in our b2b saas, PM laughs and says nobody uses that shit. Nobody except the 140M subscribers on T-Mobile US's network: * [VIDEO] But sure, be IPv4-only and add latency by forcing traffic through an extra translation box. — throw0101d, 2026-04
> They've been requiring that iOS apps work on IPv6-only networks for close to 10 years now This was at the behest of mobile network. E.g., T-Mobile US has 140M subscribers, and moved to IPv6-only many years ago: * [VIDEO] — throw0101d, 2026-04

Related videos