NOTE: This charter is a snapshot of that in effect at the time of the 38th IETF Meeting in Memphis, Tennessee. It may now be out-of-date.
Chris Wellens <email@example.com>
Llyod Young <firstname.lastname@example.org>
Applications Area Director(s):
Keith Moore <email@example.com>
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>
To Subscribe: firstname.lastname@example.org
Description of Working Group:
The Printer MIB Working Group is chartered to develop a set of managed objects for networked printers. These objects will be the minimum necessary to provide the ability to monitor and control these systems, providing fault, configuration and performance management, and will be consistent with the SNMP framework and existing SNMP standards.
At its discretion, the working group may also define a small number of unsolicited notifications (traps) which carry these managed objects. However, the working group recognizes that traps are used sparingly in the SNMP framework.
The working group recognizes that the area of networked printers is quite diverse. However, the working group is specifically confined to defining managed objects that instrument critical information about:
· Printer engine · Interpreters · Media · Input sources · Output destinations · I/O interfaces
Further, the working group is specifically prohibited from defining managed objects that define instrumentation about:
Other marking technologies (e.g., those that mark onto film): · Fonts · Spooling · Print job managementGoals and Milestones:
Post first Internet-Draft; continue discussion.
Post revised Internet-Draft.
Meet at Seattle IETF to make final review of MIB.
Submit final Internet-Draft to IESG for consideration as a Proposed Standard.
Post Internet-Draft. Solicit implementation experience on RFC1759.
Post revised Internet-Draft.
Meet at Memphis IETF for final MIB review.
Submit Internet-Draft to IESG for consideration as a Draft Standard.
· Printer MIB
Request For Comments:
Minutes of the Printer MIB (PRINTMIB) Working Group
Reported by: Ron Bergman
The meeting was called to order by Lloyd Young at 1:05 PM CST on April 8th at the Peabody Hotel in Memphis, Tennessee. The Printer MIB Working Group is presently developing two printer related MIBs. The first is the Printer MIB and the second is the Job Monitoring MIB.
I. Review of the Printer MIB interoperability testing.
II. Report on status of the Job Monitoring MIB.
The Printer MIB is presently a Proposed Standard and the current efforts are to advance to Draft Standard. One of the prime requirements for advancement to Draft Standard is to demonstrate interoperability. This test was performed in February 1997. A brief report was presented by Lloyd Young as to the test methods and results of these tests. A copy of Interoperability test results was provided to all interested attendees.
1. Static variables were tested using the Castle Rock SNMPc product.
2. Dynamic variables used the Castle Rock SNMPc product for Alerts.
3. Additional testing was performed using the InterWorking Labs MIB Test Suite.
Application testing used: IBM's NetCube, Underscore's Print Alert
Q: Why was Castle Rock's package used instead of OpenView or others?
A: This package was recommend by several of the participating vendors and Castle Rock provides free licenses for the test.
The current schedule for completing the Printer MIB:
· Last comments must be submitted by May 2
· New Internet draft ready for Working Group review by May 16
· Final comments cutoff date is May 30
· Final draft submission to IESG by June 2
II. Job Monitoring MIB:
The current status of the MIB was presented by Tom Hastings. The MIB has been simplified to a total of 13 objects, all of which are mandatory. The emphasis is on a Client - Server - Printer configuration.
The MIB currently contains four groups/tables. No traps are included in the MIB.
· The General group contains 5 objects
· The Job Id group contains 2 objects
· The Job State group contains 4 objects
· Attribute group contains 2 objects
Q: Is this a Job MIB intended for servers in general or just print servers?
A: The MIB is being designed for Printers but other functions such as faxing could use the MIB with extensions.
Q: The Job Monitoring MIB seems to be focusing on some of the same areas as IPP. Is there any coordination between the two projects?A: Yes, the IPP and Job Monitoring programs are both being developed by the same people. The Printer MIB, the Job Monitoring MIB and Internet Printing Protocol projects are being coordinated to insure that they are compatible.
There was an extended discussion on how the client creates the Job Submission ID for the job. The MIB now specifies a Client generated 32 octet Job Submission ID which is really only quasi unique. The Working Group believes that defined methods for this identification string result in an extremely low probability of duplicate strings. There was some concern in the audience that a 100% guarantee of uniqueness must be assured.
Keith Moore expressed concern that SNMP should not be used for a User application. The Working Group is aware that SNMP is not the ideal solution for this problem. Long term IPP will provide a significantly better solution. This is intended to be a solution for current legacy systems.
Q: If the client job can be sent to one of several printers, how do I determine which printer received the job?
A: The Job MIB has two objects: jmPhysicalDeviceName and jmPhysicalDeviceIndex which specify which physical device received the job.
Q: How does the Submission ID get to the printer?
A: The job submission can be either a header or wrapper to the job data or embedded with the PDL of the job. The Working Group believes that the method will be vendor specific and will also be unique to the various hardware / software platforms that are supported.
Steve Zilles commented about the definition of the Attribute Table attributes being Conditionally Mandatory. He was not sure as to the meaning of Conditionally Mandatory in this case. The MIB specification needs to fully define this meaning.
The meeting was closed by Tom Hastings at 3:00 PM CST.