<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.17 (Ruby 2.7.0) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>

<?rfc comments="yes"?>

<rfc ipr="trust200902" docName="draft-han-pce-fgotn-pcep-extension-00" category="std" consensus="true" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="fgOTN PCEP Extension">PCEP Extension for Fine Grain Optical Transport Network (fgOTN)</title>

    <author initials="L." surname="Han" fullname="Liuyan Han">
      <organization>China Mobile</organization>
      <address>
        <email>hanliuyan@chinamobile.com</email>
      </address>
    </author>
    <author initials="Y." surname="Zhao" fullname="Yang Zhao">
      <organization>China Mobile</organization>
      <address>
        <email>zhaoyangyjy@chinamobile.com</email>
      </address>
    </author>
    <author initials="Y." surname="Liu" fullname="Yucong Liu">
      <organization>China Mobile</organization>
      <address>
        <email>liuyucongyjy@chinamobile.com</email>
      </address>
    </author>

    <date year="2024" month="October" day="21"/>

    <workgroup>PCE Working Group</workgroup>
    
    
    <abstract>
<t>This document introduces the PCEP extension used for computed fgOTN path from the PCE to the PCC.</t>
    </abstract>

  </front>

  <middle>


<section anchor="introduction"><name>Introduction</name>

<t>As SDH phases out in operators’ networks, Fine Grain Optical Transport Network (fgOTN) technology complementing the existing OTN with an additional fgOTN path layer network is used as an alternative to carry private line services. A new fine grain ODU layer network has been defined in ITU-T to carry these signals across the OTN networks, to provide flexible N*10Mbps bandwidth TDM-based transport capabilities.</t>

<t>ITU-T has a series of recommendations for fgOTN (fine grain OTN ). 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 requirements is defined in <xref target="ITU-T_G.874"/> and protocol-neutral information model is defined in <xref target="ITU-T_G.875"/>.</t>

<t><xref target="RFC8779"/>provides the PCEP extensions required for GMPLS applications, for example, for Optical Transport Networks (OTNs) and Wavelength Switched Optical Networks (WSONs). Due to the new features of fgOTN technology, PCEP needs to be extended. The requirements were analyzed in <xref target="I-D.draft-han-pce-path-computation-fg-transport" />.</t>

</section>

<section anchor="requirement"><name>Requirements on the PCEP computed path information</name>
<t>For each computed fgOTN path, the information carried by the PCEP should at least include:
1) fgOTN path information 
2) fgOTN path protection type
3) Path role (working path/backup path) 
4) fgOTN path bandwidth
5) fgOTN path list:
a)	node identifier
b)	Path identifier
</t>
</section>


<section anchor="fgotn set-up pcep extension"><name>PCEP Extention for fgOTN path set-up</name>
<t>The centralized computation model of PCE architecture seems to be suitable for the fine-granularity transport network, while the PCEP (PCE communication protocol) needs to be extended to meet the fine-granularity transport requirements.</t>
<t>The protocol and signaling should support the application of fine-granularity path set-up/update/removal and resource management.</t>
<t>The extention for fgOTN path set-up is suggested as follows:</t>

