A YANG Data Model for WDM TunnelsFuturewei Technologiesaihuaguo.ietf@gmail.comNokiaSergio.belotti@nokia.comIndividualggalimbe56@gmail.comNaudit HPCNjorge.lopez_vergara@uam.esUniversidad Autonoma de Madriddaniel.perdices@uam.esCCAMP Working Groupnext generationunicornsparkling distributed ledgerThis 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).IntroductionTransport 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.TerminologyThe 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:
- clientserveraugmentdata modeldata nodeThe following terms are defined in and are not redefined here:
- configuration datastate dataOverviewThe 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 consideredGlobal transponder/transceiver configuration constraints, e.g., operational modes, tuning constraints of the transceiverGlobal optical performance constraints, e.g. generalized Signal-to-noise (G-SNR) margin of a feasible optical pathPath-scope WDM layer constraints, e.g. identities of transceivers assigned to the primary or secondary pathList of links that defines the pathOther optical attributesEach 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 UseIn 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 B 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 TunnelYANG TreeYANG Code file "ietf-wdm-tunnel@2023-10-22.yang"
module ietf-wdm-tunnel {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-wdm-tunnel";
prefix "wdm-tnl";
import ietf-te {
prefix "te";
revision-date "2023-06-16";
reference
"I-D.ietf-teas-yang-te-34: A YANG Data Model for Traffic
Engineering Tunnels, Label Switched Paths and Interfaces.";
}
import ietf-layer0-types {
prefix "l0-types";
}
organization
"IETF CCAMP Working Group";
contact
"WG Web:
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
}
/*
* Identities
*/
identity lower-first-wavelength-assignment {
base l0-types:wavelength-assignment;
description
"Assign first available wavelength starting from the
lowest frequency towards the highest frequency in
the allowable frequency range.";
}
identity upper-first-wavelength-assignment {
base l0-types:wavelength-assignment;
description
"Assign first available wavelength starting from the
highest frequency towards the lowest frequency in
the allowable frequency range.";
}
/*
* Groupings
*/
grouping tx-tune-constraints {
description
"This grouping defines the transmitter's allowed tuning
frequency range.";
container tx-tune-constraints {
description
"Transmitter's allowed tuning frequency range.";
uses l0-types:transmitter-tuning-range;
}
}
grouping transceiver-constraints-grp {
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 tx-tune-constraints;
}
grouping path-transceiver-config-grp {
description
"This grouping defines explicit transceiver configurations
on an end-to-end path.";
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-grp;
}
grouping path-transceiver-grp {
description
"This grouping defines group of transceivers on a node
functioning as starting, terminating transceivers, or
regenerators.";
container path-in-transceiver {
description
"Constraints for incoming direction transceiver
configurations";
uses path-transceiver-config-grp;
}
container path-out-transceiver {
description
"Constraints for outgoing direction transceiver
configurations";
uses path-transceiver-config-grp;
}
}
grouping global-transceiver-constraint {
description
"This grouping defines the constraints for transceiver
configurations.";
container transceiver-constraint {
description
"Constraints for transceiver configurations";
uses transceiver-constraints-grp;
}
}
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:gain-in-db-or-null;
units "dB";
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-always/"
+ "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-grp;
}
/*
* 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-always/"
+ "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-grp;
}
/*
* 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;
}
/*
* 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-always/"
+ "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-grp;
}
/*
* 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-always/"
+ "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-grp;
}
/*
* 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;
}
/*
* 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;
}
/*
* 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-always/"
+ "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-always/"
+ "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-always/"
+ "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-always/"
+ "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-always/"
+ "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-always/"
+ "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-always/"
+ "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-always/"
+ "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-always/"
+ "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-always/"
+ "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 ConsiderationsThe 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 ConsiderationsIt is proposed to IANA to assign new URIs from the "IETF XML
Registry" as follows:This document registers the following YANG module in the YANG Module Names
registry .A YANG Data Model for Wavelength Switched Optical Networks (WSONs)This document provides a YANG data model for the routing and wavelength assignment (RWA) TE topology in Wavelength Switched Optical Networks (WSONs). The YANG data model defined in this document conforms to the Network Management Datastore Architecture (NMDA).A YANG Data Model for Flexi-Grid Optical NetworksNaudit HPCNUniversidad Autonoma de MadridOld Dog ConsultingSamsungHuawei Technologies This document defines a YANG module for managing flexi-grid optical
networks. The model defined in this document specifies a flexi-grid
traffic engineering database that is used to describe the topology of
a flexi-grid network. It is based on and augments existing YANG
models that describe network and traffic engineering topologies.
The YANG data model defined in this document conforms to the Network
Management Datastore Architecture (NMDA).
The YANG 1.1 Data Modeling LanguageYANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).Key words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsRFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.Routing and Wavelength Assignment Information Model for Wavelength Switched Optical NetworksThis document provides a model of information needed by the Routing and Wavelength Assignment (RWA) process in Wavelength Switched Optical Networks (WSONs). The purpose of the information described in this model is to facilitate constrained optical path computation in WSONs. This model takes into account compatibility constraints between WSON signal attributes and network elements but does not include constraints due to optical impairments. Aspects of this information that may be of use to other technologies utilizing a GMPLS control plane are discussed.Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching RoutersGMPLS supports the description of optical switching by identifying entries in fixed lists of switchable wavelengths (called grids) through the encoding of lambda labels. Work within the ITU-T Study Group 15 has defined a finer-granularity grid, and the facility to flexibly select different widths of spectrum from the grid. This document defines a new GMPLS lambda label format to support this flexi-grid.This document updates RFCs 3471 and 6205 by introducing a new label format.Network Configuration Protocol (NETCONF)The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and InterfacesCisco Systems IncCisco Systems IncAlef EdgeJuniper NetworksIndividual This document defines a YANG data model for the provisioning and
management of Traffic Engineering (TE) tunnels, Label Switched Paths
(LSPs), and interfaces. The model covers data that is independent of
any technology or dataplane encapsulation and is divided into two
YANG modules that cover device-specific, and device independent data.
This model covers data for configuration, operational state, remote
procedural calls, and event notifications.
RESTCONF ProtocolThis document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).Network Configuration Access Control ModelThe standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.This document obsoletes RFC 6536.The IETF XML RegistryThis document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)This document provides a framework for applying Generalized Multi-Protocol Label Switching (GMPLS) and the Path Computation Element (PCE) architecture to the control of Wavelength Switched Optical Networks (WSONs). In particular, it examines Routing and Wavelength Assignment (RWA) of optical paths.This document focuses on topological elements and path selection constraints that are common across different WSON environments; as such, it does not address optical impairments in any depth. This document is not an Internet Standards Track specification; it is published for informational purposes.Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksTo allow efficient allocation of optical spectral bandwidth for systems that have high bit-rates, the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) has extended its Recommendations G.694.1 and G.872 to include a new Dense Wavelength Division Multiplexing (DWDM) grid by defining a set of nominal central frequencies, channel spacings, and the concept of the "frequency slot". In such an environment, a data-plane connection is switched based on allocated, variable-sized frequency ranges within the optical spectrum, creating what is known as a flexible grid (flexi-grid).Given the specific characteristics of flexi-grid optical networks and their associated technology, this document defines a framework and the associated control-plane requirements for the application of the existing GMPLS architecture and control-plane protocols to the control of flexi-grid DWDM networks. The actual extensions to the GMPLS protocols will be defined in companion documents.AcknowledgmentsThis 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).ContributorsOld Dog Consultingdaniel@olddog.co.ukHuawei TechnologiesH1, Xiliu Beipo Village, Songshan LakeDongguanChinazhenghaomian@huawei.comHuawei Technologiesitalo.busi@huawei.comTelefonicaoscar.gonzalezdedios@telefonica.comNokiavictor.lopez@nokia.comNokiaDieter.Beller@nokia.comCTTCricard.vilalta@cttc.esSamsungyounglee.tx@gmail.comETRIbyyun@etri.re.krUniversidad Autonoma de Madriddaniel.michaud@estudiante.uam.esCiscozali@cisco.com