[netconf] Digital Twins in context of YANG and NETCONF Datastore

"Schwarz Albrecht (ETAS/ESY1)" <Albrecht.Schwarz@etas.com> Tue, 17 September 2019 12:51 UTC

Return-Path: <Albrecht.Schwarz@etas.com>
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 E3AD4120850 for <netconf@ietfa.amsl.com>; Tue, 17 Sep 2019 05:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=etas.com
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 NsqRQPewLLQY for <netconf@ietfa.amsl.com>; Tue, 17 Sep 2019 05:51:53 -0700 (PDT)
Received: from de-out1.bosch-org.com (de-out1.bosch-org.com [139.15.230.186]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 660CA120846 for <netconf@ietf.org>; Tue, 17 Sep 2019 05:51:52 -0700 (PDT)
Received: from si0vm1947.rbesz01.com (unknown [139.15.230.188]) by fe0vms0187.rbdmz01.com (Postfix) with ESMTPS id 46Xjfs60Kfz1XLDQx for <netconf@ietf.org>; Tue, 17 Sep 2019 14:51:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=etas.com; s=key1-intmail; t=1568724709; bh=mMRLNv6nWqhKp5VQEcU3zAzJs0Kro4w0sek951h9umA=; l=10; h=From:Subject:From:Reply-To:Sender; b=iY/aLwSHbPL2SN2AZktNgHoj5KMmLYFyzw8NORghNFj081mx4tSsZxMu8uFJxRYgO GaLhEurLM9oCi/C8lCgLNoXAQkSb1B4XZTVBwEj2ll8KQYj8iJu5wjf/J4YiE5uetO rwVw+E9hzUYnfRq9p9nR2dWAt6Gs9JyUJXvRAVgM=
Received: from fe0vm1741.rbesz01.com (unknown [10.58.172.176]) by si0vm1947.rbesz01.com (Postfix) with ESMTPS id 46Xjfs5kCpz6CjY1l for <netconf@ietf.org>; Tue, 17 Sep 2019 14:51:49 +0200 (CEST)
X-AuditID: 0a3aad15-537ff70000003bb6-62-5d80d6e547a4
Received: from si0vm1950.rbesz01.com ( [10.58.173.29]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by fe0vm1741.rbesz01.com (SMG Outbound) with SMTP id 2C.05.15286.5E6D08D5; Tue, 17 Sep 2019 14:51:49 +0200 (CEST)
Received: from SI-MBX2055.de.bosch.com (unknown [10.3.230.149]) by si0vm1950.rbesz01.com (Postfix) with ESMTPS id 46Xjfs3dNKzC9P for <netconf@ietf.org>; Tue, 17 Sep 2019 14:51:49 +0200 (CEST)
Received: from SI-MBX2054.de.bosch.com (10.3.230.148) by SI-MBX2055.de.bosch.com (10.3.230.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Tue, 17 Sep 2019 14:51:49 +0200
Received: from SI-MBX2054.de.bosch.com ([fe80::187:74e0:f8c8:c9b1]) by SI-MBX2054.de.bosch.com ([fe80::187:74e0:f8c8:c9b1%4]) with mapi id 15.01.1713.009; Tue, 17 Sep 2019 14:51:49 +0200
From: "Schwarz Albrecht (ETAS/ESY1)" <Albrecht.Schwarz@etas.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Digital Twins in context of YANG and NETCONF Datastore
Thread-Index: AdVtOy/e8x/GzuO3Qz6xXy+qg7LMCw==
Date: Tue, 17 Sep 2019 12:51:49 +0000
Message-ID: <929a628b61804f9887f479f128eea20a@etas.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.132.146]
Content-Type: multipart/alternative; boundary="_000_929a628b61804f9887f479f128eea20aetascom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA21Tf0xTVxTmvj7g0vHW56MdxyrJ9gJmuFnKBtHNzZi4xSVzmWaZxm0NPuD1 xywt6StGyYgYt5WVEWVOVyoKYw0xGpkgVWALbJ0/kQWiFkFINqW4ACbW0bChjO09XrH9Y/+c fPc75/vOuefmYgVTg7XYYnPyDhtnZZOUpPLV0xmrxgcrDfprn69Yc7htJHE9esvnmyU2ow+U rxXzVssu3pGzbofS3F7XTZa6jbs9N0NkJRrf7kYpGOg8+HusPtmNlJihPQQET9ST8uEXBJH7 /mjmAYJLw/3RQzeCaw1TpKRPotfD1cH9SRJW09mwzxtOdCOM00S+sytTgmr6Tfh0AMkVOuia +4qQMElnQfCCawFT9Groam9QSBjRGXDmTP8CVtDpcDvUQMiT0uD7UeaB1sDE2HyijJ+FfZEm Qq4vgJbab5DsuQSu1oXIgyjNG2fljSvzxpXJ/IvQ+MOfSTJ+AZq/nVIs4r6fxoh4vhEln0Qa I6/fVZK7Oi9X5yjkhXJ9rq7IXtKG5GfRdKDwhDGACIwCKB8TrIbyfl1pYJ4utBfvMXOCucBR ZuUFVkv5M9YYmLQntFBWWGIRBIvdFkCAFaya2lyx18BQxdyect5hl2UBtAyTbDplwu9+xNAm zsnv5PlS3rGYXYsxC5QyKDZc4uBN/G6jxepcTLMZFEpISGCeic/EtyVwSgC9jFPF3vabogUl lHIlgsUUlS+V5cwiG5P2og/xwYljTQrcefG4GH9eiA9P+sT4lxQZ0ma38dp0yiv50pKDucz2 ZDLtcgpUFQZGE5eIuU+iIYQRm0Ydk8Sp4j+IzQTUxvAO8bJRMiZ6ySdqaFcqRPwq6Bm+gaCj PUDAHX81CdU9j0mYvl2bDJ7vzqfA6PnPlBDp/e0peFR3WAXn2q+rwBPsp+FiqJmBvlNVauip 8Wtg1DcCMDR/WQutf/RpYajz3jI48IXvORi9dYmF2Vu/slA1/3smeObuZUHV3RMroHbelQ3/ Hj+bDWePfLkSpmfdq6C1+XEODN9v1UPf/jH9pLhvQtx3dlGFtG8n5/yffUfZ2OW0lShvZ/Do hndytrjftr7f22GDmqmif0z5k9066m7LyCffv7d9ncczZ62eeH5QHT7NbVx+aKuJGXJdd5lm Hg7ccDnLQ87wBuKVhupNmcGZpoh6Zjwy/ODK2vo3CnSH2i6/Pqiaqkq/8vG5AfWdli3GrFOz 41T+gQvbpktVNY3JqW0KYi9LCmYud6XCIXD/ASDbHZegBAAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/01S9QOsFbo5MuihxDHj-5aibfYo>
Subject: [netconf] Digital Twins in context of YANG and NETCONF Datastore
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG 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, 17 Sep 2019 12:51:57 -0000

Dear All!



I'm curious whether the IETF NETCONF/OPSAWG experts did already discuss how "digital twin" related concepts could/would be mapped on our management architectures.

Being aware that there's probably still a precise term definition lacking in the IETF, I guess that we could make at least the rough working assumption that e.g. "a digital twin relates to a virtual representation of a technical entity".



Thus, when looking at the types of technical entities in scope of these IETF WGs, then the two twin entities (let's term them A and M) would/could be related to

*         twin "A" = managed system (acting in management agent or management server role) and

*         twin "M" = managing system (acting in management manager or management client role).



Consequently, the digital twins would relate to managed objects (MO), constituted by management data models.

If such a working assumption and management concept wouldn't be completely nonsense, then I could imagine that a digital twin could be equated with e.g.,

a) a dedicated YANG module (covering all management data as part of a digital twin related management services) or

b) an existent or dedicated NETCONF datastore instance "digital twin" (either explicit or implicit (using filtering))?



Could you follow such an interpretation and mapping concept of "digital twin" to NETCONF/YANG?

Did you already touch/discuss the digital twin conceptually in IETF meetings?



I think it's worth to provide some statements or recommendations how NETCONF/YANG technologies could be used for the realization of digital twins (or course in specific system contexts only). I think it's feasible.



Thanks and regards,

Albrecht



PS

I would firstly postpone the aspect whether the Internet architecture is of type IoT or non-IoT. (The IoT assumption would be that the twins would be located at IoT device and application layers.)