Re: [Netconf] issues with processing onboarding information (zerotouch)
Kent Watsen <kwatsen@juniper.net> Thu, 09 August 2018 01:30 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 C2BF2130F01 for <netconf@ietfa.amsl.com>; Wed, 8 Aug 2018 18:30:36 -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 cguH_7LrYTiJ for <netconf@ietfa.amsl.com>; Wed, 8 Aug 2018 18:30:35 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 24CEC129AB8 for <netconf@ietf.org>; Wed, 8 Aug 2018 18:30:35 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w791UYpT027404 for <netconf@ietf.org>; Wed, 8 Aug 2018 18:30:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=PnllQBnJbEe4W8nisg5znmK82eAggiQS6rFjAP2VQO0=; b=L+U8xbiQZZWxJ6oUUIVtmCJDYAc7GCPC8OuHh3a8lDs/Q0x3d4MCCkI9RvNP3Dy5t5By cXJ9ZeKR8wpohg7sEQSrME3hiGirGBAF2jSLX6rGzGxbOQMiVHqQXYEi8bvIzOPhs9bB 34NFvAd7AqQJgIPvrQgcGuxdohxYBvQ+aSLMV+bbNbapKRydTLiDE1pkNHmA8WOOprvx wLxsPO3et5W0C8KzWAvMDzD0LGj4r4bpow/ttZTl/2L7Q1SUZZgrO6dKeWZt8UGUIVWd t9IxNrV9SXG3n8TwJ6Y75Qzd3JeqJrBD1WKrT8ebdlsB//5EwT9R46wrPJ1s4zWGjfdr WA==
Received: from nam05-co1-obe.outbound.protection.outlook.com (mail-co1nam05lp0082.outbound.protection.outlook.com [216.32.181.82]) by mx0a-00273201.pphosted.com with ESMTP id 2kqy1qhgg4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <netconf@ietf.org>; Wed, 08 Aug 2018 18:30:34 -0700
Received: from BYAPR05MB4664.namprd05.prod.outlook.com (52.135.233.78) by BYAPR05MB4840.namprd05.prod.outlook.com (52.135.235.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1038.13; Thu, 9 Aug 2018 01:30:32 +0000
Received: from BYAPR05MB4664.namprd05.prod.outlook.com ([fe80::cd0c:7b9d:8c70:dfbb]) by BYAPR05MB4664.namprd05.prod.outlook.com ([fe80::cd0c:7b9d:8c70:dfbb%5]) with mapi id 15.20.1038.019; Thu, 9 Aug 2018 01:30:31 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] issues with processing onboarding information (zerotouch)
Thread-Index: AQHULoGngKlnrNh47kuPE7BK72Z9MaS2YQ2A
Date: Thu, 09 Aug 2018 01:30:31 +0000
Message-ID: <4F5A4F85-7CEC-41E9-AE04-AAAC2298B9BE@juniper.net>
References: <40EF0531-4112-4121-996F-32A030CC9670@juniper.net>
In-Reply-To: <40EF0531-4112-4121-996F-32A030CC9670@juniper.net>
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.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4840; 6:0j54XtEySUeM3M4v5H87pmio+gXDB65s2RZCYKljZmXeXM+QDt5vDiE2acmz9JeqQ1LkOZ2iV/NfN0MAYFipyIGgg1VnFSguWuGY+Y2sMgGEa6JX5zNeJ0RejYgaltqccGruT4NVT6rb5WRiYvgrohz67+THbm4VugnvUrAurT9iitnuT72NTP3AknwL/ILYnlrW20wVcvaxkJ4uab8GFaq88a//0hIIlfQR/A5Nome31PvKPQHNf9guKVemEHzH0PIZOVHFnljQbzuFQr+rt80uKAAv36nuAFmbXxpF8IsOggAhqffSrAF4C2/obfgEm+0g58i+mBV0GdSI+Erl/qfNSZdFk7yTE+HOQhal8Cudq5IPwtNmKYFek1EEMV8Q/NnsA6vIWooT9wYSwNVWTJyhhV9qld1WBBS/41W/hcE1ypiEGfEqbhaws3JE9jDGiH26WHZ6IlRZkQlZO1rx/Q==; 5:+XSak/A0BvllDS2K2F6cPyCALh0Jhhld5K1NdMU5QeqUHbBJ1ZVDJhcr1pEY0j+C0QdNn+4VKURtaGOiLMcmLVfUSaT/f5CJ6KQGtqwPCxc/u+fuG4bGZQuxmwm+sKrG02vnwbMAcJAbACyM5XeVgw3Uze4VbGClepGZkC2Ez3M=; 7:zHxTh5T00OOFnBaPGqd8XPi/Q3dGnicRv+MyCfmuFYe4hXp6MWbgBGfueSWRCArXe5KUszx4RMclXRMjGI+aUDHzRkPRvV7/eoTx1i1VEgJ4EUkoe8DutHREeEx5uu0Prp02KJjV05QFud8oI6vM40fWDQ20BbyXKFZQSjGMQqwyye7cVAxYZiIEuqOE5CsYrHoDRu0wuPGxW/nH3dmIXZMpQ4MT7NuDl3guHO0WIHpE6oi4zRYvzg9FUQ++uZld
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: d43688d2-5d45-430b-aa7f-08d5fd97b285
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600074)(711020)(4618075)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4840;
x-ms-traffictypediagnostic: BYAPR05MB4840:
x-microsoft-antispam-prvs: <BYAPR05MB484051051A83F714918C9708A5250@BYAPR05MB4840.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(20558992708506)(192374486261705);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(3231311)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123564045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4840; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4840;
x-forefront-prvs: 0759F7A50A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(376002)(346002)(366004)(136003)(396003)(39860400002)(199004)(189003)(53936002)(2906002)(1730700003)(81166006)(81156014)(6246003)(8936002)(8676002)(478600001)(5640700003)(83716003)(99286004)(14454004)(66066001)(68736007)(33656002)(6512007)(413944005)(229853002)(561944003)(3846002)(6486002)(6116002)(58126008)(316002)(6436002)(25786009)(76176011)(305945005)(2351001)(6506007)(82746002)(7736002)(86362001)(6916009)(186003)(2501003)(26005)(36756003)(102836004)(446003)(11346002)(486006)(97736004)(2616005)(476003)(5250100002)(256004)(105586002)(14444005)(106356001)(2900100001)(5660300001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4840; H:BYAPR05MB4664.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: q0rXtVvuia+4/SEA0o5HzbahugnQmENamcKavAlQkoyZofMmYE8vpsQyNlkURBxT5ifl3zENghsUvoO+e3i+giWYhfflNVX4mh5KYQfVneyARZ19LoyOjUa+4PJclp9cy65en5YIRh0+/bnNOqYvIGXEBMa14N5XKHG5+0KwLkq55g6lPLOsXilRkKutoGyebwTvyCaLjsmz8huUXRoB4uSJcax3ZtpHjZ0++eRW7Ge7+Awrry/lR9NKWM2zmEEg4EPsuKlWuwQKee+UuL13p43jVBUQoZ2mQrWgYDAgnbpDF4h8EJc+5f7uCjvWvz95VfgHKlD2meS7fhSX5NFQtwEgTOEUVaAZ0T17yl/G7PI=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <EAC033141BE07D41AE29F6BF1A6879EC@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: d43688d2-5d45-430b-aa7f-08d5fd97b285
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Aug 2018 01:30:31.8849 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4840
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-08-09_01:, , 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-1808090016
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/br4UvYjoSEbyRlNckfWERbvucTU>
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: Thu, 09 Aug 2018 01:30:37 -0000
Dear WG, One last follow-up, I realized when updating the "progress-type" enums that our plan to just have a "boot-image-success" was not enough, because with boot images, there is the huge question of: was the boot image already installed, or was a new boot image installed and a reboot is eminent. It matters because, in the latter case, the sequence to progress- reports that bootstrap server is effectively ended, whereas they more are expected in the former case. This being the case, I'm thinking to exchange the single enum: boot-image-success with the pair of enums: boot-image-already-installed boot-image-installed-reboot-eminent and define that the device MUST send the latter if the case arises. I'm open to less-verbose naming suggestions but, more importantly, are there any objections to this proposal? [I'll assume that this is okay if no objections are raised.] PS: once I post -23, so that the diffs can seen, I think the WG should be given one more chance to review the changes, before falling back to Mahesh to push the button. PPS: I also received an early Security Directorate review that has some overlapping concerns (i.e. the error handling in Section 5.6), but also some other things (mostly Security Considerations). I'll be sure to run any non-editorial changes past the WG as well, before also going into -23. Thanks, Kent // author
- [Netconf] issues with processing onboarding infor… Kent Watsen
- Re: [Netconf] issues with processing onboarding i… Kent Watsen
- Re: [Netconf] issues with processing onboarding i… Kent Watsen
- Re: [Netconf] issues with processing onboarding i… Martin Bjorklund
- Re: [Netconf] issues with processing onboarding i… Kent Watsen
- Re: [Netconf] issues with processing onboarding i… Martin Bjorklund
- Re: [Netconf] issues with processing onboarding i… Kent Watsen
- Re: [Netconf] issues with processing onboarding i… Martin Bjorklund
- Re: [Netconf] issues with processing onboarding i… Andy Bierman