1. NVO3: VPN Interactions (Some initial thoughts) David L. Black, EMC IETF NVO3 BOF – Paris March 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 March 28, 20122IETF NVO3 BOF - Paris

3. Basic Diagram End Systems Underlying Network Router Overlay (encapsulates Virtual Networks) Internet Network Virtualization Edge [NVE] integrated into end systems and gateway router IP Vnet IP Enet IP Enet NVE End System Packet/Frame Added for Overlay Removed by NVE March 28, 20123IETF NVO3 BOF - Paris

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

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

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

7. Comments? Questions?