1 / 25

IPv6 Transition for Curacao

IPv6 Transition for Curacao. IPv6 event– 9 th October 2012. Content. IPv4 exhaustion Government role Operator role Priority issues Government: set the example Private Sector Conclusions Consultation questions. IPv4 exhaustion (1/3). Source: www.potaroo.net/tools/ipv4/index.html.

aaronanderson
Download Presentation

IPv6 Transition for Curacao

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPv6 Transition for Curacao IPv6 event– 9th October 2012

  2. Content • IPv4 exhaustion • Government role • Operator role • Priority issues • Government: set the example • Private Sector • Conclusions • Consultation questions

  3. IPv4 exhaustion (1/3) Source: www.potaroo.net/tools/ipv4/index.html

  4. IPv4 exhaustion (2/3) Source: www.lacnic.net/en/registro/espacio-disponible-ipv4.html

  5. IPv4 exhaustion (3/3) • ITU IPv6 website presents the following estimates in June 2012 September 2012 early October 2012 Source: www.itu.int/net/ITU-T/ipv6/

  6. Example IPv6 plan: US Source: Planning Guide Roadmap toward IPv6 adoption in USG, May 2009

  7. Government Role • Create awareness on Curacao • Organise this seminar • Assessment of IPv6 readiness of the Telco’s • Provide IPv6 information to users with substantial ICT networks • Trigger/accelerate the IPv6 migration process at the operators • Set the example • Accelerate IPv6 deployment

  8. Operator Role: Introduction of IPv6 and migration of IPv4 to IPv6 (1/3) Recommended steps: November 2012 • Assign an official to lead and coordinate IPv6 deployment by the Operator • Complete an inventory of existing routers, switches, and hardware firewalls • Begin an inventory of all other existing IP compliant devices and technologies • Begin impact analysis to determine the deployment cost and the operational impacts and risks of migrating to IPv6 and offering IPv6 services parallel to the existing IPv4 services

  9. Operator Role: Introduction of IPv6 and migration of IPv4 to IPv6 (2/3) March 2013 • Complete inventory of existing IP compliant devices and technologies not captured in first inventory, and • Provide the completed plan for IPv6 deployment and IPv6 service introduction in 2013 June 2013, at the latest • The Operator should be offering initial IPv6 connectivity and services for their broadband access portfolio. This includes both dual-stack (IPv4 and IPv6) users and IPv6 only users

  10. Operator Role: Introduction of IPv6 and migration of IPv4 to IPv6 (3/3) October 2013 • All Internet facing services and websites must be using and supporting IPv6

  11. Priority issues • ccTLD of Curacao (.an/.cw) should provide full IPv6 capability and DNS servers should have access to IPv6 Internet connectivity • CAR-IX IPv6 peering should be taken into service to allow IPv6 peering and access to major IPv6 capable content providers such as Google and Akamai • Dual-stack IPv4/IPv6 connectivity should be provided in backbones and for connectivity to major users • All ICT procurements should take IPv6 capability into consideration

  12. Gov. IPv6 Implementation (1/2) • US: target 100% of citizen facing Government websites should be dual stack by September 30th 2012 Result: about 30% achieved the target but take up accelerates Source: http://usgv6-deploymon.antd.nist.gov/cgi-bin/generate-gov

  13. Gov. IPv6 Implementation (2/2) • Australia: citizen facing Government websites/services should be 100% IPv6 by the target date end of December 2012 Result: on-going though delays are anticipated • Netherlands: Digitale Agenda NL, at the latest by 2013 all Government websites and email should be IPv6 reachable • Belgium: June 2012 the cabinet decided that Government should be IPv6 capable before mid 2014. Priority will be given to citizen facing websites/services • Etc. Source: http://usgv6-deploymon.antd.nist.gov/cgi-bin/generate-gov

  14. Government: Set the example (1/4) Recommended steps: November 2012 • Assign an official to lead and coordinate agency planning • Complete an inventory of existing routers, switches, and hardware firewalls • Begin an inventory of all other existing IP compliant devices and technologies • Begin impact analysis to determine the deployment cost and the operational impacts and risks of migrating to IPv6

  15. Government: Set the example (2/4) March 2013 • Complete inventory of existing IP compliant devices and technologies not captured in first inventory, and • Complete impact analysis of deployment costs and operational impacts and risks. • Provide the completed IPv6 deployment and migration plan

  16. Government: Set the example (3/4) June 2013 • All Departments and Agency infrastructures (network backbones) must be using and supporting IPv6. Agencies will include progress reports on meeting this target date as part of their IPv6 transition strategy October 2013 • At least 50% of all Internet facing services and websites must be using and supporting IPv6

  17. Government: Set the example (4/4) January 2014 • 100% of all Internet facing services and websites must be using and supporting IPv6 • The Government services should be fully available in IPv6, allowing for new Internet users connected solely by IPv6

  18. Private sector: Introduction of IPv6 and migration of IPv4 to IPv6 • Specify IPv6 capability in all purchases of ICT equipment and services • Acquire IPv6 numbers • Start a trial to gain experience with IPv6 • Use dual stack capable (IPv4/IPv6) servers • Upgrade the applications to dual stack, starting with websites, firewalls and network management • Upgrade company IP network between locations • Connect to IPv6 IP Transit/Internet connectivity: • Use a dual stack ISP • Tunnel (IPv6 over IPv4 tunnel) into a public IPv6 provider if the current ISP does not (yet) offer IPv6 capability. • Migrate end-users to IPv6. NAT functionality might still be required to reach external IPv4 applications/websites.

  19. Conclusions • Timely introduction of IPv6 is of critical importance for Curacao to sustain full connectivity to the global Internet and to remain competitive as an economy • Relatively early introduction of IPv6 could provide Curacao with a competitive edge in the region • Timely introduction of IPv6 allows for a gradual migration and reduces the overall cost • Waiting until the last moment when the lack of IPv4 addresses is causing real problems is likely to be far more costly and would disadvantage Curacao’s economy and people • Actions are required from all stakeholders: Government, Operators and Private sector

  20. IPv6 Consultation Questions IPv6 event– 9th October 2012

  21. IPv6 Consultation Questions (1/5) Question 1: • What would be the impact for your company/organisation if no new IPv4 numbers would be available anymore? • How long would your current IPv4 number allocation be sufficient to run your company/organisation? • When would your company/organisation require additional IP address space from a Regional Internet Registry, RIR, (mostly LACNIC for Curacao but possibly ARIN for North America and RIPE for Europe)? Question 2: • Is your company/organisation already using IPv6? • If yes, please elaborate on the current status of IPv6 deployment in your company/organisation. • If no, is there a plan to introduce IPv6 in the near future? • Which dependencies are critical for your IPv6 introduction?

  22. IPv6 Consultation Questions (2/5) Question 3: • Are your websites (and other on-line services) ready to accommodate IPv6 only users (for example an IPv4/IPv6 dual-stack website)? • How would your company/organisation be affected if an increasing number of world-wide IPv6-only users would not be able to reach your websites (and other on-line services) anymore? Question 4: • Do you have an IPv6 capable Internet connection? • If yes, how did you realise an IPv6 internet connection? • If no, are there any plans to get an IPv6 capable Internet connection in the near future?

  23. IPv6 Consultation Questions (3/5) Question 5: • When do you expect to provide IPv6 capability on your main external websites (and/or other on-line services)? • When do you expect your internal network to be IPv6 capable? • When do you expect to be able to use IPv6 towards IPv6 only websites/services? Question 6: • Would you consider buying IPv4 numbers on a “secondary market” just to avoid or delay IPv6? • If yes, could you elaborate why you would prefer to buy “secondary” IPv4 numbers instead of introducing IPv6?

  24. IPv6 Consultation Questions (4/5) Question 7: • Is the IPv6 readiness of the .an/.cw ccTLD DNS an issue for your company/organisation? • If yes, please elaborate Question 8: • Do you anticipate difficulties or barriers to migrate to IPv6? • If yes, please elaborate. Question 9: • How long would it take to migrate your company/organisation to IPv6?

  25. IPv6 Consultation Questions (5/5) Question 10: • Do you anticipate any specific security concerns when introducing IPv6? • If yes, what measures do you anticipate to resolve any security concerns? Question 11: • Is your company/organisation planning any new services requiring IPv6? • If yes, please elaborate. Question 12: • Which dependencies are critical for your IPv6 introduction?

More Related