31–40 of 64 posts
Ok, ipv6 is here. Or not. Anyway, when is Amazon going to support ipv6 on ec2?
Here, yes, but not particularly wide-spread and slowly becoming more necessary. A little tool I built last week .. is your site IPv6 ready? http://ready.chair6.net
Earlier quoted context omitted.
The natural solution will be that IPv4 addresses will start getting more and more expensive as they become scarce. At some point, switching to IPv6 will be the cheaper option, and then the switch will happen.
But if you only buy an ipv6 address, the people who are only on ipv4 can't get to you. By itself, the ipv6 address is nearly worthless. The only people who have them now are people who also have an ipv4 address. ipv4 isn't going away any time soon...
Volia now everybody has an ipv6 address.
The main concern seems to be about ISPs starting to NAT everybody and their dog. Well, guess what, they just can't do that. For starters because their users would get very angry when their torrents stop working, and would jump ship for any other ISP that announces that it either doesn't do NAT or has implemented IPv6.
There is still a huge amount of work that can be done to compress the usage of v4 address space. Maybe not much that the RIRs or the ISPs can do, but as the cost of owning a static IPv4 address goes up (and I believe that it will go _way_ up), end users will start compressing their public services into fewer addresses and giving back small subnets to their providers to reduce costs. I mean, who the hell needs to have a mail server and a web server in two different public addresses when they can just do port-forwarding over a single address? (And since most servers are on DMZs with private addressing, they are mostly doing it already, it's just a matter of renumbering.)
The case most likely to go NAT is also the most likely to go IPv6: mobile devices. These are mostly behind NAT already, and going IPv6 would actually reduce costs for ISPs. It would also put ISPs in the track for more extensive IPv6, since the major problem now is that people have little knowledge of how IPv6 works and ISPs are trying to avoid the pain. The issue is, of course, that 99.9% of mobile devices don't support dual-stack and even in a pure v6 configuration don't actually work properly.
For this I predict that in 10 years the move to IPv6 will still be half-way. Considering that we are so close to IPv4 depletion and there is virtually _no_ IPv6 to be seen, I'm being faily optimistic.
a) what impact will this have on me as Joe Public internet user?
b) what impact will this have on me as a web developer?
Or point me to suitable websites that explain in quick skimmable chunks...
Ok, ipv6 is here. Or not. Anyway, when is Amazon going to support ipv6 on ec2?
$ dig +short AAAA ip6.16s.us
2001:4830:1600:2e4::2
IPv6 is in no sense here. The fiat allocators can exhaust their address space completely and the Internet will continue to function indefinitely; it will simply become more expensive (first marginally, and then significantly) to hold a static address. There are deep problems with universal deployment of IPv6 far beyond simply getting people to throw a switch; the number of popular software packages that will malfunct…
It's worth noting that on the 8th of June this year, Google, Facebook, Yahoo!, Akamai and others are going dual stack IPv4+IPv6 for a 24 hour period to make people with broken setups aware that they have broken setups. "World IPv6 Day":
https://isoc.org/wp/worldipv6day/
Basically, if you're one of the people with a system which thinks it has IPv6 access but doesn't, then you're not going to be able to access Facebook, Google, Yahoo etc on that day.
Earlier quoted context omitted.
If your application doesn't work behind an IPv4 NAT box, then your application is broke already. It will likely be broke in IPv6 as well since firewalls are not going away (and many of the same protocols that break because of NAT also break with stateful firewalls).
I'm implying a legacy application that only works with IPv4 addresses, and doesn't work well behind a NAT. I know those are two separate issues, but the transition to IPv6 will likely require those software packages to be rewritten anyways so the idea that it will be broken even on IPv6 is moot because it won't even work on IPv6 as it currently is.
Even after innumberable discussions about this subject, I still don't get why people are so afraid of NAT. The main concern seems to be about ISPs starting to NAT everybody and their dog. Well, guess what, they just can't do that. For starters because their users would get very angry when their torrents stop working, and would jump ship for any other ISP that announces that it either doesn't do NAT or has implemented…
I only have a basic understanding of IPv4 vs IPv6, so can someone explain to me: a) what impact will this have on me as Joe Public internet user? b) what impact will this have on me as a web developer? Or point me to suitable websites that explain in quick skimmable chunks...
a2) Alternatively, in a year or so, you get service from a brand new ISP that has no v4 connectivity (so, you are v6 native), and you cannot access anything on the v4 Internet around the world (e.g. most things today).
b) Don't store IP addresses as 32bit integers, or as 15 character strings. Be aware that geolocation services probably don't do well with v6 addresses. Make sure your deployment platform has the infrastructure in place to serve both v4 and v6 customers (or at least v6 after a year or two) - AAAA dns records, etc.