Nick Hilliard wrote (on Thu 22-Oct-2015 at 14:15 +0100): > On 22/10/2015 13:47, Daniel Walton wrote: > > The number of duplicate but somewhat modified code paths to > > hand RS in quagga is also troublesome. We need to implement > > add-path TX, then the RS could keep everything in the original > > table and use add-path to serve all of the routes.
> yep, that's the easier bit. The hard bit is to get add-path > support on all client routers. :-) Add-Path should deal with the per-client selection cost... but complicates the tracking of outbound routes (of course). Unless, that is, there is a limit on the number of outbound routes (for a given prefix) that a given client will accept -- in which case Add-Path appears to suddenly makes things even harder :-( Deciding whether a given route is allowed for a given client -- that is, deciding whether to add the route to a given client's RIB, or not -- is a significant part of the cost (futzing with community filters). The majesty of the wonderfully general import/export filtering contributes to the processing load. I dream of a RS with one RIB which can keep the routes for each prefix in descending order, with one bit per route, per outbound client to say "can be advertised". Chris _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
