[132415] in North American Network Operators' Group
Re: IPv6
daemon@ATHENA.MIT.EDU (John Gammons)
Mon Nov 22 15:10:03 2010
From: John Gammons <jgammons@gmail.com>
In-Reply-To: <AANLkTi=Sgo73ScKzLo_RmogpAqfSiCeL=n+e4jLj3FdP@mail.gmail.com>
Date: Mon, 22 Nov 2010 15:09:20 -0500
To: Cameron Byrne <cb.list6@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Nov 21, 2010, at 4:31 PM, Cameron Byrne wrote:
> On Thu, Nov 18, 2010 at 3:17 PM, Cameron Byrne <cb.list6@gmail.com> =
wrote:
>> On Thu, Nov 18, 2010 at 2:44 PM, Mike Tancsa <mike@sentex.net> wrote:
>>> On 11/18/2010 5:14 PM, Lee Riemer wrote:
>>>> Try tracerouting to 2001:500:4:13::81 (www.arin.net) or
>>>> 2001:470:0:76::2 (www.he.net) via Cogent.
>>>>=20
>>>=20
>>> Interesting. I noticed a similar issue with ipv6.cnn.com today. I =
dont
>>> see it via TATA, but see it via Cogent. So whats the story behind =
it
>>> and ARIN not being seen through cogent ? Is it due to no v6 =
relation
>>> bewtween he.net and Cogent ?
>>>=20
>>> 2620:0:2200:8:8888:8888:8888:8901 (whats with the crazy 8s?)
>>>=20
>>=20
>> Wow. CNN now has IPv6. That's awesome. I guess i missed the memo.
>>=20
>> So, major players with IPv6 are?
>>=20
>> ipv6.cnn.com (just book marked it)
>>=20
>> ipv6.comcast.net
>>=20
>> ipv6.google.com (or you can have it all with a white-list)
>>=20
>> www.ipv6.cisco.com
>>=20
>> www.v6.facebook.com
>> m.v6.facebook.com
>>=20
>> ipv6.t-mobile.com (admittedly, not major a major content source, but =
it's mine)
>>=20
>>=20
>=20
> Yahoo just dropped in on the IPv6 content party
>=20
> http://ipv6.weather.yahoo.com/
>=20
> I just bookmarked it. Well done Yahoos.
>=20
> Cameron
> =3D=3D=3D=3D=3D=3D=3D
> http://groups.google.com/group/tmoipv6beta
> =3D=3D=3D=3D=3D=3D=3D
Don't forget ipv6.netflix.com...=20
John
>=20
>> And, then debunking the "dual-stack is too risky" notion is
>> www.ucla.edu (which is a big business by most measures) and serves
>> AAAA and A records without a white-list or special FQDN.
>>=20
>> I have predicted that by the end of 2011 nearly ~50% of my network
>> traffic (mobile provider) can be served by IPv6 natively end to end.
>> I think a lot of folks that measure Facebook and Google (including
>> YouTube) traffic today can see how that is feasible given current
>> volumes and rates of growth. Hence, the viability of IPv6-only
>> endpoints (especially mobile) with NAT64/DNS64 as truly connecting =
the
>> IPv4 long-tail remaining 50% that will continue to shrink as more
>> major sites follow the CNN's path.
>>=20
>> Cameron
>> =3D=3D=3D=3D=3D=3D=3D
>> http://groups.google.com/group/tmoipv6beta
>> =3D=3D=3D=3D=3D=3D=3D
>>=20
>=20
