[homenet] my mic comment on routing protocol interop...

[Dave Taht <[e-mail]>]

What I'd meant at the microphone concerning "interoperability",
was not at the protocol level, but at the daemon level. We have
separate forks of quagga (for ISIS with source sensitive routing),
bird (for ospfv3), stand alone daemons like babels (which also has a
quagga-babel version, but I think it's from another quagga branch than
the ISIS work) and entirely separate daemons for the various other IoT
devices.

So far as I know the quagga-babel"s" work hasn't started yet. Is there
work on source sensitive ospf for quagga?

How big is all this stuff? (memory/flash?)

It IS a headache to deal with all these different daemons and stuff
flying in loose formation, and so I hope more folk pitch in to
stabilize the code (pick a codebase, any codebase... ) to get it
beyond "proof of concept" stage.

... and it would be nice to be able to evaluate each routing
protocol's configurability (and/or lack thereof, which I'd weight in
favor of) convergence time, reliability, wire usage, wireless usage,
and the source specific features...

Anyone for OLSRv2?

/me ducks

-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article