%% You should probably cite draft-ietf-bess-evpn-unequal-lb-35 instead of this revision.
@techreport{ietf-bess-evpn-unequal-lb-32,
    number =    {draft-ietf-bess-evpn-unequal-lb-32},
    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/32/},
    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 = 25,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {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.},
}