<?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="std"
      docName="draft-xiong-lsr-deterministic-link-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="IGP Extensions for Deterministic Link">IGP Extensions for Deterministic Link</title>
    <seriesInfo name="Internet-Draft" value="draft-xiong-lsr-deterministic-link-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="Xiangyang Zhu" initials="X"  surname="Zhu">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <street/>
         <city></city>
          <region/>
          <code/>
          <country>China</country>
        </postal>
        <phone></phone>
        <email>zhu.xiangyang@zte.com.cn</email>
     </address>
    </author>

   <area>Routing</area>
    <workgroup>LSR</workgroup>
   <keyword></keyword>
   
   <abstract>
    <t>This document proposes the deterministic link to provide an 
	one-dimensional metric to indicate the deterministic forwarding
	capabilities at different levels and proposes the deterministic 
	links distribution by IGP extensions.</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 bounded latency indicates the minimum and 
	  maximum end-to-end latency from source to destination and bounded jitter
	  (packet delay variation).  <xref target="I-D.ietf-detnet-scaling-requirements"></xref>
	  has described the enhanced requirements for DetNet enhanced data plane
	  including the deterministic latency guarantees. As per 
	  <xref target="I-D.ietf-detnet-controller-plane-framework" pageno="false" format="default"/>, 
	  network nodes need to collect topology information and deterministic
	  capabilities through IGP. </t>
	  
	  <t>The computing method of end-to-end delay bounds is defined in <xref target="RFC9320" pageno="false" format="default"/>.
	  It is the sum of the six delays in bounded latency model. It is
      the sum of non-queuing delay bound and queuing delay bound.
	  The upper bounds of queuing delay depends on the queuing
	  mechanisms deployed along the path. For example, a link with a 
	  queuing mechanism that does not guarantee a bounded delay is a 
	  non-deterministic link and a link with a time-based queuing 
	  mechanism that can provide deterministic latency guarantee is 
	  called a deterministic link. The delay of a deterministic link
	  is consist of the propagation delay of the packet on the link 
	  and the queuing delay of the packet at the node. A deterministic
	  link can be a sub-network that provides deterministic transmission
	  or a Point-to-Point (P2P) link. </t>
	  
	  <t>This document proposes the deterministic link to provide an
	  one-dimensional metric to indicate the deterministic forwarding 
	  capabilities at different levels and proposes the deterministic 
	  links distribution by IGP extensions.</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"/> and
	<xref target="RFC9320" pageno="false" format="default"/>.</t>
     
    </section>
	
   <section numbered="true" toc="default"><name>Deterministic Link</name>
   
   <t>This document proposes the deterministic link to provide an one-dimensional
   metric to indicate the deterministic forwarding capabilities at different
   levels. The deterministic links can shield the differences from
   underlying forwarding mechanisms.</t>
   
   <section numbered="true" toc="default"> <name>Deterministic Link Model</name>
   
   <t>As per <xref target="RFC9320" pageno="false" format="default"/>, six types of
   delays are defined in timing Model of DetNet. And the DetNet domain can also 
   be modeling as deterministic links and nodes as shown in Figure 1. The 
   deterministic node delay is constant while the deterministic link delay is 
   variable within bounded latency. The end-to-end bounded latency depends on 
   the sum of the deterministic link delay.</t>
   
   <ul spacing="normal">
   <li>Deterministic Link Delay =  Regulation delay + Queuing subsystem delay + 
			Output delay + Link delay + Frame preemption delay</li>
   <li>Deterministic Node Delay = Processing delay</li>
   </ul>
   
      	<figure title="Deterministic Link Model" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
   
           DetNet transit node A                 DetNet transit node B
      +-------------------------+             +------------------------+
      |              Queuing    |             |              Queuing   |
      |   Regulator subsystem   |             |   Regulator subsystem  |
      |   +-+-+-+-+ +-+-+-+-+   |             |   +-+-+-+-+ +-+-+-+-+  |
   -->+   | | | | | | | | | +   +------------>+   | | | | | | | | | +  +--->
      |   +-+-+-+-+ +-+-+-+-+   |             |   +-+-+-+-+ +-+-+-+-+  |
      |                         |             |                        |
      +-------------------------+             +------------------------+
      |-->|------->|------->|-->|------------>|-->|------->|------>|-->|-->|
  2,3  4      5        6      1      2,3       4      5        6     1   2,3
          |---- Deterministic Link Delay ---->| 
          
                 Deterministic Links     Deterministic Node
      | A |---------------------------------->| B |----------------------->| 
			
   	   </artwork>
 </figure>

   </section>
   
   <section numbered="true" toc="default"> <name>Classification of Deterministic Links</name>
   
   <t>There are a number of deterministic links between deterministic nodes.
   And each deterministic link provides different level of deterministic 
   forwarding capabilities indicated by Deterministic Class-Type (DT).</t>
   
   <t>Deterministic Class-Type (DT): indicate the set of Traffic Trunks
   crossing a deterministic link that is governed by a specific set of 
   bounded latency constraints and QoS requirements of deterministic
   guarantees such as tight jitter,strict latency, loose latency and 
   so on. DT is used for the purposes of deterministic link resource 
   planning, reservation and allocation, deterministic link resource
   constraint-based routing and admission control. A given Traffic 
   Trunk belongs to the same DT on all links. </t>
   
   <t>The scheduling type of the deterministic link depends on the
   classification of the queuing solutions. Many variations and 
   extensions of queuing mechanisms have been proposed to guarantee 
   the deterministic latency in DetNet such as ECQF [IEEE 802.1Qdv], 
   Multi-CQF <xref target="I-D.dang-queuing-with-multiple-cyclic-buffers"></xref>,
   TCQF <xref target="I-D.eckert-detnet-tcqf"></xref>,
   CSQF <xref target="I-D.chen-detnet-sr-based-bounded-latency"></xref>,
   TQF <xref target="I-D.peng-detnet-packet-timeslot-mechanism"></xref>,
   C-SCORE <xref target="I-D.joung-detnet-stateless-fair-queuing"></xref>,
   EDF<xref target="I-D.peng-detnet-deadline-based-forwarding"></xref>,
   gLBF <xref target="I-D.eckert-detnet-glbf"></xref> and so on.
   <xref target="I-D.ietf-detnet-dataplane-taxonomy"></xref>
   has described the classification criteria of the solutions.</t>
   
   <t><xref target="I-D.xiong-lsr-time-resource"></xref> has proposed the Time-based
   Resources Container (TRC) to indicate the capabilities with time-based
   resources. It can be used for deterministic link to reserve the 
   corresponding scheduling resources such as queuing, buffer and bandwidth 
   to guarantee the deterministic capability.</t>  
   
   <t>For example, three deterministic links with guaranteed jitter 
   are supported between the Node A and Node B as following shown.</t>
   
   <ul spacing="normal">
   <li>deterministic link 1, DT=1 (Jitter Guarantee, Link-scheduling-type=CSQF), bandwidth=20Mbit/s, jitter=10us.</li>
   <li>deterministic link 2, DT=2 (Jitter Guarantee, Link-scheduling-type=TCQF), bandwidth=30Mbit/s, jitter=20us.</li>
   <li>deterministic link 3, DT=3 (Jitter Guarantee, Link-scheduling-type=TQF), bandwidth=40Mbit/s, jitter=30us.</li>
   </ul>
   </section>
   
   
   </section>
  
	 
