<?xml version='1.0' encoding='ascii'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-xiong-detnet-6man-queuing-option-00" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
  <!-- ***** FRONT MATTER ***** -->
  <front>
    <title abbrev="DetNet Queuing Option for IPv6">DetNet Queuing Option for IPv6</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/>

        <email>xiong.quan@zte.com.cn</email>
      </address>
    </author>
	
	<author fullname="Aihua Liu" initials="A" surname="Liu">
      <organization>ZTE Corporation</organization>

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

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

        <phone/>

        <email>liu.aihua@zte.com.cn</email>
      </address>
    </author>
   
    
   <date month="April" year="2022"/>	
    <area>Routing</area>
    <workgroup>DETNET</workgroup>
    <keyword/>
    <abstract>
	
	<t> This document introduces new IPv6 options to signal the DetNet queuing 
    related information for DetNet flows in IPv6 and SRv6 networks.</t>
	 
    </abstract>
  </front>

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

  <middle>
  
    <section title="Introduction" numbered="true" toc="default">
	
	<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. 
    DetNet data planes has been specified in <xref target="RFC8938" pageno="false" format="default"/>.
	The existing deterministic technologies are facing large-scale number 
	of nodes and long-distance transmission, traffic scheduling, dynamic 
	flows, and other controversial issues in large-scale networks. 
	[draft-liu-detnet-large-scale-requirements] has described the 
	enhancement requirements for DetNet data plane.</t>
	
	<t>It is required to support a data plane method of packet treatment 
    including forwarding, service protection, and queuing over Layer 3.
	As defined in <xref target="RFC8939" pageno="false" format="default"/>, 
	the DetNet IP data plane primarily uses 6-tuple-based flow identification. 
	It is required to carry Redundancy information for service protection 
	enhancement and explicit path indicator for forwarding enhancement 
	in a native IP packet such as IPv6 and SRv6. The [draft-pthubert-detnet-ipv6-hbh]
    has proposed Redundancy Information Option and Path Options for
	IPv6 and SRv6 data plane.</t>
	
    <t>As described in [draft-ietf-detnet-bounded-latency],
	the end-to-end bounded latency depends on the value of queuing delay 
	bound along with the queuing mechanisms. Mutiple queueing mechanisms 
	can be used to ganrantee the bounded latency in DetNet. And many types 
	of queueing mechanisms have been proposed to provide diversified 
	deterministic service for various applications. For example, 
	time-scheduling queuing mechanisms includes the Time Aware 
	Shaping [IIEEE802.1Qbv] and priority-scheduling includes the 
	Credit-Based Shaper[IEEE802.1Q-2014] with Asynchronous Traffic
    Shaping[IEEE802.1Qcr]. The cyclic-scheduling queueing mechanism 
	has been proposed in [IEEE802.1Qch] and improved in [draft-dang-queuing-with-multiple-cyclic-buffers].
    The deadline-scheduling queueing mechanism has been proposed in 
	[draft-stein-srtsn] and improved in [draft-peng-detnet-deadline-based-forwarding].	
    The per-flow queueing mechanism includes Guaranteed-Service Integrated 
	service (IntServ) [RFC2212]. It is required to carry queuing 
	related information in data plane so as to make appropriate packet 
	forwarding and scheduling decisions to meet the time bounds.
	The DetNet forwarding nodes along the path can follow the 
	queue scheduling carried in the packet to achieve the 
	end-to-end bounded latency.</t>
	
	<t>This document introduces new IPv6 options to signal 
	the DetNet queuing related information for DetNet flows in 
	IPv6 and SRv6 networks.</t>
  
   </section>

    <section title="Conventions used in this document" numbered="true" toc="default">	 	
    <section title="Terminology" numbered="true" toc="default">
	<t>The terminology is defined as <xref target="RFC8655" pageno="false" format="default"/>.</t>
   </section>
   
   <section title="Requirements Language" numbered="true" toc="default">
    <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 title="The DetNet Options" numbered="true" toc="default">
   <t>This document defines new IPv6 options for DetNet to signal queuing 
   information to the DetNet layers. The format of the options follow the 
   generic definition in section 4.2 of [RFC8200]. The option may be placed
   either in an HbH or a DoH EH.</t>
   
   <section title="The Queuing information Option" numbered="true" toc="default">
   
   <t>The DetNet Queuing Information Option helps to discriminate
   the types of queuing mechanisms and specify the queuing parameters.</t>
   
      <figure title="Queuing Information Option Format" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">

