Ars Technica on IPv4 exhaustion
frnkblk at iname.com
Wed Jun 18 03:43:27 UTC 2014
These sites used to be dual-stacked:
www.cablelabs.com (over 180 days ago via ipv6.cablelabs.com)
www.att.net (over 44 days ago)
www.charter.com (over 151 days)
www.globalcrossing.com (over 802 days)
www.timewarnercable.com (over 593 days)
and www.t-online.de has been broken for over 33 days.
From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Jared Mauch
Sent: Tuesday, June 17, 2014 7:42 PM
To: Mark Andrews
Subject: Re: Ars Technica on IPv4 exhaustion
On Jun 17, 2014, at 7:24 PM, Mark Andrews <marka at isc.org> wrote:
> In message
<32832593.4076.1403046439981.JavaMail.root at benjamin.baylink.com>, Ja
> y Ashworth writes:
>> ----- Original Message -----
>>> From: "Jared Mauch" <jared at puck.nether.net>
>>> It does ring a bit hollow that these sites haven't gotten there when
>>> others (Google, Facebook) have already shown you can publish AAAA
>>> records with no adverse public impact.
>> "no" adverse impact?
>> Seems to me I've seen a few threads go by the last few years that
>> that there were a few pathological cases where having the 4A record was
> What's this "4A" garbage?
>> worse than not...
> See the red line. https://www.google.com/intl/en/ipv6/statistics.html
> Additionally Google and FaceBook have basically forced the client
> side to fix their broken network configurations by publishing AAAA
> records to everyone. It only takes one or two big sites to force
> this issue which they have done.
> You are nowhere near the bleeding edge by publishing AAAA records today.
What I do find interesting (and without any data) is why some folks have
removed IPv6, eg:
But there is no AAAA for it anymore.
My simple rant is: it's 2014, if you don't at least have IPv6 on for your
edge facing your ISP and your allocation, you're doing it wrong.
More information about the NANOG