[187269] in North American Network Operators' Group
Re: IPv6 traffic percentages?
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Jan 25 18:02:47 2016
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <4A85328F-044E-4E47-8C94-3DE177BB2A24@ndsu.edu>
Date: Mon, 25 Jan 2016 15:01:37 -0800
To: Bruce Curtis <bruce.curtis@ndsu.edu>
Cc: NANOG <nanog@nanog.org>, "nanog-isp@mail.com" <nanog-isp@mail.com>
Errors-To: nanog-bounces@nanog.org
Not to put any sort of damper on wild speculation, but at the Southern =
California Linux Expo,
with native IPv4 and IPv6 dual stack support enabled on the wifi for the =
show, we saw close to
50% of all traffic on IPv6.
Owen
> On Jan 24, 2016, at 07:23 , Bruce Curtis <bruce.curtis@ndsu.edu> =
wrote:
>=20
>=20
>> On Jan 20, 2016, at 6:14 AM, nanog-isp@mail.com wrote:
>>=20
>> Hello all,
>>=20
>> Would those with IPv6 deployments kindly share some statistics on =
their percentage of IPv6 traffic?
>>=20
>> Bonus points for sharing top IPv6 sources. Anything else than the =
usual suspects, Google/YouTube, Netflix and Facebook?
>>=20
>> Some public information I've found so far:
>> - Comcast around 25% IPv6 traffic ( =
http://www.lightreading.com/ethernet-ip/ip-protocols-software/facebook-ipv=
6-is-a-real-world-big-deal/a/d-id/718395 )
>> - Comcast has over 1 Tb/s (of mostly YouTube traffic) over IPv6 ( =
http://corporate.comcast.com/comcast-voices/comcast-reaches-key-milestone-=
in-launch-of-ipv6-broadband-network )
>> - Swisscom 26% IPv6 traffic, 60% YouTube ( =
http://www.swinog.ch/meetings/swinog27/p/01_Martin_Gysi.pdf )
>>=20
>> I'd be very much interested in hearing from smaller ISPs, especially =
those having a very limited number of IPv4 addresses and/or running out.=20=
>>=20
>>=20
>> Thanks,
>>=20
>> Jared
>=20
>=20
> This is some more public info.
>=20
>=20
> On this page click to sort on IPv6 deployment.
>=20
> http://www.worldipv6launch.org/measurements/
>=20
> About 40% of traffic inbound to our University is IPv6. I see several =
Universities on the list above at more than 60%.
>=20
> There are more links to public info sites at the bottom of the page.
>=20
> You can add Apple and Microsoft to the list of usual suspects, but for =
state in NAT boxes rather than traffic. With happy eyeballs devices =
query both IPv4 and IPv6 so end up creating state in the NAT box even if =
the client ultimately chooses IPv6 for the connection. We have lots of =
devices that like to check with Apple whenever they wake up and the =
staff here use Microsoft Exchange in the cloud which is available via =
IPv6. I don=E2=80=99t have any verified data but I have noticed a =
relation between=20
>=20
> Scroll to the bottom of this page and you will see that my latency to =
Google via IPv6 dropped from 40 ms to 20 ms.=20
>=20
> http://mcnet.cc.ndsu.nodak.edu/smokeping/?target=3DInternet.Google_IPv6
>=20
>=20
> If I compare some days before and after the change I see a decrease in =
my peak NAT pool usage. However on other days I don=E2=80=99t see a =
difference. The theory is that after my latency dropped to 20 ms that =
should be less than the magical 25 ms for Apple devices to receive an =
answer via IPv6 so they don=E2=80=99t even send out an IPv4 query.
>=20
>=20
> https://www.ietf.org/mail-archive/web/v6ops/current/msg22455.html
>=20
> This link mentions that Microsoft is already preferring IPv6 over =
IPv4 95% of the time when both are available.
>=20
> http://labs.apnic.net/?p=3D657
>=20
> I=E2=80=99m 30 ms away from Facebook so 95% of Microsoft clients would =
use IPv6 but for Apple devices it=E2=80=99s a gamble. But it=E2=80=99s =
not clear if 95% of Microsoft clients would only send an IPv6 SYN and =
not send an IPv4 SYN (saving NAT table size).
>=20
> The top of our wish list would be for twitter and AWS to support IPv6, =
I think that those would make the biggest reduction in our NAT table =
size.
>=20
>=20
> If you hover your mouse over the US on this page
>=20
> http://6lab.cisco.com/stats/
>=20
> it lists 47% for content. What that 47% means is explained here.
>=20
> http://6lab.cisco.com/stats/information.php#content
>=20
>=20
> It is fun to play with the type of regression on this page and project =
730 days or so in the future.
>=20
> https://www.vyncke.org/ipv6status/project.php
>=20
>=20
>=20
>=20
> ---
> Bruce Curtis bruce.curtis@ndsu.edu
> Certified NetAnalyst II 701-231-8527
> North Dakota State University =20
>=20