[6tisch] Genart last call review of draft-ietf-6tisch-msf-10

Vijay Gurbani via Datatracker <noreply@ietf.org> Fri, 14 February 2020 16:42 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 D213312087F; Fri, 14 Feb 2020 08:42:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Vijay Gurbani via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-ietf-6tisch-msf.all@ietf.org, last-call@ietf.org, 6tisch@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.117.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Vijay Gurbani <vijay.gurbani@gmail.com>
Message-ID: <158169855672.16297.13529972066012125176@ietfa.amsl.com>
Date: Fri, 14 Feb 2020 08:42:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/_TDJsHBW8SpuDwy3oQzNiHCHelw>
Subject: [6tisch] Genart last call review of draft-ietf-6tisch-msf-10
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: Fri, 14 Feb 2020 16:42:37 -0000

Reviewer: Vijay Gurbani
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-6tisch-msf-10
Reviewer: Vijay K. Gurbani
Review Date: 2020-02-14
IETF LC End Date: 2020-02-27
IESG Telechat date: Not scheduled for a telechat

Summary: The draft is almost ready to be published as a Proposed Standard.

Major issues: 1

Minor issues: 0

Nits/editorial comments: 1

Sn below stands for "Section n".


- S2, paragraph 4: The text says that "...a node implementing MSF SHOULD enforce
  some rules for limiting the traffic broadcast frames...".  It goes ahead and
  gives an example of the "Trickle" operation, but in the very next sentence, it
  says, "This behavior is out of the scope for MSF."  I am confused since the
  paragraph does not seem self consistent.

  The paragraph is asking the implementor to use normative strength (SHOULD) to
  enforce "some" rules, but does not enumerate the rules.  To be fair, the
  paragraph gives one example of such a rule, but immediately invalidates that
  example!  What would an implementor do?  Where would he or she go to get an
  idea of "some" rules that can be used to limit the traffic of broadcast
  frames? Perhaps some reference could be provided to a document that contains
  these rules? 


 - S6: s/It is calculated/The timeout value is calculated/

Thank you.