]> A YANG Data Model for WDM Tunnels 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 Wavelength Switched Optical Networks (WSON) systems based on only fixed-grid wavelength switching, towards elastic optical networks, based on flexi-grid Dense Wavelength Division Multiplexing (DWDM) transmission and switching technologies . Such technology aims at increasing transport network scalability and flexibility, allowing bandwidth usage optimization. While focus on flexi-grid objects such as nodes, transponders and links, this document presents a YANG model for the provisioning and management of Traffic Engineering (TE) tunnels and Label Switched Paths (LSPs) in DWDM Optical Networks, which can be Wavelength Switched Optical Networks (WSON) networks or Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks, or a mix of these two networks. This YANG module defines the path from a source transponder or node to the destination through several intermediate nodes in such a WDM optical network. 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 generic TE tunnel attributes, such as source and destination node addresses, source and destination tunnel termination points (TTPs), are already defined by the base data model in . The present model defines a WDM tunnel by augmenting the base model with the following WDM technology-specific constructs: Global WDM layer constraints that influence the TE path selection, e.g., whether wavelength conversion or regeneration is considered Global transponder/transceiver configuration constraints, e.g., operational modes, tuning constraints of the transceiver Global optical performance constraints, e.g. generalized Signal-to-noise (G-SNR) margin of a feasible optical path Path-scope WDM layer constraints, e.g. identities of transceivers assigned to the primary or secondary path List of links that defines the path Other optical attributes Each path can be a segment path (only defined by the source and destination nodes or link termination points) or an end-to-end path (additionally needs source and destination transponders). Therefore, all the attributes are optional to support both situations.
Example of Use In order to explain how this model is used, the following example is provided. An optical network usually has multiple transponders, switches (nodes) and links. shows a simple topology, where two physical paths interconnect two optical transponders via a combination of both WSON and Flexi-grid wavelength switched nodes and links.
WDM Primary Path <---------------------------------------------------> +----------+ +----------+ | Flexi- | | Flexi- | | grid | | grid | | node A | | node E | | | +------+ +------+ | | | | Link 1 |Flexi-| Link 2 | WSON | Link 3 | | | |<------>| grid |<------>| |<------>| | |......... | |node B| |node C| | .........| | Trans- : | +------+ +------+ | : Trans- | | ponder : | | : ponder | | A : | +----------+ | : E | |........: | Link 4 |Flexi-grid| Link 5 | :........| | | | D | | | | |<------------>| node |<------------>| | | | +----------+ | | +----------+ +----------+ <---------------------------------------------------> WDM Secondary Path ]]>
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 "2023-10-22" { 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 } /* * 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."; container tx-tune-constraints { description "The permissible tuning frequency range for the transmitter."; uses l0-types:transmitter-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."; } } 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-config { description "This grouping defines explicit transceiver configurations."; leaf transponder-id { type uint32; description "transponder identifier"; } list transceivers { key "lane-id"; description "List of transceivers for all lanes."; leaf lane-id { type uint8; must '. >= 1' { error-message "Lane identifier must be greater than or equal to 1."; } description "Lane identifier starting from 1."; } leaf transceiver-id { type uint32; description "transceiver identifier"; } uses transceiver-constraints; } } grouping path-transceiver-config { description "This grouping defines a set of transceivers on a node, serving as either starting transceivers, terminating transceivers, or regenerators. The position of each transceiver is determined by the direction of the path. For instance, consider the following uni-directional path with nodes labeled A, B, and C, where a, b1, b2, and c correspond to transceivers on the nodes: A(a) --> (b1)B(b2) --> (c)C - Use path-out-transceiver for the starting transceiver a and the regenerator transceiver b2. - Use path-in-transceiver for the terminating transceiver c and the regenerator transceiver b1."; container path-in-transceiver { description "Constraints for incoming direction transceiver configurations"; uses transceiver-config; } container path-out-transceiver { description "Constraints for outgoing direction transceiver configurations"; uses transceiver-config; } } grouping transceiver-state { description "This grouping includes common transceiver state information."; leaf transponder-id { type uint32; description "transponder identifier"; } list transceivers { key "lane-id"; description "List of transceivers for all lanes."; leaf lane-id { type uint8; must '. >= 1' { error-message "Lane identifier must be greater than or equal to 1."; } description "Lane identifier starting from 1."; } leaf transceiver-id { type uint32; description "transceiver identifier"; } uses l0-types:common-transceiver-readonly-param; } } grouping path-transceiver-state { description "This grouping defines the state of transceivers on a node functioning as starting, terminating transceivers, or regenerators."; container path-in-transceiver { description "Transceiver state on the incoming direction."; uses transceiver-state; } container path-out-transceiver { description "Transceiver state on the outgoing direction."; uses transceiver-state; } } 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; uses l0-types:l0-path-constraints; 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 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:l0-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."; } } } grouping wdm-path-state { description "Grouping for WDM path state."; container wdm-path-state { config false; description "WDM path state."; leaf gsnr { type l0-types:snr; description "Actual received GSNR for the WDM path."; } } } /* * 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; } /* * 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-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE primary path 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-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE primary reverse path 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-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE secondary path 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-exclude-always/te:type/" + "te:numbered-node-hop/te:numbered-node-hop" { description "Augment TE secondary reverse path with transceiver configurations."; uses path-transceiver-config; } /* * Computed path 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" { description "Augment TE computed primary path with WDM properties."; uses l0-types:l0-path-properties; } /* * Computed path 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" { description "Augment TE computed primary reverse path with WDM properties."; uses l0-types:l0-path-properties; } /* * Computed path 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" { description "Augment TE computed secondary path with WDM properties."; uses l0-types:l0-path-properties; } /* * Computed path 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" { description "Augment TE computed secondary reverse path with WDM properties."; uses l0-types:l0-path-properties; } /* * 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; } /* * 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; } /* * 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; } /* * 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; } /* * WDM path state */ augment "/te:te/te:lsps/te:lsp/" + "te:lsp-actual-route-information" { description "Augment TE LSP to with WDM path state."; uses wdm-path-state; } /* * 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 to with WDM path state."; uses path-transceiver-state; } /* * 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.
&RFC9094; &I-D.ietf-ccamp-flexigrid-yang; &RFC7950; &RFC2119; &RFC8174; &RFC7446; &RFC7699; &RFC6241; &I-D.ietf-teas-yang-te; &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