RPL enables non-equal cost multipath, Alia. That's the reasonable thing (a MUST 
if you ask me) to do with wireless connectivity when delivery is statistical 
and metrics can only provide a limited approximation of transmission chances.

Any DV can do that easily so we should be able to do it with Babel as well. 
That's called feasible successors in EIGRP.

When things move quickly or conditions change rapidly then you want to trade 
routing stretch with route quality, which means that in the NECMP routes that 
you get, it may be that none is shortest path. RPL allows to decide how many 
and which destinations will benefit from shortest path while others will get 
stretched routes, and that's the only protocol that can do that on the table 
and in the whole house. This is how RPL addresses MANET in a really efficient 
manner.

When devices get critically limited in memory, RPL allows to switch to source 
routing. Again the only protocol on the table that can do that built in. 

When bandwidth is critically limited (any powerline around?) then the 
capability to fix routes reactively, that is only when traffic is sent on a 
broken routing zone, becomes a treat. Built in RPL, nowhere else to be found.

RPL can build different routing instances to reach different gateways or reach 
then with different optimizations. The former can be done with 
source/destination routing but the latter is only available with multi topology 
routing, which may be available in some specific vendors versions of ISIS and, 
well, is built in RPL.

When only few routes are needed, but could need to be maintained aggressively, 
RPL has an experimental reactive method akin to AODV call P2P.
Any route at home that needs special treatment like a control loop? 
 
Sadly none of these questions is really on the table for Homenet though they 
were all requirements for ROLL; fact is we have a std track protocol that can 
do it all, that is implemented in openWRT and openWSN, and 3 other 
implementations which run on a few Ks of memory and were tested for interop in 
Prague.

All the best,

Pascal

> Le 11 août 2015 à 19:47, Alia Atlas <[email protected]> a écrit :
> 
> I am interested to learn what people think about whether equal-cost 
> multi-path routes are needed in homenet.  Given the previous discussion about 
> parallel wireless links - which I know I have in my house and can't use - 
> I've been wondering if these have been considered.
> 
> ECMP is critical in the data-center and backbone, but I'm interested in 
> seeing what the reasoning is as to why it isn't or is needed in the homenet 
> scenarios.
> 
> Thanks,
> Alia
> 
> P.S. I do expect that any routing protocol can be made to do ECMP, of course.
> _______________________________________________
> homenet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/homenet

_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to