<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-evpn-unequal-lb" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-unequal-lb-32">
   <front>
      <title>Weighted Multi-Path Procedures for EVPN Multi-Homing</title>
      <author initials="N." surname="Malhotra" fullname="Neeraj Malhotra">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Independent</organization>
      </author>
      <author initials="A. R." surname="Lingala" fullname="Avinash Reddy Lingala">
         <organization>ATT</organization>
      </author>
      <author initials="S." surname="Thoria" fullname="Samir Thoria">
         <organization>Cisco Systems</organization>
      </author>
      <date month="February" day="27" year="2026" />
      <abstract>
	 <t>   Ethernet VPN (EVPN) provides all-active multi-homing for Customer
   Equipment (CE) devices connected to multiple Provider Edge (PE)
   devices, enabling equal cost load balancing of both bridged and
   routed traffic across the set of multi-homing PEs.  However, existing
   procedures implicitly assume equal access bandwidth distribution
   among the multi-homing PEs, which can constrain link additions or
   removals and may not handle unequal PE-CE link bandwidth following
   link failures.  This document specifies extensions to EVPN procedures
   to support weighted multi-pathing in proportion to PE-CE link
   bandwidth or operator-defined weights, thereby providing greater
   flexibility and resilience in multi-homing deployments.  The
   extensions include signaling mechanisms to distribute traffic across
   egress PEs based on relative bandwidth or weight, and enhancements to
   Broadcast, Unknown Unicast, and Multicast (BUM) designated forwarder
   (DF) election to achieve weighted DF distribution across the multi-
   homing PE set.  The document updates RFC 8584 to enable weighted load
   balancing across different DF election algorithms.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-evpn-unequal-lb-32" />
   
</reference>
