FWIW I think I ended up capturing much of that in the erratum I submitted — but this conversation also illustrates why the fix has to be a new WG doc and not just an erratum.
Thanks, —John On Sep 14, 2022, at 4:55 PM, Jeffrey Haas <jh...@pfrc.org> wrote: On Sep 14, 2022, at 2:36 PM, John Scudder <j...@juniper.net<mailto:j...@juniper.net>> wrote: That’s cleaner but now the monitoring station has to go to the (minor?) trouble of keeping track of EoRs and reconciling them against AFs supported on the session. Yet another option would be to introduce a BMP-specific “end of initial BMP convergence” message that does what the current text suggests — a single message to say “done". That one smells the best to me, at the moment. It’s also the most intrusive. Speaking as someone who soaks in how some customers use BMP, the per-AFI/SAFI end of rib is a feature rather than a bug. BMP already serves to push the firehose of a router down a drinking straw. Being able to tell you're done with one address family is helpful to let some things come to convergence rather than waiting on everything. The other headache of the single "I'm done" bit is the consequence on trying to get all of the per-AFI/SAFI queues to be done at the same time. For example: IPv4 unicast is done, no EoR is sent. IPv6 unicast starts doing its work. IPv4 unicast has more churn go through IPv6 unicast is done, no EoR is sent. System needs to go back to trying to get IPv4 unicast done to send EoR. Pray that nothing else changes... -- Jeff
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
