[Netconf] NETCONF NMDA <get-data> on conventional datastore

Rohit R Ranade <rohitrranade@huawei.com> Tue, 05 June 2018 09:27 UTC

Return-Path: <rohitrranade@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 6F4C2130F29; Tue, 5 Jun 2018 02:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ueEqkc5Fc6Pf; Tue, 5 Jun 2018 02:27:07 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 60431130E61; Tue, 5 Jun 2018 02:27:07 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 5D2D561287A78; Tue, 5 Jun 2018 10:27:03 +0100 (IST)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 5 Jun 2018 10:27:04 +0100
Received: from DGGEML510-MBX.china.huawei.com ([169.254.2.6]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0382.000; Tue, 5 Jun 2018 17:26:54 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netconf@ietf.org" <netconf@ietf.org>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: NETCONF NMDA <get-data> on conventional datastore
Thread-Index: AdP8r0aCkN0iHcBKTemb29DO8r1+4w==
Date: Tue, 5 Jun 2018 09:26:53 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BBB91DE@dggeml510-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.150.121]
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6BBB91DEdggeml510mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/lcPNSSVWgznDG3tmr5zS5Ew8sjQ>
Subject: [Netconf] NETCONF NMDA <get-data> on conventional datastore
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing 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: Tue, 05 Jun 2018 09:27:10 -0000

Hi All,

RFC 8342 defines the conventional data-store as below

"
     identity conventional {
       base datastore;
       description
         "Abstract base identity for conventional configuration
          datastores.";
     }
"

So when using the data-store-ref with NETCONF <get-data> as below:

<rpc message-id="101"
        xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
     <get-data
             xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-nmda"
             xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores">
       <datastore>ds:conventional</datastore>
    </get-data>
</rpc>

The libyang parser was successfully able to parse this as a valid data-store-ref. But conceptually this is not a valid data-store as it is an "abstract base identity".
NETCONF Server will have to add code to send error when conventional data-store comes in input.  I would prefer if we can control this using data-model statements then the parser can handle the error. Any thoughts ?


With Regards,
Rohit R Ranade