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

Joe Clarke <jclarke@cisco.com> Tue, 26 March 2019 21:15 UTC

Return-Path: <jclarke@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 711C912006D for <netmod@ietfa.amsl.com>; Tue, 26 Mar 2019 14:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 ZAbEfQ7YmoXd for <netmod@ietfa.amsl.com>; Tue, 26 Mar 2019 14:15:35 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3995D120020 for <netmod@ietf.org>; Tue, 26 Mar 2019 14:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2985; q=dns/txt; s=iport; t=1553634935; x=1554844535; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=hwjgObpmo7Mc3Unbu6Ahb+XF6+rBY+hEXAfx+tVX3is=; b=d872d6pfNsD+SQyH/Gp4kO2YplEqKkML5MhOgPtsBkmkquzNs/1E5IzR 5CO32k+k0cO8w2Aovwe39xB16l3v8aJthU7H6RC9h5aTQ3HxdHYv6Dobu 2xfoe6bOkf9aEEczhSYiuNjXKP6pocSccqoJ4JUjLUcKihUwFGZst3e4e U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BgAACSlZpc/4ENJK1bCRkBAQEBAQE?= =?us-ascii?q?BAQEBAQEHAQEBAQEBgWWCEWgDTTMnhA6TQ4FgLZhPgWcPGAuEA0YChSIiOBI?= =?us-ascii?q?BAQMBAQkBAwJtHAyFSgEBAQMBAQEhSwsQCxEEAQEBAgImAgInKAgGAQwGAgE?= =?us-ascii?q?Bgx4BgW0ID6xLgS+KLAWBCySLMheBQD+BOII2NT6CYQEBgTcTAYMgglcDim2?= =?us-ascii?q?HDpMeCZM1BhmLJYhdix2TWoFkIYFWTSMVO4JsiwyFWyMDMJBCAQE?=
X-IronPort-AV: E=Sophos;i="5.60,274,1549929600"; d="scan'208";a="538029819"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Mar 2019 21:15:28 +0000
Received: from [192.168.10.113] (rtp-jclarke-nitro5.cisco.com [10.118.87.86]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTP id x2QLFRS8023188; Tue, 26 Mar 2019 21:15:28 GMT
To: Alex Campbell <Alex.Campbell@Aviatnet.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <94605356-c2a1-d00b-cffd-e7df94739a62@cisco.com> <665b7eef-54d1-6bd4-16bb-a66b820f5ebe@bogus.com> <1553634262537.25586@Aviatnet.com>
From: Joe Clarke <jclarke@cisco.com>
Openpgp: preference=signencrypt
Autocrypt: addr=jclarke@cisco.com; prefer-encrypt=mutual; keydata= mQINBFx0f7kBEACpXvK/9vZPCzcdpjMCFxTYDJSbYGPBj4jAct6j26evawhP4nQFuk8a/N0T u/l5KhN8nj0F+4wYLBBm/Vq6OYnXcuu/Qnaa5SeN6A8xp0KGFvY81x2BzPMqoM1XLnBAgcHU BlO+OikGlQSouJYagtw1qhlJpmtjwdcJ91Sun5N0SLd8iJVTU2ndCBdlj4PFuDBae9urft7D lkL3sDeAimsnPp8SJF8L2wdMWBXuht666lla+xYzwQ76+ibEmH+zr9Xy3JWySCcS75pbIikj eV/LF/YdyVPr6YGPXawO+srQGiiaqAcUY4oeWYEuFZuG0zGiCDNl106Sc4GVPOTOragqFMZv 1DoFvdaHvmBz3dbKQJ7L+W/paaBxk9F7uu73g9pPWgdio/Bh63iDlEfOm360qIQI3cbisSPF yR9RLnQTUWsy3aolG3NmxSJ+YPDwunNS9soPvPwZixbL6XUy05sUyu6d4lFKMtfo135VJ8N0 SgxNlBn/MZwFsuj66nLq015rz+bud5kz1EIK428q9+Kn4t92uq61oa/9un42qm9Xp/mm4j0J LUdNXXp987F1lZdZltcqkoYlY66OWmUr+YcVB+JAGPCA+C0T7CDjXgxkeyA3/9y7/jtVEDSx UWzCzLhzU/78QqC3NtMyUVRG7feRF0NWRzcc+d4ZEsojicmdEwARAQABtCtKb2UgQ2xhcmtl IChqY2xhcmtlKSAoKSA8amNsYXJrZUBjaXNjby5jb20+iQJOBBMBCAA4FiEE40r9XruLwkD8 nwY9s2u9ges9Y6oFAlx0f7kCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQs2u9ges9 Y6oT1Q//Vjy5ZVYA2Hy6eDz0jrmdkwQZklLU/MXvRgI8WWj6wGs2JKugdKSkkfwvDbD7Rg7b nqkMaZDcLK5eh/492CcwXwvcJKo/9bH1gUPYcDbu5INahiEagkgOS9GOjuHQs4cVr1JNiExf UZ/UcF0R+agP9jfqlJ7eiUN74w1cddZUfhfM0U0cLJ5TJtTjqnqsOCefNiWBLdSn+9RX8c6y cW77N4TVO6Vtv03SvLs5KniLmb6r7qwg6gkU2Vw6TDCk9UdJWSsKHEiOBmq1aGGmZHfBq9iZ GxwCaEqUBdN438JYN8RJMB2qv7EzTsv+KVz2E96jUBzeWdTFqu2xPikg4mwwUmJ1SAqc6AGI JZ8ICNr50xONoPpfdR+1QQzImnua8TuV28pracEDKex8r/ieDZQh8UyVM3mdGL7RSVa4/+EO iKCVmFfHLdnbuwhJLUhsHOlfeYSmRzmHUwS9K1sERMPUJCImMJUOAynQEoeTuLc6dDWq0oTP 6kJ3my7eMcg5MsFsGob8qtUDujiGof7LKZYHOqwYjCzrK4s4vwyX1Yh228sLRiEuNbCpvlD1 U/iKBv/VL5FMbI1kd0FPXvY+ygW+aobZYUOYXOvvdTeq9phCL2aHa5hHG7QNhSF6NsCuZhg6 mnOFOdAF7imXVmLa6cYEYqV17SGgceDKotNea2AxL965Ag0EXHR/uQEQAOIdXbR7GqhQdITX a+tCgi9r8p0o5e2Q2Rq22YIMR6FiyeWFTO2RQpW2NZW4yDfpGZnvBdFTWB62MWxu5Z7FwA09 ZON0l7c4IK7TFJ7Vx9azx1Ebx7r1p5hcARSmvU4CmlJZGPR0m9b+p9rPx27B5vCIWITQbWB/ PPgbksEdxXYYHCVJCWHk6LxL5iZJFVjoQGvHX/3PtzxByHtnVWQ937PZRCHaSAgERr6qVNWd XaO9ZlHm8l2yqMxKk+LUxOtj0FYY/vVdVwFFaGGkhXzhr4f6FJ7+j6Q+aOBbCvO2z/xfw/mh Tlg8W3cQYFwQcaW//FzdTprIRD8AiBRuEH5daLHZAhqj1M1srMv1SRyE7wu/e233ngUZ7UbZ J52bE2RsmA4sUVQVPB57/mn1U9xXW1pyus0n45sQi0GRsFl8fHujeQeAVPWIZl9AL8FiNlLZ +VDvMV0V24vChwRo7OVgohJNkc9NkIb7zYsv8Hqo2OinXWmQmMsluQzU9nSkGdC2eSgOPzVF fzY1KEcifF5O7A5PH2DPNsC1hPer+4vVZbMEQwW5mBIl04IvuCA3S3j+Vvfj3yyPuhf5ExjM 0YtaP5x0S4pqXVKNhzrHX/YtV13c3BP6Zx56MW2t5KnmV0MF97h2vejh/DHPSymz5blUv2Mr 0kknFYhJ+tp/rqP7B8+HABEBAAGJAjYEGAEIACAWIQTjSv1eu4vCQPyfBj2za72B6z1jqgUC XHR/uQIbDAAKCRCza72B6z1jqpFIEACKHqK4wdmimwJU+uq3HJcDBP12vnISDxkrcq19xWCv 01EWp1DR4izRLJXFIke7jlGk1GWfHKkjpUmkXOdujxYZvrVUXD9BwnNDWfDlZaPgpQNoMIlH Pcnq+MovlsuHiLnA29RRxUfRRn49fnpB4MQhB9tzsHGcghApFxB0h/CLs8ZWLTP6EDyDSNem ynEeJ8YjsbyBDqmAHs/+PS14FS7R6jHW8XNonzu5qKVvwkfA5EAI17CLJWTLkFwa3y7vOL6v x6qsoGNPvN4kolAGhz8cm2zqyZ/ts3paYnjZnBWnziYATv3hZzijcLKlLKBJaP7dUlkdNePN yzLkeN+oCVcz1DTGBhfIzlp+Dk3ySFoV2bYyEqiFmttpaDcBbPoB1LKvVZE/C1/f0Z9Tc0Fi VYQ2R60npDISUCanFF0JsN14PGoJdaV90Ouitr8GBzUJpKXFYi93L4M8gHCnSGWmjqAFGNj9 374pUwI8wbBAK5GI1hmjQZLA1UFM/SJ9J86gBzPUPNFR1xTSU+GTEufGHtcQ7wL42X+xz/lv 2pzhluScPl2WWXnwMSiE1a8AaVIhJvsrHuBxNH2l0RHuknWvJOjKtn6wdvPnEURJMH5dQ0jl QFqXPmJVYpL5AvqTYKXtS0Jy1z9oQN6ZUngZoaIYLDogKSQ9DOYd8WvdmOE24auWtA==
Organization: Cisco
Message-ID: <ff04350f-e870-7cdd-3f60-73b143e0888a@cisco.com>
Date: Tue, 26 Mar 2019 17:15:26 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <1553634262537.25586@Aviatnet.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.118.87.86, rtp-jclarke-nitro5.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/LYg8KV1nqXhqViC3nixhXbEMXks>
Subject: Re: [netmod] Question on draft-wu-netmod-factory-default
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2019 21:15:38 -0000

On 3/26/19 17:04, Alex Campbell wrote:
> As I understand it,the only purpose for the candidate and startup datastores is to indirectly set the contents of the running datastore.
> 
> Therefore it wouldn't make sense to have different factory defaults for the running, startup and candidate datastores. And those are the only writable ones.
> 
> Joe, which other datastores were you thinking of?

Again, this is likely vendor-dependent.  I was thinking of additional
system datastores that would also need to be reset to default for a full
device reset.  This is why I like the "reset-device" RPC, which would
take care of any such DS.

As a concrete example, Cisco switches have a vlan.dat file that is not
part of <running> or <startup> that would need to be reset to factory to
fully reset the device.

Joe

> 
> Alex
> 
> 
> ________________________________________
> From: netmod <netmod-bounces@ietf.org> on behalf of joel jaeggli <joelja@bogus.com>
> Sent: Tuesday, 26 March 2019 8:18 p.m.
> To: Joe Clarke; netmod@ietf.org
> Subject: Re: [netmod] Question on draft-wu-netmod-factory-default
> 
> On 3/25/19 07:14, Joe Clarke wrote:
>> 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?  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?
>>
>> 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?
> 
> the germ of the idea is sensible enough. reset a DS to it's factory state.
> 
> When it meets reality of course is that there seem to be a bunch of
> variants that seem like pretty compelling use cases.
> 
> reset the whole device being one of them.
> 
> the specification of a factory-default datastore and then
> 
>    o  startup configuration datastore
> 
>    o  candiate configuration datastore
> 
>    o  running configuration datastore
> 
> actually sound a bit implementation specific though I recognize that
> most network operating systems due tend to follow models that at least
> superficially resembled that.
> 
> I'm generally sympathetic to the application the draft proposes.
> 
>>
>> Joe
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>
> 
>