[SudoAlex]

All ISPs need to do is provide IPv6 connectivity, a router with IPv6 support - and the traffic will flow.

It really should be as simple as that! Windows Vista supports IPv6, modern versions of OS X supports IPv6, etc. You don't have to configure it - just like you don't have to figure IPv4 with DHCP. Typical end users don't question their IPv4 connectivity, they just plug in their router and things work. The exact same thing should happen with IPv6.

The only issue is going to be old customer routers which can't be upgraded with new firmware.

[coldpie]

What if the website you want to visit doesn't support IPv6?

[danyork]

Ask the website owner when they will support IPv6! (and you can point them to tutorials like this one: http://www.internetsociety.org/deploy360/resources/making-co... )

It would be great if more websites supported IPv6. Like, oh, (cough)(cough)HN(cough)(cough).

[zaphoyd]

In this case, your network is probably doing NAT64 or you should be doing it.

For non-HTTPS web there is also: https://www.sixxs.net/tools/gateway/

[akira2501]

NAT64? It's still an absolute mess. From http://en.wikipedia.org/wiki/NAT64:

"Not everything is accessible with NAT64, such as SIP, Skype, MSN, and sites with IPv4 literals.[a] However, 464XLAT RFC 6877,[3] which uses NAT64, allows for such protocols over ipv6 only connections."

[zaphoyd]

Agreed. None of the options for accessing IPv4 only websites via IPv6 only hosts are great. If you are running an IPv4 only website or service this should hopefully worry you.

[mhurron]

Everybody still supports IPv4 on the client. You run dual stack.