[Syslog] Review of Mib-10, part 1

Hi Glenn,

-10- looks better than -09-. Thanks for getting this out.
I sent some comments, and I think some still need to be addressed.
Have you finished addressing all Bert's comments?
Here are a couple things I spotted in -10-

1) syslEntCtlEntry should be changed to match the other prefixes
(syslogEntityControlEntry)

2) the same for syslEntOpsEntry, syslEntStarted, syslEntStopped, etc.

3) I recommend chaging "operations related information" to "operations
information"

4) I recommend changing syslogSystemGroup to syslogDefaultGroup if
that's the prefix you keep on all the "Default" variables.

5) I recommend changing syslDevOpsGroup to syslogEntityOpsGroup, and
syslDevCtlGroup to syslogEntityControlGroup. Why do we need two
groups? Can you implement Ops without the Control table, now that one
augments the other?

6) /implememt/implement/

7) Is it possible to support notifications only, since the
notifications contain data from the tables not implemented? Where do
the values come from?

8) did you run the document through the idnits checker at
http://tools.ietf.org/tools/idnits/?
It still reports this problem:
 The page length should not exceed 58 lines per page, but there was 38
    longer pages, the longest (page 2) being 60 lines

9) did you run the MIB module through the smilint utility?
Instructions can be found at
http://www.ibr.cs.tu-bs.de/projects/libsmi/mailrobot.html?lang=de

10) Can you add "Intended status: Standards Track" to the header (see
syslog-sign for an example).

David Harrington
dharrington@huawei.com 
dbharrington@comcast.net
ietfdbh@comcast.net

_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog