]> A YANG Data Model for Optical Transport Network Topology Huawei Technologies
H1, Huawei Industrial Base, Songshan Lake Dongguan Guangdong 523808 China zhenghaomian@huawei.com
Huawei Technologies
italo.busi@huawei.com
Alef Edge
xufeng.liu.ietf@gmail.com
Nokia
sergio.belotti@nokia.com
Telefonica
oscar.gonzalezdedios@telefonica.com
Routing CCAMP Working Group This document defines a YANG data model for representing, retrieving, and manipulating Optical Transport Network (OTN) topologies. It is independent of control plane protocols and captures topological and resource-related information pertaining to OTN. The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Common Control and Measurement Plane Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .
Introduction A transport network is a server-layer network designed to provide connectivity services for a client-layer network to carry the client traffic transparently across the server-layer network resources. A transport network typically utilizes several different transport technologies such as the Optical Transport Networks (OTN) or packet transport such as provided by the MPLS-Transport Profile (MPLS-TP). This document defines a data model of an OTN topology, using YANG version 1.1 . The model can be used by an application communicating with a transport controller. Furthermore, it can be used by an application for the following purposes (but not limited to): To obtain a whole view of the network topology information of its interest; To receive notifications with regard to the information change of the OTN topology; To enforce the establishment and update to the network topology with the characteristics specified in the data model; The YANG model defined in this document is independent of control plane protocols and captures topology-related information pertaining to OTN electrical layer, as the scope specified by . Furthermore, it is not a stand-alone model, but augments from the TE topology YANG model defined in , and importing from the generic Layer 1 types defined in . Following TE topology YANG model, the YANG model defined in this document is interface independent. The model is included in , which indicates the typical usage of IETF YANG models in ACTN architecture specified by . More specifically, the usage of this model between controllers is described in . This model supports both client-configured and system-controlled OTN topologies, as described . These OTN topologies can be used as overlay or underlay topologies, using the mechanisms defined in and . The reader of this document is assumed to be familiar with the OTN technology, as specified in and with the TE topology YANG data model, as defined in . also provides a framework to allow the development of protocol extensions to support GMPLS and Path Computation Element (PCE) control of OTN. provides guidelines for writing technology- specific TE topology augmentations. The YANG data model in this document conforms to the Network Management Datastore Architecture defined in .
Terminology and Notations Some of the key terms used in this document are listed as follows.
TS:
Tributary Slot.
TSG:
Tributary Slot Granularity.
TPN:
Tributary Port Number.
Refer to 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 The terminology for describing YANG data models is found in .
Requirements Language 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.
Tree Diagram A simplified graphical representation of the data model is used in of this this document. The meaning of the symbols in these diagrams is defined in .
Prefix in Data Node Names In this document, the names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, as shown in . Prefix YANG module Reference l1-types ietf-layer1-types [RFCYYYY] otnt ietf-otn-topology RFC XXXX nw ietf-network nt ietf-network-topology tet ietf-te-topology
  • RFC Editor Note: Please replace XXXX with the number assigned to the RFC once this draft becomes an RFC. Please replace YYYY with the RFC numbers assigned to .
