]> Futurewei Technologies

aihuaguo.ietf@gmail.com

Nokia

Sergio.belotti@nokia.com

Individual

ggalimbe56@gmail.com

Naudit HPCN

jorge.lopez_vergara@uam.es

Universidad Autonoma de Madrid

daniel.perdices@uam.es

Routing CCAMP Working Group next generation unicorn sparkling distributed ledger This document defines a YANG data model for the provisioning and management of Traffic Engineering (TE) tunnels and Label Switched Paths (LSPs) in Optical Networks (Wavelength Switched Optical Networks (WSON) and Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks). The YANG data model defined in this document conforms to the Network Management Datastore Architecture (NMDA).

Introduction Transport networks have evolved from traditional fixed-grid Wavelength Switched Optical Networks (WSON) to more scalable and flexible elastic optical networks. These utilize flexi-grid Dense Wavelength Division Multiplexing (DWDM) technologies to optimize bandwidth usage. Current DWDM Optical Network deployments may include fixed-grid WSON, flexi-grid DWDM, or a combination of both. In the optical domain, a WDM tunnel typically originates and concludes at a pair of transponders using one or more transceivers dependent upon the data rate and encoding type of the transceivers. These transponders are then connected to an intermediate line system composed of optical switches and multiplexers, including Reconfigurable Optical Add-Drop Multiplexers (ROADMs) and add-drop multiplexers, complemented by optical amplifiers to boost the transmission distance. The optical wavelength can be routed from the transponder or an incoming fiber, through multiplexing, to various outgoing fibers in the DWDM network. At optical nodes, wavelengths may undergo conversion via optical-electrical-optical (OEO) regenerators, depending on the switching setup and fiber configuration. Optical services, transmitted via analog signals, require careful provisioning across the network to maintain signal quality and prevent interference between different wavelength channels. The technology within optical nodes, like tunable transceivers or Colorless, Directionless and Contentionless Flexi-grid (CDC-F) ROADMs, introduces specific constraints that can limit WDM tunnel path options. These constraints must be factored into WDM tunnel provisioning and pre-computation. Additionally, assessing the end-to-end optical performance metrics like Generalized Signal-to-noise Ratio (G-SNR), Bit Error Rate (BER), and Q-factor is crucial to ensure transmission quality and receiver signal integrity. This draft introduces a YANG data model for setting up and managing TE tunnels and LSPs in DWDM Optical Networks. It aims to provide an intent-based interface used by a control entity such as a Software-defined Network (SDN) controller at its northbound to establish services between endpoints, typically optical transponders. Clients can utilize this model to either partially or fully delegate service provisioning to the SDN controller, while still capable to express additional constraints to guide its operation. Service provisioning can be as simple as identifying the source and destination transponders and delegate the rest of determination to the SDN controller, or as explicit as specifying a complete detailed path complete with tuned wavelengths and transceiver details. This document identifies the WDM tunnel components, parameters and their values, and characterizes the features and the performances of the WDM elements. An application example is provided towards the end of the document to understand their utility better.

Conventions and Definitions 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 when, and only when, they appear in all capitals, as shown here. The terminology for describing YANG data models is found in . Refer to and for the key terms used in this document. The following terms are defined in and are not redefined here: - client server augment data model data node The following terms are defined in and are not redefined here: - configuration data state data

Overview The YANG data model in this draft builds upon the generic TE tunnel model from . This base model is suitable for all TE-enabled networks and includes universal TE tunnel elements like node addresses, tunnel termination points (TTPs), and path-level constraints such as explicit path hops, label restrictions, and path diversity. The current model enhances by incorporating WDM-specific attributes and constraints relevant to WDM tunnels, including definitions for: Network-scope optical transceiver configuration constraints, e.g., operational modes, transceiver tuning constraints Network-scope WDM path routing policies for influencing WDM TE path selection. For exmaple, whether or not using regenerator or wavelength conversion is allowed, whether or not wavelength retuing is allowed for tunable transceivers, etc. Network-scope optical performance constraints, e.g. the generalized Signal-to-noise (G-SNR) margin and delta power of a feasible optical path Path-scope WDM layer constraints and transceiver configurations for working and protection path within a WDM tunnel List of WDM nodes, links, and optical wavelength that constitute an end-to-end WDM path Other relevant optical attributes which characterize the optical signal The attributes described above are optional, allowing the model to support both simplified and fully-explicit WDM tunnel provisioning to meet diverse client requirements. Additionally, the YANG model provides the status of a WDM tunnel, which includes: Computed paths for various roles such as working, protection, and restoration, indicating potential optical paths confirmed by the SDN controller via pre-computation. Actual LSPs for each tunnel path, representing the optical paths currently established in the network.

Integrated vs. External Optical Transponder In optical networks built with traditional chassis-based DWDM optical equipment, optical transponder (OTs) are typically inserted into the chassis installed as cards. WDM tunnels are established between pairs of OTs, with the SDN controller serving as the central entity for provisioning and managing these tunnels. In scenarios like data center interconnects (DCI), optical transponders may be externally mounted on a 'pizza box' and linked via dedicated fiber or wavelength multiplexer/demultiplexer to the optical line system. These external OTs could be managed by the same SDN controller or a different entity, such as an orchestrator. Consequently, a WDM tunnel might be composed of several segments joined to create a continuous end-to-end tunnel. The YANG data model offers a cohesive interface for managing WDM tunnels and tunnel segments, irrespective of transponder location.

