Mib structure issue wasTransportDomain issue

["tom.petch" <cfinss@dial.pipex.com>]

----- Original Message -----
From: "David Harrington" <ietfdbh@comcast.net>
To: <j.schoenwaelder@iu-bremen.de>; "'Glenn M. Keeni'" <glenn@cysols.com>
Cc: "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>; <syslog@ietf.org>
Sent: Thursday, December 28, 2006 10:34 PM
Subject: RE: [Syslog] TransportDomain issue


> [speaking as co-chair]
>
> As this discussion continues, and based on the updated description
> clauses, it appears more and more obvious that some objects are only
> important for receivers or for senders or for relays:

Agreed although I disagree with some of your characterisations.

More fundamentally, who is going to implement a MIB module where?

Not I (sadly) but the one I want to see is in the managed network device, the
sender, not relay/collector/receiver ( hosts which are likely to have plenty of
non-MIB ways of doing things) so that is my prejudice.  But for this work to
have value, someone needs to be likely to implement this and I do not know who
that might be; it is their views that I think matter most and I do not know what
those views are - it may be that all potential implementors only want to
implement on Windows platforms:-) which would in turn affect what should be in a
MIB module.

Whatever, my list of desirable objects is slightly different, as follows (I have
shortened the object names to make them easier to read and write, the additional
words can always go back later).  Also, I see a relay as a sender+receiver so
with one exception, I see no object as particular to a relay.

syslogAddrType / syslogAddr / syslogPort
 endpoint on which a receiver (relay) listens
 endpoint to which a sender (relay) sends

syslogService
 do not understand this except as a port, for which use syslogPort

syslogMaxMessageSize
 maximum message size a receiver (relay) will accept
syslogMsgsTooLarge
 messages received and discarded as too large by receiver (relay)
syslogMsgsReceived
 total messages received valid and invalid by receiver (relay)
syslogMsgsIllFormed
 messages received and discarded incorrect format by receiver (relay)
syslogMsgsLastRecdTime
 sysUpTime of last message received by receiver (relay)

syslogEncapsulation
 receiver (relay) formats supported (BEEP RAW, BEEP COOKED, TLS, SIGN ...)
 sender (relay) formats supported
syslogMsgsSent
 total messages sent successfully by sender (relay)
syslogMsgsDropped
 messages that could not be sent by sender (relay)
syslogMsgsLastSentTime
 sysUpTime of last message sent by sender (relay)

syslogCapability
 sending, receiving (probably as enumerated bits so both = relay)
syslogDefaultSeverity
 unclear of the role of this

syslogMsgsRelayed
 messages received and relayed (excludes messages originating in this process)

syslogConfFileName
 configuration file  - all

plus perhaps, at least for sender,

syslogHostname
syslogAppName
syslogProcId

Tom Petch

<snip>