<?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.35 (Ruby 3.0.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-zzd-tvr-use-case-tidal-network-01" category="std" consensus="true" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.17.4 -->
  <front>
    <title abbrev="use case of tidal network">Use Case of Tidal Network</title>
    <seriesInfo name="Internet-Draft" value="draft-zzd-tvr-use-case-tidal-network-01"/>
    <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="July" day="10"/>
    <area>Routing Area</area>
    <workgroup>TVR</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 43?>

<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 tidal network is provided.</t>
    </abstract>
  </front>
  <middle>
    <?line 48?>

<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 time. 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 at a low level. 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 tidal network 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>
        <?line -18?>

</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 regularity 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.</t>
      <ol spacing="normal" type="1"><li>Knowing 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-requirements">
      <name>Routing Requirements</name>
      <t>The change of link status will change the topology of network. Furthermore, the data forwarding may be affected and result in packet disorder or packet loss. In order to solve these problems, the existing routing protocols 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 but may has multiple regularities (For example, the regularity of traffic in campus network is quite different on weekdays and weekend).</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 by itself, so each node needs to advertise its own time-variant information to other nodes (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 knows all of the time-variant information about the topology by other means).</li>
        <li>Routing algorithm based on time-variant information. When the routing calculator knows the time-variant information of each node, a new algorithm is needed to calculate the routing paths based on the time-variant information, it may be quite different from the existing algorithms.</li>
        <li>Routing path with time-variant information. The routing path is calculated based on the time-variant topology, so the change of topology will also affect the routing path. Therefore, the routing path may need be expressed with a time-variant information which is associated with the change of the topology so that the node can schedule paths according to their time-variant information.</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 for the dormitory, the traffic of the network will raise at 12 o'clock and drop to the low level at 14 o'clock, then it will raise at 21 o'clock and drop to the low level at 2 o'clock. The traffic 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 +---------++--------------++-----------++---
  12        16              21           2
                 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 when the traffic is at a low level. For example, link L5 and L6 can be shut down from 16:00 to 21:00 and from 2:00 to 12:00, 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 (12:00-16:00 and 21:00-2:00)  Topology 2(16:00-21:00 and 2:00-12:00)
]]></artwork>
      </figure>
    </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>
    <?line 169?>



  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9VZ3XYbtxG+5zl8B1S6iB1zGZFS0oQnTSpL9rFSmkpluj1u
