Hi Robert, Yes, but only for the RIB dump (on initial PEER_UP and for each route-refresh) till EoR. Senders shouldn’t state compress after that, especially for Adj-RIB-In Pre-Policy. State compression should be optional. State compression is not required for the RIB dump or at any time, but it does help deal with churn while the RIB dump is in progress.
Thanks, Tim On 9/20/22, 10:52 PM, "Robert Raszuk" <[email protected]> wrote: Hi Paolo, A-la: there is multiple updates related to a certain NLRI by when a BMP message is to be sent out, let's state-compress (ie. not send out) those that were already obsoleted by a subsequent update. But this will hide BGP churn for a given NET to be detectable by BMP receiver. Is this a good thing ? I am not sure. It is a loss of information to me. Thx, R.
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
