[netmod] Operational state data in <get> operation

Rohit R Ranade <rohitrranade@huawei.com> Wed, 23 May 2018 05:31 UTC

Return-Path: <rohitrranade@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99F5B124235 for <netmod@ietfa.amsl.com>; Tue, 22 May 2018 22:31:39 -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 pH1Hbh0pTrKv for <netmod@ietfa.amsl.com>; Tue, 22 May 2018 22:31:37 -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 695D712025C for <netmod@ietf.org>; Tue, 22 May 2018 22:31:37 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 85A6EF136E457 for <netmod@ietf.org>; Wed, 23 May 2018 06:31:33 +0100 (IST)
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 23 May 2018 06:31:34 +0100
Received: from DGGEML510-MBX.china.huawei.com ([169.254.2.161]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0382.000; Wed, 23 May 2018 13:31:25 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Operational state data in <get> operation
Thread-Index: AdPyVqMugw8iIPM7TG2dz6SESDGWmg==
Date: Wed, 23 May 2018 05:31:23 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BBAF534@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_991B70D8B4112A4699D5C00DDBBF878A6BBAF534dggeml510mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/AsfvQgeNwXbweOaePyerGpe_yqw>
Subject: [netmod] Operational state data in <get> operation
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: Wed, 23 May 2018 05:31:40 -0000

Hi All,


RFC 6244 says below statements in Section 4.3.1

"   NETCONF does not follow the distinction formulated by the operators
   between configuration data, operational state data, and statistical
   data, since it considers state data to include both statistics and
   operational state data.
"

RFC 6241 definition for "state data":
   o  state data: The additional data on a system that is not
      configuration data such as read-only status information and
      collected statistics.

RFC 8342 definition:
   o  system state: The additional data on a system that is not
      configuration, such as read-only status information and collected
      statistics.  System state is transient and modified by
      interactions with internal components or other systems.  System
      state is modeled in YANG using "config false" nodes.

   o  operational state: The combination of applied configuration and
      system state.

According to NMDA, state-data and "system-state" are the same. So "state-data" does not include operational state data. This means that RFC 6244 understanding is inaccurate regarding state-data ? And hence <get> cannot output Operational state as shown below. Please clarify.

RFC 6241 : Description for <get>
7.7.  <get>

   Description:  Retrieve running configuration and device state
      information.

RFC 6241:
The <get-config> operation retrieves
   configuration data only, while the <get> operation retrieves
   configuration and state data.



With Regards,
Rohit R Ranade