Hi Qiufang, Thank you for this update.
I believe this fully addresses the issue raised by Juergen. I appreciate the simplicity and robustness of this approach. I hope that NETCONF-next and RESTCONF-next will assert the use of NMDA. Kent > On Sep 29, 2024, at 10:36 PM, maqiufang (A) > <[email protected]> wrote: > > > Hi, all, > > This version incorporates some WGLC comments. The most notable change is that > the entire 'copy' requirements, including the definition of the > 'resolve-system' parameter, have been removed from this version (note that > this still does not prevent clients from copying system data into <running>, > but it is not necessarily needed now). Instead, the following statement has > been added in the last paragraph of the introduction section: > " The solution defined in this document requires the use of NMDA for both > clients and servers. " > > This implies that this document can only be used in the context of NMDA and > thus does not impact legacy clients that rely on the validity of <running> > alone. If both clients and servers support NMDA and there could be unexpanded > templates and inactive configuration defined in <running> as per RFC 8342, > <running> could be validated by effectively validating <intended>. Therefore > no need to always copy the referenced system configuration into <running> > with <system> being merged into <intended>. Make sense? > > Best Regards, > Qiufang > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Monday, September 30, 2024 10:14 AM > To: Chong Feng <[email protected]>; Qin Wu <[email protected]>; Qin Wu > <[email protected]>; maqiufang (A) <[email protected]> > Subject: New Version Notification for draft-ietf-netmod-system-config-09.txt > > A new version of Internet-Draft draft-ietf-netmod-system-config-09.txt has > been successfully submitted by Qiufang Ma and posted to the IETF repository. > > Name: draft-ietf-netmod-system-config > Revision: 09 > Title: System-defined Configuration > Date: 2024-09-29 > Group: netmod > Pages: 32 > URL: > https://www.ietf.org/archive/id/draft-ietf-netmod-system-config-09.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-netmod-system-config/ > HTMLized: > https://datatracker.ietf.org/doc/html/draft-ietf-netmod-system-config > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-netmod-system-config-09 > > Abstract: > > The Network Management Datastore Architecture (NMDA) in RFC 8342 > defines several configuration datastores holding configuration. The > contents of these configuration datastores are controlled by clients. > This document introduces the concept of system configuration > datastore holding configuration controlled by the system on which a > server is running. The system configuration can be referenced (e.g., > leafref) by configuration explicitly created by clients. > > This document updates RFC 8342. > > > > The IETF Secretariat > > > _______________________________________________ > netmod mailing list -- [email protected] > To unsubscribe send an email to [email protected]
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
