Technical Summary
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.
Working Group Summary
Was there anything in the WG process that is worth noting?
For example, was there controversy about particular points
or were there decisions where the consensus was
particularly rough?
From the Shepherd report:
One particular point was somewhat controversial. This being that the
current solution is NMDA only, necessitating that clients wanting to
perform offline-validation must know how to fetch the <system> datastore
and merge it with the <running> datastore. However, the WG noted that
trying to support legacy clients made the solution overly complex and
architecturally unsound.
Document Quality
Are there existing implementations of the protocol? Have a
significant number of vendors indicated their plan to
implement the specification? Are there any reviewers that
merit special mention as having done a thorough review,
e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues? If
there was a MIB Doctor, Media Type, or other Expert Review,
what was its course (briefly)? In the case of a Media Type
Review, on what date was the request posted?
Again, from the Shepherd (Kent Watsen) report:
There is interest in implementing it (including by yours truly), but
I am unaware of any implementations yet.
Separately, an early and an IETF LC review was conducted by YANG experts, and they have approved the module.
Personnel
The Document Shepherd for this document is Kent Watsen. The Responsible
Area Director is Mahesh Jethanandani.