%% You should probably cite draft-ietf-bess-evpn-df-election-framework instead of this I-D. @techreport{ietf-bess-evpn-ac-df-01, number = {draft-ietf-bess-evpn-ac-df-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-ac-df-01}, author = {Jorge Rabadan and Kiran Nagaraj and Senthil Sathappan and Vinod Prabhu and Wim Henderickx and Autumn Liu and Wen Lin}, title = {{AC-Influenced Designated Forwarder Election for EVPN}}, pagetotal = 10, year = , month = , day = , abstract = {The Designated Forwarder (DF) in EVPN networks is the PE responsible for sending multicast, broadcast and unknown unicast traffic to a multi-homed CE, on a given Ethernet Tag on a particular Ethernet Segment (ES). The DF is selected based on the list of PEs that advertise the Ethernet Segment Identifier (ESI) to the EVPN network. While PE node or link failures trigger the DF re-election for a given \textless{}ESI, EVI\textgreater{}, individual Attachment Circuit (AC) or MAC-VRF failures do not trigger such DF re-election and the traffic may therefore be permanently impacted, even though there is an alternative path. This document improves the DF election algorithm so that the AC status can influence the result of the election and this type of "logical" failures can be protected too.}, }