<section numbered="true" toc="default"> <name>ISIS Extensions of Deterministic Link</name>

   <t>This document defines new IS-IS TE sub-TLVs to distribute the
    deterministic link attributes at TE link and it can be announced
    in TLVs 22, 23, 141, 222, and 223" registry. </t>
	
<section numbered="true" toc="default"> <name>Deterministic Link Sub-TLV</name>	
   
   <t>A new IS-IS Deterministic Link Sub-TLV is defined and the format
   is as shown in the following figure.</t>
   
   
	<figure title="Deterministic Link Sub-TLV" 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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Type               |           Length              |    
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               DT            |     Link Scheduling Type      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~                        Sub-sub-TLV                          ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   
   
   	   </artwork>
 </figure>
 
 <t>where:</t>
 
 	 <ul spacing="normal">
	 
	 <li>Type: Set to TBD1.</li>
	 
	 <li>Length: Contains the total length of the sub-TLV in octets.  
	The Length MUST be at least 8 and MUST be a multiple of 4.</li>
	 
	 <li>DT: the value of DT to indicates the set of Traffic Trunks
     crossing the deterministic link that is governed by a specific
	 set of bounded latency constraints.</li>
	 
	 <li>Link Scheduling Type: indicates the type of the queuing or 
	 scheduling mechanisms on this deterministic link.</li>
	 
	 <li>Sub-sub-TLV: indicates the optional sub-sub-TLV carried in
	 this sub-TLV. </li>
	  </ul>
	  
	  
   <section numbered="true" toc="default"> <name>Deterministic Link Maximum Reservable Bandwidth Sub-sub-TLV</name>
   
    <t>A new IS-IS Deterministic Link Maximum Reservable Bandwidth Sub-sub-TLV 
	is defined and the format is as shown in the following figure.</t>	
	
	<figure title="Deterministic Link Maximum Reserved Bandwidth sub-sub-TLV" 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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Type               |           Length              |    
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               Maximum Reservable Bandwidth                  |     
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   
   	   </artwork>
 </figure>
 
 <t>where:</t>
 
 	 <ul spacing="normal">
	 
	 <li>Type: Set to TBD2.</li>
	 
	 <li>Length: Contains the total length of the sub-sub-TLV in octets.  
	The Length MUST be at least 8 and MUST be a multiple of 4.</li>
	
	 <li>Maximum Reservable Bandwidth: indicates the maximum bandwidth
	 which can be reserved for this deterministic link. </li>
	 </ul>
	 
	 </section>
	 

   <section numbered="true" toc="default"> <name>Deterministic Link Available Bandwidth Sub-sub-TLV</name>	 
	
    <t>A new IS-IS Deterministic Link Available Bandwidth Sub-sub-TLV 
	is defined and the format is as shown in the following figure.</t>	
	
	<figure title="Deterministic Link Available Bandwidth sub-sub-TLV" 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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Type               |           Length              |    
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Available Bandwidth                        |     
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   
   	   </artwork>
 </figure>
 
 <t>where:</t>
 
 	 <ul spacing="normal">
	 
	 <li>Type: Set to TBD3.</li>
	 
	 <li>Length: Contains the total length of the sub-sub-TLV in octets.  
	The Length MUST be at least 8 and MUST be a multiple of 4.</li>
	
	 <li>Available Bandwidth: indicates the available bandwidth of
	 this deterministic link. </li>
	 </ul>
	</section>
	
  <section numbered="true" toc="default"> <name>Deterministic Link Delay Sub-sub-TLV</name>	 	
 
    <t>A new IS-IS Deterministic Link Delay Sub-sub-TLV is defined and the format
   is as shown in the following figure.</t>
 
 	<figure title="Deterministic Link Delay sub-sub-TLV" 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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Type               |           Length              |    
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |A| Reserved  |           Maximum Deterministic Link Delay    |     
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Reserved  |           Minimum Deterministic Link Delay    |    
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Reserved  |  Maximum Deterministic Link Delay Variation   |    
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   
   	   </artwork>
 </figure>
 
  <t>where:</t>
 
 	 <ul spacing="normal">
	 
	 <li>Type: Set to TBD4.</li>
	 
	 <li>Length: Contains the total length of the sub-sub-TLV in octets.  
	The Length MUST be at least 8 and MUST be a multiple of 4.</li>
	
	 <li>A: The A bit represents the Anomalous (A) bit. The A bit is set
     when the measured value of this parameter exceeds its configured
     maximum threshold. </li>
	 
	 <li>Maximum Deterministic Link Delay: indicates the maximum
	 deterministic link delay value (in microseconds) over a 
	 configurable interval, encoded as an integer value.</li>
	 
    <li>Minimum Deterministic Link Delay: indicates the minimum
	 deterministic link delay value (in microseconds) over a 
	 configurable interval, encoded as an integer value.</li>

    <li>Maximum Deterministic Link Delay Variation: indicates the 
	maximum deterministic link delay variation value over a 
	configurable interval in microseconds, encoded as an
    integer value.</li>	 
	 </ul>
	 
	 </section>
	 
