IETF Logo Mail Archive

Re: [Roll] clarification on rfc6206

Rahul Arvind Jadhav <rahul.jadhav@huawei.com> Mon, 20 May 2019 00:43 UTC

Return-Path: <rahul.jadhav@huawei.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 CE4F21200B1 for <roll@ietfa.amsl.com>; Sun, 19 May 2019 17:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 AS7bFPZrXLlq for <roll@ietfa.amsl.com>; Sun, 19 May 2019 17:43:36 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBF50120086 for <roll@ietf.org>; Sun, 19 May 2019 17:43:35 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id B50CA96E1CACDDB562DB for <roll@ietf.org>; Mon, 20 May 2019 01:43:33 +0100 (IST)
Received: from BLREML703-CAH.china.huawei.com (10.20.4.172) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 20 May 2019 01:43:33 +0100
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.12]) by blreml703-cah.china.huawei.com ([::1]) with mapi id 14.03.0439.000; Mon, 20 May 2019 06:13:26 +0530
From: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] clarification on rfc6206
Thread-Index: AQHVDMhCG0t5jdtt6Uq7Vt+YWPmTeKZzLBYQ
Date: Mon, 20 May 2019 00:43:25 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5DEB83E9@BLREML503-MBX.china.huawei.com>
References: <05C6607C-EE0F-4B20-B694-EC722B862DE6@ujaen.es>
In-Reply-To: <05C6607C-EE0F-4B20-B694-EC722B862DE6@ujaen.es>
Accept-Language: en-IN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.157.44]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/LWN0rtVTado1GIB4zM-q0C5PeSw>
Subject: Re: [Roll] clarification on rfc6206
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: Mon, 20 May 2019 00:43:38 -0000

Hi Francisco,

I must be greater than Imin based on rule 1 and 5. But note that in step6, I could be set to Imin on resetting the timer and then a node, in this state, could hear an inconsistent transmission yet again. In such case, step 6 will hit the condition after seeing (inconsistent transmission && I == Imin) and at this stage, there is no point in resetting the timer again.

Regards,
Rahul


> -----Original Message-----
> From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of francisco javier
> sanchez-roselly
> Sent: 17 May 2019 19:56
> To: roll@ietf.org
> Subject: [Roll] clarification on rfc6206
> 
> hi All, a minor question on section 4.2.
> 
> rule 6 states that to reset Trickle, I must be greater than Imin, but this
> condition always verifies because of rules 1 and 5.
> 
> is this redundant or I should be t in rule 6?
> 
> thanks, regards.
> 
> francisco javier sanchez-roselly
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email