1 / 7

draft-nachum-sarp-06: SARP: Proxy Gateway

draft-nachum-sarp-06: SARP: Proxy Gateway . Youval Nachum Marvell Linda Dunbar Huawei Ilan Yerushalmi Marvell Tal Mizrahi Marvell IETF Meeting 87, July 2013. History. March 2012 – draft 00. Discussion in ARMD mailing list. July 2012 – IETF 84 – presented in INTAREA WG.

elke
Download Presentation

draft-nachum-sarp-06: SARP: Proxy Gateway

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. draft-nachum-sarp-06:SARP: Proxy Gateway Youval Nachum Marvell Linda Dunbar Huawei Ilan Yerushalmi Marvell Tal Mizrahi Marvell IETF Meeting 87, July 2013

  2. History • March 2012 – draft 00. • Discussion in ARMD mailing list. • July 2012 – IETF 84 – presented in INTAREA WG. • Main feedback: need to equally address IPv4 and IPv6. • October 2012 – draft 03. • More details about SARP with IPv6. • March 2013 – draft 04: • Address issues discussed at mailing list • July 2013 – draft 06: • Explain Proxy Gateway and interaction with SEND

  3. Motivation • Environment: • hosts within one subnet (or VLAN) can spread over various access domains • Each access domain participates in many VLANs • Massive number of VMs, that can move across various physical locations. • Issues: • Switches’ MAC address table (FDB) explosion: • Even with overlay (NVO3/TRILL/etc), all the overlay edge nodes are still exposed to all the hosts MAC addresses on the VLANs that are enabled on the edges • the ARP/ND processing load impact to the L2/L3 boundary routers Core

  4. SARP • Edge devices: proxy SARP. • IP subnet does not imply location. • MAC-W / MAC-E imply location. ARP/ND: IP-D 1 Reply: MAC-D Reply: MAC-E 2 3

  5. Complexion when IPv6’s SEND is deployed • When IPv6 SEND is used, Access (or Aggregation) switches might not possess knowledge of the attached hosts (VMs)’ private keys • Recommendation in our draft? Any preferences? • state that SARP is not recommended when SEND is deployed; • recommend using RFC6496 (Secure Proxy ND Support for SEND).

  6. Next Steps • WG adoption

  7. Thanks

More Related