Internet-Draft | fgOTN PCEP Extension | October 2024 |
Han, et al. | Expires 24 April 2025 | [Page] |
This document introduces the PCEP extension used for computed fgOTN path from the PCE to the PCC.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 24 April 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
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.¶
ITU-T has a series of recommendations for fgOTN (fine grain OTN ). The fgOTN overview is defined in [ITU-T_G.709.20], fgOTN layer architecture is defined in [ITU-T_G.872], fgOTN Interface and server adaptation is defined in [ITU-T_G.709], fgOTN equipment is defined in[ITU-T_G.798], fgOTN synchronization is defined in [ITU-T_G.8251], fgOTN management requirements is defined in [ITU-T_G.874] and protocol-neutral information model is defined in [ITU-T_G.875].¶
[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 [I-D.draft-han-pce-path-computation-fg-transport].¶
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¶
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.¶
The protocol and signaling should support the application of fine-granularity path set-up/update/removal and resource management.¶
The extention for fgOTN path set-up is suggested as follows:¶
Attribute | Length (bits) | Value |
---|---|---|
Connection Identifier (LSP Object) | 96 | Composed of three tuples (Source Node Identifier, Destination Node Identifier, Service Index, each 32 bits) |
Protection Type (LSPA Object's Protection Attributes) | 8 | Includes 1+1 Protection, 1+1, Path Protection, No Protection, etc. |
Primary/Backup Flag (LSPA Object, Protection Attributes) | 8 | Set to 1 to indicate working path, set to 0 to indicate protection path |
Small timeslot granularity (Generalized Bandwidth Object) | 8 | 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) |
fgOTN Bandwidth (Generalized Bandwidth Object) | 16 | Integer, expressed in terms of the number of time slots |
Routing Information (LIST) | See Table2 | 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. |
Attribute | Length (bits) |
---|---|
Network Element Identifier | 32 |
Ingress | 32 |
Ingress ODU Service Layer Channel Number | 16 |
Ingress fgOTN Channel Number | 16 |
Egress | 32 |
Egress ODU Service Layer Channel Number | 16 |
Egress fgOTN Channel Number | 16 |
<Add any manageability considerations>¶
<Add any security considerations>¶
<Add any IANA considerations>¶