1 / 5

World IPv6 Day Call to Arms

World IPv6 Day Call to Arms. d raft-chown-v6ops-call-to-arms-01 Tim Chown tjc@ecs.soton.ac.uk. Aims. Raise awareness of the June 8 th World IPv6 Day Seek to capture:

ivrit
Télécharger la présentation

World IPv6 Day Call to Arms

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. World IPv6 Day Call to Arms draft-chown-v6ops-call-to-arms-01 Tim Chown tjc@ecs.soton.ac.uk

  2. Aims • Raise awareness of the June 8th World IPv6 Day • Seek to capture: • common causes of connectivity and performance issues, focusing on things an end-site can influence, with suggested actions/measures • methods to measure and monitor IPv6 traffic, to allow analysis of traffic behaviour on the day • Produce a final ‘guide’ well in advance of the IPv6 Day • Though the advice may have longer-term benefits • Measurement tools could be left in place • Currently also includes some info on IPv6-only draft-chown-v6ops-call-to-arms-01

  3. Issues • Currently cited (in no particular order): • Unmanaged tunnels (6to4 relays, proto41 filters,…) • Tunnel broker first-hop • Connection timeouts (failover to/from IPv4/IPv6) • PMTU discovery • Rogue router advertisements (inc. IPv4-only networks) • Tunnel performance (under higher load) • AAAA record advertised but service not enabled • Filtering – impact of drop vs unreachable draft-chown-v6ops-call-to-arms-01

  4. Measurement • Sites may enable clients, servers, or both • What could be captured on the day: • IPv6 traffic levels • Flow records • Application brokenness/preference • Reachability to IPv4-only/dual-stack/IPv6-only • PMTUD brokenness • IPv4/IPv6 performance comparison • Security monitoring (e.g. RAmond, NDPmon) draft-chown-v6ops-call-to-arms-01

  5. Next steps • Is this useful? • If so, solicit more feedback on the issues and measurement methods suggested • Raise awareness of the text • Harden well in advance of June 8th • Perhaps useful advice longer-term • Q: Should we influence the experiment? • e.g. fix PMTUD problems or just use 1280? • Deploy local 6to4 relays, or discourage 6to4? draft-chown-v6ops-call-to-arms-01

More Related