3 ms·
Why do you care? It's not a resource that's a massive loss once it's gone like forests or oil. It's still all there, just in use. I don't really see a big prob
by jodrellblank 16y ago
Why do you care? It's not a resource that's a massive loss once it's gone like forests or oil. It's still all there, just in use.
I don't really see a big problem with a move to IPv6 either - there are four main tripping points and all four of them aren't a problem. Imagine there's no more IPv4 space to request and you are forced to use IPv6 for your new site.
1) Can your IPv6 site get out to the IPv4 internet? Yes - you can have an IPv4 address behind NAT if it comes to it.
2) Can your IPv6 site get out to the IPv6 internet? Yes.
3) Can the IPv6 internet get to your site? Yes.
4) Can the IPv4 internet get to your site? If they have a tunnel broker. That means no. But as IPv6 takes off, ISPs will do this automagically.
So shortly, the only problem with having an IPv6 only site is that some users around the world on slower to adapt ISPs wont be able to get to it ... yet.
The hard parts are device firmware not supporting IPv6, planning and rollout and management and billing systems not supporting IPv6, and that's not something you can fix (except by becoming a consultant) but it's also not something you really care about. So Joe's Cheap Websites Ltd. management page wont let you create IPv6 DNS records. Don't use them. So printers from 1998 wont let you give them IPv6 addresses - use IPv4 on that network, it will still work.
- tptacek 16y agoThis assumes applications are ready for IPv6. They overwhelmingly aren't. Virtually all networked applications assume that IP address resolution is going to result in a scalar integer and will break if it doesn't.