[netconf] Re: I-D Action: draft-ietf-netconf-configuration-tracing-02.txt

Jean Quilbeuf <jean.quilbeuf@huawei.com> Mon, 21 October 2024 10:49 UTC

From: Jean Quilbeuf <jean.quilbeuf@huawei.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] I-D Action: draft-ietf-netconf-configuration-tracing-02.txt
Thread-Index: AQHbI6Ztz7eqZPu6WUGWZ8aWr0c9ZbKRBa3w
Date: Mon, 21 Oct 2024 10:49:46 +0000
Message-ID: <32cc2e3b4c0d4989b545ac1c24162130@huawei.com>
References: <172950748705.1928204.864441062829690140@dt-datatracker-78dc5ccf94-w8wgc>
In-Reply-To: <172950748705.1928204.864441062829690140@dt-datatracker-78dc5ccf94-w8wgc>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: VZRHC3ATV5N3P72EYI772FY57RWRU2XJ
Precedence: list
Subject: [netconf] Re: I-D Action: draft-ietf-netconf-configuration-tracing-02.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/urmTvfqffypEQA56AB669bQf-sM>

Dear All,
This new version is better aligned with draft-rogaglia-netconf-trace-ctx-extension and defines the attributes for passing the client id in the text instead as a YANG metadata.

Best,
Jean

> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Monday, October 21, 2024 11:45 AM
> To: i-d-announce@ietf.org
> Cc: netconf@ietf.org
> Subject: [netconf] I-D Action: draft-ietf-netconf-configuration-tracing-02.txt
> 
> Internet-Draft draft-ietf-netconf-configuration-tracing-02.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-02.txt
>    Pages:   17
>    Dates:   2024-10-21
> 
> 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-02.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-netconf-configuration-tracing-02
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> netconf mailing list -- netconf@ietf.org To unsubscribe send an email to netconf-
> leave@ietf.org

[netconf] I-D Action: draft-ietf-netconf-configur… internet-drafts
[netconf] Re: I-D Action: draft-ietf-netconf-conf… Jean Quilbeuf