Re: [netconf] Genart last call review of draft-ietf-netconf-yang-push-22

"Alexander Clemm" <ludwig@clemm.org> Wed, 24 April 2019 19:07 UTC

Return-Path: <ludwig@clemm.org>
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 A30F7120229; Wed, 24 Apr 2019 12:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 0qT33DKyZoVs; Wed, 24 Apr 2019 12:07:36 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2636E12031B; Wed, 24 Apr 2019 12:07:36 -0700 (PDT)
Received: from LAPTOPR7T053C2 ([73.189.160.186]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0MN33W-1hPxsc1F7o-006hut; Wed, 24 Apr 2019 21:07:34 +0200
From: "Alexander Clemm" <ludwig@clemm.org>
To: "'Stewart Bryant'" <stewart.bryant@gmail.com>, <gen-art@ietf.org>
Cc: <draft-ietf-netconf-yang-push.all@ietf.org>, <ietf@ietf.org>, <netconf@ietf.org>
References: <155492884208.22557.5359832641233656648@ietfa.amsl.com>
In-Reply-To: <155492884208.22557.5359832641233656648@ietfa.amsl.com>
Date: Wed, 24 Apr 2019 12:07:33 -0700
Message-ID: <10b201d4fad0$f9c70ba0$ed5522e0$@clemm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHrc+2ifezD3Octa5HoVdP9sewhBKYetUPg
Content-Language: en-us
X-Provags-ID: V03:K1:8hFbDztrTFEsdngsv3W4flfJE9efXPx+diorVWGAcGc46Ivi7PU GlB8zCUYGrSGmMnDVS0ZS2KyKFcww5oCAblq1p8genhVd02u5ZQoZrfFvljhQX4VvJorjWo iPMnhRO4XOefNPj5s70EnDR4358uED158Y5n9WLMMO90LLPTYo+/uH4VvaNI2XTy+0EyQQB 6L6vtf3jpB+zsSJa5+tqQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:fDTKLxFDV4g=:FMWpHn0zp0UPUf6p8EEi89 NulZGFFb4A4xXvzcPaCExWh+R0ihQWMLd40VogeKefG9RJcs9BWks2on2484owDzx2ZDh8qUC XSVwfW4e3Qx5cWxUPPaaNFlPE6aM4OZinbxmhOcmqoCESvU9GS+xrgs/ZflEwoOsTxRVgOD5t gzF6UxRhxLmKQe3yn02smoGd5J0xl7iOjF2rq8W2TZfdxcAPm6pCGHmZXtwb8tWjoVB9KGizX Ajl1AoIWfKNDOmhYNrjY/kRvNSeguwP2hgef3nzxU1VM0LktvwEb28Iv5uapeWg4eXI04Igct rtOnK7Lkq+O6oESLUgUuVhKOB99up99S/caBHW/+5wWNHYrDfL4ziTOzyPvlGFUekGLSNuiZe lDTSFraqs/Ttyx3U4qoNI44ROfYeq+GpQHwupjVfbjapvYNCMbVy+JXLyx9YSxFKNaep4WNe7 lJpqFV28rAi5SzOFDNWv7dyz1yikB4as9xb+k2NAfNnSrEbGnc+2kIWArZx57Ds2GlFQWQThb H++OQ1DwlBQWoFC67F9UFG4odwbjuW7rYUUbWhDw0IYC2iFQuRWhGLjI56Kiyu1fzyTRcGLBz RlrzQZxY5C0r17JfuIjxwEzfoCv7jDzwUk67tA9KxizEj8cb0fGWTjm87ynFwpPvD6Rbn57tf Yqyqkk2V2fJoozLFycmCZvWSg4Y8ntCq+nTSeXWeoj/gTySIXD+iOEC44tbPiaGw+cpc5Ve3K IP9sQw2Cgr4A2raydRWMNzFX0zqVTQwtlSX9XvJlO1rPcRnB3who4pg9nt8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/wzQwzdUMHOwDORkRYMiRPDubuIg>
Subject: Re: [netconf] Genart last call review of draft-ietf-netconf-yang-push-22
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Wed, 24 Apr 2019 19:07:39 -0000

Hi Stewart,

Thank you for your comments!  Please find replies inline, <ALEX>

--- Alex

-----Original Message-----
From: netconf <netconf-bounces@ietf.org>; On Behalf Of Stewart Bryant via
Datatracker
Sent: Wednesday, April 10, 2019 1:41 PM
To: gen-art@ietf.org
Cc: draft-ietf-netconf-yang-push.all@ietf.org; ietf@ietf.org;
netconf@ietf.org
Subject: [netconf] Genart last call review of
draft-ietf-netconf-yang-push-22

Reviewer: Stewart Bryant
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG for
the IETF Chair.  Please treat these comments just like any other last call
comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>;.

Document: draft-ietf-netconf-yang-push-22
Reviewer: Stewart Bryant
Review Date: 2019-04-10
IETF LC End Date: 2019-04-12
IESG Telechat date: Not scheduled for a telechat

Summary: A well written document with just a small nuber of minor matter in
the nits section that need to be considered.

Major issues: None

Minor issues: None

Nits/editorial comments:

  ** Obsolete normative reference: RFC 7895 (Obsoleted by RFC 8525)
============

<ALEX> We will update the reference.
</ALEX>

SB> I assume that the ADs are happy with seven front page authors.

===========
 Abstract

   Via the mechanism described in this document, subscriber applications
SB> I am not sure if  starting a sentence with "via" is good English but 
SB> I have not seen it done before.

<ALEX> we think "via" is fine; if you prefer it to say "using", please let
us know and we will change it.  
</ALEX>

===========
   Traditional approaches to providing visibility into managed entities
   from remote have been built on polling.
SB> from remote what?

<ALEX> from a remote system, a remote application, a remote location.  
I do think this is clear; if you prefer it to say "from a remote system" we
will change; please let us know if you would prefer to make that change.  
</ALEX>

===========

3.10.  On-Change Notifiable Datastore Nodes

   In some cases, a publisher supporting on-change notifications may not
   be able to push on-change updates for some object types.  Reasons for
   this might be that the value of the datastore node changes frequently
   (e.g., [RFC8343]'s in-octets counter), that small object changes are
   frequent and meaningless (e.g., a temperature gauge changing 0.1
   degrees), or that the implementation is not capable of on-change
   notification for a particular object.

SB> I could not see the parameter range specifiy what is regarded as 
SB> trivial specified in the model. It seems that it perhaps ought to be.
===================

<ALEX> This will depend heavily on the object and its intended use.
Basically we are giving only reasons why an implementation might choose to
not support on-change notifications for a particular object.  Going deeper
into reasoning behind such implementation choices, what size would be
"small" or "large", and over what time interval, etc, would IMHO go beyond
the scope of this document.  We prefer not to make a change to the document.
(Please note that there is another draft on smart filters for push updates,
which might in the future add the ability for users to e.g. configure this
and other things.)
</ALEx>

   The next figure depicts augmentations of module ietf-yang-push to the
   notifications that are specified in module ietf-subscribed-
   notifications.  The augmentations allow to include subscription
SB> s/allow to include/allow the inclusion of/
===============


<ALEX> We will make this change.
</ALEX>

_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf