1. Developments on the campus

4. What’s changing then? SURFnet - We make innovation work3 -No more IPv4 addresses!!!! POLL At your organization: Who has (more than) enough IPv4 addresses so it does not have to worry about IPv6 yet?

5. SURFnet - We make innovation work4 Remember: It takes two to tango!

7. What’s the Business Case? SURFnet - We make innovation work6 -Growth in IP-enabled devices: soon IPv6-only devices on the internet, examples: -Growing markets (Asia, Africa) IPv6 only. Customers? -Mobile networks, IPv6 only -Sensor networks (internet of things). Researchers? -Desktop clients: It’s there already! Threat for ongoing operations? Do you want to do this overnight? -IPv6 is a total new network roll-out! Impact on: numbering, routing, security (acl/firewall), redundancy, load balancers, monitoring, trouble shooting, server/desktop maintenance, processes… Do you want to do this overnight?

8. But, hold on… Should we drive towards IPv4 & IPv6 native or V4/V6 with NAT and tunneling, tech tricks

9. Continuity as driver for IPv6

10. Categorizing the “IPv6 problem” -Implementing IPv6 on (campus) infrastructures is complex -SURFnet is trying to aid/guide/support connected institutes to enable IPv6 on their campus infrastructures. But how? -We defined six categories: 1)Business case 2)Routing 3)Security 4)Numbering 5)Applications and licenses 6)Transition (adoption-phase) SURFnet - We make innovation work9

11. First steps we took SURFnet - We make innovation work10 -Organize creative session for campusinfra managers and technicians -Main idea: NO sending from SURFnet (what to send after 10 yrs?)! Except from Create Mind- setting -12 creative sessions with moderators (sold-out!). -Goal of each session: Provide a top 3 list: what do you agree to achieve? How do you divide the work and who becomes a group leader. -Results within ½ year -Highly Appreciated

12. Examples of gathered Requirements SURFnet - We make innovation work11 -How Can I -Convince management about deployment?  Calculations about early & late “rush” deployment  Build cost templates and business plans -Log MAC-IPv6 combination in case of stateless addresses?  Research possibilities of external logging of router  Capturing and parsing DAD packets - Organize my network numbering?  Gather current best practices

13. The Results 1) Business Case SURFnet - We make innovation work12 Document: Opportunities Risks for continuity Timing Impact Analysis Costs CAPEX/OPEX excel template available  OK as a start, must be developed further.

14. 2) Numbering SURFnet - We make innovation work13 -Numbering plan for IPv6 is not obvious -Helps you think about deployment further -Numberplan-howto-document (in English): www.surfnet.nl/ipv6 www.ripe.netwww.ripe.net (training material/ipv6)  8000 downloads first week, many happy twitters: A much needed piece of document! This is a very useful document, and a prerequisite for IP address management, IPAM, efforts. With all IPv6 nodes getting a public address, and no hiding behind a NAT, it is important to understand IPv6 addressing well. Brilliant manual/guideline! Excellent doc. MUST-READ ASAP on practical #IPv6 deployment RT @RIPE_NCC #IPv6 Addressing Plan Manual

15. 3) Adoption/transition SURFnet - We make innovation work14 -Case study and generalized document how to implement IPv6 (configuring end stations, static configuration, DHCP, -DNS, NAT techniques (and all the problems ;-), Security, identification of end users, test setup). Available in English on http://www.surfnet.nl/ipv6http://www.surfnet.nl/ipv6

16. Configure IP addresses and DNS resolvers: messy! SURFnet - We make innovation work15

17. 3) Adoption/transition (2) SURFnet - We make innovation work16 -Template of a transition plan (Current situation and inventory scan, roadmap, risk analysis, impact scan etcetera)  Not very detailed yet -Starting with On-site support -3 rd party helps institutes to: -Quick Scan of the current situation (hardware,software) -Make a plan, determine the impact -Provide technical hands-on - Five institutes started in last six months with on-site support

18. Preliminary results of on-site support SURFnet - We make innovation work17 -Each institute has unique problems for adopting V6. Technical, Organizational, Functional. Common steps to take are: -Set a target, make a master plan -Transition should be one step a time. No big bang. -Perform a Compliancy Scan and evaluate -Start with external part (outside services & routing) -Gradually plan for internal infrastructure. Native or temporary tunneled -Coexisting IPv4 and IPv6 -Evaluate often  Looks “standard”. Thus, is it manageable?

19. Developments in the other areas SURFnet - We make innovation work18 Applications: -Institutes worry about applications and licenses (ip-based). Demand for a list of ‘ipv6-ready’ applications -Seminar with Cisco, Juniper en L5-networks: what’s cooking? No-show from software developers Security: -Application/hardware specific challenges -SURFnet policy: No anonymous access Routing: - Hardware and protocol specific issues

20. What’s next? SURFnet - We make innovation work19 Work out documents continuing on-site support Continue to educate World IPv6 day, also in Amsterdam http://www.ipv6day.nl

21. Conclusion -IPv6 is not a technology push but customer driven. Have to keep that in mind. -When IPv6-only addresses start to emerge (or are threating to…) -Thus: 2011+ is the right time! -Gather your customers to determine needs -Involve suppliers -Keep an eye on the customer for pace -Deliver tailored support: provide value! SURFnet - We make innovation work20

22. SURFnet - We make innovation work21 Maurice van den Akker Maurice.vandenAkker@surfnet.nl www.surfnet.nl Presentation released under Creative Commons http://creativecommons.org/licenses/by/3.0/ Dekuji vám mnohokrát