Huawei Technologies

yuchaode@huawei.com

TIM

fabio.peruzzini@telecomitalia.it

China Unicom

zhengyanlei@chinaunicom.cn

Huawei Technologies

italo.busi@huawei.com

Futurewei Technologies

aihuaguo.ietf@gmail.com

Nokia

victor.lopez@nokia.com

CAICT

zhaoxing@caict.ac.cn

CCAMP Working Group This document defines a YANG data model for performance Monitoring in optical networks which provides the functionalities of performance monitoring task management, TCA (Threshold Crossing Alert) configuration and current or historic performance data retrieval. This data model should be used in the northbound of PNC.

Introduction Performance monitoring is a basic function of optical networks management. With it, operators can proactively detect the running state of devices, identify major risks in advanced and avoid users' complaints. As before, TMF has defined interfaces for performance management through traditional protocols, such as CORBA and MTOSI. With the development of SDN technologies and the using of RESTCONF interfaces, it becomes a widespread requirement to use RESTCONF protocol to support performance monitoring. Using RESTCONF does not mean changing existing performance monitoring requirements or scenarios. On the contrary, since O&M is very important, many operators' O&M departments tend to be conservative. Mostly, they are fear of introducing issues into their network due to the protocol changes and O&M habits changes. Therefore, our document prefers to use the new protocol to support legacy functionality. Traditional performance management involves control of performance monitoring, setting collectors on monitored objects, and obtaining performance data in different periods. The data can be current data on devices or processed by PNC, and historical performance data. TCA can be also configured by performance monitoring tasks. ITU-T also has a lot of related recommendations for performance monitoring. Such as session 10 of has provided very detail description of performance management application and functions. does not provide a UML model or YANG module to guide the implementation of PNC while this document does. Section 10.2 of provides a list of PM indicators which are on the NE level, which could help to reduce duplicated definition of performance indicators. Currently, there are some existing documents related to performance monitoring in IETF, but there is no overlap with our current work. For example: provides a YANG data model that describes performance monitoring and scaling intent mechanisms for TE-Tunnels and Virtual Networks(VNs). VN is determinate to be used in CMI (CNC-MDSC Interface) level and TE tunnel is more service or connection related. Our data model is proposed to be used in MPI (MDSC-PNC Interface) level and this performance monitoring is performed on network resources, such as network element, board, fiber, port or TTP (Tunnel Termination Point), which are not included in . defines a YANG data model for performance monitoring of both network topology layer and overlay VPN service topology layer. VPN service is more IP-specific and not adopted in Optical domain. And the data model in this document is augmenting network model. If the client wants to retrieve performance data of a link by RESTCONF, the URL would be probably same with the URL of topology retrieval. This may need some special mechanisms to make the client and server differentiate the using scenarios. This is not quite compliance with current O&M habits of Optical technology. provides a performance monitoring YANG data model on client signal level. It is also not operated on resource level which is not compliance with the existing O&M habits. This performance monitoring solution is more user-oriented and can be used for more automatic O&M scenarios in the future. However, there is not a complete closed-loop O&M solution at the service layer and it has not been accepted by all operators' O&M departments, resource-based performance monitoring is still required. The YANG data model defined in this document conforms to the Network Management Datastore Architecture (NMDA) defined in .

Terminology and Notations Refer to and for the key terms used in this document. The following terms are defined in and are not redefined here: * client * server * augment * data model * data node The following terms are defined in and are not redefined here: * configuration data * state data The following terms are defined in and are not redefined here: * CMI * MPI * MDSC * CNC * PNC //To Be Added: some explanation of performance indicator

Tree Diagram A simplified graphical representation of the data model is used in Section 3 of this document. The meaning of the symbols in these diagrams are defined in .

Prefix in Data Node Names 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 shown in the following table. Prefix Yang Module Reference optrpm ietf-optical-resource-pm RFC XXXX optrpm-types ietf-optical-resource-pm-types RFC XXXX yang ietf-yang-types RFC Editor Note: Please replace XXXX with the RFC number assigned to this document.

YANG Data Model for Optical Performance Monitoring According to the business requirements stated in , resource performance management requirements include: * The Interface shall support the control of performance monitoring in the network. This includes PM control, e.g., the enabling and disabling of PM collection and Threshold Crossing Alerts (TCA) control, e.g., the enabling and disabling of TCA generation. * The Interface shall support the retrieval of current and historical performance measurements for network resources. * The Interface shall support the distribution of TCAs to subscribed OSs. For these requirements of PM, there are three group of interfaces are defined in TMF, including PerformanceManagementControl, PerformanceManagementRetrieval and ThresholdCrossingAlertControl.