YANG Data Model for OTN Topology
OTN Topology Data Model Overview This document aims to describe the data model for OTN topology. As a classic Traffic-engineering (TE) technology, OTN provides TDM switching in transport network . Therefore, the YANG module presented in this document augments from a more generic Traffic Engineered (TE) network topology data model, i.e., the ietf- te-topology, as specified in . In , the guideline for augmenting TE topology model was provided, and in this draft, we augment the TE topology model to describe the topology in OTN. Common types, identities and groupings defined in is reused in this document. describes a network topology model and provides the fundamental model for . However, this work is not directly augmenting . shows the augmentation relationship.
The entities and TE attributes, such as node, termination points and links, are still applicable for describing an OTN topology and the model presented in this document only specifies technology-specific attributes/information. The OTN-specific attributes in , including the TPN, TS and TSG, can be used to represent the bandwidth and label information. These attributes have been specified in , and used in this document for augmentation of the generic TE topology model.
Attributes Augmentation There are a few characteristics augmenting the generic TE topology. Following the guidelines described in , an otn-topology network-type is specified as the indicator of OTN in the topology.
Three OTN technology-specific parameters that augment the generic TE link attributes are specified.
In OTN the resources is measured by the tributary slots (TS), as specified in . The tributary slot granularity (TSG) attribute defines the granularity, such as 1.25G, 2.5G and 5G, used by the TSs of a given OTN link. The distance attribute describes the geographical distance between a pair of OTN link termination points. This is usually measured by the length of the fibre. The OTN topology model also includes information about the access links that support the transparent client signals, defined in . These links can also be multi- function access links that can support one or more transparent client signals and OTN. A client-svc presence container is specified to augment the generic TE link termination point to describe if the point is capable of carrying a client signal and what kind of signal can be carried as follows. The same presence container is also specified for the TE link.
The list of supported-client-signal is used to provide the capabilities of the client signal specified in .
Bandwidth Augmentation Following the guidelines in , the model augments all the occurrences of the te-bandwidth container with the OTN technology- specific attributes using the otn-link-bandwidth and otn-path- bandwidth groupings defined in . The odtu-flex-type attribute of a given OTN Link (or Link Termination Point - LTP), shown in , is used, together with the OTN technology-specific attributes defined in the otn-link-bandwidth and otn-path-bandwidth groupings, to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on that OTN Link (or LTP). In order to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on an underlay path (e.g., the underlay path of a connectivity matrix entry), the odtu-flex-type attribute is added to the OTN technology-specific attributes defined in the otn-link-bandwidth and otn-path-bandwidth groupings.
Label Augmentation The model augments all the occurrences of the label-restriction list with OTN technology specific attributes using the otn-label-range- info grouping defined in . Moreover, following the guidelines in , the model augments all the occurrences of the te-label container with the OTN technology specific attributes using the otn-label-start-end, otn-label-hop and otn-label-step groupings defined in .
The YANG Model This YANG module references , , and .
WG List: Editor: Haomian Zheng Editor: Italo Busi Editor: Xufeng Liu Editor: Sergio Belotti Editor: Oscar Gonzalez de Dios "; description "This module defines a protocol independent Layer 1/ODU topology data model. The model fully conforms to the Network Management Datastore Architecture (NMDA). Copyright (c) 2024 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 Revised 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. 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 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; revision 2024-06-21 { description "Initial Revision"; reference "RFC XXXX: A YANG Data Model for Optical Transport Network Topology"; } // RFC Editor: replace XXXX with actual RFC number, update date // information and remove this note /* * Groupings */ grouping label-range-info { description "OTN technology-specific label range related information with a presence container indicating that the label range is an OTN technology-specific label range. This grouping SHOULD be used together with the otn-label-start-end and otn-label-step groupings to provide OTN technology-specific label information to the models which use the label-restriction-info grouping defined in the module ietf-te-types."; uses l1-types:otn-label-range-info { refine otn-label-range { presence "Indicates the label range is an OTN label range. This container MUST NOT be present if there are other presence containers or attributes indicating another type of label range."; } } } /* * Data nodes */ augment "/nw:networks/nw:network/nw:network-types/" + "tet:te-topology" { container otn-topology { presence "indicates a topology type of Optical Transport Network (OTN)-electrical layer."; description "OTN topology type"; } description "augment network types to include OTN."; } augment "/nw:networks/nw:network/nw:node/tet:te" + "/tet:te-node-attributes" { when "../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augment only for OTN."; } description "Augment TE node attributes."; container otn-node { presence "The TE node is an OTN node."; description "Introduce new TE node type for OTN node."; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes" { when "../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augment only for OTN."; } description "Augment link configuration"; container otn-link { description "Attributes of the OTN Link."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } leaf tsg { type identityref { base l1-types:tributary-slot-granularity; } description "Tributary slot granularity."; reference "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical Transport Network (OTN)"; } leaf distance { type uint32; description "distance in the unit of kilometers"; } } container client-svc { presence "When present, indicates that the Link supports Constant Bit Rate (CBR) client signals."; description "Attributes of the Link supporting CBR client signals."; leaf-list supported-client-signal { type identityref { base l1-types:client-signal; } min-elements 1; description "List of client signal types supported by the Link."; } } } augment "/nw:networks/nw:network/nw:node/nt:termination-point/" + "tet:te" { when "../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augment only for OTN."; } description "Augment link termination point (LTP) configuration."; container otn-link-tp { description "Attributes of the OTN Link Termination Point (LTP)."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link Termination Point (LTP)."; } } container client-svc { presence "When present, indicates that the Link Termination Point (LTP) supports Constant Bit Rate (CBR) client signals."; description "OTN LTP Service attributes."; leaf-list supported-client-signal { type identityref { base l1-types:client-signal; } description "List of client signal types supported by the LTP."; } } } /* * Augment TE bandwidth */ augment "/nw:networks/nw:network/nw:node/nt:termination-point/" + "tet:te/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment maximum LSP TE bandwidth for the link termination point (LTP)."; case otn { uses l1-types:otn-max-path-bandwidth { description "The odtu-flex-type attribute of the OTN Link Termination Point (LTP) is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN LTP."; } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE bandwidth path constraints of the TE node connectivity matrices."; case otn { uses l1-types:otn-link-bandwidth { augment otn-bandwidth { description "Augment OTN link bandwidth information."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up along the underlay paths of these OTN connectivity matrices."; } } } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE bandwidth path constraints of the connectivity matrix entry."; case otn { uses l1-types:otn-link-bandwidth { augment otn-bandwidth { description "Augment OTN link bandwidth information."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up along the underlay path of this OTN connectivity matrix entry."; } } } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE bandwidth path constraints of the TE node connectivity matrices information source."; case otn { uses l1-types:otn-link-bandwidth { augment otn-bandwidth { description "Augment OTN link bandwidth information."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up along the underlay paths of these OTN connectivity matrices."; } } } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE bandwidth path constraints of the connectivity matrix entry information source"; case otn { uses l1-types:otn-link-bandwidth { augment otn-bandwidth { description "Augment OTN link bandwidth information."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up along the underlay path of this OTN connectivity matrix entry."; } } } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:client-layer-adaptation/tet:switching-capability/" + "tet:te-bandwidth/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment client TE bandwidth of the tunnel termination point (TTP)"; case otn { uses l1-types:otn-link-bandwidth { augment otn-bandwidth { description "Augment OTN link bandwidth information."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs terminated on this OTN Tunnel Termination Point (TTP)."; } } } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/tet:path-constraints/" + "tet:te-bandwidth/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE bandwidth path constraints for the TTP Local Link Connectivities."; case otn { uses l1-types:otn-link-bandwidth { augment otn-bandwidth { description "Augment OTN link bandwidth information."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up along the underlay paths of these OTN Local Link Connectivities."; } } } } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/tet:path-constraints/" + "tet:te-bandwidth/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE bandwidth path constraints for the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-link-bandwidth { augment otn-bandwidth { description "Augment OTN link bandwidth information."; leaf odtu-flex-type { type l1-types:odtu-flex-type; description "The type of Optical Data Tributary Unit (ODTU) whose nominal bitrate is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up along the underlay path of this OTN Local Link Connectivity entry."; } } } } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment maximum LSP TE bandwidth for the TE link."; case otn { uses l1-types:otn-max-path-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment maximum TE bandwidth for the TE link"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment maximum reservable TE bandwidth for the TE link"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:unreserved-bandwidth/" + "tet:te-bandwidth" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment unreserved TE bandwidth for the TE Link"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:interface-switching-capability/" + "tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment maximum LSP TE bandwidth for the TE link information source"; case otn { uses l1-types:otn-max-path-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment maximum TE bandwidth for the TE link information source"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment maximum reservable TE bandwidth for the TE link information-source"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:unreserved-bandwidth/" + "tet:te-bandwidth" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment unreserved TE bandwidth of the TE link information source"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on this OTN Link."; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:interface-switching-capability/" + "tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { description "Augment maximum LSP TE bandwidth of the TE link template"; case otn { uses l1-types:otn-max-path-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on the OTN Link that uses this Link Template."; } } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth" { description "Augment maximum TE bandwidth the TE link template"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on the OTN Link that uses this Link Template."; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth" { description "Augment maximum reservable TE bandwidth for the TE link template."; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on the OTN Link that uses this Link Template."; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:unreserved-bandwidth/" + "tet:te-bandwidth" { description "Augment unreserved TE bandwidth the TE link template"; uses l1-types:otn-link-bandwidth { description "The odtu-flex-type attribute of the OTN Link is used to compute the number of Tributary Slots (TS) required by the ODUflex LSPs set up on the OTN Link that uses this Link Template."; } } /* * Augment TE label range information */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:label-restrictions/tet:label-restriction" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the TE node connectivity matrices."; uses label-range-info; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" + "tet:label-restrictions/tet:label-restriction" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the source LTP of the connectivity matrix entry."; uses label-range-info; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" + "tet:label-restrictions/tet:label-restriction" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the destination LTP of the connectivity matrix entry."; uses label-range-info; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/" + "tet:connectivity-matrices/tet:label-restrictions/" + "tet:label-restriction" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the TE node connectivity matrices information source."; uses label-range-info; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:from/tet:label-restrictions/tet:label-restriction" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the source LTP of the connectivity matrix entry information source."; uses label-range-info; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:to/tet:label-restrictions/tet:label-restriction" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the destination LTP of the connectivity matrix entry information source."; uses label-range-info; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:label-restrictions/tet:label-restriction" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the TTP Local Link Connectivities."; uses label-range-info; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:label-restrictions/tet:label-restriction" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the TTP Local Link Connectivity entry."; uses label-range-info; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the TE link."; uses label-range-info; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:label-restrictions/tet:label-restriction" { when "../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range information for the TE link information source."; uses label-range-info; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction" { description "Augment TE label range information for the TE link template."; uses label-range-info; } /* * Augment TE label */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/" + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the TE node connectivity matrices"; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:label-restrictions/" + "tet:label-restriction/tet:label-end/" + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the TE node connectivity matrices"; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:label-restrictions/" + "tet:label-restriction/tet:label-step/" + "tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the TE node connectivity matrices"; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:underlay/tet:primary-path/tet:path-element/" + "tet:type/tet:label/tet:label-hop/" + "tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay primary path of the TE node connectivity matrices"; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:underlay/tet:backup-path/tet:path-element/" + "tet:type/tet:label/tet:label-hop/" + "tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay backup path of the TE node connectivity matrices"; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-exclude-objects/" + "tet:route-object-exclude-object/" + "tet:type/tet:label/tet:label-hop/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects excluded by the path computation of the TE node connectivity matrices"; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-include-objects/" + "tet:route-object-include-object/" + "tet:type/tet:label/tet:label-hop/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects included by the path computation of the TE node connectivity matrices"; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/tet:label/tet:label-hop/" + "tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the computed path route objects of the TE node connectivity matrices"; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the source LTP of the connectivity matrix entry."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-end/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the source LTP of the connectivity matrix entry."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-step/" + "tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the source LTP of the connectivity matrix entry."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the destination LTP of the connectivity matrix entry."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-end/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the destination LTP of the connectivity matrix entry."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-step/" + "tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the destination LTP of the connectivity matrix entry."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:primary-path/tet:path-element/" + "tet:type/tet:label/tet:label-hop/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay primary path of the connectivity matrix entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:backup-path/tet:path-element/" + "tet:type/tet:label/tet:label-hop/" + "tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay backup path of the connectivity matrix entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:optimizations/" + "tet:algorithm/tet:metric/tet:optimization-metric/" + "tet:explicit-route-exclude-objects/" + "tet:route-object-exclude-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects excluded by the path computation of the connectivity matrix entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:optimizations/" + "tet:algorithm/tet:metric/tet:optimization-metric/" + "tet:explicit-route-include-objects/" + "tet:route-object-include-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects included by the path computation of the connectivity matrix entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the computed path route objects of the connectivity matrix entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/" + "tet:connectivity-matrices/tet:label-restrictions/" + "tet:label-restriction/" + "tet:label-start/tet:te-label/tet:technology" { when "../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the TE node connectivity matrices information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/" + "tet:connectivity-matrices/tet:label-restrictions/" + "tet:label-restriction/" + "tet:label-end/tet:te-label/tet:technology" { when "../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the TE node connectivity matrices information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/" + "tet:connectivity-matrices/tet:label-restrictions/" + "tet:label-restriction/" + "tet:label-step/tet:technology" { when "../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the TE node connectivity matrices information source."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay primary path of the TE node connectivity matrices of the information source entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay backup path of the TE node connectivity matrices of the information source entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-exclude-objects/" + "tet:route-object-exclude-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects excluded by the path computation of the TE node connectivity matrices information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-include-objects/" + "tet:route-object-include-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects included by the path computation of the TE node connectivity matrices information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the computed path route objects of the TE node connectivity matrices information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:from/tet:label-restrictions/" + "tet:label-restriction/" + "tet:label-start/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the source LTP of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:from/tet:label-restrictions/" + "tet:label-restriction/" + "tet:label-end/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the source LTP of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:from/tet:label-restrictions/" + "tet:label-restriction/" + "tet:label-step/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the source LTP of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:to/tet:label-restrictions/tet:label-restriction/" + "tet:label-start/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the destination LTP of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:to/tet:label-restrictions/tet:label-restriction/" + "tet:label-end/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the destination LTP of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:to/tet:label-restrictions/tet:label-restriction/" + "tet:label-step/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the destination LTP of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay primary path of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay backup path of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-exclude-objects/" + "tet:route-object-exclude-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects excluded by the path computation of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-include-objects/" + "tet:route-object-include-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects included by the path computation of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the computed path route objects of the connectivity matrix entry information source."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/" + "tet:te-label/tet:technology" { when "../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-end/" + "tet:te-label/tet:technology"{ when "../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-step/" + "tet:technology"{ when "../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay primary path of the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay backup path of the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-exclude-objects/" + "tet:route-object-exclude-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects excluded by the path computation of the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-include-objects/" + "tet:route-object-include-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects included by the path computation of the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the computed path route objects of the TTP Local Link Connectivities."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-end/tet:te-label/tet:technology" { when "../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-step/tet:technology" { when "../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay primary path of the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay backup path of the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-exclude-objects/" + "tet:route-object-exclude-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects excluded by the path computation of the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:optimizations/tet:algorithm/tet:metric/" + "tet:optimization-metric/" + "tet:explicit-route-include-objects/" + "tet:route-object-include-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the explicit route objects included by the path computation of the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/" + "tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the computed path route objects of the TTP Local Link Connectivity entry."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay primary path of the TE link."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { when "../../../../../../../../" + "nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label hop for the underlay backup path of the TE link."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the TE link."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-end/tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the TE link."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-step/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the TE link."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range start for the TE link information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-end/tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range end for the TE link information source."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-step/tet:technology" { when "../../../../../../nw:network-types/tet:te-topology/" + "otnt:otn-topology" { description "Augmentation parameters apply only for networks with OTN topology type."; } description "Augment TE label range step for the TE link information source."; case otn { uses l1-types:otn-label-step; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { description "Augment TE label hop for the underlay primary path of the TE link template."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { description "Augment TE label hop for the underlay backup path of the TE link template."; case otn { uses l1-types:otn-label-hop; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-start/tet:te-label/tet:technology" { description "Augment TE label range start for the TE link template."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-end/tet:te-label/tet:technology" { description "Augment TE label range end for the TE link template."; case otn { uses l1-types:otn-label-start-end; } } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:label-restrictions/tet:label-restriction/" + "tet:label-step/tet:technology" { description "Augment TE label range step for the TE link template."; case otn { uses l1-types:otn-label-step; } } } ]]>
IANA Considerations It is proposed to IANA to assign new URIs from the "IETF XML Registry" as follows:
This document registers a YANG module in the YANG Module Names registry .
  • RFC Editor Note: Please replace XXXX with the number assigned to the RFC once this draft becomes an RFC.
