[OPSAWG] RFC 8969 on A Framework for Automating Service and Network Management with YANG
rfc-editor@rfc-editor.org Sat, 23 January 2021 00:37 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B40F03A16B9; Fri, 22 Jan 2021 16:37:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4etpac10Rfaj; Fri, 22 Jan 2021 16:36:59 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83AC13A166D; Fri, 22 Jan 2021 16:36:51 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5CE05F40757; Fri, 22 Jan 2021 16:36:32 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, opsawg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210123003632.5CE05F40757@rfc-editor.org>
Date: Fri, 22 Jan 2021 16:36:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/DB9WJYaJclD6_8IFCV_GtfCO5bM>
Subject: [OPSAWG] RFC 8969 on A Framework for Automating Service and Network Management with YANG
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2021 00:37:09 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8969 Title: A Framework for Automating Service and Network Management with YANG Author: Q. Wu, Ed., M. Boucadair, Ed., D. Lopez, C. Xie, L. Geng Status: Informational Stream: IETF Date: January 2021 Mailbox: bill.wu@huawei.com, mohamed.boucadair@orange.com, diego.r.lopez@telefonica.com, xiechf@chinatelecom.cn, gengliang@chinamobile.com Pages: 40 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-opsawg-model-automation-framework-10.txt URL: https://www.rfc-editor.org/info/rfc8969 DOI: 10.17487/RFC8969 Data models provide a programmatic approach to represent services and networks. Concretely, they can be used to derive configuration information for network and service components, and state information that will be monitored and tracked. Data models can be used during the service and network management life cycle (e.g., service instantiation, service provisioning, service optimization, service monitoring, service diagnosing, and service assurance). Data models are also instrumental in the automation of network management, and they can provide closed-loop control for adaptive and deterministic service creation, delivery, and maintenance. This document describes a framework for service and network management automation that takes advantage of YANG modeling technologies. This framework is drawn from a network operator perspective irrespective of the origin of a data model; thus, it can accommodate YANG modules that are developed outside the IETF. This document is a product of the Operations and Management Area Working Group Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC