> Punting the configuration problem to Netconf doesn't reduce the > modeling (or operational) complexity presented by read-write objects > like these. If you argue instead that they should be read-only, that's > another matter (though still fraught with complexity, given the ways > Netconf can work) but doing so also, for me at least, raises the "why > bother" question regarding this MIB module. If these objects would > merely reflect the current configuration data, then they'd add no value, > and there'd be no point in having them at all.
For any given managed object in this mib module it should be shown how this is useful for monitoring purposes otherwise should not be added. If it duplicates configuration data so be it -- so long as its value has been shown. Regards, Mike MacFaden Staff Engineer R&D Apps VMware, Inc Palo Alto CA _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
