draft-ietf-syslog-device-mib-00.txt - Enums starting at zero

[Joan Cucchiara <jcucchia@CrescentNetworks.com>]

Hi Folks,

My question is about what the current practice is
for starting enums at zero when there is a reason 
for starting at zero.

Specifically in this MIB, there is an enum:

SyslogSeverity  ::=  TEXTUAL-CONVENTION
    STATUS  current
    DESCRIPTION
        "This textual convention maps out to the severity levels
         of syslog messages.  The syslog protocol uses the values
         0 (emergency), to 7 (debug)."
    SYNTAX  INTEGER {
                      emergency(1),
                      alert(2),
                      critical(3),
                      error(4),
                      warning(5),
                      notice(6),
                      info(7),
                      debug(8)
                    }


and rfc3164.txt which is The BSD syslog Protocol and is
the RFC upon which the MIB is based has:
 
           0       Emergency: system is unusable
           1       Alert: action must be taken immediately
           2       Critical: critical conditions
           3       Error: error conditions
           4       Warning: warning conditions
           5       Notice: normal but significant condition
           6       Informational: informational messages
           7       Debug: debug-level messages

At one point having enums start at zero in SMIv2 was 
not encouraged due to backwards compatibility with SMIv1,
but am wondering if this is still the case? 

  thanks, Joan