We started off with the intent of having BFD parameters in the applications/protocols which make use of BFD. For timer/multiplier this is pretty straight-forward, although the discussion of what to do when not all applications have the same BFD parameters for the same session (e.g. Go with most aggressive etc). Then we started looking at authentication parameters and having BFD authentication parms in OSPF/ISIS etc is not intuitive. And what do we do if applications have different BFD authentication parms. We concluded that the BFD authentication parms were better off in BFD. And once we did that, the timer/multiplier followed....
I may not recall all the details/discussons, but I do recall that we went back and forth on this and it took some time to make the decision. Regards, Reshad (as individual contributor). From: Mahesh Jethanandani <[email protected]<mailto:[email protected]>> Date: Thursday, May 18, 2017 at 5:34 PM To: "Acee Lindem (acee)" <[email protected]<mailto:[email protected]>> Cc: Jeffrey Haas <[email protected]<mailto:[email protected]>>, OSPF WG List <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: IETF OSPF YANG and BFD Configuration Resent-From: <[email protected]<mailto:[email protected]>> Resent-To: <[email protected]<mailto:[email protected]>>, Reshad <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>> Resent-Date: Thursday, May 18, 2017 at 5:40 PM Resending with correct BFD WG address. On May 18, 2017, at 2:33 PM, Mahesh Jethanandani <[email protected]<mailto:[email protected]>> wrote: Agree with Acee's assessment. After much debate, we decided that we should leave BFD parameter configuration in the BFD model itself, and have any IGP protocol reference the BFD instance in BFD itself. This makes sense specially if multiple protocols fate-share the BFD session. Cheers. On May 18, 2017, at 12:27 PM, Acee Lindem (acee) <[email protected]<mailto:[email protected]>> wrote: Hi Jeff, At the OSPF WG Meeting in Chicago, you suggested that we may want to provide configuration of BFD parameters within the OSPF model (ietf-ospf.yang). We originally did have this configuration. However, after much discussion and coordination with the BFD YANG design team, we agreed to leave the BFD session parameters in BFD and only enable BFD within the OSPF and IS-IS models. We did discuss the fact that vendors (notably Cisco IOS-XR and Juniper JUNOS) do allow configuration within the IGPs. However, the consensus was to leave the BFD configuration in the BFD model. The heuristics to determine what parameters to use when the same BFD endpoint was configured with different parameters in different protocols were proprietary and somewhat of a hack. I may have not remembered all the details so I'd encourage others to chime in. Thanks, Acee Mahesh Jethanandani [email protected]<mailto:[email protected]> Mahesh Jethanandani [email protected]<mailto:[email protected]>
_______________________________________________ OSPF mailing list [email protected] https://www.ietf.org/mailman/listinfo/ospf