0                   1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Option Type  |  Opt Data Len | Queuing Type  | TU| QDL | QPL | 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Maximum Queuing Delay (variable)                     | 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Maximum Queuing Delay variation (variable)           | 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Queuing Parameters (variable) (optional)             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
  
   	   </artwork>
  <postamble/>
 </figure>
 
   <t>Option Type: 8-bit identifier of the type of option.  Value TBD by
   IANA; the highest-order 3 bits of thie field is 001 to skip over this
   option and continue processing the header if the processing IPv6 node
   does not recognize the Option Type and to permit the Option Data to
   be changed en route to the packet's final destination.</t>

   <t>Opt Data Len: 8-bit unsigned integer. Length of the Option Data
   field of this option, in octets.  It is set to 12.</t>
   
   <t>Queuing Type(8 bits): indicates the type of queuing mechanisms.
   The types of queuing mechanisms should cover time-scheduling, 
   priority-scheduling, cyclic-scheduling, deadline-scheduling and 
   per-flow scheduling queuing mechanisms. Other type of queuing 
   mechanisms can be taken into considerations in the future.</t>
   
   <t>TU(2 bits): indicates the time units for Queuing Delay.</t>
   
   <t>ODL(3 bits): Length of the Queuing Delay field as an unsigned 3-bit integer.</t>
   
   <t>OPL(3 bits): Length of the Queuing Parameters field as an unsigned 3-bit integer.</t>
   
   <t>Maximum Queuing Delay (variable): indicates the Maximum queuing 
   delay. The value is various when the Queuing type is different.</t>
   
   <t>Maximum Queuing Delay variation (variable): indicates the 
   Maximum queuing delay variation. The value is various when the 
   Queuing type is different.</t>
   
   <t>Queuing Parameters(variable): it is optional and based on the 
   Queuing type. For example, Cycle Profile ID and Cycle ID may be 
   carried for cyclic-scheduling queuing mechanisms. Deadline-scheduling
   queuing mechanisms should carry information such as planned Deadline
   and deadline Deviation and so on.</t>
   
   </section>
   
   </section>
   
   <section title="Encapsulation of DetNet Options" numbered="true" toc="default">
   <section title="IPv6 Networks" numbered="true" toc="default">
   
   <t>The DetNet Queuing information Option is intended to be placed in an 
   IPv6 HbH EH since it must be processed by every DetNet forwarding node 
   along the path. All DetNet forwarding nodes can use the queuing 
   information to achieve the packet forwarding and queue scheduling.</t>
   
         <figure title="Queuing Information Option Format" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">
		 
            +-----------------------------------+
            |         DetNet App-Flow           |
            |       (original IP) Packet        |
            +-----------------------------------+
            |            other EHs              |
            +-----------------------------------+--\
            |        IPv6 Hop-by-Hop Ex Hdr     |    |
            |(DetNet Queuing information Option)| DetNet Options
            |                                   |    |
            +-----------------------------------+--/
            |            IPv6 Header            |
            +-----------------------------------+
            |             Data-Link             |
            +-----------------------------------+
            |             Physical              |
            +-----------------------------------+
			
   	   </artwork>
  <postamble/>
 </figure>
   
   </section>
   
   <section title="SRv6 Networks" numbered="true" toc="default">
   
   <t>The DetNet Queuing information Option is intended to be placed in an 
   DOH EH before an SRH since it must be processed by the DetNet forwarding 
   nodes of the SRv6 segment list. The DetNet forwarding nodes among 
   SRv6 segment list can use the queuing information to achieve 
   the packet forwarding and queue scheduling.</t>
 
         <figure title="Queuing Information Option Format" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">


            +-----------------------------------+
            |         DetNet App-Flow           |
            |       (original IP) Packet        |
            +-----------------------------------+
            |       Segment Routing Header      |
            +-----------------------------------+ ---\
            |        IPv6 Destination Ex Hdr    |    |
            |(DetNet Queuing information Option)| DetNet Options
            |                                   |    |
            +-----------------------------------+ ---/
            |            IPv6 Header            |
            +-----------------------------------+
            |             Data-Link             |
            +-----------------------------------+
            |             Physical              |
            +-----------------------------------+
  
   	   </artwork>
  <postamble/>
 </figure>
   
   </section>
   

   </section>
   
   <section title="Security Considerations" numbered="true" toc="default">
    <t>TBA</t>
   </section>

    <section anchor="Acknowledgements" title="Acknowledgements" numbered="true" toc="default">
    <t>The authors would like to thank Peng Liu, Bin Tan, Aihua Liu 
	Shaofu Peng for their review, suggestions and comments to this document.</t>
    </section>
	
	<section anchor="IANA" title="IANA Considerations" numbered="true" toc="default">
	<t>TBA</t>
    </section>

	
  </middle>

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

  <back>
  
    <references title="Normative References">
    <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="S. Bradner"><organization/></author>
