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

Joakim Eriksson <joakime@sics.se> Mon, 02 May 2016 20:00 UTC

Return-Path: <joakime@sics.se>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 676D212D165 for <roll@ietfa.amsl.com>; Mon, 2 May 2016 13:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sics-se.20150623.gappssmtp.com
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 UEZZzImM7p03 for <roll@ietfa.amsl.com>; Mon, 2 May 2016 13:00:31 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5655C12D61E for <roll@ietf.org>; Mon, 2 May 2016 13:00:31 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id y84so200502621lfc.0 for <roll@ietf.org>; Mon, 02 May 2016 13:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sics-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=LMXznkb8c+LRNLb37zUOCxniT8mZFztIvfzI07hiBOs=; b=CK37pBHIzSD+lnz9mAKoeOh2MXQ2LRfwvrajrCAEaLjTLxI/mOitfZx1MbIoDHlV+g 0Hqm7ESqNYTqOYtqMvA+eD9SM2Gd72hYvlj7hkMMIOIQE/8ghYUtyzgVyDH9YP48HFDN X7ItrJU/tXzBZBorwYtH910f/KS8LcjlIboWzRFAuIf2X5NGpwspR/C63t+v6ApC4mJC dHwZMzLlWD9Jv9Z9Ss0N8tdJ/AlALlWfXA7SQsbkR2Q+wetiqYxRQ8k8WRRxZsaX3jhG mzBAqp2c52iIuqV8F6zErVAt/bvj2hG/bFws6SkxNzNp7OYOPBMlgR/2FlkEqfCgoQLC 1gfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=LMXznkb8c+LRNLb37zUOCxniT8mZFztIvfzI07hiBOs=; b=Sz62NwqLiTWwld8t9KNP0Eja7GJWPdpInUOQTBqyQ4xrZFA5CUczUtRFBdnMIkJ15K UYLRqGmbx7+9v3ipJ4XB68UYibgZTQwbmQuYNE/+yubH16rKsbZXgvPXCa2hG+vZK4UR JxY4Grk2h9x5jA/xbCUZsCZ3d3OmB2bEQuzGNaTJ9vF2slI9Q7wq0/1sz7btpm590XaP s8lUm4cQ3YLbgAtzqYmUBLbiHAF4FL0gO5Bp1uzsLsDzl8966iVYslzn+h61AgqYjURO ug2j8pky1XwleB2qHO3DH1dx0YJcVmvxG2+tzFGZF0hmiJ75LYK7C4bigGi8VYl+L3gP dCbg==
X-Gm-Message-State: AOPr4FW3XCrDXz2AkJ0m3HdbCaHXd981LYosb6EOzdtqOFzTDiAYwzu9OeQuu3ECpyv8Hy1J
X-Received: by 10.112.134.229 with SMTP id pn5mr14895735lbb.36.1462219229553; Mon, 02 May 2016 13:00:29 -0700 (PDT)
Received: from [192.168.1.102] (195-67-245-31-no175.tbcn.telia.com. [195.67.245.31]) by smtp.gmail.com with ESMTPSA id sa9sm4370013lbb.38.2016.05.02.13.00.28 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 02 May 2016 13:00:28 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C4DC5084-C4A1-4156-B166-33FFC0C44C83"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Joakim Eriksson <joakime@sics.se>
In-Reply-To: <CAMxvJt+FnZQOtv2yFE7t6s-e97DirGHVHCbLGz2U-CJnHC8cBQ@mail.gmail.com>
Date: Mon, 2 May 2016 22:00:27 +0200
Message-Id: <466CD3E8-6DC3-4EF1-80B8-333F6FB1E4E2@sics.se>
References: <2591c152-29fd-ce24-d4c2-27fc23a9a034@gmail.com> <CAMxvJt+FnZQOtv2yFE7t6s-e97DirGHVHCbLGz2U-CJnHC8cBQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/_y_R06T3gPdOmFUmzlKCg3QWRoU>
Subject: Re: [Roll] How to react if Trickle Interval > Default Lifetime
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: 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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 02 May 2016 20:00:34 -0000

Hello,

In Contiki I do think we are typically using infinite lifetime on the installed route between the child to parent.
If the child needs a downward route it would register that via DAO and keep that re-sent at less than default lifetime as specified
by the DIO (default lifetime and lifetime unit).

Best regards,
— Joakim



> On 02 May 2016, at 21:55, Simon Duquennoy <simonduq@sics.se>; wrote:
> 
> 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?
> 
> Simon
> 
> 
> On Mon, May 2, 2016 at 9:25 PM, Cenk Gündogan <cnkgndgn@gmail.com <mailto:cnkgndgn@gmail.com>> 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] https://github.com/contiki-os/contiki/blob/master/core/net/rpl/rpl-timers.c <https://github.com/contiki-os/contiki/blob/master/core/net/rpl/rpl-timers.c>
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org <mailto:Roll@ietf.org>
> https://www.ietf.org/mailman/listinfo/roll <https://www.ietf.org/mailman/listinfo/roll>
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll