<?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-detnet-differentiated-detnet-qos-01"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">

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

 <front>

   <title abbrev="Differentiated DetNet QoS for Deterministic Services">Differentiated DetNet QoS for Deterministic Services</title>
    <seriesInfo name="Internet-Draft" value="draft-xiong-detnet-differentiated-detnet-qos-01"/>

   <author fullname="Quan Xiong" initials="Q" role="editor" 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="Junfeng Zhao" initials="J" surname="Zhao">
      <organization>CAICT</organization>

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

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

        <phone></phone>

        <email>zhaojunfeng@caict.ac.cn</email>
      </address>
    </author>	
	
    <author fullname="Zongpeng Du" initials="Z" surname="Du">
      <organization>China Mobile</organization>

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

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

        <phone></phone>

        <email>duzongpeng@chinamobile.com</email>
      </address>
    </author>
	
    <author fullname="Qimiao Zeng" initials="Q" surname="Zeng">
      <organization>China Telecom</organization>
      <address>
        <postal>
          <street></street>
          <city> </city>
          <region/>
          <code></code>
          <country>China</country>
        </postal>
        <phone></phone>
        <email>zengqm@chinatelecom.cn</email>
      </address>
    </author>
	
	<author fullname="Chang Liu" initials="C" surname="Liu">
      <organization>China Unicom</organization>
      <address>
        <postal>
          <street>No.9 Shouti Nanlu</street>
          <city>Beijing </city>
          <region/>
          <code>100048</code>
          <country>China</country>
        </postal>
        <phone>+86-010-68799999-7294</phone>
        <email> liuc131@chinaunicom.cn</email>
      </address>
    </author>
	
	
	

   <area>Routing</area>
    <workgroup>DetNet</workgroup>
   <keyword></keyword>
   
   <abstract>
   
      <t>This document describes the service requirements of scaling deterministic
	  networks and proposes Differentiated DetNet QoS (DD-QoS) for deterministic
	  services in enhanced DetNet.</t>
	  
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default"> <name>Introduction</name>
	  
	  
	  <t>According to <xref target="RFC8655" pageno="false" format="default"/>, Deterministic Networking (DetNet) 
	  operates at the IP layer and delivers service which provides 
	  extremely low data loss rates and bounded latency within a network domain. 
	  The DetNet Quality of Service (QoS) includes the bounded latency indicating the minimum and 
	  maximum end-to-end latency from source to destination and bounded 
	  jitter (packet delay variation). Three techniques are used by DetNet 
	  to provide these qualities of service including service protection, 
	  explicit routes and resource allocation. </t>
	  
	  <t><xref target="I-D.ietf-detnet-scaling-requirements" pageno="false" format="default"/> 
	  has mentioned the enhanced DetNet should support different levels of 
	  application requirements which is important for the DetNet deployment. 
	  <xref target="I-D.zhao-detnet-enhanced-use-cases" pageno="false" format="default"/> 
	  has described enhanced use cases and network requirements for
      scaling deterministic networks and seven levels of typical applications
	  have been defined. Different levels of applications differ in the 
	  network ranges and SLAs requirements. Moreover, multiple services and 
	  traffic flows with different bounded latency requirements may be also
	  co-existed in the same application. Multiple deterministic services 
	  may demand different set of SLAs and it may define more than one DetNet
	  QoS levels according to different application scenarios. These flows 
	  should be transmitted and forwarded with different DetNet QoS behaviors. 
	  From the use cases 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. </t>
	  
	  <t>This document describes the service requirements of scaling deterministic
	  networks and proposes Differentiated DetNet QoS (DD-QoS) for deterministic
	  services in enhanced DetNet.</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", "MAY", and "OPTIONAL" in this
       document are to be interpreted as described in <xref target="RFC2119" format="default">RFC 2119</xref>.</t>
	   
      </section>
    </section>
	
    <section anchor="Terminology" numbered="true" toc="default"> <name>Terminology</name>
	<t>The terminology is defined as <xref target="RFC8655" pageno="false" format="default"/>.</t>
	<t>DD-QoS: Differentiated DetNet QoS</t>
	<t>DC: DetNet Traffic Class</t>
    </section>
	
	
   <section numbered="true" toc="default"> <name>Service Requirements of Scaling Deterministic Networks</name>

   <section numbered="true" toc="default"> <name>Support Different Levels of Applications Co-existed with Differentiated SLAs</name>
   
   	<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 per <xref target="I-D.zhao-detnet-enhanced-use-cases" pageno="false" format="default"/>, various deterministic
	applications are co-existed with different SLAs guarantees in scaling 
	networks and these applications can be classified into different levels. 
    As per <xref target="I-D.ietf-detnet-scaling-requirements" pageno="false" format="default"/>,
	the enhanced DetNet should support different levels of application requirements
	and different levels of deterministic applications demand different 
	DetNet technologies in scaling deterministic networks.
	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 large-scale networks, multiple 
	services with differentiated DetNet QoS can be co-existed in the same DetNet 
	network. The classification of the deterministic flows within different 
	levels 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 Different Levels of Applications" 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  |Email    |  Voice    | Audio and | AR/VR    | Industrial |
