RE: comments/review <draft-ietf-ops-mib-review-guidelines-00.txt>

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

I have one more concern. It is something I run into
very often when reviewing MIB modules. And that is

   Naming Conventions for descriptors.

- We want them to all start with the same prefix within
  one module (to make it easier to prevent clashes with
  other IETF stds track modules). So if module is
    xxxMIB 
  Then I want all descriptors to start with xxx, e.g.
    xxxSomeotherName

- For a table, I like it if they have
    xxxZzzTable
  Then I prefer to see objects in that table as
    xxxZzzSomeotherName
  so we can easily see which objects are from which table

- I like it if, when they do use abbreviations, that they
  use them consistently. Sometimes I see
    xxxRemAddress
    xxxRemoteAddr
    xxxDestinationAddress
    xxxDestAddr
    xxxDstAddr
  I guess you get the gist

- For TCs that are not generic, I like them to also
  start with the prefix, e.g.
    XxxSomethinOrOtherTC 

I think I would like it to also be one of the checkpoints in
appendix A.

Do people find this to much of another CLR ??

Thanks,
Bert