Hi,
Juergen Schoenwaelder wrote:
> On Fri, Jun 01, 2007 at 03:06:46PM -0400, David Harrington wrote:
>
>> I would like to do a poll:
>>
>> 1) Should these textual conventions be accepted as they are?
>
> I am fine with the *nix biased values since this is where syslog is
> coming from and extremely widely deployed. However, I have no clue
> what noMap(99) is nor do I understand any of the words after the first
> sentence in the DESCRIPTION clause of SyslogFacility.
Oops. That is a legacy of the parent MIB document where it was possible
to set the defaultSyslogFacility. This is irrelevant in the present
document and will be removed.
The description will read
DESCRIPTION
"This textual convention enumerates the facilities
that originate syslog messages.
"
>
>> 2) Would this WG like to see us define a normative set or a
>> non-normative set of facilities and severities?
>
> Are you opening up section 6.2.1 of <draft-ietf-syslog-protocol-20.txt>?
> Why not use the same "creative wordings" for this ID also in the MIB?
> This makes things consistent (and perhaps leads to a de-facto standard).
> Or is the proposal to make the TC document purely Informational?
OK. I propose to replace the opening comments by text like
-- The Facilities and Severities of syslog messages are
-- numerically coded with decimal values.
-- Facility and Severity values are not normative but often used.
-- Some of the operating system daemons and processes are traditionally
-- designated by the Facility values given below.
-- Daemons and processes that do not that have an explicitly
-- assigned a Facility may use any of the "local use" facilities
-- or they may use the "user-level" Facility.
I also propose that we delete the reference to section 6.2.1 of
<draft-ietf-syslog-protocol-20.txt>.
>
>> 3) Whether normative or non-normative, which is more important?
>> efficient allocation of the limited facility values, or backwards
>> compatibility with existing (and historic) implementations?
>
> I assume compatibility; otherwise the protocol design could have used
> a very different format and enlarged the number spaces.
>
> /js
Glenn
>
> PS: I am a long time Unix user and somewhat biased. ;-)
>
_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog
