| Internet-Draft | RDNM YANG | April 2025 |
| Yu, et al. | Expires 12 October 2025 | [Page] |
This document defines two extension YANG data models augmenting to TE topology and TE tunnel modules, based on the RDNM (Rich-Detail Network Management) requirements in transport networks.¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://github.com/YuChaode/rdnm-yang/draft-yu-ccamp-rdnm-yang.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-yu-ccamp-rdnm-yang/.¶
Discussion of this document takes place on the Common Control and Measurement Plane Working Group mailing list (mailto:[email protected]), which is archived at https://mailarchive.ietf.org/arch/browse/ccamp/. Subscribe at https://www.ietf.org/mailman/listinfo/ccamp/.¶
Source for this draft and an issue tracker can be found at https://github.com/ https://github.com/YuChaode/rdnm-yang.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 12 October 2025.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
[RFC8795] defines a YANG data module for technology generic, and it is augmented by some other technology specific data modules, e.g. OTN topology data model in [I-D.draft-ietf-ccamp-otn-topo-yang].¶
[I-D.draft-ietf-teas-yang-te] defines a YANG data model for the provisioning and management of Traffic Engineering (TE) tunnels, Label Switched Paths (LSPs), and interfaces. Similarly, it could be also augmented by some other technology specific data modules to implement a specific layer of TE tunnel.¶
According to [I-D.draft-ietf-ccamp-transport-nbi-app-statement], it is good to used the current TE data model system to manage an abstracted network topology. In [I-D.draft-gstk-ccamp-actn-optical-transport-mgmt], it is called Abstracted Control (AC) approach.¶
In [I-D.draft-gstk-ccamp-actn-optical-transport-mgmt], it also raised another management approach, which is called Rich-Detail Network Management (RDNM). RDNM is designed to continue to deliver FCAPS capabilities within the context of ACTN.¶
[ITU-T_G.805] describes transport network from the viewpoint of the information transfer capability, provides a generic functional architecture which is also implementation independent. This recommendation is the implementation basis of most of the vendors' or operators' systems.¶
To provide traditional FCAPS functionalities, we need to align with the modelling of traditional approach, which is suggested to be [TMF-814]. Therefore, some more TMF attributes would be introduced. To avoid introducing non-backward-compatible (NBC) changes, we would like to provide some extension YANG data models, based on the current model architecture.¶
Some extensions, which are generic for all network layers, are defined in the RDNM topology and RDNM tunnel models. Layer-specific RDNM extensions can be found in other YANG data modules.¶
Note: to be added on demand.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
A simplified graphical representation of the data model is used in this document. The meaning of the symbols in this diagram is defined in [RFC8340].¶
In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, as showned in the following table.¶
| Prefix | Yang Module | Reference |
|---|---|---|
| nw | ietf-network | [RFC8345] |
| nt | ietf-network-topology | [RFC8345] |
| tet | ietf-te-topology | [RFC8795] |
| yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] |
| te | ietf-te | RFCYYYY |
| te-types | ietf-te-types | [RFC8776] |
| rdnmt | ietf-rdnm-topology | RFC XXXX |
| rdnm-tnl | ietf-rdnm-tunnel | RFC XXXX |
| rdnm-types | ietf-rdnm-types | RFC XXXX |
RFC Editor Note: Please replace XXXX with the RFC number assigned to this document. Please replace YYYY with the RFC number assigned to the TE tunnel draft. Please remove this note.¶
[ITU-T_G.805] describes the network as a transport network from the viewpoint of the information transfer capability. More specifically, the functional and structural architecture of transport networks are described independently of networking technology. It also defines various types of reference points, such as the Access Point (AP), Connection Point (CP), and Trail Connection Point (TCP), and the processing between reference points, which is called adaptation. A transport entity that transmits information such as trails and connections between reference points. For the details, we can refer to descriptions in chapter 3 of [ITU-T_G.805] and Figure 1 to Figure 3.¶
One disadvantage of [ITU-T_G.805] is it is too complicated. So TMF simplifies the modelling system of [ITU-T_G.805]. The adaptation is changed to be the capabilities of reference points. The reference points is so that changed to some other terminologies, e.g. PTP and FTP etc. This simplification still can be mapped to [ITU-T_G.805]. So that a lot of vendors and operators choose TMF modelling in their system.¶
Based on the TMF modelling, CORBA/XML interface was defined to provide FCAPS interfaces. These interfaces were widely used in the operators' network.¶
The transport ACTN is also initially designed to simplify network configurations. To have a unified modelling with IP technology, many new modelling terms of TE were introduced and build up a new modelling system. Theoretically, these new modelling objects should be a part of, or can be mapped to the reference points or adaptation defined by [ITU-T_G.805]. However, in the existing IETF documents, there is not sufficient details can be found.¶
If the transport ACTN interface wants to support the complete FCAPS capability, there could be two approaches. The first approach is the ACTN interface build up a new alarm/performance monitoring mechanism, based on its abstract control modelling. Just like what have been done in [ITU-T_G.874] and [ITU-T_G.875].¶
The second approach is reusing the traditional alarm/performance monitoring mechanism, so that the ACTN modelling needs to be mapped to the traditional modelling.¶
Currently, there is not sufficient theoretical support for the first approach, and there is not such a attempt is tried in IETF. For the second approach, one of the advantage is it can inherit the functions integrated before. So that there would not be two much efforts need to pay for the new integration.¶
In this document, we would like to follow the second approach. Table 2 provides a mapping between the ACTN objects and TMF objects.¶
| ACTN Object | TMF Object |
|---|---|
| Network | NA |
| Node | Management Element |
| Link | Topology Link |
| TP | PTP |
| TTP | CTP/FTP |
| Tunnel | SNC/XC |
| NE | Management Element |
| component | equipment holder/equipment |
| Client signal | NA |
| Ethernet Client signal | NA |
| NA | Protection Group |
| NA | Equipment Protection Group |
The ONF TAPI also defines a new set of terms, which are different from the definitions of the [ITU-T_G.805]. But it provides the mapping of TAPI objects to ITU-T objects in Figure 3-2 of [ONF_TR-547]. In the appendix of this document, we also compare the ACTN object modelling and TAPI object modelling, which can be used as a reference for a possible integration of these two interfaces in a same MDSC.¶
The current ACTN topology models for transport technology follows the relationship as bellow:¶
+----------------------+
| network topology |
+----------------------+
^
|augmenting
|
+----------------------+
| TE topology |
+----------------------+
^ ^ ^
| augmenting |
augmenting | | |
+--------------+ | |
| ETH topology | | |
+--------------+ | |
| |augmenting
+--------------+ |
| OTN topology | |
+--------------+ |
|
+--------------+
| WDM topology |
+--------------+
TE topology model was aimed to define common attributes for all the technologies. OTN topology and WDM topology, etc., they are all augmenting TE topology model to provide layer-specific extensions.¶
Although most of the objects in ACTN and TMF can be mapped to each other, the parameters of the objects cannot be completely matched. In other words, the current ACTN object needs to be extended with some properties to support the full functionality of a traditional object.¶
But in the traditional transport standards there is not such a saying of TE-related modelling. If we want to extend the current IETF data models to have full modelling of traditional approach, which is called RDNM extension by us, we suggest to define the common attributes for all the technologies in a RDNM extension model.¶
For layer-specific RDNM extensions could reference existing way and define in a separated layer-specific RDNM extension document. So in the RDNM approach, the ACTN topology architecture will be extended to be:¶
+----------------------+
| network topology |
+----------------------+
^
|
|
+----------------------+ +----------------------+
| TE topology |<----------| RDNM Extension |
+----------------------+ +----------------------+
^ ^ ^ ^ ^ ^
| | | | | |
| | | | | |
+--------------+ | | +----------------+ | |
| ETH topology | | | | ETH RDNM EXT | | |
+--------------+ | | +----------------+ | |
| | | |
+--------------+ | +--------------+ |
| OTN topology | | | OTN RDNM EXT | |
+--------------+ | +--------------+ |
| |
+--------------+ +--------------+
| WDM topology | | WDM RDNM EXT |
+--------------+ +--------------+
It is also same for the TE tunnel architecture. The whole architecture after RDNM tunnel extensions will be:¶
+----------------------+ +----------------------+
| TE Tunnel |<----------| RDNM Extension |
+----------------------+ +----------------------+
^ ^ ^ ^ ^ ^
| | | | | |
| | | | | |
+------------+ | | +----------------+ | |
| ETH Tunnel | | | | ETH RDNM EXT | | |
+------------+ | | +----------------+ | |
| | | |
+--------------+ | +--------------+ |
| OTN Tunnel | | | OTN RDNM EXT | |
+--------------+ | +--------------+ |
| |
+--------------+ +--------------+
| WDM Tunnel | | WDM RDNM EXT |
+--------------+ +--------------+
For the some objects, although it is defined in IETF, but the way of abstraction is not so implementation friendly, especially for TTP.¶
(To be added)¶
According to the description of [RFC8795], TTP is an element of a TE topology representing one or several potential transport service termination points, (i.e., service client adaptation points, such as a WDM/OCh transponder).¶
In the ITU-T standard, such an adaptation point can be the termination point of an end-to-end connection, or the source or sink point of the intermediate cross-connection. A physical port can generate a lot of logical objects. For example, a 100G line port can function as 80 lower-order ODU0 adaptation points, 40 ODU1 adaptation points, or even the adaptation point of an OCh tunnel. Considering the data volume in large-scale network, it is not wise to expose all these points. Because that most of them are potentially existing, they are probably not used at the end.¶
In the document of TE topology, it is not indicated whether the TTPs should be provided at day 0 or not. And it is also hard to find the correlation with the physical port.¶
In this document, we suggest not to provide the potential TTPs but the existing TTPs who have been used by connections at any time. If the client want to retrieve these potential TTPs, a single RPC can help to do so. This RPC should return the existing and potential TTPs at the same time.¶
The key of TTP is tunnel-tp-id which is a binary type. For the potential TTPs, it is no need to allocate a tunnel-tp-id for them. But the server can provide a name for these TTPs, this name should follow the pattern defined by TMF. When the client want to reference a potential TTP, it can reference the name of this TTP, and then the server will allocated a tunnel-tp-id for it after the connection created. And this TTP is no more than a potential TTP but an existing TTP, it should appear in the TTP list of topology.¶
rpcs:
+---x query-ttp-by-tps
+--ro input
| +--ro tp-list* [tp-id]
| +--ro tp-id leafref
+--ro output
+--ro result? enumeration
+--ro result-list* [tp-id]
+--ro tp-id leafref
+--ro ttp-list*
+--ro tunnel-tp-id? leafref
+--ro ttp-name? string
+--ro using-status? enumeration
¶
The current TE tunnel model only supports point-to-point scenario. Therefore, only one source and sink structure is defined on the tunnel node. In the transport technology, there are point-to-multipoint scenarios and multipoint-to-multipoint connection scenarios. For example, multicast service.¶
We suggest to extend the current TE tunnel model to support the multi-point scenario. Considering the TTPs was not generate before the tunnel created, the client can reference by the TTP by name.¶
In some maintenance scenarios, people may need to freeze the restoration capability of a TE tunnel. For example, after obtaining the customers' consent, the carrier can choose not to restore services during the TE tunnel cutover. This prevents unstable services flapping caused by repeated fiber cuts during the cutover. The unstable services flapping would also affects existing services.¶
Section 3.2.8.11 in [ITU-T_G.808] mentions the freezing operation of protection and rerouting switching. Therefore, compared with traditional path management, the current TE tunnel model also needs to add freezing capability to the protection and restoration structure.¶
For some cutover scenario, services may be rerouted to a new trail before the cutover operation. During the cutover, the fiber may be frequently plug in and plug out due to commissioning. To make sure that the new route will not go back to the original route and if the tunnel is restoration reversion, there would be a requirement the freeze the restoration reversion function. This is also a functionality defined by ITU-T and it's missing in the current TE tunnel.¶
Maintenance job usually is taken place in a fixed time window, for example at night when people are not using the network frequently as daytime. So that there will not be impact as large as operating at daytime if the maintenance job is failed. Operator can choose to revert the services to the original path at night, so that the restoration reversion would not have big impact on the network.¶
In some operator, they configure different restoration priority to different tunnels or services. When multiple services need to be restored at a same time, high-priority services preferentially occupy resources, and low-priority services can be rerouted only after the rerouting of high-priority services is complete.¶
augment /te:te/te:tunnels/te:tunnel/te:restoration: +--rw restoration-lock? boolean +--rw restoration-reversion-lock? boolean +--rw scheduled-reversion-time? yang:date-and-time +--rw restoration-priority? enumeration¶
The current TE tunnel data model can support to specify explicit node/LTP included/excluded. However, for finer grain object, such as TTP, it is not supported to specify.¶
For example, in the scenario where lower-order and higher-order ODUk tunnel are both existing, sometimes multiple lower-order ODUk tunnels need to multiplex a higher-order ODUk tunnel. The client can specify the higher-order ODUk tunnel's TTP to be included in the lower-order ODUk tunnel's creation request. If the lower-order ODUk doesn't need to multiplex a higher-order ODUk tunnel, the client can specify the higher-order ODUk tunnel's TTP to be excluded in the lower-order ODUk tunnel's creation request.¶
There can be two ways to specify this TTP. This higher-order ODUk TTP can be existing in the topology if it has been occupied by a higher-order ODUk tunnel. Then in the TTP hop, the client can specify the ttp-id of this TTP. This TTP can also be nonexisting in the topology or idle for tunnel creation. And then then client can specify the name of TTP in the creation request.¶
augment /te:te/te:tunnels/te:tunnel/te:primary-paths/te:primary-path
/te:explicit-route-objects-always
/te:route-object-include-exclude/te:type:
+--:(ttp-hop)
+--rw ttp-hop
+--rw node-id? nw:node-id
+--rw (id-or-name)?
+--:(id)
| +--rw ttp-id? binary
+--:(name)
+--rw ttp-name? string
augment /te:te/te:tunnels/te:tunnel/te:secondary-paths
/te:secondary-path/te:explicit-route-objects-always
/te:route-object-include-exclude/te:type:
+--:(ttp-hop)
+--rw ttp-hop
+--rw node-id? nw:node-id
+--rw (id-or-name)?
+--:(id)
| +--rw ttp-id? binary
+--:(name)
+--rw ttp-name? string
augment /te:te/te:tunnels/te:tunnel/te:primary-paths/te:primary-path
/te:primary-reverse-path/te:explicit-route-objects-always
/te:route-object-include-exclude/te:type:
+--:(ttp-hop)
+--rw ttp-hop
+--rw node-id? nw:node-id
+--rw (id-or-name)?
+--:(id)
| +--rw ttp-id? binary
+--:(name)
+--rw ttp-name? string
augment /te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths
/te:secondary-reverse-path/te:explicit-route-objects-always
/te:route-object-include-exclude/te:type:
+--:(ttp-hop)
+--rw ttp-hop
+--rw node-id? nw:node-id
+--rw (id-or-name)?
+--:(id)
| +--rw ttp-id? binary
+--:(name)
+--rw ttp-name? string
¶
Figure 4 below shows the tree diagram of the YANG data model defined in module "ietf-rdnm-topology".¶
module: ietf-rdnm-topology
augment /nw:networks/nw:network/nw:node/tet:te:
+--rw (layer-specific-extension)?
+--:(generic)
augment /nw:networks/nw:network/nw:node/nt:termination-point
/tet:te:
+--rw (layer-specific-extension)?
+--:(generic)
augment /nw:networks/nw:network/nw:node/tet:te
/tet:tunnel-termination-point:
+--rw (layer-specific-extension)?
+--:(generic)
augment /nw:networks/nw:network/nt:link/tet:te:
+--rw (layer-specific-extension)?
+--:(generic)
rpcs:
+---x query-ttp-by-tps
+---w input
| +---w tp-list* [tp-id]
| +---w tp-id leafref
+--ro output
+--ro result? enumeration
+--ro result-list* [tp-id]
+--ro tp-id leafref
+--ro ttp-list* []
+--ro tunnel-tp-id? leafref
+--ro ttp-name? string
+--ro using-status? enumeration
Figure 5 below shows the tree diagram of the YANG data model defined in module "ietf-rdnm-tunnel".¶
module: ietf-rdnm-tunnel
augment /te:te/te:tunnels/te:tunnel:
+--rw alias? string
+--ro create-time? yang:date-and-time
+--ro active-time? yang:date-and-time
+--rw source-endpoints
| +--rw source-endpoint* []
| +--rw node-id?
| | -> /nw:networks/network/node/node-id
| +--rw (endpoint-tp)?
| | +--:(ltp)
| | | +--rw tp-id? leafref
| | +--:(ttp)
| | +--rw (id-or-name)?
| | +--:(id)
| | | +--rw ttp-id? leafref
| | +--:(name)
| | +--rw ttp-name? leafref
| +--rw protection-role? enumeration
+--rw destination-endpoints
+--rw destination-endpoint* []
+--rw node-id?
| -> /nw:networks/network/node/node-id
+--rw (endpoint-tp)?
| +--:(ltp)
| | +--rw tp-id? leafref
| +--:(ttp)
| +--rw (id-or-name)?
| +--:(id)
| | +--rw ttp-id? leafref
| +--:(name)
| +--rw ttp-name? leafref
+--rw protection-role? enumeration
augment /te:te/te:tunnels/te:tunnel/te:restoration:
+--rw restoration-lock? boolean
+--rw restoration-reversion-lock? boolean
+--rw scheduled-reversion-time? yang:date-and-time
+--rw restoration-priority? enumeration
+--rw restoration-layer? enumeration
<CODE BEGINS> file "[email protected]" module ietf-rdnm-topology { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-rdnm-topology"; prefix rdnmt; import ietf-network { prefix "nw"; } import ietf-network-topology { prefix "nt"; } import ietf-te-topology { prefix "tet"; } organization "IETF CCAMP Working Group"; contact "WG Web: <http://tools.ietf.org/wg/ccamp/> WG List: <mailto:[email protected]> Editor: Chaode Yu <mailto:[email protected]> Xing Zhao <mailto:[email protected]> Yanxia Tan <mailto:[email protected]> Nigel Davis <mailto:[email protected]> Daniel King <mailto:[email protected]>"; description "This module provide some extensions to TE topology model, based on transport Rich-Detail Network Management requirement"; revision 2025-02-22 { description "Revision 1.0"; reference "draft-yu-ccamp-rdnm-yang-00"; } augment "/nw:networks/nw:network/nw:node/tet:te" { description "Generic Rich-Detail Network Management extensions for te node"; uses node-rdnm-ext-grouping; } augment "/nw:networks/nw:network/nw:node/nt:termination-point/" + "tet:te" { description "Generic Rich-Detail Network Management extensions for termination point"; uses tp-rdnm-ext-grouping; } augment "/nw:networks/nw:network/nw:node/tet:te" + "/tet:tunnel-termination-point" { description "Generic Rich-Detail Network Management extensions for te node"; uses ttp-rdnm-ext-grouping; } augment "/nw:networks/nw:network/nt:link/tet:te" { description "Generic Rich-Detail Network Management extensions for link"; uses link-rdnm-ext-grouping; } grouping node-rdnm-ext-grouping { description "Generic extension of node."; choice layer-specific-extension { description "The layer rate information."; case generic { } } } grouping tp-rdnm-ext-grouping { description "Generic extension of TP."; choice layer-specific-extension { description "The layer rate information."; case generic { } } } grouping ttp-rdnm-ext-grouping { description "Generic extension of TTP."; choice layer-specific-extension { description "The layer rate information."; case generic { } } } grouping link-rdnm-ext-grouping { description "Generic extension of link."; choice layer-specific-extension { description "The layer rate information."; case generic { } } } rpc query-ttp-by-tps { description "Query all the TTPs on the LTPs"; input { list tp-list { description "the LTPs to retrieve."; key tp-id; leaf tp-id { type leafref { path "/nw:networks/nw:network/nw:node" + "/nt:termination-point/nt:tp-id"; } description "the identifier of TP to querey"; } } } output { leaf result { type enumeration { enum failed; enum partially-successful; enum successful; } description "the result of retrieval"; } list result-list { description "The result list."; key tp-id; leaf tp-id { type leafref { path "/nw:networks/nw:network/nw:node" + "/nt:termination-point/nt:tp-id"; } description "the identifier of TP queried and returns TTPs"; } list ttp-list { description "the TTPs list for this LTP."; leaf tunnel-tp-id { type leafref { path "/nw:networks/nw:network/nw:node/tet:te" + "/tet:tunnel-termination-point/tet:tunnel-tp-id"; } description "Identifier of TTP which is existing in the topology. It is not required to return if it is not existing in the topology."; } leaf ttp-name { type string; description "Name of TTP. If the ttp is idle, the default name should be provided by the server and follow the naming pattern of TMF814."; } leaf using-status { type enumeration { enum idle; enum bidirectional-used; } } } } } } } <CODE ENDS>
<CODE BEGINS> file "[email protected]" module ietf-rdnm-tunnel { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-rdnm-tunnel"; prefix rdnm-tnl; import ietf-te { prefix "te"; } import ietf-yang-types { prefix "yang"; } import ietf-rdnm-types { prefix "rdnm-types"; } import ietf-network { prefix "nw"; } import ietf-network-topology { prefix "nt"; } import ietf-te-topology { prefix "tet"; } organization "IETF CCAMP Working Group"; contact "WG Web: <http://tools.ietf.org/wg/ccamp/> WG List: <mailto:[email protected]> Editor: Chaode Yu <mailto:[email protected]> Xing Zhao <mailto:[email protected]> Yanxia Tan <mailto:[email protected]> Nigel Davis <mailto:[email protected]> Daniel King <mailto:[email protected]>"; description "This module provide some extensions to TE topology model, based on transport Rich-Detail Network Management requirement"; revision 2025-02-22 { description "Revision 1.0"; reference "draft-yu-ccamp-rdnm-yang-00"; } augment "/te:te/te:tunnels/te:tunnel" { description "Extensions for TE tunnel structure, includes alias, time management and another option of specifying source and destination."; leaf alias { type string; description "alias of TE tunnel"; } uses time-state-grouping; container source-endpoints { description "Source endpoints."; list source-endpoint { uses endpoint-grouping; description "List of source endpoints."; } } container destination-endpoints { description "Destination endpoints."; list destination-endpoint { uses endpoint-grouping; description "List of destination endpoints."; } } } augment "/te:te/te:tunnels/te:tunnel/te:restoration" { description "Extensions of TE tunnel restoration."; leaf restoration-lock { type boolean; description "a lock to control whether the restoration can take effect or not, it is useful in the maintenance scenrios, such as in cutover"; } leaf restoration-reversion-lock { type boolean; description "a lock to control whether the reversion of restoration can take effect or not."; } leaf scheduled-reversion-time { type yang:date-and-time; description "a time when the reversion of restoration can take effect."; } leaf restoration-priority { type enumeration { enum high; enum medium; enum low; } description "when there are multiple services need to be restored, the higher estoration priority services can occupied the idle resource in priority, it is used to control the restoration sequence."; } leaf restoration-layer { type enumeration { enum odu; enum wdm; } description "the layer of topolgy prefered to be operated when restoration is needed."; } } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths" + "/te:primary-path/te:explicit-route-objects" + "/te:route-object-include-exclude/te:type" { description "a TTP hop"; case ttp-hop { uses rdnm-types:explicit-ttp-hop; } } augment "/te:te/te:tunnels/te:tunnel/te:secondary-paths" + "/te:secondary-path/te:explicit-route-objects" + "/te:route-object-include-exclude/te:type" { description "a TTP hop"; case ttp-hop { uses rdnm-types:explicit-ttp-hop; } } augment "/te:te/te:tunnels/te:tunnel/te:primary-paths" + "/te:primary-path/te:primary-reverse-path" + "/te:explicit-route-objects" + "/te:route-object-include-exclude/te:type" { description "a TTP hop"; case ttp-hop { uses rdnm-types:explicit-ttp-hop; } } augment "/te:te/te:tunnels/te:tunnel/te:secondary-reverse-paths" + "/te:secondary-reverse-path" + "/te:explicit-route-objects" + "/te:route-object-include-exclude/te:type" { description "a TTP hop"; case ttp-hop { uses rdnm-types:explicit-ttp-hop; } } grouping time-state-grouping { description "time management of TE tunnel."; leaf create-time { type yang:date-and-time; config false; description "the time when the tunnel was created"; } leaf active-time { type yang:date-and-time; config false; description "the lastest time when the tunnel was activated"; } } grouping endpoint-grouping { description "Source/destination endpoint information of TE tunnel."; leaf node-id { type leafref { path "/nw:networks/nw:network/nw:node/nw:node-id"; } description "Identifier of node for this endpoint."; } choice endpoint-tp { description "The client can choose to specify LTP or TTP to create TE tunnel."; case ltp { leaf tp-id { type leafref { path "/nw:networks/nw:network/nw:node/nt:termination-point" + "/nt:tp-id"; } description "identifier of LTP for this endpoint."; } } case ttp { choice id-or-name { description "The client can choose to specify the identifier or the name of TTP to create TE tunnel."; case id { leaf ttp-id { type leafref { path "/nw:networks/nw:network/nw:node/tet:te" + "/tet:tunnel-termination-point/tet:tunnel-tp-id"; } description "the identifier of TTP for this endpoint."; } } case name { leaf ttp-name { type leafref { path "/nw:networks/nw:network/nw:node/tet:te" + "/tet:tunnel-termination-point/tet:name"; } description "the name of TTP for this endpoint."; } } } } } leaf protection-role { type enumeration { enum work; enum protect; } description "role of this endpoint in multipoints scenario"; } } } <CODE ENDS>
<CODE BEGINS> file "[email protected]" module ietf-rdnm-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-rdnm-types"; prefix rdnm-types; organization "IETF CCAMP Working Group"; contact "WG Web: <http://tools.ietf.org/wg/ccamp/> WG List: <mailto:[email protected]> Editor: Chaode Yu <mailto:[email protected]> Xing Zhao <mailto:[email protected]> Yanxia Tan <mailto:[email protected]> Nigel Davis <mailto:[email protected]> Daniel King <mailto:[email protected]>"; description "This module defines Rich-Detail Network Management (RDNM) YANG types."; revision 2025-02-22 { description "Revision 1.0"; reference "draft-yu-ccamp-rdnm-yang-00"; } grouping explicit-ttp-hop { container ttp-hop { description "TTP Hop"; leaf node-id { type nw:node-id; description "identifier of node for this TTP hop."; } choice id-or-name { description "The server can choose to display the identifier or the name of TTP."; case id { leaf ttp-id { type binary; } description "the identifier of TTP for this TTP hop."; } case name { leaf ttp-name { type string; } description "the name of TTP for this TTP hop."; } } } } } <CODE ENDS>
<Add any manageability considerations>¶
<Add any security considerations>¶
<Add any IANA considerations>¶
| ACTN Object | TMF Object | TAPI Object |
|---|---|---|
| Network | NA | topology |
| Node | Management Element | node |
| Link | Topology Link | link |
| TP | PTP | SIP/NEP |
| TTP | CTP/FTP | CEP |
| Tunnel | SNC/XC | connection |
| NE | Management Element | device |
| component | equipment holder/equipment | equipment/holder |
| Client signal | NA | connectivity service |
| Ethernet Client signal | NA | connectivity service |
| NA | Protection Group | NA |
| NA | Equipment Protection Group | NA |
The authors would like to thank Adrian Farrrel and Scott Mansfield for their inputs and suggestions.¶
This document was prepared using kramdown.¶