tailieunhanh - ADM389 IPv6

Make a (brief) case for IPv6 (level 200) Give you a crash-course on the main aspects of the protocol (level 300) Explain the available technology support including migration strategies (level 300) | ADM389 IPv6 Rafal Lukawiecki rafal@ Strategic Consultant Project Botticelli Ltd in association with Objectives Make a (brief) case for IPv6 (level 200) Give you a crash-course on the main aspects of the protocol (level 300) Explain the available technology support including migration strategies (level 300) Why IPv6? IP Address Allocation History 1981 - IPv4 protocol published 1985 ~ 1/16 of total space 1990 ~ 1/8 of total space 1995 ~ 1/3 of total space 2000 ~ 1/2 of total space ~ 2/3 of total space This despite increasingly intense conservation efforts: PPP / DHCP address sharing NAT (network address translation) CIDR (classless inter-domain routing) plus some address reclamation Theoretical limit of 32-bit space: ~4 billion devices Practical limit of 32-bit space: ~250 million devices (RFC 3194) Running Out of Addresses Even if every company used only 1 address by fully utilising NATs (Network Address . | ADM389 IPv6 Rafal Lukawiecki rafal@ Strategic Consultant Project Botticelli Ltd in association with Objectives Make a (brief) case for IPv6 (level 200) Give you a crash-course on the main aspects of the protocol (level 300) Explain the available technology support including migration strategies (level 300) Why IPv6? IP Address Allocation History 1981 - IPv4 protocol published 1985 ~ 1/16 of total space 1990 ~ 1/8 of total space 1995 ~ 1/3 of total space 2000 ~ 1/2 of total space ~ 2/3 of total space This despite increasingly intense conservation efforts: PPP / DHCP address sharing NAT (network address translation) CIDR (classless inter-domain routing) plus some address reclamation Theoretical limit of 32-bit space: ~4 billion devices Practical limit of 32-bit space: ~250 million devices (RFC 3194) Running Out of Addresses Even if every company used only 1 address by fully utilising NATs (Network Address Translation) we would be out of addresses in the next 3-5 years “Slower that Y2K problem, but a surer one” More IPv4 Pain Argh, NATs Peer-to-peer is difficult NAT security record is dubious Management is a pain Security is an optional add-on QoS (Quality of Service) is rare and not real-time Routing tables too large and process slow Mobility is a pain But peer-to-peer mobility is the future of Internet Device autoconfiguration is rare DHCP & address ownership does not work across organisational boundaries Using external agents for autoconfiguration is a non-starter US versus ROW US accounts for 90% of address allocation Some universities in US have more allocated addresses than the whole of Asia The so-called, in US, “Rest of the World” is hardly an even partner Reliance on American organisations may be politically difficult, at times, for large or governmental Internet projects Gives US an unwelcome monopoly power 6 Benefits of IPv6 Address depletion solved International misallocation .