Re: [babel] Example configuration

[Juliusz Chroboczek <[e-mail]>]

>> The protocol doesn't know about interface types.  From the point of view
>> of the protocol, there are a number of algorithms that can optionally be
>> selected or enabled on a given interface.  These include:
>> 
>> - link-quality estimation (2-out-of-3 or ETX);
>> - split-horizon (on or off);
>> - RTT estimation (draft-ietf-babel-rtt);
>> - use of unicast instead of multicast;
>> - ...

> In -08 version of the draft, all references to wired, wireless, tunnel
> and others are gone. That in addition to babel-link-properties. If they
> are underlying parameters, they are truly invisible :-).

Wired, wireless etc. are the UI interface types.  The underlying
properties are link-quality and split-horizon (in RFC 6126bis) and the RTT
estimation parameters (in draft-ietf-babel-rtt).

> I understand that it is difficult for an operatori without intimate
> knowledge to know how to configure these properties. And that is why
> these should be optional properties. However, without them, there is no
> way for an operator to influence how the protocol works.

I think we're not understanding each other.  I am not arguing about hiding
any information, quite the opposite, I am in favour of exporting the
underlying properties and leaving the link type to the UI.

>> I don't think we have the manpower to do a good job.

> Ok. Let me follow up on the separate e-mail thread that you started with
> describing Babel filtering and routing policies. If it becomes too
> complex, we can drop it.

Sure, but please keep my comment about manpower in mind.

-- Juliusz