Re: [Roll] Fwd: I-D Action: draft-ietf-roll-rpl-observations-03.txt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 29 November 2019 07:32 UTC

Return-Path: <pthubert@cisco.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 7FC991201EF for <roll@ietfa.amsl.com>; Thu, 28 Nov 2019 23:32:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=lntTMH2z; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=rpsqyZE4
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 fU0Ilin-uWM2 for <roll@ietfa.amsl.com>; Thu, 28 Nov 2019 23:32:27 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0156E120147 for <roll@ietf.org>; Thu, 28 Nov 2019 23:32:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32191; q=dns/txt; s=iport; t=1575012746; x=1576222346; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=rRBlW/APrU+iyhqBKghHd04oA5RcUSbdXqzcfPOd+N8=; b=lntTMH2z7QxJOkRcIf84j2HA4i9bcY2qTkjajifb0XC5JwuqK1vZrDOS RttdIpNvlc/rtz4csznzQvzNUktiSJEp14xfYWQONx24hNESH4WxZ/3Po RLeBT8I3mUnCB3jru6lZgS2PD7Fh8M9GJiozIAadMA9gAMOhtxiEB+uB3 Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3AyGArehAJ2zUR8JDyllC6UyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qs03kTRU9Dd7PRJw6rNvqbsVHZIwK7JsWtKMfkuHw?= =?us-ascii?q?QAld1QmgUhBMCfDkiuNOLqciY3BthqX15+9Hb9Ok9QS47z?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0APAQDOyOBd/5tdJa1lGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYFtAgEBAQELAYFKJCwFbFggBAsqCoQhUYJ1A4p?= =?us-ascii?q?uToFsJYlbjimBQoEQA1QJAQEBDAEBGAEMCAIBAYRAAheBcCQ3Bg4CAw0BAQQ?= =?us-ascii?q?BAQECAQUEbYU3DIVSAQEBAQMBARARHQEBLAwPAgEIEQMBAQEoAwICAh8GCxQ?= =?us-ascii?q?JCAIEEyKDAAGBeU0DLgECAQunJQKBOIhgdYEygn4BAQWBOQIOQUCCWQ0Lghc?= =?us-ascii?q?JgTYBhRqGexqBQT+BEScMFIFOfj6CG0kBAQIBARiBKwU3DQmCWjKCLI0vgmu?= =?us-ascii?q?FTIlJjlFCCoIuhx6KIIQbG4JBc4Z6iVuGGpAMhnqCFI9HAgQCBAUCDgEBBYE?= =?us-ascii?q?/KSOBWHAVGiEqAYJBCUcRFIhUDBeDUIUUhT90gSiPJQGBDwEB?=
X-IronPort-AV: E=Sophos;i="5.69,256,1571702400"; d="scan'208,217";a="585573946"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Nov 2019 07:32:23 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id xAT7WNbk016253 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Fri, 29 Nov 2019 07:32:23 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 29 Nov 2019 01:32:22 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 29 Nov 2019 01:32:21 -0600
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 29 Nov 2019 02:32:21 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JjeJMaxIfZt9UJncmAWoTPGMxuXH6Eju4Wtp3ZVZpu90uF9G9iiA/f6p4CFzKBpz76vhyLeT2ffR7RHbk+C7rYa7e7x2QKZWf58QM32KvyNzFPveY15vdhBCEwuTXiReFaH2HyxIsszc0Dj9pwMffBCcaAuLcsws28QT3gCQtMuS+L5dUpehp/6fVoaaR8HCYw2MxoIANTngqcPe+Z1KY3pIarkFB+4E4M6HPaS/i60tiOBu6/H3YATzgvh2KDb7gTU2lySUV/MTgRmmAQW3mfkVm2aOhbvZ5RCKOHJJSHVOKNFwx+COa7VPKLuTEexROFWyKeBPOoBvRooweuzArg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rRBlW/APrU+iyhqBKghHd04oA5RcUSbdXqzcfPOd+N8=; b=Q3GwSZBWhNLBMs4ln7byjgQZEq9P+InwbYvfDnBbphJBWcb0p1UV4YM/VtcQt7hJKt449vRvI8bQvyOiZ6D2paVzx18F6RVKA6M/HSy0r7iJG6pjAh/psBmU8kioyjQOGhpvx3pZ4rgOmzsm0EMgeEiaavwYN+TqrdvqnHejK67wJFgvFx3kmSW7cA8BCeYsJMooUZbuYsAKe4saA4bcusTgMAtyV3CtfCek0CqNp5GPGGkq1JykEy5VNlAsCGP/1Z9bWcAEPJw0TfXnzjAgLYUUpe+2q+hbO5uVSguphduQRHMIFL+IA9sOvzlZwZVa3d+zZzJcUFVH5ZITNOYsaw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rRBlW/APrU+iyhqBKghHd04oA5RcUSbdXqzcfPOd+N8=; b=rpsqyZE4EJkBqqGFV3ewTItjaxUyw3lAtgqTrnf6bS287UWXlgOIH7EzrxLFKkFJNYxqM0/VzipH/u9sgazt1v00PaW1v+kQxcrVrkbwQVcg5mPgaR5IQNeqRtMhDUnnNd0qWrs+Q/6IXODZQCnQ5pVnbblupHmljSxTapVel+s=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4000.namprd11.prod.outlook.com (20.179.150.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.21; Fri, 29 Nov 2019 07:32:20 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::3037:66f1:dc79:b564]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::3037:66f1:dc79:b564%7]) with mapi id 15.20.2495.014; Fri, 29 Nov 2019 07:32:20 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Fwd: I-D Action: draft-ietf-roll-rpl-observations-03.txt
Thread-Index: AQHVpGVkXobK5qdhG0OdbsPUc6qF1KedgkpAgAK6FwCAAHrR5YABDkeH
Date: Fri, 29 Nov 2019 07:32:20 +0000
Message-ID: <AA954003-1AB4-4776-869C-CFD3B5D48048@cisco.com>
References: <157477212600.13715.10647534303499379032@ietfa.amsl.com> <CAO0Djp1K=_6DwAQ31+Y8raVkfBP7=YobaQkOzrtBCB9Da3Fd0A@mail.gmail.com> <MN2PR11MB35651EEACA6CB142CB57D1F4D8450@MN2PR11MB3565.namprd11.prod.outlook.com> <CAO0Djp2kX52TfrwJSzuBB2bOLoE46WvJOw-XJ-9D66U-nqXeuQ@mail.gmail.com> <MN2PR11MB3565F261BED62B3A70FEE564D8450@MN2PR11MB3565.namprd11.prod.outlook.com>, <CAO0Djp3+XTtr8HAJPaZJMZ=Pj2gKjbJk4MG=AkjcBG-fJQud0A@mail.gmail.com>, <D577BCA4-9DCC-4278-8CA3-56AC17E96D9A@cisco.com>
In-Reply-To: <D577BCA4-9DCC-4278-8CA3-56AC17E96D9A@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [91.69.164.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5c1e76b6-203e-4efe-d1f2-08d7749e44bd
x-ms-traffictypediagnostic: MN2PR11MB4000:
x-microsoft-antispam-prvs: <MN2PR11MB4000D3402017FA6E3899F024D8460@MN2PR11MB4000.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0236114672
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(39860400002)(346002)(396003)(136003)(53754006)(22974007)(189003)(199004)(606006)(25786009)(3846002)(6116002)(2906002)(8936002)(86362001)(81166006)(81156014)(8676002)(14454004)(54896002)(6306002)(236005)(6436002)(6512007)(4001150100001)(66574012)(6486002)(6246003)(186003)(14444005)(256004)(102836004)(26005)(6916009)(53546011)(6506007)(76176011)(66446008)(64756008)(66556008)(66476007)(66066001)(316002)(76116006)(91956017)(66946007)(99286004)(446003)(36756003)(11346002)(7736002)(5660300002)(5070765005)(2616005)(478600001)(966005)(229853002)(71190400001)(71200400001)(33656002)(244885003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4000; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: q19vUz6BqMaFOzhTx856EaTWgPawpKqGSKfoV+gNVPTWb6AlbdKuMiV1R/Y83rbQDAAcoQmhVSQpP7f+wO9uNqPf9UPHSUe8mcjjsiaSIuM/UAB9pmi+CF7gjGaTCcOBk+rmhG+Fii3dO8S9rD7YHWOiueSjWwe11UAK6bm+SKQhUg4Z5wHTwd2qpzbs7/fjBaVxCw+EZsyG+eGbxL04I2ej7gEXils4+Qvd5QfeiqKFoB5xrScl+Ij0NRLRxwFFZ+eUKRlOgb3eewWLYGrP/+QXIL+vB4X3YWFLG6cApf1aDL2l3ZXSM1C1RbNXabGSMteTF/ozuIq+BvtjnhBXMKRckZQiiEfiEg9JqjQkNA0RPk/Ioj25WYS8vhlg64XY55i8NIcBT/fh/GTG57uFxkZryDD8mH9heHXRL2LgEFi8JAWj2sEewKNA7OmRux6ue/vbw0ZKZOclXOEMs+NbAjQI8D/QouqRfv//5hNVplQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AA9540031AB44776869CCFD3B5D48048ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5c1e76b6-203e-4efe-d1f2-08d7749e44bd
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Nov 2019 07:32:20.1950 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 9AdX+KffI8zqVaIPhAV3QTpmtZ+yTyGJ8aBC6zGC8U1IoVVofbMRkcRmyqhVz0X/R8lBK7XiJkxgTa5kUcm7dA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4000
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/PytGIpied-sWmamkf5kJkS5R3iQ>
Subject: Re: [Roll] Fwd: I-D Action: draft-ietf-roll-rpl-observations-03.txt
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: Fri, 29 Nov 2019 07:32:29 -0000

Hello Rahul

I believe the test in RFC 6206 is really clear. Since you’re quoting it I cannot be unhappy.
I’m still confused why people had issues with it thus my discussion. As I said your text works, I just hope that people who were confused before are no more after this.

Regards,

Pascal

Le 28 nov. 2019 à 16:24, Pascal Thubert (pthubert) <pthubert@cisco.com>; a écrit :

 Hello Rahul

The text works. I’d have liked that it makes a distinction between resetting and restarting. The former acts on parameters the latter on a running timers.

Resetting means I<-Imin. That’s it.
Restarting the timer means an API call to the kernel timer services.
These are different things and it would be more clear if we separated them.

If I is not Imin then resetting means changing the value of I; this implies that the current running timer operates on wrong parameters and this may time out too late. The simple thing to do to solve this is to restart the timer based on the new parameters.

But if I is already set into Imin resetting it (to Imin) produces no effect. Which means that the running timer operates on the right parameters and doesn’t need to be restarted.


Regards,

Pascal

Le 28 nov. 2019 à 09:06, Rahul Jadhav <rahul.ietf@gmail.com>; a écrit :


Hi Pascal,

I have updated as follows. This clarifies the interpretation and then also explains specifically in context to multicast DIS/DIO operation.

"

5.  Interpreting Trickle Timer

   Trickle timer defines a mechanism to reset the timer.  Trickle timer
   reset is unlike regular periodic timers wherein the timer is simply
   reset to start again.  Reset of trickle timer implies resetting the
   trickle back to Imin and starting with a new interval as mentioned in
   Section 4.2 of [RFC6206].

|----|--------|----------------|--------------------------------| . . . . . .
 Imin   I2             I3                       I4                       I5

                     Figure 4: Trickle Timer Operation

   The above figure shows an example of trickle intervals.  An interval
   is double that of the previous interval size.  Section 4.2. of
   [RFC6206] states that,

   "If Trickle hears a transmission that is "inconsistent" and I is
   greater than Imin, it resets the Trickle timer.  To reset the timer,
   Trickle sets I to Imin and starts a new interval as in step 2.  If I
   is equal to Imin when Trickle hears an "inconsistent" transmission,
   Trickle does nothing.  Trickle can also reset its timer in response
   to external "events"."

   Thus if the trickle timer has advanced to subsequent intervals i.e.,
   >= I2, then a reset of trickle timer implies going back to Imin.
   However, if the trickle timer is currently in Imin and if it hears an
   inconsistent transmission then it does nothing.

   In context to multicast DIS/DIO operation, this implies that if the
   DIO trickle timer is already at Imin and if the node hears a
   multicast DIS, then the timer does nothing.  It MUST NOT reset the
   timer again in this case.

   An implementation MUST never restart the timer within an interval.
   For e.g., in the above figure, if the timer is in interval I2, the
   implementation MUST never restart the timer to the beginning of the
   current interval i.e., I2.  If the timer is in interval T2 and if the
   reset is to be done then the interval is set back to Imin.  If the
   timer is already in Imin, then the reset should do nothing.

"
https://github.com/roll-wg/rpl-observations/pull/8

Best,
Rahul

On Tue, 26 Nov 2019 at 22:31, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Rahul :

I mean that if the spec says reset trickle and I is already Imin then the timer already operates within the bounds that are expected so it does not need to be restarted. Now if I was larger than Imin at the time of the reset then it was operating out of bounds and needs to be restarted to timeout earlier. Same if K changes, e.g., by configuration. The current timer operates with the wrong parameters and should be restarted.

Makes more sense?

Pascal

From: Roll <roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>> On Behalf Of Rahul Jadhav
Sent: mardi 26 novembre 2019 15:25
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Subject: Re: [Roll] Fwd: I-D Action: draft-ietf-roll-rpl-observations-03.txt

Hi Pascal,

On Tue, 26 Nov 2019 at 20:56, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Rahul

I believe I undertand what you want to d but the text below is really unclear to me
“
  Implementations MUST not restart the trickle timer to the
  instantaneous value of I which could have been advanced over a period
  of time.
“
[RJ] ok. But I could not think of anything better. May be I should use asciiart and explain with an example. What do you think?

What I thought you’d write is that the trickle time needs only be restarted is one value I, K has changed, making the current run incompatible with the setting.
[RJ] This is unclear for me. Specifically "trickle time needs only be restarted is one value I, K has changed"


All the best

Pascal


From: Roll <roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>> On Behalf Of Rahul Jadhav
Sent: mardi 26 novembre 2019 13:47
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Subject: [Roll] Fwd: I-D Action: draft-ietf-roll-rpl-observations-03...txt

Hello All,

The update contains clarification regarding Trickle timer reset handling.

Regards,
Rahul
---------- Forwarded message ---------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Tue, 26 Nov 2019 at 20:42
Subject: [Roll] I-D Action: draft-ietf-roll-rpl-observations-03.txt
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Cc: <roll@ietf.org<mailto:roll@ietf.org>>



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Over Low power and Lossy networks WG of the IETF.

        Title           : RPL Observations
        Authors         : Rahul Arvind Jadhav
                          Rabi Narayan Sahoo
                          Yuefeng Wu
        Filename        : draft-ietf-roll-rpl-observations-03.txt
        Pages           : 18
        Date            : 2019-11-26

Abstract:
   This document describes RPL protocol design issues, various
   observations and possible consequences of the design and
   implementation choices.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-roll-rpl-observations/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-roll-rpl-observations-03
https://datatracker.ietf.org/doc/html/draft-ietf-roll-rpl-observations-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-rpl-observations-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp...ietf.org/internet-drafts/<ftp://ftp.ietf.org/internet-drafts/>

_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll