Re: [netmod] New Version Notification for draft-wu-netmod-factory-default-01.txt

Rohit R Ranade <> Mon, 22 October 2018 05:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 759C0130DC0 for <>; Sun, 21 Oct 2018 22:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cSSJJJa8SERL for <>; Sun, 21 Oct 2018 22:00:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 90D6912F1AC for <>; Sun, 21 Oct 2018 22:00:14 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id D5FD839ADD2DE; Mon, 22 Oct 2018 05:59:59 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 22 Oct 2018 05:59:28 +0100
Received: from ([]) by ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0399.000; Mon, 22 Oct 2018 12:59:17 +0800
From: Rohit R Ranade <>
To: Balázs Lengyel <>, "" <>
Thread-Topic: New Version Notification for draft-wu-netmod-factory-default-01.txt
Thread-Index: AQHUZ6edTUJh1sqnT0SD+ZwzekOYOaUmhEAAgAQuqKA=
Date: Mon, 22 Oct 2018 04:59:17 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6BC6988Fdggeml510mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] New Version Notification for draft-wu-netmod-factory-default-01.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Oct 2018 05:00:19 -0000

Some suggestions,

1.       In YANG module, the identity has name as “factory-default”, but many places  the name "factory-default-running" is used. I suggest we used “factory-default”in all places.

2.       This YANG module is importing ietf-netconf module. I suggest that this import should be removed as this module should not have dependencies on NETCONF.

3.       The description of this YANG module, still has the reference to <copy-config>.  Whether this can be removed ?

4.       The description of the indentity “factory-default”, suggest to describe the identity rather than tell “how” it can be used.

5.       Whether we can also add the statement that if the “target-datastore”, have been locked , then the reset-datastore will fail with the <error-tag> value as “in-use” ?

6.       Since we have scenario of copy to multiple targets, whether we can add a leaf called the error-option with possible values of “stop-on-error/continue-on-error/rollback-on-error”   ?

With Regards,

Rohit R

From: netmod [] On Behalf Of Balázs Lengyel
Sent: 19 October 2018 18:17
Subject: [netmod] Fwd: New Version Notification for draft-wu-netmod-factory-default-01.txt


A new version of I-D, draft-wu-netmod-factory-default-01.txt has been uploaded. Changes include:
Removed impacts to <copy-config> as the reset-datastore  RPC can anyway do the same thing.
Explained the difference between startup and factory-default datastores
Small corrections.

regards Balazs

-------- Forwarded Message --------

New Version Notification for draft-wu-netmod-factory-default-01.txt


Fri, 19 Oct 2018 05:30:05 -0700



Ye Niu <><>, Qin Wu <><>, Balazs Lengyel <><>

A new version of I-D, draft-wu-netmod-factory-default-01.txt
has been successfully submitted by Balazs Lengyel and posted to the
IETF repository.

Name: draft-wu-netmod-factory-default
Revision: 01
Title: Factory default Setting
Document date: 2018-10-19
Group: Individual Submission
Pages: 10

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-running" read-only datastore is
defined, that contains the data that will be copied over to the
running datastore at reset.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at

The IETF Secretariat


Balazs Lengyel                       Ericsson Hungary Ltd.

Senior Specialist

Mobile: +36-70-330-7909              email:<>