[PATCH 1/9] Adding configuration option --enable-sadr.

[Toke Høiland-Jørgensen]

Dean Luga <dluga93 at gmail.com> writes:

> That is correct, it will not be compatible with other OSPF implementations.
>
> From what I've searched, there is no standard for supporting SADR in
> OSPF, only some IETF drafts (some of which expired) that describe the
> desired behavior.
>
> One or two of these drafts plan to use OSPF extended LSAs to support
> SADR, but the extended LSAs are also still drafts, and I am not sure
> they would cooperate with the current ospf standard.
>
> So yes, the design details are mine, but they are based on the OSPF
> behavior specified in these documents.

Ah, I see. Well, for compatibility with the Babel SADR extension, it
would be good if at least the nest support could be done via separate
data structures (Ondrej's suggestion of a separate address family is not
a bad one). The Babel protocol specifies an extension TLV for SADR
routes that can co-exist with non-SADR routes in the same network. Would
need to support that in Bird as well, so please take that into account
when you modify the Bird core :)

-Toke