<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
     please see http://xml.resource.org/authoring/README.html. -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="3"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e., [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std"
     docName="draft-zhang-dyncast-computing-aware-sdwan-usecase-00"
     ipr="trust200902">
  <front>
    <title abbrev="draft-XX-computing-aware-sd-wan-usecase-00">Use Cases for
    Computing-aware Software-Defined Wide Area Network(SD-WAN)</title>

    <author fullname="Shuai Zhang" initials="S." surname="Zhang">
      <organization>China Unicom</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

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

        <email>zhangs366@chinaunicom.cn</email>
      </address>
    </author>

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

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

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

        <email>lijf299@chinaunicom.cn</email>
      </address>
    </author>

    <author fullname="Cheng Li" initials="C." surname="Li">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <region/>

          <code/>

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

        <email>c.l@huawei.com</email>

        <uri/>
      </address>
    </author>

    <author fullname="Xia Chen" initials="X." surname="Chen">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <region/>

          <code/>

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

        <email>jescia.chenxia@huawei.com</email>

        <uri/>
      </address>
    </author>

    <date day="3" month="March" year="2022"/>

    <!---->

    <abstract>
      <t>SD-WAN is aware of the computing power of applications deployed in
      the multiple sites of enterprise and can perform the routing policy
      according to such information. This is defined as the computing-aware
      SD-WAN.This document describes the use cases for computing-aware
      Software-Defined Wide Area Network(SD-WAN).</t>
    </abstract>

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>SD-WAN provides organizations or enterprises with centralized control
      over multiple sites which are network endpoints including branch
      offices, headquarters, data centers, clouds, and more. A enterprise may
      deploy their services and applications in different locations to achieve
      optimal performance. The traffic sent by a host will take the shortest
      WAN path to the closest server. However, the closet server MAY NOT be
      the best choice with lowest cost of network and computing resources for
      the host. If the path computation element can consider the computing
      dimension information in path computation, the best path with lowest
      cost can be provided.</t>

      <t>The computing related information can be the number of vCPUs of the
      VM running the application/services, CPU utilization rate, usage of
      memory, etc.</t>

      <t>The SD-WAN can be aware of the computing resource of applications
      deployed in the multiple sites and can perform the routing policy
      according to the information is defined as the computing-aware
      SD-WAN.</t>

      <t>This document describe the use case of computing-aware SD-WAN.</t>
    </section>

    <section title="Use Cases of Computing-aware SD-WAN">
      <section title="Computing-aware SD-WAN for Enterprise Cloudification">
        <t>Many enterprises are performing the cloud migration to migrate the
        applications from data centers to the clouds, including public,
        private, and hybrid clouds. The clouds resources can be from the same
        provider or multiple cloud providers which have some benefits
        including disaster recovery, load balancing, avoiding vendor
        lock-in.</t>

        <t>In such cloudification deployments SD-WAN provides enterprises with
        centralized control over Customer-Premises Equipments(CPEs) in branch
        offices and the cloudified CPEs(vCPEs) in the clouds.The CPEs connect
        the clients in branch offices and the application servers in clouds.
        The same application server in different clouds is called an
        application instance. Different application instances have different
        computing resource.</t>

        <t>SD-WAN is aware of the computing resource of applications deployed
        in the clouds by vCPEs, and selects the application instance for the
        client to visit according to computing power and the network state of
        WAN.</t>

        <t>Figure 1 below illustrates Computing-aware SD-WAN for Enterprise
        Cloudification.<figure>
            <artwork align="center"><![CDATA[                                                    +---------------+
   +-------+                      +----------+      |    Cloud1     |
   |Client1|            /---------|   WAN1   |------|  vCPE1  APP1  |
   +-------+           /          +----------+      +---------------+
     +-------+        +-------+
     |Client2| ------ |  CPE  |
     +-------+        +-------+                     +---------------+
   +-------+           \          +----------+      |    Cloud2     |
   |Client3|            \---------|   WAN2   |------|  vCPE2  APP1  |
   +-------+                      +----------+      +---------------+

    Figure 1: Illustration of Computing-aware SD-WAN for Enterprise
                         Cloudification]]></artwork>
          </figure></t>

        <t>The current computing load status of the application APP1 in cloud1
        and cloud2 is as follows: each application uses 6 vCPUs. The load of
        application in cloud1 is 50%. The load of application in cloud2 is
        20%. The computing resource of APP1 are collected by vCPE1 and vCPE2
        respectively. Client1 and Client2 are visiting APP1 in cloud1. WAN1
        and WAN2 have the same network states. Considering lightly loaded
        application SD-WAN selects APP1 in cloud2 for the client3 in branch
        office. The traffic of client3 follows the path: Client3 -&gt; CPE
        -&gt; WAN1 -&gt; Cloud2 vCPE1 -&gt; Cloud2 APP1</t>
      </section>
    </section>

    <section title="Security Considerations">
      <t>TBD</t>
    </section>

    <section anchor="Contributors" title="IANA Considerations">
      <t>There are no IANA considerations in this document.</t>
    </section>
  </middle>

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