@techreport{li-bess-evpn-ead-multipath-00,
    number =    {draft-li-bess-evpn-ead-multipath-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-li-bess-evpn-ead-multipath/00/},
    author =    {Zhiqiang Li and Zongpeng Du and Junjie Wang and Wei Cheng and Guoying Zhang and Xun Sun and Chunhao Zhao},
    title =     {{Multipath for EVPN Ethernet Auto-Discovery Routes}},
    pagetotal = 6,
    year =      2026,
    month =     jul,
    day =       4,
    abstract =  {In EVPN multi-homing deployments, multiple PE devices attached to the same Ethernet Segment each originate Ethernet Auto-Discovery (EAD) routes. Standard BGP best-path selection retains only one route per NLRI key, which can suppress reachability information needed for EVPN aliasing, fast convergence, and split-horizon filtering. This document specifies that BGP speakers MUST treat EAD routes as multipath and MUST advertise and install all valid EAD routes for a given Ethernet Segment, rather than selecting a single best path.},
}