Heasley, I agree, I could only speak personally here. However, it seems to me that if somebody wants to study churn, they should go with route mirroring instead...
And no, we are not planning to add bmp path marking to route mirroring yet :) Camilo On 25/3/25, 09:29, "heasley" <[email protected] <mailto:[email protected]>> wrote: > Camilo> Regarding your question and the scenario you describe, I personally > care more about the final state than transient churn. Therefore, it would be > nice to use as many tricks as we can to hide the churn behind state > compression, but I accept some churn is unavoidable, and we will have to > handle this on the receiving end. > > +1 on final state. The transient churn are less interesting If you are studying that churn, it would be useful, as is the behavior that reflects what the speaker would send after smoothing updates. I would expect more interesting after the initial exchange. no? maybe that application is too unique. _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
