Re: [Roll] How to react if Trickle Interval > Default Lifetime

Simon Duquennoy <> Mon, 02 May 2016 19:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4127212D189 for <>; Mon, 2 May 2016 12:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=cQAKAhZX; dkim=pass (2048-bit key) header.b=rKYAz5FV
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SOrNw-nkdtV7 for <>; Mon, 2 May 2016 12:55:13 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C4AF112D0BC for <>; Mon, 2 May 2016 12:55:12 -0700 (PDT)
Received: by with SMTP id g17so3703885wme.1 for <>; Mon, 02 May 2016 12:55:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to; bh=ZooowSNoKBaVSxTXLQIZhfeSyQshK3pI8ZOpF8pO9Os=; b=cQAKAhZXqoY8xGAXfHw0pup2ccwos2BqXydpNYEIR29YDODv9x6Jgztdm69JBI68/+ PRsIzoRTRxgdbeSDkfZKP0xNoEgXviBSaL+mZjkLH44DrVuUCEXQx6xvqvDpsmk5vy9g Y7o8xyTt/9YbxSYnmRhlS+3OvqsbxcZQc21fUe409IAYjZ7q4U8F+2DX2fBRT+NbQWl8 QeTjx/VCqC4pxul02XzVDfwdMZerMj5HbIszjrvVnHQsZuuXT8qhXrfHsWIPe+X5Aoig +2eTAt7Yf1Dx7+bKVKJv+wkx1liU93D+RyF7mdH7WMbjgyOivrlNnhbJCT2mpICpcuF5 195g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to; bh=ZooowSNoKBaVSxTXLQIZhfeSyQshK3pI8ZOpF8pO9Os=; b=rKYAz5FVjwjR6JQ68Q+JOu4RjglKmBv51EdNcehbxyBky7Dua98BYrWlfZuzM4se2r jGne5tDnK/c0Ux8zyHo7sOyy/MIgZPz8+CenFdh1k5S4fSlKcc9s8H0poC2hkDQGRVAf 46prcoRyyBwEerEmMiJk2nLeOVUuj2BP/g1B0jtjDaRmBzaq/o16YUKg6Oqmz13ZNhlV Ow8PtGE9EUdJEBjBk6ZHsZce415j5B5iv6h4OcfMLryobi1APYb4Ax8MdJJL3a4wjych RPjnHE7ZYHhGsV8jTILK55ifb5yZ7b7xmXKaZJ3cLX3pLm/1qUKkxb9BnIWi2De58JnX 7qLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to; bh=ZooowSNoKBaVSxTXLQIZhfeSyQshK3pI8ZOpF8pO9Os=; b=SEiOMriHRPpRb+f8gRTgf/hZfLdzcSOStLIHs/aNnkf6OpS/sKHInQnnhlGOZ4tJWb XEfKt9KU0dQRkRUJi0HzBfSrH/OPVOnoYwwecMo67QTmJxjL7dkoRwNfJFlpSxGE4C2C lbz3pfcVoIFBKlIIjiqF5lxw9d/EVNKXTlM4rmfjIJEn32nSx2nJDLhRgUFUXvL3hoaV ZVsmKiEDUEgGz6SwYQ38vopWJ561rWybPNgS7y4buymIRwaYX6xVJvpbYqvfiNb8D/kF rZrlBayc74ryvqhNweaHQF9Gw0bjyZtCarvTT2JWUkxwXd7bAMxQMZiQ6k76uiXtWDfi Q3Cw==
X-Gm-Message-State: AOPr4FWVViUE7OH47s1qRFzFsqZdO5rlrXdTNhalZw0DQ+mvyRgSPApqGBtob/e/7o8T+GlEu11wd8ef/HMbUg==
MIME-Version: 1.0
X-Received: by with SMTP id e6mr21985292wmd.94.1462218911335; Mon, 02 May 2016 12:55:11 -0700 (PDT)
Received: by with HTTP; Mon, 2 May 2016 12:55:11 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Mon, 2 May 2016 21:55:11 +0200
X-Google-Sender-Auth: BsNeAOAKxfO84RE83DKgEE8ygHU
Message-ID: <>
From: Simon Duquennoy <>
To: Routing Over Low power and Lossy networks <>
Content-Type: multipart/alternative; boundary=001a11442614cb5c750531e15edb
Archived-At: <>
Subject: Re: [Roll] How to react if Trickle Interval > Default Lifetime
X-Mailman-Version: 2.1.17
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: Mon, 02 May 2016 19:55:15 -0000

Dear Cenk,

In Contiki we send periodic multicast DIS until the node has joined any DAG.
After that, one thing you can do if enable "probing", which will
periodically send a unicast DIS to your preferred parent (and also cover
other candidates neighbors, to keep link estimates up-to-date).

In general wouldn't it be the expected practice to advertise trickle
parameters that never surpass the default lifetime?


On Mon, May 2, 2016 at 9:25 PM, Cenk Gündogan <> wrote:

> Dear RPL Veterans,
> I recently came across the question of how a RPL router may react,
> if a parent's default lifetime (and unit -- specified in the DODAG Conf.
> Opt.)
> is surpassed by the parent's continuously rising trickle interval?
> Without any action from the children, I would assume that the upward link
> to
> the parent would time out before the next DIO arrives to refresh the
> lifetime,
> hence breaking the child -> parent relation.
> Implementations seem to handle this case very differently..
> * The RPL implementation of RIOT uses unicast DIS messages to request a
> one-shot DIO
> from a parent that has a link which is about to expire.
> * From what I could gather in [1], Contiki also seems to send unicast DIS
> messages randomly in an interval of 30~55 seconds (Please correct me if I
> am wrong).
> * In an off-list discussion with Michael, I learned that unstrung is e.g.
> handling
> this case by not letting the Trickle interval exceed the default lifetime
> (Again, please correct me if I am wrong).
> I couldn't find any hints regarding this situation in RFC6550.
> Is there actually an obvious way to handle this, but I am just not seeing
> it?
> Best,
> Cenk Gündoğan
> [1]
> _______________________________________________
> Roll mailing list