[Syslog] WGLC: draft-ietf-syslog-tc-mib-02

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

Hi,

Please append the following paragraphs to section 2 "Background", and
please add these paragraphs to the comment text in the MIB itself that
describe "Textual Conventions". A reference should be added in the
section 2 text for the APPNAME SDE with a pointer to the protocol
document.

"For interoperability and backwards compatibility reasons, the values
and 
labels are normative, so the mapping from a label configured by
operators 
in syslog.conf or equivalent consistently maps to the same Facility
number 
regardless of implementation, but the label itself is often
semantically 
meaningless, because there are not enough numbers to cover all
possible 
facilities, and the enumeration (label and value) that is used by an 
actual facility is, and has historically been,
implementation-dependent.

For example, the foobar application might log messages as having come
from 
local7, even though there is no "local" process on the device, and the

operator can configure syslog.conf to have local7.critical messages be

relayed, even though there might be multiple facilities using Facility

local7.  This is typical current practice, and originators, relays and

collectors know how to handle this situation.  For improved accuracy,
the 
foobar application can also include an APPNAME SDE in the message 
identifying itself as the "foobar" application."

Thanks,
David Harrington
dbharrington at comcast.net
ietfdbh at comcast.net



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