%% You should probably cite draft-ietf-bess-evpn-unequal-lb-21 instead of this revision. @techreport{ietf-bess-evpn-unequal-lb-15, number = {draft-ietf-bess-evpn-unequal-lb-15}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-unequal-lb/15/}, author = {Neeraj Malhotra and Ali Sajassi and Jorge Rabadan and John Drake and Avinash Reddy Lingala and Samir Thoria}, title = {{Weighted Multi-Path Procedures for EVPN Multi-Homing}}, pagetotal = 21, year = 2021, month = nov, day = 17, abstract = {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.}, }