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

[Jean Quilbeuf <[e-mail]>]

Dear All,

I don’t think there are other pending comments on this draft.
I believe this draft is ready for WGLC.

Best,
Jean

> -----Original Message-----
> From: Jean Quilbeuf <jean.quilbeuf=[e-mail]>
> Sent: Tuesday, March 18, 2025 3:56 PM
> To: [e-mail]
> Subject: [netconf] Re: I-D Action: draft-ietf-netconf-configuration-tracing-05.txt
> 
> Hello,
> This version updates the security considerations to the latest template as
> requested by Mahesh during the session.
> 
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-netconf-configuration-
> tracing-05
> 
> Best,
> Jean
> 
> > -----Original Message-----
> > From: [e-mail] <[e-mail]>
> > Sent: Tuesday, March 18, 2025 3:45 PM
> > To: [e-mail]
> > Cc: [e-mail]
> > Subject: [netconf] I-D Action:
> > draft-ietf-netconf-configuration-tracing-05.txt
> >
> > Internet-Draft draft-ietf-netconf-configuration-tracing-05.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-05.txt
> >    Pages:   18
> >    Dates:   2025-03-18
> >
> > 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-trac
> > ing/
> >
> > There is also an HTML version available at:
> > https://www.ietf.org/archive/id/draft-ietf-netconf-configuration-traci
> > ng-
> > 05.html
> >
> > A diff from the previous version is available at:
> > https://author-tools.ietf.org/iddiff?url2=draft-ietf-netconf-configura
> > tion-
> > tracing-05
> >
> > Internet-Drafts are also available by rsync at:
> > rsync.ietf.org::internet-drafts
> >
> >
> > _______________________________________________
> > netconf mailing list -- [e-mail] To unsubscribe send an email
> > to netconf- [e-mail]
> _______________________________________________
> netconf mailing list -- [e-mail] To unsubscribe send an email to netconf-
> [e-mail]