6watch gauging the global rollout of ipv6 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
6Watch: Gauging the Global Rollout of IPv6 PowerPoint Presentation
Download Presentation
6Watch: Gauging the Global Rollout of IPv6

Loading in 2 Seconds...

play fullscreen
1 / 17

6Watch: Gauging the Global Rollout of IPv6 - PowerPoint PPT Presentation


  • 71 Views
  • Uploaded on

6Watch: Gauging the Global Rollout of IPv6. Dan Massey Dave Meyer Lixia Zhang Colorado State U . Oregon UCLA. Some Background. The global IPv4 address pool, managed by IANA, is exhausted. The regional registries still have some space left, but time is running out.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about '6Watch: Gauging the Global Rollout of IPv6' - denim


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
6watch gauging the global rollout of ipv6
6Watch:Gauging the Global Rollout of IPv6

Dan Massey Dave Meyer LixiaZhang

Colorado State U. Oregon UCLA

6Watch Project

some background
Some Background
  • The global IPv4 address pool, managed by IANA, is exhausted.
  • The regional registries still have some space left, but time is running out.

6Watch Project

ipv6 solves the problem
IPv6 Solves The Problem
  • IPv6 uses 128-bit addresses.
  • v6-compatible hosts need to communicate across and to the v4 network.
    • Dual-stack
    • 6to4
    • Teredo
  • But global v6 deployment still lagging
    • And North America is behind the curve

6Watch Project

underlying routeviews data
Underlying RouteViews Data
  • RouteViews Part of 6Watch Team
  • Source of Raw Data
    • IPv4 and IPv6
    • 10+ Years of global data
  • Data Cited by Everyone,
    • Hundreds of cites
    • Every major networking conference

This funding is essential to RouteViews operations.

RouteViews is essential to global research and operations.

6Watch Project

global or region reachability
Global or Region Reachability
  • Cumulative Routes and Current Routes Differ
    • 25K cumulative compared to 7K current
    • Do different ISPs see different tables?
  • Tracked Prefixes withReachability Differences
    • At least one peer
    • At least one day
  • Compare Tables With Hurricane Electric
    • Claim HE is close to “center” of IPv6

6Watch Project

comparing routeviews tables
Comparing RouteViews Tables
  • Track Number of Identical Prefixes
    • Most (5.9K out of 7K) prefixes visible everywhere

6Watch Project

the unreachable prefixes
The Unreachable Prefixes
  • Many Transient Events
    • But others persist
  • Differences Due to More Specific Routes
    • Doesn’t reflect reachability at control plane, 6spider checking data plane…
  • Remainder are unreachable address space

6Watch Project

unreachability heatmap
UnreachabilityHeatmap
  • Grouped by RIR
    • ARIN (169), RIPE (195), LACNIC (39), APNIC (26), AfriNIC (2)
    • 6to4 + Teredo on right
  • Surprising Results
    • Ipv4 transition sites are in the problem set
    • ARIN (North America) 2nd largest contributor to problem set

6Watch Project

looking forward
Looking Forward
  • Complete data plane monitoring implementation
  • Correlate control plane with data plane to provide a comprehensive overview of IPv6 deployment
  • Working on diagnosis

6watch@lists.cs.ucla.edu

6Watch Project

the 6watch team
The 6Watch Team

6Watch Project

6to4 and teredo reachability
6to4 and TeredoReachability
  • Both prefixes showed up all 20 days
    • 6to4 (2002::/16)
    • Teredo (2001::/32)
  • Unreachable by two peers
    • Both from the same AS
    • Not a significant reachability issue
    • Possibly a (mis)configuration issue

6Watch Project

is geography to blame
Is Geography To Blame?
  • Very little geographical bias
    • Except for LACNIC
  • ARIN and RIPE had the most reachability holes
    • Also have the largest v6 allocations
    • Generally not considered deployment leaders
  • APAN (Japanese ISP)
    • Most reachability holes
    • Smallest RIB table

6Watch Project