Re: [netmod] Roman Danyliw's No Objection on draft-ietf-netmod-yang-data-ext-04: (with COMMENT)

Martin Bjorklund <mbj@tail-f.com> Wed, 04 December 2019 10:16 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B508D12025D; Wed, 4 Dec 2019 02:16:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7mKRpm8rBtP; Wed, 4 Dec 2019 02:16:11 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 556F312022A; Wed, 4 Dec 2019 02:16:11 -0800 (PST)
Received: from localhost (unknown [173.38.220.41]) by mail.tail-f.com (Postfix) with ESMTPSA id E84CE1AE02AA; Wed, 4 Dec 2019 11:16:08 +0100 (CET)
Date: Wed, 04 Dec 2019 11:15:34 +0100 (CET)
Message-Id: <20191204.111534.1623958569286243992.mbj@tail-f.com>
To: rdd@cert.org, noreply@ietf.org
Cc: iesg@ietf.org, draft-ietf-netmod-yang-data-ext@ietf.org, joelja@gmail.com, netmod-chairs@ietf.org, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <157541873026.4777.16036785628686534252.idtracker@ietfa.amsl.com>
References: <157541873026.4777.16036785628686534252.idtracker@ietfa.amsl.com>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ZjKj2mc0bbgxRWQo4xkMrLV7yIM>
Subject: Re: [netmod] Roman Danyliw's No Objection on draft-ietf-netmod-yang-data-ext-04: (with COMMENT)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2019 10:16:13 -0000

Roman Danyliw via Datatracker <noreply@ietf.org> wrote:
> Roman Danyliw has entered the following ballot position for
> draft-ietf-netmod-yang-data-ext-04: 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-netmod-yang-data-ext/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Section 6. Recommend staying consistent with the standard YANG
> security considerations
> (https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines) and
> at least include this following subset (or something like it) of the
> boiler plate language:
> 
>    The YANG module in this document defines an extension in the YANG data
>    modeling language that will be imported and used by other modules.  When
>    imported and used, the resultant schema will have data nodes that can
>    be writable, or readable.  The access to such data nodes may be
>    considered sensitive or vulnerable in some network environments.
>    Write operations (e.g., edit-config) to these data nodes without
>    proper protection can have a negative effect on network operations.

Hmm, I can't find this text in the boilerplate.  As discussed with
Benjamin Kaduk, we believe that the reference to 7950 is sufficient.

> Section 7.3.  What purpose will this section serve when published?  Is seems
> like it could be removed.  The only use of the [1] reference is Appendix C
> which is supposed to be removed before publication.

I have removed both 7.3 and Appendix C from my local copy.


/martin