• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
IPv6 /48 Filtering
 

IPv6 /48 Filtering

on

  • 643 views

Presentation given by Bert Wijnen at: TREX Workshop 2012, Tempere, Finland, 14 September 2012

Presentation given by Bert Wijnen at: TREX Workshop 2012, Tempere, Finland, 14 September 2012

Statistics

Views

Total Views
643
Views on SlideShare
617
Embed Views
26

Actions

Likes
0
Downloads
1
Comments
0

1 Embed 26

http://www.ripe.net 26

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    IPv6 /48 Filtering IPv6 /48 Filtering Presentation Transcript

    • IPv6 /48 FilteringAs Seen by RIPE Atlas Bert Wijnen bwijnen@ripe.net (presenter) Emile Aben emile.aben@ripe.net RIPE NCC TREX workshop 2012 14 September 2012
    • Route Filtering (1)• IPv4: Up to /24 considered routable• IPv6: ??• RIPE-532: – “It is suggested that prefix filters allow for prudent subdivision of an IPv6 allocation. The operator community will ultimately decide what degree of subdivision is supportable, but the majority of ISPs accept prefixes up to a length of /48 within PA space.”TREX workshop 2012, Bert Wijnen, 14 September 2012 2
    • Route Filtering (2)• Recent discussion on ipv6-ops mailing list when a /48 out of PA space without covering prefix was used• So what’s the community currently deciding? – Are /48s filtered? – /48s out of IPv6 PA space?TREX workshop 2012, Bert Wijnen, 14 September 2012 3
    • Measure Data-Plane with RIPE Atlas• 700+ IPv6 enabled RIPE Atlas probes that can measure this• traceroute6 for 2 hours – /32 PA – /48 PI – naked /48 out-of-PATREX workshop 2012, Bert Wijnen, 14 September 2012 4
    • Results (2012-09-07) target failTarget is in: fail reached with !N/32 PA space 4 1 575(ipv6.google.com) (0.7%) (0.2%)/48 PI space 3 1 578(ns.ripe.net) (0.5%) (0.2%)/48 out of PA space * 12 4 569(cloudflare.com) (2.1%) (0.7%)/48 out of PA space 9 6 568(www.rtl.de) (1.6%) (1.0%) * this network has a covering /12TREX workshop 2012, Bert Wijnen, 14 September 2012 5
    • Conclusion• We see around 1-2% of RIPE Atlas probes that can’t traceroute6 to a /48-out-of-PA space• We don’t know how representative RIPE Atlas is for the IPv6 Internet at large – Guess: People/operators that care/think about the network are more likely to have a probe and are also the people that make a conscious decision about filtering this or not.TREX workshop 2012, Bert Wijnen, 14 September 2012 6
    • Follow Up• This work was (is being) done by Emile Aben• He is scheduled to discuss it more at the upcoming RIPE 65 Meeting in Amsterdam• Probably in the Routing WG session• Questions to: emile.aben@ripe.netTREX workshop 2012, Bert Wijnen, 14 September 2012 7
    • Questions?