IPv6 Deployment & Strategy

Transcription

1 Irish IPv6 Task Force IPv6 Deployment & Strategy

2 Irish IPv6 Task Force IPv6 Training Slide-sets 1. The Bigger Picture: Why is IPv6 so Important? 2. Introduction to IPv6 Fundamentals (technical) 3. IPv6 Deployment & Strategy (technical) <- This slide set is third in a series 4. The Business Case for IPv6 5. Mobile IPv6 (technical) 6. IPv6 Quality of Service (technical) 7. IPv6 Security (technical)

3 Presentation Structure Introduction How do I deploy IPv6? Transition mechanisms Connectivity & addressing Existing Deployments: How has it been done already? Use cases Sample deployments Getting it right Services, networks and staff Protecting your investment

4 Introduction

5 Introduction You ve read all about IPv6, but how should you go about deploying it? It s more than updating your software and hardware; it s updating people s knowledge, too. Plan carefully ask for IPv6 support from your suppliers now, even if you don t have a short term need for it, and this should save you costs in the long term.

6 How do I deploy IPv6?

7 How should I deploy IPv6? Have IPv4 network, want IPv6 network Problems IPv4 only hardware; software & people Solutions Transition mechanisms; staff training, future proofing new hardware & software purchases

8 Transition Mechanisms Short Term Tunnelling: IPv6 over IPv4, over UDP, 6to4 etc. Proxies: Someone speaks IPv6 on your behalf Medium Term Dual-Stack: Run IPv4 and IPv6 side by side Long Term Will networking in the future use only IPv6?

9 Short Term: Tunnelling 1. Contact your Internet Service Provider (ISP) Ask for IPv6 connectivity and a test subnet 2. Contact a Free Tunnel provider such as SixXS ( ) Provides connectivity for single hosts & networks Given a /64 subnet 3. Use automatic 6to4, Teredo tunnels to provide IPv4 users with immediate IPv6 connectivity

10 Medium Term: Dual Stack Getting IPv6 Addresses of your own Different to IPv4. Instead of applying to your Regional Internet Registry (i.e. RIPE, ARIN, APNIC) directly, address blocks are allocated by your ISP. Most ISPs will offer you a minimum /48 network. That s more than (2 16) subnets! You can get a larger allocation if your two year deployment plan can justify it (as per current allocation rules from RIPE).

11 Devising an Addressing Plan More concerned with functional address allocation than conserving IPv6 address space. Don t think of addressing plans in IPv4 terms Minimum network assignment recommended is a /64. This is to facilitate auto configured addressing And to allow for the growth of subnets without needing further address allocations Remember that the first address on every subnet is reserved (e.g. 2001:db8:100::0/64)

12 Devising an Addressing Plan for your Network Leave room for network expansion for future review. This should avoid non-contiguous network block assignment and the need to renumber networks. Use a spreadsheet or database to track allocations. List subnets, where/whom they were assigned to and when they were assigned.

13 Addressing Plan Guidelines Allocated 2001:db8:100::/48 This means that the first 48 bits (the first three colon s worth) of the address are fixed and you have the remaining 80 bits to use. Assign a /64 address block per network - i.e. per department; school; section etc. Leave the next 7 * /64 subnets free for future expansion. Keep records up to date to track properly (spreadsheet, database or reverse DNS)

14 Addressing Plan Example Customer Allocations 2001:0DB8:0000::/40 D X Prefix Allocation Allocated :0DB8:0000::/48 reserved :0DB8:0001::/48 reserved :0DB8:0002::/48 reserved :0DB8:0003::/48 reserved :0DB8:0004::/48 reserved :0DB8:0005::/48 reserved :0DB8:0006::/48 reserved :0DB8:0007::/48 reserved :0DB8:0008::/48 Customer 1 09-Nov :0DB8:0009::/48 reserved 10 A 2001:0DB8:000A::/48 reserved 11 B 2001:0DB8:000B::/48 reserved 12 C 2001:0DB8:000C::/48 reserved 13 D 2001:0DB8:000D::/48 reserved 14 E 2001:0DB8:000E::/48 reserved 15 F 2001:0DB8:000F::/48 reserved :0DB8:0010::/48 Customer 2 09-Nov :0DB8:0011::/48 reserved :0DB8:0012::/48 reserved :0DB8:0013::/48 reserved :0DB8:0014::/48 reserved :0DB8:0015::/48 reserved :0DB8:0016::/48 reserved :0DB8:0017::/48 reserved :0DB8:0018::/48 Customer 3 17-Nov-01

15 Addressing your Hosts Auto configuration is the most popular choice. Also may have manual configuration and DHCPv6. Should you use different addressing methods for user desktops & servers?

16 Numbering Desktops Use Auto configuration & DNS for easy numbering of user desktop machines. Might be large overhead in maintaining reverse DNS records if lots of users Use DHCPv6 Assign different subnets for each VLAN, and use a corresponding address. i.e. 2001:DB8:201::/48 is for machines in VLAN 201

