Juliusz Chroboczek <[email protected]> writes: >> My thinking was that filters may want to do something like: >> >> if (metric == smoothed_metric) >> metric += 100; /* route is stable, we can apply our policy */ >> >> but I honestly don't know if that's useful for anything in reality :) > > I'm a little conflicted on this. On the one hand, it's nice to give > administrators more flexibility. On the other hand, I want Babel to be as > automated as possible: that's why Babel supported ETX from the outset, and > that's why we developed RTT: so that Babel could adapt to a variety of > real-world networks with minimal human intervention. > > Toke, what problem are you aiming to solve, and are we able to develop an > algorithm that solves this problem without configuring policies > manually?
Well, the immediate problem I'm trying to solve is to consolidate Daniel's patch moving the route selection to Bird core with the RTT extension patches (and associated metric smoothing). I don't really have a particular use case in mind for exposing the metric, as indicated by my comment above. It just occurred to me as something that *might* be useful for someone :) -Toke
