<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.li-bess-evpn-ead-multipath" target="https://datatracker.ietf.org/doc/html/draft-li-bess-evpn-ead-multipath-00">
   <front>
      <title>Multipath for EVPN Ethernet Auto-Discovery Routes</title>
      <author initials="Z." surname="Li" fullname="Zhiqiang Li">
         <organization>China Mobile</organization>
      </author>
      <author initials="Z." surname="Du" fullname="Zongpeng Du">
         <organization>China Mobile</organization>
      </author>
      <author initials="J." surname="Wang" fullname="Junjie Wang">
         <organization>Centec</organization>
      </author>
      <author initials="W." surname="Cheng" fullname="Wei Cheng">
         <organization>Centec</organization>
      </author>
      <author initials="G." surname="Zhang" fullname="Guoying Zhang">
         <organization>Centec</organization>
      </author>
      <author initials="X." surname="Sun" fullname="Xun Sun">
         <organization>Inesa</organization>
      </author>
      <author initials="C." surname="Zhao" fullname="Chunhao Zhao">
         <organization>SAIA</organization>
      </author>
      <date month="July" day="4" year="2026" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-li-bess-evpn-ead-multipath-00" />
   
</reference>
