by If you are a sysadmin of any kind of system or network, you should at least be passingly familiar with IPv6 Day. If not, you're living under a rock.
You might not have deployed it yet, but you should at least be familiar with how the available IPv4 addresses are vanishingly small and that the address pool for IPv6 addresses is mind-bogglingly huge.
Hopefully you at least followed some of the posts last year from the 2011 World IPv6 Day, even if you didn't participate at that time.
For my part, I've had a tunnel through Hurricane Electric's TunnelBroker for many years now to give me IPv6 access. I've actually had several so that I can get IPv6 to all of the locations I control.
Recently though, I have one fewer tunnel: The main office for the company I work for was doing some large infrastructure replacements at my branch office and since I already had IPv6 via the tunnel I made sure to repeatedly mention IPv6 to them as part of the requirements list. Despite that they had not had any direct experience with it, due to my long-time running of tunnels and so on they made sure to include it in their plans and worked with me very closely to do the new setup. Better yet: the new network provider actually threw in IPv6 routing for the asking. [A big shout out to Hank and Pete: thank you!] My office now has even better IP IPv6 access than it did previously since it's natively-routed rather than tunnelled.
There is nothing technical standing in the way of each and every one of you doing similarly. You can tunnel IPv6 via a provider like Hurricane Electric, or you might be surprised and your network provider might even offer it natively like mine did.
At the least you should be experimenting with it to your personal networks (home, etc).
