data integrity problem with named profiles

[Andy Bierman <ietf@andybierman.com>]

Hi,

Although NETCONF has locking, it is write locking, not read locking.
If a named profile is not in a stable state (due to multiple edits),
there is no way for a manager to know this, at the time the 
<create-subscription>
is processed.

I'm not saying we need RowStatus, but it is clear that all
of the design factors wrt/ data modeling have not been thought out.
Setting precedence out of ignorance doesn't usually turn out so great.
It should be clear to the WG (and written in the document) exactly
how the data model behaves wrt/ the NETCONF protocol.

Andy


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>