Nope, in fact the only phone manufacturer that supports IPv6 on the cellular interface in Nokia. Talk about making false statements.... almost nothing works with IPv6, including 99% of home router, 99% of cell phones... and nearly no DSL or cable providers support IPv6. It is only T-Mobile USA that has it for Nokia on Mobile. Maybe you are from the future where IPv6 is common, but it is not the case today.
As stated ITFA, NAT64 is the technology used to bridge IPv6 end users, like mobile phones, to long-tail content that is ipv4-only.... note, google, facebook, netflixs, yahoo, and others have all already turned on ipv6 to some extent..... that represents over 50% of the internet traffic right there.
I have been using IPv6 on the T-Mobile USA beta and it works fine, the user experience is just like ipv4. Politics and dogmas aside, it's just a number for an end node and it works. If you google around, you can find links to try it out yourself on T-Mobile USA.
I have been using IPv6 on the T-Mobile USA beta and it works fine, the user experience is just like ipv4. Politics and dogmas aside, it's just a number for an end node and it works.
Yep, that is the fundamental issue..... if there was a enough ipv4, we could dual-stack. But, dual-stack is a broken idea when there are no IPv4 address to be had and network edges like mobile and cloud are growing so fast.
The whales have already shown the time is now to move to ipv6: ipv6.google.com, ipv6.netflix.com, ipv6.weather.yahoo.com, www.v6.facebook.com, ipv6.t-mobile.com, ipv6.comcast.net, ipv6.cnn.com, www.brocade.com, www.ipv6.cisco.com, and the list goes on. These companies are not going dual stack for fun on their servers, they are doing it because ipv6-only users are on the horizon and they all know it. Without a native IPv6 setup, they will be screwed going via a proxy on NAT64, and they dont want that.
The address is not assigned to the tower, it is assigned to your phone... so that how it scales and why you need 10net space on the handsets... yes, there really is not enough ipv4
T-Mobile is doing IPv6-only, and the Ipv4 applications are SOL. The good news, most apps are built with modern SDKs, so most Android / Apple / Symbian apps work in IPv6-only + NAT64 networks
Mobile providers already do huge IPv4 NAT. T-Mobile is now doing IPv6 handsets with NAT64, which translate the IPv6 address on your phone to an IPv4 address to reach the IPv4 internet. IPv6 native services like Google are delivered end to end with IPv6, no NAT, no Firewall. http://groups.google.com/group/tmoipv6beta
Comcast and T-Mobile both have active trials with IPv6. If you are in either of there service areas you can connect to IPv6 today. See www.comcast6.net and http://groups.google.com/group/tmoipv6beta
Slashdot Mirror
And that path will last just as long as there are ipv4 addresses ... and then (drum roll) ....
Nope, in fact the only phone manufacturer that supports IPv6 on the cellular interface in Nokia. Talk about making false statements .... almost nothing works with IPv6, including 99% of home router, 99% of cell phones ... and nearly no DSL or cable providers support IPv6. It is only T-Mobile USA that has it for Nokia on Mobile. Maybe you are from the future where IPv6 is common, but it is not the case today.
As stated ITFA, NAT64 is the technology used to bridge IPv6 end users, like mobile phones, to long-tail content that is ipv4-only .... note, google, facebook, netflixs, yahoo, and others have all already turned on ipv6 to some extent. .... that represents over 50% of the internet traffic right there.
I have been using IPv6 on the T-Mobile USA beta and it works fine, the user experience is just like ipv4. Politics and dogmas aside, it's just a number for an end node and it works. If you google around, you can find links to try it out yourself on T-Mobile USA.
I have been using IPv6 on the T-Mobile USA beta and it works fine, the user experience is just like ipv4. Politics and dogmas aside, it's just a number for an end node and it works.
+1
Yep, that is the fundamental issue ..... if there was a enough ipv4, we could dual-stack. But, dual-stack is a broken idea when there are no IPv4 address to be had and network edges like mobile and cloud are growing so fast.
The whales have already shown the time is now to move to ipv6: ipv6.google.com, ipv6.netflix.com, ipv6.weather.yahoo.com, www.v6.facebook.com, ipv6.t-mobile.com, ipv6.comcast.net, ipv6.cnn.com, www.brocade.com, www.ipv6.cisco.com, and the list goes on. These companies are not going dual stack for fun on their servers, they are doing it because ipv6-only users are on the horizon and they all know it. Without a native IPv6 setup, they will be screwed going via a proxy on NAT64, and they dont want that.
The address is not assigned to the tower, it is assigned to your phone ... so that how it scales and why you need 10net space on the handsets ... yes, there really is not enough ipv4
If dual-stack works so great, how come when i google ipv6 most pages instruct me on ways to turn it off so that my computer only uses ipv4?
T-Mobile is doing IPv6-only, and the Ipv4 applications are SOL. The good news, most apps are built with modern SDKs, so most Android / Apple / Symbian apps work in IPv6-only + NAT64 networks
right here groups.google.com/group/tmoipv6beta
T-Mobile USA has IPv6 for you http://groups.google.com/group/tmoipv6beta
Mobile providers already do huge IPv4 NAT. T-Mobile is now doing IPv6 handsets with NAT64, which translate the IPv6 address on your phone to an IPv4 address to reach the IPv4 internet. IPv6 native services like Google are delivered end to end with IPv6, no NAT, no Firewall. http://groups.google.com/group/tmoipv6beta
Comcast and T-Mobile both have active trials with IPv6. If you are in either of there service areas you can connect to IPv6 today. See www.comcast6.net and http://groups.google.com/group/tmoipv6beta
Yep, T-Mobile USA is doing this and it works for me http://groups.google.com/group/tmoipv6beta
HSPA+ that T-Mobile USA has launched 21 megabits/sec today. I have seen 10meg peaks on it myself