Vincent Cridlig wrote:
There seems to be WG consensus that actions should not
be modeled as data, but rather as RPC methods. Therefore,
restricting access to certain RPC methods (<delete-config>,
<reset-device>, etc.) is going to be important.
Each permission is expressed with two things:
- an XPath expression, saying which nodes are concerned,
- an attribute which can be "r", "w", or "rw".
What happens if Xpath expressions overlap (i.e. 1 or more nodes
are selected by more than 1 Xpath expression)? Do you just
execute the list in order, like an ACL on a router?
I am giving in on the "create/delete" feature in the ACM.
The fact is that this is more effort to implement and
takes more runtime cycles, because you have to check the
actual configuration database to know if a merge or replace
is really a create or delete.
If the ACM allows for read/write, then you only have to check
the PDU, not the configuration target as well.