> It's one additional update per table entry per day, assuming a 24 hour > beacon. If the table is 300,000 routes, it's 300,000 additional > updates a day --on top of normal churn.
note that this is not churn, in the sense of fib update, which is 90% of the cost of an update. > At some point you're going to be forced to put in timers per AS Path > hop nope. gains absolute zero replay protection. see my preso from VdeQ. but i am not really interested in the noise about beaconing. as i said in VdeQ, the feature is nice but not all that important. randy _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