17 Numbering Servers Usually a good idea to have an easily remembered address for reaching servers in case DNS breaks. Use hexadecimal version of IPv4 address to fill the lowest 32bits and pad the higher 32bits with zeros. e.g. 2001:db8:100::c101:c105 Use port number of main service on the server e.g A name server so host address ends in ::53 Use increasing low numbers and pad the rest with zeros e.g. 2001:db8:100::1, 2001:db8:100::2 etc.

18 Existing Deployments How has it been done already?

19 Use cases Let's cover some use cases: Single machine in IPv4-only land Single network similarly isolated Full dual-stacked network with native connectivity

20 Single machine This is a good way to get to grips with IPv6 Usual dual stacking procedure applies: 1. Enable support in the Operating System If necessary; MS Vista & Debian Linux IPv6 is enabled by default 2. Enable some sort of 6-over-4 connection 3. Enable the applications We will concentrate here on connectivity.

21 Single machine Use one of the transition mechanisms to arrange connectivity Dual stack your machine outbound connections use IPv6 2001:db8:1:: Add a AAAA (quad A) record to your DNS inbound connections use IPv6

22 Single machine Pros Suitable for your first deployment to get to grips. Cons Doesn't scale to multiple machines. 2001:db8:1::

23 Single network + tunnel Your IPv6 router doesn't need to be the same as your IPv4 router it can even be a PC! Again, start with some sort of tunnel. A configured tunnel gives best persistence

24

25 Single network + tunnel Pros Good initial deployment, without major initial investment. Can migrate to single dual-stacked topology over time Cons Effectively gives you two separate network topologies to manage.

26 Native Dual Stacked All your equipment and services support IPv6. IPv4 and IPv6 on your router, and your ISP transit connection(s). Management systems, servers, and clients dual stacked.

27 Native dual stacked Pros Single topology to manage IPv4 and IPv6 *should* have equal capability Requires quite some preparation, so may begin with an earlier use case

28 Getting it right

29 Ancillary services There is, of course, more to a network than the network itself: Network management systems, NOC & helpdesk staff, Customers and users.

30 Network management If you're not monitoring a service, you don't have a service. Updating management kit can be harder than upgrading the network itself.

31 Staff training Engineers get very scared by IPv6 Almost as scared as they get by multicast! It's unknown, therefore it's troublesome Integrate as far as possible into procedures In all the documents Part of internal/external training Get people used to it Strategy: involve all staff in the migration toward the "oh, it's just like IPv4!" moment

32 Future Proofing Purchases Important in both Hardware & Software Even if you don t plan on deploying IPv6 as a production service in the short term, insist on the functionality now. It will save you money in the long term! If IPv6 is not supported currently: Ask for a timeline for deployment Impose penalties if not delivered (in Tender documents, Service Level Agreements etc.)

33 Protect your investment This should not be an expensive migration Capital cost can be 0! providing you roll it in with scheduled renewal Prepare earlier than you need to deploy Understand what your needs may be, not just what they are now Equipment is often bought for a >5 year lifetime Avoid kit which will delay your future deployment

34 Summary Preparing a strategy for deploying IPv6 is something that should happen today, even if you don t have immediate plans to implement. Deployment is more than just updating hardware and software on network equipment and PCs. It s updating applications, business processes and staff knowledge, too. Start with a small test network and a tunnel and build from there.

35 Acknowledgements This presentation includes some material from these other sources:??????

36 Contact Mícheál Ó Foghlú Research Director Telecommunications Software & Systems Group Waterford Institute of Technology Cork Road Waterford Ireland (w) (Personal Blog)

37 Further Information Web Sites: National Irish IPv6 Centre Irish IPv6 Task Force IPv6 eprints Server (Public Documents) IPv6 Dissemination (Public Training) Individual Documents/Presentations: (Iljitsch van Beijnum, 7th March 2007) (Geoff Huston APNIC, 2006) Vision_2010_v 6.pdf (IPv6 Forum Roadmap & Vision, 2006) 06_Advancing_Information_Sharing_And_Data_Architecture/IPV6/NIST%20ipv6-doc-eaiv4% ppt (Doug Montgomery NIST, 2005)

38 Further Information Websites: sol/ipv6dswp.htm Books: IPv6 Network Administration by Niall Richard Murphy and David Malone (O Reilly), ISBN Deploying IPv6 Networks by Ciprian P. Popoviciu, Eric Levy- Abegnoli and Patrick Grossetete (Cisco Press), ISBN DNS & BIND by Paul Albitz and Cricket Liu (O Reilly), ISBN

39 Thank you! This presentation has been shared under the Creative Commons Attribution 2.0 UK: England & Wales Licence ( by the Irish IPv6 Task Force ( Please acknowledge this source if you use it for free or for profit