You'd think I'd be doing something, but I'm not, really. The full extent of what I'll be doing is dealing with users on our network troubleshooting why access some now-v6-available services don't work out there on the greater internet. It'll be interesting data to have, and may be useful more widely. But...
Our network isn't really v6-ready. Our core network infrastructure just doesn't have everything it needs, or if it does it's hiding from me. Also, our firewall software is just old enough I don't trust it with v6.
As for the home, I've long had a project to get a v6 tunnel going but that's been blocked since I moved out east. In large part because I suddenly have a lot less time at home, and I also need better hardware for the device that'd have to be our IPv6 gateway; the 8yo Linux server is technically good enough but I no longer trust the hardware to stay up.
So, I'm going to be spending this World IPv6 day on resolutely v4 networks. Alas.
Our network isn't really v6-ready. Our core network infrastructure just doesn't have everything it needs, or if it does it's hiding from me. Also, our firewall software is just old enough I don't trust it with v6.
As for the home, I've long had a project to get a v6 tunnel going but that's been blocked since I moved out east. In large part because I suddenly have a lot less time at home, and I also need better hardware for the device that'd have to be our IPv6 gateway; the 8yo Linux server is technically good enough but I no longer trust the hardware to stay up.
So, I'm going to be spending this World IPv6 day on resolutely v4 networks. Alas.
The press is not doing a very good job of explaining the purpose of IPv6 day.
The problem with enabling IPv6 on web sites is that some implementations on desktop OSes did not handle fallback to IPv4 very well, so if a service published an IPv6 DNS record the client would try to use that even if it doesn't have IPv6 connectivity, causing the client to hang. This is supposed to have been fixed, but nobody knows if it's still a big problem or not, and it's one of the main reasons why most web sites have not enabled IPv6.
The point really has nothing to do with getting everyone to use IPv6 for a day, it's to make sure the web services can enable IPv6 and not break the existing IPv4 clients.
"Sitting out" is exactly what you're supposed to be doing. Just make sure nothing is broken when IPv6 is enabled on these sites.
And sit it out I did. There was one problem this morning when the google-sphere had a glitch, but other then that not a peep out of anyone.
Considering our client-base, I doubt I'd have gotten approval to play "games" with access to a certain key revenue system just to be part of the zeitgeist of the Internet. So having Google, Facebook, et. al. do it means I can read up on their after-action reports.