5 ms·

Why is this being supported on an entirely new endpoint instead of added to the existing ones?

by Twirrim 10y ago

agwa 10y ago
It's kind of sucky, but there are a couple of good reasons for it: 1. Some people have broken IPv6 connectivity. Their OS will prefer the IPv6 address and won't fall back to the IPv4 address until after a lengthy timeout. 2. People might have IP address restrictions in place that currently only have IPv4 addresses whitelisted. If suddenly they started using IPv6 addresses they'd be blocked and their applications would break.
- deleted 10y ago
  [deleted]
- WorldMaker 10y ago
  (1) is the user's OS responsibility. All modern OS systems have a complex system in place already for this (using ICMP preflighting and DNS resolution timing checks and simultaneous v4/v6 connections, among other things). We're already in a world were networks have to be IPv6-first or IPv6-only (mobile networks are IPv6-first and soon likely to be IPv6-only; several large US cable ISPs have moved or are moving to IPv6-first/IPv6-only; etc), at least in the consumer world.
  - agwa 10y ago
    I agree, and furthermore the success of World IPv6 Day in 2011 showed that such breakage isn't all that common in the wild. The second point is still a real concern though.
  - saurik 10y ago
    > (1) is the user's OS responsibility. I don't care whose "responsibility" it is: if it costs my company a customer and it is something that can be fixed on my end with a seemingly simple workaround, it is something that I should fix, and I am glad that Amazon is thinking this through, particularly if it breaks an existing user when they roll out the upgrade. I mean: imagine if 0.1% of Netflix customers woke up today and the only immediate recourse Netflix has when they start being flooded with complaints is "you will need to upgrade your OS: we can no longer support whatever slightly older version you have.
detaro 10y ago
Might be to avoid problems with client libraries, firewalls, ... that don't react properly to it? E.g. if something tries to use IPv6 behind a firewall that blocks it and doesn't fall back to IPv4?
jakozaur 10y ago
Backward compatibility. If you whitelist in access rules some IPv4 IPs, than adding IPv6 support to same endpoint may give 403 for some clients which try IPv6 first.
mrpippy 10y ago
I hope the documentation deprecates usage of the old endpoints / strongly encourages use of the dual-stack ones.

Why is this being supported on an entirely new endpoint instead of added to the existing ones?

by Twirrim 10y ago

Why is this being supported on an entirely new endpoint instead of added to the existing ones?

agwa 10y ago

It's kind of sucky, but there are a couple of good reasons for it: 1. Some people have broken IPv6 connectivity. Their OS will prefer the IPv6 address and won't fall back to the IPv4 address until after a lengthy timeout. 2. People might have IP address restrictions in place that currently only have IPv4 addresses whitelisted. If suddenly they started using IPv6 addresses they'd be blocked and their applications would break.

deleted 10y ago
[deleted]
WorldMaker 10y ago
(1) is the user's OS responsibility. All modern OS systems have a complex system in place already for this (using ICMP preflighting and DNS resolution timing checks and simultaneous v4/v6 connections, among other things). We're already in a world were networks have to be IPv6-first or IPv6-only (mobile networks are IPv6-first and soon likely to be IPv6-only; several large US cable ISPs have moved or are moving to IPv6-first/IPv6-only; etc), at least in the consumer world.
- agwa 10y ago
  I agree, and furthermore the success of World IPv6 Day in 2011 showed that such breakage isn't all that common in the wild. The second point is still a real concern though.
- saurik 10y ago
  > (1) is the user's OS responsibility. I don't care whose "responsibility" it is: if it costs my company a customer and it is something that can be fixed on my end with a seemingly simple workaround, it is something that I should fix, and I am glad that Amazon is thinking this through, particularly if it breaks an existing user when they roll out the upgrade. I mean: imagine if 0.1% of Netflix customers woke up today and the only immediate recourse Netflix has when they start being flooded with complaints is "you will need to upgrade your OS: we can no longer support whatever slightly older version you have.

detaro 10y ago

Might be to avoid problems with client libraries, firewalls, ... that don't react properly to it? E.g. if something tries to use IPv6 behind a firewall that blocks it and doesn't fall back to IPv4?

jakozaur 10y ago

Backward compatibility. If you whitelist in access rules some IPv4 IPs, than adding IPv6 support to same endpoint may give 403 for some clients which try IPv6 first.

mrpippy 10y ago

I hope the documentation deprecates usage of the old endpoints / strongly encourages use of the dual-stack ones.