Re: [netconf] Shepherd review of draft-ietf-netconf-notification-capabilities

Benoit Claise <benoit.claise@huawei.com> Fri, 16 April 2021 13:42 UTC

Return-Path: <benoit.claise@huawei.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 B80A33A26B2 for <netconf@ietfa.amsl.com>; Fri, 16 Apr 2021 06:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 grkj3cgKgB5D for <netconf@ietfa.amsl.com>; Fri, 16 Apr 2021 06:42:42 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EDBF3A26C8 for <netconf@ietf.org>; Fri, 16 Apr 2021 06:42:36 -0700 (PDT)
Received: from fraeml740-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FMHLw3t5jz68BlW for <netconf@ietf.org>; Fri, 16 Apr 2021 21:37:12 +0800 (CST)
Received: from fraeml740-chm.china.huawei.com (10.206.15.221) by fraeml740-chm.china.huawei.com (10.206.15.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 16 Apr 2021 15:42:32 +0200
Received: from DGGEMS404-HUB.china.huawei.com (10.3.19.204) by fraeml740-chm.china.huawei.com (10.206.15.221) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Fri, 16 Apr 2021 15:42:32 +0200
Received: from [10.47.79.27] (10.47.79.27) by DGGEMS404-HUB.china.huawei.com (10.3.19.204) with Microsoft SMTP Server id 14.3.498.0; Fri, 16 Apr 2021 21:42:26 +0800
To: Kent Watsen <kent+ietf@watsen.net>, Benoit <benoit@claise.be>
CC: "netconf@ietf.org" <netconf@ietf.org>
References: <a0e8e350-da03-69a6-80af-da578acfc478@claise.be> <f2c6123e-b8f8-8174-fa71-2f8a23dedab7@claise.be> <172a3cd6-dd95-c535-23d0-ffbd879d6319@claise.be> <AABCC3E0-AB21-42C9-89AE-AF2D75AEEC3D@watsen.net> <01000178d3063b0c-963bb741-e8e6-41bc-821e-bb25b421ed26-000000@email.amazonses.com>
From: Benoit Claise <benoit.claise@huawei.com>
Message-ID: <d9105da8-a634-50d5-ac88-f7e8b08f7fbe@huawei.com>
Date: Fri, 16 Apr 2021 15:42:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <01000178d3063b0c-963bb741-e8e6-41bc-821e-bb25b421ed26-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="------------2F20C9ED5E783F1F5CA43903"
Content-Language: en-GB
X-Originating-IP: [10.47.79.27]
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/62x0buDL4LEGlTS8E3UdtQ01aPE>
Subject: Re: [netconf] Shepherd review of draft-ietf-netconf-notification-capabilities
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: Fri, 16 Apr 2021 13:42:52 -0000

Hi Kent,

Thanks for your review.
See inline, after some clean up.
I addressed your two remaining comments and I posted a draft version: 
draft-ietf-netconf-notification-capabilities-16

>>
>>
>>>>>
>>>>>
>>>>>> - is the comment "The special value '/' denotes all data nodes in the
>>>>>> datastore.b consistent with XPath 1.0 expressions.
>>>>>> BALAZS: we are consistent witjh the NACM RFC, which says:
>>>>>> B B B B B B B B B B B B B B B B B B B The special value '/' 
>>>>>> refers to all possible
>>>>>> B B B B B B B B B B B B B B B B B B B datastore contents.";
>>>>>
>>>>> Then the comment should say b Section ???, the special valueb
>>>> Done.
>>>> B B B B B B B B B leaf node-selector {
>>>> B B B B B B B B B B B type nacm:node-instance-identifier;
>>>> B B B B B B B B B B B description
>>>> B B B B B B B B B B B B B "Selects the data nodes for which 
>>>> capabilities are
>>>> B B B B B B B B B B B B B B specified. The special value '/' 
>>>> denotes all data nodes
>>>> B B B B B B B B B B B B B B in the datastore, as specified in path 
>>>> YANG object in
>>>> B B B B B B B B B B B B B B data definition statement [RFC8341];
>>>> B B B B B B B B B B B reference
>>>> B B B B B B B B B B B B B B B "RFC 8341: Network Configuration 
>>>> Access Control Model";
>>>> B B B B B B B B B }
>>
>> Looking at the new draft, I see the added clarification (thanks), but 
>> it’s a bit difficult to read.  Would this help?
>>
>> OLD: as specified in path YANG object in data definition statement 
>> [RFC8341]
>>
>> NEW: consistent with the “path” leaf node on page 41 in [RFC8341].
Done.
Did not include the double quotes around path to avoid troubles.
>>
>>
>>>>>> - this command detected a number of issues: pyang -f yang 
>>>>>> --keep-comments --yang-line-length 69 
>>>>>> ietf-notification-capabilities\@2020-03-23.yang > tmp; diff 
>>>>>> ietf-notification-capabilities\@2020-03-23.yang tmp. (whitespace 
>>>>>> at end of lines)
>>>>>
>>>>> No response?
>>>> That was an oversight. Done for both modules
>>
>> Thanks, but be mindful that tool’s opinion is not always perfect and 
>> that discretion can override it where preferred.  The primary intent 
>> is to show that an effort was made...
>>
>> In particular, the closing “; for the "import ietf-yang-library” 
>> statement is on a line by itself.  IDK if the tool is suggesting 
>> this, but I think it better if the closing “; were brought up to the 
>> previous line.
Corrected.

Regards, Benoit