[167436] in North American Network Operators' Group
Re: turning on comcast v6
daemon@ATHENA.MIT.EDU (Jared Mauch)
Wed Dec 11 14:39:19 2013
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <AFF69F7C-25DB-4B56-9436-B003A4388765@delong.com>
Date: Wed, 11 Dec 2013 14:32:38 -0500
To: Owen DeLong <owen@delong.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Dec 11, 2013, at 2:18 PM, Owen DeLong <owen@delong.com> wrote:
> It doesn=92t. You can get IPv6 working with off-the-shelf equipment if =
you choose to.
>=20
> Randy chose to use that particular hardware and software combination.
I'll chime in with a link to data:
http://www.google.com/ipv6/statistics.html#tab=3Dper-country-ipv6-adoption=
Looking at things, USA is at 5%+ adoption, which is due to the hard work =
of folks at Comcast (and other ISPs).
Overall google is seeing 2.5%+ of traffic over native IPv6. in several =
cases IPv6 is actually faster than IPv4:
16 bytes from 2001:418:3f4::5, icmp_seq=3D0 hlim=3D57 time=3D18.649 ms
16 bytes from 2001:418:3f4::5, icmp_seq=3D1 hlim=3D57 time=3D19.008 ms
16 bytes from 2001:418:3f4::5, icmp_seq=3D2 hlim=3D57 time=3D18.959 ms
^C
--- puck.nether.net ping6 statistics ---
4 packets transmitted, 3 packets received, 25.0% packet loss
round-trip min/avg/max/std-dev =3D 18.649/18.872/19.008/0.159 ms
PING puck.nether.net (204.42.254.5): 56 data bytes
64 bytes from 204.42.254.5: icmp_seq=3D0 ttl=3D55 time=3D32.920 ms
64 bytes from 204.42.254.5: icmp_seq=3D1 ttl=3D55 time=3D18.467 ms
64 bytes from 204.42.254.5: icmp_seq=3D2 ttl=3D55 time=3D22.014 ms
64 bytes from 204.42.254.5: icmp_seq=3D3 ttl=3D55 time=3D20.807 ms
64 bytes from 204.42.254.5: icmp_seq=3D4 ttl=3D55 time=3D19.096 ms
^C
--- puck.nether.net ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev =3D 18.467/22.661/32.920/5.280 ms
- jared=