Generic Resource The definition of most performance monitoring interfaces in TMF is quite generic. And it is also similar that the functionalities of both alarm and performance monitoring can be defined with a generic structure, regardless of what kind of object is operated on. Therefore, our data model prefer to follow this approach. And when defining our data model, we get refer to , in which a generic alarm data model is provided. In , a union type of resource attributes is defined as the source of alarm. So we also reference this structure in our data model. Additionally, we extend a resource-type attribute to indicate what exact kind of resource is. Firstly, this attribute can help to improve interaction efficiency between PNC and MDSC. The MDSC may quickly identify the resource type from this attribute, without parsing the resource identifier or searching the resource id in the whole resource. On the other hand, it will be unified with the existing IETF topology and inventory objects and form a complete interface system.

PerformanceManagementControl There are three interfaces defined in TMF for this group, including: * clearPerformanceMonitoringData: This interface shall allow MDSC to clear or reset the performance register on TPs or NEs. This clearing operation means to reset the data value to the current value. The monitoring job is still running on. * disablePerformanceMonitoringData: This interface shall allow MDSC disable PM data collection on a list of TPs or NEs. * enablePerformanceMonitoringData: This interface shall allow MDSC enable PM data collection on a list of TPs or NEs.

clearPerformanceMonitoringData Because the performance data can be changed frequently, so the current and history performance data are not suitable to define in a data model. Clearing performance monitoring data is more suitable to define an RPC to perform this operation. Especially according to the MTOSI interface, this clearing operation can be operated on multiple objects in one request. Currently there is not such an approach to support this kind of flexible method if using data API. Therefore we define a RPC operation to support this function.

If there are any resources failed to clear performance monitoring data, their identifier should be returned by the failed-resources leaf list. An empty list indicates that this operation was performed successfully.

enablePerformanceMonitoringData & disablePerformanceMonitoringData For interfaces of enable/disable performance monitoring data, we introduce a monitor task to do this control. In the monitoring task, MDSC should be able to configure what period and what kind of performance data it want to collect. The disabling, enabling operation can be satisfy by changing the admin status which includes disabled, enabled. The change's result will affect the task status accordingly.

PerformanceManagementRetrieval There are six interfaces are defined in TMF for this group, including: * getAllCurrentPerformanceMonitoringData: This interface should allow MDSC to retrieve performance data on a series of termination point. * getHistoryPerformanceMonitoringData: This interface should allow MDSC to retrieve some historic performance data on a series of termination point in a time period through FTP. * getAllPerformanceMonitoringPoints: This interface should allow MDSC to retrieve all the performance monitoring points in a specified termination point or NE. * getHoldingTime: This interface should allow MDSC to retrieve how many hours PM data records are held in PNC. * getMePerformanceMonitoringCapabilities: This interface should allow MDSC to retrieve what parameters are supported by a specified NE or termination point. * getProfileAssociatedTerminationPoints: The Interface shall allow MDSC to retrieve the names of all the TPs known to the PNC that are associated with a specified Threshold Crossing Alert (TCA) Parameter Profile.

getAllCurrentPerformanceMonitoringData & getHistoryPerformanceMonitoringData For the retrieval of current/historic performance data, we consider these data are not suitable to define in a data model. Because performance data can be changed frequently and if we follow that approach, according to the requirement of on-change notification in YANG-push , once the performance data changes, the PNC should trigger a notification to the MDSC, there would be great amount of notifications reported in the big network. These great amount of notifications will bring great pressure to both PNC and MDSC. People don't use notification to get performance data in real network. These two retrieval interfaces are usually invoked on-demand. It is also hard to support retrieving performance data of multiple resources by data model in one request. And for historic performance data retrieval, there could be a requirement to specify the start time and end time. It is not quite flexible to support this requirement by data model neither. So we suggest to define two RPCs to accomplish these two interfaces' function.

getAllPerformanceMonitoringPoints & getHoldingTime & getMePerformanceMonitoringCapabilities These three interfaces allow MDSC to retrieve performance monitoring points, holding time, and performance monitoring capabilities (indicators) as per a specific resource. We consider that these information are all performance monitoring capabilities in a broad sense. These information should be defined under the resource node.

The sub-resources is list of the performance monitoring points' identifier. And the pm-parameter-list is the indicators that can be supported by this specific resource.

