IPP> NOT - Lightweight SNMP job traps

IPP> NOT - Lightweight SNMP job traps

IPP> NOT - Lightweight SNMP job traps

McDonald, Ira imcdonald at sharplabs.com
Wed Apr 19 15:41:46 EDT 2000


Hi Ron,

The 'jmDeviceBasicV2Event' trap in the Job Mon MIB
supports the sending of reports, warnings, and
non-critical errors as notifications.

But, the 'printerV2Alert' trap in the Printer MIB
REQUIRES that ONLY critical errors be sent as 
notifications.

The concensus among the implementors of client
tools and network management station plug-ins that
I've talked to is that changing the Printer MIB
alert trap to be sent for other report/warning/
non-critical errors will probably break a LOT
of deployed client-side applications.

Also, the IETF would view it as a redefinition
of the trap and might block publication of Printer
MIB v2 entirely.  Another alternative is to define
a NEW (second) trap in Printer MIB v2 which MAY
be sent for report/warning/non-critical errors.

The other advantages of the 'jmDeviceBasicV2Event':
a) it is generalized to support Scanner, Fax, and
other MFP components (obviously not possible with
the Printer MIB trap);
b) it is independent of the IETF Host Resources MIB 
RFC 2790) Device table.
 
Cheers,
- Ira McDonald, consulting architect at Xerox and Sharp
  High North Inc

-----Original Message-----
From: Ron Bergman [mailto:rbergma at hitachi-hkis.com]
Sent: Wednesday, April 19, 2000 8:33 AM
To: McDonald, Ira
Cc: 'ipp at pwg.org'
Subject: Re: IPP> NOT - Lightweight SNMP job traps


Ira,

This looks like a big improvement, but I need to spend some time
to review in detail to ensure that meets all my requirements.

One other issue that I keep forgetting to ask.  What advantage
do you see that the jmDevice trap provides over the traps that
are currently defined in the Printer MIB?  Is it feasible to extend
the Printer MIB traps to include the events that are defined for
the jmDevice traps?

I may not be able to attend this weeks conference call, at least
at the begining.

    Ron

"McDonald, Ira" wrote:

