Re: [Roll] [roll] #165 (applicability-home-building): DIO max interval

peter van der Stok <> Fri, 14 November 2014 00:01 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 980DF1AE37C for <>; Thu, 13 Nov 2014 16:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VBnZEMsG7caP for <>; Thu, 13 Nov 2014 16:01:45 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 67B981AE380 for <>; Thu, 13 Nov 2014 16:01:39 -0800 (PST)
Received: from ([]) by with ESMTP id FC1d1p00D4Hiz6i01C1dCe; Fri, 14 Nov 2014 01:01:37 +0100
Received: from ([2001:67c:370:160:f829:bdf2:26b2:69cc]) by with HTTP (HTTP/1.1 POST); Fri, 14 Nov 2014 01:01:37 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Nov 2014 01:01:37 +0100
From: peter van der Stok <>
Organization: vanderstok consultancy
In-Reply-To: <>
References: <>
Message-ID: <>
X-Sender: (krs3n0iB2ll3S+DEhAeNojffzHWL2JHw)
User-Agent: XS4ALL Webmail
Subject: Re: [Roll] [roll] #165 (applicability-home-building): DIO max interval
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To:, Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Nov 2014 00:01:47 -0000

Hi Yvonne,

In RFC 6206 (trickle), the introduction explains:
  "When a node's data does not agree with its
    neighbors, that node communicates quickly to resolve the
    inconsistency (e.g., in milliseconds).  When nodes agree, they slow
    their communication rate exponentially, such that nodes send packets
    very infrequently (e.g., a few packets per hour)."

We propose to add the following text to section 4.3.1.

When a node sends a changed DIO, this is an inconsistency and forces the 
receiving node to respond within Imin.
So when something happens which affects the DIO, the change is ideally 
communicated to a node n hops away within n times Imin.
Often, dependent on the node density, packets are lost, or not sent, 
leading to larger delays.
In general we can expect that DIO changes to propagate within 1 to 3 
seconds within the envisaged networks.

When nothing happens, the DIO sending interval increases to 4.37 
minutes, thus drastically reducing the network load.

When a node does not receive DIO messages during more than 10 minutes it 
can safely conclude the connection with other nodes has been lost.


roll issue tracker schreef op 2014-11-10 23:12:
> #165: DIO max interval
>  Yvonne-Anne Pignolet:
>  Please state why a value of DIO max interval of 4.37min (16ms x
>  2^14) is appropriate, it seems like a much smaller value would be
>  suitable for this usecase
>  Peter van der Stok:
>  I don't understand the issue here. When something happens the 16 ms 
> come
>  into play. Assuming a limited number of hops, the change propagates 
> quite
>  timely.
>  When nothing happens, sending a reminder every 4 minutes seems quite
>  reasonable. (we are discussing propagation of network changes, not 
> user
>  commands)
>  Yvonne-Anne Pignolet:
>  Until it is noticed that some happened a long time may pass because of 
> the
>  low DIO frequencey