<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>On 03/07/2017 09:23 PM, Toke Høiland-Jørgensen wrote:
<br>
</p>
<blockquote type="cite" style="color: #000000;">Basically, I want to
do the opposite: We are going to have several
<br>
(well, at least two) protocols that understand source-specific
routing,
<br>
so the nest data structures should work with both. And since Babel
at
<br>
least is perfectly happy to mix source-specific and regular routes
(and
<br>
will interoperate with an implementation that only supports the
latter),
<br>
the nest data structures and lookup functions shouldn't be hidden
behind
<br>
a configure switch (but the OSPF support might be I guess, unless
you
<br>
can make it run-time configurable without too much hassle).
<br>
<br>
<blockquote type="cite" style="color: #000000;">1. the fib_node
structure having a couple more data fields. If a protocol
<br>
doesn't use them, this data won't hurt it, right?
<br>
</blockquote>
Some data structure overhead is probably fine.
<br>
<br>
<blockquote type="cite" style="color: #000000;">2. fib_get,
fib_find, fib_route, net_get, and net_find functions might
<br>
do some more processing, but they should ultimately have the
same
<br>
behavior.
<br>
</blockquote>
Yeah, the behaviour for non-source-specific routes should be
unchanged,
<br>
and it should do something sensible when both types of routes
exist.
<br>
Haven't gotten around to thinking seriously about how I'd
implement
<br>
source-specific routing for Babel in Bird yet, so you're kinda
breaking
<br>
new ground here; but happy to be a voice in the background at
least <span class="moz-smiley-s3" title=";)"></span>
<br>
<br>
-Toke
<br>
</blockquote>
<br>
Oh, I see what you mean. Since Babel works better with SADR, the
nest changes should be more focused on Babel, <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>then<span
class="moz-txt-tag">*</span></b> OSPF should make use of them.
Instead of the other way around.
</body>
</html>