> Your definition of the worst-case here is slightly pessimistic I believe
> (c.f. appendix B changenotes); in practise, as Trickle reset occurs if and
> only if _locally_ calculated network state changes,
I've obviously missed something. RFC 6206 says
6. If Trickle hears a transmission that is "inconsistent" and I is
greater than Imin, it resets the Trickle timer. To reset the
timer, Trickle sets I to Imin and starts a new interval as in
step 2. If I is equal to Imin when Trickle hears an
"inconsistent" transmission, Trickle does nothing.
If I read this correctly, I will never exceed I_min * 2.
> it does not cause network-wide problems nor any real state churn beyond
> extra unicast packets that are essentially ignored or replied to and
> then ignored.
I'm probably missing something again. If node A has two neighbours B and
C that reply with different data for node D, what avoids persistent churn
at A?
-- Juliusz
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