|Examples      |         |           | Video     |          |            |
+--------------+---------+-----------+-----------+----------+------------+   
|Differentiated|N/A      |delay&lt;300ms|delay&lt;50ms |delay&lt;20ms|delay&lt;10ms  |                           
|SLAs          |         |jitter&lt;50ms|jitter&lt;50ms|jitter&lt;5ms|jitter&lt;100us|
+--------------+---------+-----------+-----------+----------+------------+   
|DetNet QoS    |Bandwidth|Jitter     | Delay     | Low      | Ultra-low  |
|Forwarding    |Guarantee|Guarantee  | Guarantee | delay    |  delay and |
|Behaviors     |         |           |           |and jitter|  jitter    |
+--------------+---------+-----------+-----------+----------+------------+
   
  
   	   </artwork>
 </figure>
	
	<t>From the perspective of deterministic service requirements, 
	deterministic 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&lt;50ms, delay&lt;300ms. Typical services include 
	synchronous voice services, such as voice call. </t>
    <t>Level-3: delay guarantee. The indicator requirements include: 
	delay&lt;50ms, jitter&lt;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&lt;20ms, jitter&lt;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&lt;10ms, jitter&lt;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 numbered="true" toc="default"> <name>Support High Utilization of Network Resources</name>
   
   <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 services.</t>
   </section>
   </section>   
	
	
	
   <section numbered="true" toc="default"> <name>Pre-defined Classes for Differentiated DetNet QoS</name>
   
   <t>As per <xref target="RFC8655" pageno="false" format="default"/>,
   an important goal of the DetNet QoS is the bounded 
   latency including the minimum and maximum end-to-end latency 
   from source to destination, and bounded jitter.
   From the services requirements, a scaling network in enhanced DetNet 
   needs to provide the deterministic services for various applications. 
   The deterministic services may demand differentiated SLAs and different
   bounded latency guarantees. So multiple DetNet QoS levels should be 
   supported according to different application scenarios. Moreover, as 
   per <xref target="RFC8938" pageno="false" format="default"/>, 
   the aggregation of individual flows may be still challenging for network 
   operations with a large number of deterministic flows and network
   nodes in large-scale networks. It may provide aggregation based on
   pre-defined classes to resolve the scaling issues.</t>
   
   <t> The differentiated QoS MAY be classified based on the applications in
   scaling networks. This document proposed the DetNet Traffic Class (DC) to 
   indicate the pre-defined classes for Differentiated DetNet QoS (DD-QoS). 
   The DetNet traffic class may be divided into 4 types:</t>
   
  <figure title="Traffic class for Differentiated DetNet QoS" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
		 
   +--------------+-----------+----------+----------+-----------+-----------+   
   |Differentiated| Bandwidth | Jitter   | Delay    | Low       | Ultra-low |
   |DetNet QoS    | Guarantee | Guarantee| Guarantee| delay and |  delay and|
   |Forwarding    |           |          |          | and jitter|  jitter   |
   |Behaviors     |           |          |          |           |           |
   +--------------+-----------+----------+----------+-----------+-----------+
   | DetNet       |           |          |          |           |           |
   | Traffic      |Best-effort|  DC-1    |  DC-2    |  DC-3     |   DC-4    | 
   | Class        |           |          |          |           |           |
   +--------------+-----------+----------+----------+-----------+-----------+
   	   </artwork>
 </figure>
 
 <t> Different QoS class indicates different levels of applications with SLAs 
 requirements and each class demands differentiated QoS behaviors as well as 
 different DetNet capabilities in scaling network. For example, the behaviors 
 of jitter guarantee and delay guarantee may implement different queuing mechanisms.
 Each QoS class can be divided into serveral sub-classes based on the SLAs 
 requirements of the applications.</t>
   
   </section>
   
   <section  numbered="true" toc="default"> <name>Security Considerations</name>
    <t>Security considerations for DetNet are covered in the DetNet
   Architecture <xref target="RFC8655"></xref> and DetNet data plane
   <xref target="RFC8938"></xref>, <xref target="RFC8939"></xref>, 
   <xref target="RFC8964"></xref> and DetNet security considerations
   <xref target="RFC9055"></xref>. The security considerations 
   specified in <xref target="I-D.ietf-detnet-scaling-requirements"></xref> are also
   applicable to the procedures defined in this document.</t>
   </section>
   <section numbered="true" toc="default"> <name>IANA Considerations</name>
   <t>There might be no IANA register request in this document.</t>   
   </section>
   <section numbered="true" toc="default"> <name>Acknowledgements</name>
   <t>The authors would like to acknowledge Tianji Jiang, Aihua Liu, 
   Bin Tan for the 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.5440.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.8231.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7752.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5120.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4915.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4655.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6549.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8578.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.8655.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9357.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9320.xml"/>	
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8233.xml"/>
	    <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8938.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8939.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9055.xml"/>
	    <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8964.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-detnet-scaling-requirements.xml"/>        
		<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-zhao-detnet-enhanced-use-cases.xml"/>
		
      </references>
    </references>
 
 </back>
</rfc>
