Facebook are now using IPV6 only for all their internal networking ( http://www.internetsociety.org/deploy360/blog/2014/03/facebooks-extremely-impressive-intern

Facebook are now using IPV6 only for all their internal networking ( http://www.internetsociety.org/deploy360/blog/2014/03/facebooks-extremely-impressive-internal-use-of-ipv6/ http://www.internetsociety.org/deploy360/blog/2014/03/facebo... ) While it's possible to get by on IPV4, most of what we're doing is workarounds. DHCP is a workaround (although a useful one), NAT is a workaround, at least some VPN use-cases are workarounds (e.g inter-office connection between private subnets) A lot of problems go away when you have essentially unlimited address space to play with. The downside so far is that very few providers offer native IPV6. This is frustrating but manageable. There are tunnelling providers such as Hurricane Electric ( http://tunnelbroker.net http://tunnelbroker.net ) and SixXs ( http://sixxs.net http://sixxs.net ) Hurricane Electric are great, and they offer free self-study and certification. I was unable to open an account at SixXs. My advice would be to start experimenting with it now. This will give you a headstart over the rest of the field as IPV6 becomes more popular. If you're working with new infrastructure, experiment with IPV6 only. If you can solve those problems, your skills will be in high demand