On Mon, Sep 08, 2025 at 09:30:28AM +0000, Sébastien PARISOT wrote: > > Note: We have to refactor the nexthop implementation quite heavily soon > > This is interesting. I understand the refactor work will happen after EVPN is > released? Do you have some idea of what you would like to do already?
We would like to have 'nexthop' as an attribute, with some way of having multiple instances of the attribute (for ECMP), while the body of the attribute will be a list of sub-attributes (for iface, gw, encapsulation, MPLS stack ...), similarly how Linux Netlink is doing that. In the current situation, we store EVPN forwarding entry VXLAN remote address in a gateway field, which is a semantic abuse. Also, it prevent us to implement different encapsulations to L3VPN as we have no place to store encapsulation data for each nexthop. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: [email protected]) "To err is human -- to blame it on a computer is even more so."
