Re: [netmod] BBF extensions to ietf-entity

"Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> Tue, 06 September 2016 09:03 UTC

Return-Path: <bart.bogaert@nokia.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 C1FA112B187 for <netmod@ietfa.amsl.com>; Tue, 6 Sep 2016 02:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 pc-j5pLPStH5 for <netmod@ietfa.amsl.com>; Tue, 6 Sep 2016 02:03:42 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 3790712B0D4 for <netmod@ietf.org>; Tue, 6 Sep 2016 02:03:42 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 0DBE7F7B15F98; Tue, 6 Sep 2016 09:03:39 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u8693eSt025289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Sep 2016 09:03:40 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u8693dcJ000871 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Sep 2016 11:03:39 +0200
Received: from FR712WXCHMBA09.zeu.alcatel-lucent.com ([169.254.5.83]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Tue, 6 Sep 2016 11:03:39 +0200
From: "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [netmod] BBF extensions to ietf-entity
Thread-Index: AQHSAdSd3dfqTKzQR3WYPaIL6IHWCqBfqKbg///gwACAACKLAIAK8sAAgAAiKtD//9+uAIAAI2Tg///pnAAABLZKoP//6JUA///dQsCAAChkgP//269QgAAtgID//7M5oAAv/nAA///bVZD//9SrgP//d00w
Date: Tue, 06 Sep 2016 09:03:38 +0000
Message-ID: <D62E05768DBAFF42A72B9F4954476D65010EAB15C9@FR712WXCHMBA09.zeu.alcatel-lucent.com>
References: <D62E05768DBAFF42A72B9F4954476D65010EAB10A2@FR712WXCHMBA09.zeu.alcatel-lucent.com> <20160905.144505.1022114473592840531.mbj@tail-f.com> <D62E05768DBAFF42A72B9F4954476D65010EAB110C@FR712WXCHMBA09.zeu.alcatel-lucent.com> <20160905.151757.1934007988770514821.mbj@tail-f.com> <D62E05768DBAFF42A72B9F4954476D65010EAB1289@FR712WXCHMBA09.zeu.alcatel-lucent.com> <20160906073722.GA15815@elstar.local> <D62E05768DBAFF42A72B9F4954476D65010EAB14F7@FR712WXCHMBA09.zeu.alcatel-lucent.com> <20160906080113.GA15908@elstar.local>
In-Reply-To: <20160906080113.GA15908@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_020B_01D2082E.51CFDAE0"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/IRJYY0BCHBo5Hw1E-Mna7xmi6ts>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] BBF extensions to ietf-entity
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 06 Sep 2016 09:03:47 -0000

On Tue, Sep 06, 2016 at 07:50:47AM +0000, Bogaert, Bart (Nokia - BE) wrote:
> 
> [Bart Bogaert] When sending a configuration request to a device while 
> there is no HW physically present yet is what we call pre-provisioning 
> meaning that the configuration is made up-front in attendance of the 
> HW being plugged at a later stage.  When the plugged HW does not meet 
> the pre-configured data I think it is normal that an alarm is raised 
> but that does not take away the fact that the device was configured in
advance.
> 

In your example, there is nothing configured as far as I can tell.

The way the interfaces data model supports pre-configuration is by having a
_name binding_; a pre-configured interface is applied once the name of the
pre-configured interfaces matches the name of a
(physical) interface. I think Martin is asking the question whether the same
model of using name bindings can be applied in your case and if not why not.

[Bart Bogaert] I'm afraid I am lost in the names being used here.  Whether
it's called name binding or pre-configuration or still something else, the
key point is that we configure objects in the device prior to them being
physically present, nothing more, nothing less.  The consequence of this
being that these objects should be present in the data tree of the device
and once the HW gets plugged all operational data linked to that comes into
existence too.  I do not know of another way to explain what is intended
with what we call 'pre-configuration'.

/Bart

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>