Security Considerations This section is modeled after the template described in Section 3.7 of . The "ietf-te-types" and the "ietf-te-packet-types" YANG modules define data models that are designed to be accessed via YANG-based management protocols, such as NETCONF and RESTCONF . These protocols have to use a secure transport layer (e.g., SSH , TLS , and QUIC ) and have to use mutual authentication. The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF 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 can 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. Specifically, the following subtrees and data nodes have particular sensitivities/vulnerabilities: "/nw:networks/nw:network/nw:network-types/tet:te-topology/otnt:otn-topology"
  • This subtree specifies the OTN topology type. Modifying the configurations can render the OTN topology type invalid. By making such modifications, a malicious attacker may disable the OTN capabilities on the related networks and cause traffic to be disrupted or misrouted.
"/nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes/otnt:otn-node"
  • This subtree specifies the OTN node type. By configuring the OTN node type, an attacker may create an unauthorized OTN traffic path. By removing it, a malicious attacker may cause OTN traffic to be disabled or misrouted. Such traffic changes may also affect the traffic on the surrounding OTN nodes and OTN links in this OTN topology and the connected OTN topologies.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:otn-link/otnt:odtu-flex-type"
  • This node is used, together with the other attributes in the otn-bandwidth container, to compute the OTN bandwidth information for an OTN link, as described in . By configuring, modifying or removing this data node, a malicious attacker may modify the OTN bandwidth. The consequences of modifying the OTN bandwidth are reported below for the otn-bandwidth container.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:otn-link/otnt:tsg"
  • This node represents the TSG of the OTN link, as described in . By configuring, modifying or removing this data node, a malicious attacker may modify the resouces assigned to the OTN LSPs setup over that OTN link. The consequences of modifying the TSG would be to disrupt the traffic carried by the OTN LSPs setup over that OTN link.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:otn-link/otnt:distance"
  • This node is describes the geographical distance between a pair of OTN link termination points. By configuring, modifying or removing the distance, an attacker may cause OTN traffic to be misrouted. Such traffic changes may also affect the traffic on the surrounding OTN nodes and OTN links in this OTN topology and the connected OTN topologies.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:client-svc"
  • This subtree specifies the client traffic type supported by a link. By configuring it, an attacker may create an unauthorized client traffic path. By removing it, a malicious attacker may cause client traffic to be disabled or misrouted. Such traffic changes may also affect the traffic on the surrounding OTN nodes and OTN links in this OTN topology and the connected OTN topologies.
