jorgenson loki
DESCRIPTION
TRANSCRIPT
End of Life for IPv4 -Time for IPv6
End of Life for IPv4 -Time for IPv6
Loki JorgensonChief Scientist
Spring VON 2008 – Core Issues TrackThursday, March 20 09:00-10:15
Overview Network “climate change”
Three (sort of) easy pieces
Four stages to IPv6 Equivalence
Transition Plan
No Critical Drivers Why do we need IPv6?
Is it just about v4 depletion?
There are no (obvious) killer apps that will benefit maybe mobile/nomadic broadcast video access to the rest of the world
Climate change for the Internet The end of the Internet (as we know it)
Going IPv6
www.caida.org
Three Easy Pieces Application level
Services level
Network level
Each has internal/private vs. external/public aspects
IPv6 in the Network End-to-end IPv6
connectivity
LAN environment Dual stack network interfaces Client-side tunnels
Access to WAN/Internet VPN support Mid-path tunnels
Routing in the core and at the edge
DFZ/TCAM Crisis
bgp.potaroo.net
IPv6 in Services Services required by end-hosts
DHCP, NTP, NFS
Services required for various applications DNS/BIND, QoS, FTP/SMTP/HTTP/XXXP
Services required for network elements SNMP, BGP
Services needed for security Firewalls, VPN, IPS/IDS, Web proxies, ACLs
IPv6 in Applications Servers, clients, and stand-alone
Operating system dependencies
Library and third-party dependencies
Implementation changes to handle mixed environment
Today’s Problem Set Ex. Many essential products not fully IPv6
Ex. Ping6 annoyance
Ex. NTP breaks with first packet lost
Ex. BIND stops working over IPv6
Ex. OS maturity issues
Ex. Dead-end legacy
http://tinyurl.com/33twxk (Internet2 Winter 2008 JT agenda)http://tinyurl.com/2vdukf (NANOG 41 October 2007 plus more)
Four Stages to IPv6 Equivalence
1. Basic Connectivity make IPv6 packets flow e2e most common hardware dual-stacked
2. Security configure as secure as IPv4 www.icann.org/committees/security/sac021.pdf
3. IPv6 manageability double the views, configs, interactions… plus some
4. Complete to IPv4 functional equivalence all the familiar bells and whistles
IPv4 == IPv6
Steps in IPv6 Transition1. Develop IPv6 address allocation and routing plan2. Enable on IPv6 across LAN, WLAN, and
external/Internet3. Implement internal network services in IPv6
(DNS, NTP, DHCP, SMTP) 4. Implement public network services in IPv6
(external DNS, MXs, internet web site) 5. Deploy network management infrastructure 6. Most workstations and servers are v6-enabled 7. “Break” the IPv4 network by removing A records and
exposing issues8. Implement some regions of IPv6-only9. Enable advanced features (remote and mobile) in IPv610. Final cleanup and long tail of bug reports
