Re: [6tisch] Yatch's review on draft-ietf-6tisch-msf-08 - Re: MSF review

Yasuyuki Tanaka <yasuyuki.tanaka@inria.fr> Wed, 27 November 2019 23:37 UTC

Return-Path: <yasuyuki.tanaka@inria.fr>
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 C4D38120AF9 for <6tisch@ietfa.amsl.com>; Wed, 27 Nov 2019 15:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 tr0DUQT1wu_P for <6tisch@ietfa.amsl.com>; Wed, 27 Nov 2019 15:37:04 -0800 (PST)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (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 1AC8E12091B for <6tisch@ietf.org>; Wed, 27 Nov 2019 15:37:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.69,251,1571695200"; d="scan'208";a="413853901"
Received: from poi92-3-88-190-144-98.fbxo.proxad.net (HELO [192.168.1.29]) ([88.190.144.98]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 28 Nov 2019 00:37:01 +0100
Cc: yasuyuki.tanaka@inria.fr, 6tisch <6tisch@ietf.org>
To: Tengfei Chang <tengfei.chang@gmail.com>
References: <MN2PR11MB35655660E9DF5365BA4A1AD9D84A0@MN2PR11MB3565.namprd11.prod.outlook.com> <36e424c6-f40e-89b1-4cf1-1a25db501d72@inria.fr> <CAAdgstShO4Hpw5VrgakPnXy29Xpj3N77a8gaQ6y+_HkQDV2gRw@mail.gmail.com>
From: Yasuyuki Tanaka <yasuyuki.tanaka@inria.fr>
Message-ID: <f7b3f726-c05f-e9e7-d7c2-090870ab9bc7@inria.fr>
Date: Thu, 28 Nov 2019 00:37:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <CAAdgstShO4Hpw5VrgakPnXy29Xpj3N77a8gaQ6y+_HkQDV2gRw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/rI4aS2K5HrUmkXRMbNHCQeLCtZA>
Subject: Re: [6tisch] Yatch's review on draft-ietf-6tisch-msf-08 - Re: MSF review
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: Wed, 27 Nov 2019 23:37:06 -0000

Thank you, Tengfei.

> TC: we only mentioned 6P SIGNAL, because that's 6P leaves it to scheduling function, which must mention how it is used.

I understand that Section 6 corresponds to the following point mentioned 
Section 4.2 of RFC 8480:

rfc8480> The specification for an SF
rfc8480> ...
rfc8480>    o  SHOULD define the format of the SIGNAL command payload and
rfc8480>       its use.

I'm looking forward to the next version :-)

Best,
Yatch