IETF Logo Mail Archive

Re: [netmod] [netconf] WG Last Call: draft-ietf-netmod-factory-default-05

"Joe Clarke (jclarke)" <jclarke@cisco.com> Mon, 18 November 2019 00:30 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 AAE8D12022E; Sun, 17 Nov 2019 16:30:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=LKaiKJV6; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=NG/JVpml
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 skUOTIQGkeZx; Sun, 17 Nov 2019 16:30:56 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6F7712020A; Sun, 17 Nov 2019 16:30:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24459; q=dns/txt; s=iport; t=1574037055; x=1575246655; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3fpjI3C74hzTTHQ1yDAkBwHIKm5usf+Xh4SbEAmrNco=; b=LKaiKJV6yHM4r/KXmf4vlxqyoR9sdqWorV0FCxJEguwJQsoosKlsWYXl q/N/oV7LfU0S5KFdov+uspWuRTq5rGnnnsv0AdM4D9BUW1J6o2yzZGbGF S8wfqel+G2QuuN8jfXFnQ/kQihGRbQgB12IwitiIjT+ncDSeUwpkNjrkz U=;
IronPort-PHdr: 9a23:ZQ9h8x9xw1kbV/9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVcyODUThL/PCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BMAADk5dFd/51dJa1lHAEBAQEBBwEBEQEEBAEBgWoHAQELAYEbL1AFbFggBAsqhCmDRgOEWoYVgjmYJYEuFIEQA1QJAQEBDAEBGAEMCAIBAYN7RQIXggwkNAkOAgMLAQEEAQEBAgEFBG2FNwyFUgIBAwEBEBEdAQEsCwEPAgEGAg4xAwICAiULFBEBAQQOBSKDAAGBeU0DLgEOkTGQZAKBOIhgdYEygn4BAQWBSEGCdBiCFwMGgTYBjBQYgUA/gREnDBOBTn4+gmIBAQIBARaBLwFECYJaMoIsjVcDX4FahUeJRo8NCoIqhxqONRQHgj6HaI9rlwCRUAIEAgQFAg4BAQWBUjmBWHAVOyoBgkEJRxEUkRoMF4NQhRSFP3SBKI1KAQE
X-IronPort-AV: E=Sophos;i="5.68,318,1569283200"; d="scan'208,217";a="382396349"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 18 Nov 2019 00:30:40 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id xAI0Ue2K032108 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 18 Nov 2019 00:30:40 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 17 Nov 2019 18:30:39 -0600
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 17 Nov 2019 18:30:39 -0600
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sun, 17 Nov 2019 18:30:39 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dt3YAErnabVdrr7gtboMc7W5laDx7cQSHQ7l8FfOaxUhocmy5yr9vahwEFItVcpWQ+9c4z248I97D1qSb/0lrG8tJr5TJ2Xxyg1s5z9/4AbuPbU/UgHsiQ8uF5MTAW3Yoa3IoDEvEzN56Wv9sn/B2XnyBads8HO8VXQpoOKfAb5IEr5ogQoCbmPFsZVWe0cdOzXvnQFbilA6TsGxFkC5C0jK5QE5C9MbD28qPuwCR9MzJ4ED7w01+fX2R/OXjgETDVLKvmXy4t/kwh4BCpQ/AJapYyxKvVt9aBIkyBxgyTFKXQFQJwBYJjsO/adB4b/C9T9AGqQEUZF5zbv7JRkQLg==
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=3fpjI3C74hzTTHQ1yDAkBwHIKm5usf+Xh4SbEAmrNco=; b=cMDEoW6hp8t7GQ14DvuF7czOvMIG6c8bIZHi4OfVYY4A3goOj/Gxf3N4t6ZspKUtcCNSkiIF6TqBl9t0M5hVGvYySqmkZV4D8CX+IUzhASOJg3PA+4hJXkzm+a3mwt1H5DfZCm1tSw2c5AP+A1zQdAvUA/aWlEi8sf2SBr78oAWniSP1DTH5Z8hrCAPTKLkq6RJ7LF4IhHLCIcQ787HXlhKTgW+DbFrEbW32hbxONK1oU8GLuYxTIl5ieHfKhbHxTCDl0PJQ5ql4sxNm+qzEAzRKK+jK6yaaKYP8BFb3aH0Ebz1ostFL+qi8PO2619NCXZQrLcVmhuCKyTfwg1g+yA==
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=3fpjI3C74hzTTHQ1yDAkBwHIKm5usf+Xh4SbEAmrNco=; b=NG/JVpmltmnX2+pbN30MKR4kjW0Qc04iZqf+4YKT746weKH6zLG0fAOFoDPRrhwYYQfT0Tl+Zu1nS1+jo1iIPwlWbSkZotLAumZG0cprKt52eQcLmev1FwnWYE5izdx5eWVpfsZA38+FEDIEAVhUamd6582MYArZx22NK7RyIgg=
Received: from BN6PR11MB1667.namprd11.prod.outlook.com (10.172.23.12) by BN6PR11MB1554.namprd11.prod.outlook.com (10.172.21.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.23; Mon, 18 Nov 2019 00:30:38 +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.2451.029; Mon, 18 Nov 2019 00:30:37 +0000
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: Qin Wu <bill.wu@huawei.com>
CC: Kent Watsen <kent+ietf@watsen.net>, "netmod@ietf.org" <netmod@ietf.org>, "draft-ietf-netmod-factory-default@ietf.org" <draft-ietf-netmod-factory-default@ietf.org>
Thread-Topic: [netmod] [netconf] WG Last Call: draft-ietf-netmod-factory-default-05
Thread-Index: AdWdXAZeEZ6yjaMrTg6/yjYL+u4nFgAS2AAA
Date: Mon, 18 Nov 2019 00:30:37 +0000
Message-ID: <E5391EA3-FDA4-4D15-9699-D298B507F797@cisco.com>
References: <B8F9A780D330094D99AF023C5877DABAA9451CD7@dggeml511-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA9451CD7@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: [2001:67c:370:0:2902:154c:c647:6f22]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 355dc0c6-170f-476b-5fa0-08d76bbe88d3
x-ms-traffictypediagnostic: BN6PR11MB1554:
x-microsoft-antispam-prvs: <BN6PR11MB1554DB29042E8FD5B45FC0DFB84D0@BN6PR11MB1554.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0225B0D5BC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(396003)(366004)(346002)(136003)(39860400002)(189003)(199004)(54094003)(186003)(236005)(99286004)(36756003)(6916009)(7736002)(76116006)(91956017)(71200400001)(6116002)(316002)(54906003)(86362001)(14454004)(46003)(25786009)(6246003)(478600001)(14444005)(966005)(256004)(229853002)(4326008)(33656002)(6486002)(486006)(8936002)(81166006)(8676002)(76176011)(66946007)(66446008)(66556008)(64756008)(71190400001)(81156014)(606006)(6436002)(476003)(5660300002)(6306002)(2616005)(11346002)(446003)(6506007)(53546011)(2906002)(66476007)(54896002)(6512007)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR11MB1554; H:BN6PR11MB1667.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: cIppGOrDpwciWXxOml/1pkrdxLT81erlwN87T2bpokEFPhjrHOeADeOzUdRPc971BQxb5bQiCa2oDihHKJsjM700yEhHW7OJQ1VlqnhpykXfDyIOZ+9i9TB7MYSeOpN6MRM+0rsJqRrbkdXtCwyyFF1/3I8NyHW+/P9q4HHHbqHyYsiq80cnevceAKDe2l24y8s7jtCukaF46E9ziLFO6GzBEqwQ5R+JQb9CNTa3p2W9PPUVHLmF/GGJKo2Fs7HsC4zC0Ufr5z+Jh2aa/U+EdfrV9zGdbWJIsOH7oAgOfpXiCaDGKrECxRwdSzDtnf5s2cMeiJgbJt/D+pd/vHateaHr4RtlxKlC9q4Fg8VGUkN1XYndmijY/KgLYJDwSxFcsZOAH68SxjFNF/SY86tK5d2pktyRqN3w/H/lbUuvp6XTS2R/12kfwyUJ97kGay27
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_E5391EA3FDA44D159699D298B507F797ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 355dc0c6-170f-476b-5fa0-08d76bbe88d3
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2019 00:30:37.7627 (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: mQAiRMFq7mEqD+dxgcOVe7SLmEoJPx4NKn7RzlLsgaleHo1al79fQiQij1xOG0R23RbpDgY0yqfyNWKUwEEUEQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1554
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/QTqcQco6w254g0s8Fc4nceSexjU>
Subject: Re: [netmod] [netconf] WG Last Call: draft-ietf-netmod-factory-default-05
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, 18 Nov 2019 00:30:58 -0000


On Nov 17, 2019, at 10:29, Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>> wrote:

Done, Kent.
https://datatracker.ietf.org/doc/draft-ietf-netmod-factory-default/?include_text=1
Thanks for follow up.

Hey, Qin.  I see you removed the ZTP reference.  I saw the conversation, and you still have the text about resetting other processes.  That said, you still have an informative reference to RFC8572.

More importantly, though, how do you see this practically being implemented?  With an ops dir hat, I’m walking through Section 2, and sending a factory-reset RPC to a device.  The device immediately resets <running> to default and <operational> to some similar default state.  The device has become unreachable within the network.  A reboot or other reset is optional to implement, so as an operator I’m not really sure what to expect at this point.

Typically (well, at least for me), I’m either going to do a factory reset today through the console (if I’m going to RMA or otherwise decommission the device) in which case I don’t care if it’s reachable on the network; or I use a remote “write erase” then reload to prepare the device for a re-bootstrap.  For this latter use case I see the RPC being valuable, but I’d need to know that the device will reload or otherwise re-prepare itself for bootstrapping.  In a multi-vendor environment some consistency there would be useful.

I would think that practically an implementor would reboot the device after receiving and executing this RPC?  I admit that perhaps in virtual cases, a reload may not be required, but I wonder if some operational considerations are needed to let vendors know how best to go about implementing this for best results.

Joe



-Qin
发件人: Kent Watsen [mailto:kent+ietf@watsen.net]
发送时间: 2019年11月16日 5:16
收件人: netmod@ietf.org<mailto:netmod@ietf.org>
抄送: draft-ietf-netmod-factory-default@ietf.org<mailto:draft-ietf-netmod-factory-default@ietf.org>
主题: Re: [netconf] WG Last Call: draft-ietf-netmod-factory-default-05


Today ends the two-week Last Call, which passed.  Thank you everyone who participated.

Qin, I'll start the shepherd writeup after -07 has been posted addressing the Last Call comments.

Kent // shepherd




On Nov 1, 2019, at 10:57 AM, Kent Watsen <kent+ietf@watsen.net<mailto:kent+ietf@watsen.net>> wrote:

This begins a two-week Working Group Last Call (WGLC) on draft-ietf-netmod-factory-default-05.  The WGLC ends on Nov 15 (two days before the NETMOD 106 session).  Please send your comments to the working group mailing list.

Positive comments, e.g., "I've reviewed this document and believe it is ready for publication", are welcome!  This is useful and important, even from authors.  Objections, concerns, and suggestions are also welcomed at this time.

Thank you,
NETMOD Chairs

_______________________________________________
netmod mailing list
netmod@ietf.org<mailto:netmod@ietf.org>
https://www.ietf.org/mailman/listinfo/netmod

v2.23.0 | Report a Bug | By Email