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

Alissa Cooper <alissa@cooperw.in> Wed, 01 May 2019 18:20 UTC

Return-Path: <alissa@cooperw.in>
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 EB31C120072; Wed, 1 May 2019 11:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=OgWEhiqm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Npg2vQou
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 IiBWo9JKNFAU; Wed, 1 May 2019 11:20:11 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DC7E120136; Wed, 1 May 2019 11:20:11 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id C581022540; Wed, 1 May 2019 14:20:10 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 01 May 2019 14:20:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=V LHprhnY5JK7x+HFKxjImARh387isesWPqfw5136dPE=; b=OgWEhiqmMhLOneOEg dd/G2w4sDjEBELfDUiFCjx/4/9Cdae6DuxBxVaPMhWBVSrNVrSZJXhA9i6Nhb99k TLuvm6KcAr46zwrLtMqLbeoS4t5vEI0QOvNP4DF3Ez0FUTD6VcKLLMK3J9xjxrqm 2COnwQmghp096n/YUldHD6y5fHCm+0LM/srMVVuyWcrfveARp4Xo6QECLOGrZ920 iXc1N5CjB5WiqN+Qkw7gK/tq9IaGM6RFbOWdLCyzIqc8oI+lpFYzrFgZbQIu8JVR o+ldBJ/+AuMRl84DhmpCEDiY5sARg7LYVpQwab5+63xW/Xjvw3BSj5DRcRMhKkWU cdKNg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=VLHprhnY5JK7x+HFKxjImARh387isesWPqfw5136d PE=; b=Npg2vQouM0Bq56+zKCcC+qU1KNBlB76TtprIWOJmhwa3IVM1KwVXJnbRb VF118LcJAB0RDGhmXa82XoUnJvyXjJUKCnXYrOHs0jT8fPeEwGgWxQDsDtziFZTa T+hjuN9LTV8E6HJ/xHYUj5+CI2vJ/Wpc8hlcN97HlsDq4fGkQv/NrXf3TTL848bB lKAmW22FRxw5/ZfVw+ydGhtQoOLOZCMX4DxDlL3SvnIH6viprmdBcslQbxqmYXWj kqNpme1RdKwMHiZKMJC075kaady5WgPxYgty0esxfg9xebtvQSW4Qzmg6B3+Aovg IOJp8jre5b1sucleOXDZhzp0Hn6lg==
X-ME-Sender: <xms:WuPJXIpPIkrhHdbuxsGwdsz3-jWlaEsjq8_yFQAqgFxSfwe-LV8LFg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieejgdduvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrleegnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd
X-ME-Proxy: <xmx:WuPJXAfF8mipCU2qazkyP7vy5s_mUvC1JOKNtLJPjGede9598R-xcg> <xmx:WuPJXO9XOx_ZqcVur-W524zw4qX7m5KD9jib_lDtLw2cAB620jiY8g> <xmx:WuPJXBH1urfvsXAmG7dBxJCZFGvO1rzpbfqGacz847wKcH21gGNG_w> <xmx:WuPJXPUMEe06Y3T1f95WSVOWNISZleWTXaYyi8LKg0AN9mEGFw3Xyw>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.94]) by mail.messagingengine.com (Postfix) with ESMTPA id 1AA29E4067; Wed, 1 May 2019 14:20:08 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <10b201d4fad0$f9c70ba0$ed5522e0$@clemm.org>
Date: Wed, 1 May 2019 14:20:05 -0400
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-netconf-yang-push.all@ietf.org, "<ietf@ietf.org>" <ietf@ietf.org>, netconf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B79DAF8-4B46-4B70-BFEF-4BCA4CB04FDE@cooperw.in>
References: <155492884208.22557.5359832641233656648@ietfa.amsl.com> <10b201d4fad0$f9c70ba0$ed5522e0$@clemm.org>
To: Alexander Clemm <ludwig@clemm.org>, Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/JDRImnQiKvPHgrXtLC0Aqpw5RGY>
Subject: Re: [netconf] [Gen-art] 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, 01 May 2019 18:20:14 -0000

Stewart, thanks for your review. Alex, thanks for your responses, they all make sense to me. I have entered a No Objection ballot.

Alissa

> On Apr 24, 2019, at 3:07 PM, Alexander Clemm <ludwig@clemm.org>; wrote:
> 
> 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
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art