"/nw:networks/nw:network/nw:node/nt:termination-point/tet:te/otnt:otn-link-tp/otnt:odtu-flex-type"
  • This node is used, together with the other attributes in the otn-bandwidth container, to compute the OTN bandwidth information for an OTN link termination point, as described in . By configuring, modifying or removing this data node, a malicious attacker may modify the OTN bandwidth. The consequences of modifying the OTN bandwidth are reported below for the otn-bandwidth container.
"/nw:networks/nw:network/nw:node/nt:termination-point/tet:te/otnt:client-svc"
  • This subtree specifies the client traffic type supported by a link termination point. By configuring it, an attacker may create an unauthorized client traffic path. By removing it, a malicious attacker may cause client traffic to be disabled or misrouted. Such traffic changes may also affect the traffic on the surrounding OTN nodes and OTN links in this OTN topology and the connected topologies.
"otnt:otn-bandwidth"
  • This subtree specifies the configurations of OTN technology-specific information under any occurrence of the tet:te-bandwidth container, as defined in (e.g., "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:max-resv-link-bandwidth/tet:te-bandwidth/otnt:otn-bandwidth"). By configuring the OTN bandwidth attributes, an attacker may create an unauthorized OTN traffic path. By removing or modifying it, a malicious attacker may cause OTN traffic to be disabled or misrouted. Such traffic changes may also affect the traffic on the surrounding OTN nodes and OTN links in this OTN topology and the connected OTN topologies.
