RFC 9785: Preference-Based EVPN Designated Forwarder (DF) Election
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9785
- Published
- June 2025
- Authors
- J. Rabadan; S. Sathappan; W. Lin; J. Drake; A. Sajassi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 8584
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7271MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network OperatorsUpdated
June 2014
- RFC 4412Communications Resource Priority for the Session Initiation Protocol (SIP)Updated
February 2006
- RFC 9784Virtual Ethernet Segments for EVPN and Provider Backbone Bridge EVPNCurrent
June 2025
- RFC 9786EVPN Port-Active Redundancy ModeCurrent
June 2025
- RFC 9789MPLS Network Actions (MNAs) FrameworkUpdated
July 2025
- RFC 9780Bidirectional Forwarding Detection (BFD) for Multipoint Networks over Point-to-Multipoint MPLS Label Switched Paths (LSPs)Current
May 2025
- RFC 9790IANA Registry and Processing Recommendations for the First Nibble Following a Label StackCurrent
July 2025
- RFC 9779Performance Measurement for Segment Routing Networks with the MPLS Data PlaneCurrent
May 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?