1. Jan Žorž SAFNOG2 - Swaziland Mobile broadband and IPv6 in Slovenia 1 jan@go6.si

2. Jan Žorž IPv6 on web sites 2

3. Jan Žorž IPv6 on web sites 3

4. Jan Žorž IPv6 on web sites 4

5. Jan Žorž IPv6 traffic to Google 5

6. Jan Žorž IPv6 traffic to Google 6

7. Jan Žorž Behind the curtains: All major ISPs are doing customer trials Mobile operators testing 464XLAT and are currently happy… Maybe going “dual stack by default” in 2015 There is a strong Slovenian NOG community building up 10 th Slo IPv6 summit in June 2015 Let’s see, maybe there are some surprises 7

8. Jan Žorž Cooperation work: Go6 as a catalyst Disclaimer: IPv6 in Slovenia is being promoted by the Go6 institute, this is an industry body (important mesagge here: self regulation can work!!!) and here is one of our succes stories. Go6 as an IPv6 catalyst got 2 mobile operators together deploying IPv6 on 3GPP at the same time and here is how they did it. 8

9. Jan Žorž Tušmobil - 2a02:840::/32AS41828 9

10. Jan Žorž Tušmobil - 2a02:840::/32AS41828 IMAP login log record: Mar 5 12:07:47 go6lab dovecot: imap- login: Login: user=, method=PLAIN, rip=2a02:840:beef:4c::2, lip=2a02:e8:0:1::babe:face, TLS SMTP log record (sending mail): Mar 5 12:18:32 go6lab postfix/smtpd[24374]: 4AB9F2378666: client=unknown[2a02:840:beef:47::2], sasl_method=LOGIN, sasl_username=jan 10

11. Jan Žorž Tušmobil - 2a02:840::/32AS41828 11

12. Jan Žorž Tušmobil - 2a02:840::/32AS41828 Versions of software used: SGSN NSN, SG6 GGSN NSN, FlexiISN v 3.2 CD7 Firewall Cisco ASA v7.2 DNS64 totd 1.5.1 NAT64 ecdysis-nf-nat64-20100226 @gentoo 2.6.3 Mobile Nokia e52 12

13. Jan Žorž Mobitel - 2a02:e20::/32AS29276 13

14. Jan Žorž Mobitel and IPv6........ Packet core is IPv6 ready IPv6 only PDP context o IPv4 and IPv6 in same PDP context not supported jet 6VPE over MBICORE o Static routing Terminals Each terminal gets /64 Problems with IPv6 PPP and DNS o Manual config Limited terminal support o Nokia E and N series  OK o Window mobile 6.1  No support o Data cards  Natively no support 14

15. Jan Žorž Mobitel - 2a02:e20::/32AS29276 Versions of software used: SGSN Ericsson Mk IV 2008B Dual Access GGSN Ericsson/Juniper J120 2009A MPLS Cisco 7609 Version 12.2(33)SRC2 15

16. Jan Žorž Simobil network Test IPv6 enabled APN was fully functional in December 2011 Dual-stacked (IPv4 and IPv6 PDP connections possible) Cisco GGSN will support PDPv4v6 in Q1 2012 16

17. Jan Žorž Simobil network 17

18. Jan Žorž Simobil network 18

19. Jan Žorž Simobil network 19

20. Jan Žorž Simobil network 20

21. Jan Žorž Simobil network 21

22. Jan Žorž Simobil network Two PDP contexts also works in parallel PDPv4 and PDPv6. 22

23. Jan Žorž Nokia was ahead with IPv6 on mobile devices (21M-02) 23

24. Jan Žorž Samsung Galaxy Nexus (Android 4) - IPv6 on 3G capable 24

25. Jan Žorž Recommended reading – RFC 6459 25

26. Jan Žorž DSMIP6-TLS 26

27. Jan Žorž 464XLAT Defined in RFC6877 Combines stateless and statefull NAT64/NAT46 NAT64 prefix-discovery with querying ipv4only.arpa Deployed and used by T-Mobile USA, Verizon, etc… Implemented and on-by-default from Android 4.4 and up … 27

28. Jan Žorž 464XLAT 28

29. Jan Žorž 464XLAT 29

30. Jan Žorž 464XLAT This “hack” fixes that remaining 15% of applications on mobile phones that uses just legacy IP protocol More than 10 million happy customers of T- Mobile USA is on IPv6 only PDP context It’s in Android 4.4 and 5.x, enabled by default – use it. 30

31. About removing the next IPv6 deployment speed-bumps IPv6 Troubleshooting for Helpdesks using isp.test-ipv6.com document Jan Žorž

32. About Me – A Quick History Name: Jan Žorž Founder of Slovenian Go6 Institute Worked in Internet operations for 20+ years 16 years of IPv6 experience Active and contributing member of RIPE and IETF communities Primary co-author of RIPE-501/RIPE-554 IPv6 procurement BCP document and RIPE-631 Co-author of RFC 6346 (A+P approach to IPv4 depletion) Joined Internet Society DO team in December 2012

33. Walls-of-text warning Despite long contemplations on how to make this slide- pack without walls-of-text – we could not find any better way how to tell our story. We apologize for any inconvenience. Please, bear with us anyway…

34. Misconceptions and reality ;) Disclaimer: This document is *not* an ISOC document. This is a product of a group of a brilliant experts from the community (list with names comes later in the slide pack). I just happen to be the initiator and one of the editors of the document I would like to thanks ISOC for dedicating some of my working time to run this effort.

35. Removing one of the next IPv6 speedbumps One of the first speed-bumps was addressed by RIPE-554 Next speed-bump is lack of IPv6 knowledge at ISP helpdesks

