Hi Les,
On Tue, Jul 23, 2019 at 08:29:30PM +0000, Les Ginsberg (ginsberg) wrote: > [...] As network-wide convergence depends upon fast propagation of LSP > changes - you're losing me between that previous part and the next: > - which in turn requires consistent flooding rates on all interfaces > enabled for flooding [...] I understand and follow your reasoning if we have a classical timer that limits flooding rates per LSP. If we get multiple updates to the same LSP, dissimilar flooding rates imply we might just have sent out the previous now-outdated state, and we block for some potentially lengthy time before sending out the most recent version of that LSP. I don't understand how we get delayed propagation of LSP changes if we employ some mechanism to raise the flooding rate to something based around the target system's capabilities. Could you elaborate on how we get delayed LSP propagation in this scenario? Thanks, -David _______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
