Re: [Netconf] Warren Kumari's No Objection on draft-ietf-netconf-nmda-netconf-06: (with COMMENT)

Martin Bjorklund <mbj@tail-f.com> Mon, 01 October 2018 07:04 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2E1130DD5; Mon, 1 Oct 2018 00:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Ns3OrGM5EgBN; Mon, 1 Oct 2018 00:04:28 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 25A08130934; Mon, 1 Oct 2018 00:04:28 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 411491AE03DD; Mon, 1 Oct 2018 09:04:26 +0200 (CEST)
Date: Mon, 01 Oct 2018 09:04:25 +0200
Message-Id: <20181001.090425.762031042763991630.mbj@tail-f.com>
To: warren@kumari.net
Cc: iesg@ietf.org, draft-ietf-netconf-nmda-netconf@ietf.org, mjethanandani@gmail.com, netconf-chairs@ietf.org, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <153774762713.29234.13520591093910263393.idtracker@ietfa.amsl.com>
References: <153774762713.29234.13520591093910263393.idtracker@ietfa.amsl.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/0DcVe-tCOH5F69zU5ZCsZM2hG6E>
Subject: Re: [Netconf] Warren Kumari's No Objection on draft-ietf-netconf-nmda-netconf-06: (with COMMENT)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 01 Oct 2018 07:04:31 -0000

Hi,

Warren Kumari <warren@kumari.net> wrote:
> Warren Kumari has entered the following ballot position for
> draft-ietf-netconf-nmda-netconf-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:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-nmda-netconf/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I'll be honest -- I was expecting this review to be long, annoying and
> unpleasant. It is documenting changes to some fundamental bits, and on matters
> where I always feel like I *should( have more expertise / knowledge... and so I
> set aside time on a flight to be able to focus on this....
> 
> It turns out to have been a very well, clearly written and understandable
> document...
> 
> I only have a *minor* suggestion:
> "3.1.1.3.  Example: Retrieving an entire subtree from <running>
> 
> The following example shows the <get-data> version of the
>    <get-config> example shown in Section 7.1 of [RFC6241].
> "
> 
> Seeing that this is an introductory example, I think that it would be nice to
> make it clearer that this filters users subtree; it is clear once reading the
> example, but knowing what it is supposed to be demonstrating before seeing it
> might be nice...

Ok.  How about:

OLD:

   The following example shows the <get-data> version of the
   <get-config> example shown in Section 7.1 of [RFC6241].

NEW:

   The following example shows the <get-data> version of the
   <get-config> example shown in Section 7.1 of [RFC6241], which selects
   the entire "/users" subtree:




/martin