IETF Logo Mail Archive

Re: [Netconf] issues with processing onboarding information (zerotouch)

Kent Watsen <kwatsen@juniper.net> Mon, 13 August 2018 15:15 UTC

Return-Path: <kwatsen@juniper.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA4E9130F3E for <netconf@ietfa.amsl.com>; Mon, 13 Aug 2018 08:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 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_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 bL4zII7sQu5r for <netconf@ietfa.amsl.com>; Mon, 13 Aug 2018 08:15:45 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08D9A130E43 for <netconf@ietf.org>; Mon, 13 Aug 2018 08:15:44 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w7DFEUXZ009008; Mon, 13 Aug 2018 08:15:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=SGEt56tt9+3TWYApWaZaRkJ7Fu+BN7VAKamKOdFFldY=; b=cE6RKanDVXV0BoOMo0QO9zPBu1Az60f1QFaLQ6qgAUOZxuv00+Yp8riBR7z/Z+l8pkiC v4WaSgpYMWl3VrxsacWa9NYsDMPXTDqbeiUYrR0BKwcqZBOCwQxjiOClwePWcmgnEayq wVxl+zDdXiSdJ1Gsv3neW0IishMQFFNyYVErW+S429vRpSKfm40mccIpj/x7GrLR3oHT 3C3/KLYFu68J/0GG+AFTQccdzbfremYeyEiO6LIoBL+pdEizp44uzU1yeDXn/VWy3/dW JQW0Tu+tC1RdYaD1JVDsE9nWcRiq6A8Ehivdb0d6cz8ub6FVseldrcwszaZ6QnANznj5 Cg==
Received: from nam05-co1-obe.outbound.protection.outlook.com (mail-co1nam05lp0087.outbound.protection.outlook.com [216.32.181.87]) by mx0b-00273201.pphosted.com with ESMTP id 2ku6gg8kyn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 13 Aug 2018 08:15:44 -0700
Received: from DM6PR05MB4665.namprd05.prod.outlook.com (20.176.109.202) by DM6PR05MB4827.namprd05.prod.outlook.com (20.176.111.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1059.9; Mon, 13 Aug 2018 15:15:40 +0000
Received: from DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::e0bc:6a82:571d:258]) by DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::e0bc:6a82:571d:258%2]) with mapi id 15.20.1059.010; Mon, 13 Aug 2018 15:15:40 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Martin Bjorklund <mbj@tail-f.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] issues with processing onboarding information (zerotouch)
Thread-Index: AQHULoGngKlnrNh47kuPE7BK72Z9MaS9hdiAgAALEoA=
Date: Mon, 13 Aug 2018 15:15:40 +0000
Message-ID: <F192C17C-E9EE-4C42-AA7E-3059ACCE9A61@juniper.net>
References: <40EF0531-4112-4121-996F-32A030CC9670@juniper.net> <20180813.123601.53608699346435534.mbj@tail-f.com>
In-Reply-To: <20180813.123601.53608699346435534.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM6PR05MB4827; 6:MNndnq47mOUOJMMe1URkwIz9fB2Xj0pRsvcn/cFuAI8S01+cXA4eFjyIda92xsWNjKhyQEBf4D3opmGHCkrEOVOcACot0Kgwl8AiYzr7nfj/BPG0w1DGkDPPqsLeBq//Z32z6XMatz8YDcXClI+KLOPEvjc6nP4kDG+WjXLUxm0bgQL6VF+hcaMnGQMRXtKZ8xZTGRHtv5KELe6z3H3YsqMOmfaG/zoOQSOSdPQNmP1DeM4kwyups410QnKawZpvoOZP2oZ4paKEVpa6RbzXAmeFrVy1XWVPCobk/z1dmtM1eBCZ1WVLvwlBzEN09kLlxbwbqKULV2AlU2s+vo0kh7yxc1kk6C4CpCJWxkv7Rdr/RL3PkU3e6A0cib6CmJgbE98GfwTWSXrOF5s/IpSqwyoU+Uyxa4K9SME6crZEUlkd8hwHYiFwHw2NEGBZ0g3jiuRRqSr1Njs7rGMDh6S92Q==; 5:UnUux34E6e/r1hjt1npXH3jXtc6ZOAgKRxf4tY1Alhsikf41rE3SRsWleEU4y9M8YoyAVI5WomlQybepNh/OigMFYLuTVWEOpUJlbUZLRg4YR12Xt043PEwjaBplI0nkv725N+mhXPXk/sRwMvzhztLTE4kE+vpdsRTkOo8NSk4=; 7:7D8acg0qb+vext175PMYks0vpI295A1l3jJydiVLxHj2/nvXVVeUsV/znSv+ePbbJjvki+jW1ZPBggzuSXhPx58KcQ3p+5KNyQxJgmM2gPc1ee+onWQBH9wKABNOwpyTVQzewb+uJ9gZXkvcR61pmUrOsWDrxNWuwP1nWzJjoP05B550kMKRvsre0UtY+31nWmravLnZ64kF6wmZoozjsFwGggad4lijVQ4UszJKevlTcL5KTeP0znIiifBYgNn7
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 8b95e8ad-49b8-45a5-3eca-08d6012fa19e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DM6PR05MB4827;
x-ms-traffictypediagnostic: DM6PR05MB4827:
x-microsoft-antispam-prvs: <DM6PR05MB4827F1FE5F8B87670AC42E09A5390@DM6PR05MB4827.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(3231311)(944501410)(52105095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:DM6PR05MB4827; BCL:0; PCL:0; RULEID:; SRVR:DM6PR05MB4827;
x-forefront-prvs: 07630F72AD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(366004)(376002)(39860400002)(136003)(396003)(189003)(199004)(36756003)(476003)(2616005)(11346002)(186003)(229853002)(6486002)(58126008)(316002)(106356001)(6436002)(68736007)(105586002)(446003)(33656002)(5250100002)(486006)(99286004)(256004)(83716003)(3846002)(6116002)(2906002)(14454004)(8936002)(4326008)(7736002)(81166006)(81156014)(305945005)(76176011)(8676002)(97736004)(2900100001)(25786009)(6506007)(66066001)(6346003)(6916009)(5660300001)(26005)(6246003)(478600001)(53936002)(102836004)(6512007)(86362001)(82746002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB4827; H:DM6PR05MB4665.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: zOgCCewd2ywh7ddwKkeEwTI0+MiINUF+ozUBpYLMTketrYHP8VIWxaok4yyKEVrqBqqyezVq93IoutEYRTmUPV642s210gR4Q/Ns77+QZXpkO2Tom5fj78MJC/eWNsnZIJMb8HtKbEF9FLF+xSbnjhJDvr+SpDSn6hT9cNAwswHRo/TjNzGrCJq1b1LwlVpLuk5Vg6c7gOkgJ/Mx7GDElDrzBWmTV32+x9mjFh7HCbgAlbjoNm048VL4JnH1cFJanJg8LsZrcDmUOll8cQ/b7Pchz6bmKQxc3S+/j3UtM0RMJu/WaTLQlnU7LBmYOdltlBXZ0167ff5TZAH3Ey2cLF5s6SQnevqF9w05MTlTAa8=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <41935B67DC2845439012B25C46D46A3F@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 8b95e8ad-49b8-45a5-3eca-08d6012fa19e
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Aug 2018 15:15:40.4866 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4827
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-08-13_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1808130161
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/8dm6cxfGcAmumrJFjdnU46IVWSo>
Subject: Re: [Netconf] issues with processing onboarding information (zerotouch)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2018 15:15:47 -0000

> Do you mean that each script takes some kind of (conceptual) input
> parameter that tells it to clean up the state produced by the previous
> invocation?

Yes, exactly, it would be written as such, so implementations can choose
how to do it.


> Could we instead leave this to implementations?  In some environments
> the server might be able to do the cleanup itself (which would be less
> error prone).  In some other environments the scripts might not even
> create any state.

Perhaps.  The text could just say "the device must, on error, exit the
bootstrapping sequence leaving behind no state".  It would be good, I
believe, to mention that some implementations may achieve this thru 
infrastructure, whereas others may require scripts to 1) leave behind
no state on error, and 2) provide a conceptual "clean up" parameter 
for when an error occurs after a script had executed successfully.

What do you think?

Kent

v2.23.0 | Report a Bug | By Email