Better late than never I guess, but come on... IPv6 is nearly 20 years old in 2 years...
IAB Statement on IPv6
31–40 of 131 posts
Re: IAB Statement on IPv6
#32I check the google stats[0] on ipv6 adoption every few months. Last time I checked it was barely 9% an now it's on 15% ! I would have never thought we'd get this far this fast. Looks like the switchover is actually going to happen. [0] https://www.google.com/intl/en/ipv6/statistics.html
Really interesting how it spikes on weekends! I wonder if this is because more home broadband connections are ipv6-enabled compared to businesses?
Yea, ISPs are upgrading home users for them.. Businesses tend to have their own equipment, and need to DIY the change, even if IPv6 is pushed down the wire to them by the ISP.
Re: IAB Statement on IPv6
#33Earlier quoted context omitted.
I work for one of the companies on that wall of shame. I wonder to what extent it has the reverse of the intended effect. "Oh so not even Amazon, Twitter or GitHub gives a crap about IPv6? Why should we?".
It seems to have worked for python 3.
I kinda doubt that the site had a real influence on that.
Re: IAB Statement on IPv6
#34Re: IAB Statement on IPv6
#35IMO the major thing holding back IPv6 on the web is amazon. A huge proportion of services are hosted on AWS, and the lack of IPv6 addressing of instances cannot be forgiven.
IPv6 and a return to end-to-end addressing isn't really aligned with the AWS style of proprietary platform lock-in.
Re: IAB Statement on IPv6
#36I noticed the other day that IPv6 growth is slowing down, as Google measures it. Its access share used to double every ten or eleven months, now it doubles more slowly, and seems likely to reach 20% only in 2017 instead of this year, and if it goes on as in the recent months, 30% in 2018 instead of in 2017. At a guess, many of most competent ISPs have done their thing and now we're seeing the more sluggish middle. Or…
Here in Japan, the largest consumer fiber wholesale network (NTT) "supports" IPv6, but you need a separate, $100 router that talks PPPoEv6 since none of the common consumer routers (including the one they provision you with) seem to support it. I also haven't been able to get PPPoEv6 working in macOS.
Anything that can run OpenWRT should be able to do PPPoE with IPv6.
Re: IAB Statement on IPv6
#37Earlier quoted context omitted.
Really interesting how it spikes on weekends! I wonder if this is because more home broadband connections are ipv6-enabled compared to businesses?
I guess it's hobbyists who's normal internet connection is ipv4, but on the weekend they have time to dick around with ipv6 devices and connections.
possible i guess
do we see something similar with .onion addresses?
ive found it much more reliable and secure to give devices i want access to from anywhere a .onion address rather than a ipv6 one.
secure by design rather than plaintext insecure and only works on some internet connections occasionally by design nightmare that is ipv6.
Re: IAB Statement on IPv6
#38I've not run into a problem solved by IPv6. There's no incentive for ISPs to provide good service, so they can just follow the mobile carrier route and nat/proxy when exhaustion becomes an issue.
As other countries go IPv6, more IPv4 addresses become available for the big cloud providers.
Re: IAB Statement on IPv6
#39IMO the major thing holding back IPv6 on the web is amazon. A huge proportion of services are hosted on AWS, and the lack of IPv6 addressing of instances cannot be forgiven.
Amazon seem to be slowly getting there: https://aws.amazon.com/about-aws/whats-new/2016/10/ipv6-supp...
ELBs support ipv6 as well
Re: IAB Statement on IPv6
#40Earlier quoted context omitted.
Amazon seem to be slowly getting there: https://aws.amazon.com/about-aws/whats-new/2016/10/ipv6-supp...
Wow, how did I miss this, CloudFront getting IPv6 support is huge!
"Getting?" I set up some CloudFront instances (or whatever they call them) a month ago and it had an IPv6 checkbox (which was unchecked by default, for some reason), but it seems to have been working fine ever since.