Hi,
I have doubts regarding applicability of the solution for L3 fast convergence
defined in
draft-sajassi-bess-evpn-ip-aliasing-05<https://datatracker.ietf.org/doc/html/draft-sajassi-bess-evpn-ip-aliasing-05>
for the scenarios in which the MH ES in question operates in Single
Flow-Active load-balancing mode as described in
draft-ietf-bess-evpn-l2gw-proto-02<https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-l2gw-proto-02>.
These doubts are based on the fact that, in Single Flow-Active load-balancing
mode, the Primary PE is defined by the Layer 2 Control Protocol (or its
equivalent) for each specific host, while the EVPN IP Aliasing draft advertises
Primary/Backup paths via P/B bits in the EVPN Layer 2 Extended Community
attached to the IP A-D EVPN routes.
What, if anything, did I miss?
Your feedback would be highly appreciated.
Regards, and lots of thanks in advance,
Sasha
Notice: 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
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
