draftboutrosl 2 vpnevpnvpws04 txt Sami Boutros Ali Sajassi

draft-boutros-l 2 vpn-evpn-vpws-04. txt Sami Boutros Ali Sajassi Samer Salam Patrice Brissette John Drake Jeff Tantsura Dirk Steinberg Thomas Beckhaus IETF 90, July 2014 Toronto, Canada

How it works? • The EVPN ability to forward customer traffic to/from a given customer Attachment Circuit (aka Ethernet AD route) is ideal in providing P 2 P services (aka VPWS services). • EVPL/EPL can be considered as a VPWS with only two ACs. Traffic forwarding capability of E-VPN between a pair of Ethernet AD routes is used. • MPLS label associated with the destination Ether AD route will be used in forwarding user traffic to the destination AC.

EVPN VPWS Operation – single-home ESI – 10 bytes ESI Set to 0 for single home Segment as per EVPN baseline 3 PE 1 Eth A-D Route Eth. Tag ID – 4 -bytes VPWS service instance Identify EPL/EVPL. MPLS Label – (downstream assigned) used by remote PEs to reach EVPL/EPL RD = RD-1 a ESI = ES 1 Eth. Tag ID = AC 1 RT – RT associated with a given EVI VPWS Service 2 Config: EVI = 100 Local Eth tag ID = AC 2 PE 2 Remote Eth tag ID = AC 1 CE 2 Label (e. g. X) RT ext. community PE 1 RT-a CE 1 ES 1 – Since CE 1 is single homed to PE 1, ES 1 = 0 MPLS 1 5 RD – RD unique per adv. PE per EVI VPWS Service Config: EVI = 100 Local Eth Tag ID = AC 1 Remote Eth Tag ID = AC 2 PE 1 RIB VPN MA C ESI Eth. TAG RT-a - ES 2 AC 2 ES 2 – Since CE 2 is single homed to PE 2, ES 2 = 0 PE 2 Eth A-D Route RD = RD-2 a Path List ESI = ES 2 Eth. Tag ID = AC 2 NH PE 2 ES 2 Label (e. g. Y) 4 RT ext. community PE 2 RIB 6 VPN MA C ESI Eth. TAG RT-a - ES 1 AC 1 Path List NH PE 1 3

EVPN VPWS Operation – single-active ESI – 10 bytes ESI as per EVPN baseline RD = RD-1 a Eth. Tag ID – 4 -bytes VPWS service instance Identify EPL/EVPL. ESI = ES 1 Eth. Tag ID = AC 1 Label (e. g. X) MPLS Label – (downstream assigned) used by remote PEs to reach EVPL/EPL VPN MA C ESI Eth. TAG RT-a - ES 2 AC 2 RT – RT associated with a given EVI RT-a PE 1 ES 1 – Since CE 1 is multi-homed to 1 PE 1, ES 1 is a VPWS Service Config: ES 1 non 0 value EVI = 100 Local Eth. Tag ID = AC 1 Remote Eth. Tag ID = AC 2 PE 1 & PE 2 RIB 3 RT ext. community VPWS Service Config: ES 1 EVI = 100 CE 1 Local Eth. Tag ID = AC 1 Remote Eth. Tag ID = AC 2 5 RD – RD unique per adv. PE per EVI PE 1 Eth A-D Route PE 3 MPLS ES 2 2 ES 2 – Since CE 2 is single homed to PE 2, ES 2 = 0 PE 3 Eth A-D Route RD = RD-3 a Path List ESI = ES 2 Eth. Tag ID = AC 2 NH PE 3 VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC 2 Remote Eth. Tag ID = AC 1 CE 2 Label (e. g. Y) 4 RT ext. community PE 3 RIB 6 VPN MA C ESI Eth. TAG RT-a - ES 1 AC 1 Path List NH PE 1 PE 2(b ackup 4

EVPN VPWS Operation – all-active ESI – 10 bytes ESI as per EVPN baseline RD = RD-1 a Eth. Tag ID – 4 -bytes VPWS service instance Identify EPL/EVPL. ESI = ES 1 Eth. Tag ID = AC 1 Label (e. g. X) MPLS Label – (downstream assigned) used by remote PEs to reach EVPL/EPL VPN MA C ESI Eth. TAG RT-a - ES 2 AC 2 RT – RT associated with a given EVI RT-a PE 1 ES 1 – Since CE 1 is multi-homed to 1 PE 1, ES 1 is a VPWS Service Config: ES 1 non 0 value EVI = 100 Local Eth. Tag ID = AC 1 Remote Eth. Tag ID = AC 2 PE 1 & PE 2 RIB 3 RT ext. community VPWS Service Config: ES 1 EVI = 100 CE 1 Local Eth. Tag ID = AC 1 Remote Eth. Tag ID = AC 2 5 RD – RD unique per adv. PE per EVI PE 1 Eth A-D Route PE 3 MPLS ES 2 2 ES 2 – Since CE 2 is single homed to PE 2, ES 2 = 0 PE 3 Eth A-D Route RD = RD-3 a Path List ESI = ES 2 Eth. Tag ID = AC 2 NH PE 3 VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC 2 Remote Eth. Tag ID = AC 1 CE 2 Label (e. g. Y) 4 RT ext. community PE 3 RIB 6 VPN MA C ESI Eth. TAG RT-a - ES 1 AC 1 Path List NH PE 1 PE 2 5

Changes from 02 04 • Added requirements sub-section. • Added Patrice, Thomas and Dirk as authors. • Clarified ESI value setting aligning with base EVPN. – ESI value will be set to 0 for single home. – ESI value will be non 0 for single active or all active. • Clarified tag-id value setting in the Ethernet AD route. – Tag-id value will be set to a non 0 unique value per EVI scope for both EPL or EVPL services. • VPWS with multiple site outside the scope of the document • Acknowledged Wen Lin and Jose Liste contributions.

Next steps • Authors believe that document is ready for WG adoption. Thank you 7