On Tue, Nov 18, 2014 at 7:33 AM, Acee Lindem (acee) <[email protected]> wrote: > Hi Juliusz, > I think I understand. If there is the potential for a loop (advertised > distance >= babel router’s former distance), babel will wait for the next > sequenced route from the source. So, the loop-free guarantee is at the > expense of potentially faster convergence. Correct?
I cannot quite answer that question well, so I will leave that to juliusz. I do note that the default 4 sec update interval bugs me. Part of that is due to having to deal with wifi multicast, which can defer multicast updates for up to 200ms, and std wifi only transmits at 1mbit (unless you choose to transmit at a higher rate, which many people do, I have seen 9 and 12mbit in the field). I have longed to take the source specific version to a top of rack 10GigE switching environment, and crank up the update interval by a factor of, say, 10000, to see what happens. > Thanks, > Acee > > On Nov 18, 2014, at 10:12 AM, Juliusz Chroboczek > <[email protected]> wrote: > >>> What feature of babel keeps traffic from looping during re-convergence? >> >> Please see >> >> http://www.pps.univ-paris-diderot.fr/~jch/software/babel/babel-20140311.pdf >> >> slides 7 and 11-17. I'll be more than happy to clarify anything that's >> not obvious from the slides. >> >> -- Juliusz > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet -- Dave Täht thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
