Subject: [ipcdn] Two issues with DOCS-CABLE-DEVICE-TRAP-MIB

From: Mike MacFaden <[email-masked]>
Date: Sat, 03 Mar 2001 22:31:27 -0800

Hi,

It seems to me the the docsDevCmtsTrapControl duplicates
functionality found in SNMP-NOTIFICATION-MIB, RFC 2573.

To reduce some confusion, it would help to add some something
to the DESCRIPTION to specify order of evaluation.

Something like this:

  This object is evaluated before the notificaiton is sent
  through the Notification MIB module if present for a given
  Notification Originator.

Also, would not the term "Event" be less confusing that "Trap" 
in the MIB module and object names?  
Trap implies that this is unacknowledged, and unreliable notification. 
Any one of these "traps" may be configured via notification MIB module to
be sent as Informs via the snmpNotifyType object.

It is just so much fun to explain event/trap/inform to a confused MSO...

Thanks,
Mike MacFaden
www.riverstonenet.com

_______________________________________________
IPCDN mailing list
[email-masked]
http://www1.ietf.org/mailman/listinfo/ipcdn