36. IT helpdesk staff can be… difficult sometimes

37. Removing one of the next IPv6 speedbumps Title: “IPv6 Troubleshooting for Residential ISP Helpdesks (Using test-ipv6.com)” Contributors and authors: Lee Howard (Time Warner Cable), John Jason Brzozowski (Comcast), David Freedman (ClaraNET), Jason Fesler (Yahoo!), Tim Chown (University of Southampton), Sander Steffann (SJM Steffann), Chris Grundemann (ISOC), Jen Linkova (Google), Chris Tuska (Comcast), Daniel Breuer (Comcast), Jan Žorž (ISOC)

38. Tools used? Fact 1.: We need to build a short and simple set of detect/explain/action scenarios that would help people at help desks identify and fix the issue Fact 2.: We need a simple online tool to detect the state of connectivity on the users computer Fact 3.: Test-ipv6.com is a very useful tool that detects the state of connectivity on the users computer So the idea emerged to bring Jason Fesler in the group and talk him into creating a special version of the tool meant specially for ISP helpdesks

39. Tools used?

40. Table of content 1. What is a BCOP? 2. Summary 3. Background / History 4. Using This Document - Note for Helpdesk Managers 5. IPv6 Troubleshooting 5.1 Basic IPv6 Test 5.2 Test Connectivity 5.3 Test DNS 5.4 Check Home Router 5.5 Escalate 6. Explanation of Help Desk Codes on http://isp.test- ipv6.com 112 - IPv4, plus Broken IPv6 4 - IPv4 only 4t - IPv4 plus Teredo 46 - IPv4 + IPv6 46t - Dual Stack, Possible Tunnel 624 - 6to4 64 - NAT64

41. Table of content 64t - NAT64, possible tunnel “slow” “mtu” - “Possible MTU issues” Warning “Site(s) with failed connectivity” Warning 7. IPv6 training for helpdesk 8. Conclusion 9. Operator’s specifics Appendix A: Acknowledgements Appendix B. Basic troubleshooting flowchart Appendix C. Collecting Data for Escalation

42. Example: one of the possible generic situations Help desk code: 624 6to4 IPv4: Good, AS65536, CableCo IPv6: Good, 6to4, Preferred IPv4 address: 192.0.2.1 IPv6 address: 2001:db8::1

43. Example (continued): Interpretation: “6to4” was used to provide an IPv6 address; and the host was configured to actively take advantage of this service. Any web site that has an IPv6 presence, will be reached using 6to4 instead of native IPv4. Modern operating systems do not prefer these kinds of tunnels by default. Be aware that the user might have a very old operating system or a non-default configuration. Action: 1. Have the user disable any automatic tunneling mechanisms that are active. 6to4 is a protocol that tries to get IPv6 traffic through a public relay, using IPv4 to reach the public relay. Public 6to4 relays offer no SLA; and published studies show approximately 15% failure rates. Windows: Disable tunnel interfaces using http://support.microsoft.com/kb/929852 (for example, Microsoft Fix it 50412).

44. Example (Action continued): 2. If IPv6 is desired, configure IPv6 (verify the user has an IPv6 address, and a default route). and test again. If user is still experiencing access issues, follow the troubleshooting steps for the corresponding code returned by http://isp.test- ipv6.com/

45. Example (hardest and longest one): 112 - IPv4, plus Broken IPv6 Help desk code: 112 IPv4: Good, AS65536, CableCo IPv6: broken IPv4 address: 192.0.2.1

46. Example (hardest and longest one): Interpretation: IPv6 network connectivity somewhere between the user and the website is broken. IPv6 connections are timing out instead of succeeding (or failing fast to IPv4). The user experience visiting major web sites may be suffering, and some applications completely failing. Assumption: User has already power cycled home router, modem, and device, as part of your standard troubleshooting procedure. Action: 1. Determine whether IPv6 is offered to this customer, based on company documentation. If yes, continue to the next step. 2. …

47. Status and future work? Document is now an official RIPE BCOP document – RIPE- 631 Done in RIPE BCOP TF and subsequently to RIPE IPv6 WG Join the mailing lists and contribute to discussion: RIPE BCOP TF: https://www.ripe.net/mailman/listinfo/bcophttps://www.ripe.net/mailman/listinfo/bcop RIPE IPv6 WG ML: http://www.ripe.net/mailman/listinfo/ipv6-wg/http://www.ripe.net/mailman/listinfo/ipv6-wg/ Issues/comments/ideas tracker URL:https://git.steffann.nl/go6/ipv6- troubleshooting-for-helpdesks/issueshttps://git.steffann.nl/go6/ipv6- troubleshooting-for-helpdesks/issues https://www.ripe.net/ripe/docs/ripe-631

49. Very quick reminder: What’s a BCOP? Best Current Operational Practice A living document describing the best operational practices currently agreed on by subject matter experts Vetted and periodically reviewed by the global network engineering community (GNEC)

50. Quick facts in case you are interested: BCOP activity around the world http://www.internetsociety.org/deploy360/about/bcop/ Africa region: A BCOP group was started under AfNOG, lead by Douglas Onyango and Fiona Asonga Asia: BCOP Task Force started at JANOG, co-chaired by Seiichi Kawamura and Yoshinobu Matsuzaki, NZNOG BCOP starting up, lead by Dean Pemberton BoF at Apricot lately… Europe: RIPE BCOP Task Force created, co-chaired by Benno Overeider and Jan Žorž Latin America: A BCOP Task Force was started under LACNOG, lead by Luis Balbinot and Pedro R Torres Jr. North America: NANOG BCOP Committee established, lead by Aaron Hughes and Chris Grundemann

51. Q&A Thank you! Comments/Questions? mailto: