Hi, I guess I do not agree with the premise of the draft, which is that the client needs to take over control of the system-controlled configuration. I will wait for a draft update and see if that helps understand it better.
Andy On Tue, Aug 17, 2021 at 11:21 AM Kent Watsen <[email protected]> wrote: > > >IMO this draft overlaps the factory-default datastore. > >Unfortunately, RFC 8808 does not document NMDA, Appendix A3 details > >https://datatracker.ietf.org/doc/html/rfc8342#appendix-A.3 > >It does not say if <factory-default> datastore feeds into <running> or > into <intended>. > >It is not clear how <system> would interact with other datastores. > [Qin]: As described in Appendix-A.3, two ways to interact with other > datastore are discussed, one is interact implicitly, the other is to use > RPC to trigger application of the datastore's data, in factory default > setting case, <factory-reset> rpc will reset the contents of all relevant > datastores to factory default state. > The extreme case of factory default state is no configuration at all for > each datastore. > > > Right. Also, the word “flow” doesn’t seem quite right…at least in my > mind, it suggests an ongoing relationship, whereas <factory-default> is > really for one-time initializations. > > From https://datatracker.ietf.org/doc/html/rfc8808#section-3: > > Management operations: The contents of the datastore is set by the > server in an implementation-dependent manner. The contents cannot > be changed by management operations via the Network Configuration > Protocol (NETCONF), RESTCONF, the CLI, etc., unless specialized, > dedicated operations are provided. The datastore can be read > using the standard NETCONF/RESTCONF protocol operations. The > "factory-reset" operation copies the factory default contents to > <running> and, if present, <startup> and/or <candidate>. The > contents of these datastores is then propagated automatically to > any other read-only datastores, e.g., <intended> and > <operational>. > > > > >It is not clear why it is even needed since <factory-default> contains > only system settings. > [Qin]: I agree <factory-default> could have system setting. But > unspecified for some reasons. > Based on earlier discussion on factory default, what content is included > in <factory-default> and how to format this content, e.g., YANG instance > file format > Have been ruled out of the scope. See the diff in v-07 > https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-factory-default-07.txt > > > > Regardless, <factory-default> cannot be used for immutable “system" > defined objects, since it’s contents initialize client-editable datastores. > > > K. > > >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
