[Ntp] Éric Vyncke's No Objection on draft-ietf-ntp-yang-data-model-16: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Thu, 10 February 2022 14:08 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ntp@ietf.org
Delivered-To: ntp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 392F73A0DA7; Thu, 10 Feb 2022 06:08:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ntp-yang-data-model@ietf.org, ntp-chairs@ietf.org, ntp@ietf.org, Dieter Sibold <dsibold.ietf@gmail.com>, dsibold.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <164450209321.9264.570991062959040019@ietfa.amsl.com>
Date: Thu, 10 Feb 2022 06:08:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/VhDIg92KXMIj-e1eUR1A_HiLBbg>
Subject: [Ntp] Éric Vyncke's No Objection on draft-ietf-ntp-yang-data-model-16: (with COMMENT)
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Network Time Protocol <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2022 14:08:14 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-ntp-yang-data-model-16: 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/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-ntp-yang-data-model/



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

Thank you for the work put into this document. With the update of the normative
references, I have cleared my blocking DISCUSS (kept it in the notes for
archival only).

Special thanks for Dieter Sibold as the document shepherd write-up includes
text about the WG consensus.

Please find below one blocking DISCUSS point (but really trivial and easy to
address), some non-blocking COMMENT points (but replies would be appreciated),
and some nits.

I hope that this helps to improve the document,

Regards,

-éric

== previous DISCUSS (kept only for archive)

-- Section 13.1 --
As RFC 7317 is imported by the YANG module, it must be a normative reference.

== COMMENTS ==

Should the NTP version(s) be mentioned in the abstract ?

-- Section 1 --
The text appears to indicate that the associations can be configured while the
tree diagram indicateds tha associations are read-only. Should the associations
text moved to the section 1.1 (i.e., operational states) ?

-- Section 1.5 --
Using a table for listing references is unusual. Is there a reason why this
form is used ?

-- Section 8 --
Should there be more constraints on "ntp-version" ? I.e., a minimum of 3 ?