<date year="1997" month="March"/>
<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="RFC8655" target="https://www.rfc-editor.org/info/rfc8655">
<front>
<title>Deterministic Networking Architecture</title>
<author initials="N." surname="Finn" fullname="N. Finn"><organization/></author>
<author initials="P." surname="Thubert" fullname="P. Thubert"><organization/></author>
<author initials="B." surname="Varga" fullname="B. Varga"><organization/></author>
<author initials="J." surname="Farkas" fullname="J. Farkas"><organization/></author>
<date year="2019" month="October"/>
<abstract><t>This document provides the overall architecture for Deterministic Networking (DetNet), which provides a capability to carry specified unicast or multicast data flows for real-time applications with extremely low data loss rates and bounded latency within a network domain.  Techniques used include 1) reserving data-plane resources for individual (or aggregated) DetNet flows in some or all of the intermediate nodes along the path of the flow, 2) providing explicit routes for DetNet flows that do not immediately change with the network topology, and 3) distributing data from DetNet flow packets over time and/or space to ensure delivery of each packet's data in spite of the loss of a path.  DetNet operates at the IP layer and delivers service over lower-layer technologies such as MPLS and Time- Sensitive Networking (TSN) as defined by IEEE 802.1.</t></abstract>
</front>
<seriesInfo name="RFC" value="8655"/>
<seriesInfo name="DOI" value="10.17487/RFC8655"/>

</reference><reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
<author initials="B." surname="Leiba" fullname="B. Leiba"><organization/></author>
<date year="2017" month="May"/>
<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><reference anchor="RFC8938" target="https://www.rfc-editor.org/info/rfc8938">
<front>
<title>Deterministic Networking (DetNet) Data Plane Framework</title>
<author initials="B." surname="Varga" fullname="B. Varga"><organization/></author>
<date year="2020" month="November"/>
<abstract><t>This document provides an overall framework for the Deterministic Networking (DetNet) data plane.</t></abstract>
</front>
<seriesInfo name="RFC" value="8938"/>
<seriesInfo name="DOI" value="10.17487/RFC8938"/>

</reference><reference anchor="RFC8939" target="https://www.rfc-editor.org/info/rfc8939">
<front>
<title>Deterministic Networking (DetNet) Data Plane: IP</title>
<author initials="G." surname="Varga" fullname="G. Varga" role="editor"><organization/></author>
<date year="2020" month="November"/>
<abstract><t>This document specifies the Deterministic Networking (DetNet) data plane operation for IP hosts and routers that provide DetNet service to IP-encapsulated data.</t></abstract>
</front>
<seriesInfo name="RFC" value="8939"/>
<seriesInfo name="DOI" value="10.17487/RFC8939"/>
</reference></references>
        
  </back>
</rfc>
