IPv6 woes - RFC

Thu Sep 9 01:55:14 UTC 2021

On Wed, 08 Sep 2021 11:39:50 -0700, Owen DeLong via NANOG said:

> The reality is that if we get content dual-stacked and stop requiring IPv4
> for new eyeball installations, thatâ€™s the biggest initial win.

The problem is "get content dual-stacked".

Somebody made this handy page of the IPv6 status for the Alexa Top 500.

http://www.delong.com/ipv6_alexa500.html

Awful lot of red spots even in the top 100.  Hell, even amazon.com
isn't IPv6 yet.  And the long tail is going to be the death of a thousand
cuts for the call center unless you have a way to deal with those sites.

And the devil is in the details.  cnn.com itself has a quad-A. But looking
at Chrome loading it with the IPvFoo extension, I see that of the 145
addresses it hits, only 38 are IPv6, the rest are IPv4.

On the other hand, looking at *who* are the IPv4, they seem to be
overwhelmingly ad servers and analytics sites - so maybe hitting cnn.com as
IPv6-only is a win for the consumer.  I rather suspect that the CFO of CNN
would see it differently though....

(Eerily reminiscent of the factoid that 60% of the cost of a long distance
phone call before the AT&T breakup was keeping the accounting records
so they could bill the customer)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 494 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20210908/031ea7cc/attachment.sig>