1. Overall Outline Introduction to IPv6, Addressing & Routing ICMPv6 and Neighbour Discovery DNSSecurity QoS, Mobility Multicast, Transition OS and Platform support End-System Configuration

2. IPv6 Tutorial - Basics LAC NIC VII October 26, 2004 Wilfried Woeberwoeber@cc.univie.ac.at

3. Topics IPv6 vs. IPv4 IPv6 key features AddressingRouting

4. Whats wrong with IPv4 ? "address space exhaustion by 2005" !? -) billions of new devices, users -) 'always-on' – technologies difficult (re-)configuration sophisticated, structured header no integrated end-to-end security solution NAT is no longer adequate -) no 'called' services (e.g. IP-phones) -) performance, security, mgmt. issues

5. What can IPv6 do better ? 128 bit address 2 128 = 3.4x10 38 =340.282.366.920.938.463.463.374.607.431.768.211.456 comp. earth surface (in m 2 ) = 665.570.793.348.866.943.898.599 auto configuration / plug and play simple header (64 bit + 2x128 bit) mandatory end-to-end security (IPsec) renumbering & multihoming mobility features

6. Addressing 128 bit (64 for routing, 64 for interface ID) unicast, anycast, multicast addresses have scope and lifetime address autoconfiguration rules multiple addresses per interface easy renumbering, reconfiguration highly aggregatable initially only 15% assigned by IANA

7. Routing simplified header + extension header path MTU discovery in end systems simple source routing facilities

8. Routing router discovery ==> default gateway configuration for hosts no longer necessary ==> default gateway configuration for hosts no longer necessary prefix distribution to hosts by router(s) ==> network number (and mask) configuration for hosts no longer necessary ==> network number (and mask) configuration for hosts no longer necessary distributed prefixes do have a lifetime! support for renumbering (and multihoming) support for renumbering (and multihoming)

9. Routing Protocol Support IPV4 and IPv6 coexistence is easy in principle: no new routing architecture in principle: no new routing architecture ==> but no magical solution for multihoming ==> but no magical solution for multihoming routing protocols must be able to support different "address families" both for IGPs (e.g. OSPFv3) and EGPs (e.g. BGP4+) both for IGPs (e.g. OSPFv3) and EGPs (e.g. BGP4+) more or less a simple extensio of existing concepts to e.g. support multicast more or less a simple extensio of existing concepts to e.g. support multicast Needs a bit more memory Needs a bit more memory