Hi, The ESI label is signaled in the A-D per ES route(s), and those routes are (should be) service agnostic. Also as you can see in RFC7432, the ESI label is downstream allocated for ingress replication but upstream allocated for p2mp - So it’s not that you allocate different ESI label per service, but the label that you use has different owner.
I think RFC7432 is pretty clear about this. Not sure where the confusion is. Thanks. Jorge From: gangadhara reddy chavva <[email protected]> Date: Monday, June 3, 2019 at 2:05 PM To: "[email protected]" <[email protected]>, "Rabadan, Jorge (Nokia - US/Mountain View)" <[email protected]> Subject: SHL label Hi Jorge, I have a Question on EVPN MH SHL(split horizon label). Can ESI share the different SHL label for the same ESI? case 1: in the same ESI one customer EVPN VPN can have ingress replication for the BUM traffic and second EVPN VPN ine the same ESI can do P2MP? in this case SHL label should be different. case 2: can VPLS allocate one SHL and VPWS can allocate diffrent SHL label? or SHL should be same per ESI irrespective of number of applications enabled in that ESI. Thanks, Gangadhar
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
