1 / 13

IPv6 future plan discussion

IPv6 future plan discussion. Xavier Jeannin (CNRS) on behalf IPv6 SA2 team Etienne Dublé, Mario Reale, Marian Zurek (ETICS) Xavier.Jeannin@urec.cnrs.it EGEE SA2 – IPv6 task EGEE08 - Istanbul – September 23 rd , 2008. IPv4 address space depletion. Geoff Huston APNIC Sept. 2007.

xiomara-lamorena
Download Presentation

IPv6 future plan discussion

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 future plan discussion Xavier Jeannin (CNRS) on behalf IPv6 SA2 team Etienne Dublé, Mario Reale, Marian Zurek (ETICS) Xavier.Jeannin@urec.cnrs.it EGEE SA2 – IPv6 task EGEE08 - Istanbul – September 23rd, 2008

  2. IPv4 address space depletion • Geoff Huston • APNIC • Sept. 2007 With the courtesy of Bernard Tuy SA2: IPv6 - EGEE 08 Istanbul

  3. ICANN resolution On the Deployment of IPv6 Whereas, the unallocated pool of IPv4 address space held by IANA and the Regional Internet Registries is projected to be fully distributed within a few years; Whereas, the future growth of the Internet therefore increasingly depends on the availability and timely deployment of IPv6; Whereas, the ICANN Board and community agree with the call to action from the Address Supporting Organization and the Number Resource Organization, Regional Internet Registries, the Government Advisory Committee, and others, to participate in raising awareness of this situation and promoting solutions; The Board expresses its confidence in the Internet community to meet this challenge to its future prospects, and expresses its confidence in the bottom-up, inclusive, stakeholder-driven processes in place to provide any needed policy changes, and; The Board further resolves to work with the Regional Internet Registries and other stakeholders to promote education and outreach, with the goal of supporting the future growth of the Internet by encouraging the timely deployment of IPv6. http://www.icann.org/minutes/resolutions-29jun07.htm#n EGEE’07 conference – 2007-10-01, Budapest (HU)

  4. From emergency to IPv6 • IPv6 is already there … • Internet v6 is there today : • NRENs in EU, North America, Asia … are interconnected in IPv6 • Lots of IXP are offering IPv6 connectivity • ISPs and Telcos exchange IPv6 routes • Almost all operating system are IPv6 compliant • Then the question is not “if” but “when” and “how” … SA2: IPv6 - EGEE 08 Istanbul

  5. Why IPv6 now? • IPv6 deployment will speed up in the remaining years: • Contact with China/India/Africa • Grid interoperability (COS, Naregi) • Being non IPv6 compliant will be seen as a blocking factor for large scale new software deployment. • Only 3 years remaining before IPv6 will become mandatory! SA2: IPv6 - EGEE 08 Istanbul

  6. Future work of SA2 A comprehensive report on IPv6 programming language ( in C/C++, JAVA, Perl, Python) A report on the local usage (to the machine) of non IPv6 component like MySQL  ( local socket instead of TCP/IP connection) Specific deep test for important external modules Python/ZSI, Perl/SOAP::Lite, PostgreSQL Unknown IPv6 status packages to be tested? New version of BDII Submit bugs for non IPv6 compliant packages Finalize the LD_PRELOAD based IPv6 checker 6 SA2: IPv6 - EGEE 08 Istanbul

  7. how organize the project collaboration on IPv6 The outcome of this activity strongly depends on the effectiveness our collaboration  Organize a joint task between SA2 and JRA1 JRA1 contribution  is fundamental/crucial to provide new IPv6 compliant gLite components Organize a joint task between SA2 and SA3 without the validation process  no IPv6 gLite distribution Joint task with ETICS (testing and building) is already set up SA1, node installation and configuration? 7 SA2: IPv6 - EGEE 08 Istanbul

  8. What SA2 can provide to you? Two testbeds in (Paris/Rome) with almost all the type of gLite nodes to test the interplay between different nodes Automated test of the interplay: ETICS Specific test gLite dependencies External dependencies Assessment of IPv6 compliance of external modules Deep test for important external modules: Grid-FTP … Internal dependencies Code checker /Dynamic checker Wiki to unify all relative information about IPv6 compliance Support for the IPv6 setting up in the developers site in order to allow them to test IPv6 presentation and tutorial activities 8 SA2: IPv6 - EGEE 08 Istanbul

  9. General project issues on IPv6 Porting a code on IPv6 is an easy process David Smith port a large component DPM-LFC in 2 weeks (Dec 2007) SA2 success also to port BDII quickly (Feb 2007) Java support IPv6 without any code update It seems that having a IPv6 compliance could be achieved in the scope of EGEE-III  • Which would be the best approach to move the gLite code to IPv6 compliance?         • Which would be the strategy for non compliant externals components?     9 SA2: IPv6 - EGEE 08 Istanbul

  10. SA2-JRA1 Collaboration A roadmap toward IPv6 Working group on IPv6 Next candidate component that could be ported on IPv6 How SA2 could provide support Support for the IPv6 setting up the developers site in order to allow them to test IPv6 Testbed: test the interplay with other nodes What for of access/usage suits the developers best External dependencies Assessment of IPv6 compliance of external module Deep test for important external modules: Grid-FTP An official list A unique JRA1 interlocutor for SA2? IPv6 presentation and tutorial activities All-Hands Meeting of JRA1? 10 SA2: IPv6 - EGEE 08 Istanbul

  11. SA2-SA3 Collaboration Support to deploy IPv6 within SA3 testbed How IPv6 can be included in the SA3 testbed? Include SA2 machines in SA3 testbed IPv6 communication between SA2 testbed and SA3 testbed (CERN): tunnel A unique SA3 interlocutor for SA2? 11 SA2: IPv6 - EGEE 08 Istanbul

  12. Thank you. SA2: IPv6 - EGEE 08 Istanbul

  13. Reference Links • https://twiki.cern.ch/twiki/bin/view/EGEE/IPv6FollowUp (under construction) References • RFC 1933 Transition Mechanisms for IPv6 Hosts and Routers • RFC 3493 basic socket interface extensions for IPv6 • RFC 4038 Application aspects of IPv6 transition Programming guidelines on transition to IPv6, Miguel Castro • IPv6 network programming jun-ichiro itojun hagino • IPv4-Mapped Addresses on the Wire Considered Harmful draft-itojun-v6ops-v4mapped-harmful-02.txt jun-ichiro itojun hagino • Guidelines for IP version independence in GGF specification T Chown • IPv6 Guide for Windows Sockets Applications [Winsock] http://msdn2.microsoft.com/en-us/library/ms738649.aspx • IPv6 Théorie et pratique Gisèle Cizault • IPv6 Transition/Co-existence Security Considerations draft-ietf-v6ops-security-overview-06.txt P Savola • Status for Java Developers Kit API for IPv6 IPV6_WG J. Bound • Networking IPv6 User Guide for JDK/JRE 5.0 Sun • UNIX Network Programming W. Richard Stevens • Programming guidelines on transition to IPv6 T. P de Miguel, E. M. Castro JRA1 All Hands Meeting – 2007-10-24, CERN

More Related