Re: [netmod] Last Call: draft-ietf-netmod-snmp-cfg-03 (20131220)

[Martin Bjorklund <[e-mail]>]

Hi,

B Lukovic <[e-mail]> wrote:
> Hi,
> 
> Re: target address/target params tables.
> snmpTargetParamsName is not mapped into yang module.
> This prevents agent from restoring snmp configuration after
> restart/reload (assuming configuration is yang based). 
> E.g. agent is configured through snmp, "t1" and "t2" are rows in
> targetAddress, "p1" is row in targetParams.
> Both rows in targetAddressTable:
>     "t1",...,"p1",...
>     "t2",...,"p1",...
> "point" to the same row in targetParamsTable:
>     "p1", "v2c", "public"
> saved as yang, targetParams row(s) are merged with rows of targetAddress:
>     <target>
>       <name>t1</name>
>       ...
>       <v2c>
>         <security-name>public</security-name>
>       </v2c>
>     ..
>     </target>
>     <target>
>       <name>t2</name>
>       ...
>       <v2c>
>         <security-name>public</security-name>
>       </v2c>
>     ..
>     </target>
> 
> SNMP agent initialized from this config would not know the original
> index ("p1") used in targetParamsTable. 
> One can argue that "locally arbitrary" in description of
> snmpTargetParamsName allows agent to reassign indices,
> but I believe this would lead to confusion.

If data is created over NETCONF, the system will invent some index for
the snmpTargetParamsName.  If the data is created over SNMP, the
snmpTargetParamsName is simply not shown over NETCONF.


> Possible solutions:
> -  create "targetparams" list (index = leaf "name"), replace
>    "params" choice with leaf "params" with type leafref { path
>    "/snmp/targetparams/name" } 

This is certainly possible, but it introduces an extra level of
indirection that complicates the model.

> -  leave "params" choice, replace optional "notify-filter-profile"
>    leaf with mandatory "param-name" leaf, 
>    explain relation between "param-name" and
>    "notify-filter-profile/name" in description of "param-name" 

I don't think this solves the problem, since some reference is needed
between the notify-filter-profile and the target-params.



/martin