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

Jürgen Schönwälder <jschoenwaelder@constructor.university> Wed, 08 March 2023 14:06 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 79476C15153F for <nmrg@ietfa.amsl.com>; Wed, 8 Mar 2023 06:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 Fm93PmbKvlAB for <nmrg@ietfa.amsl.com>; Wed, 8 Mar 2023 06:06:35 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-vi1eur04on0620.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0e::620]) (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 DDDD6C15153E for <nmrg@irtf.org>; Wed, 8 Mar 2023 06:06:33 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VKrzDHq4vDJN7L6jzHrX1K1pket2tN8SnkjGdkIYRXIYSGSxgl/4NrBsdZiDu73Wo7XkL8h1GSFmflkM4kbXo9uTnR5DSaLaP/fRsqAHdhBe9NKwXtb4ONHoUSrVYGe73Jhi7iIfS9pdM3fRilVZzMjVclxHHl0ocOjv9Zc+VXHfD/s6ER3CBpICKtPF/E4XgjrgYHaS894Qwz8EOdUWzjSf2jTtggAdn/3M7kWZ0fRJxGYFVbuyvoCpTUhwwMd0Ap6F9sqdO3tt3zihDzvW1rQHP2aZpXwsZZZ38NcXbjsHFjF790T+AcuGmPp4M3mHWcqhSm5RSbrDd8oTQPZfJg==
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=QQ22BLb6hyTrSvIQiA6SNj6DRP1tRrWlQS9diIgdnhU=; b=XgVmXVLs1hBykq0nQhTV4YTKfCMCsAdJ8HidfzU2lsZV5SnlPbRMfD4gyIAoDzXoF5/rX6wXSN36Ua+6Zv5/QTKrvPgASlryzBSYRpxVpZpmNsVeN0rmBLa+hskzrg2X7DEl5YaCj3UHwzOfxROrl03vXzCvpIz2kunW3BZH8cvT945JKeXrC+h4QH2b9ClD552dHgyHssgqhMdZUg0ZnBdG37KR3h7L+ikDBM55/lGV85hvCvn4MnxXH2Oi8pOri04SSbk+UIxSvp7CVYrXLCp2+d3HvEDTG0gYHegLmCpfpiQctMsNs8bWGzj0NJY8QZ6/qwoGUluvz9N3v3Fvbw==
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=QQ22BLb6hyTrSvIQiA6SNj6DRP1tRrWlQS9diIgdnhU=; b=MwFneix3HbQc/CysCTWjYdMQp372d4WGfb7vTJ51Zd2B0DkGNVkT3jPEjxospABFnChSXJE8+c33gCSsHbKUIxESssPATJezA8Y3o0Cxox/sR4cs3AFmdGDhk+cReCtl0JK9ziCwjhuMpAWHBu9OK8+J8y+kSYK2qRCqncKrgew=
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 VE1P190MB0927.EURP190.PROD.OUTLOOK.COM (2603:10a6:800:1b1::13) 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 14:06:28 +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 14:06:28 +0000
Date: Wed, 08 Mar 2023 15:06:27 +0100
From: Jürgen Schönwälder <jschoenwaelder@constructor.university>
To: Christopher Janz <christopher.janz@huawei.com>
Cc: Cheng Zhou <zhouchengyjy@chinamobile.com>, "nmrg@irtf.org" <nmrg@irtf.org>, "'Diego R. Lopez'" <diego.r.lopez@telefonica.com>
Message-ID: <20230308140627.ksequape4w5cwpxx@anna>
Reply-To: Jürgen Schönwälder <jschoenwaelder@constructor.university>
Mail-Followup-To: Christopher Janz <christopher.janz@huawei.com>, Cheng Zhou <zhouchengyjy@chinamobile.com>, "nmrg@irtf.org" <nmrg@irtf.org>, "'Diego R. Lopez'" <diego.r.lopez@telefonica.com>
References: <20230307142824.qzzzbwyuftsyu5e7@anna> <6ad6b91698a449af9c37b2666e9b4d89@huawei.com> <VE1PR06MB7150263A1ADB2B7C7CAEC614DFB79@VE1PR06MB7150.eurprd06.prod.outlook.com> <039901d951be$7b490780$71db1680$@com> <20230308131512.vikghdteofhjmmlo@anna> <dabc121e5d8f4faaa14c4a5ef961e2ee@huawei.com>
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <dabc121e5d8f4faaa14c4a5ef961e2ee@huawei.com>
X-ClientProxiedBy: AM0P190CA0014.EURP190.PROD.OUTLOOK.COM (2603:10a6:208:190::24) To GVXP190MB1991.EURP190.PROD.OUTLOOK.COM (2603:10a6:150:3::6)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: GVXP190MB1991:EE_|VE1P190MB0927:EE_
X-MS-Office365-Filtering-Correlation-Id: 783aecdd-98e1-4175-65e2-08db1fde4fab
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: zPm/HjtatuBKABdtsNhKHYatVnoDsM3GZGz8BOJMc4oLvokG6DjOjbnOjWmCqGtm0Un8M88BK2aFA/Ji2ODu+zKehTnmZRFEofL/bQ1/TQ07LYzop481h3ps03KiBRHf66BKSqZmA+8L9tlr2mgvr7lLP4Pc9ltHuvomxe+2Fj6mgvq8QvoV3lc+EN4iIUei0/rVJSrdY/2GVnI1wmuuoCVCeCwDiuqCZ2JC6aO+ffCcX9j2+Pyv8NrGif9COUwu64yzWX+khP4eaRxS1WbsKzyHaT8iptHlICaN7/t7XPB7kS95+6Jkg8MuTLrOHygba/Fk0R3MmVl9DFJj8wHjjxGYDrjacoZJ6hYHiXKQVN4bdqyiAOGOqfWvva0FiRQ5I/BAIOB5p0rmIq8MTlfFGmWFj+pNpWVbfXYnTT07c4N/fyQY/DhTl9QmyYqC4QlEawLsEccfzat7ZwlshxXxhs4G0TU9HVN8S2AWiIVwSh9TA7+sFWZIlgYOSiLJiUbuO3V9BXDbNgIy3jRT7eBLjxDbk7yMal16t9um29/gnRnBKUZ3S0wH+VeLEbSJktVdRtN8cldiNvuz0xpAz0bJ268x6tNv6Df3of4dPnL835k3vc3v15pwcmBU8mH25Ledq8kxqmOOmVa9F1fCpIasaYk+7nsnzZK6j4Un1S4uD+2iPE13FDIl6ooDzwOpSYEBPdLEnbUp767v3WpOi8M5v4EcXXvF9oP4asKV57XOVKOFqsV4/Zm4d50MdSJki1qU
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)(39850400004)(366004)(396003)(346002)(136003)(376002)(451199018)(54906003)(66946007)(66476007)(66556008)(6512007)(1076003)(6506007)(53546011)(26005)(8676002)(316002)(786003)(52116002)(6916009)(40140700001)(478600001)(8936002)(41320700001)(5660300002)(85182001)(3450700001)(2906002)(33716001)(45080400002)(86362001)(66574015)(966005)(6486002)(38100700002)(4326008)(83380400001)(85202003)(38350700002)(66899018)(9686003)(186003)(41300700001)(46492015); DIR:OUT; SFP:1101;
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: 7lAB2cNiuL0SOmvjoQr1JXc0ffPDvc5ZhN1oh2TZ6GL0XThjyoH1vLYJHa88yx6lJHouwjRqYhCmmEe0me8GG3DCIp3MwDqRM8F29SX0ms0XRXaj7EvSno4+UlnOGukIHC9hPNJUDRts19arU3hqVRRInGRF1Lpsys3Cy+JLLJvZ7fsKX5T9gtbrabGB23N0AhnA7PV8grjODA1SlTyg8cUtGv9mnApd8UQHH3ETDMhMCdzmIn+AMOKkrtO0CrLlhYh7IPsX2DsODlZPvLPDpl4/oR6na+vaokHLRs6nRWEDSLJNr/k/JvfEKPCzxFgOirDpbgw5eSMp/VfGyRFCjIW4pacoumARtgoPT4hC1yRAYC2MP4j5bRrLvryT6mKZ+4kh7V705aBkdphIL1eTN2OaUidgrrRjGE1qqqlbcUibURQFOATo7G26RBZS1f7tHt1tveuVVtX89xoLGVty7AtrLPYXNNljTJTaYV+2CSAIVflaFJLZzbsSruIBKdGZ7KDgkGoPMR1/a3MRfx6L0lIzSFNNvbYbTHKTOGkk5jtIZ3go10TjaSXe+P03HohXkdOuY14iHhtM31DIwj8HqkBD5Wp/7WeIS6QeLKdMD0wS9FqXyJ6ci1tYsnpr/BIU6te42nmjUqOUrw4Xa9BDHw5jAI4sjXvmWA1D4NjA+rQ4zRRPr2Pp+2oyDD24RPY1eTQxQap1Al3YfAz1SAbbp61eWEPZ7EwztnKi16qCS4cquabab9mSMyb0oJObbswrCPwywU/VF6WdSF7xAc3E8Sn6xmmMlM3tJPqlpXjgVN+9Ui/OoCfsVDK3BnD0u/GHKr4zC/G9XJh1RF19vO7ddWRfEHoBvKswF89wfnO9niZwFrz0AdrgdlG7P7BLGWLhQJP1TmEUjPgT3g1h8DCW/56lF7OYORj/7RGywP316RpHFyJ5Gsn4HrdpTTIld07C+40Le86JOq48jV1Yd8v+S3jqQyfGXhay7DvhUTCZB6dq4ifUljJ1++xldessU9j56peMLwgBz5So2ebGzopuuzP8YUNaHfVV9S6ygosxWIFl+CXqglUISbS1wt1g70woE4ETfbdr3UctClFcIdO4oSCo+fVim0rIBVWaKfYyqxxE8ekTScWb6bN3zkJgDGIz1w8WodNqaIY6WVdj/HjZjollvhhczb336lUSmgfU503l7Dsmu8/tNQTxsFbLGOfxrdrXua/Z/VelXauYPZ6flnBE2gWg2SYxHUQ8o7EJyre4VCINpnY7WwbRGdgSbfHinsSwan/rLHaGTgM0QQNoQmwHBFJp4XYMFYfP/+MGTnJr4fnv4qTEfE/CbemWy+e/Sa5SJGN0e2pOjoi4a0xhM56M4hMzMIu8HUOVWLXLezd9lkFq0VXN/o2Elvosx88KvaFcHkYwCaGIOD+PAlxcBa+vH4BDueXFnzolz3KoROWChaaDKEnIE/77DIjwQHQm/5I56825a+Y0kFkt2RBB7ltSUf+baZJi3iv2G2xkG+XnY2+eKpJjLTjTKuXNisIsf5hhRQ3byyxTVzb4eRpSpq8SAocoOXoCSOO+3eBKQlF8E3DwQ11k2AZ9uN9tOmPI9gN7Gr6j7mNEa20pbSzUMkZ5nln5YxOB/IwTUkAuTrY=
X-OriginatorOrg: constructor.university
X-MS-Exchange-CrossTenant-Network-Message-Id: 783aecdd-98e1-4175-65e2-08db1fde4fab
X-MS-Exchange-CrossTenant-AuthSource: GVXP190MB1991.EURP190.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Mar 2023 14:06:28.4453 (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: TpejNbCYbQSnppQcMcSnyAUezxkOfDcSftvDYTQl3u1Y8EGIqzfc/CTLP/eUyK7dvSCM/9jtzDbp9Xk9UFQAl4DPC69qZ9MubusF1dgj3+k=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1P190MB0927
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/EOZJ1wh4tPpfpOQOczYpr2d-ZDM>
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 14:06:39 -0000

Thanks for the explanation. I started this thread because I saw
students investing time trying to understand the difference between
the terms DTN and NDT. I then checked the NMRG document and it defines
one term but then occasionally uses both. I am happy with whatever
term native English speakers consider the right term.

And even better would likely be explicit text saying that both terms
exist and that they effectively mean the same and thqt both terms are
used (or can be used) interchangeably. Then readers simply know.

/js

On Wed, Mar 08, 2023 at 01:50:17PM +0000, Christopher Janz wrote:
> Juergen, in your examples, "electric" is an adjective, as is the compound "software-defined" (properly takes a hyphen when used as an adjective). Adjectives precede the nouns they qualify in English. That is invariable: it is precisely the order which indicates what is the noun and what is the qualifier. It's a little awkward if common to use nouns where adjectives belong, but what is certain is that what precedes is the qualifier and what follows is the noun qualified. A "network digital twin" is a digital twin (noun) for or of a network (qualifier). A "digital twin network" is a network ... but the meaning of the qualification "digital twin" is unclear intrinsically. I don't think any English speaker would instinctively interpret DTN as meaning a digital twin of a network. 
> 
> Perhaps the construction "DTx" has been used, but if so, my guess is it has been used by non-native English speakers.
> 
> Not a hill to die on, but since the matter has been raised.
> 
> Chris
> 
> 
> -----Original Message-----
> From: Jürgen Schönwälder <jschoenwaelder@constructor.university> 
> Sent: Wednesday, March 8, 2023 8:15 AM
> To: Cheng Zhou <zhouchengyjy@chinamobile.com>
> Cc: nmrg@irtf.org; 'Diego R. Lopez' <diego.r.lopez@telefonica.com>; Christopher Janz <christopher.janz@huawei.com>
> Subject: Re: [nmrg] network digital twin vs. digital twin network
> 
> 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/>
> 

-- 
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/>