Just a word of caution. The main value proposition of muxing tens of thousands 
of VLANs/ACs within a single EVPN-VPWS service instance, was to have 
transparency  with respect to BGP - i.e., just setup  a single EVPN-VPWS 
service instance. If we try to signal the VLANs in BGP for single-sided 
provisioning, then we lose this transparency.

Cheers,
Ali



From: BESS <[email protected]<mailto:[email protected]>> on behalf of 
Sami Boutros <[email protected]<mailto:[email protected]>>
Date: Thursday, October 8, 2015 at 9:32 AM
To: "UTTARO, JAMES" <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Subject: Re: [bess] Seeking Comments for EVPN-VPWS Service Edge Gateway

Hi Jim,

You bring a good point in how we can extend this single sided provisioning at 
access PE, with the muxing of thousands of L2/L3 services to the same VPWS 
instance at the access, given that we don't provision anything at the service 
PE.

We need to think more about this.

Thanks,

Sami

On Thu, Oct 8, 2015 at 6:07 AM, UTTARO, JAMES 
<[email protected]<mailto:[email protected]>> wrote:
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:[email protected]<mailto:[email protected]>] On 
Behalf Of Sami Boutros
Sent: Wednesday, October 07, 2015 5:14 PM
To: [email protected]<mailto:[email protected]>
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
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to