Hi, John, On Wed, Nov 4, 2015 at 2:43 PM, John G. Scudder <[email protected]> wrote:
> On Oct 15, 2015, at 1:03 AM, Spencer Dawkins < > [email protected]> wrote: > > I found myself wondering when you can start route mirroring, > > I think the answer is "pretty much any time" following the Initiation and > Peer Up. It's true this isn't written down anywhere. I propose adding this > to the end of S 4.7: > > A Route Mirroring message may be sent any time it would be legal to > send a Route Monitoring message. That's helpful. Thanks! > > and whether > > there was any guidance about what to do when a BGP speaker runs out of > > buffers so that route mirroring is no longer complete. > > Yes, there is. You send one of these: > > o Type = 1: Information. A two-byte code that provides information > about the mirrored message or message stream. Defined codes are: > ... > * Code = 1: Messages Lost. One or more messages may have been > lost. This could occur, for example, if an implementation runs > out of available buffer space to queue mirroring messages. Got it. I'm sorry for not being clearer. I meant "what to do AFTER a BGP speakers runs out of buffers so that route mirroring is no longer complete". So, Code = 1: Messages Lost. Do you wait before trying to resynchronize, for instance? Or is retrying immediately OK? Stuff like that. Spencer
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
