[New-wg-docs] I-D Action: draft-ietf-netconf-configuration-tracing-00.txt

internet-drafts@ietf.org Thu, 11 January 2024 18:33 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: new-wg-docs@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170499800852.47648.13055459742362153096@ietfa.amsl.com>
Date: Thu, 11 Jan 2024 10:33:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-wg-docs/VS9PVFCjpe0JeNM7OyWPdSsEUts>
Subject: [New-wg-docs] I-D Action: draft-ietf-netconf-configuration-tracing-00.txt

Internet-Draft draft-ietf-netconf-configuration-tracing-00.txt is now
available. It is a work item of the Network Configuration (NETCONF) WG of the
IETF.

   Title:   External Trace ID for Configuration Tracing
   Authors: Jean Quilbeuf
            Benoit Claise
            Thomas Graf
            Diego R. Lopez
            Qiong Sun
   Name:    draft-ietf-netconf-configuration-tracing-00.txt
   Pages:   16
   Dates:   2024-01-10

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 datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-netconf-configuration-tracing/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-netconf-configuration-tracing-00.html

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

[New-wg-docs] I-D Action: draft-ietf-netconf-conf… internet-drafts