</section>



</section>
	
   <section numbered="true" toc="default"> <name>OSPF Extensions of Deterministic Links</name>
   <t>TBA</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 controller plane
   <xref target="I-D.ietf-detnet-controller-plane-framework"></xref> 
   and DetNet security considerations <xref target="RFC9055"></xref>. The 
   security considerations specified in <xref target="RFC5304"></xref> 
   are also applicable to the IGP procedures defined in this document.</t>
   </section>
   
   <section numbered="true" toc="default"> <name>IANA Considerations</name>
    <t>IANA is requested to register the following sub-TLVs
	in the "Sub-TLVs for TLVs 22, 23, 141, 222,and 223" registry:</t>
	
<artwork><![CDATA[

    Type    Description
   ------------------------------------
    TBD1    Deterministic Link Sub-TLV
    TBD2    Deterministic Link Maximum Reservable Bandwidth Sub-sub-TLV
    TBD3    Deterministic Link Available Bandwidth Sub-sub-TLV 
    TBD4    Deterministic Link Delay Sub-sub-TLV
]]></artwork>
   
   </section>
	
   <section numbered="true" toc="default"> <name>Acknowledgements</name>
   <t>The authors would like to acknowledge Aihua Liu, 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.8655.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.5304.xml"/>	
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9055.xml"/>
		<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-detnet-dataplane-taxonomy.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-ietf-detnet-controller-plane-framework.xml"/>	 
		<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-eckert-detnet-tcqf.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-dang-queuing-with-multiple-cyclic-buffers.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-peng-detnet-deadline-based-forwarding.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-peng-detnet-packet-timeslot-mechanism.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-chen-detnet-sr-based-bounded-latency.xml"/>
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-joung-detnet-stateless-fair-queuing.xml"/> 
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-eckert-detnet-glbf.xml"/>  
		<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-xiong-lsr-time-resource.xml"/> 
      </references>
    </references>
 
 </back>
</rfc>
