Hi, I like this draft -- even more than I like datastores. Looks like some thought went into the terminology section.
One minor concern: sec. 4.1: On a traditional NETCONF implementation, <running> and <intended> are always the same. The intended datastore is completely proprietary. Is that part of the architecture or are there any plans for the standards to have some purpose for the intended datastore? I want to support 2 datastores that don't fit your descriptions very well: factory: read-only config representing the values that a factory reset would use. Allows copy-config to support a factory config reload. library-config: needed as a bootstrap datastore with the module/bundle configuration. Like the ietf-yang-library, but the config does not exactly match the structure of the YANG library. Can vendors add datastores to a server? Or is this IANA-registered? And/or hard-wired in RFCs? Andy
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
