IETF Logo Mail Archive

Re: [6tisch] [Call for Review] draft-ietf-6tisch-msf-03

<toshio9.ito@toshiba.co.jp> Tue, 23 April 2019 00:51 UTC

Return-Path: <toshio9.ito@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 4834F1202A3 for <6tisch@ietfa.amsl.com>; Mon, 22 Apr 2019 17:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 SBIVpIYiXuyx for <6tisch@ietfa.amsl.com>; Mon, 22 Apr 2019 17:51:55 -0700 (PDT)
Received: from mo-csw.securemx.jp (mo-csw1514.securemx.jp [210.130.202.153]) (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 9882B1202AB for <6tisch@ietf.org>; Mon, 22 Apr 2019 17:51:55 -0700 (PDT)
Received: by mo-csw.securemx.jp (mx-mo-csw1514) id x3N0pp3Q021968; Tue, 23 Apr 2019 09:51:51 +0900
X-Iguazu-Qid: 34ts1uRUeIEZeEMY2E
X-Iguazu-QSIG: v=2; s=0; t=1555980711; q=34ts1uRUeIEZeEMY2E; m=ygkxPDU93EOP+sTD07hO/zr5AZMFniZJG4gWo7Ebod4=
Received: from imx2.toshiba.co.jp (imx2.toshiba.co.jp [106.186.93.51]) by relay.securemx.jp (mx-mr1513) id x3N0poMq015633; Tue, 23 Apr 2019 09:51:50 +0900
Received: from enc01.localdomain ([106.186.93.100]) by imx2.toshiba.co.jp with ESMTP id x3N0poGt003522; Tue, 23 Apr 2019 09:51:50 +0900 (JST)
Received: from hop001.toshiba.co.jp ([133.199.164.63]) by enc01.localdomain with ESMTP id x3N0posk006559; Tue, 23 Apr 2019 09:51:50 +0900
From: toshio9.ito@toshiba.co.jp
To: tengfei.chang@gmail.com, 6tisch@ietf.org
Thread-Topic: [6tisch] [Call for Review] draft-ietf-6tisch-msf-03
Thread-Index: AQHU7om12W7S4Bn/P0yQjcGYDJ8uE6ZI+KIA
Date: Tue, 23 Apr 2019 00:51:46 +0000
X-TSB-HOP: ON
Message-ID: <OSAPR01MB3713ACD140322CF8D83F1582E5230@OSAPR01MB3713.jpnprd01.prod.outlook.com>
References: <CAAdgstQuMOK2YjXEc9w3yEEQJSOMBXdE_Ln3eq7n-0s7g+uucw@mail.gmail.com>
In-Reply-To: <CAAdgstQuMOK2YjXEc9w3yEEQJSOMBXdE_Ln3eq7n-0s7g+uucw@mail.gmail.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
authentication-results: spf=none (sender IP is ) smtp.mailfrom=toshio9.ito@toshiba.co.jp;
x-originating-ip: [103.91.184.0]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4fcccc75-e391-4ad7-0fa2-08d6c785dc97
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:OSAPR01MB5268;
x-ms-traffictypediagnostic: OSAPR01MB5268:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <OSAPR01MB526880B96F95B6184DB5B995E5230@OSAPR01MB5268.jpnprd01.prod.outlook.com>
x-forefront-prvs: 0016DEFF96
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(136003)(346002)(376002)(366004)(51914003)(189003)(199004)(76176011)(26005)(14454004)(25786009)(99286004)(76116006)(73956011)(5660300002)(486006)(966005)(66946007)(8676002)(53546011)(46636005)(102836004)(6506007)(2501003)(3846002)(110136005)(54896002)(478600001)(66066001)(316002)(2906002)(9686003)(52536014)(7736002)(236005)(6306002)(6116002)(74316002)(53936002)(66446008)(64756008)(66556008)(81156014)(81166006)(55016002)(6246003)(8936002)(66476007)(86362001)(6436002)(74482002)(606006)(229853002)(14444005)(7696005)(476003)(186003)(11346002)(446003)(71190400001)(71200400001)(256004)(33656002)(97736004)(68736007)(7756004); DIR:OUT; SFP:1101; SCL:1; SRVR:OSAPR01MB5268; H:OSAPR01MB3713.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: toshiba.co.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5ns/zuV2lBQ3123p+AXHP60XGGVaHJoXKXsA1KAP7mb+lY6GhRkZneo+6k58sQGj8zcwQjgG4DRFfgPWy8UEEWsnQjBbGIJw1HrAooxP1JI58M6N1tOEU32KhpGgA/CWdTHFex9xYdIoPFhAbneV8ZpHHWoaZLaRwiDDn+NTSmFjQDUt/cYDCx4NkWGcAlE6QsfYbuxfP7Rfzz08ZIcaoq8438uq6mI9lVP5qK64JvCwCRgSezhA9+qXhiTEU8jEt9qiT7zz8gkPGNMbijgA9aiY8UORJtqaPFnBzDhTLg9otxnCCDqQeAEYqHyeouTyWky5a3QOX6JJlNIvIgF60ldShbHUy2tr3IcKrzqt1SCUCtk8F5oTUvAQryIqnbBRY8Ty78tHc5YSOuppLtBkhYq9IIx4Yjr5y0sbE5ZCTUE=
Content-Type: multipart/alternative; boundary="_000_OSAPR01MB3713ACD140322CF8D83F1582E5230OSAPR01MB3713jpnp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4fcccc75-e391-4ad7-0fa2-08d6c785dc97
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Apr 2019 00:51:46.4248 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f109924e-fb71-4ba0-b2cc-65dcdf6fbe4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSAPR01MB5268
MSSCP.TransferMailToMossAgent: 103
X-OriginatorOrg: toshiba.co.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/fVA5HSgHhi1xLp-8yoO9tOqD9mk>
Subject: Re: [6tisch] [Call for Review] draft-ietf-6tisch-msf-03
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Apr 2019 00:51:59 -0000

Hi Tengfei,

Thanks for the work. The draft looks promising.

I have two comments on the managed cells.


* Minimum number of managed cells

Sec. 5.1: Revision -02 had the following sentence.

msf-02> To have the counters working, at least one unicast cell need
msf-02> to be maintained all the time and never be removed.

However, this is removed in -03. So, I think it's possible that msf-03
removes all managed cells, as a result of adaptation to the
traffic. Is it OK?


* Direction of managed cells

It looks like managed cells are only for upstream traffic.

In section 4.6, the joining node adds a Tx cell to the preferred
parent.

msf-03> Then it MUST issue a 6P ADD command MUST to that parent, with
msf-03> the following fields:
msf-03>    o  CellOptions: set to TX=1,RX=0,SHARED=0
msf-03>    o  NumCells: set to 1

In section 5.1, the node adds a Tx cell to the preferred parent to
adapt to the traffic.

msf-03> the node issues a 6P ADD command to its preferred parent to
msf-03> add one managed Tx cell to the TSCH schedule.

Because 6P transaction is always initiated from the child to the
preferred parent, and CellOption in 6P ADD request is always (?) Tx=1
RX=0, there is no downstream managed cells. As a result, downstream
packets such as DAO-ACK have to use AutoDownCell or the minimal
cell. I think we should have downstream cells, too.


Best regards,
Toshio Ito

From: 6tisch <6tisch-bounces@ietf.org> On Behalf Of Tengfei Chang
Sent: Tuesday, April 09, 2019 1:06 PM
To: 6tisch@ietf.org
Subject: [6tisch] [Call for Review] draft-ietf-6tisch-msf-03

Dear all,

A new version of "draft-ietf-6tisch-msf" is just published at here: https://www.ietf.org/id/draft-ietf-6tisch-msf-03.txt

This version mainly resolved the issues presented during IETF 104 meeting.
I would like to mention one of the main changes in this version is we removed the frame pending bit feature.

It's for two reasons:
- it will influence the "adapt to traffic" strategy of MSF.
- the "adapt to traffic" strategy has the ability to handle burst traffic by using a smaller MAX_NUMCELLS

Now we are calling for reviews on the new version of MSF!
Any comments and feedback are appreciated!

Tengfei



--
Chang Tengfei,
Postdoctoral Research Engineer, Inria

v2.23.0 | Report a Bug | By Email