Hello all, I’ve been going over draft-ietf-grow-bmp-rel and it does provide an excellent way to provide additional visibility into the BGP process.
However, I noticed it doesn’t cover the cases in RFC 7606. RFC 7606 refines that update error handling in RFC 4271 and classifies update errors handling approaches into 4 categories: 1. Session Reset (as original in RFC 4271 and that will be caught in BMP using the BGP Notification message) 2. AFI/SAFI disable 3. Treat-as-withdraw 4. Attribute-discard My guess for cases 2 and 3, if local rib monitoring is enabled BMP will report a withdraw, without a reason of why. For case 4, not sure if that will be reported in BMP. Probably these events need to be monitored by BMP, since they impact the routing and can be silent (except vendor specific logging). I’m not sure if draft-ietf-grow-bmp-rel is the best place or we need an additional document to expand further the list of supported events, any feedback is welcome. Best, -Ahmed
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
