Dear all,
As discussed with the OPSAWG and NETCONF chairs, we updated
draft-quilbeuf-_opsawg_-configuration-tracing-02 by
draft-quilbeuf-_netconf_-configuration-tracing-00, to be part of the
transaction-id drafts bundle.
Only references were updated, no other diffs.
The "replaced-by" in the tracker will follow (to be done by one of the
chairs).
Regards, Benoit
-------- Forwarded Message --------
Subject: New Version Notification for
draft-quilbeuf-netconf-configuration-tracing-00.txt
Date: Thu, 21 Sep 2023 08:25:33 -0700
From: internet-dra...@ietf.org
To: Diego R. Lopez <diego.r.lo...@telefonica.com>, Benoit Claise
<benoit.cla...@huawei.com>, Diego Lopez <diego.r.lo...@telefonica.com>,
Jean Quilbeuf <jean.quilb...@huawei.com>, Qiong Sun
<sunqi...@chinatelecom.cn>, Sun Qiong <sunqi...@chinatelecom.cn>, Thomas
Graf <thomas.g...@swisscom.com>
A new version of Internet-Draft
draft-quilbeuf-netconf-configuration-tracing-00.txt has been successfully
submitted by Benoit Claise and posted to the
IETF repository.
Name: draft-quilbeuf-netconf-configuration-tracing
Revision: 00
Title: External Trace ID for Configuration Tracing
Date: 2023-09-21
Group: Individual Submission
Pages: 16
URL:
https://www.ietf.org/archive/id/draft-quilbeuf-netconf-configuration-tracing-00.txt
Status:
https://datatracker.ietf.org/doc/draft-quilbeuf-netconf-configuration-tracing/
HTML:
https://www.ietf.org/archive/id/draft-quilbeuf-netconf-configuration-tracing-00.html
HTMLized:
https://datatracker.ietf.org/doc/html/draft-quilbeuf-netconf-configuration-tracing
Abstract:
Network equipment are often configured by a variety of network
management systems (NMS), protocols, and teams. If a network issue
arises (e.g., because of a wrong configuration change), it is
important to quickly identify the root cause and obtain the reason
for pushing that modification. Another potential network issue can
stem from concurrent NMSes with overlapping intents, each having
their own tasks to perform. In such a case, it is important to map
the respective modifications to its originating NMS.
This document specifies a NETCONF mechanism to automatically map the
configuration modifications to their source, up to a specific NMS
change request. Such a mechanism is required, in particular, for
autonomous networks to trace the source of a particular configuration
change that led to an anomaly detection. This mechanism facilitates
the troubleshooting, the post mortem analysis, and in the end the
closed loop automation required for self-healing networks. The
specification also includes a YANG module that is meant to map a
local configuration change to the corresponding trace id, up to the
controller or even the orchestrator.
The IETF Secretariat
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