"otnt:otn-label-range"
  • This subtree specifies the configurations of OTN technology-specific label range information under any occurrence of the tet:te-label-restriction container, as defined in (e.g., "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:label-restrictions/tet:label-restriction\otnt:otn-label-range"). By configuring the OTN label range attributes, an attacker may create an unauthorized OTN traffic path. By removing or modifying, a malicious attacker may cause OTN traffic to be disabled or misrouted. Such traffic changes may also affect the traffic on the surrounding OTN nodes and OTN links in this OTN topology and the connected OTN topologies.
"otnt:otn-label"
  • This subtree specifies the configurations of OTN technology-specific label information under any occurrence of the tet:te-label container, as defined in (e.g., "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:label-restrictions/tet:label-restriction/tet:label-start/tet:te-label/tet:technology/otnt:otn-label"). By configuring, removing or modifying the OTN label attributes, a malicious attacker may cause OTN traffic to be disabled or misrouted. Such traffic changes may also affect the traffic on the surrounding OTN nodes and OTN links in this OTN topology and the connected OTN topologies.
Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. Specifically, the following subtrees and data nodes have particular sensitivities/vulnerabilities: "/nw:networks/nw:network/nw:network-types/tet:te-topology/otnt:otn-topology"
  • Unauthorized access to this subtree can disclose the OTN topology type.
