> I am not sure how important it is to separate fast-hello from route > announcements for hosts. We may have <= 10 addresses on a host. Where would > be have a problem ?
Radio congestion due to the announcements from the routers, which in RIP would be advertising the whole network every Update interval. One full-size frame every 72 routes, multiply by the number of routers in range, divide by the Update interval. (Recall that multicast is 2Mbit/s at the phy. 13ms for a full-size frame, not counting the cost of collisions.) > Something as simple as RIP also makes it very easy to embed it as > a library into apps No sensible platform allows unpriviledged code to manipulate the routing tables. But if you manage to solve this particular problem, the stub implementation of Babel is 1000 lines of portable C. > Lets just say with <= 5 sec failover time. Babel has consistently been measured as having failover times of 2 to 5 hello intervals over IBSS, with no link-layer support, independent of update interval (due to triggered updates and reactive route requests). The protocol supports Hello intervals down to 10ms, and allows varying Hello intervals dynamically (a feature not used by the current implementation). -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
