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

[Dean Luga]

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.

On 7 Mar 2017 11:41, "Toke Høiland-Jørgensen" <toke at toke.dk> wrote:

> Dean Luga <dluga93 at gmail.com> writes:
>
> > I used the configure switch since SADR makes changes to the LSAs and
> > it will slightly impact network traffic even with source 0::/0. If
> > someone doesn't want that, they can disable it.
>
> As in, when you enable SADR all routes announced now carry a SADR? Does
> that mean bird with SADR enabled will no longer compatible with an OSPF
> implementation that does not understand? And if so, is this inherent in
> the OSPF SADR extension, or is this a design choice of your
> implementation?
>
> -Toke
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20170307/718e6cf4/attachment.html>