Hi,
For partial locking, since the lock applies not only to Netconf but to
other NM interfaces as well, it is imperative that the managed entity
understand just what **instrumentation** is being partially locked,
not just what Netconf data model subset is being partially locked.
In SNMP, we use strings to identify a "naming scope" - a community or
a context, and it is imperative that the agent understand what data is
in the community or the context. It is the implementation of the
managed entity that determines just what distinct communities or
contexts exist within the managed entity, and an agent knows about the
data subsets, even if there are dynamic hardware changes that affect
the subsets. The manager can learn what managed objects are in a
community or context by querying the agent. I think the same
agent-centric determination of named data partitions will be required
if the partial locking will apply to multiple NM interfaces that use
different data modeling interfaces.
In SNMP and/or Netconf, the manager/operatorcan also dynamically
specify subtrees of data or "view families" or XPath expressions. I
think we need to identify whether and how this type of dynamic subset
of data might be locked by partial locking, whether such
dynamically-specified locks apply across multiple NM interfaces, and
how the managed entity knows which non-Netconf data to partially lock.