[net2-wg] problem with the timer that controls routing beacon rate in CtpRoutingEngineP.nc

[Omprakash Gnawali]

On Wed, Mar 19, 2008 at 9:26 AM, Philip Levis <pal at cs.stanford.edu> wrote:
>
>  On Mar 19, 2008, at 12:01 AM, Omprakash Gnawali wrote:
>
>  >
>  > There are three firing patterns - Trickle, trigger (64ms) and
>  > triggerImmediate (4ms). I don't understand how we can accommodate
>  > these three patterns by just resetting unless we are willing to set
>  > tau_l to 4ms. But setting tau_l to 4ms would be an overkill if it is
>  > parent change that triggers a beacon. Or we change triggerImmediate to
>  > trigger so that we can have a more reasonable tau_l of 64ms.
>  >
>  > - om_p
>
>  What I'm saying is that there's no evidence that the two fast
>  patterns are the right ones: we just stuck them in as hacks. So let's
>  simplify the protocol to use a single pattern (Trickle) and then see
>  how that works.
>
>  Why does a parent change trigger a beacon? It should only trigger a
>  beacon if the gradient changes significantly. The way to think of it
>  is that a node sees a trickle "inconsistency" when the routing
>  gradient changes a good deal (particularly, goes up).
>
>  Phil
>

Because I am not the owner of this file, I wanted to have these
discussions before making changes. Alright, I will see what happens
with a single Trickle pattern with a tau_l of 64ms. If that is bad, I
can try increasing tau_l.

- om_p