I am familiar with an implementation which supports echo and reduces rate of control packets when echo is enabled. In that implementation, the configuration has desired interval and multiplier, there isn¹t different timer configurations for async and echo. Echo is enabled by default but there is config knob to disable echo. The operational model does show the rates at which control and echo packets are being transmitted.
But back to Greg¹s original question, I¹d like to hear from other BFD implementations which support echo. Is echo enabled "on demand² e.g. For a small duration like ping, or is it continuous? Regards, Reshad. On 2017-03-24, 3:28 PM, "Jeffrey Haas" <[email protected]> wrote: > >> On Mar 24, 2017, at 3:09 PM, Greg Mirsky <[email protected]> wrote: >> >> Hi Carlos, >> indeed, the RFC 5880 does explain that the rate of BFD control packets >>transmitted in Async mode may be reduced when Echo is activated. If >>anyone is familiar with such implementation, I'd be glad to learn and >>discuss how this mechanism affects the data model. Regrettably, I don't >>have personal experience with using or implementing such mechanism. > >My *suspicion* is that the configuration would represent a set of >parameters for both async mode and echo mode. These will not alter >themselves automatically. > >The operational mode might reflect timers that have backed off. However, >this is also true if an implementation does various forms of session >auto-tuning. An example I'm aware of is a decrease in timer >aggressiveness as part of a high availability switchover event. > >-- Jeff >
