Re: Issue 13.3: <edit-config> operation set proposal

[Andy Bierman <abierman@cisco.com>]

At 04:23 PM 2/21/2004, Andy Bierman wrote:
>Hi,

I forgot to add this issue to the issue list update email.
The WG in the Seoul meeting accepted this operation set.

We've been looking into implementing the netconf operation
set on some new and existing data models, and it seems that
it can be data-model specific as to:
  - which of the 5 operations actually apply to the data model
  - what granularity each operation can be applied
  - what does it mean to do a create or a delete (sometimes nested data
    structures are auto-generated, sometimes not, etc.)

I think this operation set should be considered the
full set of standard edit-config operations, and
the data modelling language (<appinfo> extension)
should provide mechanisms for applications to automatically
answer the questions listed above.

Andy


>I am proposing the following set of enum values for the
>operation attribute.  IMO, the incremental cost in complexity
>in the device will add a lot of value to the application
>programmer, and also make access control configuration easier.
>I think this will cover all the use cases we've come up with
>so far:
>
>[Replacement text for operation attribute, (merge, replace,
>and delete are unchanged).]
>
>      operation: (create | modify | merge | replace | delete) 
>         [default: merge]
>
>         ...
>
>         The operation attribute has one of the following values:
>     
>            create: The configuration data identified by the element
>            containing this attribute is created (only if the 
>            specified portion of the data model does not already
>            exist) at the corresponding level in the configuration 
>            datastore identified by the target parameter.
>
>            modify: The configuration data identified by the element
>            containing this attribute is modified (only if the 
>            specified portion of the data model already exists) at 
>            the corresponding level in the configuration datastore 
>            identified by the target parameter.
>
>            merge: The configuration data identified by the element
>            containing this attribute is merged with the configuration
>            at the corresponding level in the configuration datastore
>            identified by the target parameter.
>
>            replace: The configuration data identified by the element
>            containing this attribute replaces any related configuration
>            in the configuration datastore identified by the target
>            parameter.  Unlike a <copy-config> operation, which replaces
>            the entire target configuration, only the configuration
>            actually present in the config parameter is affected.
>
>            delete: The configuration data identified by the element
>            containing this attribute is deleted in the configuration
>            datastore identified by the target parameter.
>
>
>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/> 


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