Re: [6tisch] nits on draft-ietf-6tisch-6top-sf0-02

Yasuyuki Tanaka <yasuyuki9.tanaka@toshiba.co.jp> Sun, 05 March 2017 13:13 UTC

Return-Path: <yasuyuki9.tanaka@toshiba.co.jp>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E6B129473 for <6tisch@ietfa.amsl.com>; Sun, 5 Mar 2017 05:13:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 5JcuWBKa6tPW for <6tisch@ietfa.amsl.com>; Sun, 5 Mar 2017 05:13:12 -0800 (PST)
Received: from mo.tsb.2iij.net (mo1500.tsb.2iij.net [210.149.48.172]) (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 68454126D74 for <6tisch@ietf.org>; Sun, 5 Mar 2017 05:13:12 -0800 (PST)
Received: by mo.tsb.2iij.net (tsb-mo1500) id v25DDAkN020833; Sun, 5 Mar 2017 22:13:10 +0900
Received: from unknown [172.27.153.190] (EHLO tsb-mr1502.hop.2iij.net) by mas1511.tsb.2iij.net(mxl_mta-7.2.4-7) with ESMTP id 6ee0cb85.0.17844.00-697.32656.mas1511.tsb.2iij.net (envelope-from <yasuyuki9.tanaka@toshiba.co.jp>); Sun, 05 Mar 2017 22:13:10 +0900 (JST)
X-MXL-Hash: 58bc0ee621afc3e6-7a0684b408be181a1d168603f654e804b5d14738
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by relay.tsb.2iij.net (tsb-mr1502) with ESMTP id v25DDAtB018671 for <6tisch@ietf.org>; Sun, 5 Mar 2017 22:13:10 +0900
Received: from tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp ([133.199.232.103]) by imx12.toshiba.co.jp with ESMTP id v25DDAWi028286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <6tisch@ietf.org>; Sun, 5 Mar 2017 22:13:10 +0900 (JST)
Received: from tsbmgw-mgw01 (localhost [127.0.0.1]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id v25DDAxA005135 for <6tisch@ietf.org>; Sun, 5 Mar 2017 22:13:10 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw01 (JAMES SMTP Server 2.3.1) with SMTP ID 465 for <6tisch@ietf.org>; Sun, 5 Mar 2017 22:13:10 +0900 (JST)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id v25DD9P2005132 for <6tisch@ietf.org>; Sun, 5 Mar 2017 22:13:09 +0900
Received: (from root@localhost) by arc11.toshiba.co.jp id v25DD9HG019780 for 6tisch@ietf.org; Sun, 5 Mar 2017 22:13:09 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id YAA19779; Sun, 5 Mar 2017 22:13:09 +0900
Received: from mx12.toshiba.co.jp (mx12.toshiba.co.jp [133.199.90.142]) by ovp11.toshiba.co.jp with ESMTP id v25DD9vb017290 for <6tisch@ietf.org>; Sun, 5 Mar 2017 22:13:09 +0900 (JST)
Received: from spiffy20.isl.rdc.toshiba.co.jp by toshiba.co.jp id v25DD95a003470; Sun, 5 Mar 2017 22:13:09 +0900 (JST)
Received: from [133.196.17.218] (nm-pptp218.isl.rdc.toshiba.co.jp [133.196.17.218]) by spiffy20.isl.rdc.toshiba.co.jp (Postfix) with ESMTPSA id 1117715EA87; Sun, 5 Mar 2017 22:13:09 +0900 (JST)
To: 6tisch@ietf.org
References: <5AC19D61-FD48-457E-AACF-7F05CD180A2F@amalfisystems.com>
From: Yasuyuki Tanaka <yasuyuki9.tanaka@toshiba.co.jp>
Message-ID: <2dae41eb-119e-ca61-617a-74b273b9ff2d@toshiba.co.jp>
Date: Sun, 05 Mar 2017 22:13:05 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <5AC19D61-FD48-457E-AACF-7F05CD180A2F@amalfisystems.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp id v25DD9P2005132
X-MAIL-FROM: <yasuyuki9.tanaka@toshiba.co.jp>
X-SOURCE-IP: [172.27.153.190]
X-Spam: exempt
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/gZbCxJGlguM-pyV4zNn-QZE9q9U>
Subject: Re: [6tisch] nits on draft-ietf-6tisch-6top-sf0-02
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Mar 2017 13:13:14 -0000

Nice comments!

I also want to see the definition of "effectively used cell" and
how to calculate PDR.

In addition, I don't think that we would count the number of
cells used for 6P in terms of SF0. Is it correct? In any case,
some text on how SF0 should handle traffic or cell usage by 6P
would be helpful.

Best,
Yatch

On 2017/03/05 11:20, Randy Turner wrote:
> Hi All,
>
> After reading the current SF0 document, I had a few nits that I thought I would pass along - hope they’re helpful.
>
>
> Section 2: Introduction
>
> (The Scheduling Algorithm)
>
> “…under effective use…”   the choice of wording seems unorthodox.
>
> Suggest the following  “A portion of these allocated cells will be effectively utilized by neighbors, while the remaining cells can be over-provisioned to handle unanticipated increases in cell requirements”
>
> (The Relocation Algorithm)
>
> “Allocated cells may experiment packet loss” should be “Allocated cells may experience packet loss…”
>
>
>
> Section 4: SF0 Triggering Events
>
> 1. “…change in the current number of used cells”  - could this be paraphrased to say “…a change in the number of required cells”  ?
>
>
>
> Section 5: SF0 Estimation Algorithm
>
> The Cell Estimation Algorithm steps, # 2 - What is an “effectively” used cell?  Could this just say “Collect the current number of used cells” ?
>
> There is actually quite a bit of emphasis in this document on the idea of an “effectively used cell” - perhaps we should explain the concept of an effectively used cell (or a reference if it’s already defined) - I was curious why the term “effective” is used so often?  In the “Cell Estimation Algorithm” Step #2, the text reads:
> “Collect the current number of effectively used cells” — which would seem to imply that ineffectively used cells wouldn’t be included in this step.  This may seem a too literal interpretation, I’m just looking for clarity as to whether or not the term “effective” or “effectively” is really needed in the doc.
>
>
> Section 11: Relocating Cells
>
> Just for completeness, I would emphasize how PDR is calculated, or include a reference to some other document if defined elsewhere
>
>
>
>
> Thanks for this work!
> Randy
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>