Re: [homenet] draft-boutier-homenet-source-specific-routing-00

[Henning Rogge <[e-mail]>]

I think the last paragraph of Section 4.1 is not necessarily true for
all protocols. You might end up with "non-source route" aware routers
that forward the source-route specific information.

Still, as long as the different destinations for the source-routed
default-routes are in a source-route aware subnet it should work. The
"non source-routed" default route will push the traffic into the
"source-route aware" subnet... and from there to the destination.

It should work both with distance-vector and linkstate routing as long
as there is also a "non-sourcerouted" default route.

Henning Rogge

On Tue, Jul 9, 2013 at 5:14 PM, Juliusz Chroboczek
<[e-mail]> wrote:
>> > The general answer is no -- incompatible forwarding behaviours cause
>> > persistent routing loops (Section 2.2.2).  However, there are
>> > particular cases where everything works out, most importantly mixing
>> > source-specific and ordinary next-hop routing (Section 4.1).  (Please
>> > do not underestimate the importance of this property -- what it says
>> > is that you can mix "legacy" routers with source-specific ones.)
>
>> Having multiple source-specific default routes (0.0.0.0/0 or ::/0) are
>> a good recipe for routing loops if some routers don't support
>> source-specific routing.
>
> See Section 4.1, notably the second paragraph.
>
> (And yes -- you get it wrong, you die.)
>
> -- Juliusz



-- 
We began as wanderers, and we are wanderers still. We have lingered
long enough on the shores of the cosmic ocean. We are ready at last to
set sail for the stars - Carl Sagan