<?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.27 (Ruby 3.0.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-zzd-tvr-use-case-tidal-network-00" category="std" consensus="true" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.17.0 -->
  <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-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="26"/>
    <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.</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 multiple groups of time-variant information (For example, the regularity of traffic in campus network is quite different 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 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 on 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>
      <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:
H4sIAAAAAAAAA9Va3XLbuBW+14zeAXUu1mlMrSW7266m7dSxnYm3ir11lHbS
bi8gEpKwJgEuAFqRHedZ+ix9sp6DHxKUqDjrXFWZRCR+Ds75zj+UJEn6PcNN
zsbknWbklMI/ck6mPKM5uWRmJdVNv0dnM8Vux6SC2dQvMXaJCEsymQpaAJlM
0blJ7u6yxNyqBHYkuCOxyxO/PDk87PfkTMucGabH/V5VZtQ94Td8pfC1kGo9
Jtpk/Z6uZgXXmksxXZdwyMX59FW/1+/xUo2JUZU2o8PD7w9HwKpidEyuZWW4
WJATeOv38MiFklU5JtO/X/d7N2wNQxmQEYYp4Ck5Q6aRIK3MUipggAAwhHCh
x2QyIP9cUrHAASfjhDcjUi2o4HfUAHNj8rqiK8ZxnBWU52Nyh+tyfnR8/Jel
nRukssB5JRF0lnEjFb5roxgzY/KS8V+Q9WtJMxxPuVnb0Z+5OzCVlTCIzOmS
C9ridIqcyqphdMqpUFTUo48yi7jZLW1umyN+GJAzGWPxA2f1yCPkf+ZskMHS
Fu1+T0hVwJZb1DuoVMyjd9LvDQYDHE+ShNAZoERTq6npknkbZPM5S421SVDj
nKeEa3LL1JqYdclTWCEFkZUKxnpAzBJWgMVWBRMG5DJKZlXKNEwg0YKRW6oA
BwNacoakUyZgSMJivyiy/gNCRYbDgmRMp4rPPCmqdVWUiIa2SwI1XpQghSYz
8IwMucPFwbkG5BXoNc/XSJawDwwWK5SOhvOIka0dKG+p5C3PWGaxcmgVPMty
hm/P0NKtjMgLuX9mRX74Whi91PX6W5lXHjsAYAG+Z/I1oYZkHGgrxBrB1SCh
VCAZLcqcHQRI0ZwZCHPJVuQ9owrVBJsIeDQB7wZx8hy5L5mEbaSQt4zMlSxw
GVfEA7MSiM5SAh/4UjMJhP3GBRNMQXghy2rR8N6WzXGIXKXAZKVj0wk8QaCo
NFDXCFmgLYNupoymS9T1rOJ5Bg/6gOR8phw2yFQO1hxkz+jamh2OOxoZOAGG
hnVYIvhiaQZkiueDh7CDFvTAQgNymVM0Zr/RSzDPQfsVyi1ntxxYR9WgTbJF
lVOVr63lXLg9JYR7XFPbPXB/MXd8eBsElxYG/oIwee6EgD14blWiAIuKQhgx
jNm5gn7gRYW6Ah9YLMvK1NtQcFATyaU1vlKuGGgTlE1mjKyoNmDUsdjcoGGi
a1iDhThBUKOLdaLpLSJeMFBNhjzoJZyToU1oNIjA4Ao9NUYP6OVyhadUGlmJ
vX215OmyJXkqhWDOk7ShBlBKgZuZRS3jKfCLBDGK4VNHvBg4x/v/ikH5rw1C
z56Ra/ZLxRVDCTWZQCKs6IKFqANZGJ0W/Gfvzbu3070D900ur+zz9fnf3l1c
n5/h89vXJ5NJ/dDzK96+vno3OWuemp2nV2/enF+euc0wSlpDvb03J+/3HGB7
Vz9OL64uTyZ7DtVYJ9bJJSqWY50A2kXVUt0LAFvtvjz98b//GR6T+/vfXL86
HQ2H3z88+Jc/DH9/DC9obu40KcDp3CtAt+7RsoRAh1TQGVJackNztEBwvCWa
LVr9oNf77b8QmX+PyR9naTk8/rMfQIFbgwGz1qDFbHtka7MDsWOo45gazdb4
BtJtfk/et94D7tGgy1Qnjb26VAYhCawEYgLoAhysAifxDo+eGBa37dgHNSid
mlLVO7uLm7ATHC7PgSwEeolRPYz5MAF2zsA24dAbIVeOapWzOD+mWNuBLw3I
hYtJyDpDL4Sc5xIFjoJyoZTlZlm4GYwWkE5T4NDYaIQBRsgs5AUubqz+qzxD
48u4prMcZYOcKdxjJRCQKK16jjTQhfyKsA0H5K/CpsPH8Ohm/ksgQmT04weE
OsHi1ULQR7J5ZSrF2mGUhrgf066LQ9BzQdEAiqYIgBFRwblcYHrx+VsxXeXG
5mhYDBNMfaNr+IHOAAtUKDNHA3IiYlXJRkktHQFhpyLP7hP08xWQ66ospTIb
ZhXzapHggheoAlnKXIKn2CM0CKznnAWVRcE50slWvTYgLxvfoiZk4BtrXR3I
fL3tYhwILdyFy1NueNqyIneYS8G2YPBTNjkGyWWrbIHEVinEtahLKOg4aZ0V
0aiAb2pLC2DWiYejzpDQYoGfG4YgaReXQDY/lEuNyo0CFrS4tyzUn0oCAIV2
x7IPXNsjw9EwbWQqc22Pw+iDBHxKdW4CpiFXuBZSBZ3xnBveePsZylGAInIA
wyyt6pJQQ0SO44spF5rsMXPvK7UWGzu0ARBIQpWlQmXonXPnAWS2JrpkKUet
Zg1XQBjaN6xCFWsK7I0qph0nmlrDa7PSFZYlZEmRex8ZoPqGsihrAg20Biqn
VvcFKI3b0hwvAJyh7+J7v9WWdIS1Jmq12wLEEpzJsMisgd6KsRuo7F1Yxxcm
sufgtlpGLoI5DBSsbNUUItEpgu9KTNxLMxAIfNc6a62unXIAq9h9WH3WKaVB
HAzXQPlSoQ63jO8g2lpnwHZwCXsM+vMBmLgPCD6g+HgWcRC4h3WgAExJOzjf
t0UxVPwl0hPQEEChzbSmypVNhNl+1FJ1uQfrJu/hO+GgM2C4FRSeR/0dIKpo
zu+6wdiIylZKXaLKQPZaE1E6QW5qOtQsLT4bVGL/Tp2mH1Vo6Jasj+77/IGW
1IHSxnE0h048W38lYhhljgZ1WG6ST1N47Qw4/whcBWQCYIBfU0N8kT2HDrwd
vfBx9bmEGKtE2wzmI/2m29bFRB2fa6p1ajr3/ZB7vxIsBI12g+SjcFQKIdc7
LhU2S6Km/7eZTVHrP24OvEBYzsC1MyXLMA45TbhyVDj9Q/PcSdxdRHSR9iRc
1MkLqY07AQC9Y0piceAvIjZuH7xILnRrJzs00nwhMA2gRl2QtiCe+pgHK+b2
1sUmnoBb8Koagq2rjrgbj2QA5oYjIr9Jc5neNOj4RhVSJ8kButyuOw7rDlzT
DBbRpjQafhml+kBXrO6solD3rqkDqO/vFZsnRiZzvhg+PFhQPn36ZEsc8rHf
uyYfyec+if30eyd2HT53LvvWff3U773Chfb1p93r6pVh3+6FdukF+VgPJJuf
TXZB6+RFPfviRXt1692+YDIEbfrP8Ls2I6Cd6MUmzvZnCpB7TO/H5FkENyH2
B48/7U27DWpbc3vNTWlUVUa5v1Ovo4eHWq3I0eWwFnDSPF565j92wP0tmoKf
3JhG3OPJaNqppD1JJha/ye9IPDmp4SU/NZqdHLW3Woo19Q26bUtpTca2sjEZ
TflpP3l5VEN03NjD5XGnJkeNJiO1RCGlVpFT4OZFQupSg7twjK4SDtxtoTcL
1+v5bNFcKHbdIWLmbILDxi23bVZAARhMQBu+eWwI2sQz/G58eIj8jYb4gGvt
+MgPD/GhLilKaDdsHdLKnLWN2g6z2zaPNmzTYr/DPsnm5/OG7HXcZcxblHZE
uY8tSl2W/1RK227ydEobTvUESpH/RQ44OdreM9nWQuOo7aNazvrredrl2U+m
tBUGnkipI2Y8gVITYOIIc3m8tWfXQksqxJsh2bcemTi/RXe1jpvg4PNmHRnt
2xVJ49Zum13XGdyOmuDW6dx1SLN31nWUmXb0K6Erazfyn6u2N2KVL3sUy23f
b6u16PeG7ZurulrfP28aNtuyR62IeJSNuvl4rBPFqt6X24+QrIWyd3BNFw5d
VGhc+Tz6kc9mAne7o2GdbXsVFRoKU9yAFw01WiA4gEV90WCGrmzFCG8DfHy6
u7yk+NtJdHVEKmG4a/M05LDUdXvh3lL7LicW2tWc8WjBsATnumi6zK47qK3/
wVE3N29ZWtkLj1Ck0/oufvryzP+afHJ5snsei78ZSOUo4p//ASimAu1nIgAA

-->

</rfc>
