IPv6 Update: Where are we now?

bhutanNOG 4 5-9 June 2017, Thimphu, Bhutan Tashi Phuntsho

tashi@apnic.net

IPv6 adoption statistics by Google

https://www.google.com/intl/en/ipv6/statistics.html

Top 1000 websites IPv6

http://www.worldipv6launch.org/measurements/

End user readiness: APNIC Labs

31 May 2017: 11.09%

60% increase in last 12 months!

https://stats.labs.apnic.net/ipv6/

IPv6 capable & preferred

•  Uses advertisement to load measurement script (HTML5/flash) on user’s browser

•  Script fetches three invisible pixels –  One using IPv4 only URL –  One using IPv6 only URL –  One with either protocols (dual-stack URL)

•  If: –  Fetches the IPv6 URLs (only or dual-stack) over IPv6, device

is deemed IPv6 capable –  Fetches the dual-stack URL using IPv6, its deemed to prefer

IPv6 (happy eyeballs bias?) •  Only Chrome (Firefox and Opera parallel; OS X and iOS – 25ms)

IPv6 economy (Asia) table

https://stats.labs.apnic.net/ipv6/

Bhutan (top 10) IPv6 samples ASN AS Name IPv6 Capable IPv6

Preferred #

Samples AS17660 DRUKNET-AS 0.26% 0.26% 41514 AS38740 TASHICELL-AS 0.74% 0.71% 16275

0

5

10

15

20

25

2014

-01

2014

-03

2014

-05

2014

-07

2014

-09

2014

-11

2015

-01

2015

-03

2015

-05

2015

-07

2015

-09

2015

-11

2016

-01

2016

-03

2016

-05

2016

-07

2016

-09

2016

-11

2017

-01

2017

-03

2017

-05

% IP

v6 C

apab

le

17660 38740

Bhutan IPv6 – delegated & routed

ORG/AS Delegated prefix Routed DRUKNET (17660) 2405:d000::/32 YES TASHICELL (38740) 2405:ec00::/32 YES DCS (132232) 2403:8700::/32 YES NANO (136039) 2400:50c0::/32 YES MoIC (135666) 2400:1440::/32 YES DrukREN (134715) 2403:580::/32 NO ThimphuIX 2001:deb:8000::/48 NO

South Asia, India, Reliance Jio

0

20

40

60

80

100 20

13-1

0 20

14-0

1 20

14-0

4 20

14-0

7 20

14-1

0 20

15-0

1 20

15-0

4 20

15-0

7 20

15-1

0 20

16-0

1 20

16-0

4 20

16-0

7 20

16-1

0 20

17-0

1 20

17-0

4

% IP

v6 C

apab

le

South Asia IN 55836

IPv6 Performance •  Enough data collected to analyze IPv6 performance •  APNIC’s Chief Scientist, Geoff Huston’s study

–  @APRICOT2016 (Feb 2016)

•  Is IPv6 as robust as IPv4? –  Do all TCP connection attempts succeed?

•  Connection failure = no ACK for an acknowledged SYN

–  IPv4 connection failure sits at 0.2% –  IPv6 connection failure sits at 1.8% (8 times higher!)

•  PMTUD (ICMPv6 filters)?

IPv6 Performance •  Enough data collected to analyze IPv6 performance •  APNIC’s Chief Scientist, Geoff Huston’s study

–  @APRICOT2016 (Feb 2016)

•  Is IPv6 as fast as IPv4? (IPv6 unicast) –  Comparison of RTT (e2e)

•  Time since SYN till ACK (factors out any congestion issues)

–  IPv6 is faster about half of the time •  36-90ms faster •  NAT? IPv4 and IPv6 using different paths (different peering policies for

IPv4 and IPv6)? –  IPv6 as fast as IPv4

IPv6 Performance •  Some good use cases •  LinkedIn Senior Director of Infrastructure Engineering, Zaid

Ali Kahn –  @APRICOT42 (September 2016)

•  IPv6 at LinkedIn: –  For some select networks in Europe, LinkedIn is seeing up

to 40% performance improvements over IPv6, and in the US, up to 10%

–  TCP timeout on IPv4 over mobile carrier networks is as high as 4.6% and IPv6 timeouts are on a much lower side at 1.6% •  CG-NAT configuration (TCP translation timeouts)?

https://blog.apnic.net/2016/05/13/linkedin-ipv6-measurements/

Asymmetric routing & performance

Industry trend: Who is in control?

http://gs.statcounter.com/platform-market-share/desktop-mobile-tablet

Mobile devices make up to 52% of all visible

devices

•  Mobile is driving the internet •  However, born and raised on NAT!

–  Still heavily based on CG-NAT (NAT44)

•  The true driver for IPv6 adoption is mobile internet!

Industry trend: Who is in control?

IPv6 in Mobile Networks: Technology

Carrier Economy Deployment Reliance Jio India Dual stack in 2016 SK Telecom Korea 464XLAT in 2014 Telstra Australia 464XLAT since 2016 T-Mobile USA 464XLAT in 2012 Verizon Wireless USA Dual stack in 2011

IPv6 in Mobile Networks: Deployment

Dual-stack in mobile network

•  Does not solve IPv4 (public) depletion issue –  Still need to use CG-NAT to access IPv4-only sites

•  But effective, and the only viable and scalable way forward –  IPv6 native access to most of the major content providers –  None of the scalability issues of v4 CG-NAT –  And of course, no DNSSEC issues

IPv6 and Mobile devices

•  Android supports 464XLAT (4.4) •  IPv6 supported over Mobile since iOS 9 (supported

IPv6 on WiFi for a long time!) –  All apps submitted to App Store must support IPv6 since

early 2016 –  https://developer.apple.com/news

•  DHCPv6: –  iOS, Android, Windows –  https://en.wikipedia.org/wiki/

Comparison_of_IPv6_support_in_operating_systems

IPv6 Tethering

•  RFC6653:DHCPv6-PD for Mobile Networks –  3GPP Release10

•  RFC7278: Extending IPv6 /64 prefix from Mobile interface to LAN –  “Flaky” support since Android 6.0 (Marshmallow) –  Stop-gap until DHCP-PD

www.apnic.net/ipv6

Thank You!END OF SESSION