Anush, I think you have already answered your question when you have described your use case😉.
ESI Label is assigned by a PE when its Ethernet port is configured to be part of an MH ES regardless of (and prior to) any specific EVI that is connected to it. Therefore it MUST be allocated from the per platform label space. My 2c. Thumb typed by Sasha Vainshtein From: Anush Mohan Sent: Wednesday, June 5, 06:38 Subject: Re: [bess] SHL label To: Alexander Vainshtein Cc: gangadhara reddy chavva, [email protected], Rabadan, Jorge (Nokia - US/Mountain View) hi, I had a follow up question regarding this. If we are using P2MP tunnel for replicating BUM traffic, the ESI-label is assigned by upstream PE, but actually programmed by downstream PEs in the context of upstream-PE. In this case, does the upstream-PE still need to assign this label from its platform label-space ? ( In other words this label can't be used by upstream-PE to receive any incoming label traffic) The scenario I want to clarify is: we already have an EVI using P2MP tunnel for replicating BUM traffic, configured on this ES. And later we configure another EVI on this ES, where we want to use ingress replication for sending BUM traffic. Regards Anush On Tue, Jun 4, 2019 at 8:33 PM Alexander Vainshtein <[email protected]<mailto:[email protected]>> wrote: Hi all, I concur with Jorge. The ESI label is allocated per MH ES and does not depend on the service or on the method by which BUM frames are deliverd. This method only affects the way in which it is used: - in the case of ingress replication a copy that is sent to the specific LE attached to a given MH ES uses the label this PE has advertised for this ES. I.e. it is used as downstream-allocated - In the case of P2MP LSPs (where all PEs receive the same copy) the transmitter uses the ESI label it has allocated for the ES (it is upstream-allocated), and each receiver uses the label(s) that identify the transmitter PE as the context labels for its correct processing. RFC 7474 is quite clear in this regard from my POV. Thumb typed by Sasha Vainshtein From: Rabadan, Jorge (Nokia - US/Mountain View) Sent: Tuesday, June 4, 15:38 Subject: Re: [bess] SHL label To: gangadhara reddy chavva, [email protected]<mailto:[email protected]> 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]<mailto:[email protected]>> Date: Monday, June 3, 2019 at 2:05 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "Rabadan, Jorge (Nokia - US/Mountain View)" <[email protected]<mailto:[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 ___________________________________________________________________________ This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. ___________________________________________________________________________ _______________________________________________ BESS mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/bess ___________________________________________________________________________ This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. ___________________________________________________________________________
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
