On 26 mrt 2009, at 11:19, Danny McPherson wrote:
The problem is that if the client is advertising 100ks of
routes (which is perfectly reasonable for a peering edge
router) to the RRs, (100ks * num_rrs) are reflected back to
the client, and it now has to senselessly process and discard
all of those updates.
Do you have any data about how much processing this requires?
Recognizing the originator ID can happen very early when expensive
actions such as applying prefix lists and route maps and inserting in
the RIB haven't happened yet, so the impact of doing this could be
fairly negligible.
(Then again, a Pentium200 can do hundreds of megabytes of MD5 hashing
but somehow enabling MD5 on BGP sessions takes a good bit of toll on
many route processors.)
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
