Re: [Roll] ticket - 172 - clarify units of trickle timers

Yusuke DOI <yusuke.doi@toshiba.co.jp> Mon, 24 August 2015 00:48 UTC

Return-Path: <yusuke.doi@toshiba.co.jp>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 070911B2E64 for <roll@ietfa.amsl.com>; Sun, 23 Aug 2015 17:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.702
X-Spam-Level:
X-Spam-Status: No, score=-1.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=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 IZsMIYpg3_lk for <roll@ietfa.amsl.com>; Sun, 23 Aug 2015 17:48:29 -0700 (PDT)
Received: from imx2.toshiba.co.jp (imx2.toshiba.co.jp [106.186.93.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC0691B2E63 for <roll@ietf.org>; Sun, 23 Aug 2015 17:48:29 -0700 (PDT)
Received: from tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp ([133.199.200.50]) by imx2.toshiba.co.jp with ESMTP id t7O0mRUO025198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <roll@ietf.org>; Mon, 24 Aug 2015 09:48:27 +0900 (JST)
Received: from tsbmgw-mgw02 (localhost [127.0.0.1]) by tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id t7O0mRgo005029 for <roll@ietf.org>; Mon, 24 Aug 2015 09:48:27 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw02 (JAMES SMTP Server 2.3.1) with SMTP ID 81 for <roll@ietf.org>; Mon, 24 Aug 2015 09:48:27 +0900 (JST)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by tsbmgw-mgw02.tsbmgw-mgw02.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id t7O0mRCV005019 for <roll@ietf.org>; Mon, 24 Aug 2015 09:48:27 +0900
Received: (from root@localhost) by arc1.toshiba.co.jp id t7O0mRl4012670 for roll@ietf.org; Mon, 24 Aug 2015 09:48:27 +0900 (JST)
Received: from ovp2.toshiba.co.jp [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id KAA12649; Mon, 24 Aug 2015 09:48:26 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id t7O0mO4E001085 for <roll@ietf.org>; Mon, 24 Aug 2015 09:48:24 +0900 (JST)
Received: from spiffy20.isl.rdc.toshiba.co.jp by toshiba.co.jp id t7O0mNpT016496; Mon, 24 Aug 2015 09:48:23 +0900 (JST)
Received: from [IPv6:2001:200:1b1:1010:bcb9:3450:1b52:1d5b] (unknown [IPv6:2001:200:1b1:1010:bcb9:3450:1b52:1d5b]) by spiffy20.isl.rdc.toshiba.co.jp (Postfix) with ESMTPS id C1F5918F4BF for <roll@ietf.org>; Mon, 24 Aug 2015 09:48:23 +0900 (JST)
To: roll@ietf.org
References: <29012.1439555277@sandelman.ca> <3ac1e1929e2d2c781db8ce08a6955e7e@xs4all.nl> <16420.1439823867@sandelman.ca> <CABOxzu08_b44EkBDTm3uE7F26x5MEHOLgBszvi1gHX93+BTb1w@mail.gmail.com> <14493.1439832712@sandelman.ca> <CABOxzu0kko1zXD3iC8q8cPZt4VwRKEyeMYW-K9-ij01n-guRtg@mail.gmail.com> <26094.1440374648@sandelman.ca>
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
Message-ID: <55DA69E6.2090503@toshiba.co.jp>
Date: Mon, 24 Aug 2015 09:48:38 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <26094.1440374648@sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/M974baAzKCBTddhF3BIDhai7rAM>
Subject: Re: [Roll] ticket - 172 - clarify units of trickle timers
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 24 Aug 2015 00:48:32 -0000

Thanks for clarifications.
I'll update the document on this week. Sorry for late update.

Yusuke

On 2015-08-24 09:04, Michael Richardson wrote:
>
> Kerry Lynn <kerlyn@ieee.org> wrote:
>      >>> It will be a nuisance if sets of nodes must be initialized with
>      >>> different
>      >>> Imin and Imax values to reach the same behaviour.
>      >>> The same problem will occur when a YANG (SMIv2) description is
>      >>> made for
>      >>> managing these parameters.
>
>      >> I think that we expect that Imax is in units of multiple of
>      >> Imin,
>      >> which
>      >> is in units of TUNIT. Is that part at least, non-controversial?
>
>      >> Imax is expressed as *doublings* of Imin, which is a tighter
>      >> constraint than "multiple".
>      >> It also represents an upper bound on the interval length.
>
>      > so, if the Imax field contains "5", does that mean that
>      > Imax = 2^5 * Imin (* TUNIT)
>
>      kerry> According to the example in Section 4.1 of RFC 6206, yes. It refers
>      kerry> to "the amount of time specified by Imax" (which should probably have
>      kerry> its own name to avoid confusion).
>
> I'd like the DHCP parameter document to more closely refer to this, and
> perhaps even copy the example from 6206 then.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>