3R Regenerators A desired optical path may span a distance beyond the reach of a single optical transponder. In that case, one or more 3R regenerators can be deployed at intermediate nodes, reamplifying, reshaping, and retiming the optical signal before transmission continues. This scenario is described in detail in Section 2.7 of . Deploying 3R regeneration is costly because it requires additional transponders; consequently, at most a single regenerator is typically used to regenerate the optical signals of an end-to-end optical tunnel. According to , there are multiple ways to implement a 3R regenerator: - Back-to-back (bi-directional) regeneration, where two optical transponders are connected back-to-back; each transceiver receives and transmits the optical signal for the same segment of the end-to-end tunnel, operating in both directions. - Uni-directional regeneration, where two transponders are used with one performing 3R regeneration in the forward direction (source to destination) and the other performing 3R regeneration in the reverse direction. When an optical signal is regenerated, it can be terminated and restored at different protocol layers depending on the transponder's capabilities. For example, if the transponder supports OTN, the signal can be regenerated at the OTU layer or at the ODU layer after the OTU overhead has been stripped; if the transponder supports Ethernet clients, the signal can be terminated at the Ethernet layer, which commonly occurs in the back-to-back configuration. Typically, the signal is regenerated at the lowest possible layer to minimize processing delay and complexity, but termination layer may be chosen deliberately during network planning for specific scenarios. To ensure correct transmission, the termination method used between the source and the receiving transponder at the regenerator node must match the method used between the sending transponder at the regenerator node and the destination transponder (or the receiving transponder at the next regenerator node). The termination of an optical signal occurs at the reference point immediately before inverse multiplexing in the transmitting direction or immediately after inverse multiplexing in the receiving direction for the corresponding transceiver, and this applies to the entire OTSiG used by the optical tunnel. For 3R regeneration, to identify the transceiver configuration associated with these reference points consistently between uni-directional and bi-directional regeneration, the following definitions are used in this draft: - Forward direction: the direction of the optical path from the source to the destination. - Reverse direction: the direction of the optical path from the destination back to the source. - Incoming transponder: for back-to-back regeneration, the transponder in the regenerator that receives from and transmits toward the same segment of the optical path toward the source; for uni-directional regeneration, the transponder that performs regeneration in the forward direction of the optical path. - Outgoing transponder: for back-to-back regeneration, the transponder in the regenerator that receives from and transmits toward the same segment of the optical path toward the destination; for uni-directional regeneration, the transponder that performs regeneration in the reverse direction of the optical path. Utilizing the figures in for 3R regeneration, and further illustrate the aforementioned reference points for back-to-back regeneration and uni-directional regeneration, respectively.

---------------------------------| Reverse Direction |------------------------------<---------------------------------| Incoming Transponder Outgoing Transponder D +-------------------+ +--------------------+ E S |Transceiver | | Transceiver| S O |-----------+ +-----| |-----+ +------------| T U ------->|Receiver |-|Sig. |-->|Sig. |-| Transmitter|-------> I R |-----------+ | | | | +------------| N C <-------|Transmitter|-|Proc.|<--|Proc.|-| Receiver|<------- A E |-----------+ +-----| |-----+ +------------| T +-------------------+ +--------------------+ I O N ]]>

---------------------------------| Reverse Direction |------------------------------<---------------------------------| Incoming Transponder 3R in forward direction +-----------------------+ |Transceiver | |-----------+ +--------+| ------->|Receiver |-|Sig. --+|| |-----------+ | ||| +---|Transmitter|-|Proc.<-+|| | |-----------+ +--------+| | +-----------------------+ E S | S O +------------------------------------> T U I R <-----------------------------------+ N C | A E +-----------------------+ | T | Transceiver| | I |+--------+ +-----------| | O ||+->Sig. |-|Transmitter|---+ N ||| | +-----------| ||+--Proc.|-|Receiver |<-------- |+--------+ +-----------| +-----------------------+ Outgoing Transponder 3R in reverse direction ]]>

Example of Use To illustrate the model's application, consider an optical network with various transponders, switches, and links. A depicted topology outlines two WDM tunnel scenarios. In the first, an end-to-end WDM tunnel (WDM Tunnel 1) comprises two physical paths (WDM Primary Path 1 and 2) linking two integrated optical transponders, Transponder A and E, through WSON and Flexi-grid nodes. The second scenario describes three WDM tunnel segments (WDM Tunnel Segment 2a to 2c) connecting two external OTs, External OT node X and Y, via the same nodes and links.

WDM Primary Path 1 <---------------------------------------------------> WDM Tunnel WDM Tunnel WDM Tunnel Segment 2a Segment 2b Segment 2c <=================><===============><===============> +----------+ +----------+ | External | | External | | OT |<----------+ +---------->| OT | | node X | | | | node Y | +----------+ | | +----------+ | | | | +----------+ | | +----------+ | Flexi- | | | | Flexi- | | grid | | | | grid | | node A | | | | node E | | | +--v---+ +---v--+ | | | | Link 1 |Flexi-| Link 2 | WSON | Link 3 | | | |<------>| grid |<------>| |<------>| | |......... | |node B| |node C| | .........| | Trans- : | +------+ +------+ | : Trans- | | ponder : | | : ponder | | A : | +------+ | : E | |........: | Link 4 |Flexi-| Link 5 | :........| | | | grid | | | | |<-------------->|node D|<-------------->| | | | +------+ | | +----------+ +----------+ <---------------------------------------------------> WDM Secondary Path 1 ]]>

