Preference-Based EVPN Designated Forwarder Election
RFC 9785, “Preference-Based EVPN Designated Forwarder Election”, is a Proposed Standard document published in June 2025 by J. Rabadan, S. Sathappan, W. Lin, J. Drake, A. Sajassi. It updates RFC 8584. The canonical text is published by the RFC Editor.
Abstract
The Designated Forwarder (DF) in Ethernet Virtual Private Networks (EVPNs) is defined as the Provider Edge (PE) router responsible for sending Broadcast, Unknown Unicast, and Multicast (BUM) traffic to a multihomed device/network in the case of an All-Active multihoming Ethernet Segment (ES) or BUM and unicast in the case of Single-Active multihoming. The Designated Forwarder is selected out of a candidate list of PEs that advertise the same Ethernet Segment Identifier (ESI) to the EVPN network, according to the default DF election algorithm. While the default algorithm provides an efficient and automated way of selecting the Designated Forwarder across different Ethernet Tags in the Ethernet Segment, there are some use cases where a more "deterministic" and user-controlled method is required. At the same time, Network Operators require an easy way to force an on-demand Designated Forwarder switchover in order to carry out some maintenance tasks on the existing Designated Forwarder or control whether a new active PE can preempt the existing Designated Forwarder PE.
This document proposes use of a DF election algorithm that meets the requirements of determinism and operation control. This document updates RFC 8584 by modifying the definition of the DF Election Extended Community.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9785 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9784 Virtual Ethernet Segments for EVPN and Provider Backbone Bridge EVPN
- RFC 9786 EVPN Port-Active Redundancy Mode
- RFC 9783 Arm's Platform Security Architecture Attestation Token
- RFC 9787 Guidance on End-to-End Email Security
- RFC 9782 Entity Attestation Token Media Types
- RFC 9788 Header Protection for Cryptographically Protected Email
- RFC 9781 A Concise Binary Object Representation Tag for Unprotected CBOR Web Token Claims Sets
- RFC 9789 MPLS Network Actions Framework