Re: partial locking and access control

[Phil Shafer <phil@juniper.net>]

Andy Bierman writes:
>Let's say an operator locks "*/ifAdminStatus" to make sure that
>nobody turns off any interfaces during some network test
>or big config change.

This example and your "div 7" one both highlight one of the problems
with partial locking.  As a server, my data model may not support
(and I don't want to support) random bits of XPath.   Locking status
fields, etc is just silliness not worth burning code on.

IMHO the data model needs to define what's lockable.  Supporting
random XPath expression locking is way too expensive.

Thanks,
 Phil

--
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/>