critical mass update on IPv6

Fri Mar 10 16:17:45 UTC 2017

Just update for those that care.

As you may know, all the major cellular providers in the USA (VZ, AT&T,
T-Mobile, Sprint) support IPv6 by default on many models of phones.
Comcast and AT&T and other large broadband players also have IPv6 widely
deployed by default

http://www.worldipv6launch.org/measurements/

Most of the major (elephants) content is IPv6 (Google, FB, Netflix, ...)

And now the other end in the cloud is coming along nicely

https://aws.amazon.com/blogs/aws/aws-ipv6-update-global-support-spanning-15-regions-multiple-aws-services/

https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-ipv6-overview

https://cloud.google.com/compute/docs/load-balancing/ipv6

Not to mention that Digital Ocean , Softlayer / IBM, Linode, and others
also support IPv6

And now you are seeing ipv4 lose support in various classes of products
like set-top boxes (
http://corporate.comcast.com/comcast-voices/world-ipv6-launch-four-years-later-taking-stock-and-looking-forward
) and static IPs (
https://www.theregister.co.uk/2017/03/10/verizon_running_out_of_ipv4_addresses/
)