"/nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes/otnt:otn-node"
  • Unauthorized access to this subtree can disclose the OTN nodes.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:otn-link/otnt:odtu-flex-type"
  • This node is used, together with the other attributes in the otn-bandwidth container, to compute the OTN bandwidth information for an OTN link, as described in . Unauthorized access to this data node can disclose the OTN bandwidth information of OTN links.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:otn-link/otnt:tsg"
  • Unauthorized access to this data node can disclose configuration information of OTN links.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:otn-link/otnt:distance"
  • Unauthorized access to this data node can disclose state information of OTN links.
"/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/otnt:client-svc"
  • Unauthorized access to this data node can disclose capabilities of OTN links.
"/nw:networks/nw:network/nw:node/nt:termination-point/tet:te/otnt:otn-link-tp/otnt:odtu-flex-type"
  • This node is used, together with the other attributes in the otn-bandwidth container, to compute the OTN bandwidth information for an OTN link termination point, as described in . Unauthorized access to this data node can disclose the OTN bandwidth information of OTN link termination points.
"/nw:networks/nw:network/nw:node/nt:termination-point/tet:te/otnt:client-svc"
  • Unauthorized access to this data node can disclose capabilities of OTN link termination points.
"otnt:otn-bandwidth"
  • This subtree specifies the configurations of OTN technology-specific information under any occurrence of the tet:te-bandwidth container, as defined in (e.g., "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:max-resv-link-bandwidth/tet:te-bandwidth/otnt:otn-bandwidth"). Unauthorized access to this data node can disclose the OTN bandwidth information of OTN links and link termination points.
