1.
End of Life for IPv4 - Time for IPv6 Spring VON 2008 – Core Issues Track Thursday, March 20 09:00-10:15 Loki Jorgenson Chief Scientist

2.
Overview <ul><li>Network “climate change” </li></ul><ul><li>Three (sort of) easy pieces </li></ul><ul><li>Four stages to IPv6 Equivalence </li></ul><ul><li>Transition Plan </li></ul>

3.
No Critical Drivers <ul><li>Why do we need IPv6? </li></ul><ul><ul><li>Is it just about v4 depletion? </li></ul></ul><ul><li>There are no (obvious) killer apps that will benefit </li></ul><ul><ul><li>maybe mobile/nomadic </li></ul></ul><ul><ul><li>broadcast video </li></ul></ul><ul><ul><li>access to the rest of the world </li></ul></ul><ul><li>Climate change for the Internet </li></ul><ul><ul><li>The end of the Internet (as we know it) </li></ul></ul>

4.
Going IPv6 www.caida.org

5.
Three Easy Pieces <ul><li>Application level </li></ul><ul><li>Services level </li></ul><ul><li>Network level </li></ul><ul><li>Each has internal/private vs. external/public aspects </li></ul>

6.
IPv6 in the Network <ul><li>End-to-end IPv6 connectivity </li></ul><ul><li>LAN environment </li></ul><ul><ul><li>Dual stack network interfaces </li></ul></ul><ul><ul><li>Client-side tunnels </li></ul></ul><ul><li>Access to WAN/Internet </li></ul><ul><ul><li>VPN support </li></ul></ul><ul><ul><li>Mid-path tunnels </li></ul></ul><ul><li>Routing in the core and at the edge </li></ul>

7.
DFZ/TCAM Crisis bgp.potaroo.net

8.
IPv6 in Services <ul><li>Services required by end-hosts </li></ul><ul><ul><li>DHCP, NTP, NFS </li></ul></ul><ul><li>Services required for various applications </li></ul><ul><ul><li>DNS/BIND, QoS, FTP/SMTP/HTTP/XXXP </li></ul></ul><ul><li>Services required for network elements </li></ul><ul><ul><li>SNMP, BGP </li></ul></ul><ul><li>Services needed for security </li></ul><ul><ul><li>Firewalls, VPN, IPS/IDS, Web proxies, ACLs </li></ul></ul>

9.
IPv6 in Applications <ul><li>Servers, clients, and stand-alone </li></ul><ul><li>Operating system dependencies </li></ul><ul><li>Library and third-party dependencies </li></ul><ul><li>Implementation changes to handle mixed environment </li></ul>

10.
Today’s Problem Set <ul><li>Ex. Many essential products not fully IPv6 </li></ul><ul><li>Ex. Ping6 annoyance </li></ul><ul><li>Ex. NTP breaks with first packet lost </li></ul><ul><li>Ex. BIND stops working over IPv6 </li></ul><ul><li>Ex. OS maturity issues </li></ul><ul><li>Ex. Dead-end legacy </li></ul>http://tinyurl.com/33twxk (Internet2 Winter 2008 JT agenda) http://tinyurl.com/2vdukf ( NANOG 41 October 2007 plus more)

11.
Four Stages to IPv6 Equivalence <ul><li>Basic Connectivity </li></ul><ul><ul><li>make IPv6 packets flow e2e </li></ul></ul><ul><ul><li>most common hardware dual-stacked </li></ul></ul><ul><li>Security </li></ul><ul><ul><li>configure as secure as IPv4 </li></ul></ul><ul><ul><li>www.icann.org/committees/security/sac021.pdf </li></ul></ul><ul><li>IPv6 manageability </li></ul><ul><ul><li>double the views, configs, interactions… plus some </li></ul></ul><ul><li>Complete to IPv4 functional equivalence </li></ul><ul><ul><li>all the familiar bells and whistles </li></ul></ul>IPv4 == IPv6

12.
Steps in IPv6 Transition <ul><li>Develop IPv6 address allocation and routing plan </li></ul><ul><li>Enable on IPv6 across LAN, WLAN, and external/Internet </li></ul><ul><li>Implement internal network services in IPv6 (DNS, NTP, DHCP, SMTP) </li></ul><ul><li>Implement public network services in IPv6 (external DNS, MXs, internet web site) </li></ul><ul><li>Deploy network management infrastructure </li></ul><ul><li>Most workstations and servers are v6-enabled </li></ul><ul><li>“ Break” the IPv4 network by removing A records and exposing issues </li></ul><ul><li>Implement some regions of IPv6-only </li></ul><ul><li>Enable advanced features (remote and mobile) in IPv6 </li></ul><ul><li>Final cleanup and long tail of bug reports </li></ul>

13.
<ul><li>Thanks </li></ul><ul><li>Loki Jorgenson </li></ul><ul><li>[email_address] </li></ul><ul><li>www.apparentNetworks.com </li></ul>