<?xml version='1.0'?>   
    <!DOCTYPE rfc SYSTEM 'rfc2629.dtd' [ 
    	<!ENTITY rfc2629 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml'> 
		]>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="info" docName="draft-xiong-detnet-enhanced-detnet-gap-analysis-00"
     ipr="trust200902">
  <!-- ***** FRONT MATTER ***** -->
  <front>
    <title abbrev="Gap Analysis for Enhanced DetNet Data Plane">Gap Analysis for Enhanced DetNet Data Plane</title>
	
    <author fullname="Quan Xiong" initials="Q" surname="Xiong">
      <organization>ZTE Corporation</organization>

      <address>
        <postal>
          <street>No.6 Huashi Park Rd</street>
          
          <city>Wuhan</city>
          
          <region>Hubei</region>
  
          <code>430223</code>

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

        <phone></phone>

        <email>xiong.quan@zte.com.cn</email>
      </address>
    </author>
	
	
    <area>Routing</area>
    <workgroup>DETNET</workgroup>
    <keyword></keyword>
    <abstract>

	 <t>From charter and milestones, the enhanced Deterministic Networking (DetNet) is 
	required to provide the enhancement of flow identification and packet treatment 
	for data plane to achieve the DetNet QoS in large-scale networks. </t>
	 
	<t>This document analyzes the gaps of the existing technologies especially applying
	the DetNet data plane as per RFC8938.</t>
	 
    </abstract>
  </front>

  <!-- ***** MIDDLE MATTER ***** -->

  <middle>
  
    <section title="Introduction">
	
   <t>As per <xref target="RFC8655" pageno="false" format="default"/>, it defined the
   overall architecture for Deterministic Networking (DetNet) , which provides a capability for 
   real-time applications with extremely low data loss rates and bounded 
   latency within a network domain. It has three goals: minimum and maximum 
   end-to-end latency from source to destination, bounded jitter (packet 
   delay variation), packet loss ratio and upper bound on out-of-order 
   packet delivery. To achieve the above objectives, multiple techniques 
   need to be used in combination, including explicit routes, service 
   protection and resource allocation defined by DetNet.</t> 
   
   <t>As defined in <xref target="RFC8938" pageno="false" format="default"/>, the DetNet data plane 
   describes how application flows, or App-flows are carried over DetNet networks 
   and it is provided by the DetNet service and forwarding sub-layers with DetNet-related
   data plane functions and mechanisms. The enhanced DetNet is required to 
   provide the enhancement of flow identification and packet treatment 
   for data plane to achieve the DetNet QoS in large-scale networks. 
   It is required to analyse the applicability in DetNet for large-scale
   networks.</t>
     
   <t>This document describes the requirements for multiple deterministic services, 
   discusses the characteristics of large-scale networks and analyzes the gaps 
   of the existing technologies especially applying the DetNet data plane as per 
   RFC8938.</t>
   
   </section>

    <section title="Conventions used in this document">	 	
    <section title="Terminology">
	<t>The terminology is defined as <xref target="RFC8655"></xref> and <xref target="RFC8938"></xref>.</t>
   </section>
   
   <section title="Requirements Language">
    <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"></xref> <xref target="RFC8174"></xref> when,
    and only when, they appear in all capitals, as shown here.</t>
    </section>
   </section>
   
   <section title="Service Requirements of Large-Scale Deterministic Networks" numbered="true" toc="default">
   
   <section title="Support the Differentiated DetNet QoS of Multiple Services" numbered="true" toc="default">
   
   	<t>5G network is oriented to the internet of everything. It need to supports 
	the Ultra-reliable Low Latency Communications (uRLLC) services. The uRLLC services
	demand SLA guarantees such as low latency and high reliability and other 
	deterministic and precise properties especially in Wide Area Network (WAN) 
	applications.The uRLLC services should be provided in large-scale networks 
	which cover the  industries such as intelligent electrical network, intelligent 
	factory, internet of vehicles, industry automation and other industrial internet 
	scenarios. The industrial internet is the key infrastructure that coordinate various 
	units of work over various system components, e.g. people, machines and things 
	in the industrial environment including big data, cloud computing, Internet of 
	Things (IOT), Augment Reality (AR), industrial robots, Artificial Intelligence 
	(AI) and other basic technologies. For the intelligent electrical network, 
	there are deterministic requirements for communication delay, jitter and packet
	loss rate. For example, in the electrical current difference model, a delay of
	3~10ms and a jitter variation is no more than 100us are required. For the 
	automation control, it is one of the basic application and the the core is 
	closed-loop control system. The control process cycle is as low as millisecond 
	level, so the system communication delay needs to reach millisecond level or 
	even lower to ensure the realization of precise control. There are three 
	levels of real-time requirements for industrial interconnection: factory 
	level is about 1s, and process level is 10~100ms, and the highest real-time 
	requirement is motion control, which requires less than 1ms. So the 
	deterministic latency requirements are different with varying services 
	and network scenarios.</t>
   
    <t>As defined in <xref target="RFC8655" pageno="false" format="default"/>, the DetNet QoS can be expressed in terms of :
	Minimum and maximum end-to-end latency, bounded jitter (packet delay 
	variation), packet loss ratio and an upper bound on out-of-order packet 
	delivery.  As described in <xref target="RFC8578" pageno="false" format="default"/>, DetNet applications differ in their 
	network topologies and specific desired behavior and different services 
	requires differentiated DetNet QoS. In the large-scale networks, multiple 
	services with differentiated DetNet QoS is co-existed in the same DetNet 
	network. The classification of the deterministic flows within different 
	levels is should be taken into considerations. It is required to provide 
	Latency, bounded jitter and  packet loss dynamically and flexibly in all 
	scenarios for each characterized flow.</t>
	
	<t>As the Figure 1 shows, the services can be divided into 5 levels and level 
	2~5 is the DetNet flows and level-1 is non-DetNet flow.  DetNet applications 
	and DetNet QoS is differentiated within each level.</t>
	
   <figure title="The classification of multiple services" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
		 
   +-------------+-----------+----------+----------+----------+-----------+
   | Item        | Level-1   | Level-2  | Level-3  | Level-4  |  Level-5  |
   +-------------+-----------+----------+----------+----------+-----------+
   | Applications| Broadcast |  Voice   | Audio and| AR/VR    | Industrial|
   | Examples    |           |          | Video    |          |           |
   +-------------+-----------+----------+----------+----------+-----------+   
   | DetNet QoS  | Bandwidth | Jitter   | Delay    | Low      | Ultra-low |
   |             | Guarantee | Guarantee| Guarantee| delay    |  delay and|
   |             |           |          |          |and jitter|  jitter   |
   +-------------+-----------+----------+----------+----------+-----------+
  
   	   </artwork>
  <postamble/>
 </figure>
	
	<t>From the perspective of deterministic service requirements, 
	deterministic Quality of Service (QoS) in the network can be 
	divided into five types or levels:</t>
    <t>Level-1: bandwidth guarantee. The indicator requirements 
	include basic bandwidth guarantee and certain packet loss 
	tolerance. There is no requirement for the upper bound of 
	the latency, and no requirement for the jitter. Typical 
	services include download and FTP services.</t>	
    <t>Level-2: jitter guarantee. The indicator requirements 
	include: jitter 50ms, delay 300ms. Typical services include 
	synchronous voice services, such as voice call. </t>
    <t>Level-3: delay guarantee. The indicator requirements include: 
	delay 50ms, jitter 50ms. Typical services include real-time 
	communication services, such as video, production monitoring, 
	and communication services. </t>
    <t>Level-4: low delay and jitter guarantee. The indicator 
	requirements include: delay 20ms, jitter 5ms. Typical services 
	include video interaction services, such as AR/VR, holographic
	communication, cloud video and cloud games.</t>
    <t>Level-5: ultra-low delay and jitter guarantee. The indicator
	requirements include: delay 10ms, jitter 100us. Typical services 
	include production control services, such as power protection 
	and remote control.</t>
	
   <t>Moreover, different DetNet services is required to tolerate different 
	percentage of packet loss ratio such as 99.9%, 99.99%, 99.999%, and so on. </t>
  
   </section>
   <section title="Support the Utilization of Network Resources" numbered="true" toc="default">
   
   <t>Traditional Ethernet, IP and MPLS networks which is based on statistical
	multiplexing provides best-effort packet service and offers no delivery and 
	SLA guarantee. As described in <xref target="RFC8655" pageno="false" format="default"/>, the primary 
	technique by which DetNet achieves its QoS is to allocate sufficient resources.
	But it can not be achieved by not sufficient resource which can be allocated 
	due to practical and cost reason. So it is required to achieve the high-efficiency
	of resources utilization when provide the DetNet service.</t>
   </section>
   </section>   
	
   <section title="Characteristics of Large-Scale Deterministic Networks " numbered="true" toc="default">

   <section title="Large-scale Dynamic Flows " numbered="true" toc="default">
   
    <t>As described in <xref target="RFC8557" pageno="false" format="default"/>, deterministic forwarding can only apply to 
	flows with such well-defined characteristics as periodicity and burstiness. 
	As defined in DetNet architecture <xref target="RFC8655" pageno="false" format="default"/>, the traffic characteristics 
	of an App-flow can be CBR (constant bit rate) or VBR (variable bit rate) 
	of L1, L2 and L3 layers (VBR takes the maximum value when reserving resources). 
	But the current scenarios and technical solutions only consider CBR flow, 
	without considering the coexistence of VBR and CBR, the burst and aperiodicity
	of flows. The operations such as shaping or scheduling have not been specified.
	Even TSN mechanisms are based on a constant and forecastable traffic
    characteristics.</t>

    <t>It will be more complicated in a large-scale network where much more flows 
	coexist and the traffic characteristics is more dynamic. A huge number of 
	flows with different DetNet QoS requirements is dynamically concurrent 
	and the state of each flow cannot be maintained.  It is required to offer 
	reliable delivery and SLA guarantee for dynamic flows. For example,
	periodic flow and aperiodic flow (including micro burst flow, etc.), CBR 
	and VBR flow, flow with different periods or phases, etc. When the network
	needs to forward these deterministic flows at the same time, it must solve
	the problems of time micro bursts, queue processing and aggregation 
	of multiple flows. </t>
   
   </section>
   
   <section title="Large-scale Network Topology" numbered="true" toc="default">
   
    <t>In large-scale applications, the network topology may consists of a large 
	number of nodes and links which leads to difficulty with controlling the
	end-to-end delay and jitter. High speed, long-distance transmission and asymmetric
	links may also co-exists and affects the bounded latency such as increasing 
	transmission latency, jitter and packet loss in large-scale networks.</t>
	
	<t>The network topology in a large-scale network may across multiple 
	domains within a single administrative control or a closed group of 
	administrative control as per <xref target="RFC8655" pageno="false" format="default"/>. Moreover, DetNet domains or 
	nodes may be interconnected with different sub-network technologies 
	such as FlexE tunnels, TSN sub-network, IP/MPLS/SRv6 tunnels and so on.
	It is required to support the inter-domain deterministic
	metric and routes to achieve the end-to-end bounded latency.</t>

	</section>

   </section>
   
   <section title="Gap Analysis of Large-Scale Deterministic Networks" numbered="true" toc="default">
   
   <t>As defined in <xref target="RFC8938" pageno="false" format="default"/>, the DetNet data plane 
   describes how application flows, or App-flows are carried over DetNet networks 
   and it is provided by the DetNet service and forwarding sub-layers with DetNet-related
   data plane functions and mechanisms. This section analyzes the DetNet technical 
   gaps when applying the DetNet data plane as per RFC8938 in large-scale networks. </t>
      
   <section title="Gap Analysis of Providing Aggregated Flows Identification" numbered="true" toc="default">  
   
   <t>In <xref target="RFC8938" pageno="false" format="default"/>, the DetNet data plane can provide the DetNet-Specific 
   Metadata such as Flow-ID for both the service and forwarding sub-layers.
   The flow-based state information is required to be maintained 
   for per-flow processing rules. For example, the resource reservation 
   configuration is required for each flow. DetNet as per <xref target="RFC8938" pageno="false" format="default"/> 
   provides the capability to aggregate the individual flows to 
   downscale the operations of flow states. However, it still 
   requires large amount of control signaling to establish and 
   maintain DetNet flows. It may be challenging for network 
   operations with a large number of deterministic flows and network
   nodes in large-scale networks.</t>

   </section>
   
   <section title="Gap Analysis of Providing Deterministic Latency" numbered="true" toc="default"> 
   
   <t>As described in <xref target="RFC8655" pageno="false" format="default"/>, the primary goals are to achieve the 
   DetNet QoS to provide minimum and maximum end-to-end latency and
   bounded jitter, low packet loss ratio and an upper bound on 
   out-of-order packet delivery. But the data plane <xref target="RFC8938" pageno="false" format="default"/>
   particularly focuses on the DetNet service sub-layer which
   provides a set of Packet Replication, Elimination, and Ordering 
   Functions (PREOF) functions to provide end-to-end service assurance. 
   It mainly provides the capabilities for DetNet to guarantee the 
   reliability.</t>
   
   <t>The DetNet forwarding sub-layer provides corresponding
   forwarding assurance with IETF existing functions using resource 
   allocations and explicit routes. But these functions can not provide 
   the deterministic latency (bounded latency, low packet loss and in-order
   delivery) assurance in large-scale networks. The following sections
   mainly discuss the gap analysis for the forwarding sub-layer functions
   to provide deterministic latency assurance.</t>

    <section title="Gap Analysis of Explicit Routes" numbered="true" toc="default">
   
   <t>Traditional routes only have reachability. As per <xref target="RFC8938" pageno="false" format="default"/>,
   explicit optimized paths with allocation of resources should be
   provided to achieve the DetNet QoS. But the deterministic 
   requirements such as end-to-end delay and jitter are only used 
   as path computation constraints. Multiple network metrics
   which are measured and distributed by the routing system should
   be taken into consideration. </t> 
   
   <t>In large-scale networks, it may be challenging to compute the
   best path to meet all of the requirements. In multi-domain
   scenarios, the inter-domain deterministic routes need to be established
   and provisioned. Especially when interconnecting with sub-networks,
   the selection of intra-domain paths acrossing cooperating domains 
   should consider the bounded latency in each domain and the stitching
   of the paths.   </t>
   
   <t>Moreover, the paths vary with the real-time change of the network 
   topology. On the basic of the resources, the steering path and 
   routes for deterministic flows should be programmed before the flows coming 
   and able to provide SLA capability. And the routes should be considered to 
   be established in distributed and centralized control Plane.</t>

   <t>As described in <xref target="RFC8557" pageno="false" format="default"/>, the packet
   replication and elimination service protection should be provided to achieve the 
   low packet loss ratio. It will copy the flows and spread the data over multiple
   disjoint forwarding paths. The bounded latency and jitter of each path should
   be meet service deterministic requirement. And the difference of latency within
   these paths should be limited. So the replication and elimination deterministic 
   routes with configured latency and jitter policy should be taken into consideration. 
   It is required to generate two disjoint paths with very close delay to
   form 1+1 protection and perform concurrent transmission and dual reception, 
   and make replication and elimination on the egress PE. </t>  
   </section>
   
    <section title="Gap Analysis of Resources Allocation" numbered="true" toc="default">
  
   <t>As per <xref target="RFC8938" pageno="false" format="default"/>, the forwarding sub-layer uses buffer resources for
   packet queuing, as well as reservation and allocation of bandwidth
   capacity resources. In large-scale networks, the bandwidth, buffer 
   and scheduling resources are combined with queuing mechanisms to 
   guarantee the deterministic latency. The reservation and allocation
   of queuing related resources or deterministic latency resources 
   should be taken into consideration in DetNet data plane.</t>

   </section>

    <section title="Gap Analysis of Queuing Mechanisms" numbered="true" toc="default">
     
	<t>As per <xref target="RFC8938" pageno="false" format="default"/>, the forwarding sub-layer provides the QoS-related 
	functions needed by the DetNet flow including the use of queuing
    techniques. But the queuing techniques which are defined in existing 
	IETF technologies can not guarantee the bounded latency such as 
	Active Queue Management(AQM). And the queuing mechanisms which are
	defined in IEEE802.1 TSN can not be directly applied in large-scale 
	networks such Time Aware Shaping [IIEEE802.1Qbv] and Cyclic Queuing
	and Forwarding [IEEE802.1Qch] with time synchronization. </t>
	
	<t>Enhancement of queuing mechanisms have been discussed in DetNet 
	such as cyclic-scheduling queuing mechanism <xref target="I-D.dang-queuing-with-multiple-cyclic-buffers" format="default"/>,
	deadline-scheduling queuing mechanism <xref target="I-D.stein-srtsn" format="default"/> and 
	<xref target="I-D.peng-detnet-deadline-based-forwarding" format="default"/>, and 	
    asynchronous queuing mechanism <xref target="I-D.joung-detnet-asynch-detnet-framework" format="default"/>.
	The function of multiple queuing mechanisms and related DetNet-Specific 
	Metadata has not been defined in DetNet data plane.</t>
 

   </section>
   
   
   </section>

   </section>
  


   
   <section title="Security Considerations">
    <t>TBA</t>
   </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>TBA</t>
    </section>
	
	<section anchor="IANA" title="IANA Considerations">
	 <t>TBA</t>
	 
    </section>
	
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
  
    <references title="Normative References">
    <?rfc include='reference.RFC.2119'?>
	<?rfc include='reference.RFC.8174'?>
	<?rfc include='reference.RFC.8655'?>
	<?rfc include='reference.RFC.8938'?>
    <?rfc include='reference.RFC.8964'?>
    <?rfc include='reference.RFC.8956'?>	
	<?rfc include='reference.RFC.9023'?>
    <?rfc include='reference.RFC.9024'?>
    <?rfc include='reference.RFC.8578'?>
	<?rfc include='reference.RFC.8557'?>
	<?rfc include='reference.I-D.stein-srtsn'?>
    <?rfc include='reference.I-D.peng-detnet-deadline-based-forwarding'?>
    <?rfc include='reference.I-D.dang-queuing-with-multiple-cyclic-buffers'?>
    <?rfc include='reference.I-D.joung-detnet-asynch-detnet-framework'?>
	
	

    </references>
        
  </back>
</rfc>
