| Internet-Draft | PCEP-LS for Optical Networks | July 2024 |
| Zhao, et al. | Expires 8 January 2025 | [Page] |
In order to compute and provide optimal paths, Path Computation Elements (PCEs) require an accurate and timely Traffic Engineering Database (TED). This Link State and TE information has previously been obtained from a link state routing protocol that supports traffic engineering extensions.¶
An existing experimental document extends the Path Computation Element Communication Protocol (PCEP) with Link-State and Traffic Engineering (TE) Information. This document provides further experimental extensions to collect Link-State and TE information for optical networks.¶
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 2 January 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.¶
[I-D.ietf-pce-pcep-ls] describes an experimental mechanism by which Link State (LS) and Traffic Engineering (TE) information can be collected from packet networks and shared with a Path Computation Element (PCE) through the Path Computation Element Communication Protocol (PCEP). This approach is called PCEP-LS and uses a new PCEP message format.¶
Problems in the optical networks, such as Optical Transport Networks (OTN), are becoming more significant owing to the growth in scale of such networks. Such growth is also challenging the requirement for memory/storage on each network element because it is important to retain information about the whole network in order to successfully achieve dynamic network operation.¶
The use of PCE can offload responsiblity for path computation and relieve the network nodes of the need to perform that function themselves, but a PCE needs to have access to a full set of information about the network for which it computes paths. PCEP-LS provides a mechanism to gather that information from packet networks that is an alternative to passive participation in the link state routing protocol or the use of BGP-LS [RFC9552].¶
In an optical network, more information is needed in order to successfully determine optimal end-to-end paths across the network than is provided in the topology and bandwidth parameters shared in PCEP-LS. Not all optical networks run an IGP to exchange reachability and TE information: in some deployments, this information is known a priori or is collected through the management plane. Further, the use of BGP-LS is not a good proposition for optical equipment that already implements PCEP, does not usually include support for BGP, and has constrained protocol processing capablities.¶
This document describes an experimental extension to PCEP-LS for use in optical networks, and explains how encodings defined in [I-D.ietf-pce-pcep-ls] can be used in optical network contexts.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
There are three main applicabilities of the mechanism described in this document:¶
Case 1: There is an IGP running in the optical network, but there is a need to collect LS and TE resource information at a PCE from individual or specific optical nodes more frequently of more rapidly than the IGP allows.¶
Note: The applicability for Case 3 may arise as a consequence of Cases 1 and 2. When TE information changes occur in the optical network, this may also affect abstracted TE information and thus needs to be updated to the parent PCE/MSDC from each child PCE/PNC.¶
The key requirements associated with link-state and TE information distribution are identified for PCEP and listed in Section 4 of [I-D.ietf-pce-pcep-ls]. The new functions introduced to PCEP to support distribution of link-state (and TE) information are described in Section 5 of [I-D.ietf-pce-pcep-ls]. Details of PCEP messages and related Objects/TLVs are specified in Sections 8 and 9 of [I-D.ietf-pce-pcep-ls]. The key requirements and new functions specified in [I-D.ietf-pce-pcep-ls] are equally applicable to optical networks.¶
Besides the generic requirements specified in [I-D.ietf-pce-pcep-ls], optical-specific features also need to be considered. Optical networks are connection-based so there are specific parameters, such as the reachability table, optical latency, wavelength consistency, etc., that need to be included during the collection of topology information. Without these additional parameters, path computation may be inaccurate or produce paths that cannot be realised in the deployment. Therefore this information needs to be included in the PCEP-LS messages.¶
The procedure for using the optical parameters is described in following sections.¶
The reachable source-destination node pair indicates that there is an optical channel (OCh) path between two nodes. The reachability is restricted by impairment, wavelength consistency, and so on. Knowledge of the reachable source-destination node pair and the impairment restrictions is necessary at the PCE to ensure that the path computed between source and destination nodes is feasible. In this scenario, the PCE is responsible for determining the set of OCh paths available to support connections between source and destination node. Moreover, if a set of optical wavelengths is indicated in the path computation request, the PCE also determines whether a wavelength from the set of preselected optical wavelengths is available for the connection between source and destination.¶
To enable the PCE to complete these functions, the reachable relationship and optical multiplex section (OMS) link information need to be reported to the PCE. Once the PCE detects that a wavelength is available, the corresponding OMS link is marked in the PCE's database as a candidate link in the optical network, which can then be used for path computation in the future.¶
Moreover, in a hierarchical PCE architecture, all of this information needs to be reported from child PCE to parent PCE, which acts as a service coordinator.¶
It is the usual case that the PCC indicates the desired maximum latency when requesting a path computation. In optical networks the latency is a very sensitive parameter and there is often stricter requirement on latency. The PCE needs to determine which of the avilable OCh path meet the requested latency threshold.¶
A PCE may run an algorithm running to verify the performance of the computed path. During the computation, the delay factor may be converted into a kind of link weight. After the algorithm provides a set of candidate paths between the source and destination nodes, the PCE selects the best path by computing the total path propagation delay.¶
This section provides the additional PCEP-LS extensions necessary to support optical networks. All Objects/TLVs defined in [I-D.ietf-pce-pcep-ls] are applicable to optical networks.¶
The Node-Attributed TLV is defined in Section 9.3.9.1 of [I-D.ietf-pce-pcep-ls]. This TLV is applicable for LS Node Object-Type as defined in [I-D.ietf-pce-pcep-ls].¶
This TLV contains a number of Sub-TLVs. [I-D.ietf-pce-pcep-ls] defines that any Node-Attribute defined for BGP-LS [RFC9552] can be used as a Sub-TLV of the PCEP Node-Attribute TLV. There is no support for optical networks defined for BGP-LS, so the Node-Attribute Sub-TLVs shown below are defined in this document for use in PCEP-LS for optical networks.¶
The Link-Attributes TLV is defined in Section 9.3.9.2 of [I-D.ietf-pce-pcep-ls]. This TLV is applicable for the LS Link Object-Type as defined in [I-D.ietf-pce-pcep-ls].¶
This TLV contains a number of Sub-TLVs. [I-D.ietf-pce-pcep-ls] defines that any Node-Attribute defined for BGP-LS [RFC9552] can be used as a Sub-TLV of the PCEP Link-Attribute TLV. There is no support for optical networks defined for BGP-LS, so the Link-Attribute Sub-TLVs shown below are defined in this document for use in PCEP-LS for optical networks.¶
This section provides additional PCEP-LS extension necessary to support the optical network parameters discussed in Section 3.1 and Section 3.2.¶
Collection of LS and TE information is necessary before the path computation processing can be done. The procedure can be divided into:¶
For OTN networks, maximum bandwidth available may be aggregated across all optical data unit (ODU) switching levels (i.e., ODUj/k) or considered per ODU 0/1/2/3 switching level.¶
For Wavelength Switched Optical Networks (WSON), Routing and Wavelength Assignment (RWA) information collected from Network Elements would be utilized to compute optical paths. The list of information collected can be found in [RFC7688]. More specifically, the maximum bandwidth available may be per lambda/frequency (OCh) or aggregated across all lambdas/frequencies. Per OCh-level abstraction gives more detailed data to the P-PCE at the expense of more information processing. Either the OCh-level or the aggregated-level abstraction in the RWA constraint (i.e., wavelength continuity) needs to be taken into account by the PCE during path computation. Resource Block Accessibility (i.e., wavelength conversion information) in [RFC7688] needs to be taken into account in order to guarantee the reliability of optical path computation.¶
This document extends PCEP-LS information distribution in optical networks by including a set of Sub-TLVs to be carried in existing TLVs of existing messages. Procedures and protocol extensions defined in this document do not affect the overall PCEP security model (see [RFC5440] and [RFC8253]). The PCE implementation SHOULD provide mechanisms to prevent strains created by network flaps and amount of LS (and TE) information as defined in [I-D.ietf-pce-pcep-ls]. Thus, any mechanism used for securing the transmission of other PCEP message SHOULD be applied here as well. As a general precaution, it is RECOMMENDED that these PCEP extensions only be activated on authenticated and encrypted sessions belonging to the same administrative authority.¶
This document requests IANA actions to allocate code points for the protocol elements defined in this document.¶
[I-D.ietf-pce-pcep-ls] requests IANA to create a registry of "PCEP-LS Sub-TLV Type Indicators". IANA is requested to make the following allocations from this registry using the range 1 to 255.¶
+-----------+-------------------------------------------------- | Sub-TLV | Meaning +-----------+-------------------------------------------------- | TBD1 | Connectivity Matrix | TBD2 | Resource Block Information | TBD3 | Resource Block Accessibility | TBD4 | Resource Block Wavelength Constraint | TBD5 | Resource Block Pool State | TBD6 | Resource Block Shared Access Wavelength Available | TBD7 | ISCD | TBD8 | OTN-TDM SCSI | TBD9 | WSON-LSC SCSI | TBD10 | Flexi-grid SCSI | TBD11 | Port Label Restriction¶
TBD¶
Dhruv Dhody Email: dhruv.ietf@gmail.com Adrian Farrel Email: adran@olddog.co.uk¶