1 / 6

Using Only Link-Local Address in Network Core draft- behringer - lla -only-00

Using Only Link-Local Address in Network Core draft- behringer - lla -only-00. 83 rd IETF , 26-30 Mar 2012 V6OPS WG Michael Behringer Eric Vyncke. Summary. We propose to use only IPv6 link-local addresses on infrastructure links wherever possible.

aren
Download Presentation

Using Only Link-Local Address in Network Core draft- behringer - lla -only-00

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. Using Only Link-Local Address in Network Coredraft-behringer-lla-only-00 83rdIETF, 26-30 Mar 2012 V6OPSWG Michael Behringer Eric Vyncke

  2. Summary • We propose to use only IPv6 link-local addresses on infrastructure links wherever possible. • We discusses advantages and disadvantages • Goal: Help in decision process. • Desired outcome: BCP

  3. Approach • No global nor ULA addresses on infrastructure links • Just link local • Proven to work Routing, etc loopback loopback Link local Link local

  4. Advantages of using link locals on infrastructure links • Smaller routing table • Reduced memory consumption • Possibly decreased convergence time • Reduced attack surface • Only need to protect loopbacks from outside • Lower configuration complexity • Less errors • Less address space required • Simpler DNS

  5. Caveats and Workarounds • Interface ICMP: • Cannot ping specific link from remote • Workaround: RFC 5837 (i/f identifier in response) • Traceroute: • Cannot see specific link • Workaround: RFC 5837 (i/f identifier in response) • Hardware dependency: • LL by default EUI-64 based, changes w/ hardware • Workaround: Configure LL statically (ex: fe80::1)

  6. Summary • We believe there are advantages in using link locals on infrastructure links. • Goal: Document advantages and caveats, to let operators make a good choice whether to use LL or not. • We request this to become a WG document.

More Related