[Netconf] Adam Roach's No Objection on draft-ietf-netconf-rfc7895bis-06: (with COMMENT)

Adam Roach <adam@nostrum.com> Thu, 11 October 2018 00:59 UTC

Return-Path: <adam@nostrum.com>
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 A32E4130DDC; Wed, 10 Oct 2018 17:59:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach <adam@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-netconf-rfc7895bis@ietf.org, Mahesh Jethanandani <mjethanandani@gmail.com>, netconf-chairs@ietf.org, mjethanandani@gmail.com, netconf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.86.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153921956365.5895.2867315554651220798.idtracker@ietfa.amsl.com>
Date: Wed, 10 Oct 2018 17:59:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/shn2U2UIXZHyB1T6Awej58gGVZ0>
Subject: [Netconf] Adam Roach's No Objection on draft-ietf-netconf-rfc7895bis-06: (with COMMENT)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Network Configuration WG mailing 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: Thu, 11 Oct 2018 00:59:24 -0000

Adam Roach has entered the following ballot position for
draft-ietf-netconf-rfc7895bis-06: 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:


Thanks for the work everyone did on this document.

ID Nits reports:

  ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446)
  ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341)


Page 16:

>      leaf checksum {
>        type string;
>        mandatory true;
>        description
>          "A server-generated checksum of the contents of the
>           'yang-library' tree.  The server MUST change the value of
>           this leaf if the information represented by the
>           'yang-library' tree, except 'yang-library/checksum', has
>           changed.";

I suspect that changing the name of this node in the tree would be disruptive
at this point in time, but this is clearly not a checksum ("There is no
requirement that the same information always results in the same 'checksum'
value"). I would suggest updating the description to use the term "version
identifier" or something similar.



>  [RFC8340]  Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
>             BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
>             <https://www.rfc-editor.org/info/rfc8340>.

Since this document is required to understand the syntax used in the tree
diagrams used by this document, it should be normative rather than informative.