Re: An SMIng module for DiffServ

[Alexandros Zachos <zachos@ibr.cs.tu-bs.de>]

Hi,
I missed 4 open issues on the draft, so I post them here:

1) In case there is one attribute (e.g. the unique id attribute) that
   we would like to use for both SNMP and COPS, the types of indexes
   for those may differ as far as the range is concerned. If it's another
   type, then i guess there's not much to do.
   Do we overwrite attributes, types, create a derivate
   class with a new attribute or just use refine?
2) A design question: for all the NextFree objects in the the MIB
   is it better to create on generic class with the one attribute
   needed and always use the same scalars clause only substituting
   the oid and the name of the NextFree-scalar?
3) DiffServDataPathEntry includes diffServDataPathIfDirection which
   has max-access not-accessible. The grammar for sming only allows
   for readwrite,readonly and notify access. Is this to be marked
   as "access notify"?
4) Descriptions in the MIB and PIB often reference other objects by name.
   Since the descriptions in any module autogenerated from the SMIng
   module would have the descriptions of the attributes, these references
   will likely not exist. I don't know how this could be cleanly solved.

OK, that's it. Thanks for your patience and I hope to get lots of
useful feedback :-)

Regards,
Alexandros Zachos