Re: [netmod] Question on draft-wu-netmod-factory-default

Qin Wu <> Tue, 26 March 2019 05:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 832D5120284 for <>; Mon, 25 Mar 2019 22:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SYkHXbFucxh2 for <>; Mon, 25 Mar 2019 22:25:59 -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 A3268120283 for <>; Mon, 25 Mar 2019 22:25:59 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id CEEC2C497191CB945077 for <>; Tue, 26 Mar 2019 05:25:57 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 26 Mar 2019 05:25:57 +0000
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Tue, 26 Mar 2019 13:25:45 +0800
From: Qin Wu <>
To: Joe Clarke <>, "" <>
Thread-Topic: [netmod] Question on draft-wu-netmod-factory-default
Thread-Index: AdTjkxFcCYeISMFOQFKN5gIZBlyFgQ==
Date: Tue, 26 Mar 2019 05:25:45 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] Question on draft-wu-netmod-factory-default
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: Tue, 26 Mar 2019 05:26:02 -0000


发件人: netmod [] 代表 Joe Clarke
发送时间: 2019年3月25日 22:14
主题: [netmod] Question on draft-wu-netmod-factory-default

I support the need for being able to reset a DS to its factory default.
However, I have a question on the current design of the model and the "factory-default" DS.

It seems to me that this is a single DS that might have been intended to reset running or startup.  However, what if I have different DSes that each have unique factory default data? 

[Qin]:We start with a simple case, you case could be addressed by invoking multiple rpc with each rpc to allow reset a set of datastores.
 If I choose to extend factory-default with a new identity of my other DS, how can I indicate that the target DS will be reset to _that_ DS?  Does that make sense?

[Qin]: In simple case, target DS will only be reset by a single factory datastore. If there is a new factory datastore could be derived from that DS, I think target DS should be changed to reset that new factory datastore.

Or if I do a <get-data> on a factory-default DS, how do I know what other DSes does this DS pertain?  Perhaps the server will use this to reset a given DS, but how would a user know that (other than perhaps naming of the factory-default DS)?

Maybe the module needs a mapping to let the client know what DS will be used to reset what other DS?
[Qin]: So your point is should we allow multiple source, multiple target in the same RPC, will think it over. Thanks.

netmod mailing list