%% You should probably cite rfc8969 instead of this I-D. @techreport{ietf-opsawg-model-automation-framework-00, number = {draft-ietf-opsawg-model-automation-framework-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-opsawg-model-automation-framework/00/}, author = {Qin Wu and Mohamed Boucadair and Diego Lopez and Chongfeng Xie and Liang Geng}, title = {{A Framework for Automating Service and Network Management with YANG}}, pagetotal = 35, year = , month = , day = , abstract = {Data models for service and network management provides a programmatic approach for representing (virtual) services or networks and deriving (1) configuration information that will be communicated to network and service components that are used to build and deliver the service and (2) state information that will be monitored and tracked. Indeed, data models can be used during various phases of the service and network management life cycle, such as service instantiation, service provisioning, optimization, monitoring, and diagnostic. Also, data models are instrumental in the automation of network management. They also provide closed-loop control for the sake of adaptive and deterministic service creation, delivery, and maintenance. This document provides a framework that describes and discusses an architecture for service and network management automation that takes advantage of YANG modeling technologies. This framework is drawn from a network provider perspective irrespective of the origin of a data module; it can accommodate even modules that are developed outside the IETF. The document aims to exemplify an approach that specifies the journey from technology-agnostic services to technology-specific actions.}, }