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

Kent Watsen <kwatsen@juniper.net> Tue, 14 August 2018 20:07 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 DB0A9130ED2 for <netconf@ietfa.amsl.com>; Tue, 14 Aug 2018 13:07:22 -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 KGNMIFBh17Q2 for <netconf@ietfa.amsl.com>; Tue, 14 Aug 2018 13:07:20 -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 A0CBC130ED0 for <netconf@ietf.org>; Tue, 14 Aug 2018 13:07:20 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w7EK3XMC029311; Tue, 14 Aug 2018 13:07:19 -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=O/mbdZncFLVGLMflkkaG7vInt+gjYTocrsbtnipXtG4=; b=qm0eg8rqqUzDnr9bjzbKiWbuMPkK1BdPGa0WhUETUGimj5IH3q2gCYZmUBDRvH9CdAe0 akjzQf7yHOvd+SsrLl1lkdTxo/FRFlej1op/F0xC8lRFFwGnrYJUd4vFEV6of9pjGXYD 0tAj85MEwf2oFjToomFMg6Db/WIHqKWTwWXLJh6hJ5X8XMlcfz2hDt0VxuhAtb74FONM JhRcEdI0olZy0gL1YDZ4y5BNGCkpsPeIiXcaRFiLbhelwwSRiGUpmGP+D9jqP4NuzEGe HGXLuil51St7QoIDu4ZQU2jwkUDuTdGnpQVQlhZCRbdFVS+14B6GMaHYDwDQcXqyWINg Pg==
Received: from nam05-dm3-obe.outbound.protection.outlook.com (mail-dm3nam05lp0119.outbound.protection.outlook.com [216.32.181.119]) by mx0b-00273201.pphosted.com with ESMTP id 2kv55601yw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 14 Aug 2018 13:07:19 -0700
Received: from DM6PR05MB4665.namprd05.prod.outlook.com (20.176.109.202) by DM6PR05MB4314.namprd05.prod.outlook.com (20.176.78.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1059.10; Tue, 14 Aug 2018 20:07:18 +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; Tue, 14 Aug 2018 20:07:18 +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: AQHULoGngKlnrNh47kuPE7BK72Z9MaS9hdiAgAALEoCAAYAaAIAAY7eA
Date: Tue, 14 Aug 2018 20:07:18 +0000
Message-ID: <BB160F25-771C-429E-A046-8096F2ADEB44@juniper.net>
References: <40EF0531-4112-4121-996F-32A030CC9670@juniper.net> <20180813.123601.53608699346435534.mbj@tail-f.com> <F192C17C-E9EE-4C42-AA7E-3059ACCE9A61@juniper.net> <20180814.121024.510147117520021210.mbj@tail-f.com>
In-Reply-To: <20180814.121024.510147117520021210.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.13]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM6PR05MB4314; 6:wmaLuvUdBL3x3pbs6O1q3i7m9O4zYct/P3ckfS3bSHAens/y3p4Ep1J9s0IgDwIarm+gpfiwG3YjVba6hhE9zozxh9r4hRfmZvA7njybVX+Rt6fm3WJJG7mz0X60N7H/TsnFFLgBJUC6bhKxv7pCIu39KJBFpTtS/pg35qSY+2lzPKlHWTVad75lhydUJLzaklVV/i9l0tv4mq67w972XvFXDQgT50OAeuBQlDsgJ9/9QChTBTX8vLUlmzg5ntXvlqM+lOLX4SRIgDWTN1lFI7v7r0js0viIxiG0JBbFlErV3YDi2rOEryATShYQb7MnOS/5RvhvrGwZPR62Hbj2cRy0dDM1CE9G1nlzpOeXhAp9vjX0woQyWx00v+V6unXPj7UMCjBX7ZxyXJk/EcymGcsW8e5Nbs7BAkSQQV84hznmfffdUXQGRbIDtzqeaHt97VtYaXKnwO6TnIz1f8GdtQ==; 5:ZspByqkLRWpQaoF8qr8fRQmYqcttBM3qbZsaeyiazp6EoxjyFcJAT43BhSBRjrmGNF3pN6w94K9eNA552WXRLhPMV6Ve3w/kJC6GcHuCLUoYIiGW04u8v/z8GZ65wyOr/VKiHImLcisKCxcnZfFdzZTCHl5yIInOjqJNfpKFOas=; 7:4M++R9PpPUtW4j/tbzyY8GY+71x1VQd2qpEAp62mlSX+4MWwXHij3J4YsvfLgQcqnwysHHN0zgylwdAtzTnd6+l/lQqAI6f+YM/Yf7ho5rfEluPFNCBy7GwUoqS7TeJqrEXn4Qz25WHzW5WiK71A1WiUciJDokmb+Tbo+jWLP5GPGfymg9atdbwpzWVDDa5JaNPTVgwNKQPy1BBKCS3g3idipr7Ewte3hCjZfIXZh6I9vqNaVOZpA/fBWeDmFnBc
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: a14d471f-bedd-4b48-f2a6-08d60221897d
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:DM6PR05MB4314;
x-ms-traffictypediagnostic: DM6PR05MB4314:
x-microsoft-antispam-prvs: <DM6PR05MB4314A2F3ACB03A5C2AE2EFD4A5380@DM6PR05MB4314.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231311)(944501410)(52105095)(10201501046)(3002001)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:DM6PR05MB4314; BCL:0; PCL:0; RULEID:; SRVR:DM6PR05MB4314;
x-forefront-prvs: 0764C4A8CD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(376002)(396003)(346002)(136003)(366004)(199004)(189003)(26005)(229853002)(6246003)(446003)(6436002)(8936002)(11346002)(83716003)(316002)(36756003)(6512007)(6916009)(6506007)(14454004)(6486002)(33656002)(3846002)(25786009)(86362001)(81166006)(99286004)(6116002)(76176011)(4326008)(81156014)(186003)(102836004)(58126008)(305945005)(256004)(14444005)(5660300001)(2906002)(486006)(7736002)(93886005)(66066001)(53936002)(2900100001)(476003)(8676002)(478600001)(97736004)(105586002)(5250100002)(68736007)(2616005)(82746002)(106356001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB4314; H:DM6PR05MB4665.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: 1OxkkkXD1QCiDX3RdstVg04nJ47DsdInHN6bLW1SuFL6ILbvH1p8vvBGIN8VnnzyYHw9W8cAtQVhB1xdEUzWEIkdWzlG2gwxk0I9SIKlyhO9frg/UZAGhc3d9jFbohplVCrTuNhjxfWZhTtqv0mC6Fk6o80+lFfd7uYwxMfMbDQGnhoDrIV83LNy11Wm/aMnhoulsLDZ3xrzPrGJmgtJjF0EPgb//GCwbnLNEJFU3oZwQR28KK2tmuHB66TyA/nGSHLDcf6hqNuNODN/p8VV2oGrQ7GrRXiBhoXdfL4fe0LKEdnugrXtDuqqI85HxUO6o16g0q/w5THhgD1EX/sFUm/zY0EgLNbZy4agtTymWw8=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <42099279EE30D541B599F66FF9A9C469@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a14d471f-bedd-4b48-f2a6-08d60221897d
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Aug 2018 20:07:18.2462 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4314
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-08-14_09:, , 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-1808140202
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/YKyw26VCG9bgOJ0ZhSS3CJ0lDKE>
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: Tue, 14 Aug 2018 20:07:23 -0000

>> Perhaps.  The text could just say "the device must, on error, exit the
>> bootstrapping sequence leaving behind no state".
>
> But even this might not be necessary in some environments.  I think
> this whole notion of dealing with state associated with script
> execution should be left to implementations to deal with.  It would be
> ok if this document had some kind of Implementation Notes where things
> like this could be discussed (w/o any 2119 language though).

This particular point was raised both offline as well as from the SecDir.
From SecDir:

  """
  I think it's already clear what an error in paragraph 6 is. What I 
  found unclear was what to do with errors in paragraphs 6 or 7. Yes, 
  don't go on to the next step, but what about: In paragraph 6, should 
  the device rollback any partial config update if there's an error? 
  In paragraph 7, should the device rollback all config from paragraph
  6 if there's an error?
  """

Thus, I think we need at least the high-level statement.


Kent // author