getProfileAssociatedTerminationPoints For the TCA related definition, it can be found in the next session. A TCA profile can be associated with a lot of resources, so we don't defined a resource list under the profile instance to avoid reporting some unnecessary notifications while the resource instances in this list have been changed. We define a RPC operation to support this flexible retrieval request.

ThresholdCrossingAlertControl There are nine interfaces are defined in TMF for this group, including: * createTcaParameterProfile: This interface should allow MDSC to create a new TCA parameter profile. This profile can be applied to the resources. * deleteTcaParameterProfile: This interface should allow MDSC to delete an existing TCA parameter profile which should not have been used by any resources. * enableThresholdCrossingAlert: This interface should allow MDSC to turn on TCA reporting on a list of TPs and NEs if the reporting was turned off before. * disableThresholdCrossingAlert: This interface should allow MDSC to turn off TCA reporting on a list of TPs and NEs. * getAllTcaParameterProfiles: This interfaces should allow MDSC to retrieve all TCA parameter profile that are being managed by a specified NE. * getTcaParameterProfile: This interface should allow MDSC to retrieve all the parameters of a specified TCA parameter profile. * getTcaTpParameter: This interface should allow MDSC to retrieve the PM threshold values on a TP. * setTcaParameterProfile: This interface should allow MDSC to configure all threshold values of a TCA parameter profile. * setTcaTpParameter: This interface should allow MDSC to modify the values of TCA Parameters on a TP To be summarized, there are four main requirements for Threshold Crossing Alert Control: * Creation/retrieval/deletion/updating of TCA profile; * Enabling/disabling TCA reporting on the resource; * Configuring TCA on the resource by associating an existing profile; * Configuring TCA on the resource by detailed parameters. And for the TCA parameters, no matter it is configured directly on the resource or by a preset profile, there should not be any differences. The TCA parameter (indicator) should include: * indicator-name: Name of indicator. This indicator should also include some data processing information, such if it is a maximum, or minimum, or average data .etc. * threshold-type: This threshold type is used to indicate when the alert will be triggered. By exceeding the upper bound value, or by below the lower bound value. * period: This period is used to indicate the frequency of the data collection. * severity: This severity is used to indicate what level of alert would be triggered if cross the threshold. * indicator-value: The value of threshold. * indicator-value-unit: The unit of threshold value. The tree structure for TCA profile:

The function of enabling/disabling TCA on the resource can be controlled by an admin-status attributes in "tca" node:

If MDSC wants to configure TCA by an existing profile, it can use this applied-profiles structure:

MDSC can also configure TCA value directly by the "tca-cfg" structure:

Performance Indicator Introduction In the session10.2 of , a performance management information table lists all the PM current data and history data collected on the EMF(Equipment Management Function). Since it is quite mature, this document would not like to do a duplicated research and would like to reference this recommendation. It is suggested to use the existing PM indicator listed in this table only if it is missing. It is impossible to list all the PM indicator exhaustively, even if ITU-T has done a lot of work. Some new performance indicators would be raised once there are some new requirements and technologies. So in this document we would like to provide String type rather than an explicit type for performance indicator, to have a better compatibility for future extension. Then if there are some new indicators, there is no need to revise this document or create a branch of documents to standardize the PM indicators. Although this approach seems too flexible, the integration will not be affected if the MDSC and PNC make a good agreement in advanced.

Optical Performance Monitoring Tree Diagram

YANG Model for Optical Performance Monitoring

