NVO3: VPN Interactions(Some initial thoughts)

David L. Black, EMCIETF NVO3 BOF – Paris

March 28, 2012

IETF NVO3 BOF - Paris 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, 2012

IETF NVO3 BOF - Paris 3

Basic Diagram

End Systems

UnderlyingNetwork

Router

Overlay (encapsulates

Virtual Networks)

Internet

Network Virtualization Edge [NVE] integrated into end systems and gateway router

IP

VnetIP

Enet

Enet

IPEnet

NVE

End SystemPacket/Frame

Added for OverlayRemoved by NVE

March 28, 2012

IETF NVO3 BOF - Paris 4

Two Data Centers, One Admin Domain (1)

Connectivity unspecified Single overlaytransported over inter-data-center connectivity (e.g., VPN)

IP

VnetIP

Enet

EnetIP

VnetIP

Enet

Enet

DC admin 1

L3VPN

IP

VnetIP

Enet

L2VPN

IP

VnetIP

Enet

EnetOR

Overlay is end-to-end

That was easy ...What if the overlay is not end-to-end?

March 28, 2012

IETF NVO3 BOF - Paris 5

Two Data Centers, Two Admin Domains (2)

Connectivity unspecifiedLeft overlay transported over inter-data-center connectivity (e.g., VPN).

IP

VnetIP

Enet

EnetIP

VnetIP

Enet

Enet

DC admin 1 DC admin 2

L3VPN

IP

VnetIP

Enet

L2VPN

IP

VnetIP

Enet

Enet

OR

Map VNIDs between the twooverlays here (two NVEs)

VPN admin

March 28, 2012

IETF NVO3 BOF - Paris 6

Two Data Centers, Two Admin Domains (3)

Connectivity unspecified, Baseline: Separate overlay domains, separate virtual networks.

IP

VnetIP

Enet

EnetIP

VnetIP

Enet

EnetL3VPN

IP

DC admin 1 DC admin 2

L2VPN

IPEnet

OR

Opportunity: Map VNIDs to/from VPN IDs Result: Single logical network (2 VNs + VPN)

VPN admin

March 28, 2012

Comments? Questions?