[secdir] Secdir last call review of draft-ietf-lpwan-schc-yang-data-model-14

Carl Wallace via Datatracker <noreply@ietf.org> Mon, 01 August 2022 11:15 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 71095C13CCDE; Mon, 1 Aug 2022 04:15:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carl Wallace via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-lpwan-schc-yang-data-model.all@ietf.org, last-call@ietf.org, lp-wan@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165935255145.43093.548189515219549798@ietfa.amsl.com>
Reply-To: Carl Wallace <carl@redhoundsoftware.com>
Date: Mon, 01 Aug 2022 04:15:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/72ojPbuKdwBMMpR0N1igRdIfCzk>
Subject: [secdir] Secdir last call review of draft-ietf-lpwan-schc-yang-data-model-14
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2022 11:15:51 -0000

Reviewer: Carl Wallace
Review result: Ready

This document describes a YANG data model for the SCHC (Static Context Header
Compression) compression and fragmentation rules. The bulk of the document is
the YANG module, which I did not review as I am not a YANG expert. The rest of
the document was fine and mostly consisted of conventions for what appears in
the YANG module. The security considerations seemed sufficient. One minor nit,
in the last sentence of security considerations, the phrase "including access
right and identities" doesn't seem quite right. Maybe "including access
controls and identities"?