Re: [Roll] Revisiting the Trickle Algorithm

peter van der Stok <stokcons@xs4all.nl> Tue, 20 January 2015 15:06 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 456F71B2DB8 for <roll@ietfa.amsl.com>; Tue, 20 Jan 2015 07:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level:
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TJdiJzXY4Aqs for <roll@ietfa.amsl.com>; Tue, 20 Jan 2015 07:06:35 -0800 (PST)
Received: from lb2-smtp-cloud2.xs4all.net (lb2-smtp-cloud2.xs4all.net [194.109.24.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4985A1B2DC2 for <roll@ietf.org>; Tue, 20 Jan 2015 07:06:24 -0800 (PST)
Received: from roundcube.xs4all.nl ([194.109.20.205]) by smtp-cloud2.xs4all.net with ESMTP id iF6J1p00Q4RV18J01F6JQ6; Tue, 20 Jan 2015 16:06:21 +0100
Received: from AMontpellier-654-1-111-203.w90-0.abo.wanadoo.fr ([90.0.86.203]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Tue, 20 Jan 2015 16:06:18 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 20 Jan 2015 16:06:18 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <CAPm4LDRFqO4AhrPJjgWfn9e_XncFFYsZ=ZgkMcdvJNpaBFrc2g@mail.gmail.com>
References: <CAPm4LDTj3-ZTZGi86ttgqNuTSRnEBUY59rAnxmr_DMvuhNWGGA@mail.gmail.com> <CAErDfUSewgX8i-qrZUTAv6S-7XQ5Vu2O5Z1qj0pUT=akwg3MiA@mail.gmail.com> <CAPm4LDRY4dUYgshFN96eJbOT4Fv18N9yOQBXeO23akRmdQ_KVg@mail.gmail.com> <CAPm4LDRFqO4AhrPJjgWfn9e_XncFFYsZ=ZgkMcdvJNpaBFrc2g@mail.gmail.com>
Message-ID: <a5a973822c943cd683984b5b3cacf57d@xs4all.nl>
X-Sender: stokcons@xs4all.nl (rhH3DdqOkpOMgmOk0YY5+fhYpiVx2pBJ)
User-Agent: XS4ALL Webmail
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/Gp4vIH07sj2-l_DWT29v9HsixXk>
Cc: badis DJAMAA <badis.djamaa@ieee.org>, JeongGil Ko <jgko@cs.jhu.edu>, "Thomas Heide Clausen \(work\)" <T.Clausen@computer.org>, Jonathan Hui <jonhui@cisco.com>
Subject: Re: [Roll] Revisiting the Trickle Algorithm
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: consultancy@vanderstok.org, Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 15:06:45 -0000

Dear all,

I like to draw you attention to the following articles.
In these articles calculations are done on the optimal MPL interval 
division with the aid of queuing networks.

In the masters thesis "Modeling and Simulating the Trickle algorithm" 
(http://alexandria.tue.nl/extra1/afstversl/wsk-i/meyfroyt2013.pdf ) by 
T.M.M. Meyfroyt (August 2013) propagation delay and message overhead for 
Trickle and "Short-Trickle" are compared by simulations and analysis in 
single-hop and multi-hop networks.

The paper "Data Dissemination Performance in Large-Scale Sensor 
Networks" (http://dl.acm.org/citation.cfm?id=2591981 ) by T.M.M. 
Meyfroyt, S.C. Borst, O.J. Boxma, D. Denteneer (June 2014), analyzes the 
message overhead of the original Trickle algorithm compared to the 
"Short-Trickle algorithm". An extended journal version of this paper has 
been submitted to QUESTA (and has been attached in this email).

In the paper "A Data Propagation Model for Wireless Gossiping" 
(http://arxiv.org/abs/1407.6396)  by T.M.M. Meyfroyt, S.C. Borst, O.J. 
Boxma, D. Denteneer (Juli 2014), an extension to the Trickle algorithm 
is proposed, similar to the "New Trickle algorithm" and its performance 
is analyzed and compared to that of the original Trickle algorithm. This 
paper has recently been accepted in Performance Evaluation 
(http://www.sciencedirect.com/science/article/pii/S0166531615000024).

Hope this is useful.

Greetings,

peter


Badis Djamaa schreef op 2015-01-20 00:43:
> Thank you Gnawali for your comments,
> 
>> Could you discuss the tradeoffs due to the proposed modification? Are
>> there some scenarios that will be worse off due to the changes?
> 
> Figure1, page 2 of the document, shows the scheme in its best-case
> (lossless networks). From that Figure, we can see a side-effect of the
> proposed scheme which can add an extra cost in lossy-networks.
> 
> Figure 4 in page 4, clearly shows this side-effect in lossy networks.
> But results in Figure 5 ( network with 90% physical loss rate) shows
> that the extra cost only affects a few following intervals and
> disappears later. Also Figure 5 shows that this additional cost does
> not affect trickle scalability.
> 
> When generating heavy inconsistencies (periodically injecting new
> packets), testbed results depicted in third row of graphs in Figure 6,
> page 4, shows a bigger additional cost because of heavy inconsistent
> traffic being generated.
> 
>> Did you consider minor variations to your scheme - e.g., rather than
>> just the first interval starting at 0, how about the first n
> intervals
>> starting at 0 rather than I/2?
> 
> Because of the side-effect depicted in Figure 4, the additional cost
> increases if we go for n intervals. Generally speaking, Trickle's
> scalability might remain logarithmic, because the extra cost only
> depends on losses. However, the extra cost is noticeable under heavy
> inconsistent traffic and wastes energy.
> 
> Note however, that we made a small variation to the scheme by letting
> a node that transmitted in an Imin interval to start listening
> immediately (put c=0). Preliminary results look promising and show
> that the side-effect can be addressed.
> 
> More results are being analysed to see whether other side-effects can
> emerge.
> 
> Best, badis
> 
> On 19 January 2015 at 15:01, Omprakash Gnawali <gnawali@cs.uh.edu>
> wrote:
> 
>> It is a good idea to explore how to make Trickle work better.
>> 
>> Could you discuss the tradeoffs due to the proposed modification?
>> Are
>> there some scenarios that will be worse off due to the changes?
>> 
>> Did you consider minor variations to your scheme - e.g., rather than
>> just the first interval starting at 0, how about the first n
>> intervals
>> starting at 0 rather than I/2?
>> 
>> It will be useful to poll the community what they use for Imin and
>> do
>> experiments with similar Imin.
>> 
>> - om_p
>> 
>> On Mon, Jan 19, 2015 at 7:51 AM, badis DJAMAA
>> <badis.djamaa@ieee.org> wrote:
>>> Dear all
>>> 
>>> We have been working with Trickle for more than two years. A
>> 4-page document
>>> available here https://dspace.lib.cranfield.ac.uk/handle/1826/9033
>> [1] shows
>>> that by a simple modification to Trickle, a great decrease in the
>>> propagation time can be achieved without affecting Trickle's
>> scalability.
>>> 
>>> The results are backed by extensive simulations and large-scale
>> testbed
>>> experiments. In-depth explanation along with more extensive
>> results are
>>> under analysis to be announced very soon.
>>> 
>>> In a nutshell the modification recommends to change step 2,
>> section 4.2. of
>>> RFC6206 as follows
>>> 
>>> Old:
>>> 
>>> 2. When an interval begins, Trickle resets c to 0 and sets t to
>> a
>>> random point in the interval, taken from the range [I/2,
>> I), that
>>> is, values greater than or equal to I/2 and less than I.
>> The
>>> interval ends at I.
>>> 
>>> New:
>>> 
>>> 2. When an interval begins, Trickle resets c to 0 and sets t to
>> a
>>> random point in the interval, taken from the range:
>>> 
>>> o [0, Imin) if the interval began as result of step 6
>>> (because of an inconsistency or external events).
>>> 
>>> o [I/2, I), otherwise(the interval began because of step 1 or
>> step 5)
>>> 
>>> The rationale behind this modification is briefly explained here
>>> https://dspace.lib.cranfield.ac.uk/handle/1826/9033 [1]
>>> 
>>> any comment is warmly welcomed
>>> 
>>> All the best
>>> badis
> 
> 
> 
> Links:
> ------
> [1] https://dspace.lib.cranfield.ac.uk/handle/1826/9033
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll