Re: [nmrg] network digital twin vs. digital twin network

Jürgen Schönwälder <jschoenwaelder@constructor.university> Wed, 08 March 2023 13:15 UTC

Return-Path: <jschoenwaelder@constructor.university>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF274C15152B for <nmrg@ietfa.amsl.com>; Wed, 8 Mar 2023 05:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jacobsuniversity.onmicrosoft.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UN2N71cUlV-p for <nmrg@ietfa.amsl.com>; Wed, 8 Mar 2023 05:15:21 -0800 (PST)
Received: from EUR02-AM0-obe.outbound.protection.outlook.com (mail-am0eur02on20614.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe13::614]) (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 36763C151533 for <nmrg@irtf.org>; Wed, 8 Mar 2023 05:15:20 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DZyYtK6iFHyXQWDlKibVqT75P7XZOM2iwSVVcTlUbxzL3/3v7i6Zbr9am+67ho3nJcLE6bnGBMhOh/zJdkmViqZ0yQ9K1PQ8yjAxzmK2Il62gfL3mGXxchAWMaI5G/7ZJtFrkTkxKrxDyawu4xHcNf30HPkZugTRZ3IBPnFNHztlx7mU/4ZzyxFu5X6LJ1fjV3QAa0PcWNQyLpqjmYRBJRhBDPwOGNS6V4I/ud6tlduglp72PvjSz9OL3gS9KZctAuzKLJSapAYuwqCYxex+Ab/uiK6d25ZFEFCIVsP5qJeAYACaJWG5IdovQudStR/n/Atbl9OOMNKODyX6Te8YiA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/Sv8tDLzSG07wwxDOlHJ0nFpZayfsrKgIRuzQkGuxiA=; b=lbw/P0oglkZinZFOE5R1QrMMYcx8cnyitFT/WH9ORb9+YIuSCmkUddEQaAUJthiBVb7VDxlY3IWYmCEc8lUSwCIlQCfAO6sNw3F2UFgc6uYCVkMVn4Z7I83bAJGw0nRZHXBFtt1ihF15T44M6x4mHBt4djQRqcm8tY4sQ8wb4XFABYS3Ksr5w5dCG6Gva2FH0PUi72gy2pKx+w2304H1a40slAZWjO1Z8uY/A1ZzDeuakeBryfmoZuBzuuUq9u/CLSTtmnubZvBmUnjEy6FBQ9gAfYwU0EtLA7+qtMq7FVj9rDVlsA7vog3uioaaschCCTcMXEMkcWLEO+GNte6ssQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=constructor.university; dmarc=pass action=none header.from=constructor.university; dkim=pass header.d=constructor.university; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jacobsuniversity.onmicrosoft.com; s=selector2-jacobsuniversity-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/Sv8tDLzSG07wwxDOlHJ0nFpZayfsrKgIRuzQkGuxiA=; b=nUHGmQ9Pm3OHMcDitf15wbGsOzZyA4wv9jmDbWgcf6UYq1aqj/+SbdpJtZOJ5HbWNLM8bu2k61Z9X6ivgF+5ImCQVRGX63xgE8zn+bRO/Ezxo8D4AfDfAezvy0AOAtvlCawIG7CRnWEB0zO9usXnNn7I6W6T9WCNCkQA6Dwtikw=
Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=constructor.university;
Received: from GVXP190MB1991.EURP190.PROD.OUTLOOK.COM (2603:10a6:150:3::6) by PR3P190MB0956.EURP190.PROD.OUTLOOK.COM (2603:10a6:102:8d::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6178.16; Wed, 8 Mar 2023 13:15:14 +0000
Received: from GVXP190MB1991.EURP190.PROD.OUTLOOK.COM ([fe80::62bb:76a:de40:c7ac]) by GVXP190MB1991.EURP190.PROD.OUTLOOK.COM ([fe80::62bb:76a:de40:c7ac%4]) with mapi id 15.20.6156.029; Wed, 8 Mar 2023 13:15:14 +0000
Date: Wed, 08 Mar 2023 14:15:12 +0100
From: Jürgen Schönwälder <jschoenwaelder@constructor.university>
To: Cheng Zhou <zhouchengyjy@chinamobile.com>
Cc: nmrg@irtf.org, "'Diego R. Lopez'" <diego.r.lopez@telefonica.com>, 'Christopher Janz' <christopher.janz=40huawei.com@dmarc.ietf.org>
Message-ID: <20230308131512.vikghdteofhjmmlo@anna>
Reply-To: Jürgen Schönwälder <jschoenwaelder@constructor.university>
Mail-Followup-To: Cheng Zhou <zhouchengyjy@chinamobile.com>, nmrg@irtf.org, "'Diego R. Lopez'" <diego.r.lopez@telefonica.com>, 'Christopher Janz' <christopher.janz=40huawei.com@dmarc.ietf.org>
References: <20230307142824.qzzzbwyuftsyu5e7@anna> <6ad6b91698a449af9c37b2666e9b4d89@huawei.com> <VE1PR06MB7150263A1ADB2B7C7CAEC614DFB79@VE1PR06MB7150.eurprd06.prod.outlook.com> <039901d951be$7b490780$71db1680$@com>
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <039901d951be$7b490780$71db1680$@com>
X-ClientProxiedBy: AS4P189CA0021.EURP189.PROD.OUTLOOK.COM (2603:10a6:20b:5db::12) To GVXP190MB1991.EURP190.PROD.OUTLOOK.COM (2603:10a6:150:3::6)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: GVXP190MB1991:EE_|PR3P190MB0956:EE_
X-MS-Office365-Filtering-Correlation-Id: 1dc1b1cb-fe41-44d9-5c24-08db1fd72743
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: kLfRffu5Qa7YnUvnHVPp+YhthFhW8b7HNL61PAun/yoB/ClztvFrkCdP7cZg4eKUH7zjjJ1S1knBXvhO4JcC+ghZB4mA3VNrtsAPim+adxmEZng3i9/+nCOb/BZrG0QeJ8CPUQmjcDVLc4INBAPcR83F+Mb7sZW9QRC7oVm0e04WmrRqJrmrOIk1NDy7tlpaYRs60HlJboKoiGRqR7EMTFUaGLvZNPd98OZE6cwlnoJUupd+fUhirvNVH6HIEH0wCPIe8p8wfo1mapnbvi6zNcQ1w0EQn3N8QRWBoZHFACNw2neM4ILhAKRLWuxe1guKGNVjNwNGBvWjNQkUve9ZF/UJ9au6Lm+w4MBb/pGpF5W5fH3XlT215Fw7FwICrlOVDYZLWyoegapBeWBBMql24OFhH2knnhfs9DF5bvv7FV+75fiAcPBrkeru3mTsUXkLW1ydk/0hcpR/dqo9LFA/I5xyg/bUH3Hg8duiEwfyPW6rTKZlGgNPoL/5CPcUNZHKyjcySDHbuZejbQazyQOtKftwFuWIgHIrcOShnpyHe9tbVzvR3IGc5SVhPmkrZ02cIxPbb4Uf1+e45gUpF5MUHWWurnqwhO5ONgRrKHeBU3xIyb/39wHs5Eb7nEsBoQwrKBLa1IWmcdW3oLGPe2qHPGLUDBT8e/Zj0ob2KyN2p+HVSjjp7OLKrg4NmY6MX8lNtCkk0WBrfUjJzqYKIXIQSq3KeJxWz6QMF+t8GwoyqaWXwhNyyzn4avaxT2x5vJ7J
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:GVXP190MB1991.EURP190.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(13230025)(7916004)(376002)(39860400002)(136003)(346002)(396003)(366004)(451199018)(9686003)(85202003)(38350700002)(66899018)(41300700001)(186003)(316002)(8676002)(786003)(66476007)(54906003)(66946007)(66556008)(53546011)(26005)(3716004)(6506007)(6512007)(1076003)(966005)(6486002)(33716001)(86362001)(66574015)(45080400002)(83380400001)(38100700002)(4326008)(40140700001)(52116002)(6916009)(85182001)(3450700001)(2906002)(5660300002)(41320700001)(478600001)(8936002)(46492015); DIR:OUT; SFP:1101;
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: VZVODez5vPkduFWxPOJKHGnEdCXoiaMoUVO3CbVKJWoy+bo3bAWJFg6wWLwquk8q82hpw6rvKIp6q7Rdj0PkFjEB6rHZA78hz909K64I6O8J6yrmIhmEiyJE3A+ktYdG1JoZZfQ39kGoylgt2YjGojwFbmp6tWkDyHUEYUT5MMfthAvHAVwxA7d8pYPpYthRH/FQ+/grwwbbfSaZpjlFEfhlG3jgPlDzf8jL8GElw+DniEwOJJkp7EqxhCfBOoJO9UnwiaBlBZiBL9Cn4LoBaJvugOfKUxaWuYuI4vWmDFse246EC+TIjxrSmp0+LrppSpSWs5SpjYNFGa0p0objImZMy6mvlcyharBvwliV1nSiETczsNRjGkKZaBEjRarR6I/usnS4FMcitFsVLAsngBSogbaMaqlUW3nlII10oTSJLeDwt46KAm3WTtKNKlcI/RSq5Otx4iYyxAnGZKsQZ8i3rMbMGU/V3GGllLn/QKEOVnQtoI2Xpc9F6f3eVlIB0jN3ipKXk5cEOBeFg42mowZkLEzu+HXjiiDVWYfuWHWONEj6Q+PVK9iKPtoZj+NTkQ3c74wz0wbWTeaDyuwFohz30ROosjDfq86TuwFhTrBiRCpxI2NhIPmkCYo3tYKMEoiigkd27ZQLy0CHEGPDTY25pXFLiCoxG/Dsm2wPL0Gieq1hHJqJKOZcryc1L7GS30iRSES+R10ZcqVGlZkpevAD6xkm1mHiMYDy4wxRKZJ9e7pmpJe4yHZPxdNJPLX/D02a0xQOEQyUV3/85UYXxEzCxJexO+ZyL152Bz0NKwG0NBUNv+7M9fOEyYz1IJ6oynbKcrv6s8NH+RPI7hsMkpo5HEjkmWzPOdI3zziz38WhrVOMe3fxyNiJD6X9Zi74tQ3/piTuzslbIcIL4HKoqS6jB6Oz1NCrirem1F2++TQdKlJRBiYvxYuOQ2cF8bGNv5yXcMVfMJV8UU8ZHj3JNcbuV3Mb8ri/GlmufZQmbleICs87wXe5NVkGRZTQ+ksC8XXqInQoFhCDHfSxh1JRR9IUvLYVXrUucuPP7dnkQt9KLZEb0qx1xpRzurY1cmyFiIFdYPxEaSwMtd97NIBhEZkVyAdqJ1KvCE9YNZbcJsVL4GLjR/ouNzerwe0Wu3n3OfR8pOjJhPDLXIcEs3Y6yok9PT7tZx8CLW/CD4VKQMgDhIe2/JUWh79VPc43XEPJ2GiRp3whx8fiJJL6uRqwdQaoPIL0lCIg4Bom6WckpDJD4n+3FAdOtUbuzEJiTtjOZWC7emr7IzvzEKVhER9RF9q8yy1DXdP0og2K+pjceg/1FvxvQhy51KX1coty2zrCOaGM+2dVVHBATpQSeSSSd7MnOxTIXR6UFbYW4oIu7ui9/rNK7wNkPW62fnqQ5WZlByWNfMWZ/bkSkZuHV7eg62eT/fYQXSgBDf1AJ0AEtEiSW9r5S52TiQanAM+jZMSYI8qy7BEz70NHdVlCaCdsyCNWaq3LwxxgJTZdz+fliJz8GF07jnd9XgkowxvzN2EyAfB4J1RTjGCDlhYEFCWbNIvGKrUniU6pbnFnuHoZHP613f9s/2biYgy4Xqcpdbvj+hvbR+4xlRbrHynG61NUzPBZvFBti32mZwmDjcvVJmQ=
X-OriginatorOrg: constructor.university
X-MS-Exchange-CrossTenant-Network-Message-Id: 1dc1b1cb-fe41-44d9-5c24-08db1fd72743
X-MS-Exchange-CrossTenant-AuthSource: GVXP190MB1991.EURP190.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Mar 2023 13:15:14.1774 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: f78e973e-5c0b-4ab8-bbd7-9887c95a8ebd
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: rk9/g3N9m8U4a+g/z9aahrEaG+ZrGi2v9BNC79gxUOcfSbdEsJQivr42d/K96Kemx8chZLqhFaC5Ai79JzX38NyBtiBicPUSzLptwveE+7A=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR3P190MB0956
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/EFGuUahO1BCChkPKDjo_cJF0fao>
Subject: Re: [nmrg] network digital twin vs. digital twin network
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Mar 2023 13:15:25 -0000

My naive understanding of the English language is that an "electric
car" is a special kind of car and a "software defined network" is a
special kind of a network, Hence, a special kind of a digital twin
would be ...

/js

On Wed, Mar 08, 2023 at 09:04:12PM +0800, Cheng Zhou wrote:
> Hi All, 
> 
>  
> 
> As Diego mentioned, we have discussed this topic some time ago. I remembered
> that the conclusion was to remove acronym ‘DTN’ to avoid conflict with
> ‘Delay/Disruption Tolerant Networking’ (a working group of IETF).  However,
> we didn’t decide to change the term of ‘digital twin network’. 
> 
> As one of the coauthors, I am open on both names. However, I still prefer to
> use ‘digital twin network’ with below concerns. 
> 
> 1)      Network is the target filed to implement Digital Twin technology.
> As DT used in other industrial fields, similar terms  ‘DTxx ‘ are being
> used, such as ‘digital twin city’, ‘digital twin manufacturing’, ‘digital
> twin factory’, ‘digital twin energy’, etc. The terms are with same meaning
> as ‘DT for xxx’. And in definition of current draft, we also pointed that
> ‘digital twin network’ is also called digital twin for networks.’  
> 
> Digital twin network: a digital twin that is used in the context of
> networking. This is also called, digital twin for networks. 
> 
> 2)      If not considering the acronym confliction, DTN can be a better
> acronym for a relatively systematic networking technology, such as SDN, CDN,
> IBN, TSN, etc.   
> 
> 3)      In academy, both NDT and DTN can be seen. And, the there seems a bit
> more papers using of ‘DTN/digital twin network’ or the extensions, such as
> ‘digital twin edge network’, ‘digital twin optical network’, ‘digital twin
> 5G network’, etc. And from extension perspective, DTN seems more easily to
> be extended to specific network domains, with terms of DTxN.
> 
> 4)      In some other SDOs such as ITU-T, 3GPP, the term of ‘Digital twin
> network’ is being used. 
> 
>  
> 
> Regarding the difference between ‘digital twin network’ and ‘network digital
> twin’ in this draft,  DTN can be the whole interactive virtual-real mapping
> system, building with the DT concept or techniques; and NDT can be the
> twinning entity of the physical network, focusing on data and models in
> digital twin layer. Hope this can help remove the confusion. 
> 
>  
> 
> More comments are welcome. 
> 
>  
> 
> Thank and Best Regards,
> 
> Cheng Zhou
> 
>  
> 
> From: nmrg [mailto:nmrg-bounces@irtf.org] On Behalf Of Diego R. Lopez
> Sent: Tuesday, March 7, 2023 11:01 PM
> To: Christopher Janz; Jürgen Schönwälder; nmrg@irtf.org
> Subject: Re: [nmrg] network digital twin vs. digital twin network
> 
>  
> 
> Hi,
> 
>  
> 
> Thanks for the observation and the recommendations.
> 
>  
> 
> As one of the coauthors, let me say we already went through this discussion
> some time ago, and my reckoning is that the use of the term DTN, initially
> employed, was caused by some language misunderstanding, and that we all
> agreed on moving towards the more adequate NDT. If there are still remnants
> of the old naming in the document, this is something that obviously needs to
> be solved.
> 
>  
> 
> Be goode,
> 
>  
> 
> --
> 
> “Esta vez no fallaremos, Doctor Infierno”
> 
>  
> 
> Dr Diego R. Lopez
> 
> Telefonica I+D
> 
>  <https://www.linkedin.com/dr2lopez/> https://www.linkedin.com/dr2lopez/
> 
>  
> 
> e-mail:  <mailto:diego.r.lopez@telefonica.com> diego.r.lopez@telefonica.com
> 
> Mobile: +34 682 051 091
> 
> ---------------------------------
> 
>  
> 
> On 7/3/23, 15:38, <nmrg-bounces@irtf.org> wrote:
> 
>  
> 
> Good observation Juergen. I'll let the authors of [1] speak with respect to
> their document, but looking elsewhere (e.g., ETSI ZSM, papers, etc.) as well
> as at normal English language usage:
> 
> - the digital twin of a network is properly a 'network digital twin' - this
> is the clear native interpretation of the term as well as the broadly used
> sense.
> - 'digital twin network' does not broadly have the connotation you suggest
> (a network operated by a digital twin), nor does the term intrinsically
> suggest such a meaning. If anything, the term suggests a network used in the
> implementation of a digital twin. I'd thus suggest the term is not a very
> useful one.
> 
> Best
> 
> Chris
> 
> 
> -----Original Message-----
> From: nmrg <nmrg-bounces@irtf.org> On Behalf Of Jürgen Schönwälder
> Sent: Tuesday, March 7, 2023 9:28 AM
> To: nmrg@irtf.org
> Subject: [nmrg] network digital twin vs. digital twin network
> 
> Hi,
> 
> I see both terms being used in [1] but only one of them is defined and I am
> a bit confused about what the exect difference is between these two terms.
> Perhaps both should have a clear and explicit definition?
> 
> Naively, I assumed that the digitial twin of a network would be called a
> 'network digital twin' and that a network that is operated by using digital
> twins as a 'digital twin network' but that does not seem to align with what
> [1] says.
> 
> /js
> 
> [1] <draft-irtf-nmrg-network-digital-twin-arch-02>
> 
> -- 
> Jürgen Schönwälder              Constructor University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://constructor.university/>
> 
> _______________________________________________
> nmrg mailing list
> nmrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nmrg
> _______________________________________________
> nmrg mailing list
> nmrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nmrg
> 
>  
> 
>   _____  
> 
> 
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de la
> legislación vigente. Si ha recibido este mensaje por error, le rogamos que
> nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
> 
> The information contained in this transmission is confidential and
> privileged information intended only for the use of the individual or entity
> named above. If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination, distribution or copying of
> this communication is strictly prohibited. If you have received this
> transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
> 
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
> 

-- 
Jürgen Schönwälder              Constructor University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://constructor.university/>