> Hi folks,                                        Tuesday (18 April 2000)
>
> In response to Ron Bergman's comments on the Job Monitoring MIB traps,
> below is a proposed set of four lightweight traps for discussion at
> tomorrow's IPP Telecon and feedback on the IPP WG mailing list.
>
> Each of these traps has only two string bindings 'jmEventTriggerEvent'
> and 'jmEventDeviceName'.  By sacrificing extensibility (for vendor
> private extensions), we could collapse the 'jmEventTriggerEvent' object
> to an enumeration.
>
> I also replaced the (extensible) string encoded 'jmEventJobStateReasons'
> with the (far more compact) integer encoded 'jmJobStateReasons1'.  I
> propose that the string encoded form be permitted as an OPTIONAL binding
> by the trap DESCRIPTION clauses.
>
> Following the proposed revised traps is the same proposal with the
> deleted original bindings shown as ASN.1 comments.
>
> Following this is the original text of the traps, as specified in
> 'draft-ietf-ipp-not-over-snmp-02.txt'.
>
> Comments?
>
> Cheers,
> - Ira McDonald, consulting architect at Xerox and Sharp
>   High North Inc
>
> ------------------------------------------------------------------------
> [proposed lightweight SNMP traps for IPP events]
>
> jmDeviceBasicV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventDeviceName,
>         jmEventDeviceState,
>         jmEventDeviceStateReasons,
>         jmEventDeviceIsAcceptingJobs
>     }
>
> jmJobBasicV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventDeviceName,
>         jmJobState,                     -- alternate binding
>         jmJobStateReasons1              -- alternate binding
>     }
>
> jmJobCompletedV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventDeviceName,
>         jmJobState,                     -- alternate binding
>         jmJobStateReasons1,             -- alternate binding
>         jmJobKOctetsProcessed,          -- alternate binding
>         jmJobImpressionsCompleted,      -- alternate binding
>         jmEventJobMediaSheetsCompleted
>     }
>
> jmJobProgressV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventDeviceName,
>         jmJobState,                     -- alternate binding
>         jmJobStateReasons1,             -- alternate binding
>         jmJobKOctetsProcessed,          -- alternate binding
>         jmJobImpressionsCompleted,      -- alternate binding
>         jmEventJobMediaSheetsCompleted,
>         jmEventJobImpressionsCompletedCC,
>         jmEventJobCollationType,
>         jmEventJobSheetCompletedCopyNum,
>         jmEventJobSheetCompletedDocNum
>     }
>
> ------------------------------------------------------------------------
> [proposed lightweight SNMP traps for IPP events w/ deleted bindings]
>
> jmDeviceBasicV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
> --      jmEventSubscriptionID,
> --      jmEventSubscriberUserName,
> --      jmEventSubscriberUserData,
> --      jmEventDeviceURI,
>         jmEventDeviceName,
> --      jmEventJobSetIndex,
> --      jmEventJobIndex,
> --      jmEventJobName,
>         jmEventDeviceState,
>         jmEventDeviceStateReasons,
>         jmEventDeviceIsAcceptingJobs
>     }
>
> jmJobBasicV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
> --      jmEventSubscriptionID,
> --      jmEventSubscriberUserName,
> --      jmEventSubscriberUserData,
> --      jmEventDeviceURI,
>         jmEventDeviceName,
> --      jmEventJobSetIndex,
> --      jmEventJobIndex,
> --      jmEventJobName,
> --      jmEventJobState,
>         jmJobState,                     -- alternate binding
> --      jmEventJobStateReasons
>         jmJobStateReasons1              -- alternate binding
>     }
>
> jmJobCompletedV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
> --      jmEventSubscriptionID,
> --      jmEventSubscriberUserName,
> --      jmEventSubscriberUserData,
> --      jmEventDeviceURI,
>         jmEventDeviceName,
> --      jmEventJobSetIndex,
> --      jmEventJobIndex,
> --      jmEventJobName,
> --      jmEventJobState,
>         jmJobState,                     -- alternate binding
> --      jmEventJobStateReasons,
>         jmJobStateReasons1,             -- alternate binding
> --      jmEventJobKOctetsProcessed,
>         jmJobKOctetsProcessed,          -- alternate binding
> --      jmEventJobImpressionsCompleted,
>         jmJobImpressionsCompleted,      -- alternate binding
>         jmEventJobMediaSheetsCompleted
>     }
>
> jmJobProgressV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
> --      jmEventSubscriptionID,
> --      jmEventSubscriberUserName,
> --      jmEventSubscriberUserData,
> --      jmEventDeviceURI,
>         jmEventDeviceName,
> --      jmEventJobSetIndex,
> --      jmEventJobIndex,
> --      jmEventJobName,
> --      jmEventJobState,
>         jmJobState,                     -- alternate binding
> --      jmEventJobStateReasons,
>         jmJobStateReasons1,             -- alternate binding
> --      jmEventJobKOctetsProcessed,
>         jmJobKOctetsProcessed,          -- alternate binding
> --      jmEventJobImpressionsCompleted,
>         jmJobImpressionsCompleted,      -- alternate binding
>         jmEventJobMediaSheetsCompleted,
>         jmEventJobImpressionsCompletedCC,
>         jmEventJobCollationType,
>         jmEventJobSheetCompletedCopyNum,
>         jmEventJobSheetCompletedDocNum
>     }
>
> ------------------------------------------------------------------------
> [excerpt from 'draft-ietf-ipp-not-over-snmp-02.txt']
>
> jmDeviceBasicV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventSubscriptionID,
>         jmEventSubscriberUserName,
>         jmEventSubscriberUserData,
>         jmEventDeviceURI,
>         jmEventDeviceName,
>         jmEventJobSetIndex,
>         jmEventJobIndex,
>         jmEventJobName,
>         jmEventDeviceState,
>         jmEventDeviceStateReasons,
>         jmEventDeviceIsAcceptingJobs
>     }
>
> jmJobBasicV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventSubscriptionID,
>         jmEventSubscriberUserName,
>         jmEventSubscriberUserData,
>         jmEventDeviceURI,
>         jmEventDeviceName,
>         jmEventJobSetIndex,
>         jmEventJobIndex,
>         jmEventJobName,
>         jmEventJobState,
>         jmEventJobStateReasons
>     }
>
> jmJobCompletedV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventSubscriptionID,
>         jmEventSubscriberUserName,
>         jmEventSubscriberUserData,
>         jmEventDeviceURI,
>         jmEventDeviceName,
>         jmEventJobSetIndex,
>         jmEventJobIndex,
>         jmEventJobName,
>         jmEventJobState,
>         jmEventJobStateReasons,
>         jmEventJobKOctetsProcessed,
>         jmEventJobImpressionsCompleted,
>         jmEventJobMediaSheetsCompleted
>     }
>
> jmJobProgressV2Event NOTIFICATION-TYPE
>     OBJECTS {
>         jmEventTriggerEvent,
>         jmEventSubscriptionID,
>         jmEventSubscriberUserName,
>         jmEventSubscriberUserData,
>         jmEventDeviceURI,
>         jmEventDeviceName,
>         jmEventJobSetIndex,
>         jmEventJobIndex,
>         jmEventJobName,
>         jmEventJobState,
>         jmEventJobStateReasons,
>         jmEventJobKOctetsProcessed,
>         jmEventJobImpressionsCompleted,
>         jmEventJobMediaSheetsCompleted,
>         jmEventJobImpressionsCompletedCC,
>         jmEventJobCollationType,
>         jmEventJobSheetCompletedCopyNum,
>         jmEventJobSheetCompletedDocNum
>     }
>
> ------------------------------------------------------------------------



More information about the Ipp mailing list