Hi all,
I have a question about Section 14.1.1 of 
draft-ietf-bess-rfc7432bis<https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-13#section-14.1.1>.

The first two para of this section say:

<quote>
For a given ES, if a remote PE has imported the set of Ethernet A‑D per ES 
routes from at least one PE, where the "Multihoming redundancy mode" in the ESI 
Label extended community is set to 1, then that remote PE MUST deduce that the 
ES is operating in Single-Active redundancy mode.

This means that for a given <EVI, BD>, a given MAC address is reachable only 
via the PE announcing the associated MAC/IP Advertisement route - this PE will 
also have advertised an Ethernet A-D per EVI route for that <EVI, BD> with an 
L2-Attr extended community in which the P bit is set. I.e., the Primary DF 
Elected PE is also responsible for sending known unicast frames to the CE and 
receiving unicast and BUM frames from it. Similarly, the Backup DF Elected PE 
will have advertised an Ethernet AD per EVI route for <EVI, BD> with an L2-Attr 
extended community in which the B bit is set.
<end quote>

Please consider the following misconfiguration scenario depicted in the 
embedded diagram below:

[cid:[email protected]]

In this diagram, PE-4:



  1.  Should treat MH ES in question as if it were operating in Single-Active 
redundancy mode – with all the implications
  2.  At the same time, would receive per-EVI RT-1 for a specific EVI with P 
bit set in the attached L2-Attr Extended Community at least from PE-3 and PE-4 
(and possibly also from PE-1 if it was elected as the DF for the EVI in 
question)
  3.  Could receive RT-2 for a specific MAC address from at least PE-3 and PE-4 
(and possibly also from PE-1 if it was elected as the DF for the EVI in 
question).

Can you please clarify what is the expected behavior of PE-4 regarding 
forwarding known unicast traffic for such a MAC address?

Your response would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha

Disclaimer

This e-mail together with any attachments may contain information of Ribbon 
Communications Inc. and its Affiliates that is confidential and/or proprietary 
for the sole use of the intended recipient. Any review, disclosure, reliance or 
distribution by others or forwarding without express permission is strictly 
prohibited. If you are not the intended recipient, please notify the sender 
immediately and then delete all copies, including any attachments.
_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to