IETF Logo Mail Archive

Re: [Roll] Trickle Reset vs Restart

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 21 November 2019 05:16 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 42A2312096A for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 21:16:47 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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=gYB8xBDr; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ees89689
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 BTkU9vwhYdki for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 21:16:45 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 407B5120966 for <roll@ietf.org>; Wed, 20 Nov 2019 21:16:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1964; q=dns/txt; s=iport; t=1574313405; x=1575523005; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=VunCLHmAEVcJSK0KGbb8IQqDxuqE1lu1GDd4oSz4nw8=; b=gYB8xBDrA+XPaF61Hd6lxteY2+3OQyTh9c9q8Pn9uwe8hRnU6MiuZ4eY J/CX3IAbSNNm3nwbVAUM7kucNKgMmYR1aWvskHfVuUHKupCeSKSHs8HwC TVnWwNpY3/EqOMMLF4xP1CMrpr16Y6S7hReBAjr/ebL4PrFUZkDoV+yas Q=;
IronPort-PHdr: 9a23:J1Sn6RyMe+Y29drXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZudFU3mJvPwcwQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CoBACvHNZd/5hdJa1kHQEBAQkBEQUFAYFtBQELAYFKUAVsWCAECyoKhCCDRgOKa06CEIlYjiiBQoEQA1QJAQEBDAEBGAsKAgEBhEACF4IQJDcGDgIDDQEBBAEBAQIBBQRthTcMhVIBAQECAQEBEBERDAEBJQcMBAsCAQgaAiYCAgIfBgsVEAIEEyKDAAGCRgMOIAECAQuifAKBOIhgdYEygn4BAQWCSYI8DQuCFwMGgQ4oAYUahnsYgUA/gTgfgkw+ghtHAQGBQQEBB4MnMoIskBWdXEEKgiuRN4QYG5oUmRSPQAIEAgQFAg4BAQWBaCOBWHAVOyoBgkFQERSGRoNzhRSFP3SBKI1dgSIBgQ4BAQ
X-IronPort-AV: E=Sophos;i="5.69,224,1571702400"; d="scan'208";a="669504778"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Nov 2019 05:16:43 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id xAL5Ghc3009250 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Thu, 21 Nov 2019 05:16:43 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 20 Nov 2019 23:16:43 -0600
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 21 Nov 2019 00:16:41 -0500
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 20 Nov 2019 23:16:41 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iBgidS92IcQJM/xhA9AezwfTHR5QaQYmuh7d90D+sABJhivfg3QAzUOp+8/6CgA6Pm6vi3uZMUpVCVYzcKwLd/uhzeRyFVc8j1VkrP900jJ2YZJUK8p2MaPYWtOXv+L+47hwXn0pzASfdE8hLH3K58Tr7xxFk1c1WBzwpbyJZRXUvFan+tfHoPI7FPOjd5QYZeR9l+zYycoM0Ystzbz9tujWEF5S1n+jzHOSoYUM6IDb17cIobH3f433aerYkZv58X+iGYc8DIuyCp+Q8N6srO55NiSixcoCAkCivWSv7D1TgoWkVNe/bHvhzMGLURvKFzbqSOc2od6nGAdWQwY8LQ==
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=VunCLHmAEVcJSK0KGbb8IQqDxuqE1lu1GDd4oSz4nw8=; b=OtdIXShPT/EPDO6zGqoTkaUYewS3NU2+Pxq3LvfUPgyomZUhVIFh4AYulgaVpoFhmXMFW2JThcByDodZP4Aw0saD1QRbvCdsNgxOrp5gp4mY518G/MY9mXO5xHjD7eLXL/gvxYu4K+8PPtef+5srFBO8hLFI2LcOxv2zJpByO1Jkftjy2OUd+/d7KJn6wLAniwWjikI2Slg39ph3Stu+SE8ehS90FKO0jaVkOWMshzuf0Wr4fgocPvdgpAiyLe0v/+a1CK2YmYqEqsGLR5bVQd6LnQra18V+HU74t/H/ulWA4/SgZTmkZtEzKZKA149kaKYl3wm3WRhlkKirOU9Zfg==
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=VunCLHmAEVcJSK0KGbb8IQqDxuqE1lu1GDd4oSz4nw8=; b=ees89689kfDXSpADxqlPLNdzqIuHqNpixvXq0mmKl1iqMpnMY5QnLK82j9Letbk25Cl6BDUeOyKYSlJ2MwfCtMi+VA6HOhKFKzNIWsigG1X01EyPqD1vstHtyoCy3g2YA5+tn72/Jgc94eCvJ29rmgd3Omv1WdIOTQTQt1VK7Js=
Received: from BYAPR11MB3558.namprd11.prod.outlook.com (20.178.206.75) by BYAPR11MB3350.namprd11.prod.outlook.com (20.177.186.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.26; Thu, 21 Nov 2019 05:16:40 +0000
Received: from BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::e5b0:1702:87b:b1e]) by BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::e5b0:1702:87b:b1e%5]) with mapi id 15.20.2474.018; Thu, 21 Nov 2019 05:16:40 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Trickle Reset vs Restart
Thread-Index: AQHVoCjp5I8O0t+EpUC9pG8zWFYuXKeVFWSA
Date: Thu, 21 Nov 2019 05:16:40 +0000
Message-ID: <DC477A92-148D-413B-9B6F-7A811459E0DD@cisco.com>
References: <CAO0Djp2LLhQ+MiQk5TbRpxrrbAdCCWP+S6BUcMG0Qg6fikBB6Q@mail.gmail.com>
In-Reply-To: <CAO0Djp2LLhQ+MiQk5TbRpxrrbAdCCWP+S6BUcMG0Qg6fikBB6Q@mail.gmail.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: [31.133.149.193]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 026d7e66-6c62-41a5-3b18-08d76e41fdc8
x-ms-traffictypediagnostic: BYAPR11MB3350:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYAPR11MB33505695A7DCFC6C73857E09D84E0@BYAPR11MB3350.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0228DDDDD7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(396003)(346002)(366004)(376002)(136003)(51444003)(199004)(189003)(11346002)(6916009)(99286004)(6486002)(36756003)(71190400001)(6246003)(81166006)(6116002)(186003)(66556008)(66476007)(64756008)(2616005)(71200400001)(81156014)(66574012)(66946007)(86362001)(8676002)(5660300002)(2906002)(33656002)(316002)(305945005)(76176011)(7736002)(102836004)(8936002)(66446008)(3846002)(66066001)(6306002)(256004)(476003)(25786009)(6512007)(6436002)(486006)(6506007)(966005)(446003)(91956017)(76116006)(14454004)(229853002)(478600001)(26005); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3350; H:BYAPR11MB3558.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: rxTrP+etxUW66m36PUosJX4HskJ7/c3i+T9hXbYi7RA6sevo+I3GbwYhCxF03Bxs1bzatmK60Iu8yyC/P54cNTPv/qh1iv2dpvLHtoVHMmhni+M2n9Tr+tSMDmLuICUDyUkMQLoHYQ1uCklsGqcEBOtzpVULvPhK6bkzNwAEwYSiNZEuuco42uiM43xiKfqQljtwqQI2KJW+Aiagx1BBydEQeyvl2Q080jkAt3x3Ww3l9xrsuz5dt4LVd28rEpcRlJidqlPhyN56JpeeAcM5oBDDIrDEog5dF9jfxilh++k7HYVi+rtd1tCU+1tzwhycQGZcgddBcZs1eS7RM20cSoullkdUgiaWpsYSiET6r02gAyZEqGkWdsPC921b6+ayfQ0Yfo63DI6k7RogSn+PIM+dBqe/CIW3fb2+WddZ5GWs75lxDdQa4u5S9pBrGpwXYtOPz0upaxuutaBc2GCMJWhLHA/AIfylvkzDn1KBOpc=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 026d7e66-6c62-41a5-3b18-08d76e41fdc8
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Nov 2019 05:16:40.4283 (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: FRrWOXt0yX2D3RCqmoPap0di3B6/YZ3M8MDuE2gRbYERCjZin87iFxYXHV/cyq4ChTJPeRDJ5nrot6XnNrlq9A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3350
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.23, xch-aln-013.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/5n1v2WlX1qkdd5B2Xi3druYoeCQ>
Subject: Re: [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:16:47 -0000

Hello Rahul 

We all observe that restarting the timer can be disfunctional. So yes I think it deserves text somewhere, starting immediately in your rich and useful observations draft.

I’m happy to add text in the eliding-options draft, for the lack of a better carrier. I think that the observation that the timer should not be restarted may not be general to trickle but seems general to where we use trickle in RPL.


Regards,

Pascal

> Le 21 nov. 2019 à 13:02, Rahul Jadhav <rahul.ietf@gmail.com> a écrit :
> 
> 
> 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
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email