Re: [netmod] comments on draft-ietf-netmod-snmp-cfg--05

[Andy Bierman <[e-mail]>]

On Thu, Jun 12, 2014 at 11:26 PM, Juergen Schoenwaelder <
[e-mail]> wrote:

> On Thu, Jun 12, 2014 at 02:49:27PM -0700, Andy Bierman wrote:
> > Hi,
> >
> > It's probably past WG Last Call, but I still do not understand
> > the value of splitting the ietf-snmp configuration module into
> > 12 files (1 main + 11 sub-modules) instead of just 1 file.
> >
> > IMO it makes it harder to read, not easier, and wrt/ YANG library
> > management,
> > there are 12 files to update and keep in sync, instead of 1.
> >
> > Is there some expectation that individual sub-modules for SNMP
> > configuration will be updated regularly in new RFCs?
>
> The organization essentially reflects the modular structure of the
> SNMPv3 MIB modules. The SNMPv3 MIB modules are roughly the same
> number.
>
> If updates will ever will be necessary, we might benefit from the
> modular structure. If updates will never be needed, there is not much
> work with synchronizing the sub-modules either. Whether modularity is
> a good thing of not can likely be discussed endlessly. In this case,
> we followed the modular structure of the SNMPv3 MIB modules.
>
>

Actually, you did not really follow the SMIv2 structure, or you would have
used
modules instead of submodules. The main module (ietf-snmp) is just a list
of include-by-revision statements.  All submodules have to be present
or the tool will exit with a fatal error.  I suppose the main module could
be altered by vendors (e.g., comment out the include-stmts they don't want
to support), but that would be non-compliant for standard modules.


/js
>

Andy


>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
> Fax:   [phone]         <http://www.jacobs-university.de/>
>