CCAMP Working Group Daniel King Internet Draft Adrian Farrel Category: Standard Track Old Dog Consulting Expires: 11 January 2024 10 July 2023 Integrating YANG Configuration and Management into an Abstraction and Control of TE Networks (ACTN) System for Optical Networks draft-gstk-ccamp-actn-optical-transport-mgmt-00 Abstract Many network technologies are operated as Traffic Engineered (TE) networks. Optical networks are a particular TE example, with many technology-specific details. Abstraction and Control of TE Networks (ACTN) is a management architecture that abstracts TE network resources to provide a limited network view for customers to request and self-manage connectivity services. It also provides functional components to orchestrate and operate the network. However, ACTN does not include consideration of Fault, Configuration, Accounting, Performance, and Security aspects of management (known as FCAPS). Nevertheless, FCAPS forms a critical part of service assurance for network operations. This document introduces FCAPS into the ACTN architecture as applied to optical networks. It considers what elements of existing IETF YANG work can be used and what new work is needed. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. King and Farrel Expires January 2024 [Page 1] Internet-Draft Integrating FCAPS with ACTN July 2023 The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on 11 January 2024. Copyright Notice Copyright (c) 2023 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 (http://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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction...................................................2 1.1. FCAPS Transport Network Management Approaches................3 1.2. Service Assurance............................................4 1.3. Motivation and Scope.........................................4 2. Extending the ACTN Architecture to Include FCAPS...............5 3. Functionality at the MPI.......................................7 3.1. Data Models at the MPI.......................................7 3.2. Abstraction and Control at the MPI...........................7 4. Introduction to FCAPS..........................................8 4.1. Functionalities Covered by FCAPS.............................8 5. Abstract Control and Fine-Grain Management for ACTN............9 5.1. Abstract Control and Fine-Grain Management Functions for the MPI...............................................................9 5.2. Fine-Grain Management Interfaces............................10 5.3. Fine-Grain Management Data Models...........................10 5.4. Fine-Grain Management Example...............................11 6. Manageability Considerations..................................11 7. Security Considerations.......................................11 8. IANA Considerations...........................................11 9. References....................................................12 9.1. Informative References...................................12 Authors' Addresses...............................................13 1. Introduction Abstraction and Control of Traffic Engineering (TE) Networks (ACTN) [RFC8453] is an architecture that simplifies and optimises King and Farrel Expires January 2024 [Page 2] Internet-Draft Integrating FCAPS with ACTN July 2023 the management and control of network resources to deliver connectivity services. ACTN abstracts and controls TE resources to enable end-to-end service provisioning and management across multiple network domains. It provides a way to orchestrate and automate the management of network resources, including connectivity and bandwidth, to meet the requirements of specific services or applications. ACTN in an optical network leverages SDN concepts to achieve its objectives. By applying SDN principles, such as centralised control and programmability, to the transport layer, ACTN enables efficient orchestration and service provisioning in a multi-domain environment. ACTN adds a higher-level framework and management capabilities specifically tailored for TE transport networks, including the abstraction of network resources, service provisioning, and resource optimisation. The term FCAPS [M.3060] is used in network management and stands for Fault, Configuration, Accounting, Performance, and Security. It is a widely accepted framework that categorises different aspects of network management. FCAPS provides a structured approach to managing and maintaining networks, addressing various operational and maintenance areas. FCAPS is a framework that categorises different aspects of network management. While ACTN primarily deals with the abstraction and control of TE networks for service provisioning, FCAPS covers broader aspects of network management, including fault detection and resolution, configuration management, performance monitoring, accounting, and security. In practice, while ACTN can be considered as a high-level architecture , operators would also like to leverage the FCAPS framework for specific operational tasks and management activities. ACTN and FCAPS are not mutually exclusive, but the ACTN framework has not described the integration of FCAPS into its management architecture. This document explains how FCAPS can be integrated into the ACTN architecture as applied to optical networks. It considers what elements of IETF work can be used, and what new work is needed. 1.1. FCAPS Transport Network Management Approaches ITU-T G.805 [G.805] is a Recommendation published by the International Telecommunication Union Telecommunication Standardization Sector (ITU-T). It specifies the architecture and framework for the management of transport networks. G.805 provides King and Farrel Expires January 2024 [Page 3] Internet-Draft Integrating FCAPS with ACTN July 2023 guidelines and principles for managing network resources and services in a coordinated and efficient manner. The TM Forum (TMF) has developed its own set of standards and frameworks for managing telecommunications networks and services. Specifically, the TMF developed the Telecommunications Management Network (TMN) model and informed the ITU-T Recommendation [M.3060] to align with G.805. TMN is a framework that defines a comprehensive set of management functions and interfaces for network operations and service management, that is, FCAPS. More recently, the ITU-T Recommendation [M.3041] introduced a framework of smart operation, management and maintenance (SOMM). In this Recommendation, characteristics, scenarios and the functional architecture of SOMM are provided to support service operation, network management and infrastructure maintenance for both traditional physical networks and software-defined networking, and network function virtualisation (non-SDN/VFN), and SDN/NFV aware networks. This document highlights how to implement G.805 [G.805] and TMN SOMM [M.3041 for a TMN Logical Layered Architecture (LLA), in the context of ACTN and FCAP principles. It will outline existing IETF mechanisms, protocols and data models, and provide requirements should gaps exist. 1.2. Service Assurance Service Assurance refers to the activities and processes that ensure the quality, availability, and performance of services delivered by a network. It monitors and manages the end-to-end service experience, and meets Service Level Agreements (SLAs) and customer expectations. By applying the FCAPS framework, network operators and service providers can address different aspects of network management to support Service Assurance. It helps them detect and resolve faults, manage configurations, track resource usage, optimise performance, and enhance security, all of which contribute to delivering reliable and high-quality services to customers. 1.3. Motivation and Scope Operators who manage optical transport networks can leverage ACTN for resource abstraction and service provisioning. At the same time, they can utilise G.805 Recommendations and the TMN model to establish effective network management practices, which will facilitate service assurance. Combining the two management King and Farrel Expires January 2024 [Page 4] Internet-Draft Integrating FCAPS with ACTN July 2023 approaches aligns with best-practice industry standards and allows adopting emerging ACTN-based abstraction and control techniques. This document studies the FCAPS requirements in the context of ACTN's functional components. It analyses the ACTN interfaces from a management operations perspective. It identifies suitable IETF data models that meet FCAPS requirements that can be utilised in the ACTN architecture to support optical transport networks. Gaps and requirements are identified where necessary so additional models may be developed. 2. Extending the ACTN Architecture to Include FCAPS Figure 1 shows the ACTN architecture from [RFC8453] enhanced to include elements of FCAPS. The Customer Network Controller (CNC), Multi-domain Service Coordinator (MDSC), and Provisioning Network Controller (PNC) are functional components of ACTN, as described in RFC 8453. There are two ACTN interfaces between the components: the CNC-MDSC Interface (CMI) and the MDSC-PNC Interface (MPI). In ACTN, the CMI and MPI are realised using a combination of IETF data models. +---------+ | CNC | +---------+ | | Boundary ===========================|========== between | Customer & | CMI Network Operator | Policy +---------------+ -----------| MDSC | / +---------------+ +-------------+ | | | | MPI+Extensions | OSS | | | | | +-------------+ | \ +---------------------+ -------| Domain | FCAPS | Controller | | | | +-----------+ | | | NMS/EMS | | | | .......... | | | : | : | | | : | PNC : | | | :..|.....: | King and Farrel Expires January 2024 [Page 5] Internet-Draft Integrating FCAPS with ACTN July 2023 | | | | | +-----------+ | | | +---------------------+ / | / | / | ----- | ( ) | ( Phys. ) | ( Net ) | ----- | ----- ( ) ( Phys. ) ( Net ) ----- Figure 1 : The ACTN Architecture Enhanced for FCAPS Figure 1 shows the ACTN functional components as described in [RFC8453], but also introduces some common management system components. The Operational Support System (OSS) is the overarching management component that the operator uses to coordinate customers, services, and the network, and to apply policies across the network. The Network Management System (NMS) allows an operator to manage a network or set of network elements as a single unit. At the same time, the Element Management System (EMS) applies configuration and management to individual network elements. As described in [RFC8453], the function of the PNC may be provided by an NMS or an EMS. Thus, Figure 1 shows the PNC overlapping with the NMS/EMS. To avoid confusion between the three possible components (NMS, EMS, PNC) that might all be used to operate the devices in the network, this document groups all of their function together and uses the term Domain Controller. In a conventional management system, the OSS uses an interface with the Domain Controller to exchange FCAPS information. Historically, this interface has been based on CORBA/XML. Furthermore, in an ACTN system, the OSS is likely the point of origin for policy instructions that guide the MDSC in how it orchestrates customer service requests and configures the network. In [RFC8453] the MPI is used by the MDSC to instruct the PNCs about how the network must be configured to deliver the customers' services. The MPI also reports to the MDSC on the status of provisioning commands and the availability of network resources. However, up to now, the MDSC has had no visibility into the majority King and Farrel Expires January 2024 [Page 6] Internet-Draft Integrating FCAPS with ACTN July 2023 of the FCAPS functions and has, therefore, had limited reactive and proactive abilities. This document examines how the MPI may be enhanced with extensions that utilise current and future YANG-based data models to deliver extensions that provide FCAPS support. 3. Functionality at the MPI This section describes the MPI as specified before the addition of FCAPS capabilities. 3.1. Data Models at the MPI Table 1 lists the data models that can be used at the MDI for abstraction and control of underlying optical networks. Category | Data Model | Document ---------+---------------------------+-------------------------------- Topology | ietf-network | RFC 8345 +---------------------------+-------------------------------- | ietf-network-topology | RFC 8345 +---------------------------+-------------------------------- | ietf-te-topology | RFC 8795 +---------------------------+-------------------------------- | ietf-wson-topology | RFC9094 +---------------------------+-------------------------------- | ietf-otn-topology | draft-ietf-ccamp-otn-topo-yang +---------------------------+-------------------------------- | ietf-flex-grid-topology | draft-ietf-ccamp-flexigrid-yang +---------------------------+-------------------------------- | ietf-optical-impairement- | draft-ietf-ccamp-optical- | topology | impairment-topology-yang ---------+---------------------------+-------------------------------- Tunnel | ietf-te | draft-ietf-teas-yang-te +---------------------------+-------------------------------- | ietf-wson-tunnel | draft-ietf-ccamp-wson-tunnel- | | model +---------------------------+-------------------------------- | ietf-otn-tunnel | draft-ietf-ccamp-otn-tunnel- | | model +---------------------------+-------------------------------- | ietf-flexi-grid-media- | draft-ietf-ccamp-flexigrid- | channel | media-channel-yang Table 1 : ACTN MPI YANG Models 3.2. Abstraction and Control at the MPI King and Farrel Expires January 2024 [Page 7] Internet-Draft Integrating FCAPS with ACTN July 2023 The abstraction of TE modeling is described in Section 3 of [RFC8795]. The major objects that are modeled include TE topology, TE node, TE link, TE Link Termination Point (LTP), TE Tunnel Termination Point (TTP). Also included in the modeling are transitional TE link, TE node connectivity matrix, and TTP Local Link Connectivity List to describe the multiplexing relationship of links. These TE concepts are generic, but they are also applicable within an optical network. The MPI deals in abstracted TE network concepts and so can be realised using the YANG models listed in Section 3.1 to expose the TE modeled objects that can be enhanced using YANG model augmentations to make them specific to optical technologies. 4. Introduction to FCAPS 4.1. Functionalities Covered by FCAPS Although the building blocks of FCAPS are Fault, Configuration, Accounting, Performance, and Security, the important functions for integration with an ACTN system are Configuration and Performance. The basic Configuration requirement in ACTN is to configure end-to- end paths across the transport network based on the requirements of users. The foundation of Performance Management is Inventory Management. This describes all objects involved in the network, including hardware resources (such as network elements, chassis, slots, boards, ports, optical modules, and cables, etc.) and logical resource objects used for service provisioning. Performance Management is comprised of Alarm Management and Performance Monitoring, and is also built on Inventory Management. Alarm Management.When a network is running, the Domain Manager collects alarm information from devices or processes connection- related alarms and reports the alarms to the OSS of operator. So that Operations and Management engineers can detect and rectify network faults in time. The main functionalities include alarm retrieval, alarm handling, and alarm control. Performance Monitoring.Based on some Operations and Management requirement scenarios, engineers need to collect and monitor performance data from certain physical devices or logical objects to identify the status of the network. The interfaces of Performance Management include performance monitoring control, performance information retrieval, and threshold crossing alert control. 5. Abstract Control and Fine-Grain Management for ACTN King and Farrel Expires January 2024 [Page 8] Internet-Draft Integrating FCAPS with ACTN July 2023 Abstract Control represents the high-level strategic view and objectives, while Fine-Grain Management represents the detailed operational tasks and activities that support the strategic objectives. Both levels are important for effective management and control within the operator network. Abstract Control is often mapped to G.805 [G.805] objects. An Abstract Control object can also be mapped to several Fine-Grain Management objects. Therefore, we should not see these concepts as mutually exclusive, but instead as necessary approaches to be combined for holistic control and operational management of ACTN- based network infrastructures. In the context of ACTN, MPI is a concept and a set of mechanisms within ACTN that enables the interconnection of services across multiple domains or administrative boundaries. The MPI addresses the challenge of interconnecting services across multiple administrative domains. It provides a mechanism to coordinate and manage the service delivery between domains while ensuring end-to-end service continuity and quality. As highlighted earlier in this document FCAPS capabilities are also vital for smooth operation and troubleshooting of ACTN-based services. It is expected that FCAPS capabilities will require Fine- Grained Management Functions. 5.1. Abstract Control and Fine-Grain Management Functions for the MPI The Fine-Grain Management Functions can be categorised as follows. Several aspects of there functions already exist in the MDSC in the ACTN architecture, and are accessed via the MPI. Others may be added to the MPI in the future. Service Provisioning: This involves the detailed provisioning and activation of services. This includes path computation, configuring service parameters, policy management, allocating resources, and ensuring proper service activation and deactivation. Network Performance Monitoring: This encompasses monitoring and analysing network performance. It involves collecting and analysing performance metrics such as latency, jitter, packet loss, and throughput to identify and resolve performance issues promptly. Fault Detection and Alarm Management: This includes advanced fault detection mechanisms to identify and troubleshoot network issues quickly. It involves monitoring network elements, analysing alarms and events, and performing fault localisation and isolation to expedite problem resolution. King and Farrel Expires January 2024 [Page 9] Internet-Draft Integrating FCAPS with ACTN July 2023 Security Management: This covers the management of security measures within the telecommunications network. It involves activities such as access control, authentication, encryption, intrusion detection, and vulnerability management to ensure network security and protect against threats. Service Level Agreement (SLA) Management: This involves tracking service performance against SLA targets, generating SLA reports, and taking corrective actions to meet or exceed customer expectations. Capacity Planning: This encompasses detailed capacity planning activities to ensure optimal resource utilisation and meet future demands. It involves analysing traffic patterns, forecasting capacity requirements, and implementing capacity expansion strategies. 5.2. Fine-Grain Management Interfaces Several legacy Fine-Grain Management interfaces exist to facilitate the precise control and management of network elements and services. These interfaces enable communication and interaction between different systems, devices, and management platforms: o Command Line Interface (CLI); o Simple Network Management Protocol (SNMP); o CORBA/XML. New interfaces and data models have been developed that support Fine-Grain Management functions. These models are written in YANG, and the interfaces use NETCONF and RESTCONF. 5.3. Fine-Grain Management Data Models As noted in Section 5.1, several data models will be required for Fine-Grain Management in ACTN-based optical networks. Corresponding IETF proposals exist to provide optical interface configuration, resource monitoring, telemetry data, alarm and incident monitoring, inventory, life cycle management, service assurance, and asset management. This existing IETF work includes: o "Incident Management for Network Services" [I-D.feng-opsawg-incident-management] o "A YANG Data Model for Network Hardware Inventory" [I-D.ietf-ccamp-network-inventory-yang] o "Service Assurance for Intent-based Networking Architecture" [I-D.ietf-opsawg-service-assurance-architecture] King and Farrel Expires January 2024 [Page 10] Internet-Draft Integrating FCAPS with ACTN July 2023 o "YANG Modules for Service Assurance" [I-D.ietf-opsawg-service-assurance-yang] o "A Data Manifest for Contextualized Telemetry Data" [I-D.claise-opsawg-collected-data-manifest] o "Asset Lifecycle Management and Operations Problem Statement" [I-D.draft-palmero-opsawg-ps-almo] o "A YANG Data Model for Optical Resource Performance Monitoring" [I-D.draft-yu-ccamp-optical-resource-pm-yang] o "A YANG model to manage the optical interface parameters for an external transponder in a WDM network" [I-D.draft-ietf-ccamp-dwdm-if-param-yang] o "A YANG Data Model for Client Signal Performance Monitoring" [I-D draft-zheng-ccamp-client-pm-yang] Editors note: This section will expand the list of the available IETF YANG data models that could provide Fine-Grain Management functionality, in the context of ACTN, specifically the MDI. 5.4. Fine-Grain Management Example Editors note: An optical example of Fine-Grain Management using the ACTN architecture will be provided in future versions of this document. 6. Manageability Considerations TBD. 7. Security Considerations TBD. 8. IANA Considerations TBD. 9. References 9.1. Informative References [RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for Abstraction and Control of TE Networks (ACTN)", RFC 8453, DOI 10.17487/RFC8453, August 2018, . King and Farrel Expires January 2024 [Page 11] Internet-Draft Integrating FCAPS with ACTN July 2023 [RFC8795] X. Liu, et al., "YANG Data Model for Traffic Engineering (TE) Topologies", RFC 8795, DOI 10.17487/RFC8795, August 2020, . [G.805] ITU-T G.805 (2000), Generic functional architecture of transport networks. [M.3060] ITU-T M.3060 (2006), Principles for the Management of Next Generation Networks. [M.3401] ITU-T M.3401 (2020), Framework of smart operation, management and maintenance. [I-D.feng-opsawg-incident-management] Feng, C., Hu, T., Contreras, L. M., Wu, Q., and C. Yu, "Incident Management for Network Services", Work in Progress, Internet-Draft, draft-feng- opsawg-incident-management, March 2023, . [I-D.ietf-ccamp-network-inventory-yang] Yu, C., Belotti, S., Bouquier, J., Peruzzini, F., and P. Bedard, "A YANG Data Model for Network Hardware Inventory", Work in Progress, Internet-Draft, draft-ietf-ccamp-network-inventory-yang, July 2023, . [I-D.ietf-opsawg-service-assurance-architecture] Claise, B., Quilbeuf, J., Lopez, D., Voyer, D., and T. Arumugam, "Service Assurance for Intent-based Networking Architecture", Work in Progress, Internet-Draft, draft- ietf-opsawg-service-assurance-architecture, January 2023, . [I-D.ietf-opsawg-service-assurance-yang] Claise, B., Quilbeuf, J., Lucente, P., Fasano, P., and T. Arumugam, "YANG Modules for Service Assurance", Work in Progress, Internet-Draft, draft-ietf-opsawg-service-assurance-yang, January 2023, . [I-D.claise-opsawg-collected-data-manifest] Claise, B., Quilbeuf, J., Lopez, D., Martinez-Casanueva, I. D., and T. Graf, "A Data Manifest for Contextualized Telemetry Data", Work in Progress, Internet-Draft, draft-claise-opsawg-collected- data-manifest, March 2023, . King and Farrel Expires January 2024 [Page 12] Internet-Draft Integrating FCAPS with ACTN July 2023 [I-D.draft-palmero-opsawg-ps-almo] Palmero, M., Brockners, F., Kumar, S., Cardona, C., and D. Lopez, "Asset Lifecycle Management and Operations, Problem Statement", Work in Progress, Internet-Draft, draft-palmero-opsawg-ps-almo, June 2023, . [I-D.draft-ietf-ccamp-dwdm-if-param-yang] Galimberti, G., Kunze, R., Hiremagalur, D., and G. Grammel, "A YANG model to manage the optical interface parameters for an external transponder in a WDM network", Work in Progress, Internet- Draft, draft-ietf-ccamp-dwdm-if-param-yang, March 2023, . [I-D.draft-yu-ccamp-optical-resource-pm-yang] C. Yu, et al., "A YANG Data Model for Optical Resource Performance Monitoring", Work in Progress, Internet-Draft, draft-yu-ccamp-optical- resource-pm-yang, July 2023, [I-D draft-zheng-ccamp-client-pm-yang] H. Zheng, et al, "A YANG Data Model for Client Signal Performance Monitoring", draft- zheng-ccamp-client-pm-yang, Work in Progress, July 2023, < https://datatracker.ietf.org/doc/draft-zheng-ccamp-client- pm-yang> [RFC8795] X. Liu, et al., "YANG Data Model for Traffic Engineering (TE) Topologies", RFC 8795, DOI 10.17487/RFC8795, August 2020, . Authors' Addresses Daniel King Old Dog Consulting Email: daniel@olddog.co.uk Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk King and Farrel Expires January 2024 [Page 13]