[netmod] Eric Rescorla's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)
Eric Rescorla <ekr@rtfm.com> Wed, 07 March 2018 19:49 UTC
Return-Path: <ekr@rtfm.com>
X-Original-To: netmod@ietf.org
Delivered-To: netmod@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ABE371200F1; Wed, 7 Mar 2018 11:49:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-netmod-rfc6087bis@ietf.org, netmod-chairs@ietf.org, kwatsen@juniper.net, netmod@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.74.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152045215867.17597.99576332554022377.idtracker@ietfa.amsl.com>
Date: Wed, 07 Mar 2018 11:49:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/mwNaH90JTLah_vJqqvzw1QNi-dc>
Subject: [netmod] Eric Rescorla's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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, 07 Mar 2018 19:49:19 -0000
Eric Rescorla has entered the following ballot position for draft-ietf-netmod-rfc6087bis-18: 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-rfc6087bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- draft-ietf-netmod-rfc6087bis.txt:500 normative, if the module itself is considered normative, and not an example module or example YANG fragment. The use of keywords defined in [RFC2119] apply to YANG description statements in normative I think you probably want to rewrite this as: "Note that if the module itself is considered normative and not an example module or example YANG fragment, then all YANG statements..." o Prefixes are never allowed for built in data types and YANG keywords. I'm not sure I understand what this means. Is the idea that I can't use "example-import" somewhere? character MAY be used if the identifier represents a well-known value that uses these characters. Is this text saying that only characters in these two subsets are allowed and therefore, for instance "." is forbidden It is RECOMMENDED that only valid YANG modules be included in documents, whether or not they are published yet. This allows: For clarify, I assume you mean "the modules are published yet" The NETCONF Access Control Model (NACM) [I-D.ietf-netconf-rfc6536bis] does not support parameter access control for RPC operations. The user is given permission (or not) to invoke the RPC operation with This might be slightly clearer if you said "parameter-based access control"
- [netmod] Eric Rescorla's No Objection on draft-ie… Eric Rescorla
- Re: [netmod] Eric Rescorla's No Objection on draf… Andy Bierman
- Re: [netmod] Eric Rescorla's No Objection on draf… Eric Rescorla
- Re: [netmod] Eric Rescorla's No Objection on draf… Andy Bierman
- Re: [netmod] Eric Rescorla's No Objection on draf… Eric Rescorla
- Re: [netmod] Eric Rescorla's No Objection on draf… Andy Bierman
- Re: [netmod] Eric Rescorla's No Objection on draf… Eric Rescorla