Luc and all,https://datatracker.ietf.org/doc/html/draft-burdet-bess-evpn-fast-reroute-06#section-5.1 I have a question regarding significance of bypassing DF Election behavior in Section 5.1 of the EVPN Fast Reroute draft, at least in the case of All-Active multi-homing and EVPN-MPLS.
To the best of my understanding, in this case DF Election based filtering is applied only to BUM traffic. Per Section 11.2 of RFC 7432<https://datatracker.ietf.org/doc/html/rfc7432#section-11.2> this traffic is carried using the label advertised in the PMSI attribute in the EVPN IMET route so that DF Election-based filtering can be applied only to the traffic received with this label: * In the case of ingress replication, this label is down-stream allocated by the egress PE and therefore would be different from the ERL label * In the case of P-multicast trees, this label would be upstream-allocated by the ingress PE and, in the case of non-aggregated tunnels, preceded by the label that identifies the P-multicast tree. (I am leaving aside the case of aggregated P-multicast trees). I.e., in both cases, the egress PE can identify the received BUM traffic based on the label stack in its EVPN encapsulation and apply DF-Election-based filtering just to this traffic - but not to traffic received with the ESL or ERL labels. What, if anything, do I miss? 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 BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
