Authors, It's good to see the ability to create snapshots, especially in combination with the additional proposal on MRT recording, getting discussed for BMP.
A challenge that dealing with a snapshot request in the midst of receiving a live BMP feed is distinguishing a topology change event from a route that is simply being re-sent in order to provide the snapshot. One possible way to address this ambiguity is to include a boolean TLV that says "this is a snapshot". By direct analogy, if you were sending a route solely because of a "route refresh" type snapshot behavior, this is distinct from a topology change. It's possible that many applications consuming BMP will not care about the distinction. However, for route monitoring purposes for live Internet data, I suspect this distinction might be useful. When done for MRT files, the long practice of "here's the dump file" and "here are the updates" should be preserved. In such a case, the regular dump file is distinct by name, rather than contents. -- Jeff _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
