On 01/11/2019 19:04, Jeffrey Haas wrote: > The one addition I'd suggest for the document is that information about > peer-up/down messages is needed to usefully decode some information or > context about the other BMP messages. You'll want a bit of operational > procedure in your text about "please save this bit of state in each file".
Indeed I was thinking about that as I wrote it. Maybe adding MRT subtypes like the BGP4MP type uses, to indicate state changes. The one I specifically thought of was the establishment and teardown of the BMP TCP connection. As I understand BMP, the termination message is optional, and of course the TCP connection could go down for other reasons. So preserving the fact that the session went down, would be useful there. Thanks, Colin _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
