6 Feb
2018
6 Feb
'18
4:55 p.m.
Ondrej Zajicek <santiago@crfreenet.org> writes:
On Tue, Feb 06, 2018 at 05:20:25PM +0100, Toke Høiland-Jørgensen wrote:
It's mandatory, otherwise you can get routing loops. See https://tools.ietf.org/html/draft-ietf-babel-source-specific-03#section-6
I figure the packet parser needs to be aware of whether it is configured to support SADR routes and drop all source-specific updates if not...
OK, so there is no need to have separate option, it could be handled just by which channel type is defined.
Yeah, that was my thought. Will add that :) -Toke