<?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-yang-nmrg-data-transfer-intent-01"
     ipr="trust200902">
  <front>
    <title abbrev="Intent-Based Networking">Data transmission intent over WAN
    - one of IBN use cases</title>

    <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="Junjie Wang" initials="J." surname="Wang">
      <organization>Centec</organization>

      <address>
        <postal>
          <street/>

          <city>Suzhou</city>

          <code>215000</code>

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

        <email>wangjj@centecnetworks.com</email>
      </address>
    </author>

    <date day="9" month="July" year="2023"/>

    <area>Networking</area>

    <workgroup>Internet Research Task Force</workgroup>

    <keyword>Intent-based management; WAN data transmission ; Intent-based
    network system</keyword>

    <abstract>
      <t>With the advent of the digital era, there are more and more scenarios
      such as data off-site AI training, data off-site cloud, and the demand
      for big data transmission in the WAN is increasing. WAN data
      transmission involves throughput, delay, packet loss, security and other
      performance indicators, as well as cost investment. Users have been
      exploring how to achieve the best performance of data transmission at
      the lowest cost. This paper implements high quality WAN data
      transmission based on IBNS.</t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>An increasing number of scenarios require WAN to transmit massive
      data, such as:</t>

      <t>1) Some applications of data production, training, reasoning deployed
      in a different position, need cloud, edge, huge amounts of data
      transmission among multiple data centers;</t>

      <t>2) Collaborative computing between multiple data centers:</t>

      <t>3) Data backup between multiple data centers;</t>

      <t>4) loud users huge amounts of data;</t>

      <t>The optimal transmission strategy is calculated based on the
      performance requirements of user data transmission and the upper cost
      input, and then translated into the specific configuration of the device
      to realize high-quality WAN data transmission based on the intentional
      network.</t>
    </section>

    <section title="Conventions Used in This Document">
      <section title="Terminology">
        <t>NTP Network Time Protocol</t>

        <t>PTP Precision Time Protocol</t>

        <t>DTN Digital Twin Network</t>
      </section>

      <section title="Requirements Language">
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
        "OPTIONAL" in this document are to be interpreted as described in BCP
        14<xref target="RFC2119"/><xref target="RFC8174"/> when, and only
        when, they appear in all capitals, as shown here.</t>
      </section>
    </section>

    <section title="Wan data transmission intent">
      <t>As defined in [RFC9315]: "Intent is a declaration of operational
      goals that a network is supposed to meet and outcomes that the network
      is supposed to deliver, without specifying how to achieve or how to
      implement them. Those goals and outcomes are defined in a manner that is
      purely declarative - they specify what to accomplish, not how to achieve
      it."</t>

      <t>Users have different performance requirements for data transmission,
      such as throughput, delay, packet loss rate, and security level, based
      on the data type and cost upper limit. These requirements are not
      optimal at the same time, or all requirements to be optimal will lead to
      very high costs, causing users to be unable to afford. When a user
      enters the data transmission intention in the IBNS, the user provides
      specific performance requirements and cost ceilings. The system
      calculates the configuration policy based on the counter requirements,
      cost upper limit, and network status. Then, you can translate the
      configurations of specific devices (including network devices,
      firewalls, and storage servers) based on the configuration policies.</t>

      <t>Data transmission configuration policies include the selection and
      parameter configuration of WAN congestion control, packet loss recovery,
      data encryption, packet loss retransmission, and other technical
      solutions.</t>

      <t>Data transmission cost is mainly dedicated line rental cost, which is
      related to bandwidth, service time, distance and other parameters.</t>
    </section>

    <section title="Intent lifecycle">
      <t>According to the intent lifecycle in [RFC9315],after a user enters
      data transmission requirements, the IBNS processes the user's intent to
      meet the requirements.</t>

      <t>(1) Input data transmission intention, clarify performance
      requirements, upper limit of cost input, etc.</t>

      <t>(2) The system detects the current network performance in real
      time,and configuration strategy obtained through comprehensive
      calculation.</t>

      <t>(3) Translate the configuration strategy into specific device
      configuration. Equipment includes network equipment and IT
      equipment.</t>

      <t>(4) Detect the performance indicators of data transmission in real
      time and predict the cost of completing data transmission.</t>

      <t>(5) Real-time calculation of whether the configuration strategy needs
      to be adjusted according to the detected network performance, data
      transmission performance and cost input.Update device configuration
      while changing configuration policy.</t>

      <t>(6) Real-time analysis of cost input and data transmission
      performance indicators, and feedback to users.</t>

      <figure align="center" title="Figure 1: Intent lifecycle">
        <artwork align="left" alt="" name="" pn="section-3" type="">User Space : Translation / IBS : Network Ops : Space : Space (1) : (2) : (3) +----------+ : +----------+ +-----------+ : +-----------+ Fulfill |recognize/+---&gt; |translate/+--^+ learn/ +--^+ configure/| |generate | | | | plan/ | | pro^ision | |intent +^--+ | refine | | render | : | | +----^-----+ : +----------+ +-----^-----+ : +------+----+ | : | : | .............|................................|................|..... | : +--------+ : ^ | : |&gt;alidate| : +-----+----+ | : |----^---+ &lt;----+ monitor/ | Assure +---+---+ : +---------+ +---------+ : | obser^e/ | |report | &lt;---+ |abstract +^---+ analyze | &lt;----+ | +-------+ : +---------+ |aggregate| : +----------+ : +---------+ : (6) (5) (4)</artwork>
      </figure>
    </section>

    <section title="Conclusion">
      <t>This is a usecase of IBNS, which uses IBNS to realize wide-area data
      transmission. After the user enters the performance parameters and the
      upper limit of the cost input, IBNS will automatically select the
      optimal configuration strategy, and can achieve high-quality data
      transmission services without manual participation.</t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>The security guarantee in data transmission is very important,
      especially in the transmission of customer privacy data over the WAN
      (Wide Area Network), which requires high-level data security encryption
      technology. Different levels of security encryption technology have
      different functional requirements for the data sending devices, network
      devices, and data receiving devices, and also have an impact on
      transmission efficiency. For users with different levels of data
      security needs, it is necessary to choose appropriate levels of data
      encryption measures and implement appropriate network configurations,
      which can be automated through the IBNS. According to the intent
      lifecycle process, IBNS can automatically perform operations such as
      intent parsing, configuration, detection, and optimization of user data
      security levels.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>TBD.</t>
    </section>
  </middle>

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

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

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

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

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

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

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