WG List: Editor: Chaode Yu Editor: Fabio Peruzzini Editor: Yanlei Zheng Editor: Victor Lopez Editor: Italo Busi Editor: Aihua Guo "; description "This module defines a model for optical performance monitoring. The model fully conforms to the Network Management Datastore Architecture (NMDA). Copyright (c) 2022 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 2023-07-04 { description "Initial revision."; } container performance-monitoring { description "the root node."; uses monitoring-tasks-grouping; uses tca-management-grouping; uses resource-info-grouping; } grouping resource-info-grouping { description "grouping of resources' PM capabilities related information"; container resources { description "resources' PM capabilities related information"; list resource-list { description "list of resource instances"; key resource; leaf resource { type union { type instance-identifier { require-instance false; } type yang:object-identifier; type string; type yang:uuid; } } leaf resource-type { description "the type of resource, such as NE, board or port"; config false; type identityref { base optrpm-types:resource-type; } } leaf holding-time { description "Contains the time period in hours within which 24h PM data records and 15min PM data records may be retrieved. If the domain controller does not store PM data it is the time supported in the NE"; type uint8; units "hour"; } list pm-parameter-list { must "../optrpm:resource-type=optrpm-types:network-element"; key "layer-rate"; leaf layer-rate { description "Layer rate of ME"; type identityref { base optrpm-types:layer-rate-type; } } leaf-list indicator-name { type string; } } leaf-list sub-resources { description "the identifier of the performace monitoring point of this resource. If the resource is a NE, the sub-resource should be termination point. If the resource is a termination point contained in this NE, the sub-resource should be the logic channel on this TP"; type leafref { path "../optrpm:resource"; } } } } } grouping monitoring-tasks-grouping { description "grouping of performance monitoring task"; container monitor-tasks { description "Information of PM tasks"; list monitor-task { description "monitoring task list"; key task-id; uses task-instance-grouping; } } } grouping task-instance-grouping { description "grouping of performance monitoring task. In this monitoring task, the client can specify a resource to run a monitor task and what kind of performance data need to be monitored."; leaf task-id { description "identifier of the performance task"; type yang:uuid; } leaf resource { description "the identifier of network resource on which the performance monitoring task is running"; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } leaf resource-type { description "the type of resource, such as NE, board or port"; config false; type identityref { base optrpm-types:resource-type; } } leaf task-name { description "the name of monitoring task"; type string; } leaf admin-status { description "it is used to control enbling/disabling PM task"; type enumeration { enum enabled { description "it is used to enable the pm task, if the task is enabled, the task-staus should be running"; } enum disabled { description "it is used to disenable the pm task, if the task is disabled, the task-staus should be suspended"; } } } leaf task-status { config false; description "the status of monitoring task."; type enumeration { enum running; enum suspended; enum abnormal; } } uses task-configuration-grouping; } grouping task-configuration-grouping { description "grouping of pm task configuration"; container task-cfg { description "Configuration of the monitoring task"; leaf period { description "it is used to indicate the interval as per monitoring task"; type identityref { base optrpm-types:period; } } container indicators { description "performance indicators"; list indicator { description "list of PM indicators to be monitored"; key indicator-name; uses indicator-grouping; } } } } grouping indicator-grouping { description "grouping of a monitoring indicator instance"; leaf indicator-name { description "performance indicator's name"; type string; } leaf indicator-value-unit { description "unit of indicator value"; type string; } } grouping tca-management-grouping { description "grouping of configuration and management for Threshol Crossing Alert"; container tca-management { description "configuration and management for Threshol Crossing Alert"; container profiles { description "the TCA profile in the whole network"; list profile { description "List of TCA profile instances"; key "profile-id"; uses tca-profile-grouping; } } container tcas { description "TCA configuration on the network resources."; list tca { description "List of TCA configuration instances"; key "resource"; leaf resource { description "the identifier of network resource on which threshold is configured for TCA purpose"; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } leaf resource-type { description "the type of resource, such as NE, board or termination point"; config false; type identityref { base optrpm-types:resource-type; } } leaf admin-status { description "it is used to control the validity of threshold"; type enumeration { enum enabled { description "if the admin-status of TCA configuration is enabled, the threshold is effective"; } enum disabled { description "if the admin-status of TCA configuration is disabled, the threshold is not effective"; } } } uses tca-grouping; } } } } grouping tca-profile-grouping { description "grouping of TCA profile instance"; leaf profile-id { description "identifier of threshold crossing alerrt profile"; type yang:uuid; } leaf profile-name { description "Name of the threshold crossing alerrt profile"; type string; } container tca-cfg { description "detailed TCA configuration in a profile"; list tca-indicator { description "list of TCA configuration."; key "indicator-name threshold-type period severity"; uses tca-indicator-grouping; } } } grouping tca-indicator-grouping { description "grouping for detail TCA configuration"; leaf indicator-name { type string; description "name of the indicator"; } leaf indicator-value { mandatory true; type string; description "treshold value of the indicator"; } leaf indicator-value-unit { mandatory true; type string; description "unit of indicator's value"; } leaf threshold-type { description "it is used to indicate the trigger/clearing condition of alert upon the threshold"; type enumeration { enum upperbound-trigger { description "If the performace data exceeds this threshold value, a TCA will be triggered"; } enum lowerbound-trigger { description "if the performace data is lower than this threshold value, a TCA will be triggered"; } enum upperbound-clear { description "If the performance data is not longer bigger than this threshold value, the TCA triggered before will be cleared by system automatically"; } enum lowerbound-clear { description "If the performance data is not longer lower than this threshold value, the TCA triggered before will be cleared by system automatically"; } } } leaf period { description "it is used to indicate the interval as per monitoring task"; type identityref { base optrpm-types:period; } } leaf severity { description "it is used to indicate what severity level of alert would be triggered if not confirms to the threashold"; type identityref { base optrpm-types:severity; } } } grouping tca-grouping { description "grouping of TCA configuration"; container applied-profiles { description "Information of applied TCA profiles on this resource"; list profile { description "list of applied TCA profile"; key "profile-id"; leaf profile-id { description "identifier of the applied TCA profile"; type leafref { path "../../../../../optrpm:profiles/optrpm:profile" + "/optrpm:profile-id"; } } } } container tca-cfg { description "detailed configuration of TCA"; list tca-indicator { description "list of tca indicator configuration"; key "indicator-name threshold-type period severity"; uses tca-indicator-grouping; } } } rpc get-all-current-pm-data { description "this RPC is used to retrieve current performance data."; input { leaf-list resources { description "the identifier of resources from which current performace data is collected"; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } } output { container pm-data { description "result of current performance data"; list pm-data-list { description "list of curent performance data"; key resource; uses pm-data-instance-grouping; } } } } rpc get-historic-pm-data { input { description "this RPC is used to retrieve historic performance data."; leaf-list resources { description "the identifier of resources from which historic performace data is collected"; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } leaf start-time { description "the starttime of performance data needed to be retrieved"; type yang:date-and-time; } leaf end-time { description "the endtime of performance data needed to be retrieved"; type yang:date-and-time; } } output { container pm-data { description "result of historic performance data"; list pm-data-list { description "list of historic performance data"; key resource; uses pm-data-instance-grouping; } } } } rpc clear-performance-monitoring-data { input { description "This operation clears (reset) the PM registers for a list of Measurement Points. Within the request for each Measurement Point, it is possible to specify the granularity (15min, 24hr, NA) and location (nearEnd and/or farEnd and/or bidirectional) for the PM registers that are to be reset."; leaf-list resources { description "the identifier of measurement points to clear PM data"; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } } output { leaf-list failed-resources { description "the identifier of measurement points which are failed to clear PM data. An empty list indicates that the total request was successful."; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } } } rpc get-profile-associated-termination-points { input { description "This operation gets the set of TPs that are associated with a TCA parameter profile."; leaf profile-id { description "the identifier of profile which the client want to retrieve"; type leafref { path "/optrpm:performance-monitoring/optrpm:tca-management" + "/optrpm:profiles/optrpm:profile/optrpm:profile-id"; } } } output { leaf-list resource-list { description "Provides the set of Resources associated with the profile provided."; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } } } grouping pm-data-instance-grouping { description "grouping for common attributes of performance data"; leaf resource { description "the identifier of network resource which is monitored."; type leafref { path "/optrpm:performance-monitoring/optrpm:resources" + "/optrpm:resource-list/optrpm:resource"; } } leaf collect-time { description "the time of this data is collected"; type yang:date-and-time; } leaf resource-type { description "the type of resource, such as NE, board or port"; type identityref { base optrpm-types:resource-type; } } container indicator-data { description "grouping for historic performance data"; list indicator-data-list { description "list of historic performance data"; key indicator-name; uses indicator-data-instance-grouping; } } } grouping indicator-data-instance-grouping { description "grouping for a performance data"; leaf indicator-name { description "name of performance data indicator"; type string; } leaf indicator-value { description "value of performance data"; type string; } leaf indicator-value-unit { description "unit of performance data value"; type string; } } } ]]>

