Weighted Multi-Path Procedures for EVPN Multi-Homing
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|Neeraj Malhotra , Ali Sajassi , Jorge Rabadan , John Drake , Avinash Reddy Lingala , Samir Thoria
|2023-06-01 (Latest revision 2022-11-28)
|Internet Engineering Task Force (IETF)
GENART Early review (of -18) by Mallory Knodel Ready w/issues
RTGDIR Early review (of -18) by Dhruv Dhody Has issues
|Mailing list discussion
|WG Consensus: Waiting for Write-Up
|Send notices to
|Stephane Litkowski <email@example.com>
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
EVPN enables all-active multi-homing for a CE device connected to two or more PEs via a LAG, such that bridged and routed traffic from remote PEs to hosts attached to the Ethernet Segment can be equally load balanced (it uses Equal Cost Multi Path) across the multi-homing PEs. EVPN also enables multi-homing for IP subnets advertised in IP Prefix routes, so that routed traffic from remote PEs to those IP subnets can be load balanced. This document defines extensions to EVPN procedures to optimally handle unequal access bandwidth distribution across a set of multi-homing PEs in order to: * provide greater flexibility, with respect to adding or removing individual multi-homed PE-CE links. * handle multi-homed PE-CE link failures that can result in unequal PE-CE access bandwidth across a set of multi-homing PEs.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)