[6tisch] Barry Leiba's Discuss on draft-ietf-6tisch-minimal-security-13: (with DISCUSS)

Barry Leiba via Datatracker <noreply@ietf.org> Wed, 30 October 2019 14:32 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 E513F120108; Wed, 30 Oct 2019 07:32:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-6tisch-minimal-security@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.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <157244593893.32540.12940667862215399690.idtracker@ietfa.amsl.com>
Date: Wed, 30 Oct 2019 07:32:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/VjQLXE5kOJxgW6kjb_N83dS6KeY>
Subject: [6tisch] Barry Leiba's Discuss on draft-ietf-6tisch-minimal-security-13: (with DISCUSS)
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: Wed, 30 Oct 2019 14:32:19 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-6tisch-minimal-security-13: Discuss

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:


I have some issues with the references here, which should be resolvable simply
by making some normative.

RFC 8505 provides terminology as well as neighbor discovery (in Sections 4.2
and 6), so it seems to me that it should be a normative reference.

As draft-ietf-6tisch-architecture is used for both necessary terminology and
concepts, I can’t see how it isn’t normative.  I did find that I had to check
it during my review.

In Section 5:
   In an operational 6TiSCH network, all frames MUST use link-layer
   frame security [RFC8180].

This would seem to be a MUST referring to 8180, making that a normative
reference as well.  But possibly this might not really be a MUST imposed here,
and is instead citing a requirement from elsewhere.  In that case, I would
simply remove the word “MUST”, so it is stating a fact, rather than a new
requirement.  You might similarly consider the subsequent sentence.  In any
case, I do wonder whether  7554 and 8180 should be normative.