RFC 8584: Framework for Ethernet VPN Designated Forwarder Election Extensibility
In plain English — editorial summary, not part of the RFC
An alternative to the default Designated Forwarder (DF) selection algorithm in Ethernet VPNs (EVPNs) is defined. The DF is the Provider Edge (PE) router responsible for sending Broadcast, Unknown Unicast, and Multicast (BUM) traffic to a multihomed Customer Edge (CE) device on a given VLAN on a particular Ethernet Segment (ES). In addition, the ability to influence the DF election result for a VLAN based on the state of the associated Attachment Circuit (AC) is specified. This document clarifies the DF election Finite State Machine in EVPN services. Therefore, it updates the EVPN specification (RFC 7432).
Document record
- Document ID
- RFC8584
- Published
- April 2019
- Authors
- J. Rabadan; S. Mohanty; A. Sajassi; J. Drake; K. Nagaraj; S. Sathappan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
- Updates:
- RFC 7432
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8578Deterministic Networking Use CasesCurrent
May 2019
- RFC 8577Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding PlaneCurrent
April 2019
- RFC 8595An MPLS-Based Forwarding Plane for Service Function ChainingCurrent
June 2019
- RFC 8596MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)Current
June 2019
- RFC 8571BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric ExtensionsCurrent
March 2019
- RFC 8570IS-IS Traffic Engineering (TE) Metric ExtensionsCurrent
March 2019
- RFC 8564Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)Current
April 2019
- RFC 8563Bidirectional Forwarding Detection (BFD) Multipoint Active TailsCurrent
April 2019
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?