Hi Harry,
The Job Monitoring MIB is a PWG Standard (and is
published an an IETF Informational RFC for the
convenience of the network management community).
The Job object in IPP (developed AFTER the Job
Mon MIB) was intentionally technically aligned
with the Job attributes in the Job Mon MIB.
The Job Mon MIB is intended to be used to instrument
jobs from ANY print channel (IPP, LPR, etc.) in
ANY print format (PostScript, etc.). It is a
companion to the Printer MIB.
The work-in-progress (mine) to add Service (Printer)
and Job SNMP traps to the Job Mon MIB was inspired
by the notifications work item in the IETF IPP WG
(and is an OPTIONAL mapping for IPP notifications).
Because of further changes in the IPP notifications
base spec, I'm revising the Job traps spec once more.
Should be posted (to this list) within the next few
weeks.
I hope this helps.
Cheers,
- Ira McDonald, consulting architect at Xerox and Sharp
High North Inc
-----Original Message-----
From: Harry Offermans [mailto:hof@oce.nl]
Sent: Thursday, August 03, 2000 6:59 AM
To: jmp@pwg.org
Subject: JMP> status and usage of Job monitoring MIB
The status of teh Job monitoring MIB is informational and the location
in the MIB tree is private/enterprises/oid_pwg/oi_mibs. The question I
have is, if the Job Monitoring MIB is, will be or is intended to be
used for job managament applications. The usage I think of is in the
same way as the Printer MIB or MIB II. Or is the purpose to have a job
description that can be used in IPP. ??
-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0
Harry Offermans OCE Research & Development
mailto: hof@oce.nl Tel: +31 77 359 3198 Fax: +31 77 359 5473
Address: OCE Technologies/PO BOX 101/5900 MA Venlo/The Netherlands
------------------------------------------------------------------
This note does not necessarily represent the position of Oce
Technologies B.V. Therefore no liability or responsibility for
whatever will be accepted.
------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Thu Aug 03 2000 - 11:35:03 EDT