Fri, Dec 28, 2018 at 03:52:39PM +0800, Tim: > Soft limit: > > 1) Alert only: Only alert triggered, neighbor is not impacted > > 2) Alert + Stop receiving route: Alert triggered, no extra route accepted.
unless it repeats the alert for every bgp packet received with announcement nlri (log coalescing/throttling permitted), that sounds like a terrible action. I expect that otherwise the event might (will) pass unnoticed. > 2. Generally to protect network from impact of route leaking, based on > my experience only relying on prefix limit mechanism is not enough. > Reason include: > > 1) Prefix limit is usually neighbor basis, while route leaking could > happen on multiple neighbors together. > > 2) Consideration also need include devices on POP that receive all > internet routes from internet gateway via RR. Such devices could hold > multiple services not only just BGP. > > In such case, either a BGP process based or global based memory&CPU > protection mechanism is needed. seems to be common sense and out of scope. _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
