<?xml version="1.0" encoding="US-ASCII"?>
<!-- This is built from a template for a generic Internet Draft. Suggestions for
     improvement welcome - write to Brian Carpenter, brian.e.carpenter @ gmail.com 
     This can be converted using the Web service at http://xml.resource.org/ -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<!-- You want a table of contents -->
<!-- Use symbolic labels for references -->
<!-- This sorts the references -->
<!-- Change to "yes" if someone has disclosed IPR for the draft -->
<!-- This defines the specific filename and version number of your draft (and inserts the appropriate IETF boilerplate -->
<?rfc sortrefs="yes"?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc topblock="yes"?>
<?rfc comments="no"?>
<rfc category="info" docName="draft-irtf-nmrg-network-digital-twin-arch-01"
     ipr="trust200902">
  <front>
    <title abbrev="Digital Twin Network Concept">Digital Twin Network:
    Concepts and Reference Architecture</title>

    <author fullname="Cheng Zhou" initials="C." surname="Zhou">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <code>100053</code>

          <country>China</country>
        </postal>

        <email>zhouchengyjy@chinamobile.com</email>
      </address>
    </author>

    <author fullname="Hongwei Yang" initials="H." surname="Yang">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <code>100053</code>

          <country>China</country>
        </postal>

        <email>yanghongwei@chinamobile.com</email>
      </address>
    </author>

    <author fullname="Xiaodong Duan" initials="X." surname="Duan">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <code>100053</code>

          <country>China</country>
        </postal>

        <email>duanxiaodong@chinamobile.com</email>
      </address>
    </author>

    <author fullname="Diego Lopez" initials="D." surname="Lopez">
      <organization>Telefonica I+D</organization>

      <address>
        <postal>
          <street/>

          <city>Seville</city>

          <country>Spain</country>
        </postal>

        <email>diego.r.lopez@telefonica.com</email>
      </address>
    </author>

    <author fullname="Antonio Pastor" initials="A." surname="Pastor">
      <organization>Telefonica I+D</organization>

      <address>
        <postal>
          <street/>

          <city>Madrid</city>

          <country>Spain</country>
        </postal>

        <email>antonio.pastorperales@telefonica.com</email>
      </address>
    </author>

    <author fullname="Qin Wu" initials="Q." surname="Wu">
      <organization>Huawei</organization>

      <address>
        <postal>
          <street>101 Software Avenue, Yuhua District</street>

          <city>Nanjing</city>

          <region>Jiangsu</region>

          <code>210012</code>

          <country>China</country>
        </postal>

        <email>bill.wu@huawei.com</email>
      </address>
    </author>

    <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
      <organization>Orange</organization>

      <address>
        <postal>
          <street>Rennes 35000</street>

          <country>France</country>
        </postal>

        <email>mohamed.boucadair@orange.com</email>
      </address>
    </author>

    <author fullname="Christian Jacquenet" initials="C." surname="Jacquenet">
      <organization>Orange</organization>

      <address>
        <postal>
          <street>Rennes 35000</street>

          <country>France</country>
        </postal>

        <email>christian.jacquenet@orange.com</email>
      </address>
    </author>

    <!---->

    <date year="2022"/>

    <area>Networking</area>

    <workgroup>Internet Research Task Force</workgroup>

    <keyword>Digtial Twin; Digital Twin Network; IBN; Network
    Management</keyword>

    <abstract>
      <t>Digital Twin technology has been seen as a rapid adoption technology
      in Industry 4.0. The application of Digital Twin technology in the
      networking field is meant to develop various rich network applications
      and realize efficient and cost effective data driven network management
      and accelerate network innovation.</t>

      <t>This document presents an overview of the concepts of Digital Twin
      Network, provides the basic definitions and a reference architecture,
      lists a set of application scenarios, and discusses the benefits and key
      challenges of such technology.</t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <!-- <t>With the advent of technologies such as 5G, Industrial Internet of
      Things, Edge Computing, and Artificial Intelligence,  ICT
      (Information and Communications Technology) and other vertical
      industries (e.g., smart cities, smart manufacturers) are transformed
      dramatically through replacing what is used to be manual processes with
      digital processes.</t> -->

      <t>The fast growth of network scale and the increased demand placed on
      these networks require them to accommodate and adapt dynamically to
      customer needs, implying a significant challenge to network operators.
      Indeed, network operation and maintenance are becoming more complex due
      to higher complexity of the managed networks and the sophisticated
      services they are delivering. As such, providing innovations on network
      technologies, management and operation will be more and more challenging
      due to the high risk of interfering with existing services and the
      higher trial costs if no reliable emulation platforms are available.</t>

      <t>A Digital Twin is the real-time representation of a physical entity
      in the digital world. It has the characteristics of virtual-reality
      interrelation and real-time interaction, iterative operation and process
      optimization, full life-cycle and comprehensive data-driven network
      infrastructure. Currently, digital twin has been widely acknowledged in
      academic publications. See more in <xref target="Concepts"/>.</t>

      <t>A digital twin for networks platform can be built by applying Digital
      Twin technologies to networks and creating a virtual image of physical
      network facilities (called herein, emulation). Basically, the digital
      twin for networks is an expansion platform of network simulation. The
      main difference compared to traditional network management systems is
      the interactive virtual-real mapping and data driven approach to build
      closed-loop network automation. Therefore, a digital twin network
      platform is more than an emulation platform or network simulator.</t>

      <t>Through the real-time data interaction between the physical network
      and its twin network(s), the digital twin network platform might help
      the network designers to achieve more simplification, automatic,
      resilient, and full life-cycle operation and maintenance. More
      specifically, the digital twin network can, thus, be used to develop
      various rich network applications and assess specific behaviors
      (including network transformation) before actual implementation in the
      physical network, tweak the network for better optimized behavior, run
      'what-if' scenarios that cannot be tested and evaluated easily in the
      physical network. In addition, service impact analysis tasks can also be
      facilitated.</t>
    </section>

    <section title="Terminology">
      <section title="Acronyms &amp; Abbreviations">
        <t><list style="hanging">
            <t hangText="IBN:">Intent-Based Networking</t>

            <t hangText="AI">Artificial Intelligence</t>

            <t hangText="CI/CD:">Continuous Integration / Continuous
            Delivery</t>

            <t hangText="ML:">Machine Learning</t>

            <t hangText="OAM:">Operations, Administration, and Maintenance</t>

            <t hangText="PLM:">Product Lifecycle Management</t>
          </list></t>
      </section>

      <section title="Definitions">
        <t>This document makes use of the following terms:<list
            style="hanging">
            <t hangText="Digital Twin: ">a virtual instance of a physical
            system (twin) that is continually updated with the latter's
            performance, maintenance, and health status data throughout the
            physical system's life cycle.</t>

            <t hangText="Digital twin network: ">a digital twin that is used
            in the context of networking. This is also called, digital twin
            for networks. See more in <xref target="def"/>.</t>
          </list></t>
      </section>
    </section>

    <section anchor="Concepts"
             title="Introduction and Concepts of Digital Twin Network">
      <section title="Background of Digital Twin">
        <t>The concept of the "twin" dates to the National Aeronautics and
        Space Administration (NASA) Apollo program in the 1970s, where a
        replica of space vehicles on Earth was built to mirror the condition
        of the equipment during the mission [Rosen2015].</t>

        <t>In 2003, Digital Twin was attributed to John Vickers by Michael
        Grieves in his product lifecycle management (PLM) course as "virtual
        digital representation equivalent to physical products" <xref
        target="Grieves2014"/>. Digital twin can be defined as a virtual
        instance of a physical system (twin) that is continually updated with
        the latter's performance, maintenance, and health status data
        throughout the physical system's life cycle <xref
        target="Madni2019"/>. By providing a living copy of physical system,
        digital twins bring numerous advantages, such as accelerated business
        processes, enhanced productivity, and faster innovation with reduced
        costs. So far, digital twin has been successfully applied in the
        fields of intelligent manufacturing, smart city, or complex system
        operation and maintenance to help with not only object design and
        testing, but also management aspects <xref target="Tao2019"/>.</t>

        <t>Compared with 'digital model' and 'digital shadow', the key
        difference of 'digital twin' is the direction of data between the
        physical and virtual systems <xref target="Fuller2020"/>. Typically,
        when using a digital twin, the (twin) system is generated and then
        synchronized using data flows in both directions between physical and
        digital components, so that control data can be sent, and changes
        between the physical and digital objectives of systems are
        automatically represented. This behavior is unlike a 'digital model'
        or 'digital shadow', which are usually synchronized manually, lacking
        of control data, and might not have a full cycle of data
        integrated.</t>

        <t>At present (2022), there is no unified definition of digital twin
        framework. The industry, scientific research institutions, and
        standards developing organizations are trying to define a general or
        domain-specific framework of digital twin. [Natis-Gartner2017]
        proposed that building a digital twin of a physical entity requires
        four key elements: model, data, monitoring, and uniqueness. [Tao2019]
        proposed a five-dimensional framework of digital twin {PE, VE, SS, DD,
        CN}, in which PE represents physical entity, VE represents virtual
        entity, SS represents service, DD represents twin data, and CN
        represents the connection between various components. [ISO-2021]
        issued a draft standard for digital twin manufacturing system, and
        proposed a reference framework including data collection domain,
        device control domain, digital twin domain, and user domain.</t>
      </section>

      <section title="Digital Twin for Networks">
        <t>Communication networks can provide a solid foundation for
        implementing various 'digital twin' applications. At the same time, in
        the face of increasing business types, scale and complexity, a network
        itself also needs to use digital twin technology to seek better
        solutions beyond physical network. Since 2017, the application of
        digital twin technology in the field of communication networks has
        gradually been researched. Some examples are listed below.</t>

        <t>In academy, [Dong2019] established the digital twin of 5G mobile
        edge computing (MEC) network, used the twin offline to train the
        resource allocation optimization and normalized energy-saving
        algorithm based on reinforcement learning, and then updated the scheme
        to MEC network. [Dai2020] established a digital twin edge network for
        mobile edge computing system, in which a twin edge server is used to
        evaluate the state of entity server, and the twin mobile edge
        computing system provides data for training offloading strategy.
        [Nguyen2021] discusses how to deploy a digital twin for complex 5G
        networks. [Hong2021] presents a digital twin platform towards
        automatic and intelligent management for data center networks, and
        then proposes a simplified the workflows of network service
        management. In addition, international workshops dedicated to digital
        twin in network field have already appeared, such as IEEE DTPI 2021 -
        Digital Twin Network Online Session [DTPI2021], and IEEE NOMS 2022 -
        TNT workshop [TNT2022].</t>

        <t>Although the application of digital twin technology in networking
        has started, the research of digital twin for networks technology is
        still in its infancy. Current applications focus on specific scenarios
        (such as network optimization), where network digital twin is just
        used as a network simulation tool to solve the problem of network
        operation and maintenance. Combined with the characteristics of
        digital twin technology and its application in other industries, this
        document believes that digital twin network can be regarded as an
        indispensable part of the overall network system and provides a
        general architecture involving the whole life cycle of physical
        network in the future, serving the application of network innovative
        technologies such as network planning, construction, maintenance and
        optimization, improving the automation and intelligence level of the
        network.</t>
      </section>

      <section anchor="def" title="Definition of Digital Twin Network">
        <t>So far, there is no standard definition of "digital twin network"
        within the networking industry. This document defines "digital twin
        network" as a virtual representation of the physical network. Such
        virtual representation of the network is meant to be used to analyze,
        diagnose, emulate, and then control the physical network based on
        data, models, and interfaces. To that aim, a real-time and interactive
        mapping is required between the physical network and its virtual twin
        network.</t>

        <t>Referring the characteristics of digital twin in other industries
        and the characteristics of the networking itself, the digital twin
        network should involve four key elements: data, mapping, models and
        interfaces as shown in <xref target="Fig_DTN_Elements"/>.</t>

        <t><figure align="center" anchor="Fig_DTN_Elements"
            title="Key Elements of Digital Twin Network">
            <artwork align="center">
    +-------------+                 +--------------+
    |             |                 |              |
    |  Mapping    |                 |  Interface   |
    |             |                 |              |
    +-------------+-----------------+--------------+
             |                          |
             |    Analyze, Diagnose     |
             |                          |
             | +----------------------+ |
             | | Digital Twin Network | |
             | +----------------------+ |
 +------------+                        +------------+
 |            |   Emulate, Control     |            |
 |   Models   |                        |    Data    |
 |            |------------------------|            |
 +------------+                        +------------+
</artwork>
          </figure><list style="hanging">
            <t hangText="Data:">A digital twin network should maintain
            historical data and/or real time data (configuration data,
            operational state data, topology data, trace data, metric data,
            process data, etc.) about its real-world twin (i.e. physical
            network) that are required by the models to represent and
            understand the states and behaviors of the real-world twin.
            <vspace blankLines="1"/>The data is characterized as the single
            source of "truth" and populated in the data repository, which
            provides timely and accurate data service support for building
            various models.</t>

            <t hangText="Models:">Techniques that involve collecting data from
            one or more sources in the real-world twin and developing a
            comprehensive representation of the data (e.g., system, entity,
            process) using specific models. These models are used as emulation
            and diagnosis basis to provide dynamics and elements on how the
            live physical network operates and generates reasoning data
            utilized for decision-making. <vspace blankLines="1"/>Various
            models such as service models, data models, dataset models, or
            knowledge graph can be used to represent the physical network
            assets and, then, instantiated to serve various network
            applications.</t>

            <t hangText="Interfaces:">Standardized interfaces can ensure the
            interoperability of digital twin network. There are two major
            types of interfaces: <list style="symbols">
                <t>The interface between the digital twin network platform and
                the physical network infrastructure.</t>

                <t>The interface between digital twin network platform and
                applications.</t>
              </list>The former provides real-time data collection and control
            on the physical network. The latter helps in delivering
            application requests to the digital twin network platform and
            exposing the various platform capabilities to applications.</t>

            <t hangText="Mapping:">Used to identify the digital twin and the
            underlying entities and establish a real-time interactive relation
            between the physical network and the twin network or between two
            twin networks. The mapping can be: <list style="symbols">
                <t>One to one (pairing, vertical): Synchronize between a
                physical network and its virtual twin network with continuous
                flows.</t>

                <t>One to many (coupling, horizontal): Synchronize among
                virtual twin networks with occasional data exchange.</t>
              </list>Such mappings provide a good visibility of actual status,
            making the digital twin suitable to analyze and understand what is
            going on in the physical network. It also allows using the digital
            twin to optimize the performance and maintenance of the physical
            network.</t>
          </list></t>

        <t>The digital twin network constructed based on the four core
        technology elements can analyze, diagnose, emulate, and control the
        physical network in its whole life cycle with the help of optimization
        algorithms, management methods, and expert knowledge. One of the
        objectives of such control is to master the digital twin network
        environment and its elements to derive the required system behavior,
        e.g., provide:<list style="symbols">
            <t>repeatability: that is the capacity to replicate network
            conditions on-demand.</t>

            <t>reproducibility: i.e., the ability to replay successions of
            events, possibly under controlled variations.</t>
          </list></t>

        <t>Note: Real-time interaction is not always mandatory for all twins.
        When testing some configuration changes or trying some innovative
        techniques, the digital twins can behave as a simulation platform
        without the need of real time telemetry data. And even in this
        scenario, it is better to have interactive mapping capability so that
        the validated changes can be tested in real network whenever required
        by the testers. In most other cases (e.g., network optimization,
        network fault recovery), real-time interaction between virtual and
        real network is mandatory. This way, digital twin network can help
        achieve the goal of autonomous network or self-driven network.</t>
      </section>
    </section>

    <section anchor="ben" title="Benefits of Digital Twin Network">
      <t>Digital twin network can help enabling closed-loop network management
      across the entire lifecycle, from deployment and emulation, to
      visualized assessment, physical deployment, and continuous verification.
      By doing so, network operators and end-users to some extent, as allowed
      by specific application interfaces, can maintain a global, systemic, and
      consistent view of the network. Also, network operators and/or
      enterprise user can safely exercise the enforcement of network planning
      policies, deployment procedures, etc., without jeopardizing the daily
      operation of the physical network.</t>

      <t>The main difference between digital twin network and simulation
      platform is the use of interactive virtual-real mapping to build
      closed-loop network automation. Simulation platforms are the predecessor
      of the digital twin network, one example of such a simulation platform
      is network simulator [NS-3], which can be seen as a variant of digital
      twin network but with low fidelity and lacking for interactive
      interfaces to the real network. Compared with those classical
      approaches, key benefits of digital twin network can be summarized as
      follows: <list style="format %d)">
          <t>Using real-time data to establish high fidelity twins, the
          effectiveness of network simulation is higher; then the simulation
          cost will be relatively low.</t>

          <t>The impact and risk on running networks is low when automatically
          applying configuration/policy changes after the full analysis and
          required verifications (e.g., service impact analysis) within the
          twin network.</t>

          <t>The faults of the physical network can be automatically captured
          by analyzing real-time data, then the correction strategy can be
          distributed to the physical network elements after conducting
          adequate analysis within the twins to complete the closed-loop
          automatic fault repair.</t>
        </list></t>

      <t>The following subsections further elaborate such benefits in
      details.</t>

      <section anchor="cost" title="Optimized Network Total Cost of Operation">
        <t>Large scale networks are complex to operate. Since there is no
        effective platform for simulation, network optimization designs have
        to be tested on the physical network at the cost of jeopardizing its
        daily operation and possibly degrading the quality of the services
        supported by the network. Such assessment greatly increases network
        operator's Operational Expenditure (OPEX) budgets too.</t>

        <t>With a digital twin network platform, network operators can safely
        emulate candidate optimization solutions before deploying them in the
        physical network. In addition, operator's OPEX on the real physical
        network deployment will be greatly decreased accordingly at the cost
        of the complexity of the assessment and the resources involved.</t>
      </section>

      <section title="Optimized Decision Making">
        <t>Traditional network operation and management mainly focus on
        deploying and managing running services, but hardly support predictive
        maintenance techniques.</t>

        <t>Digital twin network can combine data acquisition, big data
        processing, and AI modeling to assess the status of the network, but
        also to predict future trends, and better organize predictive
        maintenance. The ability to reproduce network behaviors under various
        conditions facilitates the corresponding assessment of the various
        evolution options as often as required.</t>
      </section>

      <section title="Safer Assessment of Innovative Network Capabilities">
        <t>Testing a new feature in an operational network is not only
        complex, but also extremely risky. Service impact analysis is required
        to be adequately achieved prior to effective activation of a new
        feature.</t>

        <t>Digital twin network can greatly help assessing innovative network
        capabilities without jeopardizing the daily operation of the physical
        network. In addition, it helps researchers to explore network
        innovation (e.g., new network protocols, network AI/ML applications)
        efficiently, and network operators to deploy new technologies quickly
        with lower risks. Take AI/ ML application as example, it is a conflict
        between the continuous high reliability requirement (i.e., 99.999%)
        and the slow learning speed or phase-in learning steps of AI/ML
        algorithms. With digital twin network, AI/ML can complete the learning
        and training with the sufficient data before deploying the model in
        the real network. This would encourage more network AI innovations in
        future networks.</t>
      </section>

      <section title="Privacy and Regulatory Compliance">
        <t>The requirements on data confidentiality and privacy on network
        providers increase the complexity of network management, as decisions
        made by computation logics such as an SDN controller may rely upon the
        packet payloads. As a result, the improvement of data-driven
        management requires complementary techniques that can provide a strict
        control based upon security mechanisms to guarantee data privacy
        protection and regulatory compliance. This may range from flow
        identification (using the archetypal five-tuple of addresses, ports
        and protocol) to techniques requiring some degree of payload
        inspection, all of them considered suitable to be associated to an
        individual person, and hence requiring strong protection and/or data
        anonymization mechanisms.</t>

        <t>With strong modeling capability provided by the digital twin
        network, very limited real data (if at all) will be needed to achieve
        similar or even higher level of data-driven intelligent analysis. This
        way, a lower demand of sensitive data will permit to satisfy privacy
        requirements and simplify the use of privacy-preserving techniques for
        data-driven operation.</t>
      </section>

      <section title="Customized Network Operation Training">
        <t>Network architectures can be complex, and their operation requires
        expert personnel. Digital twin network offers an opportunity to train
        staff for customized networks and specific user needs. Two salient
        examples are the application of new network architectures and
        protocols or the use of "cyber-ranges" to train security experts in
        threat detection and mitigation.</t>
      </section>
    </section>

    <section title="Challenges to Build Digital Twin Network">
      <t>According to [Hu2021], the main challenges in building and mantaining
      digital twins can be summarized as the following five aspects: <list
          style="symbols">
          <t>Data acquisition and processing</t>

          <t>High-fidelity modeling</t>

          <t>Real-time, two-way communication between the virtual and the real
          twins</t>

          <t>Unified development platform and tools</t>

          <t>Environmental coupling technologies</t>
        </list></t>

      <t>Compared with other industrial fields, digital twin in networking
      field has its unique characteristics. On one hand, network elements and
      system have higher level of digitalization, which implies that data
      acquisition and virtual-real communication are relatively easy to
      achieve. On the other hand, there are various different type of network
      elements and typologies in the network field; and the network size is
      characterized by the numbers of nodes and links in it but the network
      size growth pace can not meet the service needs, especially in the
      deployment of end to end service&nbsp;which spans across multiple
      administrative domains. So, the construction of a digital twin network
      system needs to consider the following major challenges:<list
          style="hanging">
          <t hangText="Large scale challenge:">A digital twin of large-scale
          networks will significantly increase the complexity of data
          acquisition and storage, the design and implementation of relevant
          models. The requirements of software and hardware of the digital
          twin network system will be even more constraining. Therefore,
          efficient and low cost tools in various fields should be required.
          Take data as an example, massive network data can help achieve more
          accurate models. However, the cost of virtual-real communication and
          data storage becomes extremely expensive, especially in the
          multi-domain data-driven network management case, therefore
          efficient tools on data collection and data compression methods must
          be used.</t>

          <t hangText="Interoperability:">Due to the inconsistency of
          technical implementations and the heterogeneity of vendor adopted
          technologies, it is difficult to establish a unified digital twin
          network system with a common technology in a network domain.
          Therefore, it is needed firstly to propose a unified architecture of
          digital twin network, in which all components and functionalities
          are clear to all stakeholders; then define standardized and unified
          interfaces to connect all network twins via ensuring necessary
          compatibility.</t>

          <t hangText="Data modeling difficulties:">Based on large-scale
          network data, data modeling should not only focus on ensuring the
          accuracy of model functions, but also has to consider the
          flexibility and scalability to compose and extend as required to
          support large scale and multi-purpose applications. Balancing these
          requirements further increases the complexity of building efficient
          and hierarchical functional data models. As an optional solution,
          straightforwardly clone the real network using virtualized resources
          is feasible to build the twin network when the network scale is
          relatively small. However, it will be of unaffordable resource cost
          for larger scales network. In this case, network modeling using
          mathematical abstraction or leveraging the AI algorithms will be
          more suitable solutions.</t>

          <t hangText="Real-time requirements:">Network services normally have
          real-time requirements, the processing of model simulation and
          verification through a digital twin network will introduce the
          service latency. Meanwhile, the real-time requirements will further
          impose performance requirements on the system software and hardware.
          However, given the nature of distributed systems and propagation
          delays, it is challenge to keep network digital twins in sync or
          auto-sync between physical network and digital twin network. Changes
          to the digital object automatically drive changes in the physical
          object can be even challenging. To address these requirements, the
          function and process of the data model need to be based on automated
          processing mechanism under various network application scenarios. On
          the one hand, it is needed to design a simplified process to reduce
          the time cost for tasks in network twin as much as possible; on the
          other hand, it is recommended to define the real-time requirements
          of different applications, and then match the corresponding
          computing resources and suitable solutions as needed to complete the
          task processing in the twin.</t>

          <t hangText="Security risks:">A digital twin network has to
          synchronize all or subset of the data related to involved physical
          networks in real time, which inevitably augments the attack surface,
          with a higher risk of information leakage, in particular. On one
          hand, it is mandatory to design more secure data mechanism
          leveraging legacy data protection methods, as well as innovative
          technologies such as block chain. On the other hand, the system
          design can limit the data (especially raw data) requirement on
          building digital twin network, leveraging innovative modeling
          technologies such as federal learning.</t>
        </list></t>

      <t>In brief, to address the above listed challenges, it is important to
      firstly propose a unified architecture of digital twin network, which
      defines the main functional components and interfaces (<xref
      target="ref"/>). Then, relying upon such an architecture, it is required
      to continue researching on the key enabling technologies including data
      acquisition, data storage, data modeling, interface standardization, and
      security assurance.</t>
    </section>

    <section anchor="ref"
             title="A Reference Architecture of Digital Twin Network">
      <t>Based on the definition of the key digital twin network technology
      elements introduced in <xref target="def"/>, a digital twin network
      architecture is depicted in <xref target="Fig_DTN_Architecture"/>. This
      digital twin network architecture is broken down into three layers:
      Application Layer, Digital Twin Layer, and Physical Network Layer.
      <figure align="center" anchor="Fig_DTN_Architecture"
          title="Reference Architecture of Digital Twin Network">
          <artwork align="center">+---------------------------------------------------------+
|   +-------+   +-------+          +-------+              |
|   | App 1 |   | App 2 |   ...    | App n |   Application|
|   +-------+   +-------+          +-------+              |
+-------------^-------------------+-----------------------+
              |Capability Exposure| Intent Input
              |                   | 
+-------------+-------------------v-----------------------+
|                        Instance of Digital Twin Network |
|  +--------+   +------------------------+   +--------+   |
|  |        |   | Service Mapping Models |   |        |   |
|  |        |   |  +------------------+  |   |        |   |
|  | Data   +---&gt;  |Functional Models |  +---&gt; Digital|   |
|  | Repo-  |   |  +-----+-----^------+  |   | Twin   |   |
|  | sitory |   |        |     |         |   | Network|   |
|  |        |   |  +-----v-----+------+  |   |  Mgmt  |   |
|  |        &lt;---+  |  Basic Models    |  &lt;---+        |   |
|  |        |   |  +------------------+  |   |        |   |
|  +--------+   +------------------------+   +--------+   |
+--------^----------------------------+-------------------+
         |                            |
         | data collection            | control
+--------+----------------------------v-------------------+
|                   Physical Network                      |
|                                                         |
+---------------------------------------------------------+</artwork>
        </figure><list style="hanging">
          <t hangText="Physical Network:">All or subset of network elements in
          the physical network exchange network data and control messages with
          a network digital twin instance, through twin-physical control
          interfaces. The physical network can be a mobile access network, a
          transport network, a mobile core, a backbone, etc. The physical
          network can also be a data center network, a campus enterprise
          network, an industrial Internet of Things, etc. <vspace
          blankLines="1"/>The physical network can span across a single
          network administrative domain or multiple network administrative
          domains. <vspace blankLines="1"/>This document focuses on the IETF
          related physical network such as IP bearer network and datacenter
          network.</t>

          <t hangText="Digital Twin Layer: ">This layer includes three key
          subsystems: Data Repository subsystem, Service Mapping Models
          subsystem, and Digital Twin Network Management subsystem. These key
          subsystems can be placed in one single network administrative domain
          and provide the service to the application (e.g.,SDN controller) in
          other network administrative domain, or lied in every network
          administrative domain and coordinate between each other to provide
          services to the application in the upper layer.<vspace
          blankLines="1"/>One or multiple digital twin network instances can
          be built and maintained:<list style="symbols">
              <t>Data Repository subsystem is responsible for collecting and
              storing various network data for building various models by
              collecting and updating the real-time operational data of
              various network elements through the twin southbound interface,
              and providing data services (e.g., fast retrieval, concurrent
              conflict handling, batch service) and unified interfaces to
              Service Mapping Models subsystem.</t>

              <t>Service Mapping Models complete data modeling, provide data
              model instances for various network applications, and maximizes
              the agility and programmability of network services. The data
              models include two major types: basic and functional models.
              <list style="symbols">
                  <t>Basic models refer to the network element model(s) and
                  network topology model(s) of the network digital twin based
                  on the basic configuration, environment information,
                  operational state, link topology and other information of
                  the network element(s), to complete the real-time accurate
                  characterization of the physical network.</t>

                  <t>Functional models refer to various data models used for
                  network analysis, emulation, diagnosis, prediction,
                  assurance, etc. The functional models can be constructed and
                  expanded by multiple dimensions: by network type, there can
                  be models serving for a single or multiple network domains;
                  by function type, it can be divided into state monitoring,
                  traffic analysis, security exercise, fault diagnosis,
                  quality assurance and other models; by network lifecycle
                  management, it can be divided into planning, construction,
                  maintenance, optimization and operation. Functional models
                  can also be divided into general models and special-purpose
                  models. Specifically, multiple dimensions can be combined to
                  create a data model for more specific application scenarios.
                  <vspace blankLines="1"/>New applications might need new
                  functional models that do not exist yet. If a new model is
                  needed, &lsquo;Service Mapping Models&rsquo; subsystem will
                  be triggered to help creating new models based on data
                  retrieved from &lsquo;Data Repository&rsquo;.</t>
                </list></t>

              <t>Digital Twin Network Management fulfils the management
              function of digital twin network, records the life-cycle
              transactions of the twin entity, monitors the performance and
              resource consumption of the twin entity or even of individual
              models, visualizes and controls various elements of the network
              digital twin, including topology management, model management
              and security management.</t>
            </list>Notes: 'Data collection' and 'change control' are regarded
          as southbound interfaces between virtual and physical network. From
          implementation perspective, they can optionally form a sub-layer or
          sub-system to provide common functionalities of data collection and
          change control, enabled by a specific infrastructure supporting
          bi-directional flows and facilitating data aggregation, action
          translation, pre-processing and ontologies.</t>

          <t hangText="Application Layer: ">Various applications (e.g.,
          Operations, Administration, and Maintenance (OAM)) can effectively
          run over a digital twin network platform to implement either
          conventional or innovative network operations, with low cost and
          less service impact on real networks. Network applications make
          requests that need to be addressed by the digital twin network. Such
          requests are exchanged through a northbound interface, so they are
          applied by service emulation at the appropriate twin
          instance(s).</t>
        </list></t>
    </section>

    <section title="Enabling Technologies to Build Digital Twin Network">
      <t>This section briefly describes several key enabling technologies to
      build digital twin work system, based on the challenges and the
      reference architecture described in above sections. Actually, each
      enabling technology is worth of deep researching respectively and
      separately.</t>

      <section title="Data Collection and Data Services">
        <t>Data collection technology is the foundation of building data
        repository for digital twin network. Target driven mode should be
        adopted for data collection from heterogeneous data sources. The type,
        frequency and method of data collection shall meet the application of
        digital twin network. Whenever building network models for a specific
        network application, the required data can be efficiently obtained
        from the data repository.</t>

        <t>Diverse existing tools and methods (e.g., SNMP, NETCONF, IPFIX,
        Telemetry, INT, etc.) can be used to collect different type of network
        data. And, some innovative new methods (e.g., sketch-based
        measurement) can be used to acquire complex network data such as
        network performance. Also, data transformation and aggregation
        capacity can be used to improve the applicability on network
        modelling. Toward building data repository for a digital twin system,
        data collection tools and methods should be as lightweight as
        possible, so as to reduce the occupation of network equipment
        resources, and meaningful so it can be useful. Several solutions on
        data collection in IETF/IRTF are in working progress, e.g., adaptive
        subscription defined in <xref
        target="I-D.ietf-netconf-adaptive-subscription"/>, efficient data
        collection define in <xref
        target="I-D.zcz-nmrg-digitaltwin-data-collection"/>, and contextual
        information defined in <xref
        target="I-D.claise-opsawg-collected-data-manifest"/>. </t>

        <t>Data repository works to effectively store large-scale and
        heterogeneous network data, as well provide data and services to build
        various network models. So, it is also necessary to study technologies
        regarding data services including fast search, batch-data handling,
        conflict avoidance, data access interfaces, etc.</t>
      </section>

      <section title="Network Modeling">
        <t>The basic network element models and topology models help generate
        virtual twin of the network according to the network element
        configuration, operation data, network topology relationship, link
        state and other network information. Then the operation status can be
        monitored and displayed, and the network configuration change and
        optimization strategy can be pre-verified.</t>

        <t>For small scale network, network simulating tools (e.g., [NS-3],
        [Mininet], etc.) and emulating tools (e.g., [EVE-NG], [GNS-3]) can be
        used to build basic network models. By using the packet processing
        capability of virtual network element, such tools can quickly verify
        the functions of the control plane and data plane. However, this
        modeling method also has many limitations, including high resource
        consumption, poor performance analysis ability, and poor scalability.
        For large scale network, mathematical abstraction methods can be used
        to build basic network models efficiently. Knowledge graph, network
        calculus, and formal verification can be candidate methods. Some
        relevant researches have emerged in recent years, such as [Hong2021],
        [G2-SIGCOMM], and [DNA-2022]. Going forward, how to improve the
        extensibility and accuracy of the models is still a big challenge.</t>

        <t>As an example, the theory of bottleneck structures introduced in
        [G2-SIGCOMM, G2-SIGMETRICS] can be used to construct a mathematical
        model of the network (see also <xref
        target="I-D.giraltyellamraju-alto-bsg-requirements"/> for more info).
        A bottleneck structure is a computational graph that efficiently
        captures the topology, the routing and flow properties of the network.
        The graph embeds the latent relationships that exist between
        bottlenecks and the application flows in a distributed system,
        providing an efficient mathematical framework to compute the ripple
        effects of perturbations (e.g., a flow arriving or departing from the
        system, or the dynamic change in capacity of a wireless link, among
        others). Because these perturbations can be seen as mathematical
        derivatives of the communication system, bottleneck structures can be
        used to compute optimized network configurations, providing a natural
        engineering sandbox for building network models. One of the key
        advantages of bottleneck structures is that they can be used to
        compute (symbolically or numerically) key performance indicators of
        the network (e.g., expected flow throughput, projected flow completion
        time, etc.) without the need to use computationally intensive
        simulators. This capability can be especially useful when building a
        digital twin or a large-scale network, potentially saving orders or
        magnitude in computational resources in comparison to simulation or
        emulation-based approaches.</t>

        <t>The functional model aims to realize the dynamic evolution of
        network performance evaluation and intelligent decision-making. Data
        driven AI/ML algorithm will play a great role in building complex
        network functional models. As a research hotspot in recent years, many
        successfully cases have been demonstrated, such as [RouteNet],
        [MimicNet], etc. In the future, in addition to improving the
        generalization ability and interpretability of AI models, we also need
        to focus on how to improve the real-time and interactivity of model
        reasoning based on data and control in network digital twin layer.</t>
      </section>

      <section title="Network Visualization">
        <t>It is the internal requirement of the digital twin network system
        to use network visibility technology to visually present the data and
        model in the network twin with high fidelity and intuitively reflect
        the interactive mapping between the physical network entity and the
        network twin.&nbsp;Network Visibility technology can help users
        understand the internal structure of the network, and also help mine
        valuable information hidden in the network.</t>

        <t>Network Visibility can use algorithms such as hierarchical layout,
        heuristic layout or force oriented layout (or a combination of several
        algorithms) for topology layout.&nbsp; And the related topology data
        can be acquired using solutions provided in <xref target="RFC8345"/>,
        <xref target="RFC8346"/>, <xref target="RFC8944"/>, etc. Meanwhile,
        digital twin network system can select different interaction methods
        or combinations of interaction methods to realize the visual dynamic
        interaction mapping of virtual and real networks. The data query
        technology such as SPARQL can be used to express queries across
        diverse data sources, whether the data is stored natively as RDF or
        viewed as RDF via middleware.</t>
      </section>

      <section title="Interfaces">
        <t>Based on the reference architecture, there are three types of
        interfaces on building a digital twin network system.<list
            style="format %d)">
            <t>Southbound interfaces are twin interfaces between the physical
            network and its twin entity. They are responsible for information
            exchange between physical network and network digital twin. The
            candidate interfaces can be SNMP, NetConf, etc.</t>

            <t>Northbound interfaces are Application-facing interfaces between
            the network digital twin and applications. They are responsible
            for information exchange between network digital twin and network
            applications. The lightweight and extensible [RESTFul] interface
            can be the candidate northbound interface.</t>

            <t>Internal interfaces are within network digital twin layer. They
            are responsible for information exchange between the three
            subsystems: Data Repository, Service Mapping Models, and Digital
            Twin Network Management. These interfaces should be of high-speed,
            high-efficiency and high-concurrency. The candidate interfaces or
            protocols can be XMPP (defined in <xref target="RFC7622"/>), and
            HTTP/3.0 (defined in <xref target="RFC9114"/>).</t>
          </list></t>

        <t>All interfaces are recommended to be open and standardized so as to
        help avoid either hardware or software vendor lock, and achieve
        inter-operability. Besides the interfaces list above, some new
        interfaces or protocols can be created to better serve digital twin
        network system.</t>
      </section>
    </section>

    <section title="Interaction with IBN">
      <t>Implementing Intent-Based Networking (IBN) is an innovative
      technology for life-cycle network management. Future networks will be
      possibly Intent-based, which means that users can input their abstract
      'intent' to the network, instead of detailed policies or configurations
      on the network devices. <xref
      target="I-D.irtf-nmrg-ibn-concepts-definitions"/> clarifies the concept
      of "Intent" and provides an overview of IBN functionalities. The key
      characteristic of an IBN system is that user intent can be assured
      automatically via continuously adjusting the policies and validating the
      real-time situation.</t>

      <t>IBN can be envisaged in a digital twin network context to show how
      digital twin network improves the efficiency of deploying network
      innovation. To lower the impact on real networks, several rounds of
      adjustment and validation can be emulated on the digital twin network
      platform instead of directly on physical network. Therefore, digital
      twin network can be an important enabler platform to implement IBN
      systems and speed up their deployment.</t>
    </section>

    <section title="Sample Application Scenarios">
      <t>Digital twin network can be applied to solve different problems in
      network management and operation.</t>

      <section title="Human Training">
        <t>The usual approach to network OAM with procedures applied by humans
        is open to errors in all these procedures, with impact in network
        availability and resilience. Response procedures and actions for most
        relevant operational requests and incidents are commonly defined to
        reduce errors to a minimum. The progressive automation of these
        procedures, such as predictive control or closed-loop management,
        reduce the faults and response time, but still there is the need of a
        human-in-the-loop for multiples actions. These processes are not
        intuitive and require training to learn how to respond.</t>

        <t>The use of digital twin network for this purpose in different
        network management activities will improve the operators performance.
        One common example is cybersecurity incident handling, where
        "cyber-range" exercises are executed periodically to train security
        practitioners. Digital twin network will offer realistic environments,
        fitted to the real production networks.</t>
      </section>

      <section title="Machine Learning Training">
        <t>Machine Learning requires data and their context to be available in
        order to apply it. A common approach in the network management
        environment has been to simulate or import data in a specific
        environment (the ML developer lab), where they are used to train the
        selected model, while later, when the model is deployed in production,
        re-train or adjust to the production environment context. This demands
        a specific adaption period.</t>

        <t>Digital twin network simplifies the complete ML lifecycle
        development by providing a realistic environment, including network
        topologies, to generate the data required in a well-aligned context.
        Dataset generated belongs to the digital twin network and not to the
        production network, allowing information access by third parties,
        without impacting data privacy.</t>
      </section>

      <section title="DevOps-Oriented Certification">
        <t>The potential application of CI/CD models network management
        operations increases the risk associated to deployment of non-
        validated updates, what conflicts with the goal of the certification
        requirements applied by network service providers. A solution for
        addressing these certification requirements is to verify the specific
        impacts of updates on service assurance and SLAs using a digital twin
        network environment replicating the network particularities, as a
        previous step to production release.</t>

        <t>Digital twin network control functional block supports such dynamic
        mechanisms required by DevOps procedures.</t>
      </section>

      <section title="Network Fuzzing">
        <t>Network management dependency on programmability increases systems
        complexity. The behavior of new protocol stacks, API parameters, and
        interactions among complex software components are examples that imply
        higher risk to errors or vulnerabilities in software and
        configuration.</t>

        <t>Digital twin network allows to apply fuzzing testing techniques on
        a twin network environment, with interactions and conditions similar
        to the production network, permitting to identify and solve
        vulnerabilities, bugs and zero-days attacks before production
        delivery.</t>
      </section>
    </section>

    <section title="Research Perspectives: A Summary">
      <t>Research on digital twin network has just started. This document
      presents an overview of the digital twin network concepts and reference
      architecture. Looking forward, further elaboration on digital twin
      network scenarios, requirements, architecture, and key enabling
      technologies should be investigated by the industry, so as to accelerate
      the implementation and deployment of digital twin network.</t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>This document describes concepts and definitions of digital twin
      network. As such, the following security considerations remain high
      level, i.e., in the form of principles, guidelines or requirements.</t>

      <t>Security considerations of the digital twin network include:<list
          style="symbols">
          <t>Secure the digital twin system itself.</t>

          <t>Data privacy protection.</t>
        </list></t>

      <t>Securing the digital twin network system aims at making the digital
      twin system operationally secure by implementing security mechanisms and
      applying security best practices. In the context of digital twin
      network, such mechanisms and practices may consist in data verification
      and model validation, mapping operations between physical network and
      digital counterpart network by authenticated and authorized users
      only.</t>

      <t>Synchronizing the data between the physical and the digital twin
      networks may increase the risk of sensitive data and information
      leakage. Strict control and security mechanisms must be provided and
      enabled to prevent data leaks.</t>
    </section>

    <section title="Acknowledgements">
      <t>Many thanks to the NMRG participants for their comments and reviews.
      Thanks to Daniel King, Quifang Ma, Laurent Ciavaglia,
      J&eacute;r&ocirc;me Fran&ccedil;ois, Jordi Pailliss&eacute;, Luis Miguel
      Contreras Murillo, Alexander Clemm, Qiao Xiang, Ramin Sadre, Pedro
      Martinez-Julia, Wei Wang, Zongpeng Du, and Peng Liu.</t>

      <t>Diego Lopez and Antonio Pastor were partly supported by the European
      Commission under Horizon 2020 grant agreement no. 833685 (SPIDER), and
      grant agreement no. 871808 (INSPIRE-5Gplus).</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document has no requests to IANA.</t>
    </section>

    <section title="Open issues">
      <t><list style="symbols">
          <t>Some technologies (e.g. Network connectivity, Real-time data
          communication, Collaboration management, conflict detection and
          resolution, etc.) recently discussed in the IRTF/IETF should be
          described.</t>

          <t>In section of 'Sample Application Scenarios', to dig deeper into
          one or two use cases.</t>

          <t>On the research side, the idea behind digital twin networks is
          reminiscent of earlier work from the 1990s that should be
          referenced/acknowledged. Examples include the Shadow MIB concept,
          Inductive Modeling Technique, etc.</t>
        </list></t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.7622"?>

      <?rfc include="reference.RFC.8345"?>

      <?rfc include="reference.RFC.8346"?>

      <?rfc include="reference.RFC.8944"?>

      <?rfc include="reference.RFC.9114"?>
    </references>

    <references title="Informative References">
      <?rfc include="reference.I-D.irtf-nmrg-ibn-concepts-definitions"?>

      <?rfc include="reference.I-D.zcz-nmrg-digitaltwin-data-collection"?>

      <?rfc include="reference.I-D.ietf-netconf-adaptive-subscription"?>

      <?rfc include="reference.I-D.giraltyellamraju-alto-bsg-requirements"?>

      <?rfc include="reference.I-D.claise-opsawg-collected-data-manifest"?>

      <reference anchor="Tao2019">
        <front>
          <title>Digital Twin in Industry: State-of-the-Art. IEEE Transactions
          on Industrial Informatics, vol. 15, no. 4.</title>

          <author fullname="Fei Tao" initials="F. Tao" surname="Tao">
            <organization/>
          </author>

          <author fullname="He Zhang" initials="H. Zhang" surname="Zhang">
            <organization/>
          </author>

          <author fullname="Ang Liu" initials="A. Liu" surname="Liu">
            <organization/>
          </author>

          <author fullname="A. Y. C. Nee" initials="A. Y. C. Nee"
                  surname="Nee">
            <organization/>
          </author>

          <date month="April" year="2019"/>
        </front>
      </reference>

      <reference anchor="Roson2015">
        <front>
          <title>About the importance of autonomy and DTs for the future of
          manufacturing. IFAC-Papersonline, Vol. 48, pp. 567-572.</title>

          <author fullname="R. Rosen" initials="R. Rosen" surname="Rosen">
            <organization/>
          </author>

          <author fullname="G. Von Wichert" initials="G. Von Wichert"
                  surname="Wichert">
            <organization/>
          </author>

          <author fullname="G. Lo" initials="G. Lo" surname="Lo">
            <organization/>
          </author>

          <author fullname="K.D. Bettenhausen" initials="K.D. Bettenhausen"
                  surname="Bettenhausen">
            <organization/>
          </author>

          <date year="2015"/>
        </front>
      </reference>

      <reference anchor="Grieves2014"
                 target="https://www.3ds.com/fileadmin/PRODUCTS-SERVICES/DELMIA/PDF/Whitepaper/DELMIA-APRISO-Digital-Twin-Whitepaper.pdf">
        <front>
          <title>Digital twin: Manufacturing excellence through virtual
          factory replication</title>

          <author fullname="Michael Grieves" initials="M. Grieves"
                  surname="Grieves">
            <organization/>
          </author>

          <date year="2003"/>
        </front>
      </reference>

      <reference anchor="Madni2019">
        <front>
          <title>Leveraging digital twin technology in model-based systems
          engineering. Systems, vol. 7, no. 1, p. 7</title>

          <author fullname="A. Madni" initials="A. Madni" surname="Madni">
            <organization/>
          </author>

          <author fullname="C. Madni" initials="C. Madni" surname="Madni">
            <organization/>
          </author>

          <author fullname="S. Lucero" initials="S. Lucero" surname="Lucero">
            <organization/>
          </author>

          <date month="Jan" year="2019"/>
        </front>
      </reference>

      <reference anchor="Fuller2020">
        <front>
          <title>Digital Twin: Enabling Technologies, Challenges and Open
          Research," in IEEE Access, vol. 8, pp. 108952-108971</title>

          <author fullname="A. Fuller" initials="A. Fuller" surname="Fuller">
            <organization/>
          </author>

          <author fullname="Z. Fan" initials="Z" surname="Fan">
            <organization/>
          </author>

          <author fullname="C. Day">
            <organization/>
          </author>

          <author fullname="C. Barlow">
            <organization/>
          </author>

          <date year="2020"/>
        </front>
      </reference>

      <reference anchor="Hong2021">
        <front>
          <title>NetGraph: An Intelligent Operated Digital Twin Platform for
          Data Center Networks. In ACM SIGCOMM 2021 Workshop on
          Network-Application Integration (NAI' 21), Virtual Event, USA. ACM,
          New York, NY, USA</title>

          <author fullname="H.Hong" initials="H." surname="Hong">
            <organization/>
          </author>

          <author fullname="Q. Wu" initials="Q." surname="Wu">
            <organization/>
          </author>

          <author fullname="F. Dong">
            <organization/>
          </author>

          <author fullname="W. Song">
            <organization/>
          </author>

          <author fullname="R. Sun">
            <organization/>
          </author>

          <author fullname="T. Han">
            <organization/>
          </author>

          <author fullname="C. Zhou">
            <organization/>
          </author>

          <author fullname="H. Yang">
            <organization/>
          </author>

          <date year="2021"/>
        </front>
      </reference>

      <reference anchor="Natis-Gartner2017">
        <front>
          <title>Innovation insight for digital twins - driving better
          IoT-fueled decisions.
          https://www.gartner.com/en/documents/3645341</title>

          <author fullname="Y. Natis" initials="Y. Natis" surname="Natis">
            <organization/>
          </author>

          <author fullname="A. Velosa" initials="A. Velosa" surname="Velosa">
            <organization/>
          </author>

          <author fullname="W. R. Schulte" initials="W. R. Schulte"
                  surname="Schulte">
            <organization/>
          </author>

          <date year="2017"/>
        </front>
      </reference>

      <reference anchor="ISO-2021">
        <front>
          <title>Digital Twin manufacturing framework - Part 2: Reference
          architecture: ISO/CD 23247-2.
          https://www.iso.org/standard/78743.html</title>

          <author fullname="ISO">
            <organization>ISO</organization>
          </author>

          <date year="2021"/>
        </front>
      </reference>

      <reference anchor="NS-3">
        <front>
          <title>Network Simulator, NS-3. https://www.nsnam.org/</title>

          <author>
            <organization/>
          </author>

          <date year=" "/>
        </front>
      </reference>

      <reference anchor="DTPI2021">
        <front>
          <title>IEEE International Conference on Digital Twins and Parallel
          Intelligence - Digital Twin Network Session,
          https://www.dtpi.org/video/10</title>

          <author>
            <organization/>
          </author>

          <date month="July" year="2021"/>
        </front>
      </reference>

      <reference anchor="TNT2022">
        <front>
          <title>IEEE International workshop on Technologies for Network
          Twins, https://sites.google.com/view/tnt-2022/</title>

          <author>
            <organization/>
          </author>

          <date year="2022"/>
        </front>
      </reference>

      <reference anchor="Hu2021">
        <front>
          <title>Digital twin: a state-of-the-art review of its enabling
          technologies, applications and challenges. Journal of Intelligent
          Manufacturing and Special Equipment, Vol. 2 No. 1, pp. 1-34</title>

          <author fullname="W. Hu">
            <organization/>
          </author>

          <author fullname="T. Zhang">
            <organization/>
          </author>

          <author fullname="X. Deng">
            <organization/>
          </author>

          <author fullname="Z. Liu">
            <organization/>
          </author>

          <author fullname="J. Tan">
            <organization/>
          </author>

          <date year="2021"/>
        </front>
      </reference>

      <reference anchor="Dong2019">
        <front>
          <title>Deep Learning for Hybrid 5G Services in Mobile Edge Computing
          Systems: Learn from a Digital Twin. IEEE Transactions on Wireless
          Communications,vol. 18, no. 10</title>

          <author fullname="R. Dong" initials="R. Dong" surname="Dong">
            <organization/>
          </author>

          <author fullname="C. She" initials="C. She" surname="She">
            <organization/>
          </author>

          <author fullname="W. Hardjawana" initials="W. Hardjawana"
                  surname="HardjawanaLiu">
            <organization/>
          </author>

          <author fullname="Y. Li" initials="Y. Li" surname="Li">
            <organization/>
          </author>

          <author fullname="B. Vucetic" initials="B. Vucetic"
                  surname="Vucetic">
            <organization/>
          </author>

          <date month="July" year="2019"/>
        </front>
      </reference>

      <reference anchor="Dai2020">
        <front>
          <title>Deep Reinforcement Learning for Stochastic Computation
          Offloading in Digital Twin Networks. IEEE Transactions on Industrial
          Informatics, vol. 17, no. 17</title>

          <author fullname="Y. Dai" initials="Y. Dai" surname="Dai">
            <organization/>
          </author>

          <author fullname="K. Zhang" initials="K. Zhang" surname="Zhang">
            <organization/>
          </author>

          <author fullname="S. Maharjan" initials="S. Maharjan"
                  surname="Maharjan">
            <organization/>
          </author>

          <author fullname="Yan Zhang" initials="Yan Zhang" surname="Zhang">
            <organization/>
          </author>

          <date month="August" year="2020"/>
        </front>
      </reference>

      <reference anchor="Nguyen2021">
        <front>
          <title>Digital Twin for 5G and Beyond. IEEE Communications Magazine,
          vol. 59, no. 2</title>

          <author fullname="H. X. Nguyen" initials="H. X. Nguyen"
                  surname="Nguyen">
            <organization/>
          </author>

          <author fullname="R. Trestian" initials="R. Trestian"
                  surname="Trestian">
            <organization/>
          </author>

          <author fullname="D. To" initials="D. To" surname="To">
            <organization/>
          </author>

          <author fullname="M. Tatipamula" initials="M. Tatipamula"
                  surname="Tatipamula">
            <organization/>
          </author>

          <date month="February " year="2021"/>
        </front>
      </reference>

      <reference anchor="G2-SIGCOMM">
        <front>
          <title>Designing data center networks using bottleneck structures",
          ACM SIGCOMM</title>

          <author fullname="J. Ros-Giralt" initials="J. Ros-Giralt"
                  surname="Ros-Giralt">
            <organization/>
          </author>

          <author fullname="N. Amsel" initials="N. Amsel" surname="Amsel">
            <organization/>
          </author>

          <author fullname="S. Yellamraju" initials="S. Yellamraju"
                  surname="Yellamraju">
            <organization/>
          </author>

          <author fullname="J. Ezick" initials="J. Ezick" surname="Ezick">
            <organization/>
          </author>

          <author fullname="R. Lethin" initials="R. Lethin" surname="Lethin">
            <organization/>
          </author>

          <author fullname="Y. Jiang" initials="Y. Jiang" surname="Jiang">
            <organization/>
          </author>

          <author fullname="A. Feng" initials="A. Feng" surname="Feng">
            <organization/>
          </author>

          <author fullname="L. Tassiulas" initials="L. Tassiulas"
                  surname="Tassiulas">
            <organization/>
          </author>

          <author fullname="Z. Wu" initials="Z. Wu" surname="Wu">
            <organization/>
          </author>

          <author fullname="K. Bergman" initials="K, Bergman"
                  surname="Bergman">
            <organization/>
          </author>

          <date month="August" year="2021"/>
        </front>
      </reference>

      <reference anchor="G2-SIGMETRICS">
        <front>
          <title>On the Bottleneck Structure of Congestion-Controlled
          Networks, ACM SIGMETRICS</title>

          <author fullname="J. Ros-Giralt" initials="J. Ros-Giralt"
                  surname="Ros-Giralt">
            <organization/>
          </author>

          <author fullname="A. Bohara" initials="A. Bohara" surname="Bohara">
            <organization/>
          </author>

          <author fullname="S. Yellamraju" initials="S. Yellamraju"
                  surname="Yellamraju">
            <organization/>
          </author>

          <author fullname="H. Langston" initials="H. Langston"
                  surname="Langston">
            <organization/>
          </author>

          <author fullname="R. Lethin" initials="R. Lethin" surname="Lethin">
            <organization/>
          </author>

          <author fullname="Y. Jiang" initials="Y. Jiang" surname="Jiang">
            <organization/>
          </author>

          <author fullname="L. Tassiulas" initials="L. Tassiulas"
                  surname="Tassiulas">
            <organization/>
          </author>

          <author fullname="J. Li" initials="J. Li" surname="Li">
            <organization/>
          </author>

          <author fullname="Y. Tan" initials="Y. Tan" surname="Tan">
            <organization/>
          </author>

          <author fullname="M. Veeraraghavan" initials="M. Veeraraghavan"
                  surname="Veeraraghavan">
            <organization/>
          </author>

          <date month="December" year="2019"/>
        </front>
      </reference>

      <reference anchor="DNA-2022">
        <front>
          <title>Differential Network Analysis, USENIX Symposium on Networked
          Systems Design and Implementation (NSDI 22)</title>

          <author fullname="P. Zhang" initials="P. Zhang" surname="Zhang">
            <organization/>
          </author>

          <author fullname="A. Gember-Jacobson" initials="A. Gember-Jacobson"
                  surname="Gember-Jacobson">
            <organization/>
          </author>

          <author fullname="Y. Zuo" initials="Y. Zuo" surname="Zuo">
            <organization/>
          </author>

          <author fullname="Y. Huang" initials="Y  Huang" surname="Huang">
            <organization/>
          </author>

          <author fullname="X. Liu" initials="X. Liu" surname="Liu">
            <organization/>
          </author>

          <author fullname="H. Li" initials="H. Li" surname="Li">
            <organization/>
          </author>

          <date month="April" year="2022"/>
        </front>
      </reference>

      <reference anchor="RouteNet">
        <front>
          <title>RouteNet: Leveraging Graph Neural Networks for network
          modeling and optimization in SDN. IEEE Journal on Selected Areas in
          Communication (JSAC), vol. 38, no. 10</title>

          <author fullname="K. Rusek" initials="K. Rusek" surname="Rusek">
            <organization/>
          </author>

          <author fullname="J. Su&aacute;rez-Varela"
                  initials="J. Su&aacute;rez-Varela"
                  surname="Su&aacute;rez-Varela">
            <organization/>
          </author>

          <author fullname="P. Almasan" initials="P. Almasan"
                  surname="Almasan">
            <organization/>
          </author>

          <author fullname="P. Barlet-Ros" initials="P. Barlet-Ros"
                  surname="Barlet-Ros">
            <organization/>
          </author>

          <author fullname="A. Cabellos-Aparicio"
                  initials="A. Cabellos-Aparicio" surname="Cabellos-Aparicio">
            <organization/>
          </author>

          <date month="October" year="2020"/>
        </front>
      </reference>

      <reference anchor="MimicNet">
        <front>
          <title>MimicNet: Fast Performance Estimates for Data Center Networks
          with Machine Learning. In ACM SIGCOMM 2021 Conference (SIGCOMM
          &rsquo;21).</title>

          <author fullname="Q. Zhang" initials="Q. Zhang" surname="Zhang">
            <organization/>
          </author>

          <author fullname="K. K.W. NG" initials="K. K.W. NG" surname="NG">
            <organization/>
          </author>

          <author fullname="C. W. Kazer" initials="C. W. Kazer"
                  surname="Kazer">
            <organization/>
          </author>

          <author fullname="S. Yan" initials="S. Yan" surname="Yan">
            <organization/>
          </author>

          <author fullname="J. Sedoc" initials="J. Sedoc" surname="Sedoc">
            <organization/>
          </author>

          <author fullname="V. Liu" initials="V. Liu" surname="Liu">
            <organization/>
          </author>

          <date month="August" year="2021"/>
        </front>
      </reference>

      <reference anchor="RESTFul">
        <front>
          <title>RESTful Web APIs. O'Reilly Media, Inc.</title>

          <author fullname="L. Richardson" initials="L. Richardson"
                  surname="Richardson">
            <organization/>
          </author>

          <author fullname="M. Amundsen" initials="M. Amundsen"
                  surname="Amundsen">
            <organization/>
          </author>

          <date year=" 2013"/>
        </front>
      </reference>

      <reference anchor="Mininet">
        <front>
          <title>Mninet: An Instant Virtual Network on your Laptop,
          http://mininet.org/</title>

          <author>
            <organization/>
          </author>

          <date year=" "/>
        </front>
      </reference>

      <reference anchor="EVE-NG">
        <front>
          <title>Emulated Virtual Environment Next Generation, EVE-NG.
          https://www.eve-ng.net/</title>

          <author>
            <organization/>
          </author>

          <date year=" "/>
        </front>
      </reference>

      <reference anchor="GNS3">
        <front>
          <title>Graphical Network Simulator-3, GNS3.
          https://www.gns3.com/</title>

          <author>
            <organization/>
          </author>

          <date year=" "/>
        </front>
      </reference>
    </references>

    <section title="Change Logs">
      <t>v06 - v07: Addressed reviewer&rsquo;s comments from adoption call,
      including below major changes.<list style="symbols">
          <t>Resequenced the sections via adding more subsections on concepts
          of digital twin network, removing the &lsquo;Requirements
          Language&rsquo; section, and moving ahead the
          &lsquo;Challenges&rsquo; section.</t>

          <t>Cited more papers, or industrial information on digital twin
          concepts and digital twin for networks.</t>

          <t>Added more information on describing the challenges and key
          characteristics digital twin network.</t>

          <t>Removed previous open issue on investigating related digital twin
          network work and identify the differences and commonalities, and
          added several new open issues for future study.</t>

          <t>Other editorial changes.</t>
        </list></t>

      <t>v05 - v06: Addressed comments form meeting and maillist, to request
      adoptoin call. <list style="symbols">
          <t>Remove acronym DTN to avoid conflict with 'Delay Tolerant
          Network';</t>

          <t>Elaborate the descriptoin of Digital Twin Network architecture
          that supports multiple instances;</t>

          <t>Other Editorial changes.</t>
        </list></t>

      <t>04 - v05<list style="symbols">
          <t>Clarify the difference between digital twin network platform and
          traditional network management system;</t>

          <t>Add more references of researches on applying digital twin to
          network field;</t>

          <t>Clarify the benefit of 'Privacy and Regulatory Compliance';</t>

          <t>Refine the description of reference architecture;</t>

          <t>Other Editorial changes.</t>
        </list></t>

      <t>v03 - v04<list style="symbols">
          <t>Update data definition and models definitions to clarify their
          difference.</t>

          <t>Remove the orchestration element and consolidated into control
          functionality building block in the digital twin network.</t>

          <t>Clarify the mapping relation (one to one, and one to many) in the
          mapping definition.</t>

          <t>Add explanation text for continuous verification.</t>
        </list></t>

      <t>v02 - v03<list style="symbols">
          <t>Split interaction with IBN part as a separate section.</t>

          <t>Fill security section;</t>

          <t>Clarify the motivation in the introduction section;</t>

          <t>Use new boilerplate for requirements language section;</t>

          <t>Key elements definition update.</t>

          <t>Other editorial changes.</t>

          <t>Add open issues section.</t>

          <t>Add section on application scenarios.</t>
        </list></t>
    </section>
  </back>
</rfc>
