Re:IAB Statement on IPv6
by ryao on Tuesday November 08, 2016 @04:21AM
(#12898797)
Amazon and github are the two major offenders.
[ Parent
| on HN ]
Re:IAB Statement on IPv6
by executesorder66 on Tuesday November 08, 2016 @04:25AM
(#12898816)
https://ipv6wallofshame.com/
Baidu, Twitter, Instagram and Reddit are also major players who could make a huge difference.
Re:IAB Statement on IPv6
by tomschlick on Tuesday November 08, 2016 @04:26AM
(#12898828)
The worst part about reddit in that case is that they use cloudflare which could be a 1 click update to ipv6. Previously they have stated that internal systems (spam, court orders, reporting) are holding them back from the change.
Still plausible, e.g. if their spam filters, court order handling and reporting expect to see IPv4 client addresses in their input and/or databases.
Re:IAB Statement on IPv6
by daurnimator on Tuesday November 08, 2016 @04:48AM
(#12898918)
Cloudflare have a workaround for that too! https://support.cloudflare.com/hc/en-us/articles/202494830-P...
You know, Cloudflare gets a lot of shit around here for being a centralizing entity in a decentralized Internet (sometimes justifiably), but they've done a hell of a lot to push forward needed changes in the Internet infrastructure. Often at little benefit to themselves.
Here's our motivation: https://blog.cloudflare.com/evenly-distributed-future/
Re:IAB Statement on IPv6
by Gruselbauer on Tuesday November 08, 2016 @04:25PM
(#12904082)
That is a concise, interesting read topped off by some Gibson quotes. Thanks.
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?".
Re:IAB Statement on IPv6
by CountSessine on Tuesday November 08, 2016 @10:16PM
(#12905813)
Oh so not even Amazon, Twitter or GitHub gives a crap about IPv6? Why should we?
If this is really what they're thinking, then they have no pride in their work and will never be the best at what they do. I suspect most of the engineers working for Amazon, Twitter, and GitHub are well aware that they're lagging in ipv6, and are very intent on catching up.
It seems to have worked for python 3.
I kinda doubt that the site had a real influence on that.
Those are just one site each though. GitHub and Amazon are many.
Also, I am not sure if googleadservices.com should be on that list. Leaving advertising on IPv4 to die might be for the best. ;)
At a cursory glance, it seems that Google or Google-owned sites make up a majority of the IPv6-enabled sites. Seems to me the numbers would be a lot lower without Google's work.
The list also has a ton less green when you consider that most of the sites are just the google search page with different TLDs.
With poor adoption rate of IPv6 persists in China, half of those listed (taobao, tmall, baidu, hao123, qq, youku, sina, weibo, etc.) just won't change in near future.
I am visiting China. It seems impossible to get an IPv6 address from either China Telecom (the ASN lacks IPv6 peering) or a datacentdr within China. Sending traffic to a VM in South Korea has similarly had the issue where I cannot find any VMs with IPv6 support, although most have terrible latencies.
Re:IAB Statement on IPv6
by CountSessine on Tuesday November 08, 2016 @10:20PM
(#12905828)
I don't understand; APNIC ran out of ipv4 addresses ages ago. How do they...internet?
Re:IAB Statement on IPv6
by witty_username on Wednesday November 09, 2016 @01:24AM
(#12906695)
I think IPv4 addresses can be bought for cheaper than the cost to transition to IPv6.
That site correctly lists apple.com as not supporting IPv6. The funny thing is that www.apple.com does support it.
Same with microsoft.com.
How is this the case?
Both Microsoft and Apple's www sites use Akamai's CDN, via a cname to a CNAME to something in akamaiedge.net, which support ipv6. The apex record of a domain (that is, the root record, microsoft.com or apple.com) cannot be a CNAME, it can only have an A, NS, MX or TXT record. A records make dynamic infrastructure hard, because they require API coordination between your DNS provider and your CDN. So Microsoft and apple host their own apex domain records via A records to static IPs in their own IP blocks, and have these servers issue a permanent http redirect to www.
apple.com isn't but redirects to www.apple.com which is IPv6 enabled (akamai)
https://ripe73.ripe.net/archives/video/1539/ tells a different story.
Re:IAB Statement on IPv6
by liveoneggs on Tuesday November 08, 2016 @06:53AM
(#12899492)
as fastly goes, so goes github