70 likes | 193 Views
draft-boutros-l2vpn-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?.
E N D
draft-boutros-l2vpn-evpn-vpws-04.txtSami Boutros Ali SajassiSamer SalamPatrice BrissetteJohn DrakeJeff TantsuraDirk Steinberg Thomas BeckhausIETF 90, July 2014Toronto, 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 P2P 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 RD – RD unique per adv. PE per EVI Eth.Tag ID – 4-bytes VPWS service instance Identify EPL/EVPL. MPLS RT– RT associated with a given EVI 2 MPLS Label – (downstream assigned) used by remote PEs to reach EVPL/EPL VPWS Service Config: EVI = 100 Local Eth tag ID = AC2 Remote Eth tag ID = AC1 PE1 PE2 CE1 CE2 ES1– Since CE1 is single homed to PE1, ES1 = 0 ES1 1 ES2 ES2– Since CE2 is single homed to PE2, ES2 = 0 VPWS Service Config: EVI = 100 Local Eth Tag ID = AC1 Remote Eth Tag ID = AC2 5 6 4
EVPN VPWS Operation – single-active RD – RD unique per adv. PE per EVI ESI – 10 bytes ESI as per EVPN baseline 3 Eth.Tag ID – 4-bytes VPWS service instance Identify EPL/EVPL. RT– RT associated with a given EVI MPLS MPLS Label – (downstream assigned) used by remote PEs to reach EVPL/EPL VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC2 Remote Eth. Tag ID = AC1 PE1 VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC1 Remote Eth. Tag ID = AC2 ES1 PE3 CE1 CE2 2 ES2 ES2– Since CE2 is single homed to PE2, ES2 = 0 1 ES1– Since CE1 is multi-homed to PE1, ES1 is a non 0 value VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC1 Remote Eth. Tag ID = AC2 ES1 5 6 PE2 4
EVPN VPWS Operation – all-active RD – RD unique per adv. PE per EVI ESI – 10 bytes ESI as per EVPN baseline 3 Eth.Tag ID – 4-bytes VPWS service instance Identify EPL/EVPL. RT– RT associated with a given EVI MPLS MPLS Label – (downstream assigned) used by remote PEs to reach EVPL/EPL VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC2 Remote Eth. Tag ID = AC1 PE1 VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC1 Remote Eth. Tag ID = AC2 ES1 PE3 CE1 CE2 2 ES2 ES2– Since CE2 is single homed to PE2, ES2 = 0 1 ES1– Since CE1 is multi-homed to PE1, ES1 is a non 0 value VPWS Service Config: EVI = 100 Local Eth. Tag ID = AC1 Remote Eth. Tag ID = AC2 ES1 5 6 PE2 4
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