1. Securing Future Growth: Getting Ready for IPv6 NOW! ccTLD Workshop, 8 th April 2011 Noumea, New Caledonia Miwa Fujii, Senior IPv6 Program Specialist, APNIC

2. Overview APNIC and APNIC IPv6 Program IPv4 addresses exhaustion and need to adopt IPv6 Multi-Stakeholder approach TLDs, Registrars, Domain name users (Content providers) Working together with the domain name registries and registrars How can we work together?

3. APNIC and IPv6 Program Regional Internet Registries (RIR) Asia Pacific Network Information Centre (APNIC) Open membership-based industry bodies Non-profit, neutral, and independent Internet resource allocation, registration and other services such as training, supporting infrastructure, community cooperation APNIC IPv6 Program To support the Industry to transit to IPv6 To outreach Internet multi-stakeholders

4. Growth of the Internet http://news.netcraft.com/archives/2009/04/06/april_2009_web_server_survey.html 205 million websites as of July 2010 (Netcraft)

5. IPv4 addresses exhaustion and need to adopt IPv6 3 Feb 2011 Number Resource Organization (NRO) announced the free pool of available IPv4 addresses is now fully depleted The free pool of available IPv4 addresses at APNIC will exhaust around May 2011 Need to deploy IPv6 IANA APNIC ARINRIPELACNICAfriNIC

6. Global announcements and press conference by ICANN and NRO 6 http://www.apnic.net/publications/news/2011/final-five http://www.apnic.net/publications/news/2011/webcast

7. IPv4 Consumption: Projection 7 IANA IPv4 free pool exhausted: 01/02/2011 Projected RIR exhaustion: 21/04/2011 http://www.potaroo.net/tools/ipv4/index.html Mar /2011

8. APNIC IPv4 Availability (/8) 8 http://www.apnic.net/community/ipv4-exhaustion/graphical-information

9. APNIC IPv4 Availability (/8) 9 http://www.apnic.net/community/ipv4-exhaustion/graphical-information It shows the daily total of available IPv4 addresses, expressed in terms of /8s. The total will decrease and increase according to APNIC allocations to networks and resource returns. When APNIC only has a total of one /8 left, the final /8 policy will be triggered. It shows the daily total of available IPv4 addresses, expressed in terms of /8s. The total will decrease and increase according to APNIC allocations to networks and resource returns. When APNIC only has a total of one /8 left, the final /8 policy will be triggered.

10. IPv4 exhaustion planning Appropriate policies/procedures applied at different stage 10 We are here now

11. APNIC IPv4 address management policy changes IPv4 policy during Stages 1 and 2 Address policy remains the same until APNIC reaches the final /8 IPv4 policy during Stage 3 To extend the life of APNIC’s last /8, each organization can only receive a limited size from it Current policy: limited to a single /22 Policy refinement being discussed 11

12. When will APNIC’s final /8 be exhausted? APNIC IPv4 address management policy 9.10 Distribution of the final /8 worth of space in the unallocated APNIC IPv4 address pool http://www.apnic.net/policy/add-manage-policy#9.10 A total of around 16,000 small slices that can be given out from this final /8. Currently, APNIC has around 3000 account holders. A membership growth rate of 300 new accounts during the past year. Given these variables, it will take a number of years to allocate all addresses from this final /8. And of course, IPv6 is available! 12 http://www.apnic.net/community/ipv4-exhaustion/ipv4-exhaustion-details

13. Impact of IPv4 address exhaustions Immediate impact ISPs will no longer be able to obtain IPv4 addresses from APNIC Survive for a short time of period with their own pool Business continuity of ISPs and other Internet multi- stakeholders is in question Need to find alternative source for IPv4 addresses No sustainable alternative options Prolonged impact Difficulties to maintain sustainable Internet growth No more new entries to the Internet market place Impediment of further technological development IPv6 is the only option we have now

