[Roll] DTSN increment

Rahul Jadhav <rahul.ietf@gmail.com> Tue, 11 October 2016 10:10 UTC

Return-Path: <rahul.ietf@gmail.com>
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 B3B181294D3 for <roll@ietfa.amsl.com>; Tue, 11 Oct 2016 03:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=gmail.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 0F22Uw-A0x3z for <roll@ietfa.amsl.com>; Tue, 11 Oct 2016 03:10:00 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 4488F129492 for <roll@ietf.org>; Tue, 11 Oct 2016 03:10:00 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id t73so17943489oie.1 for <roll@ietf.org>; Tue, 11 Oct 2016 03:10:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=QRXMJGKqOfLyKOxVQue+Y6EI9RaICP9/Qt2cbdkO/Ak=; b=OK/RNQBNnx79RVMnmqIw9hTahpYpRdhYMTPMXVrHBqR4/Hg4bf9yYL2dtYlBlE5VhM LvgfbPQ9o+kLXF2TVp+Uq92JXo0tPd0rJ73vPgyJA0QFQsb81fqNfocb+MaVVYYq60LD PukgR5fPzVRP5tgE1ZhiOerGjwqCrm4W0FHpNhAJBgfn7AIOoDkKU5w6eSX3XrxAhul7 TCM9kf0dEhmNYV5QXgYiA2nd87w9nIg4mJdgDY3VdgOatmTQPEphkTLA4Bz76cko32Ag kb4C7vJr4SVjn5anRqYCI8EC6GJr9sPjzgHc678v2nWRzKmiJC+2prJH5Y49SCNq52Tw sG1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=QRXMJGKqOfLyKOxVQue+Y6EI9RaICP9/Qt2cbdkO/Ak=; b=bTTUGoIpb7eB8buVPMunUD0D9bQZjy2pT21eBN1zNIJQU5DdnJo51xFAlqJcfz9yRo QPy+irgktjZtdG271JZy0UlS1RXWLrpLqFfkdYL/gR+M027Vm+BVSUljzg2SNPUs6VP5 q7PHgKUUohhTLWz5+3x54LsqO40T855UBjzC6S4rAf39kuIwwaFLbf5U+EExlghZAK0u H9rW4VQJbpvrVs59fu0VfqZ4qEfDVWPECG5hT/AyEGbKbY9ZsJeODtwNyqUEOogeR0HU yya+Unk/3Q/aE/uV7MPoeJ5cAjDj6ex790ZhgeyxS2sPU0EtOsLin6HMtGV8OroD9izU Cwxw==
X-Gm-Message-State: AA6/9RliRmvkix6gVe36BHBz7bI52NW3Dojn4thuCF2PA4hug3GfddPHE3fS5qS79SXD1cmcKMGQYqoAjlsykw==
X-Received: by 10.202.181.68 with SMTP id e65mr1726643oif.151.1476180599593; Tue, 11 Oct 2016 03:09:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.219.133 with HTTP; Tue, 11 Oct 2016 03:09:59 -0700 (PDT)
Received: by 10.202.219.133 with HTTP; Tue, 11 Oct 2016 03:09:59 -0700 (PDT)
In-Reply-To: <CAO0Djp0rMZRrSK0ECDin1_c0C8fwj8Yxtpu8SwgBWvnWO5mg=w@mail.gmail.com>
References: <CAO0Djp3V=1ew=ZieqQdZcgD+-yryvv+_LyQbKvXkzYr+D-CZ0g@mail.gmail.com> <CAO0Djp02F4kL1aXbK4_cOtZy1cUD=JVTfOzY0HeB_JJ4ymWF-Q@mail.gmail.com> <CAO0Djp2Pjh==GYFjNfngXQ-+BmNMSU8kzuR+qbmT7_4RWJBpLQ@mail.gmail.com> <CAO0Djp0BsWuk7rNbyMadr4HVYi_scDkWHq4o-TP97W6MtSXzDg@mail.gmail.com> <CAO0Djp309c9TnGv7fd0XUrYU_ccx08LbS8xca6u8h0idHgguXQ@mail.gmail.com> <CAO0Djp3=77TyVYUcOfhhPktSY2gbrvBip3dtWdF=6P3JXK2aZw@mail.gmail.com> <CAO0Djp1GVXFsLeux5YB8rc80Z9ys2S=ifwLgOPP8H_74OsRAGw@mail.gmail.com> <CAO0Djp0rMZRrSK0ECDin1_c0C8fwj8Yxtpu8SwgBWvnWO5mg=w@mail.gmail.com>
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Tue, 11 Oct 2016 12:09:59 +0200
Message-ID: <CAO0Djp1wkZnBKda6SAbnHk_Xw1n+6_RnP8gzAVMS5-ztOUpBOQ@mail.gmail.com>
To: roll@ietf.org
Content-Type: multipart/alternative; boundary="001a113ce70e435f49053e9414ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/Dfme5ocATyL-WwxjZKSM1wQGX3A>
Subject: [Roll] DTSN increment
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: Tue, 11 Oct 2016 10:10:03 -0000

Hi All,

I have specific query regarding handling of DTSN increments. DTSN
increments are handled differently in case of storing mode vs non-storing
mode.

6550 states,
"
   In a Non-Storing mode of operation, a DTSN increment will also cause
   the immediate children of a node to increment their DTSN in turn,
   triggering a set of DAO updates from the entire sub-DODAG.
   Typically, in a Non-Storing mode of operation, only the root would
   independently increment the DTSN when a DAO refresh is needed but a
   global repair (such as by incrementing DODAGVersionNumber) is not
   desired.  Typically, in a Non-Storing mode of operation, all non-root
   nodes would increment their DTSN only when their parent(s) are
   observed to do so.
"

Based on this wordings, in non-storing mode, the DTSN update is controlled
by the root only (having said that, the RFC does not mandate it).

What i don't understand is, why DTSN increment is handled differently for
storing and non-storing mode?
Also when the DTSN is incremented by the child node, isn't it desired that
DIO trickle timer is reseted, since otherwise the DIO (with incremented
DTSN) may be sent out (very) late and thus DAO update may take huge time
(depending upon where the trickle timer rests currently).

Regards,
Rahul