[Roll] Trickle Reset vs Restart

Rahul Jadhav <rahul.ietf@gmail.com> Thu, 21 November 2019 05:02 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 922B8120959 for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 21:02:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 u6BbYh7s7Mxo for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 21:02:32 -0800 (PST)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (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 2B614120964 for <roll@ietf.org>; Wed, 20 Nov 2019 21:02:32 -0800 (PST)
Received: by mail-ua1-x92f.google.com with SMTP id k11so564719ual.10 for <roll@ietf.org>; Wed, 20 Nov 2019 21:02:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=6/4i8UQsGOsydM8t+94TBra17DhY+fqybtf3Ig77gqw=; b=Jt6NKybLTFWWek3Tm2D2WemyYdmNs6a0+1X4qihJ+1TPPbR4AKoupL+PZ9kP9OsEJP Vr+rwOrrJuqW1xl5nDeOxJJqLcuaIS9SpRBqqBZTcrB39dSqp1itdH7qj5+p7W36MpGG k5FjJapO+800OBS5mQy4W6rxY2rKGPb7Mqh6btRzSHZmJXyyOMbtoOyWvZaQ4817Ia3o FdmOQIXL8y1jyrpH5munwJFmkTtFJnBoXoAeR2CJ7wtahnsSzmhu8DAkowBCbn1AOl6U /owI/RMc5mL9IJ/xfKwrGxvyWHOS4Yza9qE7csZ/xX5wsHwMhI7kq+D2EDAUaKiqRdj7 D7TA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6/4i8UQsGOsydM8t+94TBra17DhY+fqybtf3Ig77gqw=; b=aawcK1YfQSDEKZjuvpQmsGsb+qbV7MjqBIF1+cvmyUmTuxCeRw3hh3nEEK+wZip51S +3p4jQlZOPkJ6b3w/hvvQDMM9NP6XjJHOAX02J9VLfcw60R75BEJ1riutTqqLBpxbJxT PkZj98gxuRhDJhNSUPJ76S8bK4z+exTuYIVMH/dJvBdKmWsc71wG2brsaET1hQNxkKPS a1O/TmeA14EdJFQKpkSqzgFHQDdsTXBRt6d3r7fYCrZlyXH6ksi4KGjEfWYEsCdL510f mdCMQ6qtfYK9kwhseMnPppiekPfGj5QrSEw8DRleKQEHAF//UVZPxnPyrAq234YRHPqo 5qvA==
X-Gm-Message-State: APjAAAVLTXEHKWrdfkuQ7TfsopgEFlNxMagWvSJlUQFFftl7LGxmsgbu iOfCsGrzez8xjYSr1LZ+KsxmuhY0dbU/Z7Tjis8Pl4BD
X-Google-Smtp-Source: APXvYqz4P3L3Z2dtdqjRi7kxA+OESiDIWUFhsAckmFwfB8fV81GKvlxbSo4Ctp3Owd4+AtnTJe+o9JelcJ0DKrNEhFc=
X-Received: by 2002:ab0:7509:: with SMTP id m9mr4274965uap.136.1574312551027; Wed, 20 Nov 2019 21:02:31 -0800 (PST)
MIME-Version: 1.0
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Thu, 21 Nov 2019 13:02:19 +0800
Message-ID: <CAO0Djp2LLhQ+MiQk5TbRpxrrbAdCCWP+S6BUcMG0Qg6fikBB6Q@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005e99a50597d43494"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/HAQDcMkI7TqFeIOLhZNCHdGwTDE>
Subject: [Roll] Trickle Reset vs Restart
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Thu, 21 Nov 2019 05:02:34 -0000

During the IETF106 roll-session, we discussed resetting vs restarting
Trickle. Pascal raised this in another mail as well.

After checking RFC 6206 (Section 4.2), I found that there is only one
notion i.e., to reset Trickle timer, which means going back to Imin and
starting a new interval.

There is no notion of restarting the current timer for the instantaneous
value of I.

This is what my understanding was and reset is all that is needed, IMO. I
would like to be corrected if there is any use-case, where restarting the
timer would be needed.

We may not need any clarifications on this particular issue. Or do you
think we should still keep this as a note for implementors in the
observations draft?

Regards,
Rahul