3 ms·

Few of the big cloud providers -- EC2, Azure, etc. -- support IPv6. That's the big bottleneck. Fundamentally I think IPv6 itself is fine, but the transition wa

by api 11y ago

Few of the big cloud providers -- EC2, Azure, etc. -- support IPv6. That's the big bottleneck. Fundamentally I think IPv6 itself is fine, but the transition was utterly botched. They should have unshelved 240.0.0.0/4 and mapped IPv6 onto it, allowing IPv4 applications to access select "early adopter" regions of IPv6. That would have been a start.

betaby 11y ago
IPv4 to IPv6 mapping exists for a long time https://en.wikipedia.org/wiki/6to4 https://en.wikipedia.org/wiki/6to4
- ay 11y ago
  No, no no no. 6to4 as a mechanism is the worst mistreatment you can do to your users because of the way it works with asymmetric traffic paths traversing the gateways you can not control. I think what you meant to post was this: https://en.wikipedia.org/wiki/NAT64 https://en.wikipedia.org/wiki/NAT64
  - api 11y ago
    Neither of these are actually usable in the real world.
    - ay 11y ago
      re. 6to4: agreed, and never will, see https://tools.ietf.org/html/rfc7526 https://tools.ietf.org/html/rfc7526 re NAT64: not so agreed... 1. T-Mobile USA: they have few millions of IPv6-only subscribers using 464XLAT which has NAT64 as a component. 2. Starting from iOS9, every app submitted to App Store will have to work with IPv6 or across the NAT64 as a criterion for appstore submission: http://www.internetsociety.org/deploy360/blog/2015/06/apple-will-require-ipv6-support-for-all-ios-9-apps/ http://www.internetsociety.org/deploy360/blog/2015/06/apple-... 3. my own anecdata from the IPv6-only default WiFi SSID at FOSDEM conference in Brussels this year is that ~40% of the total devices were able to use IPv6-only SSID behind NAT64 - up from about 15-20% last year. Will be interesting to see the numbers for the next year - with Android 5.0 shipping RDNSS and Apple's move with iOS, this number should go up noticeably.

3 ms·

Few of the big cloud providers -- EC2, Azure, etc. -- support IPv6. That's the big bottleneck. Fundamentally I think IPv6 itself is fine, but the transition wa

by api 11y ago

betaby 11y ago
IPv4 to IPv6 mapping exists for a long time https://en.wikipedia.org/wiki/6to4 https://en.wikipedia.org/wiki/6to4
- ay 11y ago
  No, no no no. 6to4 as a mechanism is the worst mistreatment you can do to your users because of the way it works with asymmetric traffic paths traversing the gateways you can not control. I think what you meant to post was this: https://en.wikipedia.org/wiki/NAT64 https://en.wikipedia.org/wiki/NAT64
  - api 11y ago
    Neither of these are actually usable in the real world.
    - ay 11y ago
      re. 6to4: agreed, and never will, see https://tools.ietf.org/html/rfc7526 https://tools.ietf.org/html/rfc7526 re NAT64: not so agreed... 1. T-Mobile USA: they have few millions of IPv6-only subscribers using 464XLAT which has NAT64 as a component. 2. Starting from iOS9, every app submitted to App Store will have to work with IPv6 or across the NAT64 as a criterion for appstore submission: http://www.internetsociety.org/deploy360/blog/2015/06/apple-will-require-ipv6-support-for-all-ios-9-apps/ http://www.internetsociety.org/deploy360/blog/2015/06/apple-... 3. my own anecdata from the IPv6-only default WiFi SSID at FOSDEM conference in Brussels this year is that ~40% of the total devices were able to use IPv6-only SSID behind NAT64 - up from about 15-20% last year. Will be interesting to see the numbers for the next year - with Android 5.0 shipping RDNSS and Apple's move with iOS, this number should go up noticeably.