Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-03.txt
Qin Wu <bill.wu@huawei.com> Wed, 17 October 2018 07:57 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 834D112D4E9 for <netconf@ietfa.amsl.com>; Wed, 17 Oct 2018 00:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 ata92mRlKvev for <netconf@ietfa.amsl.com>; Wed, 17 Oct 2018 00:57:33 -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 48D52129AB8 for <netconf@ietf.org>; Wed, 17 Oct 2018 00:57:33 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 43242F1D81866 for <netconf@ietf.org>; Wed, 17 Oct 2018 08:57:28 +0100 (IST)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 17 Oct 2018 08:57:29 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.10]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0399.000; Wed, 17 Oct 2018 15:57:20 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Rohit R Ranade <rohitrranade@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: I-D Action: draft-wu-netconf-restconf-factory-restore-03.txt
Thread-Index: AQHUYcTrwS5U3NpM1km8WDNXxV24cqUbKuewgAAFhTCAB+axQA==
Date: Wed, 17 Oct 2018 07:57:20 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9B0AC341@nkgeml513-mbx.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA9B067713@nkgeml513-mbx.china.huawei.com> <991B70D8B4112A4699D5C00DDBBF878A6BC57104@dggeml510-mbx.china.huawei.com>
In-Reply-To: <991B70D8B4112A4699D5C00DDBBF878A6BC57104@dggeml510-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: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/m0UUhz6SCxEhYBxgV9lQMjbqt-E>
Subject: Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-03.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Oct 2018 07:57:35 -0000
Thanks Rohi. -----邮件原件----- 发件人: Rohit R Ranade 发送时间: 2018年10月12日 15:13 收件人: Qin Wu; netconf@ietf.org 主题: RE: I-D Action: draft-wu-netconf-restconf-factory-restore-03.txt Some suggestions. 1. I feel "ietf-factory" is a better module name when compared to "ietf-factory-reset" as the latter is more restrictive. [Qin]: Understand, currently we only define one new rpc that is factory-reset, I think we need a more generic name if there is some other RPCs that need to be defined. 2. I feel that we need to add a section which shows difference between <startup> and <factory-default>. Maybe we can add below section for it. "3.1 Difference between <startup> datastore and <factory-default> datastore When the device first boots up, the content of the <startup> and <factory-default> will be identical. The content of <startup> can be subsequently changed by using <startup> as a target in a <copy-config> operation. The <factory-default> is a read-only datastore and it is usually static as described in earlier sections. " [Qin]: I agree with the difference between these two datastores, will see how to incorporate them in. 3. Whether "factory-reset-config" / "factory-restore-config" is a better RPC name ? As it will be similar to "copy-config", only that now the source is <factory-default> datastore. [Qin]: I think this is datastore level operation, it will be more accurate to call it datastore-reset as we proposed. Regarding reset and restore, I think they are equivalent. 4. The datastore name as <factory> is sufficient I feel, as the only factory datastore coming will be this one. [Qin]: Point taken, will see how to tweak it. With Regards, Rohit -----Original Message----- From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Qin Wu Sent: 12 October 2018 12:18 To: netconf@ietf.org Subject: Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-03.txt A new version factory restore draft has been posted https://tools.ietf.org/html/draft-wu-netconf-restconf-factory-restore-03 The main changes include: o Restructured o Made new datastore optional o Removed Netconf capability o Listed Open issues -Qin -----邮件原件----- 发件人: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] 代表 internet-drafts@ietf.org 发送时间: 2018年10月12日 8:45 收件人: i-d-announce@ietf.org 主题: I-D Action: draft-wu-netconf-restconf-factory-restore-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Factory default Setting Authors : Qin Wu Balazs Lengyel Ye Niu Filename : draft-wu-netconf-restconf-factory-restore-03.txt Pages : 10 Date : 2018-10-11 Abstract: This document defines a method to reset a YANG datastore to its factory-default content. The reset operation may be used e.g. during initial zero-touch configuration or when the existing configuration has major errors, so re-starting the configuration process from scratch is the best option. A new reset-datastore RPC is defined. Several methods of documenting the factory-default content are specified. Optionally a new "factory-default" read-only datastore is defined, that contains the data that will be copied over to the running datastore at reset. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-wu-netconf-restconf-factory-restore/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-wu-netconf-restconf-factory-restore-03 https://datatracker.ietf.org/doc/html/draft-wu-netconf-restconf-factory-restore-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-wu-netconf-restconf-factory-restore-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt _______________________________________________ Netconf mailing list Netconf@ietf.org https://www.ietf.org/mailman/listinfo/netconf