Re: [Netconf] Comments on draft-wu-netconf-restconf-factory-restore-01

Qin Wu <bill.wu@huawei.com> Tue, 17 July 2018 03:24 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 975E3130E76 for <netconf@ietfa.amsl.com>; Mon, 16 Jul 2018 20:24:18 -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 dtKPEwic2Zm5 for <netconf@ietfa.amsl.com>; Mon, 16 Jul 2018 20:24:16 -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 8F420130E40 for <netconf@ietf.org>; Mon, 16 Jul 2018 20:24:15 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id DE25A913968; Tue, 17 Jul 2018 04:24:12 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 17 Jul 2018 04:24:13 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.110]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0382.000; Tue, 17 Jul 2018 11:24:06 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Balazs Lengyel <balazs.lengyel@ericsson.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] Comments on draft-wu-netconf-restconf-factory-restore-01
Thread-Index: AdQdcQJ6YAv/CNcZQFOK/EKsmnd7sg==
Date: Tue, 17 Jul 2018 03:24:06 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AF4FF3D@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.216]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9AF4FF3Dnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ob06urGuNUGnTJKrudd1U71hpnY>
Subject: Re: [Netconf] Comments on draft-wu-netconf-restconf-factory-restore-01
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: Tue, 17 Jul 2018 03:24:19 -0000

Hi, Balazs:
发件人: Netconf [mailto:netconf-bounces@ietf.org] 代表 Balazs Lengyel
发送时间: 2018年7月17日 4:36
收件人: netconf@ietf.org
主题: [Netconf] Comments on draft-wu-netconf-restconf-factory-restore-01


Hello Qin,
   Factory default Setting Capability for RESTCONF
   https://tools.ietf.org/html/draft-wu-netconf-restconf-factory-restore-00

From the ietf-system YANG module:
"system-restart : Request that the entire system be restarted immediately. "  So we already have a restart command,

and I still not understand the difference between your definition of reboot and restart.
[Qin]:system-restart means the entire system (not just NETCONF server, but also include DNS server,etc.) needs to be restarted while reboot means the NETCONF/RESTCONF server needs to be restarted. I see this slight difference.
From section 3.6 of RFC7317:
"The 'system-restart' operation can be used to restart the
   entire system (not just the NETCONF server). "

If we implement this we need it both for netconf and restconf. Can't we do it as a YANG model defining an rpc instead of a protocol operation?
Why not make this one more rpc in ietf-system. We already have there the system-restart.
[Qin]: Yes, that is the option. The problem is reboot is not system level rpc, when we talk about reboot, I believe it means device reboot or restart NETCONF/RESTCONF server rather than restart the whole system.
In addition, do you think we should define transport independent operations to support factory default setting. Such as copy-datastore?
There are network devices that you can reset to factory default, but where you can not read the factory-default configuration.
[Qin]: That’s why we introduce <factory> datastore.
If this is implemented such devices must also be supported.  Actually this i also how Netconf works. You can not read what will be the result of a delete-config beforehand.
[Qin]: Exactly.

regards Balazs

--

Balazs Lengyel                       Ericsson Hungary Ltd.

Senior Specialist

Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com<mailto:Balazs.Lengyel@ericsson.com>