RFC 9786: EVPN Port-Active Redundancy Mode
In plain English — editorial summary, not part of the RFC
The Multi-Chassis Link Aggregation (MC-LAG) group technology enables establishing a logical link-aggregation connection with a redundant group of independent nodes. The objective of MC-LAG is to enhance both network availability and bandwidth utilization through various modes of traffic load balancing. RFC 7432 defines an EVPN-based MC-LAG with Single-Active and All-Active multihoming redundancy modes. This document builds on the existing redundancy mechanisms supported by EVPN and introduces a new active/standby redundancy mode, called 'Port-Active'.
Document record
- Document ID
- RFC9786
- Published
- June 2025
- Authors
- P. Brissette; LA. Burdet; B. Wen; E. Leyton; J. Rabadan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9744EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) ServiceCurrent
March 2025
- RFC 9722Fast Recovery for EVPN Designated Forwarder ElectionCurrent
May 2025
- RFC 9489Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN)Current
November 2023
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 9079Source-Specific Routing in the Babel Routing ProtocolCurrent
August 2021
- RFC 8560Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) EquivalentsCurrent
May 2019
- RFC 8388Usage and Applicability of BGP MPLS-Based Ethernet VPNCurrent
May 2018
- RFC 9063Host Identity Protocol ArchitectureCurrent
July 2021
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?