<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.26 (Ruby 3.0.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-zzl-tvr-use-case-tidal-network-00" category="std" consensus="true" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.16.0 -->
  <front>
    <title abbrev="use case of tidal network">Use Case of Tidal Network</title>
    <seriesInfo name="Internet-Draft" value="draft-zzl-tvr-use-case-tidal-network-00"/>
    <author initials="L." surname="Zhang" fullname="Li Zhang" role="editor">
      <organization>Huawei</organization>
      <address>
        <postal>
          <street>Beiqing Road</street>
          <city>Beijing</city>
          <country>China</country>
        </postal>
        <email>zhangli344@huawei.com</email>
      </address>
    </author>
    <author initials="T." surname="Zhou" fullname="Tianran Zhou">
      <organization>Huawei</organization>
      <address>
        <email>zhoutianran@huawei.com</email>
      </address>
    </author>
    <author initials="J." surname="Dong" fullname="Jie Dong">
      <organization>Huawei</organization>
      <address>
        <email>jie.dong@huawei.com</email>
      </address>
    </author>
    <date year="2023" month="March" day="13"/>
    <area>Routing Area</area>
    <workgroup>TVR</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <t>The tidal effect of traffic is very typical on our network, this document introduces the time variant routing scenario in the tidal network, and then describes the assumptions and routing impacts based on the use case. Finally, an exempar of a network to the use case is provided.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro">
      <name>Introduction</name>
      <t>The tidal effect of traffic is very typical on our network, and the traffic volume varies greatly at different times. For example, in the Chinese New Year, there are 200 million people move from their work town to home town, and these people generate huge traffic on our network. For the campus network, there are thousands of people go to the Teaching buildings, libraries and labs in the daytime and go to dormitory in the night. Therefore, the traffic of different places in the campus fluctuate obviously and regularly.</t>
      <t>In the previous scenarios, If the network maintains all the devices up to guarantee the maximum throughput all the time, a lot of power will be wasted. Therefore, it is an effective energy-saving method to shut down some devices when the traffic is low. Thus, a scenario in which the network connection status can be predicted is formed in the tidal network.</t>
      <t>This document introduces the time variant routing scenario in the tidal network, and then describes the assumptions and routing impacts based on the use case. Finally, an exemplar of a network to the use case is provided.</t>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" 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 anchor="assumptions">
      <name>Assumptions</name>
      <t>In order to reduuce energy consumption based on the regularity of tidal traffic, the controller or other control device needs to know the rule of traffic changing. It is assumed that there is a algorithm that can calculates which nodes and links should be disabled or enabled under different traffic scales. Finally, it is assumed that there is a method to config the switching rules for each node.</t>
      <ol spacing="normal" type="1"><li>Known the regularity of tidal traffic, It is assumed that the controller or other control device knows the regularity of tidal traffic, and the change of traffic in the future can be predicated. The regularity information may come from the manual input or the results of computer's calculation.</li>
        <li>An algorithm to calculate which nodes or links can be disabled or enabled under different traffic scales. It is assumed that the controller or other control device supports a algorithm to calculate the minimal topology that satisfies the requirements of traffic at different time. Based on that, it is known which nodes or link should be disabled or enabled under different traffic scales.</li>
      </ol>
    </section>
    <section anchor="routing-impacts">
      <name>Routing Impacts</name>
      <t>The change of link status will change the topology of the network. Furthermore, the data routing may be affected which may result in packet disorder or packet loss. In order to solve these problems, the existing routing protocols may need to provide the following capabilities.</t>
      <ol spacing="normal" type="1"><li>Data model with time-variant information. There is a need for the nodes or controllers to deliver the predicated time-variant information by specific data model or structure. For the tidal network, the change of network topology usually has a regular period, and the overlay of mutiple groups of time-variant information (For example, the regularity of traffic in campus network is quite differern on weekdays and weekend) also should be considered.</li>
        <li>Collection and advertisement for the time-variant information of each node and link. For the distributed routing protocols, each node needs to calculate the routing table, so it is required that each node advertise its own time-variant information(This step is not necessary when every node knows all of the time-variant information about the topology). For the centralized routing protocols, the controller is responsible for the calculation of routing path, so the controller may need to collect the time-variant information of all the nodes(It is also not necessary when the controller already knows all of the time-variant information about the topology).</li>
        <li>Routing algorithm based on time-variant information. When the routing calculator knows the time-variant information of each node, there is a need for a new algorithm to calculate the routing paths, it may be quite different from the existing algorithm.</li>
      </ol>
    </section>
    <section anchor="exemplar">
      <name>Exemplar</name>
      <t>One example of a network with tidal traffic is the campus network, the traffic in the dormitory will raise in the evening and drop in the morning. In contrast, the traffic in the library will raise in the morning and almost drop to zero at night. the traffic of campus changes with a significant period.</t>
      <t>Consider a four nodes network, and the traffic of the network at different time is shown in <xref target="ref-to-fig1"/>.</t>
      <figure anchor="ref-to-fig1">
        <name>Traffic of the network at different time</name>
        <artwork><![CDATA[
T |
R |    ------                   ------
A |   /      \                 /      \
F |  /        \               /        \
F | /          \             /          \
I |/            ------------/
C +---++----++-----------------++------++---
     t1    t2                 t1+T    t2+T
                 Time
]]></artwork>
      </figure>
      <t>The topology of network is shown in <xref target="ref-to-fig2"/></t>
      <figure anchor="ref-to-fig2">
        <name>Topology of a four node network</name>
        <artwork><![CDATA[
    N1---------L1---------N2
    |  \                / |
    |    \            /   |
    |      \        /     |
    |       L6    L5      |
    L2         \/         L3
    |         /  \        |
    |       /      \      |
    |     /          \    |
    |   /              \  |
    N3--------L4----------N4
]]></artwork>
      </figure>
      <t>In order to reduce the power consumption, some of the links may be shut down during the period form t1+nT to t2+nT(n=0,1,2,...). For example, link L5 and L6 can be shut down when the traffic is low, so the possible time-variant topology is as shown in <xref target="ref-to-fig3"/></t>
      <figure anchor="ref-to-fig3">
        <name>Time-variant topology</name>
        <artwork><![CDATA[
    N1---------L1---------N2        N1---------L1---------N2
    |  \                / |         |                     |
    |    \            /   |         |                     |
    |      \        /     |         |                     |
    |        L6    L5     |         |                     |
   L2          \/        L3         L2                   L3
    |         /  \        |         |                     |
    |       /      \      |         |                     |
    |     /          \    |         |                     |
    |   /              \  |         |                     |
    N3---------L4--------N4         N3---------L4--------N4
 Topology1 (form t1+T to t2+T)    Topology 2(form t2+T to t1+T)
]]></artwork>
      </figure>
      <t>In this example, The controller is required to deliver the time-variant information of link L5 and L6 to the related nodes, and then the controller or each node(Every node has already known the time-variant information of topology) needs to calculate the routing path with the time-variant information of L5 and L6. It should be noted that if there are some packets being transmitted over link L5 or L6 at time t1, the shutdown of L5 and L6 may cause packet loss until the source node computes a new routing path. The new routing mechanism may need solve these problems of tidal network.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>TBD</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>TBD</t>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized.  This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t>RFC 2119 specifies common key words that may be used in protocol specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9Va23IbuRF9ZxX/ASs/RI5JSqSUy7KyqciSXNaGpjYynZST
zQM4A5JYzQCzAIY0Jcvfkm/Jl6UblxkML5ZsP4WuJWdwaXSfvkPb7XbbLcNN
xobknWbknMKXnJEJT2lGxsyspLptt+h0qthySEqYTfwSY5eIsCSViaA5kEkV
nZnu3V3WNUvVhR1d3NG1y7t+eff4uN2SUy0zZpgetltlkVL3hL/wk8DPXKr1
kGiTtlu6nOZcay7FZF3AIVeXk1ftVrvFCzUkRpXaDI6Pvz8eAKuK0SG5kaXh
Yk7O4K3dwiPnSpbFkEz+ftNu3bI1DKVARhimgKfuBTKNBGlpFlIBAwSAIYQL
PSSjHvnngoo5DjgZR7wekWpOBb+jBpgbktclXTGO4yynPBuSO1yX8ZPT078s
7FwvkTnOK4mgs5QbqfBdG8WYGZKXjP+KrN9ImuJ4ws3ajv7C3YGJLIVBZM4X
XNAGpxPkVJY1oxNOhaKiGn2UWcTNbmlyWx/xY49cyBiLHzmrRh4h/wtnvRSW
Nmi3W0KqHLYsUe+gUjGL3km71ev1cLzb7RI6BZRoYjU1WTBvg2w2Y4mxNglq
nPGEcE2WTK2JWRc8gRVSEFmqYKwdYhawAiy2zJkwIJdRMi0TpmECieaMLKkC
HAxoyRmSTpiAIQmL/aLI+juEihSHBUmZThSfelJU6zIvEA1tlwRqPC9ACk2m
4BkpcoeLg3P1yCvQa5atkSxhHxgsVigdDecRIxs7UN5CySVPWWqxcmjlPE0z
hm/P0NKtjMgLuX9mRX74Vhi91NX6pcxKjx0AMAffM9maUENSDrQVYo3gapBQ
KpCM5kXGOgFSNGcGwozZirxnVKGaYBMBjybg3SBOliH3BZOwjeRyychMyRyX
cUU8MCuB6Cwk8IEvFZNA2G+cM8EUhBeyKOc1703ZHIfIVQJMljo2ncATBIpS
A3WNkAXaMuhmwmiyQF1PS56l8KA7JONT5bBBpjKw5iB7StfW7HDc0UjBCTA0
rMMSwecL0yMTPB88hHUa0AMLNchFRtGY/UYvwSwD7Zcot5wuObCOqkGbZPMy
oypbW8u5cnsKCPe4prJ74P5q5vjwNgguLQz8B8JkmRMC9uC5ZYECzEsKYcQw
Zudy+oHnJeoKfGC+KEpTbUPBQU0kk9b4CrlioE1QNpkysqLagFHHYnODhomu
YQ0W4gRBjc7XXU2XiHjOQDUp8qAXcE6KNqHRIAKDK/TUGD2gl8kVnlJqZCX2
9tWCJ4uG5IkUgjlP0oYaQCkBbqYWtZQnwC8SxCiGTzviRc853v9XDMq+NAg9
e0Zu2K8lVwwl1GQEibCkcxaiDmRhdFrwn4M3795ODjrul4yv7fPN5d/eXd1c
XuDz29dno1H10PIr3r6+fje6qJ/qnefXb95cji/cZhgljaHWwZuz9wcOsIPr
nyZX1+Oz0YFDNdaJdXKJiuVYJ4B2UbVUtwLAVrsvz3/673/6p+T+/rubV+eD
fv/7hwf/8sf+H07hBc3NnSYFOJ17BejWLVoUEOiQCjpDQgtuaIYWCI63QLNF
q++1Wr/9FyLz7yH50zQp+qd/9gMocGMwYNYYtJhtj2xtdiDuGNpxTIVmY3wD
6Sa/Z+8b7wH3aNBlqrPaXl0qg5AEVgIxAXQBDlaCk3iHR08Mi5t27IMalE51
qeqd3cVN2AkOl2VAFgK9xKgexnyYADtnYJtw6K2QK0e1zFicHxOs7cCXeuTK
xSRknaEXQs5ziQJHQblQynKzyN0MRgtIpwlwaGw0wgAjZBryAhe3Vv9llqLx
pVzTaYayQc4U7rEUCEiUVj1HGuja/Bq8l3+WsTpSguwzPrdS6hU3LnWhvDaQ
EUxmlkXr2f0e+auwmfYxqHfj8hT0EXT9+AGhBLGqaCjHB8lZaUrFmhGahpQS
067qTjChnKJt5XV9ASOihHO5wMzlSwPFdJkZm/5hMUww9RtdaRbo9LD2hQp2
0CNnIrYCWeu/oX4g7LTv2f0a1X895LosCqnMhsXGvFokuOA5qkAWMpPghPYI
DQLrGWdBZVHcj3SyVQr2yMvabakJ9nprrWsHMt/mFm0fYkJ3eOVSoBueNKzI
Heayu61F/JTNu0Fy2aiIwOtKhbjmVXUGzSytEi4aFfBNbdUCzDrxcNQZElos
8HPLECTtQh7I5ocyqVG5USyE7nnJQmmrJACQa3cs+8C1PTIcDdNGJjLT9jgM
bEjAZ2vnJmAacoVrIQvRKc+44R4x8PYLlCMHRWQAhllY1XVDeRI5jq/TXHCx
x8y8r1RarO3QxlYgCQWcCkWnd869B5DpmuiCJRy1mtZcAWHoDLHAVayu3TcK
pGacqMsYr81SlxgzyYIi9z4yQGEPFVdaBxroOlRGre5zANcW/Xi14Ox8H9uH
jYZnR1Srg1az4UAowZcMC1atBDrLirFb6BlcwsAXJtLn4LVaRh6C2RH0q2w9
BjHoHGF3dStuoymIAl5r3bRS1F4RgMsqC1R5qsYaTNZATVSi9rbMrhNtrdJq
M6yEPQY9uQPG7UOBDyU+kkUcBO5hHWCPyWgP54e20oY2okB6AroMqN6Z1lS5
Woww2+Raqi7rYDHmfXsvHHQKDDfCwfOoaQREFc343W4wNuKxlVIXqC2QvdJE
lEiQm4oONQuLzwaV2LMTp+lHFRpaMOudhz5zoBHtQGnjOJpBe5+uvxExjC8n
vSog12mnrub2hpp/BK4CMgEwwK+uHp5kz6Gtb8YtfFx9LhXGKtE2d/kY3/BY
dK5QRlSRuaJaJaVL32S592vBQrxodl0+/kZFEHK956ZisxiqLxVsTlPU+o+b
Ay8QljNw7VTJIoxDNhOuxhVO/9CR7yTubjd2kfYkXNTJcqmNOwEAvWNKYlng
bzc2rjS8SC5oayc7dOd8LjABoEZdeLYgnvtwBytm9irHppy9l1XN5L1dmiCs
rgkDKe7vFZt1jexCkdx/eLDnffr0ydYN5GO7dUM+QqVHuvZDtj9uot06s+uO
3ODPW8vCRLv1ChcehfHNlfWEW3lUT/28e6FdekU+HsWz3ehzBACSF/DwAr/8
d+MThuyvrWwJMX37PdiSxPRfTNzUi4lfG38mALBH8H5InkXgwhb8c8QPB5On
6umgvseMCrMof+7U4uDhoVIicjTuV4KO6sfxwM1+3KGtI1S8n9yYRpTjyWja
KaA5SUa/t9+/I/HkqEb151pto5PmVkuxor5Bt2lojclNk4kmGzZip/3k+KSC
6LS2i/HpTk0Oak1Gaol8s1KRU+Bmm5+4GOuuA6NGv+Pu8rxZuHbJh936ui8t
lS0mkICNEPY6Dq1STOzF1QAeDsUPx51+Z9Dp9XrPN+6kbf0PCsGoAdrx/Vh9
wJ4rxCoxF1Cu22zeyD+VgdoObbdhnjzRMIN6vspwq+ePm5NblrJt2F+wedvw
v2jzhmc8bXPkN5HjjE6qwdF2uHrUr76M7Q2/+5LNW3759M07/PZpm2u/jhx7
fFot2zMPm4Nr98lhcLDgX5PnuLXy/YFfMPALYOHznXHjpI4bO12nihb2srZy
2MmOmjp0Ds0283MV4Ybb+ytuxTLbldqKIrpo375XqSrKw8u6qbANZVQui0fZ
qArkx7olrDx9SfgIyUooe0NUN4lQ6Yfmis+iv27ZIOvuHjSss9FUUaGhfsQN
2AZXaIHgABb1+dj0XXmIwdLGyvh0d7VG8Y8G0cUGKYXhrhXRkB4S15GEWzXt
K/FYaHd9F4/mDMtErvO6E9p1Q7L1vy5UBfhblpS2Hw+FJK0uoScvL/yfUc/G
Z/vnsfabglSOIv77H9IvyJRgIQAA

-->

</rfc>
