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

[Omprakash Gnawali]

There are two problems with the timer that controls the routing beacon rate:

1. Incorrect remaining time calculation. We think this is an easy fix
as discussed during last week's teleconference.

2. Triggered route updates using the same timer as Trickle timer. We
thought we would be able to fix this by calling resetInterval()
instead of starting the timer when we need to generate on-demand
beacons. This will ensure that there is only one way to change the
Timer. Unfortunately, this will not work - we want to control how long
to wait until we send a beacon in case of on-demand beacons depending
on the situation (trigger update vs trigger immediate update), not
possible using a single resetInterval() call.

It looks like we need two different pathways to set this timer.

If it is an on-demand timer, set trickle currentInterval to
min-interval, but make the delay until the first timer to be the delay
corresponding to trigger update or immediate update. We can call this
resetIntervalAndWait(). When the timer fires after the wait interval,
exponential decay can start.

Does this work?

- om_p