<texttable title="Service provisioning Initiate/Update message coding format (from control system to signaling head node)" anchor="tab-initiate-update">
      <ttcol align='left'>Attribute</ttcol>
      <ttcol align='left'>Length (bits)</ttcol>
      <ttcol align='left'>Value</ttcol>
      <c>Connection Identifier (LSP Object)</c>
      <c>96</c>
      <c>Composed of three tuples (Source Node Identifier, Destination Node Identifier, Service Index, each 32 bits)</c>
      <c>Protection Type (LSPA Object's Protection Attributes)</c>
      <c>8</c>
      <c>Includes 1+1 Protection, 1+1, Path Protection, No Protection, etc.</c>
      <c>Primary/Backup Flag (LSPA Object, Protection Attributes)</c>
      <c>8</c>
      <c>Set to 1 to indicate working path, set to 0 to indicate protection path</c>
      <c>Small timeslot granularity (Generalized Bandwidth Object)</c>
      <c>8</c>
      <c>Timeslot granularity, requires fgOTN's timeslot granularity. Timeslot granularity is defined by YD/T 4856-2024 and ITU-T G.709.20 standards; 0 – 10Mbps (fgOTN)</c>    
      <c>fgOTN Bandwidth (Generalized Bandwidth Object)</c>
      <c>16</c>
      <c>Integer, expressed in terms of the number of time slots</c>
      <c>Routing Information (LIST)</c>
      <c>See Table2</c>
	  <c>Destination node identifier, fgOTN's ingress/egress fgOTN channel number length is 10 bits
Refer to RFC5440 for RP object's B Flag bit to determine simplex or duplex. For simplex connections, routing information (LIST) will generate unidirectional exchanges. For duplex connections, routing information for both ingress and egress will generate bidirectional exchanges.
</c>
</texttable>

<texttable title="Routing Information Instance" anchor="tab-route-instance">
      <ttcol align='left'>Attribute</ttcol>
      <ttcol align='left'>Length (bits)</ttcol>
	  <c>Network Element Identifier</c>
	  <c>32</c>
	  <c>Ingress</c>
	  <c>32</c>
	  <c>Ingress ODU Service Layer Channel Number</c>
	  <c>16</c>
	  <c>Ingress fgOTN Channel Number</c>
	  <c>16</c>
	  <c>Egress</c>
	  <c>32</c>
	  <c>Egress ODU Service Layer Channel Number</c>
	  <c>16</c>
	  <c>Egress fgOTN Channel Number</c>
	  <c>16</c>
</texttable>
</section>

<section anchor="manageability-considerations"><name>Manageability Considerations</name>

<t>&lt;Add any manageability considerations&gt;</t>

</section>
<section anchor="security-considerations"><name>Security Considerations</name>

<t>&lt;Add any security considerations&gt;</t>

</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<t>&lt;Add any IANA considerations&gt;</t>

</section>

  </middle>

  <back>


<references title='Normative References'>

<reference anchor='RFC8779' target='https://www.rfc-editor.org/info/rfc8779'>
  <front>
    <title>Path Computation Element Communication Protocol (PCEP) Extensions for GMPLS</title>
    <author fullname='Cyril Margaria' initials='C.' role='editor' surname='Margaria'/>
	<author fullname='Oscar Gonzalez de Dios' initials='O.' role='editor' surname='Gonzalez de Dios'/>
	<author fullname='Fatai Zhang' initials='F.' role='editor' surname='Zhang'/>
    <date month='July' year='2020'/>
    <abstract>
      <t>A Path Computation Element (PCE) provides path computation functions for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. Additional requirements for GMPLS are identified in RFC 7025.This memo provides extensions to the Path Computation Element Communication Protocol (PCEP) for the support of the GMPLS control plane to address those requirements.</t>
    </abstract>
  </front>
  <seriesInfo name='RFC' value='8779'/>
  <seriesInfo name='DOI' value='10.17487/RFC8779'/>
</reference>

<reference anchor='I-D.draft-han-pce-path-computation-fg-transport' target='https://datatracker.ietf.org/doc/html/draft-han-pce-path-computation-fg-transport'>
  <front>
    <title>Path Computation and Control Extention Requirements for Fine-Granularity Transport Network</title>
    <author fullname='L.Han' initials='L.' surname='Han'/>
    <author fullname='H. Zheng' initials='H.' surname='Zheng'/>
    <author fullname='M. Wang' initials='M.' surname='Wang'/>
    <author fullname='Y. Zhao' initials='Y.' surname='Zhao'/>
    <date month='March' year='2024'/>
  </front>
  <seriesInfo name='Internet-Draft' value='draft-han-pce-path-computation-fg-transport'/>
</reference>

<reference anchor="ITU-T_G.709.20" >
  <front>
    <title>Overview of fine grain OTN</title>
    <author >
      <organization>International Telecommunication Union</organization>
    </author>
    <date year="2024" month="April"/>
  </front>
  <seriesInfo name="ITU-T Recommendation G.709.20" value=""/>
</reference>
<reference anchor="ITU-T_G.872" >
  <front>
    <title>Architecture of the optical transport network  </title>
    <author >
      <organization>International Telecommunication Union</organization>
    </author>
    <date year="2024" month="March"/>
  </front>
  <seriesInfo name="ITU-T Recommendation G.872" value=""/>
</reference>
<reference anchor="ITU-T_G.709" >
  <front>
    <title>Interfaces for the optical transport network</title>
    <author >
      <organization>International Telecommunication Union</organization>
    </author>
    <date year="2024" month="July"/>
  </front>
  <seriesInfo name="ITU-T Recommendation G.709" value=""/>
</reference>
<reference anchor="ITU-T_G.798" >
  <front>
    <title>Characteristics of optical transport network hierarchy equipment functional blocks  </title>
    <author >
      <organization>International Telecommunication Union</organization>
    </author>
    <date year="2023" month="September"/>
  </front>
  <seriesInfo name="ITU-T Recommendation G.798" value=""/>
</reference>
<reference anchor="ITU-T_G.874" >
  <front>
    <title>Management aspects of optical transport network elements</title>
    <author >
      <organization>International Telecommunication Union</organization>
    </author>
    <date year="2020" month="October"/>
  </front>
  <seriesInfo name="ITU-T Recommendation G.874" value=""/>
</reference>
<reference anchor="ITU-T_G.875" >
  <front>
    <title>Optical transport network: Protocol-neutral management information model for the network element view</title>
    <author >
      <organization>International Telecommunication Union</organization>
    </author>
    <date year="2020" month="June"/>
  </front>
  <seriesInfo name="ITU-T Recommendation G.875" value=""/>
</reference>
<reference anchor="ITU-T_G.8251" >
  <front>
    <title>The control of jitter and wander within the optical transport network (OTN)</title>
    <author >
      <organization>International Telecommunication Union</organization>
    </author>
    <date year="2022" month="November"/>
  </front>
  <seriesInfo name="ITU-T Recommendation G.8251" value=""/>
</reference>

    </references>
   
<section numbered="false" anchor="acknowledgments"><name>Acknowledgments</name>


</section>


  </back>

</rfc>

