Hi Jim, This work in a nutshell is about single-sided provisioning where you only need to provision the P2P EVC on the Access-PE (and not on the service PE). The Service-PE (S-PE) figures out (via EVPN signaling) what endpoint (e.g., VRF) the P2P EVC is intended for. Thus cutting network-wide provisioning for setting up P2P EVC in half.
Cheers, Ali From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of "UTTARO, JAMES" <ju1...@att.com<mailto:ju1...@att.com>> Date: Thursday, October 8, 2015 at 3:07 AM To: Sami Boutros <boutros.s...@gmail.com<mailto:boutros.s...@gmail.com>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>> Subject: Re: [bess] Seeking Comments for EVPN-VPWS Service Edge Gateway Sami, In what way is this different from the work we have been doing on creating the flexible cross connect table which enables thousands of PWs to be “landed” on a L3/L2/Internet PE? Is this specific to always using EVPN on the service PE to facilitate L2/L3 closed user groups? Thanks, Jim Uttaro From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Sami Boutros Sent: Wednesday, October 07, 2015 5:14 PM To: bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] Seeking Comments for EVPN-VPWS Service Edge Gateway Hi, The draft proposes a dynamic mechanism to terminate the VPWS transport service at a service PE into an overlay L2 or L3 service based on a single side provisioning at the access PE. https://tools.ietf.org/html/draft-boutros-bess-evpn-vpws-service-edge-gateway-01 Thanks, Sami
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