14. IPv6 Readiness at ccTLDs 150 ccTLDs name servers out of 253 (listed in IANA Roort zone database including gTLDs etc.) have IPv6 address resolution function (around 60%) Statistics provided by National Centre for High- Performance Computing in Taiwan, as of March 2010 15 gTLD out of 21 gTLD name servers have IPv6 address resolution function (70%) IPv6 readiness of direct customers of TLDs and registrars? http://www.ipdn.tw/DomainNameResources/RegistccTLDDNwwwServiceRatio

15. What ccTLDs need to do? Ability to accept AAAA records for their domain name servers - glue records Name resolution over IPv6 Adapt DNS software applications allow: Adapting domain name resolution with IPv6 Accepting incoming connections (both UDP and TCP as appropriate) over IPv6 Network infrastructure ready for IPv6 transport: Router configuration, firewall and IPv6 transit etc. Ability to access administrative tools web, WHOIS, EPP, etc. over IPv6 http://portalipv6.lacnic.net/en/ipv6/ipv6/cctld/ipv6-cctlds

16. IPv6 Readiness of IPv6 glue records within ccTLDs Registered domains with AAAA records http://bgp.he.net/ipv6-progress-report.cgi

17. IPv6 Readiness of Direct Customers of ccTLDs Registered domains with AAAA records http://bgp.he.net/ipv6-progress-report.cgi We can assume: Direct customers of TLDs and registrars need to accelerate IPv6 transition. How can you/we help them to make a smooth transition to IPv6? What kinds of messages will help them?

18. IPv6 Readiness of Registrars People and organizations connecting to the Internet after mid 2011: Will find difficulty in obtaining IPv4 global addresses: It could be more expensive It may require more complicated technical adjustments to penetrate multiple NATs IDNs and new TLDs will push for more IPv4 addresses They may choose an option to use IPv6 only websites Are registrars ready for such challenges? How can you/we support them in transitioning to IPv6?

19. Customers will choose Registrars http://www.webhostingtalk.com/showthread.php?t=921661

20. Customers will move to IPv6- Ready Services http://blog.mudy.info/tag/ipv6/

21. Customers will move to IPv6- Ready Services http://blog.mudy.info/tag/ipv6/

22. Major content providers also need to be ready with IPv6 Major content providers News media Online banking Online shopping site E-Government site Enterprise web site School web site Etc.

23. If an online shopping site is ready with IPv4 and IPv6… 23 IPv4 address only IPv4 and IPv6 address IPv6 address only

24. If an online shopping site is ready with IPv4 and IPv6… 24 IPv4 address only IPv4 and IPv6 address All customers can do online shopping IPv6 address only

25. If a site is not ready for IPv6… 25

26. If a site is not ready for IPv6… 26 Users with IPv6 address only

27. Mobile devices and smart phones!! 27 Users with IPv6 address only

28. If a site is not ready for IPv6… 28 Customers will move to elsewhere… Need to transit to IPv6!

29. What can we do to support IPv6 transition? Reach out to registrars, content providers including enterprises i.e., customers of TLDs and registrants APNIC’s message will be: IPv6 is a reality and a business continuity issue Your web, mail and other servers need to be ready with IPv6 Simple process Easy access to IPv6 with APNIC Like IPv4 Multihoming, enterprises need IPv6 Multihoming as well

30. IPv6 Kickstart

31. Useful information for busy people APNIC ICONS IPv6 web page http://icons.apnic.net/display/IPv6/Home

32. IPv6 address assignment for critical infrastructure APNIC IPv6 policy has been ready: IPv6 address assignment for critical infrastructure networks http://www.apnic.net/policy/ipv6-address- policy#5.9.3http://www.apnic.net/policy/ipv6-address- policy#5.9.3 global top level domain (gTLD) nameservers; country code TLD (ccTLDs) nameservers;

33. Working with ccTLDs Encourage registrars to prepare their services for IPv6 What kind of information will be helpful for registrars? What kind of information will be helpful for customers of registrars? Will also help direct customers of gTLDs How can we reach out to them systematically? How can we use our limited resources more effectively? We appreciate your input!

34. Thank You!