[6tisch] Mirja Kühlewind's No Objection on draft-ietf-6tisch-enrollment-enhanced-beacon-13: (with COMMENT)

Mirja Kühlewind via Datatracker <noreply@ietf.org> Tue, 18 February 2020 12:31 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 EB8411207FE; Tue, 18 Feb 2020 04:31:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-6tisch-enrollment-enhanced-beacon@ietf.org, Pascal Thubert <pthubert@cisco.com>, 6tisch-chairs@ietf.org, pthubert@cisco.com, 6tisch@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.117.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Mirja Kühlewind <ietf@kuehlewind.net>
Message-ID: <158202907388.14130.11373306134419981744.idtracker@ietfa.amsl.com>
Date: Tue, 18 Feb 2020 04:31:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/Qju2RMfu1Z7kjtENMVJ_2nb_vhg>
Subject: [6tisch] Mirja Kühlewind's No Objection on draft-ietf-6tisch-enrollment-enhanced-beacon-13: (with COMMENT)
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, 18 Feb 2020 12:31:14 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-6tisch-enrollment-enhanced-beacon-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-6tisch-enrollment-enhanced-beacon/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

One question: How is the proxy priority supposed to be calculated/set? Is there
a default value?

Is also support points raised in Roman's discuss points. More clarification is
needed.

Editorial comment:
I would recommend to repeat the abstract in the intro as, as stated in the RFC
style guide RFC7322 section 4.3, "[...] an Abstract is not a substitute for an
Introduction; the RFC should be self-contained as if there were no Abstract."

Nit: sec 1.3:
s/Although However/Although/ or s/Although However/However/ ?
s/a unicast RS may be transmitted in response[RFC6775] reduces the amount
of.../a unicast RS that may be transmitted in response [RFC6775] reduces the
amount of.../ ? (Also note missing space before [)