Re: [OPSAWG] my initial review of draft-schoenw-syslog-msg-mib-00.txt

Hi,

The discussion of truncation follows the syslog WG's protocol I-D.
I am not certain that it is necessary to state here that the trucation
might lead to incomplete UTF-8 characters, but it would probably be
more helpful than harmful. You might want to include a REFERENCE.

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

> -----Original Message-----
> From: opsawg-bounces@ietf.org 
> [mailto:opsawg-bounces@ietf.org] On Behalf Of Bert Wijnen - IETF
> Sent: Friday, May 02, 2008 9:41 AM
> To: j.schoenwaelder@jacobs-university.de; sob@harvard.edu; 
> ted.a.seely@sprint.com
> Cc: opsawg@ietf.org
> Subject: [OPSAWG] my initial review of 
> draft-schoenw-syslog-msg-mib-00.txt
> 
> In general I think a MIB module like this one makes sense and
> will be usefull.
> 
> Some comments:
> 
> - I see 2 writable objects at the beginning of the MIB module.
>   But it is unclear what the expected persistency behaviour is.
> 
> - Would it not be easier to use SnmpAdminString instead of
>   DisplayString? Do we never expect any of these fields to
>   contain Internationlized names?
> 
> - WHen I see:
>          If the first octets contain the value 'EFBBBF'h, 
> then the rest
>          of the message is a UTF-8 string. Since syslog 
> messages may be
>          truncated, the message may contain invalid UTF-8 encodings
at
>          the end."
>   I wonder if it would not be better to truncate in such a way that
>   message allways contains valid UTF-8 encodings.
>   What was/is your motivation to not do that?
> 
> - I find these somewhat weird:
>       MIN-ACCESS  accessible-for-notify
>       DESCRIPTION
>           "Read write access is not required."
> 
>   The MAX-ACCESS for this (and other) objects is read-only.
>   So the DESCRIPTION clause seems bogus.
>   I guess you mean that one does not need to support READ
> (GET/HETNEXT/GETBULK)
>   access. You have several of those.
> 
> NITs/TYPOs
> 
> - second para sect 1:
> 
>    This document defines an SNMP MIB modules to represent SYSLOG
> 
>   I guess you want to s/modules/module/
> 
> - page 9
> 
>           For syslog messages without structured data element 
> parameters
>           that were not truncted by the converter, none of the bits
is
>           set."
> 
>   s/truncted/truncated/
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg