Jorgenson Loki
Upcoming SlideShare
Loading in...5

Jorgenson Loki






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Who we are – why we are involved Kudos to Internet2 20 seconds

Jorgenson Loki Jorgenson Loki Presentation Transcript

  • 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
  • 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
  • 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
  • IPv6 in Services
    • Services required by end-hosts
      • DHCP, NTP, NFS
    • Services required for various applications
    • 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 (Internet2 Winter 2008 JT agenda) ( NANOG 41 October 2007 plus more)
  • Four Stages to IPv6 Equivalence
    • Basic Connectivity
      • make IPv6 packets flow e2e
      • most common hardware dual-stacked
    • Security
      • configure as secure as IPv4
    • IPv6 manageability
      • double the views, configs, interactions… plus some
    • Complete to IPv4 functional equivalence
      • all the familiar bells and whistles
    IPv4 == IPv6
  • Steps in IPv6 Transition
    • Develop IPv6 address allocation and routing plan
    • Enable on IPv6 across LAN, WLAN, and external/Internet
    • Implement internal network services in IPv6 (DNS, NTP, DHCP, SMTP)
    • Implement public network services in IPv6 (external DNS, MXs, internet web site)
    • Deploy network management infrastructure
    • Most workstations and servers are v6-enabled
    • “ Break” the IPv4 network by removing A records and exposing issues
    • Implement some regions of IPv6-only
    • Enable advanced features (remote and mobile) in IPv6
    • Final cleanup and long tail of bug reports
    • Thanks
    • Loki Jorgenson
    • [email_address]