[zkms]

It's not, alas, a flip-a-switch upgrade, given how many CPEs and other equipment have shoddy or non-existent IPv6 support.

Forward-thinking network operators (like Verizon Wireless or Comcast or T-Mobile USA) have taken advantage of the LTE and DOCSIS 3 transitions (which inherently involve installing and provisioning new hardware on a massive scale) to properly provision and deploy IPv6 to their customers.

There's plenty of large eyeball networks (https://www.akamai.com/uk/en/about/our-thinking/state-of-the... , click on "Networks" to sort by traffic volume, the second column is the percentage of requests from that network via IPv6) that have working IPv6 deployed and used to a significant percentage of their subscribers -- some around 80%.

[flyinghamster]

The CPE problem is a bit of an elephant in the room. Just from my own experience, setting up IPv6 on my Comcast connection took quite a bit of fumbling around before I managed to hit on the right settings - and my router's GUI hardly even acknowledges the existence of IPv6 at all.

On the upside, I have a /60 to play with...

[phil21]

This is really hit or miss (the configuration part of it) and it won't become really ubiquitous until it gets enabled on all consumer CPE by default. That said, I set up a recent Asus for a friend and it was nearly single-click easy on Comcast. Much improved since even 18 months ago.

This is also why ISP's prefer to rent you CPE and (preferably) manage it remotely.

This would in turn cause more content networks to support ipv6 - once even 1% of eyeballs can't hit revenue producing websites those customers will demand v6 or move IaaS/SaaS/etc. providers.

[zkms]

The CPE problem is why mobile has such good IPv6 deployment (along with the LTE people having their act together about IPv6) -- it's the only sector where people will eagerly upgrade their CPEs en masse :)