Hello all,
I second Thomas Graf, these are important metrics to monitor. However, I would
approach it slightly differently:
- Max configured number of prefixes for AFI/SAFI
- Current used number of prefixes for AFI/SAFI.
- Absolute max or Hardware max (if applicable) for AFI/SAFI.
And would
Hi Thomas,
Thanks for your comment. I see your need for these reason codes and i
will include them in the next revision of the draft -- the more
event-driven use-cases for REL, the better.
As i may have said before, I also like that counters make it to the
Stats message as i regard Stats
Dear Paolo and Camilo,
I have a comment on Section 3.3.1 of draft draft-lucente-grow-bmp-rel
(https://datatracker.ietf.org/doc/html/draft-lucente-grow-bmp-rel-03#section-3.3.1).
Please consider to add two additional event reason codes as described below.
As described in my previous post to the
