[netmod] Comments on draft-ietf-netconf-nmda-netconf-05

Rohit R Ranade <rohitrranade@huawei.com> Tue, 24 April 2018 13:09 UTC

Return-Path: <rohitrranade@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1FF33127AD4 for <netmod@ietfa.amsl.com>; Tue, 24 Apr 2018 06:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9cyWJwMG_zPB for <netmod@ietfa.amsl.com>; Tue, 24 Apr 2018 06:09:21 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A03E126C19 for <netmod@ietf.org>; Tue, 24 Apr 2018 06:09:21 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id A08E44C7BD6D1 for <netmod@ietf.org>; Tue, 24 Apr 2018 14:09:16 +0100 (IST)
Received: from DGGEMA404-HUB.china.huawei.com ( by LHREML712-CAH.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 24 Apr 2018 14:09:18 +0100
Received: from DGGEMA502-MBX.china.huawei.com ([]) by DGGEMA404-HUB.china.huawei.com ([]) with mapi id 14.03.0361.001; Tue, 24 Apr 2018 21:09:08 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Comments on draft-ietf-netconf-nmda-netconf-05
Thread-Index: AdPbx8ZmmFXO/JW6Snea5zZ5ApuR+g==
Date: Tue, 24 Apr 2018 13:09:07 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6B1E8D96@DGGEMA502-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6B1E8D96DGGEMA502MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/YNOiRaW_xjcOVeeZaRxgC7Rgjw8>
Subject: [netmod] Comments on draft-ietf-netconf-nmda-netconf-05
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2018 13:09:23 -0000

Hi All,

Please find some comments for the draft.

1.       If "config-filter" leaf is not given for <get-data> whether we can add explicit text that both config=true and config=false nodes will be selected.

2.       In the YANG module description for "config-filter" , also it is not clear about what happens if the leaf is not given in filter. I feel better we keep the style like RESTCONF RFC 8040 Section 4.8.1 , with "content" having  config/nonconfig/all

3.       Regarding the "max-depth" parameter, I feel we should take the text about how "depth" is calculated for each node from RESTCONF RFC from Section 4.8.2 and add it to this draft. What will be depth of parent keys which are auto-selected when selecting on child nodes. Maybe some example regarding using of "max-depth" will be helpful.

4.       For the <get-data> filter mechanism, since there are 4 filters (filter-spec and config-filter and max-depth and with-defaults), whether we can mention that all these filters are AND'ed. Also whether there is a suggested order to apply filter ? I think "max-depth" filter has to be applied last. Others maybe any order is OK.

5.       negated-origin-filter : Regarding this I feel we can add a sentence as to when user should use "negated-origin-filter" , as "origin-filter" also can be used for this purpose.

With Regards,
Rohit R Ranade