RE: Syslog Protocol document and Alarm MIB

I personally find a lot of value in the path taken by the syslog
protocol document. Our implementation experience is that a consistent
definition of alarm severities transported by various management
protocols is important in real life deployments, and the ITU perceived
severity as defined in the IETF by the Alarm MIB TC is useful and usable
for most practical purposes.=20

Dan


=20
=20

> -----Original Message-----
> From: Sharon Chisholm [mailto:[email protected]]=20
> Sent: Monday, October 09, 2006 7:20 PM
> To: Wijnen, Bert (Bert); Disman (E-mail) (E-mail)
> Subject: RE: [Disman] Syslog Protocol document and Alarm MIB
>=20
> Hi
>=20
> I actually drafted the initial version of text for this=20
> section, but of course, it would be good to get the views of=20
> the working group itself to ensure it makes sense. After my=20
> initial mapping, there was some working syslog working group=20
> discussion and some modifications were make. The problem is=20
> that a perfect mapping can't be made and so you have to=20
> decide which part of the mapping you are willing to less then ideal.
>=20
> Sharon=20
>=20
> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:[email protected]]
> Sent: Monday, October 09, 2006 7:02 AM
> To: Disman (E-mail) (E-mail)
> Subject: [Disman] Syslog Protocol document and Alarm MIB
>=20
> Since the Alarm MIB was done in this WG, you may want to take=20
> a look at section 6.2.1.1 of document=20
>    draft-ietf-syslog-protocol-17.txt
>=20
> It says:
>=20
>    6.2.1.1.  Relation to Alarm MIB
>=20
>    The Alarm MIB RFC3877 [11] defines ITU perceived=20
> severities which are
>    useful to be able to relate to the syslog severities,=20
> particularly in
>    the case where alarms are being logged.  The ITUPerceivedSeverity
>    corresponds to a syslog Severity as shown in table 2 below.
>=20
>               ITU Perceived Severity      syslog SEVERITY
>               Critical                    Alert
>               Major                       Critical
>               Minor                       Error
>               Warning                     Warning
>               Indeterminate               Notice
>               Cleared                     Notice
>=20
>            Table 3. ITUPerceivedSeverity to syslog SEVERITY mapping.
>=20
> I think this is OK. But wanted to make sure we have all had a=20
> chance to look at it and make a comment if you think it is=20
> not OK. Probably best to then also copy such comment to the=20
> [email protected] mailing list.
>=20
> Bert
>=20
>=20
>=20