[137340] in North American Network Operators' Group
Re: IPv6 mistakes, was: Re: Looking for an IPv6 naysayer...
daemon@ATHENA.MIT.EDU (Alexander Harrowell)
Fri Feb 11 10:15:09 2011
From: Alexander Harrowell <a.harrowell@gmail.com>
To: nanog@nanog.org
Date: Fri, 11 Feb 2011 15:13:54 +0000
In-Reply-To: <4D554F29.8070903@ispalliance.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--nextPart3200266.nec4v4B06F
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
On Friday 11 February 2011 15:00:57 Scott Helms wrote:
> While Facebook working over IPv6 will be a big deal you won't get all of=
=20
> their traffic since a significant fraction of that traffic is from=20
> mobile devices which are going to take much longer than PCs to get to=20
> using IPv6 in large numbers. Also, Netflix is even more problematic=20
> since the bulk of their traffic, and the fastest growing segment as=20
> well, is coming from Xboxes, Tivos, other gaming consoles, and TVs with=
=20
> enough embedded brains to talk directly. Those devices will also=20
> seriously lag behind PCs in IPv6 support
Recommendation: if you're doing some sort of under-the-TV device, if it doe=
s=20
6to4 or some other kind of IPv6 tunnelling (like Apple Airports), colocate =
your=20
relay/vpn host/tunnel exit points with content CDN servers rather than send=
ing=20
everything via your head office location.
If you're snooping on the traffic, you can always configure the nodes to do=
=20
that:-{0
=2D-=20
The only thing worse than e-mail disclaimers...is people who send e-mail to=
=20
lists complaining about them
--nextPart3200266.nec4v4B06F
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
iEYEABECAAYFAk1VUj4ACgkQ0c69vkueJcQN7ACeJG+yBdDvnvmUkJqndehD528Y
5UAAn051DTeu69cLmCoMyYspu3B7jUCC
=j0+h
-----END PGP SIGNATURE-----
--nextPart3200266.nec4v4B06F--
