It is the second draft - https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-unequal-lb
The authors have also defined a new community with the change transitivity as the motivation: Link bandwidth extended community described in [BGP-LINK-BW] for layer 3 VPNs was considered for re-use here. This Link bandwidth extended community is however defined in [BGP-LINK-BW] as optional non-transitive. Since it is not possible to change deployed behavior of extended community defined in [BGP-LINK-BW], it was decided to define a new one. > On Jun 26, 2023, at 2:44 PM, Alvaro Retana <[email protected]> wrote: > > On June 26, 2023 at 5:27:39 PM, Jeff Tantsura wrote: > > Jeff: > >> Over the last couple of years I have reached out to the authors of the >> original draft at least twice with a request to refresh the draft and bring >> the necessary changes in, without much success though. >> > ... >> Note that there’s also an EVPN specific draft (standard track). > > That made me go look -- I found two related documents! Are these what > you're referring to? > > https://datatracker.ietf.org/doc/html/draft-ietf-bess-weighted-hrw > https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-unequal-lb > > >> I’d be happy to volunteer to help managing the mess ;-) > > I know the idr/bess-chairs are listening. ;-) > > > Alvaro. _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
