Re: [babel] Example configuration

[Toke Høiland-Jørgensen <[e-mail]>]

Mahesh Jethanandani <[e-mail]> writes:

> Hi Toke,
>
>> On Aug 8, 2019, at 7:04 AM, Toke Høiland-Jørgensen <[e-mail]> wrote:
>> 
>> Why is this complexity needed? Couldn't it just be solved in the user
>> interface, something like:
>> 
>> An input form contains these four entries:
>>          [string               rw babel-interface-metric-algorithm;]
>>          [boolean               rw babel-interface-split-horizon;]
>>          [boolean               rw babel-interface-rtt;]
>>          [boolean               rw babel-interface-unicast;]
>
> While seemingly more complex, it is not. First of all, with your
> proposed schema, if you need the same presets for multiple interfaces,
> you would be having to repeat them for multiple interfaces. Secondly,
> there is no way in YANG to define a set of presets, so there will be
> no drop down menu to select from.

These both sound like UI issues rather than configuration protocol
issues. I'm not familiar with how YANG works, but from this it sounds
like a UI cannot deviate from what is defined in the YANG model?

> We were going to document the three or four well known presets.
> Thirdly, while these names and values may make sense to us, they may
> not to an operator, who might want to configure their own set of
> presets.

But how does this work in the case where nothing is set on the
management interface, the implementation auto-detect the interface type,
and fills out the defaults based on the type? As Juliusz explained, the
preset keyword cannot generally be inferred from the set values, so what
is the info model / management interface supposed to do in this case?

-Toke