To configure an end-to-end WDM tunnel to interconnect transponders A and E, first of all we have to populate the flexi-grid topology YANG model with all elements in the network: We define the transponders within nodes A and E as tunnel termination points (TTPs) and provide their internal local link connectivity towards the node interfaces. We also provide nodes A and E identifiers, addresses and interfaces. We do the same for the nodes B, C and D, providing their identifiers, addresses and interfaces, as well as the internal connectivity matrix between interfaces. Then, we also define the links 1 to 5 that interconnect nodes, indicating which WSON or flexi-grid labels are available. Other information, such as the slot frequency and granularity are also provided. After the nodes, links and transponders have been defined using and we can configure the tunnel from the information we have stored in the flexi-grid topology, by querying which elements are available, and planning the resources that have to be provided on each situation, taking into account the global and path-specific WDM tunnel constraints. Note that every element in the flexi-grid topology has a reference, and this is the way in which they are called in the tunnel. Depending on the case, it is possible to define either the source and destination node ports, or the source and destination node and transponder. In our case, we would define a network tunnel, with source transponder A and source node B, and destination transponder E and destination node C. Thus, we are going to follow path x. Then, for each link in the path x, we indicate which channel we are going to use, providing information about the slots, and what nodes are connected. Finally, the flexi-grid topology has to be updated with each element usage status each time a tunnel is created or torn down.

YANG Model for WDM Tunnel

YANG Tree

YANG Code

