[netconf] Éric Vyncke's No Objection on draft-ietf-netconf-yang-push-22: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 29 April 2019 13:12 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: netconf@ietf.org
Delivered-To: netconf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B991202FF; Mon, 29 Apr 2019 06:12:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-netconf-yang-push@ietf.org, Kent Watsen <kent+ietf@watsen.net>, netconf-chairs@ietf.org, kent+ietf@watsen.net, netconf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <155654356221.15895.6935060528947597341.idtracker@ietfa.amsl.com>
Date: Mon, 29 Apr 2019 06:12:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/G03NLVFJ4lSW1Ci11gct2YRL08w>
Subject: [netconf] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-netconf-yang-push-22=3A_=28with_COMMENT=29?=
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 13:12:42 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-netconf-yang-push-22: 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-netconf-yang-push/



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

Getting a streaming telemetry for changes in datastore appears quite useful.

Please note that I did not review in depth after the section 4.

Comments
--------

C1) Out of curiosity, it is surprising for a netconf wg document to have 7
errors indicated by the YANG validator. Are they real errors or is the `pyang`
validator incorrect or missing references?

C2) 7 authors... the limit is usually 5 authors max. Can you justify?

C3) section 2. It should be RFC 8174 without citing RFC 2119.

C4) section 3.7, why not forcing a resynch (and a patch-id of 0) rather than
simply rolling explicitly the patch-id to 0. The latter seems to me as prone to
synchronization errors.

Nits
----

N1) unsure why all Cisco Systems authors are not grouped together

N2) "Xpath": should be described (or having a reference) before first use in
section 3.6

N3) a couple of "yang" in lowercase while I believe "YANG" is always written in
uppercase