YANG Model for Optical Performance Monitoring Types

WG List: Editor: Chaode Yu Editor: Fabio Peruzzini Editor: Yanlei Zheng Editor: Victor Lopez Editor: Italo Busi Editor: Aihua Guo "; description "This module defines types model for optical performance monitoring which will be imported by ietf-performance-monitoring data model. The model fully conforms to the Network Management Datastore Architecture (NMDA). Copyright (c) 2022 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 2023-07-04 { description "Initial revision."; } identity resource-type { description "this is the base type of all the rerource type"; } identity network-element { base resource-type; description "NE resource type"; } identity board { base resource-type; description "board resource type"; } identity termination-point { base resource-type; description "Termination point resource"; } identity tunnel-termination-point { base resource-type; description "Tunnel termination point resource"; } identity period { description "this is the base type of all the performace monitoring priod type."; } identity period-15-minutes { base period; description "the during of monitoring task will be repeated at every 15 minutes"; } identity period-24-hours { base period; description "the during of monitoring task will be repeated at every 24 hours"; } identity severity { description "it is used to indicate what severity alarm will be caused if exceeds the threshold"; } identity critical { description "critical alarm will be caused if exceeds the threshold"; base severity; } identity mayjor { description "mayjor alarm will be caused if exceeds the threshold"; base severity; } identity minor { description "minor alarm will be caused if exceeds the threshold"; base severity; } identity warning { description "only a warning will be caused if exceeds the threshold"; base severity; } identity layer-rate-type { description "It is used to indicate the layer rate of network element when retrieving the pm parameters supported"; } } ]]>