WG List: Editor: Jorge E. Lopez de Vergara Editor: Daniel Perdices Editor: Victor Lopez Editor: Italo Busi Editor: Aihua Guo "; description "This module defines a YANG data model for configuring and managing Wavelength-Division Multiplexing (WDM) switched optical tunnels. The model fully conforms to the Network Management Datastore Architecture (NMDA). Copyright (c) 2021 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; revision "2025-10-20" { description "Updated revision with combined WSON and Flexi-grid tunnel YANG model"; reference "RFC XXXX: YANG data model for WDM tunnels"; // RFC Ed.: replace XXXX with actual RFC number, update date // information and remove this note } /* * Identities */ identity otsig-termination-type { description "Digital termination type applicable to OTSiG"; } identity otsi-lane-termination-type { description "Digital termination type applicable to a single OTSi. The termination of an optical signal occurs at the reference point immediately before inverse multiplexing in the transmitting direction or immediately after inverse multiplexing in the receiving direction."; } identity digital-mapping-type { description "Digital mapping type for the client payload of transceivers"; } identity inverse-mux-type { description "Inverse multiplexing type"; } identity otsig-regeneration-layer { description "Level of 3R regeneration"; } //TBD: types to be added /* * Groupings */ grouping additional-transceiver-configuration-constraints { description "This grouping defines additional optional constraints for transceiver configurations related to tunnel selection. These constraints further limit the resources available to the tunnel. All constraints operate inclusively, using an AND logic. For example, if a specific frequency range is selected, the tunnel must also be constrained to match only that range. When these constraints are combined with the operational mode, the list of operational modes should exclude any modes that cannot satisfy the additional constraints. For instance, if the frequency is restricted to the C-band, the list of operational modes should not include any modes applicable only to the L-band."; leaf otsi-carrier-frequency { type l0-types:frequency-thz; description "OTSi carrier frequency, i.e. configured transmitter frequency."; } container tx-tune-constraints { description "The permissible tuning frequency range for the transmitter."; uses l0-types:transceiver-tuning-range; } leaf-list line-coding-bitrate { type identityref { base l0-types:line-coding; } description "The list of the bit rate/line coding of the optical tributary signal that constrains the configuration of the transceiver."; reference "ITU-T G.698.2 section 7.1.2"; } leaf tx-channel-power { type l0-types:power-dbm; description "The preferred channel transmit power."; } leaf preferred-rx-channel-power { type l0-types:power-dbm; description "The preferred channel received power."; } uses l0-types:path-constraints; } grouping transceiver-constraints { description "This grouping defines constraints for transceiver configurations"; leaf-list operational-modes { type string { length "1..255"; } description "List of operational mode ids of the transceiver."; } uses additional-transceiver-configuration-constraints; } grouping transceiver-common-config { description "This grouping specifies common configurations for transceivers."; leaf transceiver-id { type uint32; description "Transceiver identifier"; } leaf otsi-carrier-id { type uint16; description "OTSi carrier identifier associated with the transceiver."; } leaf otsi-carrier-frequency { type l0-types:frequency-thz; description "OTSi carrier frequency, i.e. configured transmitter frequency."; } leaf tx-channel-power { type l0-types:power-dbm; description "The preferred channel transmit power."; } } grouping regenerator-incoming-outgoing-common-state { description "This grouping specifies common states for incoming and outgoing transceivers associated with a regenerator group."; leaf operational-mode { type string { length "1..255"; } description "Operational mode of the transceiver."; } leaf line-coding-bitrate { type identityref { base l0-types:line-coding; } description "The bit rate/line coding of the optical tributary signal that constrains the configuration of the transceiver."; reference "ITU-T G.698.2 section 7.1.2"; } } grouping regenerator-incoming-outgoing-common-config { description "This grouping specifies common configurations for incoming and outgoing transceivers associated with a regenerator group."; uses regenerator-incoming-outgoing-common-state; leaf preferred-rx-channel-power { type l0-types:power-dbm; description "The preferred channel received power."; } uses l0-types:path-constraints; } grouping transponder-digital-termination-config { description "This grouping specifies the configuration of digital layer termination applicable to the transceivers."; container digital-terminations { description "Digital layer termination applicable to the transceivers."; list digital-termination { key "index"; description "Sequence of digital layer terminations."; leaf index { type uint8; description "An index number used to identify entries in the list, organized in ascending order of their values."; } leaf termination-type { type identityref { base otsig-termination-type; } description "Digital layer termination before/after inverse multiplexing in the tx/rx direction of the transceiver, that applies to the whole OTSiG, also applicable to the special case when there is a single OTSi in the OTSiG, i.e. without inverse multiplexing."; } leaf mapping-type { type identityref { base digital-mapping-type; } description "Identifies the type of digital mapping of the client payload."; } } } } grouping transceiver-inverse-multiplexing-config { description "This grouping specifies inverse-multiplexing configurations applicable to multi-carrier transceivers."; container inverse-multiplexing { presence "When present, it indicates that the transceiver supports inverse multiplexing."; description "Transceiver configuration for inverse multiplexing."; leaf inverse-mux-type { type identityref { base inverse-mux-type; } description "Type of inverse multiplexing."; } leaf otsi-lane-termination-type { type identityref { base otsi-lane-termination-type; } description "Digital layer termination before/after inverse multiplexing in the rx/tx direction of the transceiver, that applies to a single OTSi within the inverse multiplexing group."; } container additional-transceivers { description "Configuration for additional transceivers with an index value 1 and higher within the same inverse multiplexing group."; leaf index { type uint8 { range "1..max"; } description "The index of the transceiver in the inverse multiplexing group starting from value 1."; } uses transceiver-common-config; } } } grouping transceiver-config { description "This grouping specifies configurations for transceivers at source, destination nodes, as well as at regenerator nodes with a single pair of regenerator."; leaf transponder-id { type uint32; description "transponder identifier"; } uses transponder-digital-termination-config; container transceiver { description "Specifies transceiver configurations. The attributes specified in this container, excluding those within the inverse-multiplexing container, apply to a single transceiver when inverse multiplexing is not supported, as well as to the first transceiver, identified by an index value of 0 when inverse multiplexing is enabled. Attributes within the inverse-multiplexing container are applicable exclusively to transceivers with an index value of 1 or higher, belonging to the same inverse multiplexing group."; uses transceiver-common-config; uses regenerator-incoming-outgoing-common-config; uses transceiver-inverse-multiplexing-config; } } grouping multi-regen-transceiver-config { description "This grouping specifies configurations for transceivers at at regenerator nodes with multiple pairs of regenerators."; leaf transponder-id { type uint32; description "transponder identifier"; } container transceiver { description "Specifies transceiver configurations at a regenerator node with multiple pairs of regenerators."; uses transceiver-common-config; } } grouping regenerator-common-config { description "This grouping defines a set of common attributes applicable to 3R regenerators."; leaf regen-group-id { type uint32; description "3R group identifier."; } leaf regeneration-layer { type identityref { base otsig-regeneration-layer; } description "Indicate the chosen level of digital layer regeneration, e.g. ODU, FlexOnM, before/after inverse multiplexing in the tx/rx direction, that applies to the whole OTSiG. It also applies to the case when there is only one OTSi in the OTSiG, i.e. without inverse multiplexing, in which case the number of OTSis in the OTSiGs before/after the regenerator may be different."; } } grouping path-transceiver-config { description "This grouping defines a set of transceivers on a node, serving as either source transceivers, destination transceivers, or regenerators."; choice node-position { description "The relative position of the node within the path."; case source { container source-transponder { description "Constraints for configuring transceivers at the source node transponder."; uses transceiver-config; } } case destination { container destination-transponder { description "Constraints for configuring transceivers at the source node transponder."; uses transceiver-config; } } case regenerator { container regenerator { description "Constraints for configuring transponders at the regenerator node with a pair of transponder as regenerator. The forward direction refers to the direction of the optical path traversing from the source to the destination, while the reverse direction refers to direction of the optical path, traveling from the destination back to the source. For uni-directional regenerators, one transponder, labeled 'incoming', regenerates signals in the forward direction, while another transponder, labeled 'outgoing', handles signal regeneration in the reverse direction. For bi-directional, or back-to-back regenerators, one transponder, labeled 'incoming', receives and transmits signal from/to the same segment of the optical path toward the source, while another transponder, labeled 'outgoing', receives and transmits signal from/to the same segment of the optical path toward the destination."; uses regenerator-common-config; container incoming-transponder { description "Constraints for transceiver configurations in the incoming direction of the regenerator."; uses transceiver-config; } container outgoing-transponder { description "Constraints for transceiver configurations at the outgoing direction of the regenerator"; uses transceiver-config; } } } case regenerators { container regenerators { description "Constraints for configuring transponders at the regenerator node with multiple transponder pairs (therefore, in multiple regenerator groups) as regenerators. A such example is described in ITU-T G.798 Amd.3 for FlexOxR. The forward direction refers to the direction of the optical path traversing from the source to the destination, while the reverse direction refers to direction of the optical path, traveling from the destination back to the source. For uni-directional regenerators, mulitple transponders, labeled 'incoming', together regenerate signals in the forward direction, while another multiple transponders, labeled 'outgoing', handles signal regeneration in the reverse direction. For bi-directional, or back-to-back regenerators, mulitple transponder, labeled 'incoming', receive and transmits signal from/to the same segment of the optical path toward the source, while another multiple transponder, labeled 'outgoing', receives and transmits signal from/to the same segment of the optical path toward the destination."; container common-incoming { description "Common configuration for transponders in the incoming direction."; uses regenerator-incoming-outgoing-common-config; } container common-outgoing { description "Common configuration for transponders in the outgoing direction."; uses regenerator-incoming-outgoing-common-config; } list regenerator { key "index"; description "A list of regenerators used at the regenerator node."; leaf index { type uint8; description "An index number used to identify a regenerator in the list, organized in ascending order of their values."; } uses regenerator-common-config; container incoming-transponder { description "Constraints for transceiver configurations in the incoming direction of the regenerator."; uses multi-regen-transceiver-config; } container outgoing-transponder { description "Constraints for transceiver configurations at the outgoing direction of the regenerator"; uses multi-regen-transceiver-config; } } } } } } grouping transceiver-measured-parameters { description "Measured transceiver parameters."; container pre-fec-ber { description "Timestamp and value of the Pre-FEC Bit Error Rate (BER) of the received signal."; leaf timestamp { type yang:timestamp; description "Timestamp associated with the Pre-FEC BER."; } leaf value { type decimal64 { fraction-digits 18; } description "Pre-FEC BER of the received signal."; } } container q-factor { description "Timestamp and value of the estimated Q-factor based on the pre-FEC BER."; leaf timestamp { type yang:timestamp; description "Timestamp associated with the Q-factor."; } leaf value { type l0-types:decimal-2-or-unknown; units "dB"; description "Estimated Q-factor based on the pre-FEC BER."; } } } grouping transceiver-state { description "This grouping specifies transceiver state parameters at source, destination nodes, as well as at regenerator nodes with a single pair of regenerator."; leaf transponder-id { type uint32; description "transponder identifier"; } uses transponder-digital-termination-config; container transceiver { description "Specifies transceiver states. The attributes specified in this container, excluding those within the inverse-multiplexing container, apply to a single transceiver when inverse multiplexing is not supported, as well as to the first transceiver, identified by an index value of 0 when inverse multiplexing is enabled. Attributes within the inverse-multiplexing container are applicable exclusively to transceivers with an index value of 1 or higher, belonging to the same inverse multiplexing group."; uses transceiver-common-config; uses regenerator-incoming-outgoing-common-state; uses l0-types:common-transceiver-readonly-param; uses transceiver-inverse-multiplexing-config; } } grouping e2e-media-channel-info { description "This grouping includes end-to-end media channel path id information."; leaf-list e2e-mc-path-id { type uint16; description "The list of the possible end-to-end Media Channel (e2e-MC) paths associated with the OTSi which have different optical impairments. This list is meaningful in case the OTSi can be associated with multiple end-to-end Media Channel (e2e-MC) paths (e.g., when OPS protection is configured). The list can be empty when the OTSi has only one e2e-MC path."; } } grouping path-transceiver-state { description "This grouping defines a set of transceivers on a node, serving as either source transceivers, destination transceivers, or regenerators."; choice node-position { description "The relative position of the node within the path."; case source { container source-transponder { description "Transceiver states at the source node transponder."; uses transceiver-state; } } case destination { container destination-transponder { description "Transceiver states at the destination node transponder."; uses transceiver-state; } } case regenerator { container regenerator { description "The states of a regenerator node with a pair of transponder as regenerator. The forward direction refers to the direction of the optical path traversing from the source to the destination, while the reverse direction refers to direction of the optical path, traveling from the destination back to the source. For uni-directional regenerators, one transponder, labeled 'incoming', regenerates signals in the forward direction, while another transponder, labeled 'outgoing', handles signal regeneration in the reverse direction. For bi-directional, or back-to-back regenerators, one transponder, labeled 'incoming', receives and transmits signal from/to the same segment of the optical path toward the source, while another transponder, labeled 'outgoing', receives and transmits signal from/to the same segment of the optical path toward the destination."; uses regenerator-common-config; container incoming-transponder { description "Constraints for transceiver configurations in the incoming direction of the regenerator."; uses transceiver-state; } container outgoing-transponder { description "Constraints for transceiver configurations at the outgoing direction of the regenerator"; uses transceiver-state; } } } case regenerators { container regenerators { description "Regenerator states at a regenerator node formed by multiple parallel regenerators. A such example is described in ITU-T G.798 Amd.3 for FlexOxR. The forward direction refers to the direction of the optical path traversing from the source to the destination, while the reverse direction refers to direction of the optical path, traveling from the destination back to the source. For uni-directional regenerators, mulitple transponders, labeled 'incoming', together regenerate signals in the forward direction, while another multiple transponders, labeled 'outgoing', handles signal regeneration in the reverse direction. For bi-directional, or back-to-back regenerators, mulitple transponder, labeled 'incoming', receive and transmits signal from/to the same segment of the optical path toward the source, while another multiple transponder, labeled 'outgoing', receives and transmits signal from/to the same segment of the optical path toward the destination."; container common-incoming { description "Common configuration for transponders in the incoming direction."; uses regenerator-incoming-outgoing-common-state; } container common-outgoing { description "Common configuration for transponders in the outgoing direction."; uses regenerator-incoming-outgoing-common-state; } list regenerator { key "index"; description "A list of regenerators used at the regenerator node."; leaf index { type uint8; description "An index number used to identify a regenerator in the list, organized in ascending order of their values."; } uses regenerator-common-config; container incoming-transponder { description "Constraints for transceiver configurations in the incoming direction of the regenerator."; uses multi-regen-transceiver-config; } container outgoing-transponder { description "Constraints for transceiver configurations at the outgoing direction of the regenerator"; uses multi-regen-transceiver-config; } } } } } } grouping global-transceiver-constraint { description "This grouping defines the constraints for transceiver configurations."; container transceiver-constraint { description "Constraints for transceiver configurations"; uses transceiver-constraints; } } grouping wdm-constraint { description "Grouping for WDM tunnel constraints"; container wdm-constraint { description "WDM tunnel constraints."; uses global-transceiver-constraint; leaf use-regen { type boolean; default false; description "Indicate whether or not regenerators (e.g. 3R) should be considered. When this parameter is set to true, the tunnel path may include a regen when the path is not feasible for direct optical reach."; } /* leaf-list regen-levels { when '../use-regen = "true"' { description "Regenerator must be enabled for the regen levels to be considered."; } //type l0-types:regen-level; type string; description "Indicate the levels of 3R regeration permitted by the tunnel."; } */ leaf wavelength-conversion { when '../use-regen = "true"' { description "Regenerator must be enabled for wavelength conversion to be considered."; } type boolean; default false; description "Indicate whether or not wavelength conversion is allowed along the tunnel path. Applicable only when 3R regeneration is enabled."; } uses l0-types:tunnel-attributes; leaf guard-band-size { type l0-types:frequency-thz; description "Guard band size in THz."; } leaf matching-fwd-rev-wavelength { type boolean; default true; description "Indicate whether or not the assigned channels for forward and reverse wavelength path must be the same."; } leaf allow-retuning { type boolean; default false; description "Indicate whether or not re-tuning is allowed when one or more paths of a WDM tunnel is being restored. Typically, wavelength retuning is not preferred for wavelength planning considerations."; } leaf delta-power { type l0-types:power-ratio; description "Delta power in dB indicating the per-channel power deviation from the nominal power per channel at the output of an OMS."; } } } /* * Data nodes */ /* * Global constraints for WDM tunnel */ augment "/te:te/te:tunnels/te:tunnel" { description "Augment with additional parameters required for WDM tunnel configurations."; uses wdm-constraint; //uses digital-layer-constraint; } /* * Transceiver constraints for primary path * Applicable to starting, terminating and regenerator * transceivers. */ augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE primary explicit path (include or exclude) with transceiver configurations."; uses path-transceiver-config; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE primary explicit path (exclude always) with transceiver configurations."; uses path-transceiver-config; } /* * Transceiver constraints for primary reverse path * Applicable to starting, terminating and regenerator * transceivers. */ augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE primary reverse explicit path (include or exclude) with transceiver configurations."; uses path-transceiver-config; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE primary reverse explicit path (exclude always) with transceiver configurations."; uses path-transceiver-config; } /* * Transceiver constraints for secondary path * Applicable to starting, terminating and regenerator * transceivers. */ augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE secondary explicit path (include or exclude) with transceiver configurations."; uses path-transceiver-config; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE secondary explicit path (exclude always) with transceiver configurations."; uses path-transceiver-config; } /* * Transceiver constraints for secondary reverse path * Applicable to starting, terminating and regenerator * transceivers. */ augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/" + "te:secondary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE secondary reverse explicit path (include or exclude) with transceiver configurations."; uses path-transceiver-config; } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/" + "te:secondary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE secondary reverse explicit path (exclude always) with transceiver configurations."; uses path-transceiver-config; } /* * Computed transceiver properties for primary path. */ augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE computed primary path with transceiver properties."; uses path-transceiver-state; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:source/" + "wdm-tnl:source-transponder/wdm-tnl:transceiver" { description "Augment source transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:destination/" + "wdm-tnl:destination-transponder/wdm-tnl:transceiver" { description "Augment destination transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:incoming-transponder/wdm-tnl:transceiver" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:outgoing-transponder/wdm-tnl:transceiver" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-incoming" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-outgoing" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } /* * Computed transceiver properties for primary reverse path. */ augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE computed primary path with transceiver properties."; uses path-transceiver-state; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:source/" + "wdm-tnl:source-transponder/wdm-tnl:transceiver" { description "Augment source transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:destination/" + "wdm-tnl:destination-transponder/wdm-tnl:transceiver" { description "Augment destination transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:incoming-transponder/wdm-tnl:transceiver" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:outgoing-transponder/wdm-tnl:transceiver" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-incoming" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths/" + "te:primary-path/te:primary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-outgoing" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } /* * Computed transceiver properties for secondary path. */ augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE computed primary path with transceiver properties."; uses path-transceiver-state; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:source/" + "wdm-tnl:source-transponder/wdm-tnl:transceiver" { description "Augment source transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:destination/" + "wdm-tnl:destination-transponder/wdm-tnl:transceiver" { description "Augment destination transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:incoming-transponder/wdm-tnl:transceiver" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:outgoing-transponder/wdm-tnl:transceiver" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-incoming" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths/" + "te:secondary-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-outgoing" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } /* * Computed transceiver properties for secondary reverse path. */ augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths/" + "te:secondary-reverse-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE computed primary path with transceiver properties."; uses path-transceiver-state; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths/" + "te:secondary-reverse-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:source/" + "wdm-tnl:source-transponder/wdm-tnl:transceiver" { description "Augment source transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths/" + "te:secondary-reverse-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:destination/" + "wdm-tnl:destination-transponder/wdm-tnl:transceiver" { description "Augment destination transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths/" + "te:secondary-reverse-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:incoming-transponder/wdm-tnl:transceiver" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths/" + "te:secondary-reverse-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:outgoing-transponder/wdm-tnl:transceiver" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths/" + "te:secondary-reverse-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-incoming" { description "Augment regen incoming transceiver with additional estimated parameters."; uses l0-types:path-properties; } augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths/" + "te:secondary-reverse-path/te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-outgoing" { description "Augment regen outgoing transceiver with additional estimated parameters."; uses l0-types:path-properties; } /* * Actual transceiver state. */ augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE LSP with WDM path state."; uses path-transceiver-state; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:source/" + "wdm-tnl:source-transponder/wdm-tnl:transceiver" { description "Augment source transceiver with additional measured parameters."; uses transceiver-measured-parameters; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:destination/" + "wdm-tnl:destination-transponder/wdm-tnl:transceiver" { description "Augment destination transceiver with additional measured parameters."; uses transceiver-measured-parameters; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:incoming-transponder/wdm-tnl:transceiver" { description "Augment regen incoming transceiver with additional measured parameters."; uses transceiver-measured-parameters; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerator/" + "wdm-tnl:regenerator/" + "wdm-tnl:outgoing-transponder/wdm-tnl:transceiver" { description "Augment regen outgoing transceiver with additional measured parameters."; uses transceiver-measured-parameters; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-incoming" { description "Augment regen incoming transceiver with additional measured parameters."; uses transceiver-measured-parameters; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-node-hop/te:numbered-node-hop/" + "wdm-tnl:node-position/wdm-tnl:regenerators/" + "wdm-tnl:regenerators/wdm-tnl:common-outgoing" { description "Augment regen outgoing transceiver with additional measured parameters."; uses transceiver-measured-parameters; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:numbered-link-hop/te:numbered-link-hop" { description "Augment TE LSP with end-to-end media channel information."; uses e2e-media-channel-info; } augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/" + "te:unnumbered-link-hop/te:unnumbered-link-hop" { description "Augment TE LSP with end-to-end media channel information."; uses e2e-media-channel-info; } /* * Augment TE label range information */ augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-in-segment/" + "te:label-restrictions/te:label-restriction" { description "Augment TE label range information for the ingress segment of the named path constraint."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-out-segment/" + "te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the egress segment of the named path constraint."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the ingress segment of the primay path."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the egress segment of the primay path."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the ingress segment of the primay reverse path."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the egress segment of the primay reverse path."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the ingress segment of the secondary path."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the egress segment of the secondary path."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the ingress segment of the secondary reverse path."; uses l0-types:wdm-label-range-info; } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction" { description "Augment TE label range information for the egress segment of the secondary reverse path."; uses l0-types:wdm-label-range-info; } /* * Augment TE label. */ augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/" + "te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects always excluded by the path computation with the named path constraint."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/" + "te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects included or excluded by the path computation with the named path constraint."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-in-segment/" + "te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the ingress segment of the named path constraint."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-in-segment/" + "te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the ingress segment of the named path constraint."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-in-segment/" + "te:label-restrictions/te:label-restriction/" + "te:label-step/te:technology" { description "Augment TE label range step for the ingress segment of the named path constraint."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-out-segment/" + "te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the egress segment of the named path constraint."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-out-segment/" + "te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the egress segment of the named path constraint."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:globals/te:named-path-constraints/" + "te:named-path-constraint/te:path-out-segment/" + "te:label-restrictions/te:label-restriction/" + "te:label-step/te:technology" { description "Augment TE label range step for the egress segment of the named path constraint."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-exclude-objects/" + "te:route-object-exclude-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects excluded by the path computation of the primary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-include-objects/" + "te:route-object-include-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects included by the path computation of the primary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects always excluded by the path computation of the primary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects included or excluded by the path computation of the primary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the ingress segment of the primay path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the ingress segment of the primay path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range step for the ingress segment of the primay path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the egress segment of the primay path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the egress segment of the primay path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range end for the egress segment of the primay path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/te:path-properties/" + "te:path-route-objects/te:path-route-object/" + "te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the route object of the computed primary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-exclude-objects/" + "te:route-object-exclude-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects excluded by the path computation of the primary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-include-objects/" + "te:route-object-include-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects included by the path computation of the primary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-exclude-always/" + "te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects always excluded by the path computation of the primary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-include-exclude/" + "te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects included or excluded by the path computation of the primary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the ingress segment of the primay reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the ingress segment of the primay reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range step for the ingress segment of the primay reverse path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the egress segment of the primay reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the egress segment of the primay reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range step for the egress segment of the primay reverse path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:primary-paths/te:primary-path/" + "te:primary-reverse-path/" + "te:computed-paths-properties/te:computed-path-properties/" + "te:path-properties/te:path-route-objects/" + "te:path-route-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the route object of the computed primary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-exclude-objects/" + "te:route-object-exclude-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects excluded by the path computation of the secondary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-include-objects/" + "te:route-object-include-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects included by the path computation of the secondary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects always excluded by the path computation of the secondary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects included or excluded by the path computation of the secondary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the ingress segment of the secondary path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the ingress segment of the secondary path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range step for the ingress segment of the secondary path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the egress segment of the secondary path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the egress segment of the secondary path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range step for the egress segment of the secondary path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-paths/te:secondary-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/" + "te:path-properties/te:path-route-objects/" + "te:path-route-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the route object of the computed secondary path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-exclude-objects/" + "te:route-object-exclude-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects excluded by the path computation of the secondary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:optimizations/te:algorithm/te:metric/" + "te:optimization-metric/te:explicit-route-include-objects/" + "te:route-object-include-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the optimization of the explicit route objects included by the path computation of the secondary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-exclude-always/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects always excluded by the path computation of the secondary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:explicit-route-objects/" + "te:route-object-include-exclude/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the explicit route objects included or excluded by the path computation of the secondary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the ingress segment of the secondary reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the ingress segment of the secondary reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-in-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range step for the ingress segment of the secondary reverse path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-start/" + "te:te-label/te:technology" { description "Augment TE label range start for the egress segment of the secondary reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-end/" + "te:te-label/te:technology" { description "Augment TE label range end for the egress segment of the secondary reverse path."; case wdm { uses l0-types:wdm-label-start-end; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:path-out-segment/te:label-restrictions/" + "te:label-restriction/te:label-step/te:technology" { description "Augment TE label range step for the egress segment of the secondary reverse path."; case wdm { uses l0-types:wdm-label-step; } } augment "/te:te/te:tunnels/te:tunnel/" + "te:secondary-reverse-paths/te:secondary-reverse-path/" + "te:computed-paths-properties/" + "te:computed-path-properties/" + "te:path-properties/te:path-route-objects/" + "te:path-route-object/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the route object of the computed secondary reverse path."; case wdm { uses l0-types:wdm-label-hop; } } augment "/te:te/te:lsps/" + "te:lsp/te:lsp-actual-route-information/" + "te:lsp-actual-route-information/te:type/te:label/" + "te:label-hop/te:te-label/te:technology" { description "Augment TE label hop for the actual route of the LSP."; case wdm { uses l0-types:wdm-label-hop; } } } ]]>

Security Considerations The configuration, state, and action data defined in this document are designed to be accessed via a management protocol with a secure transport layer, such as NETCONF or RESTCONF . The NETCONF access control model provides the means to restrict access for particular NETCONF users to a preconfigured subset of all available NETCONF protocol operations and content. There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: /te:te/te:tunnels/te:tunnel /te:te/.../te:te-bandwidth/te:technology /te:te/.../te:type/te:label/te:label-hop/te:te-label/te:technology /te:te/.../te:label-restrictions/te:label-restriction/te:label- start/te:te-label/te:technology /te:te/.../te:label-restrictions/te:label-restriction/te:label- end/te:te-label/te:technology /te:te/.../te:label-restrictions/te:label-restriction/ Editors note: we are using simplified description by folding similar branches to avoid repetition.

IANA Considerations This document requests IANA to register the following URIs in the "ns" subregistry within the "IETF XML Registry" . Following the format in , the following registrations are requested.

This document requests IANA to register the following YANG modules in the "IANA Module Names" . Following the format in , the following registrations are requested:

RFC Editor: Please replace XXXX with the RFC number assigned to this document.

&RFC7950; &RFC2119; &RFC8174; &RFC7446; &RFC7699; &RFC6241; &I-D.ietf-teas-yang-te; &I-D.ietf-ccamp-optical-impairment-topology-yang; &I-D.ietf-ccamp-flexigrid-yang; &RFC9094; &RFC8040; &RFC8341; &RFC3688; &RFC6020; &RFC6163; &RFC7698;

Acknowledgments This work is also partially funded by the Spanish State Research Agency under the project AgileMon (AEI PID2019-104451RB-C21) and by the Spanish Ministry of Science, Innovation and Universities under the program for the training of university lecturers (Grant number: FPU19/05678).

Contributors Old Dog Consulting

daniel@olddog.co.uk

Huawei Technologies

H1, Xiliu Beipo Village, Songshan Lake Dongguan China zhenghaomian@huawei.com

Huawei Technologies

italo.busi@huawei.com

Telefonica

oscar.gonzalezdedios@telefonica.com

Nokia

victor.lopez@nokia.com

Nokia

Dieter.Beller@nokia.com

CTTC

ricard.vilalta@cttc.es

Samsung

younglee.tx@gmail.com

ETRI

byyun@etri.re.kr

Universidad Autonoma de Madrid

daniel.michaud@estudiante.uam.es

Cisco

zali@cisco.com

Orange

esther.lerouzic@orange.com

Orange

julien.meuric@orange.com

Juniper

ggrammel@juniper.net

Cisco

manzoro@gmail.com