IPv4 Depletion - Hackdot

Re:IPv4 Depletion by api on Thursday June 25, 2015 @06:07PM (#9781217)

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.

[ Parent | on HN ]

Re:IPv4 Depletion by betaby on Thursday June 25, 2015 @06:44PM (#9781389)

IPv4 to IPv6 mapping exists for a long time https://en.wikipedia.org/wiki/6to4

[ Parent | on HN ]

Re:IPv4 Depletion by ay on Friday June 26, 2015 @04:04PM (#9787392)

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

[ Parent | on HN ]

Re:IPv4 Depletion by api on Friday June 26, 2015 @04:14PM (#9787451)

Neither of these are actually usable in the real world.

[ Parent | on HN ]

Re:IPv4 Depletion by ay on Friday June 26, 2015 @04:28PM (#9787527)

re. 6to4: agreed, and never will, see 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-...

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.

[ Parent | on HN ]