Re: [6tisch] WGLC for https://www.ietf.org/id/draft-ietf-6tisch-architecture-17.txt

Yasuyuki Tanaka <yasuyuki.tanaka@inria.fr> Thu, 06 December 2018 15:58 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 2FD84130E1A for <6tisch@ietfa.amsl.com>; Thu, 6 Dec 2018 07:58:31 -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_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 3sKRyaZRekHC for <6tisch@ietfa.amsl.com>; Thu, 6 Dec 2018 07:58:29 -0800 (PST)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) (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 92DFF130E19 for <6tisch@ietf.org>; Thu, 6 Dec 2018 07:58:28 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.56,322,1539640800"; d="scan'208";a="288167660"
Received: from wifi-pro-82-176.paris.inria.fr ([128.93.82.176]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Dec 2018 16:58:26 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Yasuyuki Tanaka <yasuyuki.tanaka@inria.fr>
In-Reply-To: <dbe324f3422a48769377c64bbfa78b80@XCH-RCD-001.cisco.com>
Date: Thu, 06 Dec 2018 16:58:26 +0100
Cc: Yasuyuki Tanaka <yasuyuki.tanaka@inria.fr>, "6tisch@ietf.org" <6tisch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC5D670A-8CC1-476E-95B9-E9A2839BEEB0@inria.fr>
References: <eaeba2a200c644738778e865a5f539b2@XCH-RCD-001.cisco.com> <102BCDE7-8750-4E09-84F2-00FFC589F2BC@inria.fr> <dbe324f3422a48769377c64bbfa78b80@XCH-RCD-001.cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/MH-glhDJJnHod6gqKTZN-NFcgjY>
Subject: Re: [6tisch] WGLC for https://www.ietf.org/id/draft-ietf-6tisch-architecture-17.txt
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: Thu, 06 Dec 2018 15:58:31 -0000

Thank you, Pascal.

> Please let me know if you intend to provide a review soon.

Yes. Here are my additional but minor comments:

---

[Definition of 6P / Section 2.2 and Figure 1]

In the terminology section, 6top is explained as follows:

   6top (6TiSCH Operation Sublayer):  The next highest layer of the IEEE
               Std 802.15.4 TSCH medium access control layer.  It
               implements and terminates 6P, and contains at least one
               SF.

However, 6top doesn't contain SFs in Figure 1. My understanding on 6top is the same as Figure 1. In addition, the original text says that 6top "contains at least one SF". However, 6TiSCH could work without SF. Then, the explanations of 6top and 6P in Section 2.2 would be:

   6top (6TiSCH Operation Sublayer):  The next higher layer of the IEEE
               Std 802.15.4 TSCH medium access control layer.  It
               provides the abstraction of an IP link over a TSCH
               MAC, schedules packets over TSCH cells, and expose a management
               interface to schedule TSCH cells.

   6P (6top Protocol):  Allows neighbor nodes to communicate to add/
               delete cells to one another in their TSCH schedule. 6P is terminated at
               the 6top layer.

[Terminology / Section 2.2]

Are these terms common? It seems so, but they are not used in the draft nor in RFC7554/RFC8180/RFC8480, are they?: 

   blacklist of frequencies:  A set of frequencies which should not be
               used for communication.

   broadcast cell:  A scheduled cell used for broadcast transmission.

Does "broadcast cell" means a cell having the broadcast MAC address in its neighbor MAC address field? I'd like to have more text on them or to remove them.

["6P protocol"]
"6P protocol" is used three times in the draft, which should be replaced with "6P" (or "6top Protocol").

---

That's all :-) 

> Maybe we'll work on them in PAW ML. Did you register?

Yes, I did.

Thanks!
Yatch