So... what incentive is there to make your services IPv6 compatible today other than geek cred?
I set up an IPv6 tunnel at home, and recently added AAAA records to my web site (a tech blog). For my very technical audience, barely 1.8% traffic is IPv6. If I look only at the RSS feed, it goes up to 3%, which seems to be mostly Apple machines and hosted RSS aggregators.
Depends how you look at it. There might not be an individual incentive for you to do it, but there is a general incentive for us to do it. You can choose to contribute towards the move to IPv6, or not. I prefer to contribute, because I recognise how important it is.
It looks like CloudFlare are counting down until 2012-06-06 00:00:00 in your local time, while the WorldIPv6Launch site is counting down to 2012-06-06 00:00:00 UTC.
When will phones get IPv6? Then you can host services yourself, e.g a website, your email. Basically opens up all sorts of possibilities that will allow people to own their content.
(yeah sure you prob want to back up to somewhere off your phone)
I'm sure phone providers will find a way to configure their links so that they work the same as with IPv4 (i.e. no incoming connection allowed). This isn't even necessarily a bad thing - remember all these jailbroken iphones with the default root password running an sshd? While not providing perfect security by a long shot, denying all incoming connections to a client on the firewall can help mitigate some issues.
It also "fixes" a lot of potential "problems" like people running p2p software on their phones or using VoIP instead of the much higher priced voice calls by the phone proivder (yes. voip works today, but it could work ever so much better if these devices were accessible directly)
One of Australia's 3g networks had an alternate APN you could use that gave you direct access to the internet, and an externally facing IP address. I only discovered this last month and the network is being shut down this year. It's such a pity this isn't a standard feature.
Would be nice if they gave you an Internet facing IPv6 address by default, but default firewall rules that blocked incoming connections, and the ability to modify those rules for your connection only.
But I guess that would only be valuable if they also gave you a static IP. And static IPs for client devices like phones aren't exactly a good thing from a privacy perspective. Ideally you'd have both a dynamic and a static IP, and new outgoing connections would originate from the dynamic one.
I wouldn't want to run a Web server or SMTP server on Dynamic DNS. The delays introduced by DNS cache when your IP changes provide an opportunity for somebody else to intercept/replace your traffic. Although I admit that is pretty unlikely.
Android phones on Verizon's LTE network get a global IPv6 address by default. Their firewall prevents unsolicited incoming traffic though. Not sure about AT&T LTE.
I get no ipv6 connectivity on my sgh989 (tmobile usa ver of galaxys2) when on 4g (turning off wifi). On wifi, I get ipv6 (local net has ipv6 connectivity).
Could it be regional... T-Mobile enabling ipv6 for some cities and not others? Or perhaps the current tmobile firmware (mine is 2.3.6, T989, UVKL1) for their sgh989 disables ipv6 for the gsm/utms portion of the radio.
CloudFlare provides a IPv6 -> IPv4 gateway. As a result, if you're on CloudFlare, your host doesn't need to have IPv6 support for your site to be available. You can enable the gateway for free. CloudFlare's DNS listens on IPv6 and will return a valid AAAA record when requested. If your host supports IPv6 then the connection is IPv6 end-to-end. If your host only supports IPv4 then the connection is IPv6 from the browser to CloudFlare's network, and then IPv4 from CloudFlare's network to your origin server. Here's more on how it works:
Oh and there was me thinking that this was an attempt to produce an alternate replacement for ipv6 that is designed with migration in mind rather than the ivory tower OSI style standard it became.
