Re: [netmod] [netconf] RE: pls clarify get operation

Qin Wu <> Sun, 21 July 2019 14:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 05B3B120020; Sun, 21 Jul 2019 07:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UCYeXNLggED9; Sun, 21 Jul 2019 07:58:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 716031200B6; Sun, 21 Jul 2019 07:58:52 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 47AC06503978D906291E; Sun, 21 Jul 2019 15:58:50 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 21 Jul 2019 15:58:49 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Sun, 21 Jul 2019 15:58:48 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Sun, 21 Jul 2019 15:58:47 +0100
Received: from ([]) by ([]) with mapi id 14.03.0439.000; Sun, 21 Jul 2019 22:58:44 +0800
From: Qin Wu <>
To: Kent Watsen <>
CC: "" <>, "" <>
Thread-Topic: [netconf] [netmod] RE: pls clarify get operation
Thread-Index: AdU9ETq4sTpTMz3bTxurvnfGNPR27gCw1Dg5
Date: Sun, 21 Jul 2019 14:58:43 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA8816CEFnkgeml513mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] [netconf] RE: pls clarify get operation
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 21 Jul 2019 14:58:56 -0000

I blieve there is sufficient discussion on this issue, we have requested a timeslot in netmod session to give the update, hopefully conluded this discussion. Thanks!


发件人: netconf [] 代表 Qin Wu []
发送时间: 2019年7月18日 10:43
收件人: Kent Watsen
主题: Re: [netconf] [netmod] RE: pls clarify get operation

发件人: Kent Watsen []
发送时间: 2019年7月10日 2:31
收件人: Qin Wu <>
主题: Re: [netconf] [netmod] RE: pls clarify get operation

[Just back from a 4th of July thing]

Hi Qin,
It provides guideline how to create temporary non-NMDA module from NMDA module, but temporary non-NMDA module is not standard module. So everybody will create the same temporary non-NMDA module?
I also feel this second paragraph is not very clear, especially the last sentence,  is nested config false data nodes part of NMDA module or temporary non-NMDA
Module? Looks like  nested config false data node part of NMDA module?
True, but as I wrote Frank on the 28th:

"Some drafts already publish a "state" module in their Appendix and, when they do, there is a completely standard non-NMDA IETF solution.  I don't know if this strategy is being followed universally but, if not, then I don't believe the IETF would object at all to the publication of drafts for missing state models in drafts that only assumed NMDA."

Are you facing this situation currently?   If so, with which modules?  Have you considered submitting an I-D to define the missing state tree module?

[Qin]: Yes, we are looking for completely standard non-NMDA IETF solution in this NMDA transition time period, since we assume many NETCONF clients in the existing deployment don’t support NMDA. We are not sure state module in the appendix is standard non-NMDA model or not? How many operators and implementer will use them as standard model.
Yeah, for some of other model may not define such state module in the appendix.
Can non-NMDA client consume NMDA module?

Sort of.  The config-true nodes will appear in the <running> as usual, and the config-false nodes can be accessed via the standard operations.  But there will be issues as, for instance, the config-false nodes will only appear for configured items and the operational value for config-true nodes will be missing, the latter of which may be important as an NMDA-optimized data model is unlikely to define config-false nodes for any config-true nodes, and hence the config-false that are defined may be far and few between, leading to an unacceptably incomplete upstate view.

[Qin]:That is exactly the issue we are facing. How do we as Non-NMDA client use NDMA module to get system generated configuration. I assume config false nodes for config-true nodes are referred to system generated configuration. These system generated configuration can not be obtained through get operation.