[6tisch] Opsdir last call review of draft-ietf-6tisch-enrollment-enhanced-beacon-08

Qin Wu via Datatracker <noreply@ietf.org> Tue, 21 January 2020 13:12 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: 6tisch@ietf.org
Delivered-To: 6tisch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D4D711200F8; Tue, 21 Jan 2020 05:12:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Qin Wu via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: last-call@ietf.org, 6tisch@ietf.org, draft-ietf-6tisch-enrollment-enhanced-beacon.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Qin Wu <bill.wu@huawei.com>
Message-ID: <157961235471.28933.16198137615082431630@ietfa.amsl.com>
Date: Tue, 21 Jan 2020 05:12:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/xAct0cjYaog0O-EfsT0VX01_afo>
Subject: [6tisch] Opsdir last call review of draft-ietf-6tisch-enrollment-enhanced-beacon-08
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Jan 2020 13:12:35 -0000

Reviewer: Qin Wu
Review result: Ready

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

This document extends IEEE 802.15.4 with 6TiSCH Join and Enrollment Information
for layer 2 synchronization and layer 3 synchronization. I think this document
is ready for publication.

Major issue:
Not found

Minor issue:
1.      Abstract
Is small details about 6TiSCH join and enrollment information? If yes, why not
document it explicitly? Also it will be great to clarify in the abstract why
6TiSCH join and enrollment information needs to be carried? For which purpose?
2 Section 1, 1st paragraph s/slot designated a broadcast slot/slot designated
as a broadcast slot 3.Section 1.2 2nd paragraph s/annouce/announce 4. Section
1.2, last paragraph is slot/s slot per second? Please make clear about this.
5.Section 3, 2nd paragraph s/Beagon/Beacon 6.Section 4 Should the last
paragraph be moved after the first sentence and before the second sentence in
the first paragraph? How DODAGID is related to network ID? Should you add
DODAGID as a new abbreviation or term? When Dogagid is hashed, how interloper
can use the network ID to map out the extend of mesh network? What do you mean
by the extend of the mesh network? s/ provides some cover the addresses used
within the network/ provides some cover for the addresses used within the