3QtwFyQR7QIbAEuakuVn6bP0yTqDn/0hl5YqX3V9bO4Cg8HMN7+Aoyjqdgw3
KRuRt5qRMwr/yDmZ8oSmZMLMWqrrbofOZoqtRqSA2diTGEsiAkkiY0EzYJMo
OjfRzU0SmZWKYEWEKyJLHnny6GjQ7ciZlikzTI+6nSJPqHvDX/iJ4Wch1WZE
tEm6HV3MMq41l2K6yWGTixfTl91Ot8NzNSJGFdoMj45+OBqCqIrREbmSheFi
QU7hq9vBLRdKFvmITP921e1csw0MJcBGGKZApugchUaGtDBLqUAAAsAQwoUe
kXGf/GNJxQIHnI5jXo1ItaCC31ADwo3Iq4KuGcdxllGejsgN0qX8+OTkz0s7
149lhvNKIugs4UYq/NZGMWZG5Dnjv6PoV5ImOB5zs7Gjv3G3YSwLYRCZsyUX
tCHpFCWVRSXolFOhqChH7xUWcbNLmtJWW/zSJ+eyjsUvnJUj97D/jbN+AqQN
3t2OkCqDJSu0O5hUzGvfpNvp9/s4HkURoTNAicbWUtMl8z7I5nMWG+uTYMY5
jwnXZMXUhphNzmOgkILIQgVn7RGzBArw2CJjwoBeRsmkiJmGCWSaMbKiCnAw
YCXnSDpmAoYkEHuimvf3CBUJDguSMB0rPvOsqNZFliMa2pIEbjzLQQtNZhAZ
CUqHxCG4+uQl2DVNN8iWsA8MiNVOxKGOuZIrnrDE4uMQyniSpAy/DtG7rV64
P7k9tGrefSl0XtOSfiXTwuMFSi8g3ky6IdSQhANvhfgioKCUVKAMzfKU9QKK
6MEM1J6wNXnHqELLwBoCQUwgoEGbNEXhcyZhGcnkipG5khmScUUsDkaugZkk
Swli4EcpIzD2CxdMMAUZhSyLRSV6UzUnIUoVg5CFrntLkAlyQ6GBu0bEAm+J
u+O6KaPxEs07K3iawIvukZTPlIMGhUrBgYPuCd1YT8NxxyMBv8dssAkkgi+W
pk+muD8EBes1kAcRKozzlKL/+oVeg3kKxi9QbzlbcRAdLYNuyBZFSlW6sY5z
4dbkkOGRpnR1kP5i7uTwLgdRLAz8BWXS1CkBa3DfIkcFFgWFzGEYs3MZ/cCz
Am0Fbr9Y5oUpl6HiYCaSSut7uVwzsCYYm8wYWVNtwKfranODfonRYP0VUgNB
iy42kaYrRDxjYJoEZdBL2CdBn9DoEEHANQZnHT3kZ6wIa5KyFUtxw0KjVPVY
Xy95vGyAEEshmIspbagBwGIQbGYBTHgMoiNvzGH41pIt+i4E/78yUPqQFHR4
SK7Y7wVXDLXSZAylr6ALFnIO1F2MWQifg9dv30wPeu6XTC7t+9WLv769uHpx
ju9vXp2Ox+VLx1O8eXX5dnxevVUrzy5fv34xOXeLYZQ0hjoHr0/fHTiQDi5/
nV5cTk7HBw7Juh1sjEs0JsfOACyK5qS6E0C1Fn1+9ut//j04Ibe3f7h6eTYc
DH64u/Mf3w/+eAIf6G1uNykg5twnILzp0DyHPIdcMBZimnNDU/Q6iLslei06
fb/T+fqfiMy/RuTHWZwPTn7yA6hwYzBg1hi0mO2O7Cx2ILYMtWxTotkY30K6
Ke/pu8Z3wL02+OPPKRQAEg2+//mnjitap5XDuqoG6QlcBvIDGAYirIAo8cGP
oRiIm47sExx0TpXT+sB3ORRWQsSlKbCFpC8xw4cxnzLAyRk4Kmx6LSBFtHD1
iSTGBg9Cqk8uXJZCBRgGI+QXVzpwFOwN/Sw3y8zNYNKA+hoDR2PzE+YZIZNQ
Kbi4ti5RpAn6Y8I1naWoIVRR4V4LgbDU6qyXSANfpm1EDvrkLyA+Rvy9uLSL
/xCoECF9/wahdbCIsUbT4cw2L0yhWDOf0lAL6rzLHhHsnVF0hKxqDGBEFLAv
F1hyfE1XTBepsXUbiGGCqa90aQDg08c+FbrNYZ+cirqxZGWmhpWAsTOSF/cR
FvoCyHWR51KZLceqy2qR4IJnaAKZy1RCxNgtNCis55wFk9Uyds0mLS3c8yrG
qAlVGY0v2pD5cu/FfBBOcvXC4uamDVdyO7qCbDsJP2VLZVAf6Kpur1AIbFb2
VXDypFi311QltqcAxwLZqW05sAzYzgndCP0Vyuc1Q4i0y06gmR9KpUbT1tIW
nHNXLHSkSoL6mXZ7sg9cW/VCXYZpI2OZapt/cLGvsC5AwClcNEPloDOecsOr
SD9HBTIwQQoImKU1WhTaiFrI+NbKpSW7zdxHSWm/ygNtCgSW0HOp0Cf6sNy7
AZltiM5ZzNGeSSUVMIbzG/akilXt9lYj08wQodUoTVjoAjsTsqQovc8J0ItD
ZwSuBgGPZsPJDAzFsUEv8wZ6/JPGMWR/Vudi6xiAaIEHGlZzWdB0zdg1dPIu
aeMHE8nTWi45QxBdt4gUNAEYIfqsH5ew78URBMIzhbVLWRYq5MD5DHQlBdpi
x4F6taVlLWumh7DGYESi0bjRLJ33wGHbFpfCIx2xx659ggO1S1vOo57Ydhfa
+hxhFND1QwvNtKbKNUeE2TOn3c4VE+yO5Pzz6NAZyN8I8Ke1QxwArGjKb9qx
2UqzIBWEdg79BEco5uVJsKwPKE3Jh5qlBWmLC7peCNvYGf5e+4YjkQfKV4QU
mLfAtLXfl0CF5nYmyhgV+qlNIsf9Mt9WVaXqrPbmk78H4QJCATipas3Bg9y8
Z3PSurY/d7nQw9rqwGiQrbPMvs1s2fKpfTueyw6iTMulFC7JnlT44JYPSLMN
EVGVUoHkM/IGI1VOVrVMwX62yFlHcRVqB5Cdi4OGKKWvzlBdSOoahbEK0f2W
cmXe9Swy5lYNB0JTyLqjWRV8Z2MjHBsmHS+hl4dQc6ajcSxd1XV3KVzthzV0
Bi/8udR9XwoW8roNqzJvexvVOlGUf889z3ZHWl3JWLgVtdnPzUHOEtZHIC8n
SuZhHDoK4c4DwgUr1aaVubsbamPtWbiSkWZSG7cDgHPDlMTezN8NbV0IeZWc
JXQwp+YLgbUYkXSV0oJ4hukOWxRse4qQqwNuIQeWEOzcPtVvRWo6gHCDIZFf
xamMryt0/CVZed9i6U4CXc9dXkBsNjkNBw/jVG7oom5vE4u2dwdtgPr2FsIj
MjKa88Xg7s6C8unTJ9tcko/dzhX5SD73RPbpdk4tHb63kn3jft53Oy+R0H6+
309XUoZ1+wkt6QX5WA5E28+2uGB18qycffasSd34th/YyYA1/TP4rikIWKf2
Ybue5jMFyD2mtyNyWIObEPvfTn86mLY71K7lDqq7691+fq9dh3d3pVlRosmg
VHBcvU688B9b4P4GXcFPbk0j7vXJ2rQzSXOSjC1+429JfXJcwkveV5YdHzeX
Wo4l9y2+TU9pTNZ9ZWuyNuWn/eTkuITopPKHyUmrJYeVJWtmqaWU0kTOgNv3
ObEr5e4OuHaj03MXuN4t3FHb1+3qjvch17qNjt8eE8EAmEzAGv7sXjG0LcDg
u9HREco3HOAL0trxoR8e4EtZm3M479musbWEu2LZ7pvHW75psd/jn2T7+bwj
exu3OfMOpz1Z7mODU5vnP5bTbpg8ntNWUD2CUy3+agE4Pt5dM961QhWoza0a
wfq/y7Qvsh/NaScNPJJTS854BKcqwdQzzORkZ80+Qssq5JsBeWIjMnJxi+Fq
AzfCwacVHRk+sRRRFdZumaVrTW7HVXJrDW6X0rAbfcPiwl4ihK6KlnfY0+fn
/j9kTyen++exWs9ofO044p//Auef1USeIQAA

-->

</rfc>
