<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-han-pce-path-computation-fg-transport-01"
     ipr="trust200902">
  <front>
    <title abbrev="draft-han-pce-path-computation-fg-transport-01">Path Computation and Control Extention Requirements for Fine-Granularity Transport Network</title>

<author fullname="Liuyan Han" initials="L" surname="Han">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street>No.32 Xuanwumen west street</street>

          <code>100053</code>

          <region>Beijing</region>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>hanliuyan@chinamobile.com</email>
      </address>
      
    </author>
    
    <author fullname="Haomian Zheng" initials="H" surname="Zheng">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street> H1, Huawei Xiliu Beipo Village, Songshan Lake.</street>

          <city>Dongguan</city>

          <region>Guangdong</region>

          <code>523808</code>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>Zhenghaomian@huawei.com</email>

        <uri/>
      </address>
    </author>

  <author fullname="Minxue Wang" initials="M" surname="Wang">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street>No.32 Xuanwumen west street</street>

          <code>100053</code>

          <region>Beijing</region>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>wangminxue@chinamobile.com</email>
      </address>
    </author>

    <author fullname="Yang Zhao" initials="Y" surname="Zhao">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street>No.32 Xuanwumen west street</street>

          <code>100053</code>

          <region>Beijing</region>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>zhaoyangyj@chinamobile.com</email>
      </address>
    </author>

 

    <date day="4" month="March" year="2024"/>

    <workgroup>PCE Working Group</workgroup>

    <abstract>
      <t>This document focuses on the requirements for path computation and control
      of the fine-granularity transport network. It  provides the general
      context of the use cases of path computation and the considerations
      on the requirements of PCE extension in such fine-granularity transport network.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>With the proposal of new service demand, the technology of the transport
      network is constantly developing. TDM based Optical Transport Network (OTN) 
      and Metro Transport Network (MTN) technologies are both moving towards fine-
      grain hard slices. The vertical industries and dedicated line services
      have higher requirements on isolation, security and reliability but with 
      smaller bandwidth. Fine-grain TDM technology can provide the flexible 
      N*10Mbps bandwidth for these connections.</t>

      <t>ITU-T has a series of recommendations for fgOTN (fine grain OTN ) and 
      fgMTN (fine grain MTN). The fgOTN overview is defined in 
      <xref target="ITU-T_G.709.20"/>, fgOTN layer architecture is defined
      in <xref target="ITU-T_G.872"/>, fgOTN Interface and server adaptation
      is defined in <xref target="ITU-T_G.709"/>, fgOTN equipment is defined in <xref target="ITU-T_G.798"/>,
      fgOTN synchronization is defined in <xref target="ITU-T_G.8251"/>,
      fgOTN management requirementsis defined in <xref target="ITU-T_G.874"/>
     and protocol-neutral information model is defined in <xref target="ITU-T_G.875"/>.
      The fgMTN overview is defined in<xref target="ITU-T_G.8312.20"/>,
      fgMTN layer architecture is defined in <xref target="ITU-T_G.8310"/>,
      fgMTN interface is defined in  <xref target="ITU-T_G.8312"/>, 
      fgMTN equipment is defined in <xref target="ITU-T_G.8321"/>,
      fgMTN synchronization is defined in <xref target="ITU-T_G.mtn-sync"/> ,
      and management requirement and information model is defined in  <xref target="ITU-T_G.8350"/>.
      Both the fgOTN and fgMTN protection are defined in <xref target="ITU-T_G.808.4"/>.
     </t>


      <t>The new fine-grain transport technology will significantly increase
      the number of path connections in the network compared to the traditional
      connections based on optical wavelength or ODUk with larger bandwidth. 
      For the future massive fine-grain channel connections, how to 
      effectively perform end-to-end path computation and control will be an
      important technical topic.</t>

 	<t>The architecture of a Path Computation Element (PCE)-based model has been
 	presented in <xref target="RFC4655"/>. It discusses PCE-based implementations including
 	composite, external, and multiple PCE path computation. <xref target="RFC8779"/>addresses 
 	the extensions required for GMPLS applications and routing requests,
 	for example, for Optical Transport Networks (OTNs) and Wavelength Switched 
 	Optical Networks (WSONs). Due to the new features of fine-grain technology,
 	PCE may need to be extended.</t>

      <t>This document focuses on the requirements for path computation and control
      of the fine-grain transport network. Section 3 provides the general
      context of the use cases of path computation. Section 4 provides the considerations
      on the requirements of PCE extension in such fine-grain transport network.</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 target="RFC8174"/> when, and only
        when, they appear in all capitals, as shown here.</t>
      </section>

    <section anchor="terminology">
      <name>Terminology</name>

      <t>Domain:</t>

      <ul empty="true">
        <li>
          <t>A domain, as defined in <xref target="RFC4655"/>, is "any
          collection of network elements within a common sphere of address
          management or path computation responsibility". Specifically, within
          this document, we mean a part of an operator's network under common
          management (i.e., under shared operational management using the same
          instances of a tool and the same policies). Network elements are
          often grouped into domains based on technologies, vendor profiles,
          or geographic proximity.</t>
        </li>
      </ul>

    <t>FG:</t>
      <ul empty="true">
        <li>
          <t>Fine Grain</t>
        </li>
      </ul>

     <t>MTN:</t>
      <ul empty="true">
        <li>
          <t>Metro Transport Network</t>
        </li>
      </ul>
   
      <t>OTN:</t>
      <ul empty="true">
        <li>
          <t>Optical Transport Network</t>
        </li>
      </ul>

