IPv6 mistakes, was: Re: Looking for an IPv6 naysayer...

Alexander Harrowell a.harrowell at gmail.com
Fri Feb 11 09:13:54 CST 2011


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 
> their traffic since a significant fraction of that traffic is from 
> mobile devices which are going to take much longer than PCs to get to 
> using IPv6 in large numbers.  Also, Netflix is even more problematic 
> since the bulk of their traffic, and the fastest growing segment as 
> well, is coming from Xboxes, Tivos, other gaming consoles, and  TVs with 
> enough embedded brains to talk directly.  Those devices will also 
> seriously lag behind PCs in IPv6 support

Recommendation: if you're doing some sort of under-the-TV device, if it does 
6to4 or some other kind of IPv6 tunnelling (like Apple Airports), colocate your 
relay/vpn host/tunnel exit points with content CDN servers rather than sending 
everything via your head office location.

If you're snooping on the traffic, you can always configure the nodes to do 
that:-{0
-- 
The only thing worse than e-mail disclaimers...is people who send e-mail to 
lists complaining about them
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20110211/8b9634ca/attachment.bin>


More information about the NANOG mailing list