Re: [Netconf] Review of draft-zheng-netconf-inline-action-capability-00

Qin Wu <bill.wu@huawei.com> Mon, 02 July 2018 02:18 UTC

Return-Path: <bill.wu@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 E697A130DF1 for <netconf@ietfa.amsl.com>; Sun, 1 Jul 2018 19:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 i8i2LLhkZKg9 for <netconf@ietfa.amsl.com>; Sun, 1 Jul 2018 19:18:31 -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 5BCE8124D68 for <netconf@ietf.org>; Sun, 1 Jul 2018 19:18:31 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 22EEAFB03FF8D for <netconf@ietf.org>; Mon, 2 Jul 2018 03:18:28 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 2 Jul 2018 03:18:29 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.193]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0382.000; Mon, 2 Jul 2018 10:18:17 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Wubo (lana)" <lana.wubo@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Review of draft-zheng-netconf-inline-action-capability-00
Thread-Index: AdQRqTdVZgjuvQxKTiOHMbgCclej/AAALLew
Date: Mon, 02 Jul 2018 02:18:17 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AEBE24F@nkgeml513-mbx.china.huawei.com>
References: <520ECC8D9CA1724BA1CE492DF898F6A33176A2@DGGEMI526-MBX.china.huawei.com>
In-Reply-To: <520ECC8D9CA1724BA1CE492DF898F6A33176A2@DGGEMI526-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.244]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9AEBE24Fnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/3p-XRThpirPG9s0m3ofcN9CKeQ8>
Subject: Re: [Netconf] Review of draft-zheng-netconf-inline-action-capability-00
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: Mon, 02 Jul 2018 02:18:33 -0000

Thanks Bo, please see reply line.
发件人: Netconf [mailto:netconf-bounces@ietf.org] 代表 Wubo (lana)
发送时间: 2018年7月2日 10:10
收件人: netconf@ietf.org
主题: [Netconf] Review of draft-zheng-netconf-inline-action-capability-00

Hi,all
I like this proposal and add missing piece in NETCONF 2.0 on how to handle action operation together with other NC operations. A few quick comments as follows:

1.How do we identify ifstatenable within <config> as action operation?
<config>
<ifstatenable xc:operation="action">
<enable>true<enable>
</ifstatenable>
</config>

[Qin]: Good catch, I think we should ifstatenable element should be include within <action>element and use action element to identify action operation data.

2.How do you prevent action operation from conflicting with other sub-operation within <edit-config> and <edit-data>?

[Qin]:Good point, we should make sure action operation and other operation to be executed together will not generate unexpected result.

3.I think inline action operation can also be applied to other NC/RC operations such as <get>,<get-config>,<get-data>?

[Qin]: Yes, that’s correct, at this stage, we like to start from <edit-config> and <edit-data> cases. We will cover other NC/RC operations in the later version after
action operation within <edit-config> and <edit-data> operation are well specified.

Best regards.

Bo