17
10/6/11 6Watch Project 1 6Watch: Gauging the Global Rollout of IPv6 Dan Massey Dave Meyer Lixia Zhang Colorado State U. Oregon UCLA

6Watch: Gauging the Global Rollout of IPv6

  • Upload
    denim

  • View
    24

  • Download
    0

Embed Size (px)

DESCRIPTION

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. - PowerPoint PPT Presentation

Citation preview

Page 1: 6Watch: Gauging  the Global Rollout of IPv6

10/6/11 6Watch Project 1

6Watch: Gauging the Global Rollout of IPv6

Dan Massey Dave Meyer Lixia ZhangColorado State U. Oregon UCLA

Page 2: 6Watch: Gauging  the Global Rollout of IPv6

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.

10/6/11 26Watch Project

Page 3: 6Watch: Gauging  the Global Rollout of IPv6

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

10/6/11 36Watch Project

Page 4: 6Watch: Gauging  the Global Rollout of IPv6

410/6/11 6Watch Project

Page 5: 6Watch: Gauging  the Global Rollout of IPv6

510/6/11 6Watch Project

But only 7K in the current table!

Page 6: 6Watch: Gauging  the Global Rollout of IPv6

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

10/6/11 66Watch Project

This funding is essential to RouteViews operations.RouteViews is essential to global research and operations.

Page 7: 6Watch: Gauging  the Global Rollout of IPv6

Global or Region Reachability Cumulative Routes and Current Routes Differ

25K cumulative compared to 7K current Do different ISPs see different tables?

Tracked Prefixes with Reachability Differences At least one peer At least one day

Compare Tables With Hurricane Electric Claim HE is close to “center” of IPv6

10/6/11 76Watch Project

Page 8: 6Watch: Gauging  the Global Rollout of IPv6

Comparing RouteViews Tables

10/6/11 86Watch Project

Track Number of Identical Prefixes Most (5.9K out of 7K) prefixes visible everywhere

Page 9: 6Watch: Gauging  the Global Rollout of IPv6

The Unreachable Prefixes

10/6/11 96Watch Project

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

Page 10: 6Watch: Gauging  the Global Rollout of IPv6

Unreachability Heatmap 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

10/6/11 106Watch Project

Page 11: 6Watch: Gauging  the Global Rollout of IPv6

11

Looking Forward• Complete data plane monitoring implementation• Correlate control plane with data plane to provide

a comprehensive overview of IPv6 deployment• Working on diagnosis

10/6/11

[email protected]

6Watch Project

Page 12: 6Watch: Gauging  the Global Rollout of IPv6

12

The 6Watch Team

10/6/11 6Watch Project

Page 13: 6Watch: Gauging  the Global Rollout of IPv6

13

Additional Information

10/6/11 6Watch Project

Page 14: 6Watch: Gauging  the Global Rollout of IPv6

What Shows US is Behind?Why Pick HE As the Center?

10/6/11 146Watch Project

Page 15: 6Watch: Gauging  the Global Rollout of IPv6

Some More Detail on An EyeP Entry

10/6/11 6Watch Project

Page 16: 6Watch: Gauging  the Global Rollout of IPv6

6to4 and Teredo Reachability

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

10/6/11 166Watch Project

Page 17: 6Watch: Gauging  the Global Rollout of IPv6

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

10/6/11 176Watch Project