1 / 7

NVO3: VPN Interactions (Some initial thoughts)

NVO3: VPN Interactions (Some initial thoughts). David L. Black, EMC IETF NVO3 BOF – Paris March 28, 2012. What’s this about?. Draft NVO3 charter: “Finally, some work may be needed in connecting an overlay network with traditional L2 or L3 VPNs (e.g., VPLS).”

hawa
Download Presentation

NVO3: VPN Interactions (Some initial thoughts)

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. NVO3: VPN Interactions(Some initial thoughts) David L. Black, EMCIETF NVO3 BOF – ParisMarch 28, 2012

  2. What’s this about? • Draft NVO3 charter: “Finally, some work may be needed in connecting an overlay network with traditional L2 or L3 VPNs (e.g., VPLS).” • These slides: Some initial thoughts • 3 examples of overlay-VPN interactions IETF NVO3 BOF - Paris

  3. Basic Diagram Overlay (encapsulates Virtual Networks) IP Enet NVE Vnet IP Enet Internet Router UnderlyingNetwork IP Enet End Systems End SystemPacket/Frame Added for OverlayRemoved by NVE Network Virtualization Edge [NVE] integrated into end systems and gateway router IETF NVO3 BOF - Paris

  4. Two Data Centers, One Admin Domain (1) IP IP IP Enet Enet Enet Vnet Vnet Vnet IP IP IP Enet Enet Enet OR IP Overlay is end-to-end Enet Vnet IP L3VPN L2VPN DC admin 1 That was easy ... What if the overlay is not end-to-end? Connectivity unspecifiedSingle overlaytransported over inter-data-center connectivity (e.g., VPN) IETF NVO3 BOF - Paris

  5. Two Data Centers, Two Admin Domains (2) Map VNIDs between the twooverlays here (two NVEs) IP IP Enet Enet Vnet Vnet IP IP Enet Enet OR IP IP Enet Enet Vnet Vnet IP IP • L3VPN Enet L2VPN DC admin 2 DC admin 1 Connectivity unspecifiedLeft overlay transported over inter-data-center connectivity (e.g., VPN). VPN admin IETF NVO3 BOF - Paris

  6. Two Data Centers, Two Admin Domains (3) Opportunity: Map VNIDs to/from VPN IDs Result: Single logical network (2 VNs + VPN) IP Enet Vnet IP Enet OR IP IP IP Enet Enet Vnet • L3VPN L2VPN IP Enet DC admin 1 DC admin 2 Connectivity unspecified, Baseline: Separate overlay domains, separate virtual networks. VPN admin IETF NVO3 BOF - Paris

  7. Comments? Questions?

More Related