- if you're a software developer, make sure your code can handle ipv6 address strings and fields. Very few do. - if you work at an ISP, start evangelizing ipv6

- if you're a software developer, make sure your code can handle ipv6 address strings and fields. Very few do. - if you work at an ISP, start evangelizing ipv6 to coworkers and managers. Major ISPs have had their heads in the sand and are really counting on implementing carrier-level NAT, which brings me to... - if you're an ISP customer, make it quite clear to to your ISP that you won't accept a connection behind an ISP NAT, and you'll switch to a different ISP if they impose one on you. Also make it clear that you'll advise anyone you do tech support for (families, friends) to do the same. - if you program network video games or voip software, get the word out (either through offical documentation or a blog) about the evil of ISP-level NAT and how this will affect your application. Actually, some sort of ipv4 NAT will be inevitable for ISP customers. But the really atrocious ISPs won't give you a unique block of ipv6 addresses to mitigate that.