, the ESI
label MUST be assigned from the per-platfirm label space.
This is my reading of Section 8.3.1 of RFC 7432.
Hope this helps.
Thumb typed by Sasha Vainshtein
From: Alexander Vainshtein
Sent: Wednesday, June 5, 07:14
Subject: Re: [bess] SHL label
To: Anush Mohan
Cc: gangadhara reddy chavva
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, bess@ietf.org, Rabadan, Jorge (Nokia - US/Mountain
View)
hi,
I had a follow up question
) 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
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
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
