[netmod] NMDA DataStore Read-Only / Write-able programmability

Rohit R Ranade <rohitrranade@huawei.com> Thu, 03 May 2018 10:11 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 64B421200F1 for <netmod@ietfa.amsl.com>; Thu, 3 May 2018 03:11:10 -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 IEbt6xQqSBNs for <netmod@ietfa.amsl.com>; Thu, 3 May 2018 03:11:04 -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 093E01252BA for <netmod@ietf.org>; Thu, 3 May 2018 03:11:04 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 8FB43F9D69877 for <netmod@ietf.org>; Thu, 3 May 2018 11:11:00 +0100 (IST)
Received: from DGGEMA406-HUB.china.huawei.com ( by lhreml709-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 3 May 2018 11:11:01 +0100
Received: from DGGEMA502-MBS.china.huawei.com ([]) by DGGEMA406-HUB.china.huawei.com ([]) with mapi id 14.03.0361.001; Thu, 3 May 2018 18:10:53 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] NMDA DataStore Read-Only / Write-able programmability
Thread-Index: AdPixRIB0M7SoKBRTEKVAgOLu2eK5w==
Date: Thu, 3 May 2018 10:10:53 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6B1F7204@DGGEMA502-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6B1F7204DGGEMA502MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/RseqvEfbrYMWMYwONwnYvIXfvA0>
Subject: [netmod] NMDA DataStore Read-Only / Write-able programmability
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: Thu, 03 May 2018 10:11:10 -0000

Hi All,

Currently I see in the NMDA RFC, that whether a data-store is write-able or read-only is mentioned in the RFC sections, but not in the YANG module. So user cannot know if write-able or not by looking at the NMDA Yang modules .

For example <intended> and <operational> are read-only. So the NETCONF <edit-data> cannot be done on these data-stores.

"If an <edit-data> operation is invoked on a non-writable
   datastore, then an error is returned, as specified in
   "ietf-netconf-nmda"" ==> How can ietf-netconf-nmda know at run-time whether a data-store supports write or not ? Hard-code ? How to handle for new data-stores which use the dynamic identity  ?

With Regards,
Rohit R Ranade