<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<rfc
      xmlns:xi="http://www.w3.org/2001/XInclude"
      category="info"
      docName="draft-xiong-rtgwg-requirements-hp-wan-00"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">

 <!-- ***** FRONT MATTER ***** -->

 <front>

   <title abbrev="Requirements for High-performance Wide Area Networks">Requirements for High-performance Wide Area Networks</title>
    <seriesInfo name="Internet-Draft" value="draft-xiong-rtgwg-requirements-hp-wan-00"/>
   
   <author fullname="Quan Xiong" initials="Q" surname="Xiong">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <street/>
         <city></city>
          <region/>
          <code/>
          <country>China</country>
        </postal>
        <phone></phone>
        <email>xiong.quan@zte.com.cn</email>
     </address>
    </author>

    <author fullname="Chenqiang Gao" initials="C" surname="Gao">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <street/>
         <city></city>
          <region/>
          <code/>
          <country>China</country>
        </postal>
        <phone></phone>
        <email>gao.chenqiang@zte.com.cn</email>
     </address>
    </author>	
	
	 <author fullname="Zhengxin Han" initials="Z" surname="Han">
      <organization>China Unicom</organization>

      <address>
        <postal>
          <street></street>
          
          <city></city>
          
          <region></region>
  
          <code></code>

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

        <phone></phone>

        <email>hanzx21@chinaunicom.cn</email>
      </address>
    </author>	
	
	 <author fullname="Guangyu Zhao" initials="G" surname="Zhao">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street></street>
          
          <city></city>
          
          <region></region>
  
          <code></code>

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

        <phone></phone>

        <email>zhaoguangyu@chinamobile.com</email>
      </address>
    </author>
	
	 <author fullname="Wenkuan Qu" initials="W" surname="Qu">
      <organization>China Telecom</organization>

      <address>
        <postal>
          <street></street>
          
          <city></city>
          
          <region></region>
  
          <code></code>

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

        <phone></phone>

        <email>quwk@chinatelecom.cn</email>
      </address>
    </author>	
	

   <area>Routing</area>
    <workgroup>RTGWG</workgroup>
   <keyword></keyword>
   
   <abstract>
   
    <t>Many applications such as big data and intelligent computing demand 
	massive data transmission between data centers, which needs to ensure
	data integrity and provide stable and efficient transmission services 
	in wide area networks and metropolitan area networks. This document 
	outlines the requirements for High-performance Wide Area Networks (HP-WAN).</t>
	  
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default"> <name>Introduction</name>
	
	<t>Big data and intelligent computing is undergoing rapid development. 
	There are many applications requiring massive data transmission 
	between data centers, which need to ensure data integrity and 
	provide stable and efficient transmission services in Wide Area 
	Networks (WAN) and Metropolitan Area Networks (MAN). The use cases
	have been discussed in [I-D.xiong-rtgwg-requirements-hp-wan]. 
	The industries need to solve the problems such as long distance,
	slow feedback, multiple paths, load balance, low throughput and 
	so on.</t>
	
	<t>Compared with ordinary WAN, High-performance Wide Area 
	Networks (HP-WAN) puts forward higher performance requirements 
	such as ultra-high bandwidth utilization, and ultra-low packet
	loss ratio ensuring effective high-throughput transmission. 
    The topology in HP-WAN is complicated with long distances, 
	multiple hops, paths, domains and the services are massive and
	concurrent with multiple types and different traffic models 
	such as the elephant flows with short interval time, high speed 
	and large data scale. </t>

	<t>The network requirements demand high performance such as 
	the high-throughput data transmission between data centers.
	It is viewed as the main performance indicator which is affected
	by long-distance delays, jitter and packet loss ratio. For example,
	the massive data transmission between data centers mainly depend 
	on the transport layer protocols such as Transfer Control Protocol
	(TCP), Remote Direct Memory Access (RDMA) and Quick UDP Internet
	Connections (QUIC) etc. The throughput will dramatically decrease
	when the packet loss ratio is over a threshold value. Extremely
	low packet loss ratio or even zero packet loss will greatly reduce 
	the bandwidth resource consumption caused by packet loss retransmission.</t> 
	
	<t>Existing technologies in data centers, e.g. Priority-based Flow 
	Control (PFC) [IEEE 802.1qbb] and Explicit Congestion Notification 
	(ECN) <xref target="RFC3168"></xref>, have problems due to various 
	service types, massive data, large burst, and high Round-Trip Time 
	(RTT) latency and jitter in large-scale networks. It will be challenging
	to achieve high-throughput transmission in HP-WAN.</t>
	
	<t>This document outlines the requirements for High-performance 
	Wide Area Networks (HP-WAN).</t>
	    
      <section numbered="true" toc="default"><name>Requirements Language</name>
	   
	   	<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
       "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
       "OPTIONAL" in this document are to be interpreted as described in BCP
       14 <xref target="RFC2119" pageno="false" format="default"/> 
	   <xref target="RFC8174" pageno="false" format="default"/> when, and only when, 
	   they appear in all capitals, as shown here.</t>
	
      </section>
    </section>
	
    <section anchor="Terminology" numbered="true" toc="default"> <name>Terminology</name>
	
	<t>The terminology is defined as following.</t>
	
    <t>High-performance Wide Area Networks (HP-WAN): indicates the WAN 
	or MAN which puts forward higher performance requirements such as
	ultra-high bandwidth utilization, and ultra-low packet loss ratio 
	ensuring effective high-throughput transmission.</t>
	
    <t>Abbreviations and definitions used in this document:</t>
	   
	   <dl newline="false" spacing="normal" indent="15" pn="section-2-3">
		<dt>PFC: </dt>
		<dd>Priority Flow Control</dd>	
	    <dt>ECN: </dt>
	    <dd>Explicit Congestion Notification</dd>
	    <dt>ECMP: </dt>
	    <dd>Equal-Cost Multipath</dd>
	    <dt>RTT: </dt>
	    <dd>Round-Trip Time</dd>
	    <dt>TCP: </dt>
	    <dd>Transfer Control Protocol </dd>
	    <dt>RDMA: </dt>
	    <dd>Remote Direct Memory Access Round-Trip Time</dd>
	    <dt>QUIC: </dt>
	    <dd>Quick UDP Internet Connections</dd>
	    <dt>WAN: </dt>
	    <dd>Wide Area Networks</dd>
	    <dt>MAN: </dt>
	    <dd>Metropolitan Area Networks</dd>
		</dl>
    
    </section>

    <section numbered="true" toc="default"> <name>Primary Goals</name>
	
	<t>The primary goal of HP-WAN is to ensure the effective high-throughput
	transmission of massive data with the performance indicators such as 
	ultra-high bandwidth utilization, zero packet loss ratio and low latency. 
	For instance, the computing method of throughput for TCP is as following 
	shown.</t>
	
	<t>Throughput = min{BW,WindowSize/RTT,(MSS/RTT)*(1/P));</t>
	
	<t>BW indicates the maximum bandwidth, WindowSize indicates the 
	size of the window, MSS indicates the maximum segment size, 
	RTT indicates the round time delay, P indicates the square
	root of packet loss ratio. </t>
	
   <section numbered="true" toc="default"> <name>Extremely Low or Zero Packet Loss Ratio</name>
	
   <t>According to the throughput computing formula, the packet loss 
	negatively correlates with throughput. The lower the 
	packet loss rate, the higher the throughput. According to the 
	experimental data, for TCP, the throughput dramatically decreases
	up to 89.9% when the packet loss ratio is 2%. For RDMA, the 
	throughput dramatically decreases with a packet loss ratio greater 
	than 0.1%, and a 2% packet loss ratio effectively reduces the 
	throughput to zero. It is important to ensure the extremely 
	low or zero packet loss ratio to achieve high-throughput data 
	transmission in HP-WAN.</t>
	</section>
	    
	<section numbered="true" toc="default"> <name>Low Long-distance Delay and Jitter</name>
	
	<t>According to the throughput computing formula, the RTT is 
	negatively correlated with throughput. The lower the RTT, 
	the higher the throughput. But the RTT delay is impacted
	with the long-distance latency. For example, when the 
	distance between the data centers is 500 kilometers, the 
	RTT is 5ms. When the distance is 3000 kilometers, the
	RTT is 30ms. According to the experimental data, when
	the jitter is over 300~500us, the throughput will 
	dramatically decrease. So it is required to guarantee low
    long-distance delay and jitter to achieve high-throughput 
	data transmission in HP-WAN.</t>
	
	</section>
	
	<section numbered="true" toc="default"> <name>Ultra-high Bandwidth Utilization</name>
	
   <t>It is important to reserve sufficient bandwidth to
   achieve high-throughput transmission for a single flow. 
   But for massive concurrent flows in a network with certain 
   resources, bandwidth utilization is the key aspect.
   Ultra-high bandwidth utilization refers to the efficient 
   use of available network capacity to maximize data transfer
   rates and minimize latency. This is particularly important 
   in scenarios where high volumes of data need to be transferred
   quickly. So it is required to improve the bandwidth utilization
   to achieve high-throughput data transmission for multiple 
   concurrent services in HP-WAN.</t> 
   
   </section>
   </section>

   <section numbered="true" toc="default"> <name>Requirements </name>
   
   <t>Challenges of high-throughput transmission in HP-WAN come from 
   massive concurrent services and long-distance delays, jitter 
   and packet loss. The existing network technologies have various
   problems and cannot meet the demands. This document outlines
   the requirements for high-throughput data transmission in HP-WAN.</t>
   
   <section numbered="true" toc="default"> <name>Support High-precision Flow Control</name>
   
   <t>Flow control refers to a method for ensuring the data is
   transmitted efficiently and reliably and controlling the rate
   of data transmission to prevent the fast sender from overwhelming
   the slow receiver and prevent packet loss in congested situations. 
   PFC (Priority-based Flow Control) [IEEE 802.1qbb] is a hop-by-hop
   and priority-based flow control method which provides backpressure
   mechanism for the receiver signals the sender to slow down the rate
   of data transmission. For the long-distance link and transmission 
   delay in WAN, it is required to configure the reasonable threshold
   and increase buffer for effective throughput without packet loss.</t>

   <t>PFC creates 8 virtual channels on a link and assigns a 
   priority to each channel, allowing for individual pause 
   and restart of any one of the virtual channels. The existing
   flow control mechanism is based on port and priority with 
   limited number, while there are multiple services with various
   types and different traffic requirements. It is required to 
   provide fine-grained and high-precision flow control to reduce 
   the impact between different traffic flows. </t>
   
   </section> 
   
   <section numbered="true" toc="default"> <name>Support Congestion Control based on End-network Coordination</name>

   <t>Congestion control refers to a method for controlling the total
   amount of data entering the network to maintain the traffic at an
   acceptable level. The difference between congestion control and 
   flow control is that flow control acts on the receiver, while 
   congestion control acts on the network. As per <xref target="RFC3168"></xref>, ECN 
   defines an end-to-end congestion notification mechanism based 
   on IP and transport layers. When the congestion occurred, the 
   device marks packets and transmits congestion information to 
   the server and the server sends packets to the client to notify 
   the source to adjust the transmission rate to achieve congestion 
   control.</t>
   
   <t>The long-distance transmission of thousands of kilometers 
   results in extremely long link transmission delays and it will 
   delay the network state feedback. And it is inefficient that 
   1-bit ECN signal can not specify the detailed congestion information.
   And it mainly relies on passive congestion control to adjust 
   the rate after receiving congestion signals. It is required to
   improve the congestion control by enhancing the IP network 
   capability  to achieve the end and network coordination in WAN. 
   For example, the device could initial the notification directly 
   to the source and provide precise notification information. 
   And the device in the network may further perform the proactive
   congestion control.</t>
   
   </section>
   
   <section numbered="true" toc="default"> <name>Support Muti-path Load Balance</name>

   <t>Load balance refers to a method for the allocation of load (traffic)
   to multiple links for forwarding traffic. When transmitting intelligent 
   computing services, the traffic is mainly elephant flow and the network
   resources is insufficient in WAN. Uneven network load will lead to a 
   decrease in network throughput and low link utilization. In order to 
   improve bandwidth utilization, it is required to implement multi-path 
   load balance to achieve low latency, zero packet loss and high-throughput
   performance in WAN. </t>
   
   <t>There are three optional methods such as flow-based ECMP, 
   flowlet-based load balance and packet-based load balance. As per <xref target="RFC7424"></xref>, 
   Link Aggregation Group (LAG) and Equal-Cost Multipath (ECMP) are used 
   for bandwidth scaling. ECMP uses 5-tuple for HASH load balancing to 
   achieve per-flow load balancing and link backup and it is applied 
   to scenarios with large number of flows. It will be challenging for 
   HASH conflict and poor network balancing with massive elephant flows. 
   For example, flow-based ECMP will distribute the elephant flows into 
   the same link, resulting in congestion and packet loss. Packet-based 
   load balance will result in out-of-order packets. Flowlet-based load 
   balance can distribute the sub-flows to different paths. The time 
   interval gap value between sub-flows needs be accurately configured 
   based on the delay information of multiple path. The deterministic 
   technology can be implemented to guarantee the latency and jitter. </t>
  
   </section>
   
   <section numbered="true" toc="default"> <name>Support the Differentiated Traffic Scheduling </name>
   
    <t>Traffic scheduling refers to a method for managing and allocating
	the flow of data packets within a network to optimize performance 
	and utilize network resources efficiently. Considering the multiple
	services with various types and different traffic requirements, the 
	traffic is required to be scheduled to multiple paths and resources
	to achieve differentiated QoS requirements. The existing technologies
	such as resource reservation, network slicing, queuing-based solutions
	to guarantee deterministic latency can be used for providing zero packet
	loss, long-distance latency and jitter guarantees and high reliability
	in WAN.  For example, the flow-specific data may require low latency
	or loose latency and it is required to provide different queuing and 
	scheduling functionalities.</t>
   </section> 
   
   
    <section numbered="true" toc="default"> <name>Support Flow-based Network Monitoring </name>
	
	<t> When a fault occurs in data transmission, it should 
	discover root causes of some of the hard-to-debug network and
	identify the node which is dropping the packets. Bandwidth 
	monitoring is also important for network planning and service-level
	assurance, which the network operators can predict bandwidth 
	availability and guarantee the high-throughput transmission. The 
	performance monitoring is a critical aspect of managing and optimizing 
	networks such as end-to-end measurement of packet loss, latency, 
	jitter and hop-by-hop node ID, node delay, queue and buffer information.</t>
	
	<t>As per <xref target="RFC9232"></xref>, network telemetry is a 
	technology for gaining network insight and facilitating efficient 
	and automated network management.It is required to provide flow-based 
	network monitoring based on telemetry, which makes it easier to  
	troubleshoot issues and monitor bandwidth, traffic and performance. </t>
	
	</section>
    </section>

   <section  numbered="true" toc="default"> <name>Security Considerations</name>

   <t>This document lists the requirements for HP-WAN and does not raise
   any security concerns or issues in addition to ones common to networking
   which may have security considerations from both the use-specific 
   perspective and the technology-specific perspective. </t>
   </section>
   
   <section numbered="true" toc="default"> <name>IANA Considerations</name>
   <t>This document makes no requests for IANA action.</t>   
   </section>
	
   <section numbered="true" toc="default"> <name>Acknowledgements</name>
   <t>The authors would like to acknowledge Yao Liu, Zheng Zhang and Bin Tan for 
   their thorough review and very helpful comments.</t>
   </section> 
   
  </middle>
  
  <!--  *****BACK MATTER ***** -->

 <back>
 
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8664.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9232.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7424.xml"/>	
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3168.xml"/>
		
      </references>
    </references>
 
 </back>
</rfc>
