Re: [netmod] New Version Notification for draft-ietf-netmod-factory-default-04.txt

Qin Wu <> Tue, 29 October 2019 02:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 41751120047 for <>; Mon, 28 Oct 2019 19:56:32 -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 EKr2nFOSv96H for <>; Mon, 28 Oct 2019 19:56:30 -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 EB420120046 for <>; Mon, 28 Oct 2019 19:56:29 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id B64A480239FB9F5011A4 for <>; Tue, 29 Oct 2019 02:56:27 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 29 Oct 2019 02:56:27 +0000
Received: from ([]) by ([]) with mapi id 14.03.0439.000; Tue, 29 Oct 2019 10:56:23 +0800
From: Qin Wu <>
To: "Joe Clarke (jclarke)" <>
CC: "" <>
Thread-Topic: [netmod] New Version Notification for draft-ietf-netmod-factory-default-04.txt
Thread-Index: AdWOAz5S0PTnUSaLTlWNb0HPnt4vDA==
Date: Tue, 29 Oct 2019 02:56:23 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] New Version Notification for draft-ietf-netmod-factory-default-04.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: Tue, 29 Oct 2019 02:56:32 -0000

Hi, Joe:
Thanks for your valuable comments, see reply inline below.
发件人: Joe Clarke (jclarke) [] 
发送时间: 2019年10月28日 22:13
收件人: Qin Wu <>
主题: Re: [netmod] New Version Notification for draft-ietf-netmod-factory-default-04.txt

> On Oct 27, 2019, at 23:37, Qin Wu <> wrote:
> v-04 is posted
> additional text to clarify rpc usage.

Thanks, Qin.  I re-read this latest draft, and albeit there were only a few changes, I have some broader comments.

First, I remember we talked about a reboot operation I think at the last IETF(?).  It was said that perhaps a reboot would happen as part of this RPC because once the <running> datastore is reset to factory-default, the device would not be reachable.  I don’t know where we landed on that.  However, I think some attention should be paid to things like zero-touch provisioning.  If I reset to factory-default, I would expect the device to undergo any out-of-the-box bootstrapping.  Perhaps adding some text that after the RPC is executed, the device SHOULD perform any initial bootstrapping processes?

[Qin]:Yes, initial bootstrapping processes should be covered, I will propose text in the separate email for this.


In Section 2, perhaps for clarity say that, “Factory-default content SHALL be specified by one of the following means in descending order of precedence”?  I’m nit-picking on this one, though.

[Qin]: okay, fixed.

In Section 2, you mention Instance Data is second in the list.  What is really meant by this?  Does that mean the factory-default config is defined by an instance data file specified by the vendor in some offline location?  If so, perhaps it’s worth clarifying that.
[Qin]: How about the following proposed changes:
YANG Instance Data [I-D.ietf-netmod-yang-instance-file-format]
  by vendors using YANG Instance Data [I-D.ietf-netmod-yang-instance-file-format] file format in
  vendor's website or other places where off-line document is kept;


In Section 2 and in the YANG module description for the RPC your tenses don’t match.  You should say:

Upon receiving the RPC the server resets the contents of all read-write configuration datastore (e.g., <running> and <startup>) to their factory-default contents.

[Qin]:Good catch, fixed.

In Section 2, you say, “some of the SW processes”.  I think you mean software.  You should expand SW.


> -Qin
> -----邮件原件-----
> 发件人: [] 
> 发送时间: 2019年10月28日 11:36
> 收件人: Niuye <>; Qin Wu <>; Qin Wu <>; Balazs Lengyel <>
> 主题: New Version Notification for draft-ietf-netmod-factory-default-04.txt
> A new version of I-D, draft-ietf-netmod-factory-default-04.txt
> has been successfully submitted by Qin Wu and posted to the IETF repository.
> Name:		draft-ietf-netmod-factory-default
> Revision:	04
> Title:		Factory Default Setting
> Document date:	2019-10-26
> Group:		netmod
> Pages:		11
> URL:  
> Status:
> Htmlized:
> Htmlized:
> Diff: 
> Abstract:
>   This document defines a method to reset a server 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 factory-reset 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.
> 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
> _______________________________________________
> netmod mailing list