Manageability Considerations <Add any manageability considerations>

Security Considerations The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The NETCONF access control model 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 may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. Considerations in Section 8 of are also applicable to their subtrees in the module defined in this document. 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. Considerations in Section 8 of are also applicable to their subtrees in the module defined in this document.

IANA Considerations This document registers following YANG modules in the YANG Module Names registry . name: ietf-optical-resource-pm namespace: urn:ietf:params:xml:ns:yang:ietf-optical-resource-pm prefix: optrpm reference: RFC XXXX: A YANG Data Model for Optical Performance Monitoring name: ietf-optical-resource-pm-types namespace: urn:ietf:params:xml:ns:yang:ietf-optical-resource-pm-types prefix: optrpm-types reference: RFC XXXX: A YANG Data Model for Optical Performance Monitoring

TM Forum (TMF) International Telecommunication Union International Telecommunication Union 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. This document provides a model of information needed by the Routing and Wavelength Assignment (RWA) process in Wavelength Switched Optical Networks (WSONs). The purpose of the information described in this model is to facilitate constrained optical path computation in WSONs. This model takes into account compatibility constraints between WSON signal attributes and network elements but does not include constraints due to optical impairments. Aspects of this information that may be of use to other technologies utilizing a GMPLS control plane are discussed. A Wavelength Switched Optical Network (WSON) requires certain key information fields be made available to facilitate path computation and the establishment of Label Switched Paths (LSPs). The information model described in "Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks" (RFC 7446) shows what information is required at specific points in the WSON. Part of the WSON information model contains aspects that may be of general applicability to other technologies, while other parts are specific to WSONs. This document provides efficient, protocol-agnostic encodings for the WSON-specific information fields. It is intended that protocol- specific documents will reference this memo to describe how information is carried for specific uses. Such encodings can be used to extend GMPLS signaling and routing protocols. In addition, these encodings could be used by other mechanisms to convey this same information to a Path Computation Element (PCE). 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). 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] 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. This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. 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). This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] 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. 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. 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. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] Samsung Electronics Huawei Technologies CTTC Lancaster University Cisco This document provides YANG data models that describe performance monitoring parameters and scaling intent mechanisms for TE-tunnels and Virtual Networks (VNs). There performance monitoring parameters are exposed as the key telemetry data for tunnels and VN. The models presented in this document allow customers to subscribe to and monitor the key performance data of the TE-tunnel or the VN. The models also provide customers with the ability to program autonomic scaling intent mechanisms on the level of TE-tunnel as well as VN. Huawei Huawei Orange Telefonica Comcast The data model for network topologies defined in RFC 8345 introduces vertical layering relationships between networks that can be augmented to cover network and service topologies. This document defines a YANG module for performance monitoring (PM) of both underlay networks and overlay VPN services that can be used to monitor and manage network performance on the topology of both layers. Huawei Technologies Huawei Technologies China Unicom Nokia Telefonica A transport network is a server-layer network to provide connectivity services to its client. Given the client signal is configured, the followup function for performance monitoring, such as latency and bit error rate, would be needed for network operation. This document describes the data model to support the performance monitoring functionalities. This document provides an information model for Abstraction and Control of TE Networks (ACTN). This document defines a YANG module for alarm management. It includes functions for alarm-list management, alarm shelving, and notifications to inform management systems. There are also operations to manage the operator state of an alarm and administrative alarm procedures. The module carefully maps to relevant alarm standards. This document describes a mechanism that allows subscriber applications to request a continuous and customized stream of updates from a YANG datastore. Providing such visibility into updates enables new capabilities based on the remote mirroring and monitoring of configuration and operational state.

Acknowledgments This document was prepared using kramdown.