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. Frank -----Original Message----- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Jared Mauch Sent: Tuesday, June 17, 2014 7:42 PM To: Mark Andrews Cc: NANOG Subject: Re: Ars Technica on IPv4 exhaustion On Jun 17, 2014, at 7:24 PM, Mark Andrews <ma...@isc.org> wrote: > > In message <32832593.4076.1403046439981.javamail.r...@benjamin.baylink.com>, Ja > y Ashworth writes: >> ----- Original Message ----- >>> From: "Jared Mauch" <ja...@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 suggested >> 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: http://xkcd.com/865/ 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. - Jared