</section>
 
    <section title="Path Computation Requirements in Fine-grain Transport Network">
      <t>Compared to traditional optical networks, fine-grain transport networks
      require more quantity, faster, and more flexible path set-up and removing 
      capabilities. The path computation architecture should be reliable, scalable and 
      efficient to facilitate the configuration of a large amount of fine-granularity
      channel connections.</t>
      
<figure title="Scenario of E2E fine-grain connection" anchor="fig"><artwork><![CDATA[
      +-----------------------+           +------------------------+
      |         Domain A      |           |        Domain B        |
    +-+-+   +--+    +--+     ++-+       +-++    +--+    +--+     +-+-+    
--->|PE1+---+P1+----+P2+---->+P4|------>|P5+----+P6+----+P7+---->+PE2|--->
    +-+-+   +--+    +--+     ++-+       +-++    +--+    +--+     +-+-+
      |                       |           |                        |
      +-----------------------+           +------------------------+
      ^                                                            ^
      |                                                            |
      +-----------------E2E fine-grain connection----------------+
]]></artwork></figure>

        <t>o The number of fine-grain TDM channels will significantly increase:</t>
        <ul empty="true">
        <li>
        <t>FgOTN and fgMTN support 10Mbit/s level tributary slots granularity. One ODU2
        channel can support up to 952 fgOTN connections. One 5Gbps MTN channel can support up to 480 
        fgMTN connections. For transport devices with a switching capacity of several Tbps, 
        they can support fine-grain channel connections of tens of thousands or even tens 
        of thousands. Therefore, for the network, the number of connections throughout the entire
        network will significantly increase.</t>
        </li>
      </ul>

       <t>o According to service requirements, fine-grain paths may change frequently and dynamically:</t>
        <ul empty="true">
        <li>
        <t>One fine-grain channel can carry and correspond to a certain CBR or Ethernet service,
        rather than serving as a large optical channel. When the services appear or end, or its bandwidth 
        changes, or the destination address changes, they will cause changes in fine-grain channels. 
        Therefore, compared to serving as an optical bandwidth channel for the routers, the fine-granularity
        channels serve directly as service channels, which are more likely to change.</t>
        </li>
      </ul>
      </section>
 
    <section title="Use Cases of Fine-grain Path Computation">
      <t> To address the massive fine-grain path computation issues, it is necessary
      to combine centralized control systems and distributed control protocols.
      On the one hand, a centralized control system is used to calculate the global
      optimal routing and develop resource scheduling strategies. On the other hand, 
      distributed control protocols between devices are used to perform operations 
      such as cross connection configuration and time slot occupation assignment.</t>
    <t>The applications of fine-grain path computation and related capabilities at least include:</t>

   <t>o Fine-grain path set-up:</t>

      <ul empty="true">
        <li>
          <t>The control system calculates service routing in a centralized way and 
          sends messages to the source node. Then, the connection is established 
          between devices through connection control signaling. The end-to-end 
          fine-grain connections may cross one or more domains.</t>
        </li>
      </ul>

  <t>o Fine-grain resource management:</t>

      <ul empty="true">
        <li>
          <t>The topology and resource information of fine-grain devices 
          and slots need to be collected and reported, so that the centralized 
          system can calculate new routes based on this information and allocate
          slot resources for the new connections.</t>
        </li>
      </ul>

   <t>o Fine-grain path update:</t>

      <ul empty="true">
        <li>
          <t>During the connection, fine-grain channels can undergo hitless
          bandwidth adjustment. When channel bandwidth increases or decreases, time 
          slots need to be added or removed. It is needed to control and update the
          existing path parameter.</t>
        </li>
      </ul>

   
   <t>o Fine-grain path removal:</t>

      <ul empty="true">
        <li>
  <t>When the service no longer needs this connection, it is necessary to
          remove this fine-grain channel and release the corresponding 
          resources.</t>
        </li>
      </ul>
 
   
