[173677] in North American Network Operators' Group
Re: Carrier Grade NAT
daemon@ATHENA.MIT.EDU (Owen DeLong)
Wed Jul 30 19:48:59 2014
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <36D0D1C9-84C4-4ED5-86DF-6D83E8687054@cisco.com>
Date: Wed, 30 Jul 2014 16:39:14 -0700
To: "Fred Baker (fred)" <fred@cisco.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jul 30, 2014, at 11:41 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>=20
> On Jul 30, 2014, at 8:45 AM, Owen DeLong <owen@delong.com> wrote:
>=20
>> I will say that if amazon would get off the dime and support IPv6, it =
would make a significant difference.=20
>=20
> Someone that works for Amazon once told me that they are primed for it =
now; the question is whether their customers tick the box appropriately.
>=20
Owens-MacBook-Pro:toneAC owendelong$ host www.amazon.com
www.amazon.com has address 72.21.215.232
Owens-MacBook-Pro:toneAC owendelong$ host www.google.com
www.google.com has address 74.125.239.145
www.google.com has address 74.125.239.146
www.google.com has address 74.125.239.148
www.google.com has address 74.125.239.144
www.google.com has address 74.125.239.147
www.google.com has IPv6 address 2607:f8b0:4005:802::1010
It appears to me that they have failed to tick their own box correctly.
I was talking about Amazon, not AWS. Yes, AWS would help too, but in =
terms of the Alexa list, Amazon would swing the percentage meaningfully. =
I don=92t know to what extent AWS would swing the percentage.
Owen
