[Syslog] MIB Issue #2: document terminology.

["David Harrington" <ietfdbh@comcast.net>]

Hi,

[speaking as co-chair]

For issue#2, you do not need to worry about the MIB module itself, so
a lack of SNMP expertise is not important to resolving this issue.

I have a copy of an unofficial -02- revision of the syslog-device-mib
that was edited by Bruno Pape, dated August 2002. The current mib
draft inherited its terminology and architecture diagrams and support
for multiple entities from the WG drafts edited by Bruno. So the
current terminology and architecture and table structure was decided
by the WG, in the adoption and subsequent development of the mib
document.

As WG editor, it is Glenn's responsibility to represent in the
document the consensus of the WG; if only one WG member argues for
substantial changes to an existing WG document, then there is no clear
WG consensus to make such changes. 

We need multiple WG members to review the current MIB document for the
chairs to determine that the terminology used in the text sections
represents what the WG wants to see, and that WG agrees the text
section adequately describes what information is needed to manage a
syslog sender, receiver, relay, and/or collector.

Again, you do not need to be SNMP-literate to do such a review; We
need a review of the surrounding text.

Please make suggestions for replacement text when you think the
current text is not appropriate.

David Harrington
dharrington@huawei.com 
dbharrington@comcast.net
ietfdbh@comcast.net
Syslog WG co-chair



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