|
of course it needs jitter. Now trickle is armed anyway at
all times right (T timer). If we do not do anything specific, the DIO will not
come earlier with DIS than without...
So if no immediate response is needed, then DIS is not
needed. I still think it is, for instance anytime you lose you r last parent,
and do not want to wait possibly hours to get a DIO. This is the same as with
RS/RA (jittered !)
Resetting trickle (I to Imin, and T to random ) does not
make sense I guess, as sending a DIS does not always mean global instability.
Thoughts on how to arm a small jittered timer?
Best,
Julien
At
the moment, I cannot figure when an immediate response would be needed.
I
think Phil mentions that somewhere else as well. The idea would be to arm
trickle and let it time out.
Also
let us keep in mind that in networking at large, most timers are jittered to
avoid network synchronizations. In wireless, it is even worse since as you
point out, synchronization also means collisions.
Pascal
From:
roll-bounces at ietf.org [mailto:roll-bounces at ietf.org] On Behalf Of
Julien Abeille (jabeille)
Sent: lundi 2 novembre 2009
18:01
To: ROLL WG
Subject: [Roll] need clarification: DIS
processing
when a router
receives a DIS, should it answer right away? I guess this is a good source of
collision, so a random timer would help. Could we set T to a random value
between I_min /2 and I_Min, without resetting I (receiving a DIS does not
mean inconsistency)?
|