<t>o Service awareness and mapping:</t>
     <ul empty="true">
        <li>
  <t>In order to accurately match the fine-grain service requirements,
  the service awareness and mapping function for fine-grain transport 
  network have been defined in<xref target="I-D.liu-ccamp-optical2cloud-problem-statement"/>.
  The PE device learns and identifies the packet header carried by client
  services (including source and destination MAC or IP addresses etc). Then it
  reports the identified client services to the control system. The control 
  system selects or creates connection(s) acorrding to service requirements, 
  and configures the mapping between service and connection(s).</t>
        </li>
      </ul>

    </section> 
   
    <section title="Requirements of PCE Extension for Fine-grain Transport Network">
      <t>The centralized computation model of PCE architecture seems to be suitable
      for the fine-grain transport network, while the PCEP (PCE communication protocol)
      needs to be extended to meet the fine-grain transport requirements.</t>

      <t>The path calculation request/reply message from the PCC or the PCE must contain the 
      information specifying appropriate fine-grain channel attributes, including the 
      fine-grain switching capability/type, the fine-grain server layer type, the
      fine-grain time slots, the fine-grain client ID, end-to-End fine-granularity
      path protection type, etc.</t>

     <t>The protocol and signaling should support the application of fine-grain path 
     set-up/update/removal and resource management.</t>
      </section>

    <section title="PCEP Extension for Fine-grain Transport Network">
      <t>Fine-grain path set-up/adjustment,service awareness and mapping and fine-
         grain resource management may be invovled in PCEP extensions. The specific
         extentions will continue to apply in the future.</t>
    </section>
    
    <section title="Manageability Consideration">
      <t>TBD</t>
    </section>

    <section title="Security Considerations">
      <t>TBD</t>
    </section>
    
    <section title="IANA Considerations">
      <t>TBD</t>
    </section>


  </middle>

  <back>
  
    <references title="Normative References">

      <?rfc include="reference.RFC.3688"?>

      <?rfc include="reference.RFC.2119"?>

       <?rfc include="reference.RFC.8174"?>

     <?rfc include="reference.RFC.4655"?>

     <?rfc include="reference.RFC.8779"?>

     <?rfc include='reference.I-D.liu-ccamp-optical2cloud-problem-statement'?>     
      
      <?rfc ?>

      <reference anchor="ITU-T_G.709.20">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.709.20: Overview of fine grain OTN;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="Work in progress"/>

      </reference>

      <reference anchor="ITU-T_G.872">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.872: Architecture of the optical transport network;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.872"/>
        
      </reference>
      
       <reference anchor="ITU-T_G.709">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.709: Interfaces for the optical transport network;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.709"/>

      </reference> 
            
       <reference anchor="ITU-T_G.8251">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.8251: The control of jitter and wander within the optical transport network (OTN);
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.8251"/>

      </reference> 
      
             <reference anchor="ITU-T_G.874">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.874: Management aspects of optical transport network elements;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.874"/>

      </reference> 

          
             <reference anchor="ITU-T_G.875">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.875: Optical transport network: Protocol-neutral management information model for the network element view;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.875"/>

      </reference> 
      
      <reference anchor="ITU-T_G.8312.20">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.8312.20:Overview of fine grain MTN;
          01/2024</title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="January" year="2024"/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.8312.20"/>

    </reference>
    
        <reference anchor="ITU-T_G.8310">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.8310: Architecture of the metro transport network;
          01/2024</title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="January" year="2024"/>
        </front>

        <seriesInfo name="" value="Work in progress"/>
      </reference>
      
     <reference anchor="ITU-T_G.8312">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.8312:Interfaces for metro transport networks;
          01/2024</title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="January" year="2024"/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.8312"/>

    </reference>
    
      <reference anchor="ITU-T_G.8321">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.8321:Characteristics of metro transport network equipment functional blocks;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.8321"/>

    </reference>

        <reference anchor="ITU-T_G.mtn-sync">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.mtn-sync:Synchronization aspects of metro transport network
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="Work in progress"/>

    </reference>
    
    <reference anchor="ITU-T_G.8350">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.8350: Management and Control of metro transport networks;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.8350"/>
      </reference>

    <reference anchor="ITU-T_G.808.4">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.808.4: Linear protection for fgMTN and fgOTN;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="Work in progress"/>
      </reference>

      
    <reference anchor="ITU-T_G.798">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>ITU-T G.798: Characteristics of optical transport network hierarchy equipment functional blocks;
          </title>

          <author>
            <organization>ITU-T</organization>
          </author>

          <date month="" year=""/>
        </front>

        <seriesInfo name="" value="https://www.itu.int/rec/T-REC-G.798"/>
      </reference>
      
  </references>
  </back>
</rfc>