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

"Joe Clarke (jclarke)" <jclarke@cisco.com> Mon, 28 October 2019 14:13 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 90CE8120834 for <netmod@ietfa.amsl.com>; Mon, 28 Oct 2019 07:13:24 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 header.b=LfsdYT8r; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=atdYxWG8
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 4gS-Fh_wJFfA for <netmod@ietfa.amsl.com>; Mon, 28 Oct 2019 07:13:22 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C752312081B for <netmod@ietf.org>; Mon, 28 Oct 2019 07:13:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5366; q=dns/txt; s=iport; t=1572272002; x=1573481602; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Lk0JUyNlx99Wp4IcKr+0efCCniGnIV+ugqp9DK2uqHM=; b=LfsdYT8rpWrT9/CmeTpgrTSeESnmwtN+SIeD+Qd0jeCs/egTAYDTSYek +ETS6d0E/Yx/zjwerpfczG59VVaOsn0kMkmu8kmTu7+JmQmvk+H7H0InE nmYQ/jK9LxEx99X7UP6xdPN3ab+hMTVr5ekyuXgcTCBj6X41ypobhzz7s U=;
IronPort-PHdr: =?us-ascii?q?9a23=3AJctLWhz8/PSOKGnXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YhSN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuHAknyNv3nRyc7B89FElRi+iLzPA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AeAAAD97Zd/4ENJK1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBEQEBAQEBAQEBAQEBgWoBAQEBAQELAYFKUAVsWCAECyoKhB6?= =?us-ascii?q?DRgOKboI5JZdrgUKBEANUCQEBAQwBARgNCAIBAYFMgi9FAheDMiQ3Bg4CAwk?= =?us-ascii?q?BAQQBAQECAQUEbYU3DIVRAQEBAQIBAQEQEREMAQEsCQIBBAsCAQYCDgoCAiM?= =?us-ascii?q?DAgICJQsUARABAQQOBSKDAAGCRgMOIAEOlC6QYgKBOIhgdYEygn4BAQWBOAI?= =?us-ascii?q?OQUCCRhiCFwmBDigBjA4YgUA/gTgME4JMPoJiAQECAQEWgTABFoMQMoIsiUq?= =?us-ascii?q?De4I0hWCYEwqCJIcQhRuEIYRiG4I8coZlhDCLF5ZpkR4CBAIEBQIOAQEFgWg?= =?us-ascii?q?jgVhwFRohKgGCQQlHEBSDBgwXFYM7hRSFP3QBgSeOHgEuXwEB?=
X-IronPort-AV: E=Sophos;i="5.68,240,1569283200"; d="scan'208";a="360061934"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Oct 2019 14:13:21 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x9SEDLpV012475 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 28 Oct 2019 14:13:21 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 28 Oct 2019 09:13:21 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 28 Oct 2019 09:13:20 -0500
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 28 Oct 2019 10:13:20 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kfrhgJpYqIvk7fbHYilQJg3hlVE+UanUgXmPS3y3mYLWRye+DrM784hjua1syFxBkfBeDCJF+TjWPCx5rP1jO01tN/ABomcqmWP5R1ByKvfBswoxWbT55D/7vJotGIrdbUm9Nsypqh5u4MGE92Tf6kSrYYR6/4g6W63ypa2GyF8FygwRXfsWfh5mub45C9LC4Bmv7xpKV6hdFXJgdOoOgLqmZd8nMKS7QAwSxv+XQsKbpZ3ddAJYORw+1X3YCHBvUOiTsua/Dkd5+9WoMxY2BXDE6fJyJDbkQ0AdTLAWPfuO/InNbkLB72r+DozT8MCFNeo7IdweYoem68RqHz18Ig==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Lk0JUyNlx99Wp4IcKr+0efCCniGnIV+ugqp9DK2uqHM=; b=WlMlpvt9w9GWOGNM74M1afAPIirOaSzQaT1blL+S5Q8R/1G7m8rIbJNghiZlZdNHsuIEgS/D9gP2rxhf3CutW6uNPZFbHcMyOIPR/buB9cI2Y33j73yXge7vzQLtCGsHcpj8bt9MmdzPoXCayx5A8APf/8aL/BE3p/vgIwjKbgRtijuH1J9ZKzxqjEMun2O2M4RyCd4lm1AAXt50JSf34Obo90vVLLZdmus01utypiZu6gVa0T8WTwrHQYY82Ws2Mh040elalvEIrgeXzi/jyt+/DxW2cifczi2rgVQ5dW8I9G/cuFLPaHRDqz+0yCo54kIT+nlfXw08dl2FYG2+fA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Lk0JUyNlx99Wp4IcKr+0efCCniGnIV+ugqp9DK2uqHM=; b=atdYxWG8jC9bDrkkq8qrvDuTyLoYYT5wSWxKxV3RDuZ7fhVzwI6bfbt/JgzP0LiBuTeN+H0aW34K6NQc+EakyLhZgNuhVpYFCSbp0zYQ5CsYtp7fE4f2+dmUg4MMX/b1BsMbv2uMFHGWO2NownbxZW7xnkUMOnTdM13BbnH5Ndw=
Received: from BN6PR11MB1667.namprd11.prod.outlook.com (10.172.23.12) by BN6PR11MB0067.namprd11.prod.outlook.com (10.161.152.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.24; Mon, 28 Oct 2019 14:13:19 +0000
Received: from BN6PR11MB1667.namprd11.prod.outlook.com ([fe80::499:8548:e967:458e]) by BN6PR11MB1667.namprd11.prod.outlook.com ([fe80::499:8548:e967:458e%12]) with mapi id 15.20.2387.025; Mon, 28 Oct 2019 14:13:19 +0000
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: Qin Wu <bill.wu@huawei.com>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] New Version Notification for draft-ietf-netmod-factory-default-04.txt
Thread-Index: AdWNQOVQabaxliJZSKidndMJAls3pQAWPM8A
Date: Mon, 28 Oct 2019 14:13:18 +0000
Message-ID: <B98EA06F-CC07-42B3-9030-7027F732583E@cisco.com>
References: <B8F9A780D330094D99AF023C5877DABAA93AD5B0@dggeml511-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA93AD5B0@dggeml511-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jclarke@cisco.com;
x-originating-ip: [173.38.117.74]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 42ded8cf-5ed1-40fc-a402-08d75bb0fbb0
x-ms-traffictypediagnostic: BN6PR11MB0067:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <BN6PR11MB0067A883D24EB769401C4A16B8660@BN6PR11MB0067.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0204F0BDE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(136003)(396003)(39860400002)(346002)(376002)(199004)(189003)(14444005)(4001150100001)(14454004)(6916009)(53546011)(316002)(99286004)(256004)(66946007)(15650500001)(76116006)(91956017)(86362001)(966005)(66476007)(66556008)(66574012)(64756008)(5660300002)(66446008)(478600001)(11346002)(81166006)(81156014)(4326008)(8936002)(66066001)(486006)(25786009)(33656002)(6486002)(229853002)(8676002)(186003)(446003)(36756003)(102836004)(26005)(3846002)(76176011)(2906002)(7736002)(6116002)(305945005)(6506007)(476003)(2616005)(6246003)(6306002)(71200400001)(71190400001)(6512007)(6436002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR11MB0067; H:BN6PR11MB1667.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: fIRgy1RhgWd2HCCJeMLSOiZNZYf3W+j1oF3gxX/5b0LcGTF4/x9gSG4lUbCoSvxVdHO+YS+Zr224//ljqDRnpslDbvCGnGNFPJcpP8D2lnx67CvL9UYWbgLYyK24rYUeA/OAdegGAJ0r8KeQL64aVFwMPGc6kqrZ7wWpd6JmARmwcUzkVtVJ1eSmRoEjTwFJue97gvTFlY2tdvcOdCy6oDtUL5kedJ04Zpw7KAwtsytwvSjl3m6uwv6f3EPtrC2/taFc/5ITpHJX2fFLvPAfESxIMB4vOGDvsVR7JiVUeeDuKmbx/T18IlXD9ej6600GlG7Ih9q6qXoRMBk9qlrPxV9/eM9j5IgWdMCgzSAMG+i6xJ+wEfqW4VizjIXXmbPU7eVeAhLwYsn49EojNbeEp2kE1Gv0vbp1CyqVI8REYAF0+bv/9d5S8gc4dPNl1VE/S8grKWigl33tSCYbV6o6vLLRSwVuy7zJAF+VLbYK0gM=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <63BE8E34325CBA4C9F1627F24D3451A3@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 42ded8cf-5ed1-40fc-a402-08d75bb0fbb0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2019 14:13:19.0179 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Ec7LAc44nZkofDJCLTrUj6iJH0LU3yUlXkhp+hgHZk9RwW9dLaMXE7R1EIIAp7Rz0L6is4Zw4PQabyVGAo770w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB0067
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.19, xch-rcd-009.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/sUAfSjtrTSBzqaMXrHhzCrGEvrk>
Subject: Re: [netmod] New Version Notification for draft-ietf-netmod-factory-default-04.txt
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: Mon, 28 Oct 2019 14:13:24 -0000


> On Oct 27, 2019, at 23:37, Qin Wu <bill.wu@huawei.com>; wrote:
> 
> v-04 is posted
> https://tools.ietf.org/html/draft-ietf-netmod-factory-default-04
> 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?

===

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.

===

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.

===

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.

===

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

Joe

> 
> -Qin
> -----邮件原件-----
> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> 发送时间: 2019年10月28日 11:36
> 收件人: Niuye <niuye@huawei.com>;; Qin Wu <bill.wu@huawei.com>;; Qin Wu <bill.wu@huawei.com>;; Balazs Lengyel <balazs.lengyel@ericsson.com>;
> 主题: 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:            https://www.ietf.org/internet-drafts/draft-ietf-netmod-factory-default-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-netmod-factory-default/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-netmod-factory-default-04
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-netmod-factory-default
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-factory-default-04
> 
> 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 tools.ietf.org.
> 
> The IETF Secretariat
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod