[172391] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Ars Technica on IPv4 exhaustion

daemon@ATHENA.MIT.EDU (Jared Mauch)
Tue Jun 17 20:41:46 2014

X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <20140617232402.0FC23185D08F@rock.dv.isc.org>
Date: Tue, 17 Jun 2014 20:41:55 -0400
To: Mark Andrews <marka@isc.org>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org


On Jun 17, 2014, at 7:24 PM, Mark Andrews <marka@isc.org> wrote:

>=20
> In message =
<32832593.4076.1403046439981.JavaMail.root@benjamin.baylink.com>, Ja
> y Ashworth writes:
>> ----- Original Message -----
>>> From: "Jared Mauch" <jared@puck.nether.net>
>>=20
>>> 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.=20
>>=20
>> "no" adverse impact?
>>=20
>> 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=20
>=20
> What's this "4A" garbage?
>=20
>> worse than not...
>=20
> See the red line.  https://www.google.com/intl/en/ipv6/statistics.html=20=

>=20
> 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.
>=20
> 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=

home help back first fref pref prev next nref lref last post