Hi,
Appropriate caution SHOULD be taken when picking routing events to
report, as next-hop related updates may produce heavy message loads
during network instability. Mitigation measures SHOULD be deployed
on both reporting and receiving sides. For example, local endpoints
can apply event filtering controls, while receivers maintain
corresponding processing mechanisms to handle potential high-volume
event bursts gracefully.
During the meeting today the text above was highlighted by Nan (based on
feedback from Prasad). I have no issue with the feedback and text, but is there
any indication of filtering sent to the collector?
draft-ietf-grow-bmp-adj-ribs-filtered which was presented earlier adds a Peer F
flag for Adj-Rib-In/Out, IIUC that doesn't cover events in
draft-geng-grow-bmp-rel-enhancement? IMO we want indication of filtering for
"critical" events.
Regards,Reshad.
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
