[152877] in North American Network Operators' Group
Re: Current IPv6 state of US Mobile Phone Carriers
daemon@ATHENA.MIT.EDU (Paul Graydon)
Tue May 22 20:37:02 2012
Date: Tue, 22 May 2012 14:36:13 -1000
From: Paul Graydon <paul@paulgraydon.co.uk>
To: nanog@nanog.org
In-Reply-To: <4FBC23D8.5040109@paulgraydon.co.uk>
X-SA-Exim-Mail-From: paul@paulgraydon.co.uk
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 05/22/2012 01:40 PM, Paul Graydon wrote:
> On 05/22/2012 01:21 PM, Cameron Byrne wrote:
>> On May 22, 2012 4:00 PM, "Paul Porter"<paul.porter@gree.co.jp> wrote:
>>> Hi NANOG,
>>>
>>> I'm looking for some information on the four largest US mobile phone
>>> carriers and the current state of their IPv6 infrastructure.
>>> Specifically,
>>> we are trying to figure out:
>>>
>>> 1. How much of the carrier core and edge for AT&T, Verizon.
>>> T-Mobile, and
>>> Sprint are on IPv6 now?
>> Hi,
>>
>> T-Mobile USA has native ipv6 to all subscribers in all of it's coverage
>> area. But, less than 1% of subscribers use IPv6 because they do not
>> have an
>> IPv6 capable phone. The Nexus S and Galaxy Nexus work well.
>>
>> This device challenge will improve in time. Samsung is doing a good
>> job of
>> bringing IPv6 to Android devices. More info here
> That's interesting. I have a Galaxy Nexus on T-Mobile USA and it
> doesn't get an IPv6 address, only IPv4. Works fine with IPv6 over my
> wireless network at home. Doesn't seem to be anything obvious in the
> settings to enable or disable that.
>
> Paul
>
Cameron contacted me off list and pointed out the steps. Works a treat,
NAT64 is handling the IPv4 traffic without any obvious problems, along
with IPv6. Smooth and simple. Shame it has to be switched on through
some manual steps, but I guess that's understandable for now given it's
technically in Beta stage.
Paul
