<?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.39 (Ruby 3.0.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-zzd-tvr-use-case-tidal-network-02" category="std" consensus="true" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.17.5 -->
  <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-02"/>
    <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>
    <author initials="N." surname="Nzima" fullname="Nkosinathi Nzima">
      <organization>MTN</organization>
      <address>
        <email>Nkosinathi.Nzima@mtn.com</email>
      </address>
    </author>
    <date year="2023" month="July" day="29"/>
    <area>Routing Area</area>
    <workgroup>TVR</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 48?>

<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 53?>

<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 174?>



  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9VZ3XYbtxG+5zl8B0S+iF1zGZFS04QnTSJL9rFSikpluj1u
3QtwFyQR7QIbAEuakuVn6bP0yTqDn/0hl5YqX3V9bO4Cg8HMN7+Aoyjqdgw3
KRuRt5qRUwr/yDmZ8oSmZMLMWqrrbofOZoqtRqSA2diTGEsiAkkiY0EzYJMo
OjfRzU0SmZWKYEWEKyJLHnny6HDY7ciZlikzTI+6nSJPqHvDX/iJ4Wch1WZE
tEm6HV3MMq41l2K6yWGT85fTV91Ot8NzNSJGFdoMDw+/R65UMToiV7IwXCzI
CXx1O7jlQskiH5Hp3666nWu2gaEE2AjDFMgUnaHQyJAWZikVCEAAGEK40CMy
7pN/LKlY4IDTccyrEakWVPAbakC4EXld0DXjOM4yytMRuUG6lB8dH/+8tHP9
WGY4rySCzhJupMJvbRRjZkReMP47in4laYLjMTcbO/obdxvGshAGkTldckEb
kk5RUllUgk45FYqKcvReYRE3u6QpbbXFL31yJutY/MJZOXIP+9846ydAuo/3
pE8mNzyjFfPJtdSgpFnyaqa5ycV0Utuhou9b+p8zI9w23Y6QKoNFK3Qv8Bwx
r32Tbqff7+N4FEWEzsAYNLYOMV0y7+psPmexsa4P3jLnMeGarJjaELPJeQwU
UhBZqBATPQJiaAKBUWRMGFDRKJkUMdMwgUwzRlZUAdwGnMH5q46ZgCEJxJ6o
FmQ9QkWCw4IkTMeKzzwrqnWR5YiHtiSBG89y0EKTGQRggtIhcYjhPnkFSKXp
BtkS9oEBsdoJbNQxV3LFE5ZYfBxCGU+SlOHXEwwiqxfuT26fWDXvvhQ6r2lJ
v5Jp4fECpRcQ1ibdEGpIwoG3QnwRUFBKKlCGZnnKegFFDBQGak/YmrxjVKFl
YA2BXEEgb4A2aYrC50zCMpLJFSNzJTMk44pYHIxcAzNJlhLEwI9SRmDsFy6Y
YAoSF1kWi0r0pmpOQpQqBiELXfeWIBOkoEIDd42IBd4Sd8d1U0bjJZp3VvA0
gRfdIymfKQcNCpWCAwfdE7qxnobjjkcCfo9JZxNIBF8sTZ9McX8ICtZrIA8i
VBjnKUX/9Qu9BvMUjF+g3nK24iA6WgbdkC2KlKp0Yx3n3K3JoZAgTenqIP35
3MnhXQ5CWRj4C8qkqVMC1uC+RY4KLAoKCcowZucy+oFnBdoK3H6xzAtTLkPF
wUwkldb3crlmYE0wNpkxsqbagE/X1eYG/RKjwforpAaCFl1sIk1XiHjGwDQJ
yqCXsE+CPqHRIYKAawzOOnrIz1gR1iRlK5bihoVGqeqxvl7yeNkAIZZCMBdT
2lADgMUg2MwCmPAYREfemMPwrSVb9F0I/n9loPQhKejJE3LFfi+4YqiVJmOo
sAVdsJBzoLxjzEL4HFy8fTM96LlfMrm071cv//r2/OrlGb6/eX0yHpcvHU/x
5vXl2/FZ9VatPL28uHg5OXOLYZQ0hjoHFyfvDhxIB5e/Ts8vJyfjA4dk3Q42
xiUak2MDAhZFc1LdCaBai744/fU//x4ck9vbr65enQ4Hg+/v7vzHd4M/HcMH
epvbTQqIOfcJCG86NM8hzyEXjIWY5tzQFL0O4m6JXotO3+90/vBPROZfI/LD
LM4Hxz/6AVS4MRgwawxazHZHdhY7EFuGWrYp0WyMbyHdlPfkXeM74F4b/OGn
FAoAiQbf/fRjxxWtk8phXVWD9AQuA/kBDAMRVkCU+ODHUAzETUf2CQ4atMpp
feC7HAorIeLSFNhC0peY4cOYTxng5AwcFTa9FpAiWrj6RBJjHwkh1SfnLkuh
AgyDEfKLKx04CvaGtpmbZeZmMGlAfY2Bo7H5CfOMkEmoFFxcW5co0gT9MeGa
zlLUEKqocK+FQFhqddZLpIEv0zYiB33yFxAfI/5eXNrFfwhUiJC+f4PQOljE
WKPpcGabF6ZQrJlPaagFdd5ljwj2zig6QlY1BjAiCtiXCyw5vqYrpovU2LoN
xDDB1Ne6NADw6WOzCt3msE9ORN1YsjJTw0rA2BnJi/sIC30B5LrIc6nMlmPV
ZbVIcAG9NphA5jKVEDF2Cw0K6zlnwWS1jF2zSUsL96KKMWpCVUbjizZkvtx7
MR+EA2O9sLi5acOV3I6uINtOwk/ZUhnUB7qq2ysUApuVfRUccCnW7TVVie0p
wLFAdmpbDiwDtnNCN0J/hfJ5zRAi7bITaOaHUqnRtLW0BcfpFQsdqZKgfqbd
nuwD11a9UJdh2shYptrmH1zsK6wLEHAKF81QOeiMp9zwKtLPUIEMTJACAmZp
jRaFNqIWMr61cmnJbjP3UVLar/JAmwKBJfRcKvSJPiz3bkBmG6JzFnO0Z1JJ
BYzh/IY9qWJVu73VyDQzRGg1ShMWusDOhCwpSu9zAvTi0BmBq0HAo9lwMgND
cWzQy7yBHv+0cQzZn9W52DoGIFrggYbVXBY0XTN2DZ28S9r4wUTyrJZLThFE
1y0iBU0ARog+68cl7HtxBIHwTGHtUpaFCjlwPgNdSYG22HGgXm1pWcua6SGs
MRiRaDRuNEvnPXDYtsWl8EhH7LFrn+BA7dKW86intt2Ftj5HGAV0/dBCM62p
cs0RYfbMabdzxQS7Izn/PDp0BvI3AvxZ7RAHACua8pt2bLbSLEgFoZ1DP8ER
inl5EizrA0pT8qFmaUHa4oKuF8I2doa/177hSOSB8hUhBeYtMG3t9yVQobmd
iTJGhX5mk8hRv8y3VVWpOqu9+eTvQbiAUABOqlpz8CA379mctK7tz10u9LC2
OjAaZOsss28zW7Z8at+O57KDKNNyKYVLsscVPrjlA9JsQ0RUpVQg+Yy8wUiV
k1UtU7CfLXLWUVyF2gFk5+KgIUrpqzNUF5K6RmGsQnS/pVyZdz2LjLlVw4HQ
FLLuaFYF39nYCMeGScdL6OUh1JzpaBxLV3XdXQpX+2ENncFLfy5135eChbxu
w6rM295GtU4U5d9zz7PdkVZXMhZuRW32c3OQs4T1EcjLiZJ5GIeOQrjzgHDB
SrVpZe7uhtpYexauZKSZ1MbtAODcMCWxN/N3Q1sXQl4lZwkdzKn5QmAtRiRd
pbQgnmK6wxYF254i5OqAW8iBJQQ7t0/1W5GaDiDcYEjk13Eq4+sKHX9JVt63
WLrjQNdzlxcQm01Ow8HDOJUbuqjb28Si7d1BG6C+vYXwiIyM5nwxuLuzoHz6
9Mk2l+Rjt3NFPpLPPZF9up0TS4fvrWTfuJ/33c4rJLSf7/fTlZRh3X5CS3pO
PpYD0fazLS5YnTwvZ58/b1I3vu0HdjJgTf8Mvm0KAtapfdiup/lMAXKP6e2I
PKnBTYj9360/H0zbHWrXcgfV3fVuP7/XrsO7u9KsKNFkUCo4rl4nXviPLXB/
g67gJ7emEff6ZG3amaQ5ScYWv/EfSX1yXMJL3leWHR81l1qOJfctvk1PaUzW
fWVrsjblp/3k5KiE6Ljyh8lxqyWHlSVrZqmllNJEzoDb9zmxK+XuDrh2o9Nz
F7jeLdxR29ft6o73Ide6jY7fHhPBAJhMwBr+7F4xtC3A4NvR4SHKNxzgC9La
8aEfHuBLWZtzOO/ZrrG1hLti2e6bR1u+abHf459k+/m8I3sbtznzDqc9We5j
g1Ob5z+W026YPJ7TVlA9glMt/moBOD7aXTPetUIVqM2tGsH6v8u0L7IfzWkn
DTySU0vOeASnKsHUM8zkeGfNPkLLKuSbAXlqIzJycYvhagM3wsFnFR0ZPrUU
URXWbpmla01uR1Vyaw1ul9KwG33D4sJeIoSuipZ32NMXZ/4/ZE8mJ/vnsVrP
aHztOOKf/wKYDJnmBSIAAA==

-->

</rfc>
