Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt

Qin Wu <bill.wu@huawei.com> Sun, 15 July 2018 20:12 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 42BE7130E6A for <netconf@ietfa.amsl.com>; Sun, 15 Jul 2018 13:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 AcxJffx5XIgf for <netconf@ietfa.amsl.com>; Sun, 15 Jul 2018 13:12:06 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 B0871130E48 for <netconf@ietf.org>; Sun, 15 Jul 2018 13:12:05 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id D375E4595A432 for <netconf@ietf.org>; Sun, 15 Jul 2018 21:11:38 +0100 (IST)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.399.0; Sun, 15 Jul 2018 21:11:39 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.110]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0382.000; Mon, 16 Jul 2018 04:11:28 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, Rohit R Ranade <rohitrranade@huawei.com>
CC: netconf <netconf@ietf.org>
Thread-Topic: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt
Thread-Index: AdQcd1AZfDh7f6HNQBSYWXXLxqIR1g==
Date: Sun, 15 Jul 2018 20:11:28 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AF3F925@nkgeml513-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.124.182.198]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9AF3F925nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ePnwvcNhqveY49qbHy1_M_m8pZI>
Subject: Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 15 Jul 2018 20:12:08 -0000

Yes, the new factory is also applicable to NETCONF and other YANG based protocol.
Good catch for security section, will fix that in the next version.

-Qin
发件人: Reshad Rahman (rrahman) [mailto:rrahman@cisco.com]
发送时间: 2018年7月15日 21:59
收件人: Rohit R Ranade <rohitrranade@huawei.com>; Qin Wu <bill.wu@huawei.com>
抄送: netconf <netconf@ietf.org>
主题: Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt

Hi,

The new “factory” datastore can be used for NETCONF also so a corresponding NETCONF draft should be updated to support this functionality?

BTW the security considerations section refers to NETCONF instead of RESTCONF.

Regards,
Reshad.

From: Netconf <netconf-bounces@ietf.org<mailto:netconf-bounces@ietf.org>> on behalf of Rohit R Ranade <rohitrranade@huawei.com<mailto:rohitrranade@huawei.com>>
Date: Monday, July 2, 2018 at 11:23 PM
To: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>
Cc: netconf <netconf@ietf.org<mailto:netconf@ietf.org>>
Subject: Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt


In addition, when a device boots then <startup> is initialized to <factory> if it doesn't exist.  Or alternatively, <running> is initialized to <factory> if <startup> doesn't exist.
A client can use an RPC to copy <factory> to <startup> or to <running> if they want, but then can never write to <factory> (although factory could change via a software update).

[Qin]: Good summary, this is exactly what we like to propose.
[Rohit R Ranade] +1

Existing protocol operations can be used (e.g, copy-config from factory to running).
Now RESTCONF is datastore aware, it looks like we need to add a "copy-config" RPC (or should it just be "copy"?) to RESTCONF to allow the contents of one datastore to be copied to another datastore.  Such an RPC should be entirely generic and not tied to the factory datastore in anyway.

[Qin]: Yes, one of our thoughts is to define a generic operation, e.g., copy-datastore, delete-datastore, maybe compare-datastore, all these operations are datastore level instead of data node level.
[Rohit R Ranade] +1 .

Possibly, related to this, it might be worth considering if there are any other operations in NETCONF that should be supported in RESTCONF and to do that as a single update to the protocol rather than lots of piecemeal extensions.