"otnt:otn-label-range"
  • This subtree specifies the configurations of OTN technology-specific label range information under any occurrence of the tet:te-label-restriction container, as defined in (e.g., "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:label-restrictions/tet:label-restriction\otnt:otn-label-range"). Unauthorized access to this data node can disclose the state information of OTN links and link termination points.
"otnt:otn-label"
  • This subtree specifies the configurations of OTN technology-specific label information under any occurrence of the tet:te-label container, as defined in (e.g., "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:label-restrictions/tet:label-restriction/tet:label-start/tet:te-label/tet:technology/otnt:otn-label"). Unauthorized access to this data node can disclose the state information of OTN links and link termination points.
This YANG module does not define RPC operations. This YANG module uses groupings from other YANG modules that define nodes that may be considered sensitive or vulnerable in network environments. Refer to the Security Considerations of for information as to which nodes may be considered sensitive or vulnerable in network environments. Finally, the YANG module described in this document augments the "ietf-network" YANG module and the "ietf-te-topology" YANG module by adding data nodes. The security considerations for the subtrees described in those RFCs apply equally to the new data nodes that this module adds.
Interfaces for the optical transport network ITU-T Recommendation G.709 The YANG 1.1 Data Modeling Language YANG 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). YANG Data Model for Traffic Engineering (TE) Topologies This document defines a YANG data model for representing, retrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that other technology-specific TE topology models can augment. Common YANG Data Types for Layer 1 Networks Huawei Technologies Huawei Technologies This document defines a collection of common common data types, identities, and groupings in the YANG data modeling language. These derived common common data types, identities, and groupings are intended to be imported by modules that model Layer 1 configuration and state capabilities. The Layer 1 types are representative of Layer 1 client signals applicable to transport networks, such as Optical Transport Networks (OTN). The Optical Transport Network (OTN) data structures are included in this document as Layer 1 types. A YANG Data Model for Network Topologies This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models. Network Management Datastore Architecture (NMDA) Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. 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] Key words for use in RFCs to Indicate Requirement Levels In 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 Words RFC 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. GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport Networks ITU-T Recommendation G.709 [G709-2012] introduced new Optical channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e, and ODUflex) and enhanced Optical Transport Network (OTN) flexibility. This document updates the ODU-related portions of RFC 4328 to provide extensions to GMPLS signaling to control the full set of OTN features, including ODU0, ODU4, ODU2e, and ODUflex. The IETF XML Registry This 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. Network Configuration Access Control Model The 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. Framework for GMPLS and PCE Control of G.709 Optical Transport Networks This document provides a framework to allow the development of protocol extensions to support Generalized Multi-Protocol Label Switching (GMPLS) and Path Computation Element (PCE) control of Optical Transport Networks (OTNs) as specified in ITU-T Recommendation G.709 as published in 2012. Applicability of YANG models for Abstraction and Control of Traffic Engineered Networks Samsung Huawei Cisco ETRI Nokia Abstraction and Control of TE Networks (ACTN) refers to the set of virtual network operations needed to orchestrate, control and manage large-scale multi-domain TE networks, so as to facilitate network programmability, automation, efficient resource sharing, and end-to- end virtual service aware connectivity and network function virtualization services. This document explains how the different types of YANG models defined in the Operations and Management Area and in the Routing Area are applicable to the ACTN framework. This document also shows how the ACTN architecture can be satisfied using classes of data model that have already been defined, and discusses the applicability of specific data models that are under development. It also highlights where new data models may need to be developed. Framework for Abstraction and Control of TE Networks (ACTN) Traffic Engineered (TE) networks have a variety of mechanisms to facilitate the separation of the data plane and control plane. They also have a range of management and provisioning protocols to configure and activate network resources. These mechanisms represent key technologies for enabling flexible and dynamic networking. The term "Traffic Engineered network" refers to a network that uses any connection-oriented technology under the control of a distributed or centralized control plane to support dynamic provisioning of end-to- end connectivity. Abstraction of network resources is a technique that can be applied to a single network domain or across multiple domains to create a single virtualized network that is under the control of a network operator or the customer of the operator that actually owns the network resources. This document provides a framework for Abstraction and Control of TE Networks (ACTN) to support virtual network services and connectivity services. Transport Northbound Interface Applicability Statement Huawei Old Dog Consulting Huawei CAICT This document provides an analysis of the applicability of the YANG models defined by the IETF (in particular in the Traffic Engineering Architecture and Signaling (TEAS) and Common Control and Measurement Plane (CCAMP) working groups) to support ODU transit services, transparent client services, and Ethernet Private Line/Ethernet Virtual Private Line (EPL/EVPL) services over Optical Transport Network (OTN) in single and multi-domain network scenarios. This document also describes how existing YANG models can be used through several worked examples and JSON fragments. YANG Tree Diagrams This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. Guidelines for Authors and Reviewers of Documents Containing YANG Data Models YumaWorks Orange Huawei This memo provides guidelines for authors and reviewers of specifications containing YANG modules, including IANA-maintained modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) and RESTCONF protocol implementations that utilize YANG modules. This document obsoletes RFC 8407. Also, this document updates RFC 8126 by providing additional guidelines for writing the IANA considerations for RFCs that specify IANA-maintained modules. The document also updates RFC 6020 by clarifying how modules and their revisions are handled by IANA. RESTCONF Protocol This 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). The Secure Shell (SSH) Authentication Protocol The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are described in separate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK] The Transport Layer Security (TLS) Protocol Version 1.3 This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. QUIC: A UDP-Based Multiplexed and Secure Transport This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. JSON Encoding of Data Modeled with YANG This document defines encoding rules for representing configuration data, state data, parameters of Remote Procedure Call (RPC) operations or actions, and notifications defined using YANG as JavaScript Object Notation (JSON) text.
YANG Tree This section provides the YANG Tree of the OTN topology data model.
JSON Examples This appendix contains an example of an instance data tree in JSON encoding . The example instantiates the "ietf-otn-topology" model for the OTN topology depicted in below. The OTN topology consists of three nodes (D1, D2, and D3) with three link termination (LTPs) each: two LTPs which terminates the links that belongs to the OTN topology and one LTP which terminates inter- domain links, as defined in . The OTN links within the OTN network are 100G OTN links while the links at the edge of the network are 10G links. All these OTN links support ODU4, ODU2 and ODU0 connections. The link between nodes D1 and D2 also supports ODUflex. The OTN links within the OTN network are bidirectional and symmetrical: for this reasons, the link attributes (e.g., support for OTN switching capability or transparent client signal and the OTN maximum link bandwidth) are instantiated only on the link representing the forward direction, while the link representing the reverse direction are instantiated without any link attribute (other than the name) to indicate that the OTN links are bidirectional and symmetrical. The link between nodes D1 and D2 is an example of a multi-function link, as defined in , which can support both OTN and 100G client signal (e.g., 100GE): the interface-switching-capability list indicates support for OTN switching capability and the client-svc presence container is instantiated. For the LTPs which terminate OTN links, only the identifiers information is instantiated. All the other properties are defined in the links they terminate. For the LTPs at the edge network, additional properties are instantiated to indicate whether the link can support OTN or transparent client signals. In particular: LTP 1 on Node D1 is an example of an LTP terminating a multi- function access link, as defined in , which can support both OTN and 10G client signals (e.g., 10GE and STM-64): the interface-switching-capability list indicates support for OTN switching capability and the client-svc presence container is instantiated; LTP 2 on Node D2 is an example of an LTP which can support only 10G OTN (ODU2) signal: the interface-switching-capability list indicates support for OTN switching capability and the client-svc presence container is not instantiated; LTP 3 on Node D3 is an example of an LTP which can support only 10G (e.g., 10GE and STM-64) client signals: the interface- switching-capability list does not indicate support for OTN switching capability and the client-svc presence container is instantiated.
| | 1 | | | | 2 | |<----------------| | 2 | | \-/ 3 \-/ \-/ 3 \-/ | /----\ | | /----\ | +---| |---+ +---| |---+ \----/ \----/ A | A | | | | | | | | | | | +------------+ | | | | | D3 | | | | | /-\ /-\ | | | +----->| | 1 | |-------+ | +---------| | 2 | |<---------+ \-/ 3 \-/ | /----\ | +---| |---+ \----/ ]]>
Acknowledgments We would like to thank Igor Bryskin, Zhe Liu, Zheyu Fan and Daniele Ceccarelli for their comments and discussions.
Contributors Futurewei
aihuaguo.ietf@gmail.com
Google
ansha@google.com
CAICT
xuyunbin@caict.ac.cn
China Mobile
wangleiyj@chinamobile.com
Huawei Technologies
raobaoquan@huawei.com
Huawei Technologies
Huawei Technologies
Hai Gaoming BV
huubatwork@gmail.com
Nokia
victor.lopez@nokia.com
China Mobile
liyunbo@chinamobile.com
Nokia
dieter.beller@nokia.com