]> git.ipfire.org Git - thirdparty/cups.git/blame - standards/rfc3805.txt
projects / thirdparty / cups.git / blame
? search:
summary | shortlog | log | commit | commitdiff | tree
blob | blame (incremental) | history | HEAD
Merge changes from CUPS 1.5rc1-r9834.
[thirdparty/cups.git] / standards / rfc3805.txt
CommitLineData
a74454a7 1
2
3
4
5
6
7Network Working Group R. Bergman
8Request for Comments: 3805 Hitachi Printing Solutions
9Obsoletes: 1759 H. Lewis
10Category: Standards Track IBM Corporation
11 I. McDonald
12 High North Inc.
13 June 2004
14
15
16 Printer MIB v2
17
18Status of this Memo
19
20 This document specifies an Internet standards track protocol for the
21 Internet community, and requests discussion and suggestions for
22 improvements. Please refer to the current edition of the "Internet
23 Official Protocol Standards" (STD 1) for the standardization state
24 and status of this protocol. Distribution of this memo is unlimited.
25
26Copyright Notice
27
28 Copyright (C) The Internet Society (2004).
29
30Abstract
31
32 This document provides definitions of models and manageable objects
33 for printing environments. The objects included in this MIB apply to
34 physical, as well as logical entities within a printing device. This
35 document obsoletes RFC 1759.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58Bergman, et al. Standards Track [Page 1]
59\f
60RFC 3805 Printer MIB v2 June 2004
61
62
63Table of Contents
64
65 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 4
66 1.1. Network Printing Environment. . . . . . . . . . . . . . 4
67 1.2. Printer Device Overview . . . . . . . . . . . . . . . . 6
68 1.3. Categories of Printer Information . . . . . . . . . . . 6
69 1.3.1. Descriptions. . . . . . . . . . . . . . . . . . 6
70 1.3.2. Status. . . . . . . . . . . . . . . . . . . . . 6
71 1.3.3. Alerts. . . . . . . . . . . . . . . . . . . . . 6
72 1.4. The Internet-Standard Management Framework. . . . . . . 7
73 1.5. Requirement Levels. . . . . . . . . . . . . . . . . . . 7
74 2. Printer Model . . . . . . . . . . . . . . . . . . . . . . . . 8
75 2.1. Overview of the Printer Model . . . . . . . . . . . . . 10
76 2.2. Printer Sub-Units . . . . . . . . . . . . . . . . . . . 10
77 2.2.1. General Printer . . . . . . . . . . . . . . . . 10
78 2.2.1.1. International Considerations. . . . . 10
79 2.2.2. Inputs. . . . . . . . . . . . . . . . . . . . . 11
80 2.2.3. Media . . . . . . . . . . . . . . . . . . . . . 12
81 2.2.4. Outputs . . . . . . . . . . . . . . . . . . . . 12
82 2.2.5. Finishers . . . . . . . . . . . . . . . . . . . 12
83 2.2.6. Markers . . . . . . . . . . . . . . . . . . . . 13
84 2.2.7. Media Paths . . . . . . . . . . . . . . . . . . 13
85 2.2.8. System Controller . . . . . . . . . . . . . . . 14
86 2.2.9. Interfaces. . . . . . . . . . . . . . . . . . . 14
87 2.2.10. Print Job Delivery Channels . . . . . . . . . . 14
88 2.2.11. Interpreters. . . . . . . . . . . . . . . . . . 15
89 2.2.12. Console . . . . . . . . . . . . . . . . . . . . 15
90 2.2.13. Alerts. . . . . . . . . . . . . . . . . . . . . 15
91 2.2.13.1. Status and Alerts . . . . . . . . . . 16
92 2.2.13.2. Overall Printer Status. . . . . . . . 16
93 2.2.13.2.1. Host Resources MIB
94 Printer Status. . . . . . 18
95 2.2.13.2.2. Sub-unit Status . . . . . 20
96 2.2.13.3. Alert Tables. . . . . . . . . . . . . 21
97 2.2.13.4. Alert Table Management. . . . . . . . 21
98 2.3. Read-Write Objects. . . . . . . . . . . . . . . . . . . 23
99 2.4. Enumerations. . . . . . . . . . . . . . . . . . . . . . 24
100 2.4.1. Registering Additional Enumerated Values. . . . 25
101 3. Groups from other MIB Specifications. . . . . . . . . . . . . 25
102 3.1. System Group. . . . . . . . . . . . . . . . . . . . . . 25
103 3.2. System Controller . . . . . . . . . . . . . . . . . . . 25
104 3.3. Interface Group objects . . . . . . . . . . . . . . . . 26
105 3.3.1. Interface Types . . . . . . . . . . . . . . . . 26
106 4. Differences from RFC 1759 . . . . . . . . . . . . . . . . . . 26
107 5. The IANA Printer MIB. . . . . . . . . . . . . . . . . . . . . 29
108 6. The Printer MIB . . . . . . . . . . . . . . . . . . . . . . . 56
109 -- Textual conventions for this MIB module. . . . . . . . . . 59
110 -- The General Printer Group. . . . . . . . . . . . . . . . . 67
111
112
113
114Bergman, et al. Standards Track [Page 2]
115\f
116RFC 3805 Printer MIB v2 June 2004
117
118
119 -- The Responsible Party group. . . . . . . . . . . . . . . . 70
120 -- The Auxiliary Sheet Group. . . . . . . . . . . . . . . . . 73
121 -- Administrative section (The General V2 Group) . . . . . . 74
122 -- General alert table section (Alert Table V2 Group). . . . 74
123 -- The Cover Table. . . . . . . . . . . . . . . . . . . . . . 75
124 -- The Localization Table . . . . . . . . . . . . . . . . . . 76
125 -- The System Resources Tables. . . . . . . . . . . . . . . . 78
126 -- The Input Group. . . . . . . . . . . . . . . . . . . . . . 81
127 -- The Extended Input Group . . . . . . . . . . . . . . . . . 86
128 -- The Input Media Group. . . . . . . . . . . . . . . . . . . 87
129 -- The Input Switching Group. . . . . . . . . . . . . . . . . 89
130 -- The Output Group . . . . . . . . . . . . . . . . . . . . . 90
131 -- The Extended Output Group. . . . . . . . . . . . . . . . . 93
132 -- The Output Dimensions Group. . . . . . . . . . . . . . . . 95
133 -- The Output Features Group. . . . . . . . . . . . . . . . . 97
134 -- The Marker Group . . . . . . . . . . . . . . . . . . . . . 98
135 -- The Marker Supplies Group. . . . . . . . . . . . . . . . . 104
136 -- The Marker Colorant Group. . . . . . . . . . . . . . . . . 107
137 -- The Media Path Group . . . . . . . . . . . . . . . . . . . 109
138 -- The Print Job Delivery Channel Group . . . . . . . . . . . 113
139 -- The Interpreter Group. . . . . . . . . . . . . . . . . . . 115
140 -- The Console Group. . . . . . . . . . . . . . . . . . . . . 120
141 -- The Alerts Group . . . . . . . . . . . . . . . . . . . . . 125
142 -- Conformance Information. . . . . . . . . . . . . . . . . . 129
143 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 147
144 8. Internationalization Considerations . . . . . . . . . . . . . 147
145 9. Security Considerations . . . . . . . . . . . . . . . . . . . 148
146 10. References. . . . . . . . . . . . . . . . . . . . . . . . . . 150
147 10.1. Normative References. . . . . . . . . . . . . . . . . . 150
148 10.2. Informative References. . . . . . . . . . . . . . . . . 151
149 Appendix A - Glossary of Terms. . . . . . . . . . . . . . . . . . 153
150 Appendix B - Media Size Names . . . . . . . . . . . . . . . . . . 156
151 Appendix C - Media Names. . . . . . . . . . . . . . . . . . . . . 158
152 Appendix D - Roles of Users . . . . . . . . . . . . . . . . . . . 162
153 Appendix E - Overall Printer Status Table . . . . . . . . . . . . 165
154 Appendix F - Participants . . . . . . . . . . . . . . . . . . . . 166
155 Significant Contributors. . . . . . . . . . . . . . . . . . . . . 168
156 Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . . 170
157 Full Copyright Statement. . . . . . . . . . . . . . . . . . . . . 171
158
159
160
161
162
163
164
165
166
167
168
169
170Bergman, et al. Standards Track [Page 3]
171\f
172RFC 3805 Printer MIB v2 June 2004
173
174
1751. Introduction
176
1771.1. Network Printing Environment
178
179 The management of producing a printed document, in any computer
180 environment, is a complex subject. Basically, the task can be
181 divided into two overlapping pieces, the management of printing and
182 the management of the printer. Printing encompasses the entire
183 process of producing a printed document from generation of the file
184 to be printed, selection of a printer, choosing printing properties,
185 routing, queuing, resource management, scheduling, and final printing
186 including notifying the user. Most of the printing process is
187 outside the scope of the model presented here; only the management of
188 the printer is covered.
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226Bergman, et al. Standards Track [Page 4]
227\f
228RFC 3805 Printer MIB v2 June 2004
229
230
231 Figure 1 - One Printer's View of the Network
232
233 system printer asset user user user
234 manager operator manager
235 O O O O O O
236 /|\ /|\ /|\ /|\ /|\ /|\
237 / \ / \ / \ / \ / \ / \
238 | | | | | |
239+---------+ +-------+ +-------+ +-------+ +-----------+ +-----------+
240|configur-| |printer| | asset | |printer| | user | | user |
241|ator | |manager| |manager| |browser| |application| |application|
242+---------+ +-------+ +-------+ +-------+ +-----------+ +-----------+
243 ^ ^ ^ ^ | |
244 |R/W |R/W |R |R +-----------+ +-----------+
245 | | | | | spooler | | spooler |
246 | | | | +-----------+ +-----------+
247 | | | | | |
248 | | | | +-----------+ +-----------+
249 | | | | |supervisor | |supervisor |
250 | | | | +-----------+ +-----------+
251 | | | | ^ ^ ^ ^
252 | | | | |R |R/W |R |R/W
253 v v | | | | | |
254================================================== | ===== |
255 | print| print|
256 |SNMP data| data|
257 +-----+ +-------+ PCL| PCL|
258 | MIB |<------>| agent | PostScript| PostScript|
259 +-----+ +-------+ NPAP| NPAP|
260 |unspecified etc.| etc.|
261 +=============+ +-----------------+ | |
262 | |--|channel/interface|<--+ |
263 | | +-----------------+ |
264 | PRINTER | |
265 | | +-----------------+ |
266 | |--|channel/interface|<----------------+
267 +=============+ +-----------------+
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282Bergman, et al. Standards Track [Page 5]
283\f
284RFC 3805 Printer MIB v2 June 2004
285
286
2871.2. Printer Device Overview
288
289 A printer is the physical device that takes media from an input
290 source, produces marks on that media according to some page
291 description or page control language and puts the result in some
292 output destination, possibly with finishing applied. Printers are
293 complex devices that consume supplies, produce waste and may have
294 mechanical problems. In the management of the physical device the
295 description, status and alert information concerning the printer and
296 its various subparts has to be made available to the management
297 application so that it can be reported to the end user, key operators
298 for the replenishment of supplies or the repair or maintenance of the
299 device. The information needed in the management of the physical
300 printer and the management of a printing job overlap highly and many
301 of the tasks in each management area require the same or similar
302 information.
303
3041.3. Categories of Printer Information
305
306 Information about printers is classified into three basic categories:
307 descriptions, status and alerts.
308
3091.3.1. Descriptions
310
311 Descriptions convey information about the configuration and
312 capabilities of the printer and its various sub-units. This
313 information is largely static information and does not generally
314 change during the operation of the system but may change as the
315 printer is repaired, reconfigured or upgraded. The descriptions are
316 one part of the visible state of the printer where state means the
317 condition of being of the printer at any point in time.
318
3191.3.2. Status
320
321 Status is the information regarding the current operating state of
322 the printer and its various sub-units. As an example of the use of
323 status, a management application must be able to determine if the
324 various sub-units are ready to print or are in some state that
325 prevents printing or may prevent printing in the future.
326
3271.3.3. Alerts
328
329 An Alert is the representation of a reportable event in the printer.
330 An event is a change in the state of the printer. Some of those
331 state changes are of interest to a management application and are
332 therefore reportable. Typically, these are the events that affect
333 the printer's ability to print. Alerts usually occur asynchronously
334 to the operation of the computer system(s) to which the printer is
335
336
337
338Bergman, et al. Standards Track [Page 6]
339\f
340RFC 3805 Printer MIB v2 June 2004
341
342
343 attached. For convenience below, "alert" will be used for both the
344 event caused by a change in the printer's state and for the
345 representation of that event.
346
347 Alerts can be classified into two basic categories, critical and non-
348 critical. A critical alert is one that is triggered by entry into a
349 state in which the printer is stopped and printing can not continue
350 until the condition that caused the critical alert is eliminated.
351 "Out of paper", "toner empty" and "output bin full" are examples of
352 critical alerts. Non-critical alerts are triggered by those events
353 that enter a state in which printing is not stopped. Such a non-
354 critical state may, at some future time, lead to a state in which
355 printing may be stopped. Examples of these kinds of non-critical
356 alerts are "input media low", "toner low" and "output bin nearly
357 full". Or, a non-critical alert may simply provide information, such
358 as signaling a configuration changed in the printer.
359
360 Description, status and alert information about the printer can be
361 thought of as a database describing the printer. The management
362 application for a printer will want to view the printer data base
363 differently depending on how and for what purposes the information in
364 the database is needed.
365
3661.4. The Internet-Standard Management Framework
367
368 For a detailed overview of the documents that describe the current
369 Internet-Standard Management Framework, please refer to section 7 of
370 RFC 3410 [RFC3410].
371
372 Managed objects are accessed via a virtual information store, termed
373 the Management Information Base or MIB. MIB objects are generally
374 accessed through the Simple Network Management Protocol (SNMP).
375 Objects in the MIB are defined using the mechanisms defined in the
376 Structure of Management Information (SMI). This memo specifies a MIB
377 module that is compliant to the SMIv2, which is described in STD 58,
378 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
379 [RFC2580].
380
3811.5. Requirement Levels
382
383 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
384 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
385 document are to be interpreted as described in [RFC2119].
386
387 Compliant implementations must follow this specification.
388
389
390
391
392
393
394Bergman, et al. Standards Track [Page 7]
395\f
396RFC 3805 Printer MIB v2 June 2004
397
398
3992. Printer Model
400
401 In order to accomplish the management of the printer, an abstract
402 model of the printer is needed to represent the sub-units from which
403 the printer is composed. A printer can be described as consisting of
404 13 types of sub-units. It is important to note that the sub-units of
405 a printer do not necessarily relate directly to any physically
406 identifiable mechanism. Sub-units can also be a set of definable
407 logical processes, such as interpreters for page description
408 languages or command processors that set various operating modes of
409 the printer.
410
411 Figure 2 shows a block diagram of the printer and its basic 13 sub-
412 units.
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450Bergman, et al. Standards Track [Page 8]
451\f
452RFC 3805 Printer MIB v2 June 2004
453
454
455 Figure 2 - Printer Block Diagram
456
457 Physical Connections
458 |
459 +-----------+
460 | |
461 +-------------+ |
462 | Interface |-+
463 | MIB-II |
464 +-------------+
465 |
466 +-----------+
467 | |
468 +-------------+ | +-----------+
469 | Channel |-+ | Operator |
470 | | | Console |
471 +-------------+ +-----------+
472 |
473 +-----------+ +---------+
474 | | | |
475 +-----------+ +-------------+ | +-----------+ |
476 | General | | Interpreter |-+ | Alerts |-+
477 | Printer | | | | |
478 +-----------+ +-------------+ +-----------+
479 |
480 +-------------------------------+
481 | System Controller |
482 | HOST-RESOURCES-MIB |
483 +-------------------------------+
484
485 +------+ +--------+ +--------+
486 | | | | | |
487+-------+ | +-------+ +---------+ | +-------+ +--------+ |
488| Input |-+ +--------+| | Marker |-+ +--------+| | Output |-+
489| |===>| |+<==>| |<==>| |+==>| |
490+-------+ +--+ +--+ +---------+ +--+ +--+ +--------+
491 \ | || | || \
492 \ | || | || \
493 \ | || | || \
494 +--------+ | |+-------------------------| || +---------+
495 | | | +--------------------------+ || | |
496+----------+ | | Media Path |+ +----------+ |
497| Media |-+ +--------------------------------+ | Finisher |-+
498|(optional)| |(optional)|
499+----------+ +----------+
500
501
502
503
504
505
506Bergman, et al. Standards Track [Page 9]
507\f
508RFC 3805 Printer MIB v2 June 2004
509
510
5112.1. Overview of the Printer Model
512
513 The model has three basic parts: (1) the flow of a print file into an
514 interpreter and onto the marker, (2) the flow of media through the
515 marker and (3) the auxiliary sub-units that control and facilitate
516 the two prior flows. The flow of the print data comes through a
517 physical connection on which some form of transport protocol stack is
518 running. The data provided by the transport protocol (interface)
519 appears on a channel, which is the input to an interpreter. The
520 interpreter converts the print data into a form suitable for marking
521 on the media.
522
523 The media resides in Input sub-units from which the media is selected
524 and then transported via a Media Path first to a Marking sub-unit and
525 then onto an Output sub-unit with (optionally) some finishing
526 operations being performed. The auxiliary sub-units facilitate
527 control of the printer, inquiry/control of the operator panel,
528 reporting of alerts and the adaptation of the printer to various
529 natural languages and characters sets. All the software sub-units
530 run on the System Controller that represents the processor, memory
531 and storage systems of the Printer. Each of the sub-units is
532 discussed in more detail below.
533
534 All of the sub-units other than the Alerts report only state
535 information, either a description or a status. The Alerts sub-unit
536 reports event information.
537
5382.2. Printer Sub-Units
539
540 A printer is composed of 13 types of sub-units, called groups. The
541 following sections describe the different types of sub-units.
542
5432.2.1. General Printer
544
545 The general printer sub-unit is responsible for the overall control
546 and status of the printer. There is exactly one general printer sub-
547 unit in a printer. The General Printer Group in the model represents
548 the general printer sub-unit. In addition to the providing the
549 status of the whole printer and allowing the printer to be reset,
550 this Group provides information on the status of the packaging of the
551 printer, in particular, the covers. The general printer sub-unit is
552 usually implemented on the system controller.
553
5542.2.1.1. International Considerations
555
556 The localization portion of the general printer sub-unit is
557 responsible for identifying the natural language, country, and
558 character set in which certain character strings are expressed in
559
560
561
562Bergman, et al. Standards Track [Page 10]
563\f
564RFC 3805 Printer MIB v2 June 2004
565
566
567 this MIB. Character sets are identified in this MIB using the
568 IANACharset textual convention imported from the IANA Character Set
569 MIB [CHARMIB].
570
571 There may be one or more localizations supported per printer. The
572 available localizations are specified in the Localization table.
573 Localization SHOULD only be performed on string objects which are
574 named 'xxxDescription' (sub-unit descriptions) or
575 'prtConsoleDisplayBufferText' (local console text).
576
577 The agent SHALL return all other character strings in coded character
578 sets in which code positions 0-127 (decimal) are US-ASCII [ASCII].
579 The agent SHOULD return all other character strings in the UTF-8
580 [RFC3629] transform of ISO 10646 [ISO10646], to conform with the IETF
581 Policy on Character Sets and Languages [RFC2277]. Control codes
582 (code positions 0-31 and 127 decimal) SHALL NOT be used unless
583 specifically required in the DESCRIPTION of an object.
584
585 The character set portion of the general printer Localization table
586 is responsible for identifying the possible character sets for the
587 operator console, and network management requests for display
588 objects. There may be one or more character sets per printer.
589 Default coded character sets for interpreter unit and output octets
590 are described in the interpreter sub-unit by
591 prtInterpreterDefaultCharSetIn and prtInterpreterDefaultCharSetOut.
592 These input/output character sets may be overridden by commands in
593 the interpreter language itself.
594
5952.2.2. Inputs
596
597 Input sub-units are mechanisms that feed media to be marked on into
598 the printer. A printer contains one or more input sub-units. The
599 Input Group in the model represents these. The model does not
600 distinguish fixed input bins from removable trays, except to report
601 when a removable tray has been removed.
602
603 There are as many input sub-units as there are distinctly selectable
604 input "addresses". For example, if one tray has both a manual and
605 auto feeding option, then this is two input sub-units if these two
606 sources can be (must be) separately selected. However, the above
607 would be considered one input sub-unit if putting a sheet in the
608 manual feed slot overrides feeding from the contents of the tray. In
609 the second case there is no way to separately select or address the
610 manual feed slot.
611
612
613
614
615
616
617
618Bergman, et al. Standards Track [Page 11]
619\f
620RFC 3805 Printer MIB v2 June 2004
621
622
6232.2.3. Media
624
625 An input sub-unit can hold one or more instances of the media on
626 which marking is to be done. Typically, there is a large set of
627 possible media that can be associated with an input. The Media Group
628 is an extension of the Input Group, which represents media in an
629 input sub-unit. The Media Group only describes the current contents
630 of each input and not the possible content of the input sub-unit.
631
6322.2.4. Outputs
633
634 Output sub-units are mechanisms that receive media that has been
635 marked on. The Output Group in the model represents the one or more
636 output mechanisms contained by a printer. The model does not
637 distinguish fixed output bins from removable output bins, except to
638 report when a removable bin has been removed.
639
640 There are as many output sub-units as there are distinctly selectable
641 output "addresses". Output sub-units can be addressed in two
642 different ways: (1) as a set of "mailboxes" which are addressed by a
643 specific mailbox selector such as a bin number or a bin name, or (2)
644 as a set of "slots" into which multiple copies are collated.
645 Sometimes both modes of using the output sub-units can be used on the
646 same printer. All that is important from the viewpoint of the model
647 is that the output units can be separately selected.
648
6492.2.5. Finishers
650
651 A finisher is a sub-unit that performs some operations on the media
652 other than marking. The Finisher Group in the model represents the
653 finisher sub-units. Some examples of finishing processes are
654 stapling, punching, binding, inserting, or folding. Finishing
655 processes may have supplies associated with the process. Stapling,
656 binding, and punching are examples of processes that have supplies.
657 A printer may have more than one finishing sub-unit and each
658 finishing sub-unit may be associated with one or more output sub-
659 units. Finishers are described in the companion Finisher MIB
660 [RFC3806].
661
662 The model does not specify the exact interaction and sequencing
663 between an output device and its associated finisher. It depends on
664 the type of finishing process and the exact implementation of the
665 printer system. This standard allows for the logical association of
666 a finishing process with an output device but does not put any
667 restrictions on the exact sequence or interaction with the associated
668 output device. The output and finisher sub-units may or may not be
669 separate identifiable physical mechanisms depending on the exact
670
671
672
673
674Bergman, et al. Standards Track [Page 12]
675\f
676RFC 3805 Printer MIB v2 June 2004
677
678
679 implementation of a printer. In addition, a single output device may
680 be associated with multiple finishing sub-units and a single
681 finishing sub-unit may be associated with multiple output devices.
682
6832.2.6. Markers
684
685 A marker is the mechanism that produces marks on the print media.
686 The Marker Group in the model represents the marker sub-units and
687 their associated supplies. A printer can contain one or more marking
688 mechanisms. Some examples of multiple marker sub-units are a printer
689 with separate markers for normal and magnetic ink or an image setter
690 that can output to both a proofing device and final film. Each
691 marking device can have its own set of characteristics associated
692 with it, such as marking technology and resolution.
693
694 In this model the marker sub-unit is viewed as very generalized and
695 encompasses all aspects of a marking process. For example, in a
696 xerographic process, the marking process as well as the fusing
697 process would be included in the generalized concept of the marker.
698 With the generalized concept of a marking process, the concept of
699 multiple marking supplies associated with a single marking sub-unit
700 results. For example, in the xerographic process, there is not only
701 a supply of toner, but there can also be other supplies such as a
702 fuser supply (e.g., fuser oil) that can be consumed and replaced
703 separately. In addition there can be multiple supplies of toner for
704 a single marker device, as in a color process.
705
7062.2.7. Media Paths
707
708 The media paths encompass the mechanisms in the printer that move the
709 media through the printer and connect all other media related sub-
710 units: inputs, outputs, markers and finishers. A printer contains
711 one or more media paths. The Media Path Group in the model
712 represents these. The Media Path group has some objects that apply
713 to all paths plus a table of the separate media paths.
714
715 In general, the design of the media paths determines the maximum
716 speed of the printer as well as the maximum media size that the
717 printer can handle. Media paths are complex mechanisms and can
718 contain many different identifiable sub-mechanisms such as media
719 movement devices, media buffers, duplex units and interlocks. Not
720 all of the various sub-mechanisms reside on every media path. For
721 example, one media path may provide printing only on one surface of
722 the media (a simplex path) and another media path may have a sub-
723 mechanism that turns the media over and feeds it a second time
724 through the marker sub-unit (a duplex path). The duplex path may
725
726
727
728
729
730Bergman, et al. Standards Track [Page 13]
731\f
732RFC 3805 Printer MIB v2 June 2004
733
734
735 even have a buffer sub-mechanism that allows multiple copies of the
736 obverse side to be held before the reverse side of all the copies is
737 marked.
738
7392.2.8. System Controller
740
741 The System Controller is the sub-unit upon which the software
742 components of the Printer run. The Host Resources MIB [RFC2790]
743 represents the System Controller in the model. The Host Resources
744 MIB allows for the specification of the processor(s), memory, disk
745 storage, file system and other underlying sub-mechanisms of the
746 printer. The controller can range from simple single processor
747 systems to multiprocessor systems. In addition, controllers can have
748 a full range of resources such as hard disks. The printer is modeled
749 to have one system controller even though it may have more than one
750 processor and multiple other resources associated with it.
751
7522.2.9. Interfaces
753
754 An interface is the communications port and associated protocols that
755 are responsible for the transport of data to the printer. A printer
756 has one or more interface sub-units. The interfaces are represented
757 by the Interfaces Group of MIB-II [RFC1213], [RFC2863]. Some
758 examples of interfaces are serial ports (with little or no protocol)
759 and Ethernet ports on which one might run Internet IP, Novell IPX,
760 etc.
761
7622.2.10. Print Job Delivery Channels
763
764 The print job delivery channel sub-units identify the independent
765 sources of print data (here print data is the information that is
766 used to construct printed pages and may have both data and control
767 aspects). A printer may have one or more channels. The channel sub-
768 units are represented by the Print Job Delivery Channel Group in the
769 Model. The electronic path typically identifies each channel and
770 service protocol used to deliver print data to the printer. A
771 channel sub-unit may be independently enabled (allowing print data to
772 flow) or disabled (stopping the flow of print data). It has a
773 current Control Language that can be used to specify which
774 interpreter is to be used for the print data and to query and change
775 environment variables used by the interpreters (and SNMP). There is
776 also a default interpreter that is to be used if an interpreter is
777 not explicitly specified using the Control Language. Print Job
778 Delivery Channel sub-units can, and usually are, based on an
779 underlying interface.
780
781
782
783
784
785
786Bergman, et al. Standards Track [Page 14]
787\f
788RFC 3805 Printer MIB v2 June 2004
789
790
7912.2.11. Interpreters
792
793 The interpreter sub-units are responsible for the conversion of a
794 description of intended print instances into images that are to be
795 marked on the media. A printer may have one or more interpreters.
796 The Interpreter Group in the Model represents the interpreter sub-
797 units. Each interpreter is generally implemented with software
798 running on the System Controller sub-unit. The Interpreter Table has
799 one entry per interpreter where the interpreters include both Page
800 Description Language (PDL) Interpreters and Control Language
801 Interpreters.
802
8032.2.12. Console
804
805 Many printers have a console on the printer, the operator console
806 that is used to display and modify the state of the printer. The
807 console can be as simple as a few indicators and switches or as
808 complicated as full screen displays and keyboards. There can be at
809 most one such console. The Console Group in the model represents
810 this console sub-unit. Although most of the information displayed
811 there is also available in the state of the printer as represented by
812 the various Groups, it is useful to be able to query and modify the
813 operator console remotely. For example, a management application
814 might like to display to its user the current message on the operator
815 console of the remote printer or the management application user
816 might like to modify the current message on the operators console of
817 the remote printer. As another example, one might have a remote
818 application that puts up a pseudo console on a workstation screen.
819 Since the rules by which the printer state is mapped onto the console
820 and vice versa are not standardized, it is not possible to reproduce
821 the console state or the action of console buttons and menus.
822 Therefore, the Console Group provides access to the console. The
823 operator console is usually implemented on the system controller with
824 additional hardware for input and display.
825
8262.2.13. Alerts
827
828 The alert sub-unit is responsible for detecting reportable events,
829 making an entry in the alert table and, if and only if the event is a
830 critical event, initiating a trap. The exception to this rule is
831 when the "alertRemovalofBinaryChangeEntry" trap is generated. The
832 alert sub-unit is represented by the Alerts Group and, in particular,
833 the Alert Table. This table contains information on the severity,
834 sub- unit, and detailed location within the sub-unit, alert code and
835 description of each alert that is currently active within the
836 printer. Each reportable event causes an entry to be made in the
837 Alert Table.
838
839
840
841
842Bergman, et al. Standards Track [Page 15]
843\f
844RFC 3805 Printer MIB v2 June 2004
845
846
8472.2.13.1. Status and Alerts
848
849 Summary information about the state of the printer is reported at
850 three separate levels: (1) The status of the printer as a whole is
851 reported in the Host Resources MIB, (2) The status of various sub-
852 units is reported in the principle table of the Group that represents
853 the sub-unit, and (3) Alert codes are reported in the Alert Table.
854
8552.2.13.2. Overall Printer Status
856
857 Of the many states a printer can be in, certain states are more
858 "interesting" because of the distinct actions they are likely to
859 provoke in the administrator. These states may be applied to the
860 printer as a whole, or to a particular sub-unit of the printer.
861 These named states are:
862
863 Non Critical Alert Active - For the printer this means that one or
864 more sub-units have a non-critical alert active. For a sub-unit,
865 this means that the sub-unit has a non-critical alert active.
866
867 Critical Alert Active - For the printer this means that one or more
868 sub-units have a critical alert active. For a sub-unit, this means
869 that the sub-unit has a critical alert active.
870
871 Unavailable - The printer or sub-unit is unavailable for use (this is
872 the same as "broken" or "down" in other terminology). A trained
873 service person is typically necessary to make it available.
874
875 Moving on-line or off-line - The printer is either off-line, in the
876 process of moving off-line or moving back on-line. For example, on
877 printers with motorized hoppers, reloading paper involves a
878 transition to off-line to open the paper bin, filling the hopper and,
879 finally, a transition back to on-line as the paper bin is
880 repositioned for printing.
881
882 Standby - The printer or sub-unit is not immediately available but
883 can accept new instructions.
884
885 Available - The printer or subunit is functioning normally.
886
887 Idle - The printer or subunit is immediately available.
888
889 Active - The printer or subunit is performing its primary function.
890
891 Busy - The printer or subunit is performing a function (not
892 necessarily its primary function) and is not immediately available
893 for its primary function.
894
895
896
897
898Bergman, et al. Standards Track [Page 16]
899\f
900RFC 3805 Printer MIB v2 June 2004
901
902
903 The Host Resources MIB [RFC2790] provides three status objects that
904 can be used to describe the status of a printer: (1) hrDeviceStatus
905 in the entry in the hrDeviceTable; (2) hrPrinterStatus in the
906 hrPrinterTable; and (3) hrPrinterDetectedErrorState in the
907 hrPrinterTable. These objects describe many of the states that a
908 printer can be in. The following table shows how the values of the
909 three printer-related objects in the Host Resources MIB relate to the
910 states named above:
911
912 Printer hrDeviceStatus hrPrinterStatus hrPrinterDetected-
913 Status ErrorState
914
915 Idle running(2) idle(3) none set
916
917 Busy/ running(2) printing(4)
918 Active
919
920 Non Critical warning(3) idle(3) or could be: lowPaper,
921 Alert Active printing(4) lowToner, or
922 serviceRequested
923
924 Critical down(5) other(1) could be: jammed,
925 Alert Active noPaper, noToner,
926 coverOpen, or
927 serviceRequested
928
929 Unavailable down(5) other(1)
930
931 Moving off- warning(3) idle(3) or offline
932 line printing(4)
933 Off-line down(5) other(1) offline
934
935 Moving down(5) warmup(5)
936 on-line
937
938 Standby running(2) other(1)
939
940 These named states are only a subset of the possible states - they
941 are not an exhaustive list of the possible states. Nevertheless,
942 several things should be noted. When using these states, it is not
943 possible to detect when both critical and non-critical alerts are
944 pending - if both are pending, the Critical Alert Active state will
945 prevail. In addition, a printer in the Standby state will be
946 represented in the Host Resources MIB with a device status of
947 running(2) and a printer status of other(1), a set of states that
948 don't uniquely distinguish this important printer state.
949
950
951
952
953
954Bergman, et al. Standards Track [Page 17]
955\f
956RFC 3805 Printer MIB v2 June 2004
957
958
959 Detailed status per sub-unit is reported in the sub-unit status
960 fields.
961
9622.2.13.2.1. Host Resources MIB Printer Status
963
964 For completeness, the definitions of the Printer Status objects of
965 the Host Resources MIB [RFC2790] are given below:
966
967 hrDeviceStatus OBJECT-TYPE
968 SYNTAX INTEGER {
969 unknown(1),
970 running(2),
971 warning(3),
972 testing(4),
973 down(5)
974 }
975 ACCESS read-only
976 STATUS mandatory
977 DESCRIPTION
978 "The current operational state of the device
979 described by this row of the table. A value
980 unknown(1) indicates that the current state of the
981 device is unknown. running(2) indicates that the
982 device is up and running and that no unusual error
983 conditions are known. The warning(3) state
984 indicates that agent has been informed of an
985 unusual error condition by the operational software
986 (e.g., a disk device driver) but that the device
987 is still 'operational'. An example would be high
988 number of soft errors on a disk. A value of
989 testing(4), indicates that the device is not
990 available for use because it is in the testing
991 state. The state of down(5) is used only when
992 the agent has been informed that the device is
993 not available for any use."
994 ::= { hrDeviceEntry 5 }
995
996 hrPrinterStatus OBJECT-TYPE
997 SYNTAX INTEGER {
998 other(1),
999 unknown(2),
1000 idle(3),
1001 printing(4),
1002 warmup(5)
1003 }
1004 ACCESS read-only
1005 STATUS mandatory
1006 DESCRIPTION
1007
1008
1009
1010Bergman, et al. Standards Track [Page 18]
1011\f
1012RFC 3805 Printer MIB v2 June 2004
1013
1014
1015 "The current status of this printer device. When in the
1016 idle(3), printing(4), or warmup(5) state, the corresponding
1017 hrDeviceStatus should be running(2) or warning(3). When in
1018 the unknown(2) state, the corresponding hrDeviceStatus
1019 should be unknown(1)."
1020 ::= { hrPrinterEntry 1 }
1021
1022 hrPrinterDetectedErrorState OBJECT-TYPE
1023 SYNTAX OCTET STRING (0..128)
1024 ACCESS read-only
1025 STATUS mandatory
1026 DESCRIPTION
1027 "This object represents any error conditions detected by the
1028 printer. The error conditions are encoded as an OCTET STRING
1029 with the following definitions:
1030
1031 Condition Bit #
1032
1033 lowPaper 0
1034 noPaper 1
1035 lowToner 2
1036 noToner 3
1037 doorOpen 4
1038 jammed 5
1039 offline 6
1040 serviceRequested 7
1041
1042 inputTrayMissing 8
1043 outputTrayMissing 9
1044 markerSupplyMissing 10
1045 outputNearFull 11
1046 outputFull 12
1047 inputTrayEmpty 13
1048 overduePreventMaint 14
1049
1050 Bit # 15 is not assigned.
1051
1052 If multiple conditions are currently detected and the
1053 hrDeviceStatus would not otherwise be unknown(1) or
1054 testing(4), the hrDeviceStatus shall correspond to the worst
1055 state of those indicated, where down(5) is worse than
1056 warning(3), which is worse than running(2).
1057
1058 Bits are numbered starting with the most significant bit of
1059 the first byte being bit 0, the least significant bit of the
1060 first byte being bit 7, the most significant bit of the
1061 second byte being bit 8, and so on. A one bit encodes that
1062 the condition was detected, while a zero bit encodes that
1063
1064
1065
1066Bergman, et al. Standards Track [Page 19]
1067\f
1068RFC 3805 Printer MIB v2 June 2004
1069
1070
1071 the condition was not detected.
1072
1073 This object is useful for alerting an operator to specific
1074 warning or error conditions that may occur, especially those
1075 requiring human intervention."
1076 ::= { hrPrinterEntry 2 }
1077
10782.2.13.2.2. Sub-unit Status
1079
1080 Sub-unit status is reported in the entries of the principle table in
1081 the Group that represents the sub-unit. For sub-units that report a
1082 status, there is a status column in the table and the value of this
1083 column is always an integer formed in the following way.
1084
1085 The PrtSubUnitStatusTC is an integer that is the sum of 5 distinct
1086 values, Availability, Non-Critical, Critical, On-line, and
1087 Transitioning. These values are:
1088
1089 Availability value
1090
1091 Available and Idle 0 000'b
1092 Available and Standby 2 010'b
1093 Available and Active 4 100'b
1094 Available and Busy 6 110'b
1095 Unavailable and OnRequest 1 001'b
1096 Unavailable because Broken 3 011'b
1097 Unknown 5 101'b
1098
1099 Non-Critical
1100
1101 No Non-Critical Alerts 0
1102 Non-Critical Alerts 8
1103
1104 Critical
1105
1106 No Critical Alerts 0
1107 Critical Alerts 16
1108
1109 On-Line
1110
1111 State is On-Line 0
1112 State is Off-Line 32
1113
1114 Transitioning
1115
1116 At intended state 0
1117 Transitioning to intended state 64
1118
1119
1120
1121
1122Bergman, et al. Standards Track [Page 20]
1123\f
1124RFC 3805 Printer MIB v2 June 2004
1125
1126
1127 For example, an input (tray) that jammed on the next to the last page
1128 may show a status of 27 (unavailable because broken (3) + a critical
1129 state (16), jammed, and a noncritical state (8), low paper).
1130
11312.2.13.3. Alert Tables
1132
1133 The Alert Group consists of a single table in which all active alerts
1134 are represented. This section provides an overview of the table and
1135 a description of how it is managed. The basic content of the alert
1136 table is the severity (critical or non-critical) of the alert, the
1137 Group and entry where a state change caused the alert, additional
1138 information about the alert (a more detailed location, an alert code,
1139 and a description), and an indication of the level of training needed
1140 to service the alert.
1141
1142 The Alert Table contains some information that is redundant, for
1143 example that an event has occurred, and some information that is only
1144 represented in the Alert Table, for example the additional
1145 information. A single table was used because a single entry in a
1146 group could cause more than one alert, for example paper jams in more
1147 than one place in a media path. Associating the additional
1148 information with the entry in the affected group would only allow one
1149 report where associating the additional information with the alert
1150 makes multiple reports possible. Every time an alert occurs in the
1151 printer, the printer makes one or more entries into the Alert Table.
1152 The printer determines if an event is to be classified as critical or
1153 non-critical. If the severity of the Alert is "critical", the
1154 printer sends a trap or event notification to the host indicating
1155 that the table has changed. Whether or not a trap is sent, the
1156 management application is expected to poll the printer on a regular
1157 basis and to read and parse the table to determine what conditions
1158 have changed, in order to provide reliable information to the
1159 management application user.
1160
11612.2.13.4. Alert Table Management
1162
1163 The alert tables are sparsely populated tables. This means the
1164 tables will only contain entries of the alerts that are currently
1165 active and the number of rows, or entries in the table will be
1166 dynamic. More than one event can be added or removed from the event
1167 tables at a time depending on the implementation of the printer.
1168
1169 There are basically two kinds of events that produce alerts: binary
1170 change events and unary change events. Binary change events come in
1171 pairs: the leading edge event and the trailing edge event. The
1172 leading edge event enters a state from which there is only one exit;
1173 for example, going from running to stopped with a paper jam. The
1174 only exit from this state is fixing the paper jam and it is clear
1175
1176
1177
1178Bergman, et al. Standards Track [Page 21]
1179\f
1180RFC 3805 Printer MIB v2 June 2004
1181
1182
1183 when that is accomplished. The trailing edge event exits the state
1184 that was entered by the leading edge event. In the example above,
1185 fixing the paper jam is the trailing edge event.
1186
1187 It is relatively straightforward to manage binary change events in
1188 the Alert Table. Only the leading edge event makes an entry in the
1189 alert table. This entry persists in the Alert Table until the
1190 trailing edge event occurs at which point this event is signaled by
1191 the removal of the leading edge event entry in the Alert Table. That
1192 is, a trailing edge event does not create an entry; it removes the
1193 corresponding leading edge event. Removing the leading edge entry
1194 may cause the unary change event "alertRemovalofBinaryChangeEntry" to
1195 be added to the table. With binary change events it is possible to
1196 compute the maximum number that can occur at the same time and
1197 construct an Alert Table that would hold that many events. There
1198 would be no possibility of table overflow and no information about
1199 outstanding events would be lost.
1200
1201 Unfortunately, there are some events that are not binary changes.
1202 This other category of event, the unary change event, is illustrated
1203 by the configuration change event. With this kind of event the state
1204 of the machine has changed, but to a state which is (often) just as
1205 valid as the state that was left and from which no return is
1206 necessary. For example, an operator may change the paper that is in
1207 the primary input source from letter to legal. At some time in the
1208 future the paper may be changed back to letter, but it might be
1209 changed to executive instead. This is where the problem occurs. It
1210 is not obvious how long to keep unary change event entries in the
1211 Alert Table. If they were never removed, the Alert Table would
1212 continue to grow indefinitely.
1213
1214 The agent needs to have an algorithm implemented for the management
1215 of the alert table, especially in the face of combinations of binary
1216 and unary alerts that would overflow the storage capacity of the
1217 table. When the table is full and new alerts need to be added, an
1218 old alert to be deleted should be chosen using the following rules:
1219
1220 1. Find a non-critical unary alert and delete it. If there are
1221 multiple non-critical unary alerts, it is suggested that the
1222 oldest one is chosen. If there are no non-critical unary alerts,
1223 then,
1224
1225 2. Find a non-critical binary alert and delete it. If there are
1226 multiple non-critical binary alerts, it is suggested that the
1227 oldest one is chosen. If there are no non-critical binary alerts,
1228 then,
1229
1230
1231
1232
1233
1234Bergman, et al. Standards Track [Page 22]
1235\f
1236RFC 3805 Printer MIB v2 June 2004
1237
1238
1239 3. Find a critical (binary) alert and delete it. If there are
1240 multiple critical alerts, it is suggested that the oldest one be
1241 chosen. Agent implementers are encouraged to provide at least
1242 enough storage space for the maximum number of critical alerts
1243 that could occur simultaneously. Note that all critical alerts
1244 are binary.
1245
1246 In the event that a critical binary alert has been deleted out of the
1247 alert table; when space allows and the alert condition still exists,
1248 the alert should be re-added to the alert table even if there was no
1249 subsequent transition into the associated state. It is recommended
1250 that this be done for non-critical binary alerts as well. Note that
1251 the new alert entry will not have the same index as the original
1252 entry that was moved out of the table.
1253
1254 Note that because the Alert Index is a monotonically increasing
1255 integer there will be gaps in the values in the table when an alert
1256 is deleted. The management application may want to re-acquire the
1257 Printer state and check for state changes that it did not observe in
1258 the Alert Table if such gaps are detected.
1259
12602.3. Read-Write Objects
1261
1262 Some objects in the printer MIB reflect the existence or amount of a
1263 given resource within the printer. Some examples of such resources
1264 are the size and number of sheets in a paper tray or the existence of
1265 certain output options. Some printers have automatic sensors for
1266 these resources. Most printers lack sensors for every property of
1267 every resource. The management application is allowed to write into
1268 objects that hold descriptive or existence values for printers that
1269 cannot sense these values. The ability to change the value of a
1270 read- write object may depend on the implementation of the agent.
1271 Many objects in the MIB are given read-write access, but a printer
1272 implementation might only permit a management application to change
1273 the value if the printer can not sense the value itself. Note that
1274 even though some objects explicitly state the behavior of conditional
1275 ability to change values, any read-write object may act this way.
1276
1277 Generally, an object is given read-write access in the Printer MIB
1278 specification if:
1279
1280 1. The object involves installation of a resource that some printers
1281 cannot themselves detect. Therefore, external means are needed to
1282 inform the printer of the installation. (Here external means
1283 include using the operator console, or remote management
1284 application) and
1285
1286
1287
1288
1289
1290Bergman, et al. Standards Track [Page 23]
1291\f
1292RFC 3805 Printer MIB v2 June 2004
1293
1294
1295 2. The printer will behave differently if the installation of the
1296 resource is reported than the printer would if the installation
1297 were not reported; that is, the object is not to be used as a
1298 place to put information not used by the printer, i.e., not a
1299 "sticky-note". Another way of saying this is that the printer
1300 believes that information given it and acts as if the information
1301 were true. For example, on a printer that cannot sense the size,
1302 if one paper size is loaded, but another size is set into the
1303 paper size object, then the printer will use the size that was set
1304 as its current paper size in its imaging and paper handling.
1305
1306 3. The printer may get hints that it may not know about the existence
1307 or properties of certain resources. For example, a paper tray may
1308 be removed and re-inserted. When this removal and insertion
1309 happens, the printer may either assume that a property, such as
1310 the size of paper in the tray, has not changed or the printer may
1311 change the value of the associated object to "unknown", as might
1312 be done for the amount of paper in the tray. As long as the
1313 printer acts according to the value in the object either strategy
1314 is acceptable.
1315
1316 4. It is an implementation-specific matter as to whether or not MIB
1317 object values are persistent across power cycles or cold starts.
1318 It is particularly important that the values of the
1319 prtMarkerLifeCount object persist throughout the lifetime of the
1320 printer. Therefore, if the value of any MIB object persists
1321 across power cycles, then the prtMarkerLifeCount object must also
1322 persist.
1323
13242.4. Enumerations
1325
1326 Enumerations (enums) are sets of symbolic values defined for use with
1327 one or more objects. Commonly used enumeration sets are assigned a
1328 symbolic data type name (textual convention), rather than being
1329 specified in the SYNTAX clause of each individual object definition.
1330
1331 Textual conventions defined in the Printer MIB or the companion IANA
1332 Printer MIB are extensible by RFC publication or by Designated Expert
1333 Review (see the 'IANA Considerations' section of this Printer MIB and
1334 the DESCRIPTION clause in MODULE-IDENTITY of IANA Printer MIB). All
1335 of these textual conventions are:
1336
1337 a) used more than once in the Printer MIB itself; or
1338
1339 b) imported and used in the companion Finisher MIB; or
1340
1341 c) imported and used in any other, including vendor private, MIB
1342 modules.
1343
1344
1345
1346Bergman, et al. Standards Track [Page 24]
1347\f
1348RFC 3805 Printer MIB v2 June 2004
1349
1350
1351 The Printer MIB has also defined the following special values for use
1352 with objects of the syntax "Integer32" to define conditions that are
1353 outside of the normal numeric range: other(-1), unknown(-2), and
1354 partial(-3). The 'partial' value means that there is some supply
1355 remaining (but the amount is indeterminate) or there is some capacity
1356 remaining (but the amount is indeterminate). The Integer32 range
1357 field indicates in which objects these special values are valid.
1358
13592.4.1. Registering Additional Enumerated Values
1360
1361 The Printer MIB and the companion IANA Printer MIB each defines one
1362 category of textual convention, according to the process employed to
1363 control the addition of new enumerations:
1364
1365 Type 1 - All of the legal values are defined in the Printer MIB.
1366 Additional enumerated values require the publication of a new Printer
1367 MIB.
1368
1369 Type 2 - All of the legal values are registered in the IANA Printer
1370 MIB. Additional enumerated values require a Designated Expert Review
1371 defined in "Guidelines for Writing an IANA Considerations Section in
1372 RFCs" [RFC2434]. The Designated Expert will be selected by the IETF
1373 Area Director(s) of the Applications Area.
1374
13753. Groups from other MIB Specifications
1376
1377 This section identifies the groups from other MIBs that shall be
1378 supported to supplement and complete a printer MIB implementation.
1379 The section also describes some of the less obvious characteristics
1380 of the Printer MIB structure that are related to the inclusion of
1381 these other MIB groups.
1382
13833.1. System Group
1384
1385 All objects in the system group of MIB-II [RFC1213] shall be
1386 implemented; however, as described in paragraph 2.4, implementers
1387 should carefully consider what constitutes the "system".
1388
13893.2. System Controller
1390
1391 The storage and device groups of the Host Resources MIB [RFC2790]
1392 shall be implemented to support the printer(s) system controller, and
1393 any supporting devices. If deemed appropriate by the implementer,
1394 other groups of the Host Resources MIB (System, Running Software,
1395 Running Software Performance, and Installed Software) may be
1396 implemented. Because of the structure of the Host Resources MIB, the
1397 devices constituting the system controller are at the same level as
1398 the printer.
1399
1400
1401
1402Bergman, et al. Standards Track [Page 25]
1403\f
1404RFC 3805 Printer MIB v2 June 2004
1405
1406
14073.3. Interface Group objects
1408
1409 All objects in the Interfaces Group of MIB-II [RFC1213] shall be
1410 implemented for all print information interfaces to the printer,
1411 including non-network interfaces.
1412
14133.3.1. Interface Types
1414
1415 The interfaces group of RFC 1213 [RFC1213] contains only a partial
1416 list of interface types that can be specified in the "ifType" object.
1417 For a complete list of interface types, refer to the IANA registry at
1418 "ftp://ftp.isi.edu/mib/iana.mib/ianaiftype.mib"
1419
14204. Differences from RFC 1759
1421
1422 This document supersedes and replaces RFC 1759. However, a compliant
1423 implementation of RFC 1759 is also compliant with this document. The
1424 following changes to RFC 1759 are included: (See the printmib
1425 REVISION/DESCRIPTION clause for additional details of changes.)
1426
1427 - Minor editorial corrections and changes. Updated the cover page
1428 and added the "SNMP Management Framework" boilerplate to section
1429 1.
1430
1431 - Updated figure 2 to use MIB names instead of RFC numbers.
1432
1433 - Updated Coded Character Set description and IANA registration
1434 process.
1435
1436 - Change hrPrinterDetectedErrorState "coverOpen" (bit 4) to
1437 "doorOpen" per RFC 2790.
1438
1439 - Added second octet of hrPrinterDetectedErrorState as partially
1440 described and assigned in the updated Host Resources MIB (RFC
1441 2790).
1442
1443 - Remove fixed association of hrDeviceStatus (warning/down) from
1444 hrPrinterDetetctedErrorState per RFC 2790.
1445
1446 - Instead of showing bit 15 as "not assigned" in the quote from RFC
1447 2790 in the hrPrinterDetectedErrorState object, removed that from
1448 the tabular form and added it as a sentence, because the RFC
1449 doesn't show bit 15 in the tabular form.
1450
1451 - Clarified the international considerations.
1452
1453
1454
1455
1456
1457
1458Bergman, et al. Standards Track [Page 26]
1459\f
1460RFC 3805 Printer MIB v2 June 2004
1461
1462
1463 - Added prtChannelInformation to the Channel Group textual-
1464 conventions on a per channel basis to clarify the channel
1465 description and enhance interoperability.
1466
1467 - Deprecated some obsolete channel types.
1468
1469 - Extended the Alert Table and PrtMarkerSuppliesSupplyUnit textual
1470 conventions to include values from the Finisher MIB.
1471
1472 - Clarified alerts based on unary vs. binary change events.
1473
1474 - Added (optional) unary change event
1475 alertRemovalOfBinaryChangeEntry(1801).
1476
1477 - Establish a convention for contact information for
1478 prtGeneralCurrentOperator and prtGeneralServicePerson.
1479
1480 - Added prtAuxiliarySheetStartupPage PresentOnOff
1481
1482 - Added prtAuxiliarySheetBannerPage PresentOnOff
1483
1484 - Added prtGeneralPrinterName OCTET STRING
1485
1486 - Added prtGeneralSerialNumber OCTET STRING
1487
1488 - Added prtInputNextIndex Integer32
1489
1490 - Added the Input Switching Group
1491
1492 - Added prtAlertCriticalEvents Counter32
1493
1494 - Added prtAlertAllEvents Counter32
1495
1496 - Updated PrtAlertCode enums including generic alert codes.
1497
1498 - Created five OBJECT-GROUPs (prtAuxilliarySheetGroup,
1499 prtInputSwitchingGroup, prtGeneralV2Group, prtAlertTableV2Group,
1500 prtChannelV2Group). Added the nine new objects to them
1501 (prtAuxiliarySheetStartupPage, prtAuxiliarySheetBannerPage,
1502 prtGeneralPrinterName, prtGeneralSerialNumber,
1503 prtAlertCriticalEvents, prtAlertAllEvents,
1504 prtInputMediaLoadTimeout, prtInputNextIndex,
1505 prtChannelInformation). Created one new NOTIFICATION-GROUP
1506 (prtAlertTrapGroup) to contain printerV2Alert. Included the new
1507 OBJECT-GROUPs and the NOTIFICATION_GROUP in prtMIBCompliance, all
1508 in GROUP (not MANDATORY-GROUP) clauses. The nine new objects are
1509 optional, i.e., this document is backward compatible with RFC
1510 1759.
1511
1512
1513
1514Bergman, et al. Standards Track [Page 27]
1515\f
1516RFC 3805 Printer MIB v2 June 2004
1517
1518
1519 - prtAlertTime is strongly recommended.
1520
1521 - Deprecated the use of alert codes doorOpen(501) and
1522 doorClosed(502), in favor of coverOpened(3) and coverClosed(4).
1523
1524 - Added the PrtConsoleDisableTC and PrtMarkerAddressabilityUnitTC
1525 textual conventions, and changed the PrtConsoleDisable and
1526 PrtMarkerAddressabilityUnit objects' syntax to use those TCs, and
1527 changed the PrtGeneralEntry and PrtMarkerColorantEntry SEQUENCEs
1528 to reflect the new syntax.
1529
1530 - Added textual conventions "PrtLocalizedDescriptionStringTC" and
1531 "PrtConsoleDescriptionStringTC" and updated several objects to use
1532 them.
1533
1534 - Changed most enumerations to textual conventions and therefore
1535 changed the SYNTAX of many objects from RFC 1759 to specify the
1536 appropriate textual conventions. (28 TCs were added.)
1537
1538 - Changed the TC names "MediaUnit" to "PrtMediaUnitTC",
1539 "CapacityUnit" to "PrtCapacityUnitTC", and "SubUnitStatus" to
1540 "PrtSubUnitStatusTC"
1541
1542 - All objects with a MAX-ACCESS of read-write now have a MIN-ACCESS
1543 of read-only.
1544
1545 - Added 'IANA Considerations' and 'Internationalization
1546 Considerations' as top level sections, per IETF guidelines.
1547
1548 - Updated Security and Copyright sections.
1549
1550 - Updated references and split into Normative and Informative
1551 groups.
1552
1553 - Added Appendix E - Overall Printer Status Table.
1554
1555 - Updated participant and contact information.
1556
1557 - Removed CodedCharSet Textual Convention, replaced with an import
1558 of the IANACharset.
1559
1560 - Removed all comment statements that indicated objects or groups
1561 are mandatory or optional. Avoids any potential conflicts with
1562 the conformance section.
1563
1564
1565
1566
1567
1568
1569
1570Bergman, et al. Standards Track [Page 28]
1571\f
1572RFC 3805 Printer MIB v2 June 2004
1573
1574
1575 - Added text to empty description clauses. (prtStorageRefTable,
1576 prtDeviceRefTable, prtMarkerTable, prtMediaPathTable,
1577 prtChannelTable, prtInterpreterTable, prtConsoleLightTable, and
1578 prtAlertTable)
1579
1580 - Added "DEFVAL { unknown }" to prtInterpreterDefaultCharSetIn and
1581 prtInterpreterDefaultCharSetOut.
1582
1583 - Changed "...values are expected to remain stable..." to "...values
1584 SHOULD remain stable..." in the description clauses for the index
1585 object in all tables.
1586
1587 - Added ranges to all objects with a syntax of Integer32.
1588
1589 - Revised the description clause for prtAlertGroupIndex.
1590
1591 - Added additional text to the description clause for
1592 prtMediaPathEntry, prtChannelEntry, prtInterpreterEntry, and
1593 printerV2Alert.
1594
1595 - Added text to section 2.4 to explain the usage of textual
1596 conventions in this MIB and others. Also added a note defining
1597 the common usage of the enumerations 'other(-1)' and 'unknown(-2)'
1598
1599 - Changed range of prtStorageRefSeqNumber, prtDeviceRefSeqNumber,
1600 and prtConsoleLightIndex from (0..65535) to (1..65535) since index
1601 values cannot be zero. (Typo in RFC 1759)
1602
1603 - The PWG Standard for Standardized Media Names is now recommended
1604 for the objects prtInputMediaName, prtInputMediaColor, and
1605 prtInputMediaType.
1606
1607 - Added chSMTP(45) to prtChannelTypeTC.
1608
16095. The IANA Printer MIB
1610
1611IANA-PRINTER-MIB DEFINITIONS ::= BEGIN
1612 -- http://www.iana.org/assignments/ianaprinter-mib
1613
1614IMPORTS
1615 MODULE-IDENTITY,
1616 mib-2
1617 FROM SNMPv2-SMI -- [RFC2578]
1618 TEXTUAL-CONVENTION
1619 FROM SNMPv2-TC; -- [RFC2579]
1620
1621ianaPrinterMIB MODULE-IDENTITY
1622 LAST-UPDATED "200406020000Z" -- June 2, 2004
1623
1624
1625
1626Bergman, et al. Standards Track [Page 29]
1627\f
1628RFC 3805 Printer MIB v2 June 2004
1629
1630
1631 ORGANIZATION "IANA"
1632 CONTACT-INFO "Internet Assigned Numbers Authority
1633 Postal: ICANN
1634 4676 Admiralty Way, Suite 330
1635 Marina del Rey, CA 90292
1636
1637 Tel: +1 310 823 9358
1638 E-Mail: iana@iana.org"
1639
1640 DESCRIPTION "This MIB module defines a set of printing-related
1641 TEXTUAL-CONVENTIONs for use in Printer MIB (RFC 3805),
1642 Finisher MIB (RFC 3806), and other MIBs which need to
1643 specify printing mechanism details.
1644
1645 Any additions or changes to the contents of this MIB
1646 module require either publication of an RFC, or
1647 Designated Expert Review as defined in RFC 2434,
1648 Guidelines for Writing an IANA Considerations Section
1649 in RFCs. The Designated Expert will be selected by
1650 the IESG Area Director(s) of the Applications Area.
1651
1652 Copyright (C) The Internet Society (2004). The
1653 initial version of this MIB module was published
1654 in RFC 3805. For full legal notices see the RFC
1655 itself or see:
1656 http://www.ietf.org/copyrights/ianamib.html"
1657
1658 REVISION "200406020000Z" -- June 2, 2004
1659 DESCRIPTION "Original version, published in coordination
1660 with Printer MIB (RFC 3805)."
1661 ::= { mib-2 109 }
1662
1663--
1664-- Generic TEXTUAL-CONVENTIONs
1665--
1666
1667PrtCoverStatusTC ::= TEXTUAL-CONVENTION
1668 -- This TC was extracted from prtCoverStatus in RFC 1759.
1669 STATUS current
1670 DESCRIPTION
1671 "Values for encoding the state of a particular cover or
1672 access panel on the printer case or enclosure."
1673 SYNTAX INTEGER {
1674 other(1),
1675 coverOpen(3),
1676 coverClosed(4),
1677 interlockOpen(5),
1678 interlockClosed(6)
1679
1680
1681
1682Bergman, et al. Standards Track [Page 30]
1683\f
1684RFC 3805 Printer MIB v2 June 2004
1685
1686
1687 }
1688
1689--
1690-- General Group TEXTUAL-CONVENTIONs
1691--
1692
1693PrtGeneralResetTC ::= TEXTUAL-CONVENTION
1694 -- This TC was extracted from prtGeneralReset in RFC 1759.
1695 STATUS current
1696 DESCRIPTION
1697 "Values for reading and writing the prtGeneralReset object.
1698
1699 If a device does not have NVRAM, the device shall none the
1700 less respond to a SET with the value resetToNVRAM(5) with a
1701 sort of warm reset that resets the device to implementation-
1702 defined state that is preferably under control of the system
1703 administrator by some means outside the scope of the Printer
1704 MIB specification."
1705
1706 SYNTAX INTEGER {
1707 notResetting(3),
1708 powerCycleReset(4), -- Cold Start
1709 resetToNVRAM(5), -- Warm Start
1710 resetToFactoryDefaults(6) -- Reset contents of
1711 -- NVRAM to factory
1712 -- defaults
1713 }
1714--
1715-- Channel Group TEXTUAL-CONVENTIONs
1716--
1717
1718PrtChannelTypeTC ::= TEXTUAL-CONVENTION
1719 -- This TC was extracted from prtChannelType in RFC 1759.
1720 STATUS current
1721 DESCRIPTION
1722 "This enumeration indicates the type of channel that is
1723 receiving jobs."
1724 SYNTAX INTEGER {
1725 other(1),
1726 chSerialPort(3),
1727 chParallelPort(4),
1728 chIEEE1284Port(5),
1729 chSCSIPort(6),
1730 chAppleTalkPAP(7),
1731 -- AppleTalk Printer
1732 -- Access Protocol (PAP)
1733 --
1734 -- prtChannelInformation entry:
1735
1736
1737
1738Bergman, et al. Standards Track [Page 31]
1739\f
1740RFC 3805 Printer MIB v2 June 2004
1741
1742
1743 --
1744 -- Printer Name
1745 -- Keyword: Name
1746 -- Syntax: Name
1747 -- Status: Optional
1748 -- Multiplicity: Single
1749 -- Description: The name of the printer
1750 -- within the AppleTalk naming scope
1751 chLPDServer(8),
1752 -- prtChannelInformation entry:
1753 --
1754 -- Printer queue name
1755 -- Keyword: Queue
1756 -- Syntax: Name
1757 -- Status: Mandatory
1758 -- Multiplicity: Single
1759 -- Description: queue name as
1760 -- defined in [RFC1179].
1761 chNetwareRPrinter(9),
1762 -- Novell, Inc.
1763 -- For each entry of this type, the
1764 -- prtChannelInformation must have a pair of
1765 -- keywords. For Netware 3.x channels this must
1766 -- be a (PServer, Printer) pair. For Netware
1767 -- 4.x channels and for IntranetWare channels
1768 -- this must be a (NDSTree, NDSPrinter) pair.
1769 --
1770 -- prtChannelInformation entries:
1771
1772 -- Print Server Name
1773 -- Keyword: PServer
1774 -- Syntax: Name
1775 -- Status: Mandatory
1776 -- Multiplicity: Single
1777 -- Description: The Pserver's SAP name
1778 --
1779 -- Printer Number
1780 -- Keyword: Printer
1781 -- Syntax: Integer
1782 -- Status: Mandatory
1783 -- Multiplicity: Single
1784 -- Description: The printer number
1785 --
1786 -- NDSTree
1787 -- Keyword: NDSTree
1788 -- Syntax: Name
1789 -- Multiplicity: Single
1790 -- Description: The tree's SAP name
1791
1792
1793
1794Bergman, et al. Standards Track [Page 32]
1795\f
1796RFC 3805 Printer MIB v2 June 2004
1797
1798
1799 --
1800 -- NDS Printer object
1801 -- Keyword: NDSPrinter
1802 -- Syntax: Text (Unicode)
1803 -- Status: Mandatory
1804 -- Multiplicity: Single
1805 -- Description: The fully qualified
1806 -- name of the Printer
1807 --
1808 -- In the Netware 3.x environment, the
1809 -- client checks the Bindery object
1810 -- representing the named PServer. The
1811 -- client then checks for queues which
1812 -- are associated with the numbered
1813 -- printer. In the 4.x and IntraNetware
1814 -- environment, the client looks up the
1815 -- queues which are associated with the
1816 -- NDS Printer Object in the named Tree.
1817 -- Depending on client access rights to
1818 -- those queues, the client submits jobs
1819 -- to the appropriate queue.
1820 chNetwarePServer(10),
1821 -- Novell,Inc.
1822 -- For each entry of this type, the
1823 -- prtChannelInformation must have a pair
1824 -- of keywords. For Netware 3.x channels
1825 -- this must be a (Server, PServer) pair.
1826 -- For Netware 4.x and IntranetWare
1827 -- channels, this must be a
1828 -- (NDSTree, NDSPServer) pair.
1829 --
1830 -- prtChannelInformation entries:
1831 --
1832 -- Server Name
1833 -- Keyword: Server
1834 -- Syntax: Name
1835 -- Status: Mandatory
1836 -- Multiplicity: Single
1837 -- Description: The SAP name of the
1838 -- server for which the PServer is defined.
1839 --
1840 -- PServer
1841 -- Keyword: PServer
1842 -- Syntax: Name
1843 -- Status: Mandatory
1844 -- Multiplicity: Single
1845 -- Description: The bindery name of
1846 -- the PServer
1847
1848
1849
1850Bergman, et al. Standards Track [Page 33]
1851\f
1852RFC 3805 Printer MIB v2 June 2004
1853
1854
1855 --
1856 -- NDS Tree
1857 -- Keyword: NDSTree
1858 -- Syntax: Name
1859 -- Status: Mandatory
1860 -- Multiplicity: Single
1861 -- Description: The NDS Tree name
1862 --
1863 -- PServer
1864 -- Keyword: NDSPServer
1865 -- Syntax: Text (Unicode)
1866 -- Status: Mandatory
1867 -- Multiplicity: Single
1868 -- Description: The fully qualified
1869 -- name of the PServer object in the tree.
1870 --
1871 -- In the 3.x environment, the client
1872 -- checks the bindery object
1873 -- representing the named PServer on the
1874 -- named Server. In the 4.x and
1875 -- IntranetWare environment,
1876 -- the client checks the NDS object
1877 -- representing the named PServer in the
1878 -- named Tree. In either case, the
1879 -- client then checks for all queues
1880 -- associated with the Pserver object.
1881 -- Depending on client access rights
1882 -- to those queues, the client submits
1883 -- jobs to the appropriate queue.
1884 chPort9100(11),
1885 -- DEPRECATED
1886 -- (see chPortTCP - 37; chBidirPortTCP - 38)
1887 chAppSocket(12),
1888 -- A bi-directional, LPD-like, protocol using
1889 -- 9101 for control and 9100 for data.
1890 -- Adobe Systems, Inc.
1891 chFTP(13), -- [RFC959]
1892 chTFTP(14), -- [RFC1350]
1893 chDLCLLCPort(15),
1894 chIBM3270(16), -- IBM Coax
1895 chIBM5250(17), -- IBM Twinax
1896 chFax(18),
1897 chIEEE1394(19),
1898 chTransport1(20),
1899 -- TCP port 35, for reserved TCP port list see
1900 -- [RFC3232]. This RFC should also be
1901 -- referenced for other channel
1902 -- enumerations utilizing TCP port
1903
1904
1905
1906Bergman, et al. Standards Track [Page 34]
1907\f
1908RFC 3805 Printer MIB v2 June 2004
1909
1910
1911 -- numbers 0 through 1024.
1912 chCPAP(21), -- TCP port 170
1913 -- Digital Equipment Corp.
1914 chDCERemoteProcCall(22), -- OSF
1915 -- DEPRECATED
1916 chONCRemoteProcCall(23), -- SUN Microsystems
1917 -- DEPRECATED
1918 chOLE(24), -- Microsoft
1919 -- DEPRECATED
1920 chNamedPipe(25),
1921 chPCPrint(26), -- Banyan
1922 chServerMessageBlock(27),
1923 -- File/Print sharing protocol used by
1924 -- various network operating systems
1925 -- from IBM 3Com, Microsoft and others
1926 --
1927 -- prtChannelInformation entry:
1928 --
1929 -- Service Name
1930 -- Keyword: Name
1931 -- Syntax: Name
1932 -- Status: Optional
1933 -- Multiplicity: Single
1934 -- Description: The service name of
1935 -- the printer
1936 chDPMF(28), -- IBM Infoprint
1937 chDLLAPI(29), -- Microsoft
1938 -- DEPRECATED
1939 chVxDAPI(30), -- Microsoft
1940 -- DEPRECATED
1941 chSystemObjectManager(31), -- IBM
1942 chDECLAT(32),
1943 -- Digital Equipment Corp.
1944 --
1945 -- prtChannelInformation entries:
1946 --
1947 -- Port Name
1948 -- Keyword: Port
1949 -- Syntax: Name
1950 -- Status: Conditionally
1951 -- Mandatory
1952 -- (see note below)
1953 -- Multiplicity: Single
1954 -- Description: LAT port name
1955 --
1956 -- Service Name
1957 -- Keyword: Service
1958 -- Syntax: Name
1959
1960
1961
1962Bergman, et al. Standards Track [Page 35]
1963\f
1964RFC 3805 Printer MIB v2 June 2004
1965
1966
1967 -- Status: Conditionally
1968 -- Mandatory
1969 -- Multiplicity: Single
1970 -- Description: LAT service name
1971 --
1972 -- The LAT channel may be
1973 -- identified by either a port or
1974 -- service, so either a
1975 -- Port or Service entry must be
1976 -- specified, but not both.
1977 chNPAP(33),
1978 chUSB(34), -- Not in RFC 1759
1979 -- Universal Serial Bus
1980 chIRDA(35), -- Not in RFC 1759
1981 -- Infrared Data Assoc. Prot.
1982 chPrintXChange(36), -- Not in RFC 1759
1983 -- PrintXChange Protocol
1984 chPortTCP(37), -- Not in RFC 1759
1985 -- A unidirectional "raw" TCP
1986 -- channel that uses an administratively
1987 -- assigned TCP port address.
1988 --
1989 -- prtChannelInformation entry:
1990 --
1991 -- Port Number
1992 -- Keyword: Port
1993 -- Syntax: decimal number
1994 -- Status: Mandatory
1995 -- Multiplicity: Single
1996 -- Description: TCP port number
1997 chBidirPortTCP(38), -- Not in RFC 1759
1998 -- A bi-directional version of chPortTCP
1999 --
2000 -- prtChannelInformation entries:
2001 -- (See chPortTCP)
2002 chUNPP(39), -- Not in RFC 1759
2003 -- Universal Network Printing
2004 -- Protocol(UNPP). A bi-directional,
2005 -- multiport network printing
2006 -- application protocol available on
2007 -- multiple transport protocols.
2008 -- Underscore, Inc.
2009 -- Contact: info@underscore.com
2010 chAppleTalkADSP(40), -- Not in RFC 1759
2011 -- AppleTalk Data Stream Protocol.
2012 -- ADSP is part of the AppleTalk
2013 -- suite of protocols.
2014 -- It is a symmetric, connection-
2015
2016
2017
2018Bergman, et al. Standards Track [Page 36]
2019\f
2020RFC 3805 Printer MIB v2 June 2004
2021
2022
2023 -- oriented protocol that makes
2024 -- possible the establishment
2025 -- and maintenance of full-duplex
2026 -- streams of data bytes between
2027 -- two sockets in an AppleTalk
2028 -- internet.
2029 -- See [APPLEMAC].
2030 chPortSPX(41), -- Not in RFC 1759
2031 -- Sequenced Packet Exchange (SPX)
2032 -- socket.
2033 -- Novell, Inc. Similar to TCP, a
2034 -- bi-directional data pipe using
2035 -- Novell SPX as a transport.
2036 --
2037 -- prtChannelInformation entries:
2038 --
2039 -- Network Number
2040 -- Keyword: Net
2041 -- Syntax: HexString
2042 -- Status: Mandatory
2043 -- Multiplicity: Single
2044 -- Description: The network number
2045 --
2046 -- Node Number
2047 -- Keyword: Node
2048 -- Syntax: HexString
2049 -- Status: Mandatory
2050 -- Multiplicity: Single
2051 -- Description: The node number
2052 --
2053 -- Socket Number
2054 -- Keyword: Socket
2055 -- Syntax: HexString
2056 -- Status: Mandatory
2057 -- Multiplicity: Single
2058 -- Description: The SPX socket number
2059 --
2060 -- There must be exactly one "Net" and
2061 -- one "Node" and one "Socket" entry. A
2062 -- HexString is a binary value
2063 -- represented as a string of
2064 -- ASCII characters using hexadecimal
2065 -- notation.
2066 chPortHTTP(42), -- Not in RFC 1759
2067 -- Hypertext Transfer Protocol. See [RFC1945]
2068 -- and [RFC2616].
2069 chNDPS(43), -- Not in RFC 1759
2070 -- Novell, Inc.
2071
2072
2073
2074Bergman, et al. Standards Track [Page 37]
2075\f
2076RFC 3805 Printer MIB v2 June 2004
2077
2078
2079 --
2080 -- prtChannelInformation entry:
2081 --
2082 -- Printer Agent Name
2083 -- Keyword: PA
2084 -- Syntax: Name
2085 -- Status: Mandatory
2086 -- Multiplicity: Single
2087 -- Description: The NDPS Printer
2088 -- Agent Name
2089 chIPP(44), -- Not in RFC 1759
2090 -- Internet Printing Protocol (IPP),
2091 -- (IPP/1.1 - see [RFC2910] and [RFC2911])
2092 -- also applies to all future versions of IPP.
2093 --
2094 -- IPP Printer URI
2095 -- Keyword: URI
2096 -- Syntax: URI (Unicode UTF-8 per
2097 -- [RFC2396])
2098 -- Status: Mandatory
2099 -- Multiplicity: Single
2100 -- Default: not applicable
2101 -- Description: URI of this IPP Printer
2102 -- within Internet naming scope. Unicode
2103 -- UTF-8 [RFC3629] string with
2104 -- hexadecimal escapes for any non-ASCII
2105 -- characters (per [RFC2396]).
2106 -- Conformance: An IPP Printer shall list all
2107 -- IPP URI it supports (one per IPP Channel
2108 -- entry). If a URI contains the 'http:'
2109 -- scheme it must have an explicit port.
2110 -- See: [RFC3629], [RFC2396], [RFC2910],
2111 -- [RFC2911].
2112 --
2113 -- IPP Printer Client Authentication
2114 -- Keyword: Auth
2115 -- Syntax: Keyword
2116 -- Status: Optional
2117 -- Multiplicity: Single
2118 -- Default: 'none'
2119 -- Description: A client authentication
2120 -- mechanism supported for this IPP Printer
2121 -- URI:
2122 -- 'none'
2123 -- no client authentication mechanism
2124 -- 'requesting-user-name'
2125 -- authenticated user in 'requesting-
2126 -- user-name'
2127
2128
2129
2130Bergman, et al. Standards Track [Page 38]
2131\f
2132RFC 3805 Printer MIB v2 June 2004
2133
2134
2135 -- 'basic'
2136 -- authenticated user via HTTP Basic
2137 -- mechanism
2138 -- 'digest'
2139 -- authenticated user via HTTP Digest
2140 -- mechanism
2141 -- 'certificate'
2142 -- authenticated user via certificate
2143 -- mechanism
2144 -- Conformance: An IPP Printer should list
2145 -- all IPP client authentication mechanisms
2146 -- it supports (one per IPP Channel entry).
2147 -- See: [RFC2911] and [RFC2910].
2148 --
2149 -- IPP Printer Security
2150 -- Keyword: Security
2151 -- Syntax: Keyword
2152 -- Status: Optional
2153 -- Multiplicity: Single
2154 -- Default: 'none'
2155 -- Description: A security mechanism
2156 -- supported for this IPP Printer URI:
2157 -- 'none'
2158 -- no security mechanism
2159 -- 'ssl3'
2160 -- SSL3 secure communications channel
2161 -- protocol
2162 -- 'tls'
2163 -- TLS secure communications channel
2164 -- protocol
2165 -- Conformance: An IPP Printer should list
2166 -- all IPP security mechanisms it supports
2167 -- (one per IPP Channel entry).
2168 -- See: [RFC2246], [RFC2911].
2169 --
2170 -- IPP Printer Protocol Version
2171 -- Keyword: Version
2172 -- Syntax: Keyword
2173 -- Status: Optional
2174 -- Multiplicity: Multiple
2175 -- Default: '1.1'
2176 -- Description: All of the IPP protocol
2177 -- versions (major.minor) supported for
2178 -- this IPP Printer URI:
2179 -- '1.0'
2180 -- IPP/1.0 conforming Printer
2181 -- '1.1'
2182 -- IPP/1.1 conforming Printer
2183
2184
2185
2186Bergman, et al. Standards Track [Page 39]
2187\f
2188RFC 3805 Printer MIB v2 June 2004
2189
2190
2191 -- Conformance: An IPP Printer should list
2192 -- all IPP versions it supports (all listed
2193 -- in each IPP Channel entry). An IPP
2194 -- Client should select the highest
2195 -- numbered version the IPP Client supports
2196 -- for use in all IPP Requests (for optimum
2197 -- interworking).
2198 -- See: [RFC2911].
2199 chSMTP(45)
2200 -- Print Job submission via Simple Mail
2201 -- Transfer Protocol (SMTP) - see [RFC2821]
2202 --
2203 -- prtChannelInformation entry:
2204 --
2205 -- Keyword: Mailto
2206 -- Syntax: Name
2207 -- Status: Mandatory
2208 -- Multiplicity: Single
2209 -- Default: not applicable
2210 -- Description: The SMTP URL of the printer.
2211}
2212
2213--
2214-- Interpreter Group TEXTUAL-CONVENTIONs
2215--
2216
2217PrtInterpreterLangFamilyTC ::= TEXTUAL-CONVENTION
2218 -- This TC was extracted from prtInterpreterLangFamily in RFC 1759.
2219 STATUS current
2220 DESCRIPTION
2221 "This enumeration indicates the type of interpreter that is
2222 receiving jobs."
2223 SYNTAX INTEGER {
2224 other(1),
2225 unknown(2), -- Not in RFC 1759
2226 langPCL(3), -- PCL. Starting with PCL version 5,
2227 -- HP-GL/2 is included as part of the
2228 -- PCL language.
2229 -- PCL and HP-GL/2 are registered
2230 -- trademarks of Hewlett-Packard
2231 -- Company.
2232 langHPGL(4), -- Hewlett-Packard Graphics Language.
2233 -- HP-GL is a registered trademark of
2234 -- Hewlett-Packard Company.
2235 langPJL(5), -- Peripheral Job Language. Appears in
2236 -- the data stream between data intended
2237 -- for a page description language.
2238 -- Hewlett-Packard Co.
2239
2240
2241
2242Bergman, et al. Standards Track [Page 40]
2243\f
2244RFC 3805 Printer MIB v2 June 2004
2245
2246
2247 langPS(6), -- PostScript (tm) Language
2248 -- Postscript - a trademark of Adobe
2249 -- Systems Incorporated which may be
2250 -- registered in certain jurisdictions
2251 langIPDS(7), -- Intelligent Printer Data Stream
2252 -- Bi-directional print data stream for
2253 -- documents consisting of data objects
2254 -- (text, image, graphics, bar codes),
2255 -- resources (fonts, overlays) and page,
2256 -- form and finishing instructions.
2257 -- Facilitates system level device
2258 -- control, document tracking and error
2259 -- recovery throughout the print
2260 -- process.
2261 -- IBM Corporation.
2262 langPPDS(8), -- IBM Personal Printer Data Stream.
2263 -- Originally called IBM ASCII, the name
2264 -- was changed to PPDS when the Laser
2265 -- Printer was introduced in 1989.
2266 -- Lexmark International, Inc.
2267 langEscapeP(9), -- Epson Corp.
2268 langEpson(10),
2269 langDDIF(11), -- Digital Document Interchange Format
2270 -- Digital Equipment Corp., Maynard MA
2271 langInterpress(12),
2272 -- Xerox Corp.
2273 langISO6429(13), -- ISO 6429. Control functions for
2274 -- Coded Character Sets (has ASCII
2275 -- control characters, plus additional
2276 -- controls for
2277 -- character imaging devices.)
2278 langLineData(14), -- line-data: Lines of data as
2279 -- separate ASCII or EBCDIC records
2280 -- and containing no control functions
2281 -- (no CR, LF, HT, FF, etc.)
2282 -- For use with traditional line
2283 -- printers. May use CR and/or LF to
2284 -- delimit lines, instead of records.
2285 -- See ISO 10175 Document Printing
2286 -- Application (DPA) [ISO10175].
2287 langMODCA(15), -- Mixed Object Document Content
2288 -- Architecture
2289 -- Definitions that allow the
2290 -- composition, interchange, and
2291 -- presentation of final form
2292 -- documents as a collection of data
2293 -- objects (text, image, graphics, bar
2294 -- codes), resources (fonts, overlays)
2295
2296
2297
2298Bergman, et al. Standards Track [Page 41]
2299\f
2300RFC 3805 Printer MIB v2 June 2004
2301
2302
2303 -- and page, form and finishing
2304 -- instructions.
2305 -- IBM Corporation.
2306 langREGIS(16), -- Remote Graphics Instruction Set,
2307 -- Digital Equipment Corp., Maynard MA
2308 langSCS(17), -- SNA Character String
2309 -- Bi-directional print data stream for
2310 -- SNA LU-1 mode of communication.
2311 -- IBM
2312 langSPDL(18), -- ISO 10180 Standard Page Description
2313 -- Language
2314 -- ISO Standard
2315 langTEK4014(19), -- Tektronix Corp.
2316 langPDS(20),
2317 langIGP(21), -- Printronix Corp.
2318 langCodeV(22), -- Magnum Code-V, Image and printer
2319 -- control language used to control
2320 -- impact/dot-matrix printers.
2321 -- QMS, Inc., Mobile AL
2322 langDSCDSE(23), -- DSC-DSE: Data Stream Compatible and
2323 -- Emulation Bi-directional print data
2324 -- stream for non-SNA (DSC) and SNA LU-3
2325 -- 3270 controller (DSE) communications
2326 -- IBM
2327 langWPS(24), -- Windows Printing System, Resource
2328 -- based command/data stream used by
2329 -- Microsoft At Work Peripherals.
2330 -- Developed by the Microsoft
2331 -- Corporation.
2332 langLN03(25), -- Early DEC-PPL3, Digital Equipment
2333 -- Corp.
2334 langCCITT(26),
2335 langQUIC(27), -- QUIC (Quality Information Code), Page
2336 -- Description Language for laser
2337 -- printers. Included graphics, printer
2338 -- control capability and emulation of
2339 -- other well-known printer.
2340 -- QMS, Inc.
2341 langCPAP(28), -- Common Printer Access Protocol
2342 -- Digital Equipment Corp.
2343 langDecPPL(29), -- Digital ANSI-Compliant Printing
2344 -- Protocol
2345 -- (DEC-PPL)
2346 -- Digital Equipment Corp.
2347 langSimpleText(30),
2348 -- simple-text: character coded data,
2349 -- including NUL, CR , LF, HT, and FF
2350 -- control characters. See ISO 10175
2351
2352
2353
2354Bergman, et al. Standards Track [Page 42]
2355\f
2356RFC 3805 Printer MIB v2 June 2004
2357
2358
2359 -- Document Printing Application (DPA)
2360 -- [ISO10175].
2361 langNPAP(31), -- Network Printer Alliance Protocol
2362 -- (NPAP). This protocol has been
2363 -- superseded by the IEEE 1284.1 TIPSI
2364 -- Std (ref. LangTIPSI(49)).
2365 langDOC(32), -- Document Option Commands, Appears in
2366 -- the data stream between data
2367 -- intended for a page description.
2368 -- QMS, Inc.
2369 langimPress(33), -- imPRESS, Page description language
2370 -- originally developed for the
2371 -- ImageServer product line. A binary
2372 -- language providing representations
2373 -- of text, simple graphics, and some
2374 -- large forms (simple
2375 -- bit-map and CCITT group 3/4
2376 -- encoded).The
2377 -- language was intended to be sent over
2378 -- an 8-bit channel and supported early
2379 -- document preparation languages (e.g.,
2380 -- TeX and TROFF).
2381 -- QMS, Inc.
2382 langPinwriter(34),
2383 -- 24 wire dot matrix printer for
2384 -- USA, Europe, and Asia except
2385 -- Japan.
2386 -- More widely used in Germany, and
2387 -- some Asian countries than in US.
2388 -- NEC
2389 langNPDL(35), -- Page printer for Japanese market.
2390 -- NEC
2391 langNEC201PL(36), -- Serial printer language used in
2392 -- the Japanese market.
2393 -- NEC
2394 langAutomatic(37),
2395 -- Automatic PDL sensing. Automatic
2396 -- sensing of the interpreter
2397 -- language family by the printer
2398 -- examining the document content.
2399 -- Which actual interpreter language
2400 -- families are sensed depends on
2401 -- the printer implementation.
2402 langPages(38), -- Page printer Advanced Graphic
2403 -- Escape Set
2404 -- IBM Japan
2405 langLIPS(39), -- LBP Image Processing System
2406 langTIFF(40), -- Tagged Image File Format (Aldus)
2407
2408
2409
2410Bergman, et al. Standards Track [Page 43]
2411\f
2412RFC 3805 Printer MIB v2 June 2004
2413
2414
2415 langDiagnostic(41),
2416 -- A hex dump of the input to the
2417 -- interpreter
2418 langPSPrinter(42),
2419 -- The PostScript Language used for
2420 -- control (with any PDLs)
2421 -- Adobe Systems Incorporated
2422 langCaPSL(43), -- Canon Print Systems Language
2423 langEXCL(44), -- Extended Command Language
2424 -- Talaris Systems Inc.
2425 langLCDS(45), -- Line Conditioned Data Stream
2426 -- Xerox Corporation
2427 langXES(46), -- Xerox Escape Sequences
2428 -- Xerox Corporation
2429 langPCLXL(47), -- Not in RFC 1759
2430 -- Printer Control Language. Extended
2431 -- language features for printing, and
2432 -- printer control.
2433 -- Hewlett-Packard Co.
2434 langART(48), -- Not in RFC 1759
2435 -- Advanced Rendering Tools (ART).
2436 -- Page Description language
2437 -- originally developed for the Laser
2438 -- Press printers.
2439 -- Technical reference manual: "ART IV
2440 -- Reference Manual", No F33M.
2441 -- Fuji Xerox Co., Ltd.
2442 langTIPSI(49), -- Not in RFC 1759
2443 -- Transport Independent Printer
2444 -- System Interface (ref. IEEE Std.
2445 -- 1284.1)
2446 langPrescribe(50), -- Not in RFC 1759
2447 -- Page description and printer
2448 -- control language. It can be
2449 -- described with ordinary ASCII
2450 -- Technical reference manual:
2451 -- "PRESCRIBE II Programming Manual"
2452 langLinePrinter(51), -- Not in RFC 1759
2453 -- A simple-text character stream which
2454 -- supports the control codes LF, VT,
2455 -- FF, and plus Centronics or
2456 -- Dataproducts Vertical Format Unit
2457 -- (VFU) language is commonly used on
2458 -- many older model line and matrix
2459 -- printers.
2460 langIDP(52), -- Not in RFC 1759
2461 -- Imaging Device Protocol
2462 -- Apple Computer.
2463
2464
2465
2466Bergman, et al. Standards Track [Page 44]
2467\f
2468RFC 3805 Printer MIB v2 June 2004
2469
2470
2471 langXJCL(53), -- Not in RFC 1759
2472 -- Xerox Job Control Language (JCL).
2473 -- A Job Control language originally
2474 -- developed for the LaserPress printers
2475 -- and is capable of switching PDLs.
2476 -- Technical reference manual:
2477 -- "ART IV Reference Manual", No F33M.
2478 -- Fuji Xerox Co., Ltd.
2479 langPDF(54), -- Not in RFC 1759
2480 -- Adobe Portable Document Format
2481 -- Adobe Systems, Inc.
2482 langRPDL(55), -- Not in RFC 1759
2483 -- Ricoh Page Description Language for
2484 -- printers.
2485 -- Technical manual "RPDL command
2486 -- reference" No.307029
2487 -- RICOH, Co. LTD
2488 langIntermecIPL(56), -- Not in RFC 1759
2489 -- Intermec Printer Language for label
2490 -- printers.
2491 -- Technical Manual: "IPL Programmers
2492 -- Reference Manual"
2493 -- Intermec Corporation
2494 langUBIFingerprint(57), -- Not in RFC 1759
2495 -- An intelligent basic-like programming
2496 -- language for label printers.
2497 -- Reference Manual: "UBI Fingerprint
2498 -- 7.1", No. 1-960434-00
2499 -- United Barcode Industries
2500 langUBIDirectProtocol(58), -- Not in RFC 1759
2501 -- An intelligent control language for
2502 -- label printers.
2503 -- Programmers guide: " UBI Direct
2504 -- Protocol", No. 1-960419-00
2505 -- United Barcode Industries
2506 langFujitsu(59), -- Not in RFC 1759
2507 -- Fujitsu Printer Language
2508 -- Reference Manual:
2509 -- "FM Printer Sequence" No. 80HP-0770
2510 -- FUJITSU LIMITED
2511 langCGM(60), -- Not in RFC 1759
2512 -- Computer Graphics Metafile
2513 -- MIME type 'image/cgm'
2514 langJPEG(61), -- Not in RFC 1759
2515 -- Joint Photographic Experts Group
2516 -- MIME type 'image/jpeg'
2517 langCALS1(62), -- Not in RFC 1759
2518 -- US DOD CALS1 (see MIL-STD-1840)
2519
2520
2521
2522Bergman, et al. Standards Track [Page 45]
2523\f
2524RFC 3805 Printer MIB v2 June 2004
2525
2526
2527 -- MIME type 'application/cals-1840'
2528 langCALS2(63), -- Not in RFC 1759
2529 -- US DOD CALS2 (see MIL-STD-1840)
2530 -- MIME type 'application/cals-1840'
2531 langNIRS(64), -- Not in RFC 1759
2532 -- US DOD NIRS (see MIL-STD-1840)
2533 -- MIME type 'application/cals-1840'
2534 langC4(65) -- Not in RFC 1759
2535 -- US DOD C4 (see MIL-STD-1840)
2536 -- MIME type 'application/cals-1840'
2537}
2538
2539--
2540-- Input/Output Group TEXTUAL-CONVENTIONs
2541--
2542
2543PrtInputTypeTC ::= TEXTUAL-CONVENTION
2544 -- This TC was extracted from prtInputType in RFC 1759.
2545 STATUS current
2546 DESCRIPTION
2547 "The type of technology (discriminated primarily according to
2548 feeder mechanism type) employed by a specific component or
2549 components."
2550 SYNTAX INTEGER {
2551 other(1),
2552 unknown(2),
2553 sheetFeedAutoRemovableTray(3),
2554 sheetFeedAutoNonRemovableTray(4),
2555 sheetFeedManual(5),
2556 continuousRoll(6),
2557 continuousFanFold(7)
2558 }
2559
2560PrtOutputTypeTC ::= TEXTUAL-CONVENTION
2561 -- This TC was extracted from prtOutputType in RFC 1759.
2562 STATUS current
2563 DESCRIPTION
2564 "The Type of technology supported by this output subunit."
2565 SYNTAX INTEGER {
2566 other(1),
2567 unknown(2),
2568 removableBin(3),
2569 unRemovableBin(4),
2570 continuousRollDevice(5),
2571 mailBox(6),
2572 continuousFanFold(7)
2573 }
2574
2575
2576
2577
2578Bergman, et al. Standards Track [Page 46]
2579\f
2580RFC 3805 Printer MIB v2 June 2004
2581
2582
2583--
2584-- Marker Group TEXTUAL-CONVENTIONs
2585--
2586
2587PrtMarkerMarkTechTC ::= TEXTUAL-CONVENTION
2588 -- This TC was extracted from prtMarkerMarkTech in RFC 1759.
2589 STATUS current
2590 DESCRIPTION
2591 "The type of marking technology used for this marking
2592 subunit."
2593 SYNTAX INTEGER {
2594 other(1),
2595 unknown(2),
2596 electrophotographicLED(3),
2597 electrophotographicLaser(4),
2598 electrophotographicOther(5),
2599 impactMovingHeadDotMatrix9pin(6),
2600 impactMovingHeadDotMatrix24pin(7),
2601 impactMovingHeadDotMatrixOther(8),
2602 impactMovingHeadFullyFormed(9),
2603 impactBand(10),
2604 impactOther(11),
2605 inkjetAqueous(12),
2606 inkjetSolid(13),
2607 inkjetOther(14),
2608 pen(15),
2609 thermalTransfer(16),
2610 thermalSensitive(17),
2611 thermalDiffusion(18),
2612 thermalOther(19),
2613 electroerosion(20),
2614 electrostatic(21),
2615 photographicMicrofiche(22),
2616 photographicImagesetter(23),
2617 photographicOther(24),
2618 ionDeposition(25),
2619 eBeam(26),
2620 typesetter(27)
2621 }
2622
2623PrtMarkerSuppliesTypeTC ::= TEXTUAL-CONVENTION
2624 -- This TC was extracted from prtMarkerSuppliesType in RFC 1759.
2625 STATUS current
2626 DESCRIPTION
2627 "The type of this supply."
2628 SYNTAX INTEGER {
2629 other(1),
2630 unknown(2),
2631
2632
2633
2634Bergman, et al. Standards Track [Page 47]
2635\f
2636RFC 3805 Printer MIB v2 June 2004
2637
2638
2639 -- Values for Printer MIB
2640 toner(3),
2641 wasteToner(4),
2642 ink(5),
2643 inkCartridge(6),
2644 inkRibbon(7),
2645 wasteInk(8),
2646 opc(9), -- photo conductor
2647 developer(10),
2648 fuserOil(11),
2649 solidWax(12),
2650 ribbonWax(13),
2651 wasteWax(14),
2652 fuser(15), -- Not in RFC 1759
2653 coronaWire(16), -- Not in RFC 1759
2654 fuserOilWick(17), -- Not in RFC 1759
2655 cleanerUnit(18), -- Not in RFC 1759
2656 fuserCleaningPad(19), -- Not in RFC 1759
2657 transferUnit(20), -- Not in RFC 1759
2658 tonerCartridge(21), -- Not in RFC 1759
2659 fuserOiler(22), -- Not in RFC 1759
2660 -- End of values for Printer MIB
2661 -- Values for Finisher MIB
2662 water(23), -- Not in RFC 1759
2663 wasteWater(24), -- Not in RFC 1759
2664 glueWaterAdditive(25),-- Not in RFC 1759
2665 wastePaper(26), -- Not in RFC 1759
2666 bindingSupply(27), -- Not in RFC 1759
2667 bandingSupply(28), -- Not in RFC 1759
2668 stitchingWire(29), -- Not in RFC 1759
2669 shrinkWrap(30), -- Not in RFC 1759
2670 paperWrap(31), -- Not in RFC 1759
2671 staples(32), -- Not in RFC 1759
2672 inserts(33), -- Not in RFC 1759
2673 covers(34) -- Not in RFC 1759
2674 -- End of values for Finisher MIB
2675 }
2676
2677--
2678-- Media Path TEXTUAL-CONVENTIONs
2679--
2680
2681PrtMediaPathTypeTC ::= TEXTUAL-CONVENTION
2682 -- This TC was extracted from prtMediaPathType in RFC 1759.
2683 STATUS current
2684 DESCRIPTION
2685 "The type of the media path for this media path."
2686 SYNTAX INTEGER {
2687
2688
2689
2690Bergman, et al. Standards Track [Page 48]
2691\f
2692RFC 3805 Printer MIB v2 June 2004
2693
2694
2695 other(1),
2696 unknown(2),
2697 longEdgeBindingDuplex(3),
2698 shortEdgeBindingDuplex(4),
2699 simplex(5)
2700 }
2701
2702--
2703-- Console Group TEXTUAL-CONVENTIONs
2704--
2705
2706PrtConsoleColorTC ::= TEXTUAL-CONVENTION
2707 -- This TC was extracted from prtConsoleColor in RFC 1759.
2708 STATUS current
2709 DESCRIPTION
2710 "The color of this light."
2711 SYNTAX INTEGER {
2712 other(1),
2713 unknown(2),
2714 white(3),
2715 red(4),
2716 green(5),
2717 blue(6),
2718 cyan(7),
2719 magenta(8),
2720 yellow(9),
2721 orange(10) -- Not in RFC 1759
2722 }
2723
2724PrtConsoleDisableTC ::= TEXTUAL-CONVENTION
2725 -- This TC was extracted from prtConsoleDisable in RFC 1759.
2726 STATUS current
2727 DESCRIPTION
2728 "This value indicates whether or not input is accepted from
2729 the operator console. A value of 'enabled' indicates that
2730 input is accepted from the console, and a value of 'disabled'
2731 indicates that input is not accepted from the console. "
2732 SYNTAX INTEGER {
2733 enabled(3),
2734 disabled(4)
2735 }
2736
2737--
2738-- Alert Group TEXTUAL-CONVENTIONs
2739--
2740
2741PrtAlertTrainingLevelTC ::= TEXTUAL-CONVENTION
2742 -- This TC was extracted from prtAlertTrainingLevel in RFC 1759.
2743
2744
2745
2746Bergman, et al. Standards Track [Page 49]
2747\f
2748RFC 3805 Printer MIB v2 June 2004
2749
2750
2751 STATUS current
2752 DESCRIPTION
2753 "The level of training required to handle this alert, if
2754 human intervention is required. The noInterventionRequired
2755 value should be used if the event does not require any human
2756 intervention. The training level is an enumeration that is
2757 determined and assigned by the printer manufacturer based on
2758 the information or training required to handle this alert.
2759 The printer will break alerts into these different training
2760 levels. It is the responsibility of a management application
2761 in the system to determine how a particular alert is handled
2762 and how and to whom that alert is routed. The following are
2763 the four training levels of alerts:
2764
2765 Field Service - Alerts that typically require advanced
2766 training and technical knowledge of the printer and its
2767 subunits. An example of a technical person would be a
2768 manufacturer's Field Service representative, or other
2769 person formally trained by the manufacturer or similar
2770 representative.
2771 Trained - Alerts that require an intermediate or moderate
2772 knowledge of the printer and its subunits. A typical
2773 example of such an alert is replacing a toner cartridge.
2774 Untrained - Alerts that can be fixed without prior
2775 training either because the action to correct the alert
2776 is obvious or the printer can help the untrained person
2777 fix the problem. A typical example of such an alert is
2778 reloading paper trays or emptying output bins on a low
2779 end printer.
2780 Management - Alerts that have to do with overall operation
2781 of and configuration of the printer. Examples of such
2782 management events are configuration change of subunits."
2783 SYNTAX INTEGER {
2784 other(1),
2785 unknown(2),
2786 untrained(3),
2787 trained(4),
2788 fieldService(5),
2789 management(6),
2790 noInterventionRequired(7) -- Not in RFC 1759
2791 }
2792
2793PrtAlertGroupTC ::= TEXTUAL-CONVENTION
2794 -- Values in the range 1 to 29 must not be IANA-assigned without
2795 -- re-publishing Printer MIB.
2796 -- Values of 30 and greater are for use in MIBs that augment
2797 -- the Printer MIB, such as the Finisher MIB.
2798 -- This TC extracted from prtAlertGroup in RFC 1759.
2799
2800
2801
2802Bergman, et al. Standards Track [Page 50]
2803\f
2804RFC 3805 Printer MIB v2 June 2004
2805
2806
2807 STATUS current
2808 DESCRIPTION
2809 "The type of subunit within the printer model that this alert
2810 is related. Input, output, and markers are examples of
2811 printer model groups, i.e., examples of types of subunits.
2812 Wherever possible, the enumerations match the sub-identifier
2813 that identifies the relevant table in the Printer MIB.
2814
2815 NOTE: Alert type codes have been added for the Host Resources
2816 MIB storage table and device table. These additional types
2817 are for situations in which the printer's storage and device
2818 objects must generate alerts (and possibly traps for critical
2819 alerts)."
2820 SYNTAX INTEGER {
2821 other(1),
2822 -- (2) is reserved for conformance information
2823 -- Values for Host Resources MIB
2824 hostResourcesMIBStorageTable(3),
2825 hostResourcesMIBDeviceTable(4),
2826 -- Values for Printer MIB
2827 generalPrinter(5),
2828 cover(6),
2829 localization(7),
2830 input(8),
2831 output(9),
2832 marker(10),
2833 markerSupplies(11),
2834 markerColorant(12),
2835 mediaPath(13),
2836 channel(14),
2837 interpreter(15),
2838 consoleDisplayBuffer(16),
2839 consoleLights(17),
2840 alert(18), -- Not in RFC 1759
2841 -- Values (5) to (29) reserved for Printer MIB
2842 -- Values for Finisher MIB
2843 finDevice(30), -- Not in RFC 1759
2844 finSupply(31), -- Not in RFC 1759
2845 finSupplyMediaInput(32), -- Not in RFC 1759
2846 finAttribute(33) -- Not in RFC 1759
2847 -- Values (30) to (39) reserved for Finisher MIB
2848 }
2849
2850PrtAlertCodeTC ::= TEXTUAL-CONVENTION
2851 -- This TC was extracted from prtAlertCode in RFC 1759.
2852 STATUS current
2853 DESCRIPTION
2854 "The code that describes the type of alert for this entry in
2855
2856
2857
2858Bergman, et al. Standards Track [Page 51]
2859\f
2860RFC 3805 Printer MIB v2 June 2004
2861
2862
2863 the table. Binary change event alerts describe states of the
2864 subunit while unary change event alerts describe a single
2865 event. The same alert code can be used for a binary change
2866 event or a unary change event, depending on implementation.
2867 Also, the same alert code can be used to indicate a critical
2868 or non-critical (warning) alert, depending on implementation.
2869 The value of prtAlertSeverityLevel specifies binary vs. unary
2870 and critical vs. non-critical for each event for the
2871 implementation.
2872
2873 While there are some specific codes for many subunits, the
2874 generic codes should be used for most subunit alerts. The
2875 network management station can then query the subunit
2876 specified by prtAlertGroup to determine further subunit
2877 status and other subunit information.
2878
2879 An agent shall not add two entries to the alert table for the
2880 same event, one containing a generic event code and the other
2881 containing a specific event code; the agent shall add only
2882 one entry in the alert table for each event; either generic
2883 (preferred) or specific, not both.
2884
2885 Implementation of the unary change event
2886 alertRemovalOfBinaryChangeEntry(1801) is optional. When
2887 implemented, this alert code shall indicate to network
2888 management stations that the trailing edge of a binary change
2889 event has occurred and the corresponding alert entry has been
2890 removed from the alert table. As with all events, the
2891 alertRemovalOfBinaryChangeEntry(1801) alert shall be placed
2892 at the end of the alert table. Such an alert table entry
2893 shall specify the following information:
2894
2895 prtAlertSeverityLevel warningUnaryChangeEvent(4)
2896 prtAlertTrainingLevel noInterventionRequired(7)
2897 prtAlertGroup alert(18)
2898 prtAlertGroupIndex the index of the row in the
2899 alert table of the binary
2900 change event that this event
2901 has removed.
2902 prtAlertLocation unknown (-2)
2903 prtAlertCode alertRemovalOfBinaryChangeEntry(1801)
2904 prtAlertDescription <description or null string>
2905 prtAlertTime the value of sysUpTime at
2906 the time of the removal of the
2907 binary change event from the
2908 alert table.
2909
2910 Optionally, the agent may generate a trap coincident with
2911
2912
2913
2914Bergman, et al. Standards Track [Page 52]
2915\f
2916RFC 3805 Printer MIB v2 June 2004
2917
2918
2919 removing the binary change event and placing the unary change
2920 event alertRemovalOfBinaryChangeEntry(1801) in the alert
2921 table. For such a trap, the prtAlertIndex sent with the above
2922 trap parameters shall be the index of the
2923 alertRemovalOfBinaryChangeEvent row that was added to the
2924 prtAlertTable; not the index of the row that was removed from
2925 the prtAlertTable."
2926 SYNTAX INTEGER {
2927 other(1),
2928 -- an event that is not represented
2929 -- by one of the alert codes
2930 -- specified below.
2931 unknown(2),
2932 -- The following generic codes are common to
2933 -- multiple groups. The NMS may examine the
2934 -- prtAlertGroup object to determine what group
2935 -- to query for further information.
2936 coverOpen(3),
2937 coverClosed(4),
2938 interlockOpen(5),
2939 interlockClosed(6),
2940 configurationChange(7),
2941 jam(8),
2942 subunitMissing(9), -- Not in RFC 1759
2943 -- The subunit tray, bin, etc.
2944 -- has been removed.
2945 subunitLifeAlmostOver(10), -- Not in RFC 1759
2946 subunitLifeOver(11), -- Not in RFC 1759
2947 subunitAlmostEmpty(12), -- Not in RFC 1759
2948 subunitEmpty(13), -- Not in RFC 1759
2949 subunitAlmostFull(14), -- Not in RFC 1759
2950 subunitFull(15), -- Not in RFC 1759
2951 subunitNearLimit(16), -- Not in RFC 1759
2952 subunitAtLimit(17), -- Not in RFC 1759
2953 subunitOpened(18), -- Not in RFC 1759
2954 subunitClosed(19), -- Not in RFC 1759
2955 subunitTurnedOn(20), -- Not in RFC 1759
2956 subunitTurnedOff(21), -- Not in RFC 1759
2957 subunitOffline(22), -- Not in RFC 1759
2958 subunitPowerSaver(23), -- Not in RFC 1759
2959 subunitWarmingUp(24), -- Not in RFC 1759
2960 subunitAdded(25), -- Not in RFC 1759
2961 subunitRemoved(26), -- Not in RFC 1759
2962 subunitResourceAdded(27), -- Not in RFC 1759
2963 subunitResourceRemoved(28), -- Not in RFC 1759
2964 subunitRecoverableFailure(29),
2965 -- Not in RFC 1759
2966 subunitUnrecoverableFailure(30),
2967
2968
2969
2970Bergman, et al. Standards Track [Page 53]
2971\f
2972RFC 3805 Printer MIB v2 June 2004
2973
2974
2975 -- Not in RFC 1759
2976 subunitRecoverableStorageError(31),
2977 -- Not in RFC 1759
2978 subunitUnrecoverableStorageError(32),
2979 -- Not in RFC 1759
2980 subunitMotorFailure(33), -- Not in RFC 1759
2981 subunitMemoryExhausted(34), -- Not in RFC 1759
2982 subunitUnderTemperature(35), -- Not in RFC 1759
2983 subunitOverTemperature(36), -- Not in RFC 1759
2984 subunitTimingFailure(37), -- Not in RFC 1759
2985 subunitThermistorFailure(38), -- Not in RFC 1759
2986
2987 -- General Printer group
2988 doorOpen(501), -- DEPRECATED
2989 -- Use coverOpened(3)
2990 doorClosed(502), -- DEPRECATED
2991 -- Use coverClosed(4)
2992 powerUp(503),
2993 powerDown(504),
2994 printerNMSReset(505), -- Not in RFC 1759
2995 -- The printer has been reset by some
2996 -- network management station(NMS)
2997 -- writing into 'prtGeneralReset'.
2998 printerManualReset(506), -- Not in RFC 1759
2999 -- The printer has been reset manually.
3000 printerReadyToPrint(507), -- Not in RFC 1759
3001 -- The printer is ready to print. (i.e.,
3002 -- not warming up, not in power save
3003 -- state, not adjusting print quality,
3004 -- etc.).
3005
3006 -- Input Group
3007 inputMediaTrayMissing(801),
3008 inputMediaSizeChange(802),
3009 inputMediaWeightChange(803),
3010 inputMediaTypeChange(804),
3011 inputMediaColorChange(805),
3012 inputMediaFormPartsChange(806),
3013 inputMediaSupplyLow(807),
3014 inputMediaSupplyEmpty(808),
3015 inputMediaChangeRequest(809), -- Not in RFC 1759
3016 -- An interpreter has detected that a
3017 -- different medium is need in this input
3018 -- tray subunit. The prtAlertDescription may
3019 -- be used to convey a human readable
3020 -- description of the medium required to
3021 -- satisfy the request.
3022 inputManualInputRequest(810), -- Not in RFC 1759
3023
3024
3025
3026Bergman, et al. Standards Track [Page 54]
3027\f
3028RFC 3805 Printer MIB v2 June 2004
3029
3030
3031 -- An interpreter has detected that manual
3032 -- input is required in this subunit. The
3033 -- prtAlertDescription may be used to convey
3034 -- a human readable description of the medium
3035 -- required to satisfy the request.
3036 inputTrayPositionFailure(811), -- Not in RFC 1759
3037 -- The input tray failed to position correctly.
3038 inputTrayElevationFailure(812),
3039 -- Not in RFC 1759
3040 inputCannotFeedSizeSelected(813),
3041 -- Not in RFC 1759
3042 -- Output Group
3043 outputMediaTrayMissing(901),
3044 outputMediaTrayAlmostFull(902),
3045 outputMediaTrayFull(903),
3046 outputMailboxSelectFailure(904),
3047 -- Not in RFC 1759
3048 -- Marker group
3049 markerFuserUnderTemperature(1001),
3050 markerFuserOverTemperature(1002),
3051 markerFuserTimingFailure(1003),
3052 -- Not in RFC 1759
3053 markerFuserThermistorFailure(1004),
3054 -- Not in RFC 1759
3055 markerAdjustingPrintQuality(1005),
3056 -- Not in RFC 1759
3057 -- Marker Supplies group
3058 markerTonerEmpty(1101),
3059 markerInkEmpty(1102),
3060 markerPrintRibbonEmpty(1103),
3061 markerTonerAlmostEmpty(1104),
3062 markerInkAlmostEmpty(1105),
3063 markerPrintRibbonAlmostEmpty(1106),
3064 markerWasteTonerReceptacleAlmostFull(1107),
3065 markerWasteInkReceptacleAlmostFull(1108),
3066 markerWasteTonerReceptacleFull(1109),
3067 markerWasteInkReceptacleFull(1110),
3068 markerOpcLifeAlmostOver(1111),
3069 markerOpcLifeOver(1112),
3070 markerDeveloperAlmostEmpty(1113),
3071 markerDeveloperEmpty(1114),
3072 markerTonerCartridgeMissing(1115),
3073 -- Not in RFC 1759
3074 -- Media Path Device Group
3075 mediaPathMediaTrayMissing(1301),
3076 mediaPathMediaTrayAlmostFull(1302),
3077 mediaPathMediaTrayFull(1303),
3078 mediaPathCannotDuplexMediaSelected(1304),
3079
3080
3081
3082Bergman, et al. Standards Track [Page 55]
3083\f
3084RFC 3805 Printer MIB v2 June 2004
3085
3086
3087 -- Not in RFC 1759
3088 -- Interpreter Group
3089 interpreterMemoryIncrease(1501),
3090 interpreterMemoryDecrease(1502),
3091 interpreterCartridgeAdded(1503),
3092 interpreterCartridgeDeleted(1504),
3093 interpreterResourceAdded(1505),
3094 interpreterResourceDeleted(1506),
3095 interpreterResourceUnavailable(1507),
3096 interpreterComplexPageEncountered(1509),
3097 -- Not in RFC 1759
3098 -- The interpreter has encountered a page
3099 -- that is too complex for the resources that
3100 -- are available.
3101 -- Alert Group
3102 alertRemovalOfBinaryChangeEntry(1801)
3103 -- Not in RFC 1759
3104 -- A binary change event entry has been
3105 -- removed from the alert table. This unary
3106 -- change alert table entry is added to the
3107 -- end of the alert table.
3108 }
3109END
3110
31116. The Printer MIB
3112
3113Printer-MIB DEFINITIONS ::= BEGIN
3114
3115IMPORTS
3116 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, TimeTicks,
3117 NOTIFICATION-TYPE, OBJECT-IDENTITY,
3118 mib-2 FROM SNMPv2-SMI -- [RFC2578]
3119 TEXTUAL-CONVENTION FROM SNMPv2-TC -- [RFC2579]
3120 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
3121 FROM SNMPv2-CONF -- [RFC2580]
3122 hrDeviceIndex, hrStorageIndex FROM HOST-RESOURCES-MIB -- [RFC2790]
3123 InterfaceIndexOrZero FROM IF-MIB -- [RFC2863]
3124 PrtCoverStatusTC, PrtGeneralResetTC, PrtChannelTypeTC,
3125 PrtInterpreterLangFamilyTC, PrtInputTypeTC, PrtOutputTypeTC,
3126 PrtMarkerMarkTechTC, PrtMarkerSuppliesTypeTC, PrtConsoleColorTC,
3127 PrtConsoleDisableTC, PrtMediaPathTypeTC, PrtAlertGroupTC,
3128 PrtAlertTrainingLevelTC, PrtAlertCodeTC
3129 FROM IANA-PRINTER-MIB
3130 IANACharset FROM IANA-CHARSET-MIB;
3131
3132printmib MODULE-IDENTITY
3133 LAST-UPDATED "200406020000Z"
3134 ORGANIZATION "PWG IEEE/ISTO Printer Working Group"
3135
3136
3137
3138Bergman, et al. Standards Track [Page 56]
3139\f
3140RFC 3805 Printer MIB v2 June 2004
3141
3142
3143 CONTACT-INFO
3144 "Harry Lewis
3145 IBM
3146 Phone (303) 924-5337
3147 Email: harryl@us.ibm.com
3148 http://www.pwg.org/index.html
3149
3150 Send comments to the printmib WG using the Printer MIB
3151 Project (PMP) Mailing List: pmp@pwg.org
3152
3153 For further information, access the PWG web page under 'Printer
3154 MIB': http://www.pwg.org/
3155
3156 Implementers of this specification are encouraged to join the
3157 pmp mailing list in order to participate in discussions on any
3158 clarifications needed and registration proposals being reviewed
3159 in order to achieve consensus."
3160 DESCRIPTION
3161 "The MIB module for management of printers.
3162 Copyright (C) The Internet Society (2004). This
3163 version of this MIB module was published
3164 in RFC 3805. For full legal notices see the RFC itself."
3165 REVISION "200406020000Z"
3166 DESCRIPTION
3167 "Printer MIB v2.
3168 Moved all enum groups to be maintained by IANA into new TCs
3169 within the ianaPrinterMIB, which is contained in this
3170 document.
3171 New TCs created from enums defined within RFC 1759 Objects:
3172 PrtPrintOrientationTC, PrtLocalizedDescriptionStringTC,
3173 PrtConsoleDescriptionStringTC, PrtChannelStateTC,
3174 PrtOutputStackingOrderTC, PrtOutputPageDeliveryOrientationTC,
3175 PrtMarkerCounterUnitTC, PrtMarkerSuppliesSupplyUnitTC,
3176 PrtMarkerSuppliesClassTC, PrtMarkerAddressabilityUnitTC,
3177 PrtMarkerColorantRoleTC, PrtMediaPathMaxSpeedPrintUnitTC,
3178 PrtInterpreterTwoWayTC, and PrtAlertSeverityLevelTC.
3179 The following four TCs have been deprecated:
3180 MediaUnit (replaced by PrtMediaUnitTC),
3181 CapacityUnit (replaced by PrtCapacityUnitTC),
3182 SubUnitStatus (replaced by PrtSubUnitStatusTC),
3183 CodedCharSet (replaced by IANACharset in IANA Charset MIB)
3184 Five new OBJECT-GROUPs: prtAuxilliarySheetGroup,
3185 prtInputSwitchingGroup, prtGeneralV2Group,
3186 prtAlertTableV2Group, prtChannelV2Group.
3187 Nine new objects added to those groups:
3188 prtAuxiliarySheetStartupPage, prtAuxiliarySheetBannerPage,
3189 prtGeneralPrinterName, prtGeneralSerialNumber,
3190 prtAlertCriticalEvents, prtAlertAllEvents,
3191
3192
3193
3194Bergman, et al. Standards Track [Page 57]
3195\f
3196RFC 3805 Printer MIB v2 June 2004
3197
3198
3199 prtInputMediaLoadTimeout, prtInputNextIndex,
3200 prtChannelInformation.
3201 SYNTAX range changed from (0..65535) to (1..65535) for the
3202 index objects prtStorageRefSeqNumber, prtDeviceRefSeqNumber,
3203 and prtConsoleLightIndex.
3204 SYNTAX range changed from (0..65535) to (0..2147483647) for the
3205 objects prtStorageRefIndex and prtDeviceRefIndex to agree
3206 with the Host Resources MIB.
3207 Defined a range for the objects with a SYNTAX of Integer32:
3208 prtOutputDefaultIndex, prtInputMediaDimFeedDirDeclared,
3209 prtInputMediaDimXFeedDirDeclared, prtInputMaxCapacity,
3210 prtInputCurrentLevel, prtInputMediaDimFeedDirChosen,
3211 prtInputMediaDimXFeedDirChosen, prtInputMediaWeight,
3212 prtInputMediaFormParts, prtOutputIndex,
3213 prtOutputMaxCapacity, prtOutputRemainingCapacity,
3214 prtOutputMaxDimFeedDir, prtOutputMaxDimXFeedDir,
3215 prtOutputMinDimFeedDir, prtOutputMinDimXFeedDir,
3216 prtMarkerAddressibilityFeedDir,
3217 prtMarkerAddressibilityXFeedDir, prtMarkerNorthMargin,
3218 prtMarkerSouthMargin, prtMarkerWestMargin,
3219 prtMarkerEastMargin, prtMarkerSuppliesMaxCapacity,
3220 prtMarkerSuppliesLevel, prtMarkerColorantTonality,
3221 prtMediaPathMaxSpeed, prtMediaPathMaxMediaFeedDir,
3222 prtMediaPathMaxMediaXFeedDir, prtMediaPathMinMediaFeedDir,
3223 prtMediaPathMinMediaXFeedDir, prtChannelIndex,
3224 prtChannelCurrentJobCntlLangIndex, prtInterpreterIndex,
3225 prtChannelDefaultPageDescLangIndex, prtConsoleOnTime,
3226 prtInterpreterFeedAddressibility, prtConsoleOffTime,
3227 prtInterpreterXFeedAddressibility, prtAlertIndex,
3228 prtAlertGroupIndex, prtAlertLocation.
3229 Changed SYNTAX from Integer32 to InterfaceIndexOrZero for
3230 prtChannelIfIndex.
3231 Changed MAX-ACCESS of prtAlertIndex from not-accessible to
3232 Read-only and added a compliance statement to allow a
3233 MIN-ACCESS of accessible-for-notify.
3234 One new NOTIFICATION-GROUP: prtAlertTrapGroup which contains
3235 printerV2Alert.
3236 In MODULE-COMPLIANCE prtMIBCompliance, new OBJECT-GROUPs and
3237 the NOTIFICATION_GROUP, all in GROUP (not MANDATORY-GROUP)
3238 clauses. The nine new objects are optional, i.e., this
3239 document is backward compatible with RFC 1759."
3240 REVISION "199411250000Z"
3241 DESCRIPTION
3242 "The original version of this MIB, published as RFC1759."
3243 ::= { mib-2 43 }
3244
3245
3246
3247
3248
3249
3250Bergman, et al. Standards Track [Page 58]
3251\f
3252RFC 3805 Printer MIB v2 June 2004
3253
3254
3255-- TEXTUAL-CONVENTIONs for this MIB module
3256--
3257-- Generic unspecific TEXTUAL-CONVENTIONs
3258--
3259
3260PrtMediaUnitTC ::= TEXTUAL-CONVENTION
3261 -- Replaces MediaUnit in RFC 1759.
3262 STATUS current
3263 DESCRIPTION
3264 "Units of measure for media dimensions."
3265 SYNTAX INTEGER {
3266 tenThousandthsOfInches(3), -- .0001
3267 micrometers(4)
3268 }
3269
3270MediaUnit ::= TEXTUAL-CONVENTION
3271 -- Replaced by PrtMediaUnitTC.
3272 STATUS deprecated
3273 DESCRIPTION
3274 "Units of measure for media dimensions."
3275 SYNTAX INTEGER {
3276 tenThousandthsOfInches(3), -- .0001
3277 micrometers(4)
3278 }
3279
3280PrtCapacityUnitTC ::= TEXTUAL-CONVENTION
3281 -- Replaces CapacityUnit in RFC 1759.
3282 STATUS current
3283 DESCRIPTION
3284 "Units of measure for media capacity."
3285 SYNTAX INTEGER {
3286 other(1), -- New, not in RFC 1759
3287 unknown(2), -- New, not in RFC 1759
3288 tenThousandthsOfInches(3), -- .0001
3289 micrometers(4),
3290 sheets(8),
3291 feet(16),
3292 meters(17),
3293 -- Values for Finisher MIB
3294 items(18), -- New, not in RFC 1759
3295 percent(19) -- New, not in RFC 1759
3296 }
3297
3298CapacityUnit ::= TEXTUAL-CONVENTION
3299 -- Replaced by PrtCapacityUnitTC.
3300 STATUS deprecated
3301 DESCRIPTION
3302 "Units of measure for media capacity."
3303
3304
3305
3306Bergman, et al. Standards Track [Page 59]
3307\f
3308RFC 3805 Printer MIB v2 June 2004
3309
3310
3311 SYNTAX INTEGER {
3312 tenThousandthsOfInches(3), -- .0001
3313 micrometers(4),
3314 sheets(8),
3315 feet(16),
3316 meters(17)
3317 }
3318
3319PrtPrintOrientationTC ::= TEXTUAL-CONVENTION
3320 -- This TC was extracted from prtInterpreterDefaultOrientation in
3321 -- RFC 1759.
3322 STATUS current
3323 DESCRIPTION
3324 "A generic representation for printing orientation on a
3325 'page'."
3326 SYNTAX INTEGER {
3327 other(1),
3328 portrait(3),
3329 landscape(4)
3330 }
3331
3332PrtSubUnitStatusTC ::= TEXTUAL-CONVENTION
3333 -- Replaces SubUnitStatus in RFC 1759.
3334 STATUS current
3335 DESCRIPTION
3336 "Status of a printer sub-unit.
3337
3338 The SubUnitStatus is an integer that is the sum of 5 distinct
3339 values, Availability, Non-Critical, Critical, On-line, and
3340 Transitioning. These values are:
3341
3342 Availability Value
3343
3344 Available and Idle 0 0000'b
3345 Available and Standby 2 0010'b
3346 Available and Active 4 0100'b
3347 Available and Busy 6 0110'b
3348 Unavailable and OnRequest 1 0001'b
3349 Unavailable because Broken 3 0011'b
3350 Unknown 5 0101'b
3351
3352 Non-Critical
3353 No Non-Critical Alerts 0 0000'b
3354 Non-Critical Alerts 8 1000'b
3355
3356 Critical
3357
3358 No Critical Alerts 0 0000'b
3359
3360
3361
3362Bergman, et al. Standards Track [Page 60]
3363\f
3364RFC 3805 Printer MIB v2 June 2004
3365
3366
3367 Critical Alerts 16 1 0000'b
3368
3369 On-Line
3370
3371 State is On-Line 0 0000'b
3372 State is Off-Line 32 10 0000'b
3373
3374 Transitioning
3375
3376 At intended state 0 0000'b
3377 Transitioning to intended state 64 100 0000'b"
3378
3379 SYNTAX INTEGER (0..126)
3380
3381SubUnitStatus ::= TEXTUAL-CONVENTION
3382 -- Replaced by PrtSubUnitStatusTC.
3383 STATUS deprecated
3384 DESCRIPTION
3385 "Status of a printer sub-unit.
3386
3387 The SubUnitStatus is an integer that is the sum of 5 distinct
3388 values, Availability, Non-Critical, Critical, On-line, and
3389 Transitioning. These values are:
3390
3391 Availability Value
3392 Available and Idle 0 0000'b
3393 Available and Standby 2 0010'b
3394 Available and Active 4 0100'b
3395 Available and Busy 6 0110'b
3396 Unavailable and OnRequest 1 0001'b
3397 Unavailable because Broken 3 0011'b
3398 Unknown 5 0101'b
3399
3400 Non-Critical
3401 No Non-Critical Alerts 0 0000'b
3402 Non-Critical Alerts 8 1000'b
3403
3404 Critical
3405
3406 No Critical Alerts 0 0000'b
3407 Critical Alerts 16 1 0000'b
3408
3409 On-Line
3410
3411 State is On-Line 0 0000'b
3412 State is Off-Line 32 10 0000'b
3413
3414 Transitioning
3415
3416
3417
3418Bergman, et al. Standards Track [Page 61]
3419\f
3420RFC 3805 Printer MIB v2 June 2004
3421
3422
3423 At intended state 0 0000'b
3424 Transitioning to intended state 64 100 0000'b"
3425
3426 SYNTAX INTEGER (0..126)
3427
3428PresentOnOff ::= TEXTUAL-CONVENTION
3429 STATUS current
3430 DESCRIPTION
3431 "Presence and configuration of a device or feature."
3432 SYNTAX INTEGER {
3433 other(1),
3434 on(3),
3435 off(4),
3436 notPresent(5)
3437 }
3438
3439PrtLocalizedDescriptionStringTC ::= TEXTUAL-CONVENTION
3440 -- This TC did not appear in RFC 1759.
3441 STATUS current
3442 DESCRIPTION
3443 "An object MUST use this TEXTUAL-CONVENTION when its
3444 'charset' is controlled by the value of
3445 prtGeneralCurrentLocalization."
3446 SYNTAX OCTET STRING (SIZE(0..255))
3447
3448PrtConsoleDescriptionStringTC ::= TEXTUAL-CONVENTION
3449 -- This TC did not appear in RFC 1759.
3450 STATUS current
3451 DESCRIPTION
3452 "An object MUST use this TEXTUAL-CONVENTION when its
3453 'charset' is controlled by the value of
3454 prtConsoleLocalization."
3455 SYNTAX OCTET STRING (SIZE(0..255))
3456
3457CodedCharSet ::= TEXTUAL-CONVENTION
3458
3459 -- Replaced by IANACharset TEXTUAL-CONVENTION in IANA Charset MIB.
3460 STATUS deprecated
3461 DESCRIPTION
3462 "The original description clause from RFC 1759 [RFC1759] was
3463 technically inaccurate and therefore has been deleted."
3464 SYNTAX INTEGER {
3465 other(1) -- used if the designated coded
3466 -- character set is not currently in
3467 -- the enumeration
3468}
3469
3470--
3471
3472
3473
3474Bergman, et al. Standards Track [Page 62]
3475\f
3476RFC 3805 Printer MIB v2 June 2004
3477
3478
3479-- Channel Group TEXTUAL-CONVENTIONs
3480--
3481
3482PrtChannelStateTC ::= TEXTUAL-CONVENTION
3483 -- This TC was extracted from prtChannelState in RFC 1759.
3484 STATUS current
3485 DESCRIPTION
3486 "The state of this print job delivery channel. The value
3487 determines whether print data is allowed through this channel."
3488 SYNTAX INTEGER {
3489 other(1),
3490 printDataAccepted(3),
3491 noDataAccepted(4)
3492 }
3493
3494--
3495-- Input/Output Group TEXTUAL-CONVENTIONs
3496--
3497
3498PrtOutputStackingOrderTC ::= TEXTUAL-CONVENTION
3499 -- This TC was extracted from prtOutputStackingOrder in RFC 1759.
3500 STATUS current
3501 DESCRIPTION
3502 "The current state of the stacking order for the associated
3503 output sub-unit. 'firstToLast' means that as pages are output,
3504 the front of the next page is placed against the back of the
3505 previous page. 'lastToFirst' means that as pages are output,
3506 the back of the next page is placed against the front of the
3507 previous page."
3508 SYNTAX INTEGER {
3509 unknown(2),
3510 firstToLast(3),
3511 lastToFirst(4)
3512 }
3513
3514PrtOutputPageDeliveryOrientationTC ::= TEXTUAL-CONVENTION
3515 -- This TC was extracted from prtOutputPageDeliveryOrientation
3516 -- in RFC 1759.
3517 STATUS current
3518 DESCRIPTION
3519 "The reading surface that will be 'up' when pages are delivered
3520 to the associated output sub-unit. Values are Face-Up and Face
3521 Down (Note: interpretation of these values is, in general,
3522 context-dependent based on locale; presentation of these values
3523 to an end-user should be normalized to the expectations of the
3524 user."
3525 SYNTAX INTEGER {
3526 faceUp(3),
3527
3528
3529
3530Bergman, et al. Standards Track [Page 63]
3531\f
3532RFC 3805 Printer MIB v2 June 2004
3533
3534
3535 faceDown(4)
3536 }
3537
3538--
3539-- Marker Group TEXTUAL-CONVENTIONs
3540--
3541
3542PrtMarkerCounterUnitTC ::= TEXTUAL-CONVENTION
3543 -- This TC was extracted from prtMarkerCounterUnit in RFC 1759.
3544 STATUS current
3545 DESCRIPTION
3546 "The unit that will be used by the printer when reporting
3547 counter values for this marking sub-unit. The
3548 time units of measure are provided for a device like a
3549 strip recorder that does not or cannot track the physical
3550 dimensions of the media and does not use characters,
3551 lines or sheets."
3552
3553 SYNTAX INTEGER {
3554 tenThousandthsOfInches(3), -- .0001
3555 micrometers(4),
3556 characters(5),
3557 lines(6),
3558 impressions(7),
3559 sheets(8),
3560 dotRow(9),
3561 hours(11),
3562 feet(16),
3563 meters(17)
3564 }
3565
3566PrtMarkerSuppliesSupplyUnitTC ::= TEXTUAL-CONVENTION
3567 -- This TC was extracted from prtMarkerSuppliesSupplyUnit
3568 -- in RFC 1759.
3569 STATUS current
3570 DESCRIPTION
3571 "Unit of this marker supply container/receptacle."
3572 SYNTAX INTEGER {
3573 other(1), -- New, not in RFC 1759
3574 unknown(2), -- New, not in RFC 1759
3575 tenThousandthsOfInches(3), -- .0001
3576 micrometers(4),
3577 impressions(7), -- New, not in RFC 1759
3578 sheets(8), -- New, not in RFC 1759
3579 hours(11), -- New, not in RFC 1759
3580 thousandthsOfOunces(12),
3581 tenthsOfGrams(13),
3582 hundrethsOfFluidOunces(14),
3583
3584
3585
3586Bergman, et al. Standards Track [Page 64]
3587\f
3588RFC 3805 Printer MIB v2 June 2004
3589
3590
3591 tenthsOfMilliliters(15),
3592 feet(16), -- New, not in RFC 1759
3593 meters(17), -- New, not in RFC 1759
3594 -- Values for Finisher MIB
3595 items(18), -- e.g., #staples. New, not in RFC 1759
3596 percent(19) -- New, not in RFC 1759
3597 }
3598
3599PrtMarkerSuppliesClassTC ::= TEXTUAL-CONVENTION
3600 -- This TC was extracted from prtMarkerSuppliesClass in RFC 1759.
3601 STATUS current
3602 DESCRIPTION
3603 "Indicates whether this supply entity represents a supply
3604 that is consumed or a receptacle that is filled."
3605 SYNTAX INTEGER {
3606 other(1),
3607 supplyThatIsConsumed(3),
3608 receptacleThatIsFilled(4)
3609 }
3610
3611PrtMarkerColorantRoleTC ::= TEXTUAL-CONVENTION
3612 -- This TC was extracted from prtMarkerColorantRole in RFC 1759.
3613 STATUS current
3614 DESCRIPTION
3615 "The role played by this colorant."
3616 SYNTAX INTEGER { -- Colorant Role
3617 other(1),
3618 process(3),
3619 spot(4)
3620 }
3621
3622PrtMarkerAddressabilityUnitTC ::= TEXTUAL-CONVENTION
3623 -- This TC was extracted from prtMarkerAddressabilityUnit
3624 -- in RFC 1759.
3625 STATUS current
3626 DESCRIPTION
3627 "The unit of measure of distances, as applied to the marker's
3628 resolution."
3629 SYNTAX INTEGER {
3630 tenThousandthsOfInches(3), -- .0001
3631 micrometers(4)
3632 }
3633
3634--
3635-- Media Path TEXTUAL-CONVENTIONs
3636--
3637
3638PrtMediaPathMaxSpeedPrintUnitTC ::= TEXTUAL-CONVENTION
3639
3640
3641
3642Bergman, et al. Standards Track [Page 65]
3643\f
3644RFC 3805 Printer MIB v2 June 2004
3645
3646
3647 -- This TC was extracted from prtMediaPathMaxSpeedPrintUnit
3648 -- in RFC 1759.
3649 STATUS current
3650 DESCRIPTION
3651 "The unit of measure used in specifying the speed of all
3652 media paths in the printer."
3653 SYNTAX INTEGER {
3654 tenThousandthsOfInchesPerHour(3),-- .0001/hour
3655 micrometersPerHour(4),
3656 charactersPerHour(5),
3657 linesPerHour(6),
3658 impressionsPerHour(7),
3659 sheetsPerHour(8),
3660 dotRowPerHour(9),
3661 feetPerHour(16),
3662 metersPerHour(17)
3663 }
3664
3665--
3666-- Interpreter Group TEXTUAL-CONVENTIONs
3667--
3668
3669PrtInterpreterTwoWayTC ::= TEXTUAL-CONVENTION
3670 -- This TC was extracted from prtInterpreterTwoWay in RFC 1759.
3671 STATUS current
3672 DESCRIPTION
3673 "Indicates whether or not this interpreter returns information
3674 back to the host."
3675 SYNTAX INTEGER {
3676 yes(3),
3677 no(4)
3678 }
3679
3680--
3681-- Alert Group TEXTUAL-CONVENTIONs
3682--
3683
3684PrtAlertSeverityLevelTC ::= TEXTUAL-CONVENTION
3685 -- This TC was extracted from prtAlertSeverityLevel in RFC 1759.
3686 STATUS current
3687 DESCRIPTION
3688 "The level of severity of this alert table entry. The printer
3689 determines the severity level assigned to each entry in the
3690 table. A critical alert is binary by nature and definition. A
3691 warning is defined to be a non-critical alert. The original and
3692 most common warning is unary. The binary warning was added later
3693 and given a more distinguished name."
3694 SYNTAX INTEGER {
3695
3696
3697
3698Bergman, et al. Standards Track [Page 66]
3699\f
3700RFC 3805 Printer MIB v2 June 2004
3701
3702
3703 other(1),
3704 critical(3),
3705 warning(4),
3706 warningBinaryChangeEvent(5) -- New, not in RFC 1759
3707 }
3708
3709-- The General Printer Group
3710--
3711-- The general printer sub-unit is responsible for the overall
3712-- control and status of the printer. There is exactly one
3713-- general printer sub-unit in a printer.
3714
3715prtGeneral OBJECT IDENTIFIER ::= { printmib 5 }
3716
3717prtGeneralTable OBJECT-TYPE
3718 SYNTAX SEQUENCE OF PrtGeneralEntry
3719 MAX-ACCESS not-accessible
3720 STATUS current
3721 DESCRIPTION
3722 "A table of general information per printer.
3723 Objects in this table are defined in various
3724 places in the MIB, nearby the groups to
3725 which they apply. They are all defined
3726 here to minimize the number of tables that would
3727 otherwise need to exist."
3728 ::= { prtGeneral 1 }
3729
3730prtGeneralEntry OBJECT-TYPE
3731 SYNTAX PrtGeneralEntry
3732 MAX-ACCESS not-accessible
3733 STATUS current
3734 DESCRIPTION
3735 "An entry exists in this table for each device entry in the
3736 host resources MIB device table with a device type of
3737 'printer'.
3738
3739 NOTE: The above description has been modified from RFC 1759
3740 for clarification."
3741 INDEX { hrDeviceIndex }
3742 ::= { prtGeneralTable 1 }
3743
3744PrtGeneralEntry ::= SEQUENCE {
3745 -- Note that not all of the objects in this sequence are in
3746 -- the general printer group. The group to which an
3747 -- object belongs is tagged with a label "General", "Input"
3748 -- "Output", etc. after each entry in the following sequence.
3749 --
3750 prtGeneralConfigChanges Counter32, -- General
3751
3752
3753
3754Bergman, et al. Standards Track [Page 67]
3755\f
3756RFC 3805 Printer MIB v2 June 2004
3757
3758
3759 prtGeneralCurrentLocalization Integer32, -- General
3760 prtGeneralReset PrtGeneralResetTC,
3761 -- General
3762 prtGeneralCurrentOperator OCTET STRING,
3763 -- Responsible Party
3764 prtGeneralServicePerson OCTET STRING,
3765 -- Responsible Party
3766 prtInputDefaultIndex Integer32, -- Input
3767 prtOutputDefaultIndex Integer32, -- Output
3768 prtMarkerDefaultIndex Integer32, -- Marker
3769 prtMediaPathDefaultIndex Integer32, -- Media Path
3770 prtConsoleLocalization Integer32, -- Console
3771 prtConsoleNumberOfDisplayLines Integer32, -- Console
3772 prtConsoleNumberOfDisplayChars Integer32, -- Console
3773 prtConsoleDisable PrtConsoleDisableTC,
3774 -- Console,
3775 prtAuxiliarySheetStartupPage PresentOnOff,
3776 -- AuxiliarySheet
3777 prtAuxiliarySheetBannerPage PresentOnOff,
3778 -- AuxiliarySheet
3779 prtGeneralPrinterName OCTET STRING,
3780 -- General V2
3781 prtGeneralSerialNumber OCTET STRING,
3782 -- General V2
3783 prtAlertCriticalEvents Counter32, -- Alert V2
3784 prtAlertAllEvents Counter32 -- Alert V2
3785 }
3786
3787prtGeneralConfigChanges OBJECT-TYPE
3788 SYNTAX Counter32
3789 MAX-ACCESS read-only
3790 STATUS current
3791 DESCRIPTION
3792 "Counts configuration changes within the printer. A
3793 configuration change is defined to be an action that results in
3794 a change to any MIB object other than those that reflect status
3795 or level, or those that act as counters or gauges. In addition,
3796 any action that results in a row being added or deleted from
3797 any table in the Printer MIB is considered a configuration
3798 change. Such changes will often affect the capability of the
3799 printer to service certain types of print jobs. Management
3800 applications may cache infrequently changed configuration
3801 information about sub units within the printer. This object
3802 should be incremented whenever the agent wishes to notify
3803 management applications that any cached configuration
3804 information for this device is to be considered 'stale'. At
3805 this point, the management application should flush any
3806 configuration information cached about this device and fetch
3807
3808
3809
3810Bergman, et al. Standards Track [Page 68]
3811\f
3812RFC 3805 Printer MIB v2 June 2004
3813
3814
3815 new configuration information.
3816
3817 The following are examples of actions that would cause the
3818 prtGeneralConfigChanges object to be incremented:
3819
3820 - Adding an output bin
3821 - Changing the media in a sensing input tray
3822 - Changing the value of prtInputMediaType
3823
3824 Note that the prtGeneralConfigChanges counter would not be
3825 incremented when an input tray is temporarily removed to load
3826 additional paper or when the level of an input device changes.
3827
3828 NOTE: The above description has been modified from RFC 1759
3829 for clarification."
3830
3831 ::= { prtGeneralEntry 1 }
3832
3833prtGeneralCurrentLocalization OBJECT-TYPE
3834 SYNTAX Integer32 (1..65535)
3835 MAX-ACCESS read-write
3836 STATUS current
3837 DESCRIPTION
3838 "The value of the prtLocalizationIndex corresponding to the
3839 current language, country, and character set to be used for
3840 localized string values that are identified as being dependent
3841 on the value of this object. Note that this object does not
3842 apply to localized strings in the prtConsole group or to any
3843 object that is not explicitly identified as being localized
3844 according to prtGeneralCurrentLocalization. When an object's
3845 'charset' is controlled by the value of
3846 prtGeneralCurrentLocalization, it MUST specify
3847 PrtLocalizedDescriptionStringTC as its syntax.
3848
3849 NOTE: The above description has been modified from RFC 1759
3850 for clarification."
3851 ::= { prtGeneralEntry 2 }
3852
3853prtGeneralReset OBJECT-TYPE
3854 -- NOTE: In RFC 1759, the enumeration values were implicitly defined
3855 -- by this object.
3856 SYNTAX PrtGeneralResetTC
3857 MAX-ACCESS read-write
3858 STATUS current
3859 DESCRIPTION
3860 "Setting this value to 'powerCycleReset', 'resetToNVRAM', or
3861 'resetToFactoryDefaults' will result in the resetting of the
3862 printer. When read, this object will always have the value
3863
3864
3865
3866Bergman, et al. Standards Track [Page 69]
3867\f
3868RFC 3805 Printer MIB v2 June 2004
3869
3870
3871 'notResetting(3)', and a SET of the value 'notResetting' shall
3872 have no effect on the printer. Some of the defined values are
3873 optional. However, every implementation must support at least
3874 the values 'notResetting' and 'resetToNVRAM'."
3875 ::= { prtGeneralEntry 3 }
3876
3877-- The Responsible Party group
3878
3879prtGeneralCurrentOperator OBJECT-TYPE
3880 SYNTAX OCTET STRING (SIZE(0..127))
3881 MAX-ACCESS read-write
3882 STATUS current
3883 DESCRIPTION
3884 "The name of the person who is responsible for operating
3885 this printer. It is suggested that this string include
3886 information that would enable other humans to reach the
3887 operator, such as a phone number. As a convention to
3888 facilitate automatic notification of the operator by the
3889 agent or network management station, the phone number,
3890 fax number or email address should be indicated by the
3891 URL schemes 'tel:', 'fax:' and 'mailto:', respectively.
3892 If either the phone, fax, or email information is not
3893 available, then a line should not be included for this
3894 information.
3895
3896 NOTE: For interoperability purposes, it is advisable to
3897 use email addresses formatted according to [RFC2822]
3898 requirements.
3899
3900 NOTE: The above description has been modified from RFC 1759
3901 for clarification."
3902 ::= { prtGeneralEntry 4 }
3903
3904prtGeneralServicePerson OBJECT-TYPE
3905 SYNTAX OCTET STRING (SIZE(0..127))
3906 MAX-ACCESS read-write
3907 STATUS current
3908 DESCRIPTION
3909 "The name of the person responsible for servicing this
3910 printer. It is suggested that this string include
3911 information that would enable other humans to reach the
3912 service person, such as a phone number. As a convention
3913 to facilitate automatic notification of the operator by
3914 the agent or network management station, the phone
3915 number, fax number or email address should be indicated
3916 by the URL schemes 'tel:', 'fax:' and 'mailto:',
3917 respectively. If either the phone, fax, or email
3918 information is not available, then a line should not
3919
3920
3921
3922Bergman, et al. Standards Track [Page 70]
3923\f
3924RFC 3805 Printer MIB v2 June 2004
3925
3926
3927 be included for this information.
3928
3929 NOTE: For interoperability purposes, it is advisable to use
3930 email addresses formatted per [RFC2822] requirements.
3931
3932 NOTE: The above description has been modified from RFC 1759
3933 for clarification."
3934
3935 ::= { prtGeneralEntry 5 }
3936
3937-- Default indexes section
3938--
3939-- The following four objects are used to specify the indexes of
3940-- certain subunits used as defaults during the printing process.
3941
3942prtInputDefaultIndex OBJECT-TYPE
3943 SYNTAX Integer32 (1..65535)
3944 MAX-ACCESS read-write
3945 STATUS current
3946 DESCRIPTION
3947 "The value of prtInputIndex corresponding to the default input
3948 sub-unit: that is, this object selects the default source of
3949 input media."
3950::= { prtGeneralEntry 6 }
3951
3952prtOutputDefaultIndex OBJECT-TYPE
3953 -- A range has been added to the SYNTAX clause that was not in
3954 -- RFC 1759. Although this violates SNMP compatibility rules,
3955 -- it provides a more reasonable guide for SNMP managers.
3956 SYNTAX Integer32 (1..65535)
3957 MAX-ACCESS read-write
3958 STATUS current
3959 DESCRIPTION
3960 "The value of prtOutputIndex corresponding to the default
3961 output sub-unit; that is, this object selects the default
3962 output destination."
3963::= { prtGeneralEntry 7 }
3964
3965prtMarkerDefaultIndex OBJECT-TYPE
3966 SYNTAX Integer32 (1..65535)
3967 MAX-ACCESS read-write
3968 STATUS current
3969 DESCRIPTION
3970 "The value of prtMarkerIndex corresponding to the
3971 default marker sub-unit; that is, this object selects the
3972 default marker."
3973 ::= { prtGeneralEntry 8 }
3974
3975
3976
3977
3978Bergman, et al. Standards Track [Page 71]
3979\f
3980RFC 3805 Printer MIB v2 June 2004
3981
3982
3983prtMediaPathDefaultIndex OBJECT-TYPE
3984 SYNTAX Integer32 (1..65535)
3985 MAX-ACCESS read-write
3986 STATUS current
3987 DESCRIPTION
3988 "The value of prtMediaPathIndex corresponding to
3989 the default media path; that is, the selection of the
3990 default media path."
3991 ::= { prtGeneralEntry 9 }
3992
3993-- Console general section
3994--
3995-- The following four objects describe overall parameters of the
3996-- printer console subsystem.
3997
3998prtConsoleLocalization OBJECT-TYPE
3999 SYNTAX Integer32 (1..65535)
4000 MAX-ACCESS read-write
4001 STATUS current
4002 DESCRIPTION
4003 "The value of the prtLocalizationIndex corresponding to
4004 the language, country, and character set to be used for the
4005 console. This localization applies both to the actual display
4006 on the console as well as the encoding of these console objects
4007 in management operations. When an object's 'charset' is
4008 controlled by the value of prtConsoleLocalization, it MUST
4009 specify PrtConsoleDescriptionStringTC as its syntax.
4010
4011 NOTE: The above description has been modified from RFC 1759
4012 for clarification."
4013 ::= { prtGeneralEntry 10 }
4014
4015prtConsoleNumberOfDisplayLines OBJECT-TYPE
4016 SYNTAX Integer32 (0..65535)
4017 MAX-ACCESS read-only
4018 STATUS current
4019 DESCRIPTION
4020 "The number of lines on the printer's physical
4021 display. This value is 0 if there are no lines on the
4022 physical display or if there is no physical display"
4023 ::= { prtGeneralEntry 11 }
4024
4025prtConsoleNumberOfDisplayChars OBJECT-TYPE
4026 SYNTAX Integer32 (0..65535)
4027 MAX-ACCESS read-only
4028 STATUS current
4029 DESCRIPTION
4030 "The number of characters per line displayed on the physical
4031
4032
4033
4034Bergman, et al. Standards Track [Page 72]
4035\f
4036RFC 3805 Printer MIB v2 June 2004
4037
4038
4039 display. This value is 0 if there are no lines on the physical
4040 display or if there is no physical display"
4041 ::= { prtGeneralEntry 12 }
4042
4043prtConsoleDisable OBJECT-TYPE
4044 -- In RFC 1759, the enumeration values were implicitly defined
4045 -- by this object.
4046 SYNTAX PrtConsoleDisableTC
4047 MAX-ACCESS read-write
4048 STATUS current
4049 DESCRIPTION
4050 "This value indicates how input is (or is not) accepted from
4051 the operator console.
4052
4053 NOTE: The above description has been modified from RFC 1759
4054 for clarification."
4055 ::= { prtGeneralEntry 13 }
4056
4057-- The Auxiliary Sheet Group
4058--
4059-- The auxiliary sheet group allows the administrator to control
4060-- the production of auxiliary sheets by the printer. This group
4061-- contains only the "prtAuxiliarySheetStartupPage" and
4062-- "prtAuxiliarySheetBannerPage" objects.
4063
4064prtAuxiliarySheetStartupPage OBJECT-TYPE
4065 SYNTAX PresentOnOff
4066 MAX-ACCESS read-write
4067 STATUS current
4068 DESCRIPTION
4069 "Used to enable or disable printing a startup page. If enabled,
4070 a startup page will be printed shortly after power-up, when the
4071 device is ready. Typical startup pages include test patterns
4072 and/or printer configuration information."
4073 ::= { prtGeneralEntry 14 }
4074
4075prtAuxiliarySheetBannerPage OBJECT-TYPE
4076 SYNTAX PresentOnOff
4077 MAX-ACCESS read-write
4078 STATUS current
4079 DESCRIPTION
4080 "Used to enable or disable printing banner pages at the
4081 beginning of jobs. This is a master switch which applies to all
4082 jobs, regardless of interpreter."
4083 ::= { prtGeneralEntry 15 }
4084
4085
4086
4087
4088
4089
4090Bergman, et al. Standards Track [Page 73]
4091\f
4092RFC 3805 Printer MIB v2 June 2004
4093
4094
4095-- Administrative section (The General V2 Group)
4096--
4097-- The following two objects are used to specify administrative
4098-- information assigned to the printer.
4099
4100prtGeneralPrinterName OBJECT-TYPE
4101 SYNTAX OCTET STRING (SIZE (0..127))
4102 MAX-ACCESS read-write
4103 STATUS current
4104 DESCRIPTION
4105 "An administrator-specified name for this printer. Depending
4106 upon implementation of this printer, the value of this object
4107 may or may not be same as the value for the MIB-II 'SysName'
4108 object."
4109 ::= { prtGeneralEntry 16 }
4110
4111prtGeneralSerialNumber OBJECT-TYPE
4112 SYNTAX OCTET STRING (SIZE (0..255))
4113 MAX-ACCESS read-write
4114 STATUS current
4115 DESCRIPTION
4116 "A recorded serial number for this device that indexes some
4117 type device catalog or inventory. This value is usually set by
4118 the device manufacturer but the MIB supports the option of
4119 writing for this object for site-specific administration of
4120 device inventory or tracking."
4121 ::= { prtGeneralEntry 17 }
4122
4123-- General alert table section (Alert Table V2 Group)
4124--
4125-- The following two objects are used to specify counters
4126-- associated with the Alert Table.
4127
4128prtAlertCriticalEvents OBJECT-TYPE
4129 SYNTAX Counter32
4130 MAX-ACCESS read-only
4131 STATUS current
4132 DESCRIPTION
4133 "A running counter of the number of critical alert events that
4134 have been recorded in the alert table. The value of this object
4135 is RESET in the event of a power cycle operation (i.e., the
4136 value is not persistent."
4137 ::= { prtGeneralEntry 18 }
4138
4139prtAlertAllEvents OBJECT-TYPE
4140 SYNTAX Counter32
4141 MAX-ACCESS read-only
4142 STATUS current
4143
4144
4145
4146Bergman, et al. Standards Track [Page 74]
4147\f
4148RFC 3805 Printer MIB v2 June 2004
4149
4150
4151 DESCRIPTION
4152 "A running counter of the total number of alert event entries
4153 (critical and non-critical) that have been recorded in the
4154 alert table"
4155 ::= { prtGeneralEntry 19 }
4156
4157-- The Cover Table
4158--
4159-- The cover portion of the General print sub-unit describes the
4160-- covers and interlocks of the printer. The Cover Table has an
4161-- entry for each cover and interlock.
4162
4163prtCover OBJECT IDENTIFIER ::= { printmib 6 }
4164
4165prtCoverTable OBJECT-TYPE
4166 SYNTAX SEQUENCE OF PrtCoverEntry
4167 MAX-ACCESS not-accessible
4168 STATUS current
4169 DESCRIPTION
4170 "A table of the covers and interlocks of the printer."
4171 ::= { prtCover 1 }
4172
4173prtCoverEntry OBJECT-TYPE
4174 SYNTAX PrtCoverEntry
4175 MAX-ACCESS not-accessible
4176 STATUS current
4177 DESCRIPTION
4178 "Information about a cover or interlock.
4179 Entries may exist in the table for each device
4180 index with a device type of 'printer'.
4181
4182 NOTE: The above description has been modified from RFC 1759
4183 for clarification."
4184 INDEX { hrDeviceIndex, prtCoverIndex }
4185 ::= { prtCoverTable 1 }
4186
4187PrtCoverEntry ::= SEQUENCE {
4188 prtCoverIndex Integer32,
4189 prtCoverDescription PrtLocalizedDescriptionStringTC,
4190 prtCoverStatus PrtCoverStatusTC
4191 }
4192
4193prtCoverIndex OBJECT-TYPE
4194 SYNTAX Integer32 (1..65535)
4195 MAX-ACCESS not-accessible
4196 STATUS current
4197 DESCRIPTION
4198 "A unique value used by the printer to identify this Cover sub
4199
4200
4201
4202Bergman, et al. Standards Track [Page 75]
4203\f
4204RFC 3805 Printer MIB v2 June 2004
4205
4206
4207 unit. Although these values may change due to a major
4208 reconfiguration of the device (e.g., the addition of new cover
4209 sub-units to the printer), values SHOULD remain stable across
4210 successive printer power cycles.
4211
4212 NOTE: The above description has been modified from RFC 1759
4213 for clarification."
4214 ::= { prtCoverEntry 1 }
4215
4216prtCoverDescription OBJECT-TYPE
4217 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
4218 -- to a TC to better support localization of the object.
4219 SYNTAX PrtLocalizedDescriptionStringTC
4220 MAX-ACCESS read-only
4221 STATUS current
4222 DESCRIPTION
4223 "The manufacturer provided cover sub-mechanism name in the
4224 localization specified by prtGeneralCurrentLocalization."
4225 ::= { prtCoverEntry 2 }
4226
4227prtCoverStatus OBJECT-TYPE
4228 -- NOTE: In RFC 1759, the enumeration values were implicitly defined
4229 -- by this object and are now defined in the IANA-PRINTER-MIB. The
4230 -- new TC has defined "coverOpen" and "coverClosed" to replace
4231 -- "doorOpen" and "doorClosed" in RFC 1759. A name change is not
4232 -- formally allowed per SMI rules, but was agreed to by the WG group
4233 -- since a door has a more restrictive meaning than a cover and
4234 -- Cover group is intended to support doors as a subset of covers.
4235
4236 SYNTAX PrtCoverStatusTC
4237 MAX-ACCESS read-only
4238 STATUS current
4239 DESCRIPTION
4240 "The status of this cover sub-unit."
4241 ::= { prtCoverEntry 3 }
4242
4243-- The Localization Table
4244--
4245-- The localization portion of the General printer sub-unit is
4246-- responsible for identifying the natural language, country, and
4247-- character set in which character strings are expressed. There
4248-- may be one or more localizations supported per printer. The
4249-- available localizations are represented by the Localization
4250-- table.
4251
4252prtLocalization OBJECT IDENTIFIER ::= { printmib 7 }
4253
4254prtLocalizationTable OBJECT-TYPE
4255
4256
4257
4258Bergman, et al. Standards Track [Page 76]
4259\f
4260RFC 3805 Printer MIB v2 June 2004
4261
4262
4263 SYNTAX SEQUENCE OF PrtLocalizationEntry
4264 MAX-ACCESS not-accessible
4265 STATUS current
4266 DESCRIPTION
4267 "The available localizations in this printer."
4268 ::= { prtLocalization 1 }
4269
4270prtLocalizationEntry OBJECT-TYPE
4271 SYNTAX PrtLocalizationEntry
4272 MAX-ACCESS not-accessible
4273 STATUS current
4274 DESCRIPTION
4275 "A description of a localization.
4276 Entries may exist in the table for each device
4277 index with a device type of 'printer'.
4278
4279 NOTE: The above description has been modified from RFC 1759
4280 for clarification."
4281 INDEX { hrDeviceIndex, prtLocalizationIndex }
4282 ::= { prtLocalizationTable 1 }
4283
4284PrtLocalizationEntry ::= SEQUENCE {
4285 prtLocalizationIndex Integer32,
4286 prtLocalizationLanguage OCTET STRING,
4287 prtLocalizationCountry OCTET STRING,
4288 prtLocalizationCharacterSet IANACharset
4289 }
4290
4291prtLocalizationIndex OBJECT-TYPE
4292 SYNTAX Integer32 (1..65535)
4293 MAX-ACCESS not-accessible
4294 STATUS current
4295 DESCRIPTION
4296 "A unique value used by the printer to identify this
4297 localization entry. Although these values may change due to a
4298 major reconfiguration of the device (e.g., the addition of new
4299 localization data to the printer), values SHOULD remain
4300 stable across successive printer power cycles.
4301
4302 NOTE: The above description has been modified from RFC 1759
4303 for clarification."
4304 ::= { prtLocalizationEntry 1 }
4305
4306prtLocalizationLanguage OBJECT-TYPE
4307 -- Note: The size is fixed, was incorrectly 0..2 in RFC 1759.
4308 SYNTAX OCTET STRING (SIZE(2))
4309 MAX-ACCESS read-only
4310 STATUS current
4311
4312
4313
4314Bergman, et al. Standards Track [Page 77]
4315\f
4316RFC 3805 Printer MIB v2 June 2004
4317
4318
4319 DESCRIPTION
4320 "A two character language code from ISO 639. Examples en,
4321 es, fr, de. NOTE: These examples were shown as upper case in
4322 RFC 1759 and are now shown as lower case to agree with ISO 639."
4323 ::= { prtLocalizationEntry 2 }
4324
4325prtLocalizationCountry OBJECT-TYPE
4326 -- Note: The size is fixed, was incorrectly 0..2 in RFC 1759.
4327 SYNTAX OCTET STRING (SIZE(2))
4328 MAX-ACCESS read-only
4329 STATUS current
4330 DESCRIPTION
4331 "A two character country code from ISO 3166, a blank string
4332 (two space characters) shall indicate that the country is not
4333 defined. Examples: US, GB, FR, DE, ..."
4334 ::= { prtLocalizationEntry 3 }
4335
4336prtLocalizationCharacterSet OBJECT-TYPE
4337 SYNTAX IANACharset
4338 MAX-ACCESS read-only
4339 STATUS current
4340 DESCRIPTION
4341 "The coded character set used for this localization."
4342 ::= { prtLocalizationEntry 4 }
4343
4344-- The System Resources Tables
4345--
4346-- The Printer MIB makes use of the Host Resources MIB to
4347-- define system resources by referencing the storage
4348-- and device groups of the print group.
4349
4350prtStorageRefTable OBJECT-TYPE
4351 SYNTAX SEQUENCE OF PrtStorageRefEntry
4352 MAX-ACCESS not-accessible
4353 STATUS current
4354 DESCRIPTION
4355 "This table defines which printer, amongst multiple printers
4356 serviced by one agent, owns which storage units.
4357
4358 NOTE: The above description has been modified from RFC 1759
4359 for clarification."
4360 ::= { prtGeneral 2 }
4361
4362prtStorageRefEntry OBJECT-TYPE
4363 SYNTAX PrtStorageRefEntry
4364 MAX-ACCESS not-accessible
4365 STATUS current
4366 DESCRIPTION
4367
4368
4369
4370Bergman, et al. Standards Track [Page 78]
4371\f
4372RFC 3805 Printer MIB v2 June 2004
4373
4374
4375 "This table will have an entry for each entry in the Host
4376 Resources MIB storage table that represents storage associated
4377 with a printer managed by this agent.
4378
4379 NOTE: The above description has been modified from RFC 1759
4380 for clarification."
4381 INDEX { hrStorageIndex, prtStorageRefSeqNumber }
4382 ::= { prtStorageRefTable 1 }
4383
4384PrtStorageRefEntry ::= SEQUENCE {
4385 prtStorageRefSeqNumber Integer32,
4386 prtStorageRefIndex Integer32
4387 }
4388
4389prtStorageRefSeqNumber OBJECT-TYPE
4390 -- NOTE: The range has been changed from RFC 1759, which allowed a
4391 -- minumum value of zero. This was incorrect, since zero is not a
4392 -- valid index.
4393 SYNTAX Integer32 (1..65535)
4394 MAX-ACCESS not-accessible
4395 STATUS current
4396 DESCRIPTION
4397 "This value will be unique amongst all entries with a common
4398 value of hrStorageIndex. This object allows a storage entry to
4399 point to the multiple printer devices with which it is
4400 associated."
4401 ::= { prtStorageRefEntry 1 }
4402
4403prtStorageRefIndex OBJECT-TYPE
4404 -- NOTE: The range has been changed from RFC 1759 to be compatible
4405 -- with the defined range of hrDeviceIndex.
4406 SYNTAX Integer32 (0..2147483647)
4407 MAX-ACCESS read-only
4408 STATUS current
4409 DESCRIPTION
4410 "The value of the hrDeviceIndex of the printer device that this
4411 storageEntry is associated with."
4412 ::= { prtStorageRefEntry 2 }
4413
4414prtDeviceRefTable OBJECT-TYPE
4415 SYNTAX SEQUENCE OF PrtDeviceRefEntry
4416 MAX-ACCESS not-accessible
4417 STATUS current
4418 DESCRIPTION
4419 "This table defines which printer, amongst multiple printers
4420 serviced by one agent, is associated with which devices.
4421
4422 NOTE: The above description has been modified from RFC 1759
4423
4424
4425
4426Bergman, et al. Standards Track [Page 79]
4427\f
4428RFC 3805 Printer MIB v2 June 2004
4429
4430
4431 for clarification."
4432 ::= { prtGeneral 3 }
4433
4434prtDeviceRefEntry OBJECT-TYPE
4435 SYNTAX PrtDeviceRefEntry
4436 MAX-ACCESS not-accessible
4437 STATUS current
4438 DESCRIPTION
4439 "This table will have an entry for each entry in the Host
4440 Resources MIB device table that represents a device associated
4441 with a printer managed by this agent.
4442
4443 NOTE: The above description has been modified from RFC 1759
4444 for clarification."
4445 INDEX { hrDeviceIndex, prtDeviceRefSeqNumber }
4446 ::= { prtDeviceRefTable 1 }
4447
4448PrtDeviceRefEntry ::= SEQUENCE {
4449 prtDeviceRefSeqNumber Integer32,
4450 prtDeviceRefIndex Integer32
4451 }
4452
4453prtDeviceRefSeqNumber OBJECT-TYPE
4454 -- NOTE: The range has been changed from RFC 1759, which allowed a
4455 -- minumum value of zero. This was incorrect, since zero is not a
4456 -- valid index.
4457 SYNTAX Integer32 (1..65535)
4458 MAX-ACCESS not-accessible
4459 STATUS current
4460 DESCRIPTION
4461 "This value will be unique amongst all entries with a common
4462 value of hrDeviceIndex. This object allows a device entry to
4463 point to the multiple printer devices with which it is
4464 associated."
4465 ::= { prtDeviceRefEntry 1 }
4466
4467prtDeviceRefIndex OBJECT-TYPE
4468 -- NOTE: The range has been changed from RFC 1759 to be compatible
4469 -- with the defined range of hrDeviceIndex.
4470 SYNTAX Integer32 (0..2147483647)
4471 MAX-ACCESS read-only
4472 STATUS current
4473 DESCRIPTION
4474 "The value of the hrDeviceIndex of the printer device that this
4475 deviceEntry is associated with."
4476 ::= { prtDeviceRefEntry 2 }
4477
4478
4479
4480
4481
4482Bergman, et al. Standards Track [Page 80]
4483\f
4484RFC 3805 Printer MIB v2 June 2004
4485
4486
4487-- The Input Group
4488--
4489-- Input sub-units are managed as a tabular, indexed collection
4490-- of possible devices capable of providing media for input to
4491-- the printing process. Input sub-units typically have a
4492-- location, a type, an identifier, a set of constraints on
4493-- possible media sizes and potentially other media
4494-- characteristics, and may be capable of indicating current
4495-- status or capacity.
4496
4497prtInput OBJECT IDENTIFIER ::= { printmib 8 }
4498
4499prtInputTable OBJECT-TYPE
4500 SYNTAX SEQUENCE OF PrtInputEntry
4501 MAX-ACCESS not-accessible
4502 STATUS current
4503 DESCRIPTION
4504 "A table of the devices capable of providing media for input to
4505 the printing process."
4506 ::= { prtInput 2 }
4507
4508prtInputEntry OBJECT-TYPE
4509 SYNTAX PrtInputEntry
4510 MAX-ACCESS not-accessible
4511 STATUS current
4512 DESCRIPTION
4513 "Attributes of a device capable of providing media for input to
4514 the printing process. Entries may exist in the table for each
4515 device index with a device type of 'printer'.
4516
4517 NOTE: The above description has been modified from RFC 1759
4518 for clarification."
4519 INDEX { hrDeviceIndex, prtInputIndex }
4520 ::= { prtInputTable 1 }
4521
4522PrtInputEntry ::= SEQUENCE {
4523 prtInputIndex Integer32,
4524 prtInputType PrtInputTypeTC,
4525 prtInputDimUnit PrtMediaUnitTC,
4526 prtInputMediaDimFeedDirDeclared Integer32,
4527 prtInputMediaDimXFeedDirDeclared Integer32,
4528 prtInputMediaDimFeedDirChosen Integer32,
4529 prtInputMediaDimXFeedDirChosen Integer32,
4530 prtInputCapacityUnit PrtCapacityUnitTC,
4531 prtInputMaxCapacity Integer32,
4532 prtInputCurrentLevel Integer32,
4533 prtInputStatus PrtSubUnitStatusTC,
4534 prtInputMediaName OCTET STRING,
4535
4536
4537
4538Bergman, et al. Standards Track [Page 81]
4539\f
4540RFC 3805 Printer MIB v2 June 2004
4541
4542
4543 prtInputName OCTET STRING,
4544 prtInputVendorName OCTET STRING,
4545 prtInputModel OCTET STRING,
4546 prtInputVersion OCTET STRING,
4547 prtInputSerialNumber OCTET STRING,
4548 prtInputDescription PrtLocalizedDescriptionStringTC,
4549 prtInputSecurity PresentOnOff,
4550 prtInputMediaWeight Integer32,
4551 prtInputMediaType OCTET STRING,
4552 prtInputMediaColor OCTET STRING,
4553 prtInputMediaFormParts Integer32,
4554 prtInputMediaLoadTimeout Integer32,
4555 prtInputNextIndex Integer32
4556 }
4557
4558prtInputIndex OBJECT-TYPE
4559 SYNTAX Integer32 (1..65535)
4560 MAX-ACCESS not-accessible
4561 STATUS current
4562 DESCRIPTION
4563 "A unique value used by the printer to identify this input
4564 sub-unit. Although these values may change due to a major
4565 reconfiguration of the device (e.g., the addition of new input
4566 sub-units to the printer), values SHOULD remain stable across
4567 successive printer power cycles.
4568
4569 NOTE: The above description has been modified from RFC 1759
4570 for clarification."
4571 ::= { prtInputEntry 1 }
4572
4573prtInputType OBJECT-TYPE
4574 -- NOTE: In RFC 1759, the enumeration values were implicitly
4575 -- defined by this object.
4576 SYNTAX PrtInputTypeTC
4577 MAX-ACCESS read-only
4578 STATUS current
4579 DESCRIPTION
4580 "The type of technology (discriminated primarily according to
4581 feeder mechanism type) employed by the input sub-unit. Note,
4582 the Input Class provides for a descriptor field to further
4583 qualify the other choice."
4584 ::= { prtInputEntry 2 }
4585
4586prtInputDimUnit OBJECT-TYPE
4587 SYNTAX PrtMediaUnitTC
4588 MAX-ACCESS read-only
4589 STATUS current
4590 DESCRIPTION
4591
4592
4593
4594Bergman, et al. Standards Track [Page 82]
4595\f
4596RFC 3805 Printer MIB v2 June 2004
4597
4598
4599 "The unit of measurement for use calculating and relaying
4600 dimensional values for this input sub-unit."
4601 ::= { prtInputEntry 3 }
4602
4603prtInputMediaDimFeedDirDeclared OBJECT-TYPE
4604 -- NOTE: In RFC 1759, the range was not defined.
4605 SYNTAX Integer32 (-2..2147483647)
4606 MAX-ACCESS read-write
4607 STATUS current
4608 DESCRIPTION
4609 "This object provides the value of the declared dimension, in
4610 the feed direction, of the media that is (or, if empty, was or
4611 will be) in this input sub-unit. The feed direction is the
4612 direction in which the media is fed on this sub-unit. This
4613 dimension is measured in input sub-unit dimensional units
4614 (controlled by prtInputDimUnit, which uses PrtMediaUnitTC). If
4615 this input sub-unit can reliably sense this value, the value is
4616 sensed by the printer and may not be changed by management
4617 requests. Otherwise, the value may be changed. The value (-1)
4618 means other and specifically means that this sub-unit places no
4619 restriction on this parameter. The value (-2) indicates
4620 unknown."
4621 ::= { prtInputEntry 4 }
4622
4623prtInputMediaDimXFeedDirDeclared OBJECT-TYPE
4624 -- NOTE: In RFC 1759, the range was not defined.
4625 SYNTAX Integer32 (-2..2147483647)
4626 MAX-ACCESS read-write
4627 STATUS current
4628 DESCRIPTION
4629 "This object provides the value of the declared dimension, in
4630 the cross feed direction, of the media that is (or, if empty,
4631 was or will be) in this input sub-unit. The cross feed
4632 direction is ninety degrees relative to the feed direction
4633 associated with this sub-unit. This dimension is measured in
4634 input sub-unit dimensional units (controlled by
4635 prtInputDimUnit,which uses PrtMediaUnitTC). If this input sub-
4636 unit can reliably sense this value, the value is sensed by the
4637 printer and may not be changed by management requests.
4638 Otherwise, the value may be changed. The value (-1) means other
4639 and specifically means that this sub-unit places no restriction
4640 on this parameter. The value (-2) indicates unknown."
4641 ::= { prtInputEntry 5 }
4642
4643prtInputMediaDimFeedDirChosen OBJECT-TYPE
4644 -- NOTE: In RFC 1759, the range was not defined.
4645 SYNTAX Integer32 (-2..2147483647)
4646 MAX-ACCESS read-only
4647
4648
4649
4650Bergman, et al. Standards Track [Page 83]
4651\f
4652RFC 3805 Printer MIB v2 June 2004
4653
4654
4655 STATUS current
4656 DESCRIPTION
4657 "The printer will act as if media of the chosen dimension (in
4658 the feed direction) is present in this input source. Note that
4659 this value will be used even if the input tray is empty. Feed
4660 dimension measurements are taken relative to the feed direction
4661 associated with that sub-unit and are in input sub-unit
4662 dimensional units (controlled by prtInputDimUnit, which uses
4663 PrtMediaUnitTC). If the printer supports the declared
4664 dimension,the granted dimension is the same as the declared
4665 dimension. If not, the granted dimension is set to the closest
4666 dimension that the printer supports when the declared dimension
4667 is set. The value (-1) means other and specifically indicates
4668 that this sub-unit places no restriction on this parameter. The
4669 value (-2)indicates unknown."
4670 ::= { prtInputEntry 6 }
4671
4672prtInputMediaDimXFeedDirChosen OBJECT-TYPE
4673 -- NOTE: In RFC 1759, the range was not defined.
4674 SYNTAX Integer32 (-2..2147483647)
4675 MAX-ACCESS read-only
4676 STATUS current
4677 DESCRIPTION
4678 "The printer will act as if media of the chosen dimension (in
4679 the cross feed direction) is present in this input source. Note
4680 that this value will be used even if the input tray is empty.
4681 The cross feed direction is ninety degrees relative to the feed
4682 direction associated with this sub-unit. This dimension is
4683 measured in input sub-unit dimensional units (controlled by
4684 prtInputDimUnit, which uses PrtMediaUnitTC). If the printer
4685 supports the declare dimension, the granted dimension is the
4686 same as the declared dimension. If not, the granted dimension
4687 is set to the closest dimension that the printer supports when
4688 the declared dimension is set. The value (-1) means other and
4689 specifically indicates that this sub-unit places no restriction
4690 on this parameter. The value (-2) indicates unknown."
4691 ::= { prtInputEntry 7 }
4692
4693prtInputCapacityUnit OBJECT-TYPE
4694 -- NOTE: In RFC 1759, the enumeration values were implicitly
4695 -- defined by this object.
4696 SYNTAX PrtCapacityUnitTC
4697 MAX-ACCESS read-only
4698 STATUS current
4699 DESCRIPTION
4700 "The unit of measurement for use in calculating and relaying
4701 capacity values for this input sub-unit."
4702 ::= { prtInputEntry 8 }
4703
4704
4705
4706Bergman, et al. Standards Track [Page 84]
4707\f
4708RFC 3805 Printer MIB v2 June 2004
4709
4710
4711prtInputMaxCapacity OBJECT-TYPE
4712 -- NOTE: In RFC 1759, the range was not defined.
4713 SYNTAX Integer32 (-2..2147483647)
4714 MAX-ACCESS read-write
4715 STATUS current
4716 DESCRIPTION
4717 "The maximum capacity of the input sub-unit in input sub-unit
4718 capacity units (PrtCapacityUnitTC). There is no convention
4719 associated with the media itself so this value reflects claimed
4720 capacity. If this input sub-unit can reliably sense this value,
4721 the value is sensed by the printer and may not be changed by
4722 management requests; otherwise, the value may be written (by a
4723 Remote Control Panel or a Management Application). The value
4724 (-1) means other and specifically indicates that the sub-unit
4725 places no restrictions on this parameter. The value (-2) means
4726 unknown."
4727 ::= { prtInputEntry 9 }
4728
4729prtInputCurrentLevel OBJECT-TYPE
4730 -- NOTE: In RFC 1759, the range was not defined.
4731 SYNTAX Integer32 (-3..2147483647) -- in capacity units
4732 -- (PrtCapacityUnitTC).
4733 MAX-ACCESS read-write
4734 STATUS current
4735 DESCRIPTION
4736 "The current capacity of the input sub-unit in input sub-unit
4737 capacity units (PrtCapacityUnitTC). If this input sub-unit can
4738 reliably sense this value, the value is sensed by the printer
4739 and may not be changed by management requests; otherwise, the
4740 value may be written (by a Remote Control Panel or a Management
4741 Application). The value (-1) means other and specifically
4742 indicates that the sub-unit places no restrictions on this
4743 parameter. The value (-2) means unknown. The value (-3) means
4744 that the printer knows that at least one unit remains."
4745 ::= { prtInputEntry 10 }
4746
4747prtInputStatus OBJECT-TYPE
4748 SYNTAX PrtSubUnitStatusTC
4749 MAX-ACCESS read-only
4750 STATUS current
4751 DESCRIPTION
4752 "The current status of this input sub-unit."
4753 ::= { prtInputEntry 11 }
4754
4755prtInputMediaName OBJECT-TYPE
4756 SYNTAX OCTET STRING (SIZE(0..63))
4757 MAX-ACCESS read-write
4758 STATUS current
4759
4760
4761
4762Bergman, et al. Standards Track [Page 85]
4763\f
4764RFC 3805 Printer MIB v2 June 2004
4765
4766
4767 DESCRIPTION
4768 "A description of the media contained in this input sub-unit;
4769 This description is to be used by a client to format and
4770 Localize a string for display to a human operator. This
4771 description is not processed by the printer. It is used to
4772 provide information not expressible in terms of the other
4773 media attributes (e.g., prtInputMediaDimFeedDirChosen,
4774 prtInputMediaDimXFeedDirChosen, prtInputMediaWeight,
4775 prtInputMediaType)."
4776 -- The following reference was not included in RFC 1759.
4777 REFERENCE
4778 "The PWG Standardized Media Names specification [PWGMEDIA]
4779 contains the recommended values for this object. See also
4780 RFC 3805 Appendix C,'Media Names', which lists the values
4781 Of standardized media names defined in ISO/IEC 10175."
4782 ::= { prtInputEntry 12 }
4783
4784-- INPUT MEASUREMENT
4785--
4786-- _______ | |
4787-- ^ | |
4788-- | | | |
4789-- | |_ _ _ _ _ _ _ _| _______________ |direction
4790-- | | | ^ v
4791-- MaxCapacity | Sheets | |
4792-- | | left | CurrentLevel
4793-- | | in | |
4794-- v | tray | v
4795-- _______ +_______________+ _______
4796
4797-- The Extended Input Group
4798
4799prtInputName OBJECT-TYPE
4800 SYNTAX OCTET STRING (SIZE(0..63))
4801 MAX-ACCESS read-write
4802 STATUS current
4803 DESCRIPTION
4804 "The name assigned to this input sub-unit."
4805 ::= { prtInputEntry 13 }
4806
4807prtInputVendorName OBJECT-TYPE
4808 SYNTAX OCTET STRING (SIZE(0..63))
4809 MAX-ACCESS read-only
4810 STATUS current
4811 DESCRIPTION
4812 "The vendor name of this input sub-unit."
4813 ::= { prtInputEntry 14 }
4814
4815
4816
4817
4818Bergman, et al. Standards Track [Page 86]
4819\f
4820RFC 3805 Printer MIB v2 June 2004
4821
4822
4823prtInputModel OBJECT-TYPE
4824 SYNTAX OCTET STRING (SIZE(0..63))
4825 MAX-ACCESS read-only
4826 STATUS current
4827 DESCRIPTION
4828 "The model name of this input sub-unit."
4829 ::= { prtInputEntry 15 }
4830
4831prtInputVersion OBJECT-TYPE
4832 SYNTAX OCTET STRING (SIZE(0..63))
4833 MAX-ACCESS read-only
4834 STATUS current
4835 DESCRIPTION
4836 "The version of this input sub-unit."
4837 ::= { prtInputEntry 16 }
4838
4839prtInputSerialNumber OBJECT-TYPE
4840 SYNTAX OCTET STRING (SIZE(0..32))
4841 MAX-ACCESS read-only
4842 STATUS current
4843 DESCRIPTION
4844 "The serial number assigned to this input sub-unit."
4845 ::= { prtInputEntry 17 }
4846
4847prtInputDescription OBJECT-TYPE
4848 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
4849 -- to a TC to better support localization of the object.
4850 SYNTAX PrtLocalizedDescriptionStringTC
4851 MAX-ACCESS read-only
4852 STATUS current
4853 DESCRIPTION
4854 "A free-form text description of this input sub-unit in the
4855 localization specified by prtGeneralCurrentLocalization."
4856 ::= { prtInputEntry 18 }
4857
4858prtInputSecurity OBJECT-TYPE
4859 SYNTAX PresentOnOff
4860 MAX-ACCESS read-write
4861 STATUS current
4862 DESCRIPTION
4863 "Indicates if this input sub-unit has some security associated
4864 with it."
4865 ::= { prtInputEntry 19 }
4866
4867-- The Input Media Group
4868--
4869-- The Input Media Group supports identification of media
4870-- installed or available for use on a printing device.
4871
4872
4873
4874Bergman, et al. Standards Track [Page 87]
4875\f
4876RFC 3805 Printer MIB v2 June 2004
4877
4878
4879-- Medium resources are identified by name, and include a
4880-- collection of characteristic attributes that may further be
4881-- used for selection and management of them.
4882-- The Input Media group consists of a set of optional
4883-- "columns" in the Input Table. In this manner, a minimally
4884-- conforming implementation may choose to not support reporting
4885-- of media resources if it cannot do so.
4886
4887prtInputMediaWeight OBJECT-TYPE
4888 -- NOTE: In RFC 1759, the range was not defined.
4889 SYNTAX Integer32 (-2..2147483647)
4890 MAX-ACCESS read-write
4891 STATUS current
4892 DESCRIPTION
4893 "The weight of the medium associated with this input sub-unit
4894 in grams / per meter squared. The value (-2) means unknown."
4895 ::= { prtInputEntry 20 }
4896
4897prtInputMediaType OBJECT-TYPE
4898 SYNTAX OCTET STRING (SIZE(0..63))
4899 MAX-ACCESS read-write
4900 STATUS current
4901 DESCRIPTION
4902 "The name of the type of medium associated with this input sub
4903 unit. This name need not be processed by the printer; it might
4904 simply be displayed to an operator.
4905
4906 NOTE: The above description has been modified from RFC 1759."
4907 -- The following reference was not included in RFC 1759.
4908 REFERENCE
4909 "The PWG Standardized Media Names specification [PWGMEDIA],
4910 section 3 Media Type Names, contains the recommended values for
4911 this object. Implementers may add additional string values.
4912 The naming conventions in ISO 9070 are recommended in order to
4913 avoid potential name clashes."
4914 ::= { prtInputEntry 21 }
4915
4916prtInputMediaColor OBJECT-TYPE
4917 SYNTAX OCTET STRING (SIZE(0..63))
4918 MAX-ACCESS read-write
4919 STATUS current
4920 DESCRIPTION
4921 "The name of the color of the medium associated with
4922 this input sub-unit using standardized string values.
4923
4924 NOTE: The above description has been modified from RFC 1759."
4925 -- The following reference was not included in RFC 1759.
4926 REFERENCE
4927
4928
4929
4930Bergman, et al. Standards Track [Page 88]
4931\f
4932RFC 3805 Printer MIB v2 June 2004
4933
4934
4935 "The PWG Standardized Media Names specification [PWGMEDIA],
4936 section 4 Media Color Names, contains the recommended values
4937 for this object. Implementers may add additional string values.
4938 The naming conventions in ISO 9070 are recommended in order to
4939 avoid potential name clashes."
4940 ::= { prtInputEntry 22 }
4941
4942prtInputMediaFormParts OBJECT-TYPE
4943 -- NOTE: In RFC 1759, the range was not defined.
4944 SYNTAX Integer32 (-2..2147483647)
4945 MAX-ACCESS read-write
4946 STATUS current
4947 DESCRIPTION
4948 "The number of parts associated with the medium
4949 associated with this input sub-unit if the medium is a
4950 multi-part form. The value (-1) means other and
4951 specifically indicates that the device places no
4952 restrictions on this parameter. The value (-2) means
4953 unknown."
4954 ::= { prtInputEntry 23 }
4955
4956-- The Input Switching Group
4957--
4958-- The input switching group allows the administrator to set the
4959-- input subunit time-out for the printer and to control the
4960-- automatic input subunit switching by the printer when an input
4961-- subunit becomes empty.
4962
4963prtInputMediaLoadTimeout OBJECT-TYPE
4964 SYNTAX Integer32 (-2..2147483647)
4965 MAX-ACCESS read-write
4966 STATUS current
4967 DESCRIPTION
4968 "When the printer is not able to print due to a subunit being
4969 empty or the requested media must be manually loaded, the
4970 printer will wait for the duration (in seconds) specified by
4971 this object. Upon expiration of the time-out, the printer will
4972 take the action specified by prtInputNextIndex.
4973
4974 The event which causes the printer to enter the waiting state
4975 is product specific. If the printer is not waiting for manually
4976 fed media, it may switch from an empty subunit to a different
4977 subunit without waiting for the time-out to expire.
4978
4979 A value of (-1) implies 'other' or 'infinite' which translates
4980 to 'wait forever'. The action which causes printing to continue
4981 is product specific. A value of (-2) implies 'unknown'."
4982 ::= { prtInputEntry 24 }
4983
4984
4985
4986Bergman, et al. Standards Track [Page 89]
4987\f
4988RFC 3805 Printer MIB v2 June 2004
4989
4990
4991prtInputNextIndex OBJECT-TYPE
4992 SYNTAX Integer32 (-3..2147483647)
4993 MAX-ACCESS read-write
4994 STATUS current
4995 DESCRIPTION
4996 "The value of prtInputIndex corresponding to the input subunit
4997 which will be used when this input subunit is emptied and the
4998 time-out specified by prtInputMediaLoadTimeout expires. A value
4999 of zero(0) indicates that auto input switching will not occur
5000 when this input subunit is emptied. If the time-out specified
5001 by prtInputLoadMediaTimeout expires and this value is zero(0),
5002 the job will be aborted. A value of (-1) means other. The
5003 value (-2)means 'unknown' and specifically indicates that an
5004 implementation specific method will determine the next input
5005 subunit to use at the time this subunit is emptied and the time
5006 out expires. The value(-3) means input switching is not
5007 supported for this subunit."
5008 ::= { prtInputEntry 25 }
5009
5010-- The Output Group
5011--
5012-- Output sub-units are managed as a tabular, indexed collection
5013-- of possible devices capable of receiving media delivered from
5014-- the printing process. Output sub-units typically have a
5015-- location, a type, an identifier, a set of constraints on
5016-- possible media sizes and potentially other characteristics,
5017-- and may be capable of indicating current status or capacity.
5018
5019prtOutput OBJECT IDENTIFIER ::= { printmib 9 }
5020
5021prtOutputTable OBJECT-TYPE
5022 SYNTAX SEQUENCE OF PrtOutputEntry
5023 MAX-ACCESS not-accessible
5024 STATUS current
5025 DESCRIPTION
5026 "A table of the devices capable of receiving media delivered
5027 from the printing process."
5028 ::= { prtOutput 2 }
5029
5030prtOutputEntry OBJECT-TYPE
5031 SYNTAX PrtOutputEntry
5032 MAX-ACCESS not-accessible
5033 STATUS current
5034 DESCRIPTION
5035 "Attributes of a device capable of receiving media delivered
5036 from the printing process. Entries may exist in the table for
5037 each device index with a device type of 'printer'.
5038
5039
5040
5041
5042Bergman, et al. Standards Track [Page 90]
5043\f
5044RFC 3805 Printer MIB v2 June 2004
5045
5046
5047 NOTE: The above description has been modified from RFC 1759
5048 for clarification."
5049 INDEX { hrDeviceIndex, prtOutputIndex }
5050 ::= { prtOutputTable 1 }
5051
5052PrtOutputEntry ::= SEQUENCE {
5053 prtOutputIndex Integer32,
5054 prtOutputType PrtOutputTypeTC,
5055 prtOutputCapacityUnit PrtCapacityUnitTC,
5056 prtOutputMaxCapacity Integer32,
5057 prtOutputRemainingCapacity Integer32,
5058 prtOutputStatus PrtSubUnitStatusTC,
5059 prtOutputName OCTET STRING,
5060 prtOutputVendorName OCTET STRING,
5061 prtOutputModel OCTET STRING,
5062 prtOutputVersion OCTET STRING,
5063 prtOutputSerialNumber OCTET STRING,
5064 prtOutputDescription PrtLocalizedDescriptionStringTC,
5065 prtOutputSecurity PresentOnOff,
5066 prtOutputDimUnit PrtMediaUnitTC,
5067 prtOutputMaxDimFeedDir Integer32,
5068 prtOutputMaxDimXFeedDir Integer32,
5069 prtOutputMinDimFeedDir Integer32,
5070 prtOutputMinDimXFeedDir Integer32,
5071 prtOutputStackingOrder PrtOutputStackingOrderTC,
5072 prtOutputPageDeliveryOrientation
5073 PrtOutputPageDeliveryOrientationTC,
5074 prtOutputBursting PresentOnOff,
5075 prtOutputDecollating PresentOnOff,
5076 prtOutputPageCollated PresentOnOff,
5077 prtOutputOffsetStacking PresentOnOff
5078 }
5079
5080prtOutputIndex OBJECT-TYPE
5081 -- NOTE: In RFC 1759, the range was not defined.
5082 SYNTAX Integer32 (1..65535)
5083 MAX-ACCESS not-accessible
5084 STATUS current
5085 DESCRIPTION
5086 "A unique value used by this printer to identify this output
5087 sub-unit. Although these values may change due to a major
5088 reconfiguration of the sub-unit (e.g., the addition of new
5089 output devices to the printer), values SHOULD remain stable
5090 across successive printer power cycles.
5091
5092 NOTE: The above description has been modified from RFC 1759
5093 for clarification."
5094 ::= { prtOutputEntry 1 }
5095
5096
5097
5098Bergman, et al. Standards Track [Page 91]
5099\f
5100RFC 3805 Printer MIB v2 June 2004
5101
5102
5103prtOutputType OBJECT-TYPE
5104 -- NOTE: In RFC 1759, the enumeration values were implicitly defined
5105 -- by this object.
5106 SYNTAX PrtOutputTypeTC
5107 MAX-ACCESS read-only
5108 STATUS current
5109 DESCRIPTION
5110 "The type of technology supported by this output sub-unit."
5111 ::= { prtOutputEntry 2 }
5112
5113prtOutputCapacityUnit OBJECT-TYPE
5114 SYNTAX PrtCapacityUnitTC
5115 MAX-ACCESS read-only
5116 STATUS current
5117 DESCRIPTION
5118 "The unit of measurement for use in calculating and relaying
5119 capacity values for this output sub-unit."
5120 ::= { prtOutputEntry 3 }
5121
5122prtOutputMaxCapacity OBJECT-TYPE
5123 -- NOTE: In RFC 1759, the range was not defined.
5124 SYNTAX Integer32 (-2..2147483647)
5125 MAX-ACCESS read-write
5126 STATUS current
5127 DESCRIPTION
5128 "The maximum capacity of this output sub-unit in output sub-
5129 unit capacity units (PrtCapacityUnitTC). There is no convention
5130 associated with the media itself so this value essentially
5131 reflects claimed capacity. If this output sub-unit can reliably
5132 sense this value, the value is sensed by the printer and may
5133 not be changed by management requests; otherwise, the value may
5134 be written (by a Remote Control Panel or a Management
5135 Application). The value (-1) means other and specifically
5136 indicates that the sub-unit places no restrictions on this
5137 parameter. The value (-2) means unknown."
5138 ::= { prtOutputEntry 4 }
5139
5140prtOutputRemainingCapacity OBJECT-TYPE
5141 -- NOTE: In RFC 1759, the range was not defined.
5142 SYNTAX Integer32 (-3..2147483647)
5143 MAX-ACCESS read-write
5144 STATUS current
5145 DESCRIPTION
5146 "The remaining capacity of the possible output sub-unit
5147 capacity in output sub-unit capacity units
5148 (PrtCapacityUnitTC)of this output sub-unit. If this output sub-
5149 unit can reliably sense this value, the value is sensed by the
5150 printer and may not be modified by management requests;
5151
5152
5153
5154Bergman, et al. Standards Track [Page 92]
5155\f
5156RFC 3805 Printer MIB v2 June 2004
5157
5158
5159 otherwise, the value may be written (by a Remote Control Panel
5160 or a Management Application). The value (-1) means other and
5161 specifically indicates that the sub-unit places no restrictions
5162 on this parameter. The value (-2) means unknown. The value
5163 (-3) means that the printer knows that there remains capacity
5164 for at least one unit."
5165 ::= { prtOutputEntry 5 }
5166
5167prtOutputStatus OBJECT-TYPE
5168 SYNTAX PrtSubUnitStatusTC
5169 MAX-ACCESS read-only
5170 STATUS current
5171 DESCRIPTION
5172 "The current status of this output sub-unit."
5173 ::= { prtOutputEntry 6 }
5174
5175-- OUTPUT MEASUREMENT
5176--
5177-- _______ | | ________
5178-- ^ | | ^
5179-- | | | |
5180-- | | |RemainingCapacity
5181-- MaxCapacity| | |
5182-- | | | v ^
5183-- | |_ _ _ _ _ _ _ _ | _______________ |direction
5184-- | | Sheets | |
5185-- | | in |
5186-- v | Output |
5187-- _______ +________________+
5188
5189-- The Extended Output Group
5190
5191prtOutputName OBJECT-TYPE
5192 SYNTAX OCTET STRING (SIZE(0..63))
5193 MAX-ACCESS read-write
5194 STATUS current
5195 DESCRIPTION
5196 "The name assigned to this output sub-unit."
5197 ::= { prtOutputEntry 7 }
5198
5199prtOutputVendorName OBJECT-TYPE
5200 SYNTAX OCTET STRING (SIZE(0..63))
5201 MAX-ACCESS read-only
5202 STATUS current
5203 DESCRIPTION
5204 "The vendor name of this output sub-unit."
5205 ::= { prtOutputEntry 8 }
5206
5207
5208
5209
5210Bergman, et al. Standards Track [Page 93]
5211\f
5212RFC 3805 Printer MIB v2 June 2004
5213
5214
5215prtOutputModel OBJECT-TYPE
5216 SYNTAX OCTET STRING (SIZE(0..63))
5217 MAX-ACCESS read-only
5218 STATUS current
5219 DESCRIPTION
5220 "The model name assigned to this output sub-unit.
5221
5222 NOTE: The above description has been modified from RFC 1759
5223 for clarification."
5224 ::= { prtOutputEntry 9 }
5225
5226prtOutputVersion OBJECT-TYPE
5227 SYNTAX OCTET STRING (SIZE(0..63))
5228 MAX-ACCESS read-only
5229 STATUS current
5230 DESCRIPTION
5231 "The version of this output sub-unit."
5232 ::= { prtOutputEntry 10 }
5233
5234prtOutputSerialNumber OBJECT-TYPE
5235 SYNTAX OCTET STRING (SIZE(0..63))
5236 MAX-ACCESS read-only
5237 STATUS current
5238 DESCRIPTION
5239 "The serial number assigned to this output sub-unit."
5240 ::= { prtOutputEntry 11 }
5241
5242prtOutputDescription OBJECT-TYPE
5243 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
5244 -- to a TC to better support localization of the object.
5245 SYNTAX PrtLocalizedDescriptionStringTC
5246 MAX-ACCESS read-only
5247 STATUS current
5248 DESCRIPTION
5249 "A free-form text description of this output sub-unit in the
5250 localization specified by prtGeneralCurrentLocalization."
5251 ::= { prtOutputEntry 12 }
5252
5253prtOutputSecurity OBJECT-TYPE
5254 SYNTAX PresentOnOff
5255 MAX-ACCESS read-write
5256 STATUS current
5257 DESCRIPTION
5258 "Indicates if this output sub-unit has some security associated
5259 with it and if that security is enabled or not."
5260 ::= { prtOutputEntry 13 }
5261
5262
5263
5264
5265
5266Bergman, et al. Standards Track [Page 94]
5267\f
5268RFC 3805 Printer MIB v2 June 2004
5269
5270
5271-- The Output Dimensions Group
5272
5273prtOutputDimUnit OBJECT-TYPE
5274 SYNTAX PrtMediaUnitTC
5275 MAX-ACCESS read-only
5276 STATUS current
5277 DESCRIPTION
5278 "The unit of measurement for use in calculating and relaying
5279 dimensional values for this output sub-unit."
5280 ::= { prtOutputEntry 14 }
5281
5282prtOutputMaxDimFeedDir OBJECT-TYPE
5283 -- NOTE: In RFC 1759, the range was not defined.
5284 SYNTAX Integer32 (-2..2147483647)
5285 MAX-ACCESS read-write
5286 STATUS current
5287 DESCRIPTION
5288 "The maximum dimensions supported by this output sub-unit
5289 for measurements taken parallel relative to the feed
5290 direction associated with that sub-unit in output
5291 sub-unit dimensional units (controlled by prtOutputDimUnit,
5292 which uses PrtMediaUnitTC). If this output sub-unit can
5293 reliably sense this value, the value is sensed by the printer
5294 and may not be changed with management protocol operations.
5295 The value (-1) means other and specifically indicates that the
5296 sub-unit places no restrictions on this parameter. The value
5297 (-2) means unknown.
5298
5299 NOTE: The above description has been modified from RFC 1759
5300 for clarification and to explain the purpose of (-1) and (-2)."
5301 ::= { prtOutputEntry 15 }
5302
5303prtOutputMaxDimXFeedDir OBJECT-TYPE
5304 -- NOTE: In RFC 1759, the range was not defined.
5305 SYNTAX Integer32 (-2..2147483647)
5306 MAX-ACCESS read-write
5307 STATUS current
5308 DESCRIPTION
5309 "The maximum dimensions supported by this output sub-unit
5310 for measurements taken ninety degrees relative to the
5311 feed direction associated with that sub-unit in output
5312 sub-unit dimensional units (controlled by prtOutputDimUnit,
5313 which uses PrtMediaUnitTC). If this output sub-unit can
5314 reliably sense this value, the value is sensed by the printer
5315 and may not be changed with management protocol operations.
5316 The value (-1) means other and specifically indicates that the
5317 sub-unit places no restrictions on this parameter. The value
5318 (-2) means unknown.
5319
5320
5321
5322Bergman, et al. Standards Track [Page 95]
5323\f
5324RFC 3805 Printer MIB v2 June 2004
5325
5326
5327 NOTE: The above description has been modified from RFC 1759
5328 for clarification and to explain the purpose of (-1) and (-2)."
5329 ::= { prtOutputEntry 16 }
5330
5331prtOutputMinDimFeedDir OBJECT-TYPE
5332 -- NOTE: In RFC 1759, the range was not defined.
5333 SYNTAX Integer32 (-2..2147483647)
5334 MAX-ACCESS read-write
5335 STATUS current
5336 DESCRIPTION
5337 "The minimum dimensions supported by this output sub-unit
5338 for measurements taken parallel relative to the feed
5339 direction associated with that sub-unit in output
5340 sub-unit dimensional units (controlled by prtOutputDimUnit,
5341 which uses PrtMediaUnitTC). If this output sub-unit can
5342 reliably sense this value, the value is sensed by the printer
5343 and may not be changed with management protocol operations.
5344 The value (-1) means other and specifically indicates that the
5345 sub-unit places no restrictions on this parameter. The value
5346 (-2) means unknown.
5347
5348 NOTE: The above description has been modified from RFC 1759
5349 for clarification and to explain the purpose of (-1) and (-2)."
5350 ::= { prtOutputEntry 17 }
5351
5352prtOutputMinDimXFeedDir OBJECT-TYPE
5353 -- NOTE: In RFC 1759, the range was not defined.
5354 SYNTAX Integer32 (-2..2147483647)
5355 MAX-ACCESS read-write
5356 STATUS current
5357 DESCRIPTION
5358 "The minimum dimensions supported by this output sub-unit
5359 for measurements taken ninety degrees relative to the
5360 feed direction associated with that sub-unit in output
5361 sub-unit dimensional units (controlled by prtOutputDimUnit,
5362 which uses PrtMediaUnitTC). If this output sub-unit can
5363 reliably sense this value, the value is sensed by the printer
5364 and may not be changed with management protocol operations.
5365 The value (-1) means other and specifically indicates that the
5366 sub-unit places no restrictions on this parameter. The value
5367 (-2) means unknown.
5368
5369 NOTE: The above description has been modified from RFC 1759
5370 for clarification and to explain the purpose of (-1) and (-2)."
5371 ::= { prtOutputEntry 18 }
5372
5373
5374
5375
5376
5377
5378Bergman, et al. Standards Track [Page 96]
5379\f
5380RFC 3805 Printer MIB v2 June 2004
5381
5382
5383-- The Output Features Group
5384
5385prtOutputStackingOrder OBJECT-TYPE
5386 -- NOTE: In RFC 1759, the enumeration values were implicitly
5387 -- defined by this object.
5388 SYNTAX PrtOutputStackingOrderTC
5389 MAX-ACCESS read-write
5390 STATUS current
5391 DESCRIPTION
5392 "The current state of the stacking order for the
5393 associated output sub-unit. 'FirstToLast' means
5394 that as pages are output the front of the next page is
5395 placed against the back of the previous page.
5396 'LasttoFirst' means that as pages are output the back
5397 of the next page is placed against the front of the
5398 previous page."
5399 ::= { prtOutputEntry 19 }
5400
5401prtOutputPageDeliveryOrientation OBJECT-TYPE
5402 -- NOTE: In RFC 1759, the enumeration values were implicitly
5403 -- defined by this object.
5404 SYNTAX PrtOutputPageDeliveryOrientationTC
5405 MAX-ACCESS read-write
5406 STATUS current
5407 DESCRIPTION
5408 "The reading surface that will be 'up' when pages are
5409 delivered to the associated output sub-unit. Values are
5410 faceUp and faceDown. (Note: interpretation of these
5411 values is in general context-dependent based on locale;
5412 presentation of these values to an end-user should be
5413 normalized to the expectations of the user)."
5414 ::= { prtOutputEntry 20 }
5415
5416prtOutputBursting OBJECT-TYPE
5417 SYNTAX PresentOnOff
5418 MAX-ACCESS read-write
5419 STATUS current
5420 DESCRIPTION
5421 "This object indicates that the outputting sub-unit supports
5422 bursting, and if so, whether the feature is enabled. Bursting
5423 is the process by which continuous media is separated into
5424 individual sheets, typically by bursting along pre-formed
5425 perforations."
5426 ::= { prtOutputEntry 21 }
5427
5428prtOutputDecollating OBJECT-TYPE
5429 SYNTAX PresentOnOff
5430 MAX-ACCESS read-write
5431
5432
5433
5434Bergman, et al. Standards Track [Page 97]
5435\f
5436RFC 3805 Printer MIB v2 June 2004
5437
5438
5439 STATUS current
5440 DESCRIPTION
5441 "This object indicates that the output supports decollating,
5442 and if so, whether the feature is enabled. Decollating is the
5443 process by which the individual parts within a multi-part form
5444 are separated and sorted into separate stacks for each part."
5445 ::= { prtOutputEntry 22 }
5446
5447prtOutputPageCollated OBJECT-TYPE
5448 SYNTAX PresentOnOff
5449 MAX-ACCESS read-write
5450 STATUS current
5451 DESCRIPTION
5452 "This object indicates that the output sub-unit supports page
5453 collation, and if so, whether the feature is enabled. See RFC
5454 3805 Appendix A, Glossary Of Terms, for definition of how this
5455 document defines collation.
5456
5457 NOTE: The above description has been modified from RFC 1759
5458 for clarification."
5459 ::= { prtOutputEntry 23 }
5460
5461prtOutputOffsetStacking OBJECT-TYPE
5462 SYNTAX PresentOnOff
5463 MAX-ACCESS read-write
5464 STATUS current
5465 DESCRIPTION
5466 "This object indicates that the output supports offset
5467 stacking,and if so, whether the feature is enabled. See RFC
5468 3805 Appendix A, Glossary Of Terms, for how Offset Stacking is
5469 defined by this document.
5470
5471 NOTE: The above description has been modified from RFC 1759
5472 for clarification."
5473 ::= { prtOutputEntry 24 }
5474
5475-- The Marker Group
5476--
5477-- A marker is the mechanism that produces marks on the print
5478-- media. The marker sub-units and their associated supplies are
5479-- represented by the Marker Group in the model. A printer can
5480-- contain one or more marking mechanisms. Some examples of
5481-- multiple marker sub-units are: a printer
5482-- with separate markers for normal and magnetic ink or an
5483-- imagesetter that can output to both a proofing device and
5484-- final film. Each marking device can have its own set of
5485-- characteristics associated with it, such as marking technology
5486-- and resolution.
5487
5488
5489
5490Bergman, et al. Standards Track [Page 98]
5491\f
5492RFC 3805 Printer MIB v2 June 2004
5493
5494
5495prtMarker OBJECT IDENTIFIER ::= { printmib 10 }
5496
5497-- The printable area margins as listed below define an area of
5498-- the print media which is guaranteed to be printable for all
5499-- combinations of input, media paths, and interpreters for this
5500-- marker.
5501
5502prtMarkerTable OBJECT-TYPE
5503 SYNTAX SEQUENCE OF PrtMarkerEntry
5504 MAX-ACCESS not-accessible
5505 STATUS current
5506 DESCRIPTION
5507 "The marker table provides a description of each marker
5508 sub-unit contained within the printer.
5509
5510 NOTE: The above description has been modified from RFC 1759
5511 for clarification."
5512 ::= { prtMarker 2 }
5513
5514prtMarkerEntry OBJECT-TYPE
5515 SYNTAX PrtMarkerEntry
5516 MAX-ACCESS not-accessible
5517 STATUS current
5518 DESCRIPTION
5519 "Entries in this table define the characteristics and status
5520 of each marker sub-unit in the printer.
5521
5522 NOTE: The above description has been modified from RFC 1759
5523 for clarification."
5524 INDEX { hrDeviceIndex, prtMarkerIndex }
5525 ::= { prtMarkerTable 1 }
5526
5527PrtMarkerEntry ::= SEQUENCE {
5528 prtMarkerIndex Integer32,
5529 prtMarkerMarkTech PrtMarkerMarkTechTC,
5530 prtMarkerCounterUnit PrtMarkerCounterUnitTC,
5531 prtMarkerLifeCount Counter32,
5532 prtMarkerPowerOnCount Counter32,
5533 prtMarkerProcessColorants Integer32,
5534 prtMarkerSpotColorants Integer32,
5535 prtMarkerAddressabilityUnit PrtMarkerAddressabilityUnitTC,
5536 prtMarkerAddressabilityFeedDir Integer32,
5537 prtMarkerAddressabilityXFeedDir Integer32,
5538 prtMarkerNorthMargin Integer32,
5539 prtMarkerSouthMargin Integer32,
5540 prtMarkerWestMargin Integer32,
5541 prtMarkerEastMargin Integer32,
5542 prtMarkerStatus PrtSubUnitStatusTC
5543
5544
5545
5546Bergman, et al. Standards Track [Page 99]
5547\f
5548RFC 3805 Printer MIB v2 June 2004
5549
5550
5551 }
5552
5553prtMarkerIndex OBJECT-TYPE
5554 SYNTAX Integer32 (1..65535)
5555 MAX-ACCESS not-accessible
5556 STATUS current
5557 DESCRIPTION
5558 "A unique value used by the printer to identify this marking
5559 SubUnit. Although these values may change due to a major
5560 reconfiguration of the device (e.g., the addition of new marking
5561 sub-units to the printer), values SHOULD remain stable across
5562 successive printer power cycles.
5563
5564 NOTE: The above description has been modified from RFC 1759
5565 for clarification."
5566 ::= { prtMarkerEntry 1 }
5567
5568prtMarkerMarkTech OBJECT-TYPE
5569 -- NOTE: In RFC 1759, the enumeration values were implicitly
5570 -- defined by this object.
5571 SYNTAX PrtMarkerMarkTechTC
5572 MAX-ACCESS read-only
5573 STATUS current
5574 DESCRIPTION
5575 "The type of marking technology used for this marking
5576 sub-unit."
5577 ::= { prtMarkerEntry 2 }
5578
5579prtMarkerCounterUnit OBJECT-TYPE
5580 -- NOTE: In RFC 1759, the enumeration values were implicitly
5581 -- defined by this object.
5582 SYNTAX PrtMarkerCounterUnitTC
5583 MAX-ACCESS read-only
5584 STATUS current
5585 DESCRIPTION
5586 "The unit that will be used by the printer when reporting
5587 counter values for this marking sub-unit. The time units of
5588 measure are provided for a device like a strip recorder that
5589 does not or cannot track the physical dimensions of the media
5590 and does not use characters, lines or sheets."
5591 ::= { prtMarkerEntry 3 }
5592
5593prtMarkerLifeCount OBJECT-TYPE
5594 SYNTAX Counter32
5595 MAX-ACCESS read-only
5596 STATUS current
5597 DESCRIPTION
5598 "The count of the number of units of measure counted during the
5599
5600
5601
5602Bergman, et al. Standards Track [Page 100]
5603\f
5604RFC 3805 Printer MIB v2 June 2004
5605
5606
5607 life of printer using units of measure as specified by
5608 prtMarkerCounterUnit.
5609
5610 Note: This object should be implemented as a persistent object
5611 with a reliable value throughout the lifetime of the printer."
5612 ::= { prtMarkerEntry 4 }
5613
5614prtMarkerPowerOnCount OBJECT-TYPE
5615 SYNTAX Counter32
5616 MAX-ACCESS read-only
5617 STATUS current
5618 DESCRIPTION
5619 "The count of the number of units of measure counted since the
5620 equipment was most recently powered on using units of measure
5621 as specified by prtMarkerCounterUnit."
5622 ::= { prtMarkerEntry 5 }
5623
5624prtMarkerProcessColorants OBJECT-TYPE
5625 SYNTAX Integer32 (0..65535)
5626 MAX-ACCESS read-only
5627 STATUS current
5628 DESCRIPTION
5629 "The number of process colors supported by this marker. A
5630 process color of 1 implies monochrome. The value of this
5631 object and prtMarkerSpotColorants cannot both be 0. The value
5632 of prtMarkerProcessColorants must be 0 or greater.
5633
5634 NOTE: The above description has been modified from RFC 1759
5635 for clarification."
5636 ::= { prtMarkerEntry 6 }
5637
5638prtMarkerSpotColorants OBJECT-TYPE
5639 SYNTAX Integer32 (0..65535)
5640 MAX-ACCESS read-only
5641 STATUS current
5642 DESCRIPTION
5643 "The number of spot colors supported by this marker. The value
5644 of this object and prtMarkerProcessColorants cannot both be 0.
5645 Must be 0 or greater.
5646
5647 NOTE: The above description has been modified from RFC 1759
5648 for clarification."
5649 ::= { prtMarkerEntry 7 }
5650
5651prtMarkerAddressabilityUnit OBJECT-TYPE
5652 -- NOTE: In RFC 1759, the enumeration values were implicitly
5653 -- defined by this object.
5654 SYNTAX PrtMarkerAddressabilityUnitTC
5655
5656
5657
5658Bergman, et al. Standards Track [Page 101]
5659\f
5660RFC 3805 Printer MIB v2 June 2004
5661
5662
5663 MAX-ACCESS read-only
5664 STATUS current
5665 DESCRIPTION
5666 "The unit of measure of distances, as applied to the marker's
5667 resolution.
5668
5669 NOTE: The above description has been modified from RFC 1759
5670 for clarification."
5671 ::= { prtMarkerEntry 8 }
5672
5673prtMarkerAddressabilityFeedDir OBJECT-TYPE
5674 -- NOTE: In RFC 1759, the range was not defined.
5675 SYNTAX Integer32 (-2..2147483647)
5676 MAX-ACCESS read-only
5677 STATUS current
5678 DESCRIPTION
5679 "The maximum number of addressable marking positions in the
5680 feed direction per 10000 units of measure specified by
5681 prtMarkerAddressabilityUnit. A value of (-1) implies 'other'
5682 or 'infinite' while a value of (-2) implies 'unknown'.
5683
5684 NOTE: The above description has been modified from RFC 1759
5685 for clarification."
5686 ::= { prtMarkerEntry 9 }
5687
5688prtMarkerAddressabilityXFeedDir OBJECT-TYPE
5689 -- NOTE: In RFC 1759, the range was not defined.
5690 SYNTAX Integer32 (-2..2147483647)
5691 MAX-ACCESS read-only
5692 STATUS current
5693 DESCRIPTION
5694 "The maximum number of addressable marking positions in the
5695 cross feed direction in 10000 units of measure specified by
5696 prtMarkerAddressabilityUnit. A value of (-1) implies 'other'
5697 or 'infinite' while a value of (-2) implies 'unknown'.
5698
5699 NOTE: The above description has been modified from RFC 1759
5700 for clarification."
5701 ::= { prtMarkerEntry 10 }
5702
5703prtMarkerNorthMargin OBJECT-TYPE
5704 -- NOTE: In RFC 1759, the range was not defined.
5705 SYNTAX Integer32 (-2..2147483647)
5706 MAX-ACCESS read-only
5707 STATUS current
5708 DESCRIPTION
5709 "The margin, in units identified by prtMarkerAddressabilityUnit,
5710 from the leading edge of the medium as the medium flows through
5711
5712
5713
5714Bergman, et al. Standards Track [Page 102]
5715\f
5716RFC 3805 Printer MIB v2 June 2004
5717
5718
5719 the marking engine with the side to be imaged facing the
5720 observer. The leading edge is the North edge and the other
5721 edges are defined by the normal compass layout of directions
5722 with the compass facing the observer. Printing within the area
5723 bounded by all four margins is guaranteed for all interpreters.
5724 The value (-2) means unknown."
5725 ::= { prtMarkerEntry 11 }
5726
5727prtMarkerSouthMargin OBJECT-TYPE
5728 -- NOTE: In RFC 1759, the range was not defined.
5729 SYNTAX Integer32 (-2..2147483647)
5730 MAX-ACCESS read-only
5731 STATUS current
5732 DESCRIPTION
5733 "The margin from the South edge (see prtMarkerNorthMargin) of
5734 the medium in units identified by prtMarkerAddressabilityUnit.
5735 Printing within the area bounded by all four margins is
5736 guaranteed for all interpreters. The value (-2) means unknown."
5737 ::= { prtMarkerEntry 12 }
5738
5739prtMarkerWestMargin OBJECT-TYPE
5740 -- NOTE: In RFC 1759, the range was not defined.
5741 SYNTAX Integer32 (-2..2147483647)
5742 MAX-ACCESS read-only
5743 STATUS current
5744 DESCRIPTION
5745 "The margin from the West edge (see prtMarkerNorthMargin) of
5746 the medium in units identified by prtMarkerAddressabilityUnit.
5747 Printing within the area bounded by all four margins is
5748 guaranteed for all interpreters. The value (-2) means unknown."
5749 ::= { prtMarkerEntry 13 }
5750
5751prtMarkerEastMargin OBJECT-TYPE
5752 -- NOTE: In RFC 1759, the range was not defined.
5753 SYNTAX Integer32 (-2..2147483647)
5754 MAX-ACCESS read-only
5755 STATUS current
5756 DESCRIPTION
5757 "The margin from the East edge (see prtMarkerNorthMargin) of
5758 the medium in units identified by prtMarkerAddressabilityUnit.
5759 Printing within the area bounded by all four margins is
5760 guaranteed for all interpreters. The value (-2) means unknown."
5761 ::= { prtMarkerEntry 14 }
5762
5763prtMarkerStatus OBJECT-TYPE
5764 SYNTAX PrtSubUnitStatusTC
5765 MAX-ACCESS read-only
5766 STATUS current
5767
5768
5769
5770Bergman, et al. Standards Track [Page 103]
5771\f
5772RFC 3805 Printer MIB v2 June 2004
5773
5774
5775 DESCRIPTION
5776 "The current status of this marker sub-unit."
5777 ::= { prtMarkerEntry 15 }
5778
5779-- The Marker Supplies Group
5780
5781prtMarkerSupplies OBJECT IDENTIFIER ::= { printmib 11 }
5782
5783prtMarkerSuppliesTable OBJECT-TYPE
5784 SYNTAX SEQUENCE OF PrtMarkerSuppliesEntry
5785 MAX-ACCESS not-accessible
5786 STATUS current
5787 DESCRIPTION
5788 "A table of the marker supplies available on this printer."
5789 ::= { prtMarkerSupplies 1 }
5790
5791prtMarkerSuppliesEntry OBJECT-TYPE
5792 SYNTAX PrtMarkerSuppliesEntry
5793 MAX-ACCESS not-accessible
5794 STATUS current
5795 DESCRIPTION
5796 "Attributes of a marker supply. Entries may exist in the table
5797 for each device index with a device type of 'printer'.
5798
5799 NOTE: The above description has been modified from RFC 1759
5800 for clarification."
5801 INDEX { hrDeviceIndex, prtMarkerSuppliesIndex }
5802 ::= { prtMarkerSuppliesTable 1 }
5803PrtMarkerSuppliesEntry ::= SEQUENCE {
5804 prtMarkerSuppliesIndex Integer32,
5805 prtMarkerSuppliesMarkerIndex Integer32,
5806 prtMarkerSuppliesColorantIndex Integer32,
5807 prtMarkerSuppliesClass PrtMarkerSuppliesClassTC,
5808 prtMarkerSuppliesType PrtMarkerSuppliesTypeTC,
5809 prtMarkerSuppliesDescription PrtLocalizedDescriptionStringTC,
5810 prtMarkerSuppliesSupplyUnit PrtMarkerSuppliesSupplyUnitTC,
5811 prtMarkerSuppliesMaxCapacity Integer32,
5812 prtMarkerSuppliesLevel Integer32
5813 }
5814
5815prtMarkerSuppliesIndex OBJECT-TYPE
5816 SYNTAX Integer32 (1..65535)
5817 MAX-ACCESS not-accessible
5818 STATUS current
5819 DESCRIPTION
5820 "A unique value used by the printer to identify this marker
5821 supply. Although these values may change due to a major
5822 reconfiguration of the device (e.g., the addition of new marker
5823
5824
5825
5826Bergman, et al. Standards Track [Page 104]
5827\f
5828RFC 3805 Printer MIB v2 June 2004
5829
5830
5831 supplies to the printer), values SHOULD remain stable across
5832 successive printer power cycles.
5833
5834 NOTE: The above description has been modified from RFC 1759
5835 for clarification."
5836 ::= { prtMarkerSuppliesEntry 1 }
5837
5838prtMarkerSuppliesMarkerIndex OBJECT-TYPE
5839 SYNTAX Integer32 (0..65535)
5840 MAX-ACCESS read-only
5841 STATUS current
5842 DESCRIPTION
5843 "The value of prtMarkerIndex corresponding to the marking sub
5844 unit with which this marker supply sub-unit is associated."
5845 ::= { prtMarkerSuppliesEntry 2 }
5846
5847prtMarkerSuppliesColorantIndex OBJECT-TYPE
5848 SYNTAX Integer32 (0..65535)
5849 MAX-ACCESS read-only
5850 STATUS current
5851 DESCRIPTION
5852 "The value of prtMarkerColorantIndex corresponding to the
5853 colorant with which this marker supply sub-unit is associated.
5854 This value shall be 0 if there is no colorant table or if this
5855 supply does not depend on a single specified colorant.
5856 NOTE: The above description has been modified from RFC 1759
5857 for clarification."
5858 ::= { prtMarkerSuppliesEntry 3 }
5859
5860prtMarkerSuppliesClass OBJECT-TYPE
5861 -- NOTE: In RFC 1759, the enumeration values were implicitly
5862 -- defined by this object.
5863 SYNTAX PrtMarkerSuppliesClassTC
5864 MAX-ACCESS read-only
5865 STATUS current
5866 DESCRIPTION
5867 "Indicates whether this supply entity represents a supply that
5868 is consumed or a receptacle that is filled.
5869
5870 NOTE: The above description has been modified from RFC 1759
5871 for clarification."
5872 ::= { prtMarkerSuppliesEntry 4 }
5873
5874prtMarkerSuppliesType OBJECT-TYPE
5875 -- NOTE: In RFC 1759, the enumeration values were implicitly
5876 -- defined by this object.
5877 SYNTAX PrtMarkerSuppliesTypeTC
5878 MAX-ACCESS read-only
5879
5880
5881
5882Bergman, et al. Standards Track [Page 105]
5883\f
5884RFC 3805 Printer MIB v2 June 2004
5885
5886
5887 STATUS current
5888 DESCRIPTION
5889 "The type of this supply."
5890 ::= { prtMarkerSuppliesEntry 5 }
5891
5892prtMarkerSuppliesDescription OBJECT-TYPE
5893 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
5894 -- to a TC to better support localization of the object.
5895 SYNTAX PrtLocalizedDescriptionStringTC
5896 MAX-ACCESS read-only
5897 STATUS current
5898 DESCRIPTION
5899 "The description of this supply container/receptacle in the
5900 localization specified by prtGeneralCurrentLocalization."
5901 ::= { prtMarkerSuppliesEntry 6 }
5902
5903prtMarkerSuppliesSupplyUnit OBJECT-TYPE
5904 -- NOTE: In RFC 1759, the enumeration values were implicitly
5905 -- defined by this object.
5906 SYNTAX PrtMarkerSuppliesSupplyUnitTC
5907 MAX-ACCESS read-only
5908 STATUS current
5909 DESCRIPTION
5910 "Unit of measure of this marker supply container/receptacle.
5911
5912 NOTE: The above description has been modified from RFC 1759
5913 for clarification."
5914 ::= { prtMarkerSuppliesEntry 7 }
5915
5916prtMarkerSuppliesMaxCapacity OBJECT-TYPE
5917 -- NOTE: In RFC 1759, the range was not defined.
5918 SYNTAX Integer32 (-2..2147483647)
5919 MAX-ACCESS read-write
5920 STATUS current
5921 DESCRIPTION
5922 "The maximum capacity of this supply container/receptacle
5923 expressed in prtMarkerSuppliesSupplyUnit. If this supply
5924 container/receptacle can reliably sense this value, the value
5925 is reported by the printer and is read-only; otherwise, the
5926 value may be written (by a Remote Control Panel or a Management
5927 Application). The value (-1) means other and specifically
5928 indicates that the sub-unit places no restrictions on this
5929 parameter. The value (-2) means unknown."
5930 ::= { prtMarkerSuppliesEntry 8 }
5931
5932prtMarkerSuppliesLevel OBJECT-TYPE
5933 -- NOTE: In RFC 1759, the range was not defined.
5934 SYNTAX Integer32 (-3..2147483647)
5935
5936
5937
5938Bergman, et al. Standards Track [Page 106]
5939\f
5940RFC 3805 Printer MIB v2 June 2004
5941
5942
5943 MAX-ACCESS read-write
5944 STATUS current
5945 DESCRIPTION
5946 "The current level if this supply is a container; the remaining
5947 space if this supply is a receptacle. If this supply
5948 container/receptacle can reliably sense this value, the value
5949 is reported by the printer and is read-only; otherwise, the
5950 value may be written (by a Remote Control Panel or a Management
5951 Application). The value (-1) means other and specifically
5952 indicates that the sub-unit places no restrictions on this
5953 parameter. The value (-2) means unknown. A value of (-3) means
5954 that the printer knows that there is some supply/remaining
5955 space, respectively."
5956 ::= { prtMarkerSuppliesEntry 9 }
5957
5958-- The Marker Colorant Group
5959
5960prtMarkerColorant OBJECT IDENTIFIER ::= { printmib 12 }
5961
5962prtMarkerColorantTable OBJECT-TYPE
5963 SYNTAX SEQUENCE OF PrtMarkerColorantEntry
5964 MAX-ACCESS not-accessible
5965 STATUS current
5966 DESCRIPTION
5967 "A table of all of the colorants available on the printer."
5968 ::= { prtMarkerColorant 1 }
5969
5970prtMarkerColorantEntry OBJECT-TYPE
5971 SYNTAX PrtMarkerColorantEntry
5972 MAX-ACCESS not-accessible
5973 STATUS current
5974 DESCRIPTION
5975 "Attributes of a colorant available on the printer. Entries may
5976 exist in the table for each device index with a device type of
5977 'printer'.
5978
5979 NOTE: The above description has been modified from RFC 1759
5980 for clarification."
5981 INDEX { hrDeviceIndex, prtMarkerColorantIndex }
5982 ::= { prtMarkerColorantTable 1 }
5983
5984PrtMarkerColorantEntry ::= SEQUENCE {
5985 prtMarkerColorantIndex Integer32,
5986 prtMarkerColorantMarkerIndex Integer32,
5987 prtMarkerColorantRole PrtMarkerColorantRoleTC,
5988 prtMarkerColorantValue OCTET STRING,
5989 prtMarkerColorantTonality Integer32
5990 }
5991
5992
5993
5994Bergman, et al. Standards Track [Page 107]
5995\f
5996RFC 3805 Printer MIB v2 June 2004
5997
5998
5999prtMarkerColorantIndex OBJECT-TYPE
6000 SYNTAX Integer32 (1..65535)
6001 MAX-ACCESS not-accessible
6002 STATUS current
6003 DESCRIPTION
6004 "A unique value used by the printer to identify this colorant.
6005 Although these values may change due to a major reconfiguration
6006 of the device (e.g., the addition of new colorants to the
6007 printer) , values SHOULD remain stable across successive
6008 printer power cycles.
6009
6010 NOTE: The above description has been modified from RFC 1759
6011 for clarification."
6012 ::= { prtMarkerColorantEntry 1 }
6013
6014prtMarkerColorantMarkerIndex OBJECT-TYPE
6015 SYNTAX Integer32 (0..65535)
6016 MAX-ACCESS read-only
6017 STATUS current
6018 DESCRIPTION
6019 "The value of prtMarkerIndex corresponding to the marker sub
6020 unit with which this colorant entry is associated."
6021 ::= { prtMarkerColorantEntry 2 }
6022
6023prtMarkerColorantRole OBJECT-TYPE
6024 -- NOTE: In RFC 1759, the enumeration values were implicitly
6025 -- defined by this object.
6026 SYNTAX PrtMarkerColorantRoleTC
6027 MAX-ACCESS read-only
6028 STATUS current
6029 DESCRIPTION
6030 "The role played by this colorant."
6031 ::= { prtMarkerColorantEntry 3 }
6032
6033prtMarkerColorantValue OBJECT-TYPE
6034 -- NOTE: The string length range has been increased from RFC 1759.
6035 SYNTAX OCTET STRING (SIZE(0..255))
6036 MAX-ACCESS read-only
6037 STATUS current
6038 DESCRIPTION
6039 "The name of the color of this colorant using standardized
6040 string names from ISO 10175 (DPA) and ISO 10180 (SPDL) such as:
6041 other
6042 unknown
6043 white
6044 red
6045 green
6046 blue
6047
6048
6049
6050Bergman, et al. Standards Track [Page 108]
6051\f
6052RFC 3805 Printer MIB v2 June 2004
6053
6054
6055 cyan
6056 magenta
6057 yellow
6058 black
6059 Implementers may add additional string values. The naming
6060 conventions in ISO 9070 are recommended in order to avoid
6061 potential name clashes"
6062 ::= { prtMarkerColorantEntry 4 }
6063
6064prtMarkerColorantTonality OBJECT-TYPE
6065 -- NOTE: In RFC 1759, the range was not defined.
6066 SYNTAX Integer32 (2..2147483647)
6067 MAX-ACCESS read-only
6068 STATUS current
6069 DESCRIPTION
6070 "The distinct levels of tonality realizable by a marking sub
6071 unit when using this colorant. This value does not include the
6072 number of levels of tonal difference that an interpreter can
6073 obtain by techniques such as half toning. This value must be at
6074 least 2."
6075 ::= { prtMarkerColorantEntry 5 }
6076
6077-- The Media Path Group
6078--
6079-- The media paths encompass the mechanisms in the printer that
6080-- move the media through the printer and connect all other media
6081-- related sub-units: inputs, outputs, markers and finishers. A
6082-- printer contains one or more media paths. These are
6083-- represented by the Media Path Group in the model.
6084
6085prtMediaPath OBJECT IDENTIFIER ::= { printmib 13 }
6086
6087prtMediaPathTable OBJECT-TYPE
6088 SYNTAX SEQUENCE OF PrtMediaPathEntry
6089 MAX-ACCESS not-accessible
6090 STATUS current
6091 DESCRIPTION
6092 "The media path table includes both physical and logical paths
6093 within the printer.
6094
6095 NOTE: The above description has been modified from RFC 1759
6096 for clarification."
6097 ::= { prtMediaPath 4 }
6098
6099prtMediaPathEntry OBJECT-TYPE
6100 SYNTAX PrtMediaPathEntry
6101 MAX-ACCESS not-accessible
6102 STATUS current
6103
6104
6105
6106Bergman, et al. Standards Track [Page 109]
6107\f
6108RFC 3805 Printer MIB v2 June 2004
6109
6110
6111 DESCRIPTION
6112 "Entries may exist in the table for each device index with a
6113 device type of 'printer' Each entry defines the physical
6114 characteristics of and the status of the media path. The data
6115 provided indicates the maximum throughput and the media
6116 size limitations of these subunits.
6117
6118 NOTE: The above description has been modified from RFC 1759
6119 for clarification."
6120 INDEX { hrDeviceIndex, prtMediaPathIndex }
6121 ::= { prtMediaPathTable 1 }
6122
6123PrtMediaPathEntry ::= SEQUENCE {
6124 prtMediaPathIndex Integer32,
6125 prtMediaPathMaxSpeedPrintUnit PrtMediaPathMaxSpeedPrintUnitTC,
6126 prtMediaPathMediaSizeUnit PrtMediaUnitTC,
6127 prtMediaPathMaxSpeed Integer32,
6128 prtMediaPathMaxMediaFeedDir Integer32,
6129 prtMediaPathMaxMediaXFeedDir Integer32,
6130 prtMediaPathMinMediaFeedDir Integer32,
6131 prtMediaPathMinMediaXFeedDir Integer32,
6132 prtMediaPathType PrtMediaPathTypeTC,
6133 prtMediaPathDescription PrtLocalizedDescriptionStringTC,
6134 prtMediaPathStatus PrtSubUnitStatusTC
6135 }
6136
6137prtMediaPathIndex OBJECT-TYPE
6138 SYNTAX Integer32 (1..65535)
6139 MAX-ACCESS not-accessible
6140 STATUS current
6141 DESCRIPTION
6142 "A unique value used by the printer to identify this media
6143 path. Although these values may change due to a major
6144 reconfiguration of the device (e.g., the addition of new media
6145 paths to the printer), values SHOULD remain stable across
6146 successive printer power cycles.
6147
6148 NOTE: The above description has been modified from RFC 1759
6149 for clarification."
6150 ::= { prtMediaPathEntry 1 }
6151
6152prtMediaPathMaxSpeedPrintUnit OBJECT-TYPE
6153 -- NOTE: In RFC 1759, the enumeration values were implicitly
6154 -- defined by this object.
6155 SYNTAX PrtMediaPathMaxSpeedPrintUnitTC
6156 MAX-ACCESS read-only
6157 STATUS current
6158 DESCRIPTION
6159
6160
6161
6162Bergman, et al. Standards Track [Page 110]
6163\f
6164RFC 3805 Printer MIB v2 June 2004
6165
6166
6167 "The unit of measure used in specifying the speed of all media
6168 paths in the printer."
6169 ::= { prtMediaPathEntry 2 }
6170
6171prtMediaPathMediaSizeUnit OBJECT-TYPE
6172 SYNTAX PrtMediaUnitTC
6173 MAX-ACCESS read-only
6174 STATUS current
6175 DESCRIPTION
6176 "The units of measure of media size for use in calculating and
6177 relaying dimensional values for all media paths in the
6178 printer."
6179 ::= { prtMediaPathEntry 3 }
6180
6181prtMediaPathMaxSpeed OBJECT-TYPE
6182 -- NOTE: In RFC 1759, the range was not defined.
6183 SYNTAX Integer32 (-2..2147483647)
6184 MAX-ACCESS read-only
6185 STATUS current
6186 DESCRIPTION
6187 "The maximum printing speed of this media path expressed in
6188 prtMediaPathMaxSpeedUnit's. A value of (-1) implies 'other'."
6189 ::= { prtMediaPathEntry 4 }
6190
6191prtMediaPathMaxMediaFeedDir OBJECT-TYPE
6192 -- NOTE: In RFC 1759, the range was not defined.
6193 SYNTAX Integer32 (-2..2147483647)
6194 MAX-ACCESS read-only
6195 STATUS current
6196 DESCRIPTION
6197 "The maximum physical media size in the feed direction of this
6198 media path expressed in units of measure specified by
6199 PrtMediaPathMediaSizeUnit. A value of (-1) implies 'unlimited'
6200 a value of (-2) implies 'unknown'.
6201
6202 NOTE: The above description has been modified from RFC 1759
6203 for clarification."
6204 ::= { prtMediaPathEntry 5 }
6205
6206prtMediaPathMaxMediaXFeedDir OBJECT-TYPE
6207 -- NOTE: In RFC 1759, the range was not defined.
6208 SYNTAX Integer32 (-2..2147483647)
6209 MAX-ACCESS read-only
6210 STATUS current
6211 DESCRIPTION
6212 "The maximum physical media size across the feed direction of
6213 this media path expressed in units of measure specified by
6214 prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'.
6215
6216
6217
6218Bergman, et al. Standards Track [Page 111]
6219\f
6220RFC 3805 Printer MIB v2 June 2004
6221
6222
6223 NOTE: The above description has been modified from RFC 1759
6224 for clarification."
6225 ::= { prtMediaPathEntry 6 }
6226
6227prtMediaPathMinMediaFeedDir OBJECT-TYPE
6228 -- NOTE: In RFC 1759, the range was not defined.
6229 SYNTAX Integer32 (-2..2147483647)
6230 MAX-ACCESS read-only
6231 STATUS current
6232 DESCRIPTION
6233 "The minimum physical media size in the feed direction of this
6234 media path expressed in units of measure specified by
6235 prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'.
6236
6237 NOTE: The above description has been modified from RFC 1759
6238 for clarification."
6239 ::= { prtMediaPathEntry 7 }
6240
6241prtMediaPathMinMediaXFeedDir OBJECT-TYPE
6242 -- NOTE: In RFC 1759, the range was not defined.
6243 SYNTAX Integer32 (-2..2147483647)
6244 MAX-ACCESS read-only
6245 STATUS current
6246 DESCRIPTION
6247 "The minimum physical media size across the feed direction of
6248 this media path expressed in units of measure specified by
6249 prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'.
6250
6251 NOTE: The above description has been modified from RFC 1759
6252 for clarification."
6253 ::= { prtMediaPathEntry 8 }
6254
6255prtMediaPathType OBJECT-TYPE
6256 -- NOTE: In RFC 1759, the enumeration values were implicitly
6257 -- defined by this object.
6258 SYNTAX PrtMediaPathTypeTC
6259 MAX-ACCESS read-only
6260 STATUS current
6261 DESCRIPTION
6262 "The type of the media path for this media path."
6263 ::= { prtMediaPathEntry 9 }
6264
6265prtMediaPathDescription OBJECT-TYPE
6266 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
6267 -- to a TC to better support localization of the object.
6268 SYNTAX PrtLocalizedDescriptionStringTC
6269 MAX-ACCESS read-only
6270 STATUS current
6271
6272
6273
6274Bergman, et al. Standards Track [Page 112]
6275\f
6276RFC 3805 Printer MIB v2 June 2004
6277
6278
6279 DESCRIPTION
6280 "The manufacturer-provided description of this media path in
6281 the localization specified by prtGeneralCurrentLocalization."
6282 ::= { prtMediaPathEntry 10 }
6283
6284prtMediaPathStatus OBJECT-TYPE
6285 SYNTAX PrtSubUnitStatusTC
6286 MAX-ACCESS read-only
6287 STATUS current
6288 DESCRIPTION
6289 "The current status of this media path."
6290 ::= { prtMediaPathEntry 11 }
6291
6292-- The Print Job Delivery Channel Group
6293--
6294-- Print Job Delivery Channels are independent sources of print
6295-- data. Here, print data is the term used for the information
6296-- that is used to construct printed pages and may have both data
6297-- and control aspects. The output of a channel is in a form
6298-- suitable for input to one of the interpreters as a
6299-- stream. A channel may be independently enabled (allowing
6300-- print data to flow) or disabled (stopping the flow of
6301-- print data). A printer may have one or more channels.
6302--
6303-- The Print Job Delivery Channel table describes the
6304-- capabilities of the printer and not what is currently being
6305-- performed by the printer
6306--
6307-- Basically, the print job delivery channel abstraction
6308-- describes the final processing step of getting the print data
6309-- to an interpreter. It might include some level of
6310-- decompression or decoding of print stream data.
6311-- channel. All of these aspects are hidden in the channel
6312-- abstraction.
6313--
6314-- There are many kinds of print job delivery channels; some of
6315-- which are based on networks and others which are not. For
6316-- example, a channel can be a serial (or parallel) connection;
6317-- it can be a service, such as the UNIX Line Printer Daemon
6318-- (LPD), offering services over a network connection; or
6319-- it could be a disk drive into which a floppy disk with
6320-- the print data is inserted. Each print job delivery channel is
6321-- identified by the electronic path and/or service protocol
6322-- used to deliver print data to a print data interpreter.
6323--
6324-- Channel example Implementation
6325--
6326-- serial port channel bi-directional data channel
6327
6328
6329
6330Bergman, et al. Standards Track [Page 113]
6331\f
6332RFC 3805 Printer MIB v2 June 2004
6333
6334
6335-- parallel port channel often uni-directional channel
6336-- IEEE 1284 port channel bi-directional channel
6337-- SCSI port channel bi-directional
6338-- Apple PAP channel may be based on LocalTalk,
6339-- Ethernet or Tokentalk
6340-- LPD Server channel TCP/IP based, port 515
6341-- Netware Remote Printer SPX/IPX based channel
6342-- Netware Print Server SPX/IPX based channel
6343--
6344-- It is easy to note that this is a mixed bag. There are
6345-- some physical connections over which no (or very meager)
6346-- protocols are run (e.g., the serial or old parallel ports)
6347-- and there are services which often have elaborate
6348-- protocols that run over a number of protocol stacks. In
6349-- the end, what is important is the delivery of print data
6350-- through the channel.
6351--
6352-- The print job delivery channel sub-units are represented by
6353-- the Print Job Delivery Channel Group in the Model. It has a
6354-- current print job control language, which can be used to
6355-- specify which interpreter is to be used for the print data and
6356-- to query and change environment variables used by the
6357-- interpreters (and Management Applications). There is also a
6358-- default interpreter that is to be used if an interpreter is
6359-- not explicitly specified using the Control Language.
6360
6361-- The first seven items in the Print Job Delivery Channel Table
6362-- define the "channel" itself. A channel typically depends on
6363-- other protocols and interfaces to provide the data that flows
6364-- through the channel.
6365--
6366-- Control of a print job delivery channel is largely limited to
6367-- enabling or disabling the entire channel itself. It is likely
6368-- that more control of the process of accessing print data
6369-- will be needed over time. Thus, the ChannelType will
6370-- allow type-specific data to be associated with each
6371-- channel (using ChannelType specific groups in a fashion
6372-- analogous to the media specific MIBs that are associated
6373-- with the IANAIfType in the Interfaces Table). As a first
6374-- step in this direction, each channel will identify the
6375-- underlying Interface on which it is based. This is the
6376-- eighth object in each row of the table.
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386Bergman, et al. Standards Track [Page 114]
6387\f
6388RFC 3805 Printer MIB v2 June 2004
6389
6390
6391-- The Print Job Delivery Channel Table
6392
6393prtChannel OBJECT IDENTIFIER ::= { printmib 14 }
6394
6395prtChannelTable OBJECT-TYPE
6396 SYNTAX SEQUENCE OF PrtChannelEntry
6397 MAX-ACCESS not-accessible
6398 STATUS current
6399 DESCRIPTION
6400 "The channel table represents the set of input data sources
6401 which can provide print data to one or more of the
6402 interpreters available on a printer.
6403
6404 NOTE: The above description has been modified from RFC 1759
6405 for clarification."
6406 ::= { prtChannel 1 }
6407
6408prtChannelEntry OBJECT-TYPE
6409 SYNTAX PrtChannelEntry
6410 MAX-ACCESS not-accessible
6411 STATUS current
6412 DESCRIPTION
6413 "Entries may exist in the table for each device index with a
6414 device type of 'printer'. Each channel table entry is
6415 characterized by a unique protocol stack and/or addressing.
6416 The channel may also have printer dependent features that are
6417 associated with a printing language.
6418
6419 NOTE: The above description has been modified from RFC 1759
6420 for clarification."
6421 INDEX { hrDeviceIndex, prtChannelIndex }
6422 ::= { prtChannelTable 1 }
6423
6424PrtChannelEntry ::= SEQUENCE {
6425 prtChannelIndex Integer32,
6426 prtChannelType PrtChannelTypeTC,
6427 prtChannelProtocolVersion OCTET STRING,
6428 prtChannelCurrentJobCntlLangIndex Integer32,
6429 prtChannelDefaultPageDescLangIndex Integer32,
6430 prtChannelState PrtChannelStateTC,
6431 prtChannelIfIndex InterfaceIndexOrZero,
6432 prtChannelStatus PrtSubUnitStatusTC,
6433 prtChannelInformation OCTET STRING
6434 }
6435
6436prtChannelIndex OBJECT-TYPE
6437 -- NOTE: In RFC 1759, the range was not defined.
6438 SYNTAX Integer32 (1..65535)
6439
6440
6441
6442Bergman, et al. Standards Track [Page 115]
6443\f
6444RFC 3805 Printer MIB v2 June 2004
6445
6446
6447 MAX-ACCESS not-accessible
6448 STATUS current
6449 DESCRIPTION
6450 "A unique value used by the printer to identify this data
6451 channel. Although these values may change due to a major
6452 reconfiguration of the device (e.g., the addition of new data
6453 channels to the printer), values SHOULD remain stable across
6454 successive printer power cycles.
6455
6456 NOTE: The above description has been modified from RFC 1759
6457 for clarification."
6458 ::= { prtChannelEntry 1 }
6459
6460prtChannelType OBJECT-TYPE
6461 -- NOTE: In RFC 1759, the enumeration values were implicitly
6462 -- defined by this object.
6463 SYNTAX PrtChannelTypeTC
6464 MAX-ACCESS read-only
6465 STATUS current
6466 DESCRIPTION
6467 "The type of this print data channel. This object provides the
6468 linkage to ChannelType-specific groups that may (conceptually)
6469 extend the prtChannelTable with additional details about that
6470 channel."
6471 ::= { prtChannelEntry 2 }
6472
6473prtChannelProtocolVersion OBJECT-TYPE
6474 SYNTAX OCTET STRING (SIZE(0..63))
6475 MAX-ACCESS read-only
6476 STATUS current
6477 DESCRIPTION
6478 "The version of the protocol used on this channel. The format
6479 used for version numbering depends on prtChannelType."
6480 ::= { prtChannelEntry 3 }
6481
6482prtChannelCurrentJobCntlLangIndex OBJECT-TYPE
6483 -- NOTE: In RFC 1759, the range was not defined.
6484 SYNTAX Integer32 (0..65535)
6485 MAX-ACCESS read-write
6486 STATUS current
6487 DESCRIPTION
6488 "The value of prtInterpreterIndex corresponding to the Control
6489 Language Interpreter for this channel. This interpreter defines
6490 the syntax used for control functions, such as querying or
6491 changing environment variables and identifying job boundaries
6492 (e.g., PJL, PostScript, NPAP). A value of zero indicates that
6493 there is no current Job Control Language Interpreter for this
6494 channel.
6495
6496
6497
6498Bergman, et al. Standards Track [Page 116]
6499\f
6500RFC 3805 Printer MIB v2 June 2004
6501
6502
6503 NOTE: The above description has been modified from RFC 1759
6504 for clarification."
6505 ::= { prtChannelEntry 4 }
6506
6507prtChannelDefaultPageDescLangIndex OBJECT-TYPE
6508 -- NOTE: In RFC 1759, the range was not defined.
6509 SYNTAX Integer32 (0..65535)
6510 MAX-ACCESS read-write
6511 STATUS current
6512 DESCRIPTION
6513 "The value of prtInterpreterIndex corresponding to the Page
6514 Description Language Interpreter for this channel. This
6515 interpreter defines the default Page Description Language
6516 interpreter to be used for the print data unless the Control
6517 Language is used to select a specific interpreter (e.g., PCL,
6518 PostScript Language, auto-sense). A value of zero indicates
6519 that there is no default page description language interpreter
6520 for this channel.
6521
6522 NOTE: The above description has been modified from RFC 1759
6523 for clarification."
6524 ::= { prtChannelEntry 5 }
6525
6526prtChannelState OBJECT-TYPE
6527 -- NOTE: In RFC 1759, the enumeration values were implicitly
6528 -- defined by this object.
6529 SYNTAX PrtChannelStateTC
6530 MAX-ACCESS read-write
6531 STATUS current
6532 DESCRIPTION
6533 "The state of this print data channel. The value determines
6534 whether control information and print data is allowed through
6535 this channel or not."
6536 ::= { prtChannelEntry 6 }
6537
6538prtChannelIfIndex OBJECT-TYPE
6539 SYNTAX InterfaceIndexOrZero -- Was Integer32 in RFC 1759.
6540 MAX-ACCESS read-write
6541 STATUS current
6542 DESCRIPTION
6543 "The value of ifIndex in the ifTable; see the Interfaces Group
6544 MIB [RFC2863] which corresponds to this channel.
6545 When more than one row of the ifTable is relevant, this is the
6546 index of the row representing the topmost layer in the
6547 interface hierarchy. A value of zero indicates that no
6548 interface is associated with this channel.
6549
6550 NOTE: The above description has been modified from RFC 1759
6551
6552
6553
6554Bergman, et al. Standards Track [Page 117]
6555\f
6556RFC 3805 Printer MIB v2 June 2004
6557
6558
6559 for clarification."
6560 ::= { prtChannelEntry 7 }
6561
6562prtChannelStatus OBJECT-TYPE
6563 SYNTAX PrtSubUnitStatusTC
6564 MAX-ACCESS read-only
6565 STATUS current
6566 DESCRIPTION
6567 "The current status of the channel."
6568 ::= { prtChannelEntry 8 }
6569
6570prtChannelInformation OBJECT-TYPE
6571 SYNTAX OCTET STRING (SIZE (0..255))
6572 MAX-ACCESS read-only
6573 STATUS current
6574 DESCRIPTION
6575 "Auxiliary information to allow a printing application to use
6576 the channel for data submission to the printer. An application
6577 capable of using a specific PrtChannelType should be able to
6578 use the combined information from the prtChannelInformation and
6579 other channel and interface group objects to 'bootstrap' its
6580 use of the channel. prtChannelInformation is not intended to
6581 provide a general channel description, nor to provide
6582 information that is available once the channel is in use.
6583
6584 The encoding and interpretation of the prtChannelInformation
6585 object is specific to channel type. The description of each
6586 PrtChannelType enum value for which prtChannelInformation is
6587 defined specifies the appropriate encoding and interpretation,
6588 including interaction with other objects. For channel types
6589 that do not specify a prtChannelInformation value, its value
6590 shall be null (0 length).
6591
6592 When a new PrtChannelType enumeration value is registered, its
6593 accompanying description must specify the encoding and
6594 interpretation of the prtChannelInformation value for the
6595 channel type. prtChannelInformation semantics for an existing
6596 PrtChannelType may be added or amended in the same manner as
6597 described in section 2.4.1 for type 2 enumeration values.
6598
6599 The prtChannelInformation specifies values for a collection of
6600 channel attributes, represented as text according to the
6601 following rules:
6602
6603 1. The prtChannelInformation is not affected by localization.
6604
6605 2. The prtChannelInformation is a list of entries representing
6606 the attribute values. Each entry consists of the following
6607
6608
6609
6610Bergman, et al. Standards Track [Page 118]
6611\f
6612RFC 3805 Printer MIB v2 June 2004
6613
6614
6615 items, in order:
6616
6617 a. A keyword, composed of alphabetic characters (A-Z, a-z)
6618 represented by their NVT ASCII [RFC854] codes, that
6619 identifies a channel attribute,
6620
6621 b. The NVT ASCII code for an Equals Sign (=) (code 61) to
6622 delimit the keyword,
6623
6624 c. A data value encoded using rules specific to the
6625 PrtChannelType to with the prtChannelInformation applies which
6626 must in no case allow an octet with value 10 (the NVT ASCII
6627 Line Feed code),
6628
6629 d. the NVT ASCII code for a Line Feed character (code 10) to
6630 delimit the data value.
6631
6632 No other octets shall be present.
6633
6634 Keywords are case-sensitive. Conventionally, keywords are
6635 capitalized (including each word of a multi-word keyword) and
6636 since they occupy space in the prtChannelInformation, they are
6637 kept short.
6638
6639 3. If a channel attribute has multiple values, it is
6640 represented by multiple entries with the same keyword, each
6641 specifying one value. Otherwise, there shall be at most one
6642 entry for each attribute.
6643
6644 4. By default, entries may appear in any order. If there are
6645 ordering constraints for particular entries, these must be
6646 specified in their definitions.
6647
6648 5. The prtChannelInformation value by default consists of text
6649 represented by NVT ASCII graphics character codes. However,
6650 other representations may be specified:
6651
6652 a. In cases where the prtChannelInformation value contains
6653 information not normally coded in textual form, whatever
6654 symbolic representation is conventionally used for the
6655 information should be used for encoding the
6656 prtChannelInformation value. (For instance, a binary port value
6657 might be represented as a decimal number using NVT ASCII
6658 codes.) Such encoding must be specified in the definition of
6659 the value.
6660
6661 b. The value may contain textual information in a character set
6662 other than NVT ASCII graphics characters. (For instance, an
6663
6664
6665
6666Bergman, et al. Standards Track [Page 119]
6667\f
6668RFC 3805 Printer MIB v2 June 2004
6669
6670
6671 identifier might consist of ISO 10646 text encoded using the
6672 UTF-8 encoding scheme.) Such a character set and its encoding
6673 must be specified in the definition of the value.
6674
6675 6. For each PrtChannelType for which prtChannelInformation
6676 entries are defined, the descriptive text associated with the
6677 PrtChannelType enumeration value shall specify the following
6678 information for each entry:
6679
6680 Title: Brief description phrase, e.g.: 'Port name',
6681 'Service Name', etc.
6682
6683 Keyword: The keyword value, e.g.: 'Port' or 'Service'
6684
6685 Syntax: The encoding of the entry value if it cannot be
6686 directly represented by NVT ASCII.
6687
6688 Status: 'Mandatory', 'Optional', or 'Conditionally
6689 Mandatory'
6690
6691 Multiplicity: 'Single' or 'Multiple' to indicate whether the
6692 entry may be present multiple times.
6693
6694 Description: Description of the use of the entry, other
6695 information required to complete the definition
6696 (e.g.: ordering constraints, interactions between
6697 entries).
6698
6699 Applications that interpret prtChannelInformation should ignore
6700 unrecognized entries, so they are not affected if new entry
6701 types are added."
6702
6703 ::= { prtChannelEntry 9 }
6704
6705-- The Interpreter Group
6706--
6707-- The interpreter sub-units are responsible for the conversion
6708-- of a description of intended print instances into images that
6709-- are to be marked on the media. A printer may have one or more
6710-- interpreters. The interpreter sub-units are represented by the
6711-- Interpreter Group in the Model. Each interpreter is generally
6712-- implemented with software running on the System Controller
6713-- sub-unit. The Interpreter Table has one entry per interpreter
6714-- where the interpreters include both Page Description Language
6715-- (PDL) Interpreters and Control Language Interpreters.
6716
6717prtInterpreter OBJECT IDENTIFIER ::= { printmib 15 }
6718
6719
6720
6721
6722Bergman, et al. Standards Track [Page 120]
6723\f
6724RFC 3805 Printer MIB v2 June 2004
6725
6726
6727-- Interpreter Table
6728
6729prtInterpreterTable OBJECT-TYPE
6730 SYNTAX SEQUENCE OF PrtInterpreterEntry
6731 MAX-ACCESS not-accessible
6732 STATUS current
6733 DESCRIPTION
6734 "The interpreter table is a table representing the
6735 interpreters in the printer. An entry shall be placed in the
6736 interpreter table for each interpreter on the printer.
6737
6738 NOTE: The above description has been modified from RFC 1759
6739 for clarification."
6740 ::= { prtInterpreter 1 }
6741
6742prtInterpreterEntry OBJECT-TYPE
6743 SYNTAX PrtInterpreterEntry
6744 MAX-ACCESS not-accessible
6745 STATUS current
6746 DESCRIPTION
6747 "Entries may exist in the table for each device index with a
6748 device type of 'printer'. Each table entry provides a complete
6749 description of the interpreter, including version information,
6750 rendering resolutions, default character sets, output
6751 orientation, and communication capabilities.
6752
6753 NOTE: The above description has been modified from RFC 1759
6754 for clarification."
6755 INDEX { hrDeviceIndex, prtInterpreterIndex }
6756 ::= { prtInterpreterTable 1 }
6757
6758PrtInterpreterEntry ::= SEQUENCE {
6759 prtInterpreterIndex Integer32,
6760 prtInterpreterLangFamily PrtInterpreterLangFamilyTC,
6761 prtInterpreterLangLevel OCTET STRING,
6762 prtInterpreterLangVersion OCTET STRING,
6763 prtInterpreterDescription PrtLocalizedDescriptionStringTC,
6764 prtInterpreterVersion OCTET STRING,
6765 prtInterpreterDefaultOrientation PrtPrintOrientationTC,
6766 prtInterpreterFeedAddressability Integer32,
6767 prtInterpreterXFeedAddressability Integer32,
6768 prtInterpreterDefaultCharSetIn IANACharset,
6769 prtInterpreterDefaultCharSetOut IANACharset,
6770 prtInterpreterTwoWay PrtInterpreterTwoWayTC
6771 }
6772
6773prtInterpreterIndex OBJECT-TYPE
6774 -- NOTE: In RFC 1759, the range was not defined.
6775
6776
6777
6778Bergman, et al. Standards Track [Page 121]
6779\f
6780RFC 3805 Printer MIB v2 June 2004
6781
6782
6783 SYNTAX Integer32 (1..65535)
6784 MAX-ACCESS not-accessible
6785 STATUS current
6786 DESCRIPTION
6787 "A unique value for each PDL or control language for which
6788 there exists an interpreter or emulator in the printer. The
6789 value is used to identify this interpreter. Although these
6790 values may change due to a major reconfiguration of the device
6791 (e.g., the addition of new interpreters to the printer), values
6792 SHOULD remain stable across successive printer power cycles.
6793
6794 NOTE: The above description has been modified from RFC 1759
6795 for clarification."
6796 ::= { prtInterpreterEntry 1 }
6797
6798prtInterpreterLangFamily OBJECT-TYPE
6799 -- NOTE: In RFC 1759, the enumeration values were implicitly
6800 -- defined by this object.
6801 SYNTAX PrtInterpreterLangFamilyTC
6802 MAX-ACCESS read-only
6803 STATUS current
6804 DESCRIPTION
6805 "The family name of a Page Description Language (PDL) or
6806 control language which this interpreter in the printer can
6807 interpret or emulate.
6808
6809 NOTE: The above description has been modified from RFC 1759
6810 for clarification."
6811 ::= { prtInterpreterEntry 2 }
6812
6813prtInterpreterLangLevel OBJECT-TYPE
6814 SYNTAX OCTET STRING (SIZE(0..31))
6815 MAX-ACCESS read-only
6816 STATUS current
6817 DESCRIPTION
6818 "The level of the language which this interpreter is
6819 interpreting or emulating. This might contain a value like
6820 '5e'for an interpreter which is emulating level 5e of the PCL
6821 language. It might contain '2' for an interpreter which is
6822 emulating level 2 of the PostScript language. Similarly it
6823 might contain '2' for an interpreter which is emulating level 2
6824 of the HPGL language."
6825 ::= { prtInterpreterEntry 3 }
6826
6827prtInterpreterLangVersion OBJECT-TYPE
6828 SYNTAX OCTET STRING (SIZE(0..31))
6829 MAX-ACCESS read-only
6830 STATUS current
6831
6832
6833
6834Bergman, et al. Standards Track [Page 122]
6835\f
6836RFC 3805 Printer MIB v2 June 2004
6837
6838
6839 DESCRIPTION
6840 "The date code or version of the language which this
6841 interpreter is interpreting or emulating."
6842 ::= { prtInterpreterEntry 4 }
6843
6844prtInterpreterDescription OBJECT-TYPE
6845 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
6846 -- to a TC to better support localization of the object.
6847 SYNTAX PrtLocalizedDescriptionStringTC
6848 MAX-ACCESS read-only
6849 STATUS current
6850 DESCRIPTION
6851 "A string to identify this interpreter in the localization
6852 specified by prtGeneralCurrentLocalization as opposed to the
6853 language which is being interpreted. It is anticipated that
6854 this string will allow manufacturers to unambiguously identify
6855 their interpreters."
6856 ::= { prtInterpreterEntry 5 }
6857
6858prtInterpreterVersion OBJECT-TYPE
6859 SYNTAX OCTET STRING (SIZE(0..31))
6860 MAX-ACCESS read-only
6861 STATUS current
6862 DESCRIPTION
6863 "The date code, version number, or other product specific
6864 information tied to this interpreter. This value is associated
6865 with the interpreter, rather than with the version of the
6866 language which is being interpreted or emulated."
6867 ::= { prtInterpreterEntry 6 }
6868
6869prtInterpreterDefaultOrientation OBJECT-TYPE
6870 -- NOTE: In RFC 1759, the enumeration values were implicitly
6871 -- defined by this object.
6872 SYNTAX PrtPrintOrientationTC
6873 MAX-ACCESS read-write
6874 STATUS current
6875 DESCRIPTION
6876 "The current orientation default for this interpreter. This
6877 value may be overridden for a particular job (e.g., by a
6878 command in the input data stream)."
6879 ::= { prtInterpreterEntry 7 }
6880
6881prtInterpreterFeedAddressability OBJECT-TYPE
6882 -- NOTE: In RFC 1759, the range was not defined.
6883 SYNTAX Integer32 (-2..2147483647)
6884 MAX-ACCESS read-only
6885 STATUS current
6886 DESCRIPTION
6887
6888
6889
6890Bergman, et al. Standards Track [Page 123]
6891\f
6892RFC 3805 Printer MIB v2 June 2004
6893
6894
6895 "The maximum interpreter addressability in the feed
6896 direction in 10000 prtMarkerAddressabilityUnits (as specified
6897 by prtMarkerDefaultIndex) for this interpreter. The
6898 value (-1) means other and specifically indicates that the
6899 sub-unit places no restrictions on this parameter. The value
6900 (-2) means unknown.
6901
6902 NOTE: The above description has been modified from RFC 1759
6903 for clarification."
6904 ::= { prtInterpreterEntry 8 }
6905
6906prtInterpreterXFeedAddressability OBJECT-TYPE
6907 -- NOTE: In RFC 1759, the range was not defined.
6908 SYNTAX Integer32 (-2..2147483647)
6909 MAX-ACCESS read-only
6910 STATUS current
6911 DESCRIPTION
6912 "The maximum interpreter addressability in the cross feed
6913 direction in 10000 prtMarkerAddressabilityUnits (as specified
6914 by prtMarkerDefaultIndex) for this interpreter. The
6915 value (-1) means other and specifically indicates that the
6916 sub-unit places no restrictions on this parameter. The value
6917 (-2) means unknown.
6918
6919 NOTE: The above description has been modified from RFC 1759
6920 for clarification."
6921 ::= { prtInterpreterEntry 9 }
6922
6923prtInterpreterDefaultCharSetIn OBJECT-TYPE
6924 SYNTAX IANACharset
6925 MAX-ACCESS read-write
6926 STATUS current
6927 DESCRIPTION
6928 "The default coded character set for input octets encountered
6929 outside a context in which the Page Description Language
6930 established the interpretation of the octets. (Input octets are
6931 presented to the interpreter through a path defined in the
6932 channel group.)"
6933 ::= { prtInterpreterEntry 10 }
6934
6935prtInterpreterDefaultCharSetOut OBJECT-TYPE
6936 SYNTAX IANACharset
6937 MAX-ACCESS read-write
6938 STATUS current
6939 DESCRIPTION
6940 "The default character set for data coming from this
6941 interpreter through the printer's output channel (i.e. the
6942 'backchannel')."
6943
6944
6945
6946Bergman, et al. Standards Track [Page 124]
6947\f
6948RFC 3805 Printer MIB v2 June 2004
6949
6950
6951 ::= { prtInterpreterEntry 11 }
6952
6953prtInterpreterTwoWay OBJECT-TYPE
6954 -- NOTE: In RFC 1759, the enumeration values were implicitly
6955 -- defined by this object.
6956 SYNTAX PrtInterpreterTwoWayTC
6957 MAX-ACCESS read-only
6958 STATUS current
6959 DESCRIPTION
6960 "Indicates whether or not this interpreter returns information
6961 back to the host."
6962 ::= { prtInterpreterEntry 12 }
6963
6964-- The Console Group
6965--
6966-- Many printers have a console on the printer, the operator
6967-- console, that is used to display and modify the state of the
6968-- printer. The console can be as simple as a few indicators and
6969-- switches or as complicated as full screen displays and
6970-- keyboards. There can be at most one such console.
6971
6972-- The Display Buffer Table
6973
6974prtConsoleDisplayBuffer OBJECT IDENTIFIER ::= { printmib 16 }
6975
6976prtConsoleDisplayBufferTable OBJECT-TYPE
6977 SYNTAX SEQUENCE OF PrtConsoleDisplayBufferEntry
6978 MAX-ACCESS not-accessible
6979 STATUS current
6980 DESCRIPTION
6981 "Physical display buffer for printer console display or
6982 operator panel
6983
6984 NOTE: The above description has been modified from RFC 1759
6985 for clarification."
6986 ::= { prtConsoleDisplayBuffer 5 }
6987
6988prtConsoleDisplayBufferEntry OBJECT-TYPE
6989 SYNTAX PrtConsoleDisplayBufferEntry
6990 MAX-ACCESS not-accessible
6991 STATUS current
6992 DESCRIPTION
6993 "This table contains one entry for each physical line on
6994 the display. Lines cannot be added or deleted. Entries may
6995 exist in the table for each device index with a device type of
6996 'printer'.
6997
6998 NOTE: The above description has been modified from RFC 1759
6999
7000
7001
7002Bergman, et al. Standards Track [Page 125]
7003\f
7004RFC 3805 Printer MIB v2 June 2004
7005
7006
7007 for clarification."
7008 INDEX { hrDeviceIndex, prtConsoleDisplayBufferIndex }
7009 ::= { prtConsoleDisplayBufferTable 1 }
7010
7011PrtConsoleDisplayBufferEntry ::= SEQUENCE {
7012 prtConsoleDisplayBufferIndex Integer32,
7013 prtConsoleDisplayBufferText PrtConsoleDescriptionStringTC
7014 }
7015
7016prtConsoleDisplayBufferIndex OBJECT-TYPE
7017 SYNTAX Integer32 (1..65535)
7018 MAX-ACCESS not-accessible
7019 STATUS current
7020 DESCRIPTION
7021 "A unique value for each console line in the printer. The value
7022 is used to identify this console line. Although these values
7023 may change due to a major reconfiguration of the device (e.g.,
7024 the addition of new console lines to the printer). Values
7025 SHOULD remain stable across successive printer power cycles.
7026
7027 NOTE: The above description has been modified from RFC 1759
7028 for clarification."
7029 ::= { prtConsoleDisplayBufferEntry 1 }
7030
7031prtConsoleDisplayBufferText OBJECT-TYPE
7032 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
7033 -- to a TC to better support localization of the object.
7034 SYNTAX PrtConsoleDescriptionStringTC
7035 MAX-ACCESS read-write
7036 STATUS current
7037 DESCRIPTION
7038 "The content of a line in the logical display buffer of
7039 the operator's console of the printer. When a write
7040 operation occurs, normally a critical message, to one of
7041 the LineText strings, the agent should make that line
7042 displayable if a physical display is present. Writing a zero
7043 length string clears the line. It is an implementation-
7044 specific matter as to whether the agent allows a line to be
7045 overwritten before it has been cleared. Printer generated
7046 strings shall be in the localization specified by
7047 prtConsoleLocalization.Management Application generated strings
7048 should be localized by the Management Application."
7049 ::= { prtConsoleDisplayBufferEntry 2 }
7050
7051-- The Console Light Table
7052
7053prtConsoleLights OBJECT IDENTIFIER ::= { printmib 17 }
7054
7055
7056
7057
7058Bergman, et al. Standards Track [Page 126]
7059\f
7060RFC 3805 Printer MIB v2 June 2004
7061
7062
7063prtConsoleLightTable OBJECT-TYPE
7064 SYNTAX SEQUENCE OF PrtConsoleLightEntry
7065 MAX-ACCESS not-accessible
7066 STATUS current
7067 DESCRIPTION
7068 "The console light table provides a description and state
7069 information for each light present on the printer console.
7070
7071 NOTE: The above description has been modified from RFC 1759
7072 for clarification."
7073 ::= { prtConsoleLights 6 }
7074
7075prtConsoleLightEntry OBJECT-TYPE
7076 SYNTAX PrtConsoleLightEntry
7077 MAX-ACCESS not-accessible
7078 STATUS current
7079 DESCRIPTION
7080 "Entries may exist in the table for each device index with a
7081 device type of 'printer'.
7082
7083 NOTE: The above description has been modified from RFC 1759
7084 for clarification."
7085 INDEX { hrDeviceIndex, prtConsoleLightIndex }
7086 ::= { prtConsoleLightTable 1 }
7087
7088PrtConsoleLightEntry ::= SEQUENCE {
7089 prtConsoleLightIndex Integer32,
7090 prtConsoleOnTime Integer32,
7091 prtConsoleOffTime Integer32,
7092 prtConsoleColor PrtConsoleColorTC,
7093 prtConsoleDescription PrtConsoleDescriptionStringTC
7094 }
7095
7096prtConsoleLightIndex OBJECT-TYPE
7097 SYNTAX Integer32 (1..65535) -- Lower limit invalid in RFC 1759
7098 MAX-ACCESS not-accessible
7099 STATUS current
7100 DESCRIPTION
7101 "A unique value used by the printer to identify this light.
7102 Although these values may change due to a major
7103 reconfiguration of the device (e.g., the addition of new lights
7104 to the printer). Values SHOULD remain stable across successive
7105 printer power cycles.
7106
7107 NOTE: The above description has been modified from RFC 1759
7108 for clarification."
7109 ::= { prtConsoleLightEntry 1 }
7110
7111
7112
7113
7114Bergman, et al. Standards Track [Page 127]
7115\f
7116RFC 3805 Printer MIB v2 June 2004
7117
7118
7119prtConsoleOnTime OBJECT-TYPE
7120 -- NOTE: In RFC 1759, the range was not defined.
7121 SYNTAX Integer32 (0..2147483647)
7122 MAX-ACCESS read-write
7123 STATUS current
7124 DESCRIPTION
7125 "This object, in conjunction with prtConsoleOffTime, defines
7126 the current status of the light. If both prtConsoleOnTime and
7127 prtConsoleOffTime are non-zero, the lamp is blinking and the
7128 values presented define the on time and off time, respectively,
7129 in milliseconds. If prtConsoleOnTime is zero and
7130 prtConsoleOffTime is non-zero, the lamp is off. If
7131 prtConsoleOffTime is zero and prtConsoleOnTime is non-zero, the
7132 lamp is on. If both values are zero the lamp is off.
7133
7134 NOTE: The above description has been modified from RFC 1759
7135 for clarification."
7136 ::= { prtConsoleLightEntry 2 }
7137
7138prtConsoleOffTime OBJECT-TYPE
7139 -- NOTE: In RFC 1759, the range was not defined.
7140 SYNTAX Integer32 (0..2147483647)
7141 MAX-ACCESS read-write
7142 STATUS current
7143 DESCRIPTION
7144 "This object, in conjunction with prtConsoleOnTime, defines the
7145 current status of the light. If both prtConsoleOnTime and
7146 prtConsoleOffTime are non-zero, the lamp is blinking and the
7147 values presented define the on time and off time, respectively,
7148 in milliseconds. If prtConsoleOnTime is zero and
7149 prtConsoleOffTime is non-zero, the lamp is off. If
7150 prtConsoleOffTime is zero and prtConsoleOnTime is non-zero, the
7151 lamp is on. If both values are zero the lamp is off.
7152
7153 NOTE: The above description has been modified from RFC 1759
7154 for clarification."
7155 ::= { prtConsoleLightEntry 3 }
7156
7157prtConsoleColor OBJECT-TYPE
7158 -- NOTE: In RFC 1759, the enumeration values were implicitly
7159 -- defined by this object.
7160 SYNTAX PrtConsoleColorTC
7161 MAX-ACCESS read-only
7162 STATUS current
7163 DESCRIPTION
7164 "The color of this light."
7165 ::= { prtConsoleLightEntry 4 }
7166
7167
7168
7169
7170Bergman, et al. Standards Track [Page 128]
7171\f
7172RFC 3805 Printer MIB v2 June 2004
7173
7174
7175prtConsoleDescription OBJECT-TYPE
7176 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
7177 -- to a TC to better support localization of the object.
7178 SYNTAX PrtConsoleDescriptionStringTC
7179 MAX-ACCESS read-only
7180 STATUS current
7181 DESCRIPTION
7182 "The vendor description or label of this light in the
7183 localization specified by prtConsoleLocalization."
7184 ::= { prtConsoleLightEntry 5 }
7185
7186-- The Alerts Group
7187--
7188-- The table contains information on the severity, component,
7189-- detail location within the component, alert code and
7190-- description of each critical alert that is currently active
7191-- within the printer. See 2.2.13 for a more complete
7192-- description of the alerts table and its management.
7193--
7194-- Each parameter in the Trap PDU is a full OID which itself is
7195-- indexed by the host resources MIB "hrDeviceIndex" object. In
7196-- order for a management station to obtain the correct
7197-- "hrDeviceIndex" associated with a particular Trap PDU, the
7198-- "hrDeviceIndex" value can be extracted from the returned OID
7199-- value in the Trap PDU when the PDU is received by the
7200-- Management station.
7201
7202prtAlert OBJECT IDENTIFIER ::= { printmib 18 }
7203
7204prtAlertTable OBJECT-TYPE
7205 SYNTAX SEQUENCE OF PrtAlertEntry
7206 MAX-ACCESS not-accessible
7207 STATUS current
7208 DESCRIPTION
7209 "The prtAlertTable lists all the critical and non-critical
7210 alerts currently active in the printer. A critical alert is
7211 one that stops the printer from printing immediately and
7212 printing can not continue until the critical alert condition
7213 is eliminated. Non-critical alerts are those items that do
7214 not stop printing but may at some future time.
7215
7216 NOTE: The above description has been modified from RFC 1759
7217 for clarification."
7218 ::= { prtAlert 1 }
7219
7220prtAlertEntry OBJECT-TYPE
7221 SYNTAX PrtAlertEntry
7222 MAX-ACCESS not-accessible
7223
7224
7225
7226Bergman, et al. Standards Track [Page 129]
7227\f
7228RFC 3805 Printer MIB v2 June 2004
7229
7230
7231 STATUS current
7232 DESCRIPTION
7233 "Entries may exist in the table for each device
7234 index with a device type of 'printer'.
7235
7236 NOTE: The above description has been modified from RFC 1759
7237 for clarification."
7238 INDEX { hrDeviceIndex, prtAlertIndex }
7239 ::= { prtAlertTable 1 }
7240
7241PrtAlertEntry ::= SEQUENCE {
7242 prtAlertIndex Integer32,
7243 prtAlertSeverityLevel PrtAlertSeverityLevelTC,
7244 prtAlertTrainingLevel PrtAlertTrainingLevelTC,
7245 prtAlertGroup PrtAlertGroupTC,
7246 prtAlertGroupIndex Integer32,
7247 prtAlertLocation Integer32,
7248 prtAlertCode PrtAlertCodeTC,
7249 prtAlertDescription PrtLocalizedDescriptionStringTC,
7250 prtAlertTime TimeTicks
7251 }
7252
7253prtAlertIndex OBJECT-TYPE
7254 -- NOTE: In RFC 1759, the range was not defined. The MAX-ACCESS has
7255 -- been changed from not accessible to allow the object to be
7256 -- included (as originally in RFC 1759) in the trap bindings.
7257
7258 SYNTAX Integer32 (1..2147483647)
7259 MAX-ACCESS read-only
7260 STATUS current
7261 DESCRIPTION
7262 "The index value used to determine which alerts have been added
7263 or removed from the alert table. This is an incrementing
7264 integer initialized to 1 when the printer is reset. (i.e., The
7265 first event placed in the alert table after a reset of the
7266 printer shall have an index value of 1.) When the printer adds
7267 an alert to the table, that alert is assigned the next higher
7268 integer value from the last item entered into the table. If
7269 the index value reaches its maximum value, the next index value
7270 used must be 1.
7271
7272 NOTE: The management application will read the alert table when
7273 a trap or event notification occurs or at a periodic rate and
7274 then parse the table to determine if any new entries were added
7275 by comparing the last known index value with the current
7276 highest index value. The management application will then
7277 update its copy of the alert table. When the printer discovers
7278 that an alert is no longer active, the printer shall remove the
7279
7280
7281
7282Bergman, et al. Standards Track [Page 130]
7283\f
7284RFC 3805 Printer MIB v2 June 2004
7285
7286
7287 row for that alert from the table and shall reduce the number
7288 of rows in the table. The printer may add or delete any number
7289 of rows from the table at any time. The management station can
7290 detect when binary change alerts have been deleted by
7291 requesting an attribute of each alert, and noting alerts as
7292 deleted when that retrieval is not possible. The objects
7293 'prtAlertCriticalEvents'and 'prtAlertAllEvents' in the
7294 'prtGeneralTable' reduce the need for management applications
7295 to scan the 'prtAlertTable'.
7296
7297 NOTE: The above description has been modified from RFC 1759
7298 for clarification."
7299 ::= { prtAlertEntry 1 }
7300
7301prtAlertSeverityLevel OBJECT-TYPE
7302 -- NOTE: In RFC 1759, the enumeration values were implicitly
7303 -- defined by this object.
7304 SYNTAX PrtAlertSeverityLevelTC
7305 MAX-ACCESS read-only
7306 STATUS current
7307 DESCRIPTION
7308 "The level of severity of this alert table entry. The printer
7309 determines the severity level assigned to each entry into the
7310 table."
7311 ::= { prtAlertEntry 2 }
7312
7313prtAlertTrainingLevel OBJECT-TYPE
7314 -- NOTE: In RFC 1759, the enumeration values were implicitly
7315 -- defined by this object.
7316 SYNTAX PrtAlertTrainingLevelTC
7317 MAX-ACCESS read-only
7318 STATUS current
7319 DESCRIPTION
7320 "See TEXTUAL-CONVENTION PrtAlertTrainingLevelTC.
7321
7322 NOTE: The above description has been modified from RFC 1759
7323 for clarification."
7324 ::= { prtAlertEntry 3 }
7325
7326prtAlertGroup OBJECT-TYPE
7327 -- NOTE: In RFC 1759, the enumeration values were implicitly
7328 -- defined by this object.
7329 SYNTAX PrtAlertGroupTC
7330 MAX-ACCESS read-only
7331 STATUS current
7332 DESCRIPTION
7333 "The type of sub-unit within the printer model that this alert
7334 is related. Input, output, and markers are examples of printer
7335
7336
7337
7338Bergman, et al. Standards Track [Page 131]
7339\f
7340RFC 3805 Printer MIB v2 June 2004
7341
7342
7343 model groups, i.e., examples of types of sub-units. Wherever
7344 possible, these enumerations match the sub-identifier that
7345 identifies the relevant table in the printmib."
7346 ::= { prtAlertEntry 4 }
7347
7348prtAlertGroupIndex OBJECT-TYPE
7349 -- NOTE: In RFC 1759, the range was not defined.
7350 SYNTAX Integer32 (-1..2147483647)
7351 MAX-ACCESS read-only
7352 STATUS current
7353 DESCRIPTION
7354 "The low-order index of the row within the table identified
7355 by prtAlertGroup that represents the sub-unit of the printer
7356 that caused this alert, or -1 if not applicable. The
7357 combination of the prtAlertGroup and the prtAlertGroupIndex
7358 defines exactly which printer sub-unit caused the alert; for
7359 example, Input #3, Output#2, and Marker #1. Every object in
7360 this MIB is indexed with hrDeviceIndex and optionally, another
7361 index variable. If this other index variable is present in the
7362 table that generated the alert, it will be used as the value
7363 for this object. Otherwise, this value shall be -1.
7364
7365 NOTE: The above description has been modified from RFC 1759
7366 for clarification."
7367 ::= { prtAlertEntry 5 }
7368
7369prtAlertLocation OBJECT-TYPE
7370 -- NOTE: In RFC 1759, the range was not defined.
7371 SYNTAX Integer32 (-2..2147483647)
7372 MAX-ACCESS read-only
7373 STATUS current
7374 DESCRIPTION
7375 "The sub-unit location that is defined by the printer
7376 manufacturer to further refine the location of this alert
7377 within the designated sub-unit. The location is used in
7378 conjunction with the Group and GroupIndex values; for example,
7379 there is an alert in Input #2 at location number 7. The value
7380 (-2) indicates unknown.
7381
7382 NOTE: The above description has been modified from RFC 1759
7383 for clarification."
7384 ::= { prtAlertEntry 6 }
7385
7386prtAlertCode OBJECT-TYPE
7387 -- NOTE: In RFC 1759, the enumeration values were implicitly
7388 -- defined by this object.
7389 SYNTAX PrtAlertCodeTC
7390 MAX-ACCESS read-only
7391
7392
7393
7394Bergman, et al. Standards Track [Page 132]
7395\f
7396RFC 3805 Printer MIB v2 June 2004
7397
7398
7399 STATUS current
7400 DESCRIPTION
7401 "See associated TEXTUAL-CONVENTION PrtAlertCodeTC.
7402
7403 NOTE: The above description has been modified from RFC 1759
7404 for clarification."
7405 ::= { prtAlertEntry 7 }
7406
7407prtAlertDescription OBJECT-TYPE
7408 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed
7409 -- to a TC to better support localization of the object.
7410 SYNTAX PrtLocalizedDescriptionStringTC
7411 MAX-ACCESS read-only
7412 STATUS current
7413 DESCRIPTION
7414 "A description of this alert entry in the localization
7415 specified by prtGeneralCurrentLocalization. The description is
7416 provided by the printer to further elaborate on the enumerated
7417 alert or provide information in the case where the code is
7418 classified as 'other' or 'unknown'. The printer is required to
7419 return a description string but the string may be a null
7420 string."
7421 ::= { prtAlertEntry 8 }
7422
7423prtAlertTime OBJECT-TYPE
7424 SYNTAX TimeTicks
7425 MAX-ACCESS read-only
7426 STATUS current
7427 DESCRIPTION
7428 "The value of sysUpTime at the time that this alert was
7429 generated."
7430 ::= { prtAlertEntry 9 }
7431
7432printerV1Alert OBJECT-IDENTITY
7433 STATUS current
7434 DESCRIPTION
7435 "The value of the enterprise-specific OID in an SNMPv1 trap
7436 sent signaling a critical event in the prtAlertTable."
7437 ::= { prtAlert 2 }
7438
7439printerV2AlertPrefix OBJECT IDENTIFIER ::= { printerV1Alert 0 }
7440
7441printerV2Alert NOTIFICATION-TYPE
7442 OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup,
7443 prtAlertGroupIndex, prtAlertLocation, prtAlertCode }
7444 STATUS current
7445 DESCRIPTION
7446 "This trap is sent whenever a critical event is added to the
7447
7448
7449
7450Bergman, et al. Standards Track [Page 133]
7451\f
7452RFC 3805 Printer MIB v2 June 2004
7453
7454
7455 prtAlertTable.
7456
7457 NOTE: The prtAlertIndex object was redundantly included in the
7458 bindings of the 'printerV2Alert' notification in RFC 1759, even
7459 though the value exists in the instance qualifier of all the
7460 other bindings. This object has been retained to provide
7461 compatiblity with existing RFC 1759 implementaions."
7462 ::= { printerV2AlertPrefix 1 }
7463
7464-- Note that the SNMPv2 to SNMPv1 translation rules dictate that
7465-- the preceding structure will result in SNMPv1 traps of the
7466-- following form:
7467--
7468-- printerAlert TRAP-TYPE
7469-- ENTERPRISE printerV1Alert
7470-- VARIABLES { prtAlertIndex, prtAlertSeverityLevel,
7471-- prtAlertGroup, prtAlertGroupIndex,
7472-- prtAlertLocation, prtAlertCode }
7473-- DESCRIPTION
7474-- "This trap is sent whenever a critical event is added
7475-- to the prtAlertTable."
7476-- ::= 1
7477
7478-- Conformance Information
7479
7480prtMIBConformance OBJECT IDENTIFIER ::= { printmib 2 }
7481
7482-- compliance statements
7483
7484prtMIBCompliance MODULE-COMPLIANCE
7485
7486 STATUS current
7487 DESCRIPTION
7488 "The compliance statement for agents that implement the
7489 printer MIB as defined by RFC 1759."
7490 MODULE -- this module
7491 MANDATORY-GROUPS { prtGeneralGroup, prtInputGroup,
7492 prtOutputGroup,
7493 prtMarkerGroup, prtMediaPathGroup,
7494 prtChannelGroup, prtInterpreterGroup,
7495 prtConsoleGroup, prtAlertTableGroup }
7496 OBJECT prtGeneralReset
7497 SYNTAX INTEGER {
7498 notResetting(3),
7499 resetToNVRAM(5)
7500 }
7501 DESCRIPTION
7502 "It is conformant to implement just these two states in this
7503
7504
7505
7506Bergman, et al. Standards Track [Page 134]
7507\f
7508RFC 3805 Printer MIB v2 June 2004
7509
7510
7511 object. Any additional states are optional."
7512
7513 OBJECT prtConsoleOnTime
7514 MIN-ACCESS read-only
7515 DESCRIPTION
7516 "It is conformant to implement this object as read-only"
7517
7518 OBJECT prtConsoleOffTime
7519 MIN-ACCESS read-only
7520 DESCRIPTION
7521 "It is conformant to implement this object as read-only"
7522 ::= { prtMIBConformance 1 }
7523
7524prtMIB2Compliance MODULE-COMPLIANCE
7525 STATUS current
7526 DESCRIPTION
7527 "The compliance statement for agents that implement the
7528 printer MIB V2."
7529 -- The changes from RFC 1759 fall into 2 categories:
7530 -- 1. New objects plus existing objects with a MIN-ACCESS of
7531 -- read-only are included. Existing objects have been added
7532 -- to this category due to feedback from implementers and
7533 -- interoperability testing. This allows products to be
7534 -- be designed with a higher degree of SNMP security.
7535 -- 2. New object groups have been added to include all new
7536 -- objects in this MIB. All new object groups are optional.
7537 -- Any MIB that is compliant with RFC 1759 will also be
7538 -- compliant with this version of the MIB.
7539 MODULE -- this module
7540 MANDATORY-GROUPS { prtGeneralGroup, prtInputGroup,
7541 prtOutputGroup,
7542 prtMarkerGroup, prtMediaPathGroup,
7543 prtChannelGroup, prtInterpreterGroup,
7544 prtConsoleGroup, prtAlertTableGroup }
7545 OBJECT prtGeneralReset
7546 SYNTAX INTEGER {
7547 notResetting(3),
7548 resetToNVRAM(5)
7549 }
7550 DESCRIPTION
7551 "It is conformant to implement just these two states in this
7552 object. Any additional states are optional."
7553
7554 OBJECT prtGeneralCurrentLocalization
7555 MIN-ACCESS read-only
7556 DESCRIPTION
7557 "It is conformant to implement this object as read-only"
7558
7559
7560
7561
7562Bergman, et al. Standards Track [Page 135]
7563\f
7564RFC 3805 Printer MIB v2 June 2004
7565
7566
7567 OBJECT prtGeneralCurrentOperator
7568 MIN-ACCESS read-only
7569 DESCRIPTION
7570 "It is conformant to implement this object as read-only"
7571
7572 OBJECT prtGeneralServicePerson
7573 MIN-ACCESS read-only
7574 DESCRIPTION
7575 "It is conformant to implement this object as read-only"
7576
7577 OBJECT prtGeneralPrinterName
7578 MIN-ACCESS read-only
7579 DESCRIPTION
7580 "It is conformant to implement this object as read-only"
7581
7582 OBJECT prtGeneralSerialNumber
7583 MIN-ACCESS read-only
7584 DESCRIPTION
7585 "It is conformant to implement this object as read-only"
7586
7587 OBJECT prtInputDefaultIndex
7588 MIN-ACCESS read-only
7589 DESCRIPTION
7590 "It is conformant to implement this object as read-only"
7591
7592 OBJECT prtInputMediaDimFeedDirDeclared
7593 MIN-ACCESS read-only
7594 DESCRIPTION
7595 "It is conformant to implement this object as read-only"
7596
7597 OBJECT prtInputMaxCapacity
7598 MIN-ACCESS read-only
7599 DESCRIPTION
7600 "It is conformant to implement this object as read-only"
7601
7602 OBJECT prtInputCurrentLevel
7603 MIN-ACCESS read-only
7604 DESCRIPTION
7605 "It is conformant to implement this object as read-only"
7606
7607 OBJECT prtInputMediaName
7608 MIN-ACCESS read-only
7609 DESCRIPTION
7610 "It is conformant to implement this object as read-only"
7611
7612 OBJECT prtInputName
7613 MIN-ACCESS read-only
7614 DESCRIPTION
7615
7616
7617
7618Bergman, et al. Standards Track [Page 136]
7619\f
7620RFC 3805 Printer MIB v2 June 2004
7621
7622
7623 "It is conformant to implement this object as read-only"
7624
7625 OBJECT prtInputSecurity
7626 MIN-ACCESS read-only
7627 DESCRIPTION
7628 "It is conformant to implement this object as read-only"
7629
7630 OBJECT prtInputMediaWeight
7631 MIN-ACCESS read-only
7632 DESCRIPTION
7633 "It is conformant to implement this object as read-only"
7634
7635 OBJECT prtInputMediaType
7636 MIN-ACCESS read-only
7637 DESCRIPTION
7638 "It is conformant to implement this object as read-only"
7639
7640 OBJECT prtInputMediaColor
7641 MIN-ACCESS read-only
7642 DESCRIPTION
7643 "It is conformant to implement this object as read-only"
7644
7645 OBJECT prtInputMediaFormParts
7646 MIN-ACCESS read-only
7647 DESCRIPTION
7648 "It is conformant to implement this object as read-only"
7649
7650 OBJECT prtOutputDefaultIndex
7651 MIN-ACCESS read-only
7652 DESCRIPTION
7653 "It is conformant to implement this object as read-only"
7654
7655 OBJECT prtOutputMaxCapacity
7656 MIN-ACCESS read-only
7657 DESCRIPTION
7658 "It is conformant to implement this object as read-only"
7659
7660 OBJECT prtOutputRemainingCapacity
7661 MIN-ACCESS read-only
7662 DESCRIPTION
7663 "It is conformant to implement this object as read-only"
7664
7665 OBJECT prtOutputName
7666 MIN-ACCESS read-only
7667 DESCRIPTION
7668 "It is conformant to implement this object as read-only"
7669
7670 OBJECT prtOutputSecurity
7671
7672
7673
7674Bergman, et al. Standards Track [Page 137]
7675\f
7676RFC 3805 Printer MIB v2 June 2004
7677
7678
7679 MIN-ACCESS read-only
7680 DESCRIPTION
7681 "It is conformant to implement this object as read-only"
7682
7683 OBJECT prtOutputMaxDimFeedDir
7684 MIN-ACCESS read-only
7685 DESCRIPTION
7686 "It is conformant to implement this object as read-only"
7687
7688 OBJECT prtOutputMaxDimXFeedDir
7689 MIN-ACCESS read-only
7690 DESCRIPTION
7691 "It is conformant to implement this object as read-only"
7692
7693 OBJECT prtOutputMinDimFeedDir
7694 MIN-ACCESS read-only
7695 DESCRIPTION
7696 "It is conformant to implement this object as read-only"
7697
7698 OBJECT prtOutputMinDimXFeedDir
7699 MIN-ACCESS read-only
7700 DESCRIPTION
7701 "It is conformant to implement this object as read-only"
7702
7703 OBJECT prtOutputStackingOrder
7704 MIN-ACCESS read-only
7705 DESCRIPTION
7706 "It is conformant to implement this object as read-only"
7707
7708 OBJECT prtOutputPageDeliveryOrientation
7709 MIN-ACCESS read-only
7710 DESCRIPTION
7711 "It is conformant to implement this object as read-only"
7712
7713 OBJECT prtOutputBursting
7714 MIN-ACCESS read-only
7715 DESCRIPTION
7716 "It is conformant to implement this object as read-only"
7717
7718 OBJECT prtOutputDecollating
7719 MIN-ACCESS read-only
7720 DESCRIPTION
7721 "It is conformant to implement this object as read-only"
7722
7723 OBJECT prtOutputPageCollated
7724 MIN-ACCESS read-only
7725 DESCRIPTION
7726 "It is conformant to implement this object as read-only"
7727
7728
7729
7730Bergman, et al. Standards Track [Page 138]
7731\f
7732RFC 3805 Printer MIB v2 June 2004
7733
7734
7735 OBJECT prtOutputOffsetStacking
7736 MIN-ACCESS read-only
7737 DESCRIPTION
7738 "It is conformant to implement this object as read-only"
7739
7740 OBJECT prtMarkerDefaultIndex
7741 MIN-ACCESS read-only
7742 DESCRIPTION
7743 "It is conformant to implement this object as read-only"
7744
7745 OBJECT prtMarkerSuppliesMaxCapacity
7746 MIN-ACCESS read-only
7747 DESCRIPTION
7748 "It is conformant to implement this object as read-only"
7749
7750 OBJECT prtMarkerSuppliesLevel
7751 MIN-ACCESS read-only
7752 DESCRIPTION
7753 "It is conformant to implement this object as read-only"
7754
7755 OBJECT prtMediaPathDefaultIndex
7756 MIN-ACCESS read-only
7757 DESCRIPTION
7758 "It is conformant to implement this object as read-only"
7759
7760 OBJECT prtChannelCurrentJobCntlLangIndex
7761 MIN-ACCESS read-only
7762 DESCRIPTION
7763 "It is conformant to implement this object as read-only"
7764
7765 OBJECT prtChannelDefaultPageDescLangIndex
7766 MIN-ACCESS read-only
7767 DESCRIPTION
7768 "It is conformant to implement this object as read-only"
7769
7770 OBJECT prtChannelState
7771 MIN-ACCESS read-only
7772 DESCRIPTION
7773 "It is conformant to implement this object as read-only"
7774
7775 OBJECT prtChannelIfIndex
7776 MIN-ACCESS read-only
7777 DESCRIPTION
7778 "It is conformant to implement this object as read-only"
7779
7780 OBJECT prtInterpreterDefaultOrientation
7781 MIN-ACCESS read-only
7782 DESCRIPTION
7783
7784
7785
7786Bergman, et al. Standards Track [Page 139]
7787\f
7788RFC 3805 Printer MIB v2 June 2004
7789
7790
7791 "It is conformant to implement this object as read-only"
7792
7793 OBJECT prtInterpreterDefaultCharSetIn
7794 MIN-ACCESS read-only
7795 DESCRIPTION
7796 "It is conformant to implement this object as read-only"
7797
7798 OBJECT prtInterpreterDefaultCharSetOut
7799 MIN-ACCESS read-only
7800 DESCRIPTION
7801 "It is conformant to implement this object as read-only"
7802
7803 OBJECT prtConsoleLocalization
7804 MIN-ACCESS read-only
7805 DESCRIPTION
7806 "It is conformant to implement this object as read-only"
7807
7808 OBJECT prtConsoleDisable
7809 MIN-ACCESS read-only
7810 DESCRIPTION
7811 "It is conformant to implement this object as read-only"
7812
7813 OBJECT prtConsoleDisplayBufferText
7814 MIN-ACCESS read-only
7815 DESCRIPTION
7816 "It is conformant to implement this object as read-only"
7817
7818 OBJECT prtConsoleOnTime
7819 MIN-ACCESS read-only
7820 DESCRIPTION
7821 "It is conformant to implement this object as read-only"
7822
7823 OBJECT prtConsoleOffTime
7824 MIN-ACCESS read-only
7825 DESCRIPTION
7826 "It is conformant to implement this object as read-only"
7827
7828 OBJECT prtAlertIndex
7829 MIN-ACCESS accessible-for-notify
7830 DESCRIPTION
7831 "It is conformant to implement this object as
7832 accessible-for-notify "
7833
7834 GROUP prtResponsiblePartyGroup
7835 DESCRIPTION
7836 "This group is unconditionally optional."
7837
7838 GROUP prtExtendedInputGroup
7839
7840
7841
7842Bergman, et al. Standards Track [Page 140]
7843\f
7844RFC 3805 Printer MIB v2 June 2004
7845
7846
7847 DESCRIPTION
7848 "This group is unconditionally optional."
7849
7850 GROUP prtInputMediaGroup
7851 DESCRIPTION
7852 "This group is unconditionally optional."
7853
7854 GROUP prtExtendedOutputGroup
7855 DESCRIPTION
7856 "This group is unconditionally optional."
7857
7858 GROUP prtOutputDimensionsGroup
7859 DESCRIPTION
7860 "This group is unconditionally optional."
7861
7862 GROUP prtOutputFeaturesGroup
7863 DESCRIPTION
7864 "This group is unconditionally optional."
7865
7866 GROUP prtMarkerSuppliesGroup
7867 DESCRIPTION
7868 "This group is unconditionally optional."
7869
7870 GROUP prtMarkerColorantGroup
7871 DESCRIPTION
7872 "This group is unconditionally optional."
7873
7874 GROUP prtAlertTimeGroup
7875 DESCRIPTION
7876 "This group is unconditionally optional."
7877
7878 -- the prtResponsiblePartyGroup, prtExtendedInputGroup,
7879 -- prtInputMediaGroup, prtExtendedOutputGroup,
7880 -- prtOutputDimensionsGroup, prtOutputFeaturesGroup,
7881 -- prtMarkerSuppliesGroup, prtMarkerColorantGroup, and the
7882 -- prtAlertTimeGroup are completely optional. However, it is
7883 -- strongly RECOMMENDED that the prtAlertTimeGroup be implemented.
7884
7885 -- New to version 2 of this printer MIB:
7886 OBJECT prtAuxiliarySheetStartupPage
7887 MIN-ACCESS read-only
7888 DESCRIPTION
7889 "It is conformant to implement this object as read-only"
7890
7891 OBJECT prtAuxiliarySheetBannerPage
7892 MIN-ACCESS read-only
7893 DESCRIPTION
7894 "It is conformant to implement this object as read-only"
7895
7896
7897
7898Bergman, et al. Standards Track [Page 141]
7899\f
7900RFC 3805 Printer MIB v2 June 2004
7901
7902
7903 OBJECT prtInputMediaLoadTimeout
7904 MIN-ACCESS read-only
7905 DESCRIPTION
7906 "It is conformant to implement this object as read-only"
7907
7908 OBJECT prtInputNextIndex
7909 MIN-ACCESS read-only
7910 DESCRIPTION
7911 "It is conformant to implement this object as read-only"
7912
7913 GROUP prtAuxiliarySheetGroup
7914 DESCRIPTION
7915 "This group is unconditionally optional."
7916
7917 GROUP prtInputSwitchingGroup
7918 DESCRIPTION
7919 "This group is unconditionally optional."
7920
7921 GROUP prtGeneralV2Group
7922 DESCRIPTION
7923 "This group is unconditionally optional."
7924
7925 GROUP prtAlertTableV2Group
7926 DESCRIPTION
7927 "This group is unconditionally optional."
7928
7929 GROUP prtChannelV2Group
7930 DESCRIPTION
7931 "This group is unconditionally optional."
7932
7933 GROUP prtAlertTrapGroup
7934 DESCRIPTION
7935 "This group is unconditionally optional."
7936 ::= { prtMIBConformance 3 }
7937
7938prtMIBGroups OBJECT IDENTIFIER ::= { prtMIBConformance 2 }
7939-- These groups are from RFC 1759 and are applicable to Printer MIB V2
7940
7941prtGeneralGroup OBJECT-GROUP
7942 OBJECTS { prtGeneralConfigChanges,
7943 prtGeneralCurrentLocalization,
7944 prtGeneralReset, prtCoverDescription,
7945 prtCoverStatus,
7946 prtLocalizationLanguage, prtLocalizationCountry,
7947 prtLocalizationCharacterSet, prtStorageRefIndex,
7948 prtDeviceRefIndex }
7949 STATUS current
7950 DESCRIPTION
7951
7952
7953
7954Bergman, et al. Standards Track [Page 142]
7955\f
7956RFC 3805 Printer MIB v2 June 2004
7957
7958
7959 "The general printer group."
7960 ::= { prtMIBGroups 1 }
7961
7962prtResponsiblePartyGroup OBJECT-GROUP
7963 OBJECTS { prtGeneralCurrentOperator, prtGeneralServicePerson }
7964 STATUS current
7965 DESCRIPTION
7966 "The responsible party group contains contact information for
7967 humans responsible for the printer."
7968 ::= { prtMIBGroups 2 }
7969
7970prtInputGroup OBJECT-GROUP
7971 OBJECTS { prtInputDefaultIndex, prtInputType, prtInputDimUnit,
7972 prtInputMediaDimFeedDirDeclared,
7973 prtInputMediaDimXFeedDirDeclared,
7974 prtInputMediaDimFeedDirChosen,
7975 prtInputMediaDimXFeedDirChosen, prtInputCapacityUnit,
7976 prtInputMaxCapacity, prtInputCurrentLevel, prtInputStatus,
7977 prtInputMediaName }
7978 STATUS current
7979 DESCRIPTION
7980 "The input group."
7981 ::= { prtMIBGroups 3 }
7982
7983prtExtendedInputGroup OBJECT-GROUP
7984 OBJECTS { prtInputName, prtInputVendorName, prtInputModel,
7985 prtInputVersion, prtInputSerialNumber,
7986 prtInputDescription, prtInputSecurity }
7987 STATUS current
7988 DESCRIPTION
7989 "The extended input group."
7990 ::= { prtMIBGroups 4 }
7991
7992prtInputMediaGroup OBJECT-GROUP
7993 OBJECTS { prtInputMediaWeight, prtInputMediaType,
7994 prtInputMediaColor, prtInputMediaFormParts }
7995 STATUS current
7996 DESCRIPTION
7997 "The input media group."
7998 ::= { prtMIBGroups 5 }
7999
8000prtOutputGroup OBJECT-GROUP
8001 OBJECTS { prtOutputDefaultIndex, prtOutputType,
8002 prtOutputCapacityUnit, prtOutputMaxCapacity,
8003 prtOutputRemainingCapacity, prtOutputStatus }
8004 STATUS current
8005 DESCRIPTION
8006 "The output group."
8007
8008
8009
8010Bergman, et al. Standards Track [Page 143]
8011\f
8012RFC 3805 Printer MIB v2 June 2004
8013
8014
8015 ::= { prtMIBGroups 6 }
8016
8017prtExtendedOutputGroup OBJECT-GROUP
8018 OBJECTS { prtOutputName, prtOutputVendorName, prtOutputModel,
8019 prtOutputVersion, prtOutputSerialNumber,
8020 prtOutputDescription, prtOutputSecurity }
8021 STATUS current
8022 DESCRIPTION
8023 "The extended output group."
8024 ::= { prtMIBGroups 7 }
8025
8026prtOutputDimensionsGroup OBJECT-GROUP
8027 OBJECTS { prtOutputDimUnit, prtOutputMaxDimFeedDir,
8028 prtOutputMaxDimXFeedDir, prtOutputMinDimFeedDir,
8029 prtOutputMinDimXFeedDir }
8030 STATUS current
8031 DESCRIPTION
8032 "The output dimensions group"
8033 ::= { prtMIBGroups 8 }
8034
8035prtOutputFeaturesGroup OBJECT-GROUP
8036 OBJECTS { prtOutputStackingOrder,
8037 prtOutputPageDeliveryOrientation, prtOutputBursting,
8038 prtOutputDecollating, prtOutputPageCollated,
8039 prtOutputOffsetStacking }
8040 STATUS current
8041 DESCRIPTION
8042 "The output features group."
8043 ::= { prtMIBGroups 9 }
8044
8045prtMarkerGroup OBJECT-GROUP
8046 OBJECTS { prtMarkerDefaultIndex, prtMarkerMarkTech,
8047 prtMarkerCounterUnit, prtMarkerLifeCount,
8048 prtMarkerPowerOnCount, prtMarkerProcessColorants,
8049 prtMarkerSpotColorants, prtMarkerAddressabilityUnit,
8050 prtMarkerAddressabilityFeedDir,
8051 prtMarkerAddressabilityXFeedDir, prtMarkerNorthMargin,
8052 prtMarkerSouthMargin, prtMarkerWestMargin,
8053 prtMarkerEastMargin, prtMarkerStatus }
8054 STATUS current
8055 DESCRIPTION
8056 "The marker group."
8057 ::= { prtMIBGroups 10 }
8058
8059prtMarkerSuppliesGroup OBJECT-GROUP
8060 OBJECTS { prtMarkerSuppliesMarkerIndex,
8061 prtMarkerSuppliesColorantIndex, prtMarkerSuppliesClass,
8062 prtMarkerSuppliesType, prtMarkerSuppliesDescription,
8063
8064
8065
8066Bergman, et al. Standards Track [Page 144]
8067\f
8068RFC 3805 Printer MIB v2 June 2004
8069
8070
8071 prtMarkerSuppliesSupplyUnit,
8072 prtMarkerSuppliesMaxCapacity, prtMarkerSuppliesLevel }
8073 STATUS current
8074 DESCRIPTION
8075 "The marker supplies group."
8076 ::= { prtMIBGroups 11 }
8077
8078prtMarkerColorantGroup OBJECT-GROUP
8079 OBJECTS { prtMarkerColorantMarkerIndex, prtMarkerColorantRole,
8080 prtMarkerColorantValue, prtMarkerColorantTonality }
8081 STATUS current
8082 DESCRIPTION
8083 "The marker colorant group."
8084 ::= { prtMIBGroups 12 }
8085
8086prtMediaPathGroup OBJECT-GROUP
8087 OBJECTS { prtMediaPathDefaultIndex, prtMediaPathMaxSpeedPrintUnit,
8088 prtMediaPathMediaSizeUnit, prtMediaPathMaxSpeed,
8089 prtMediaPathMaxMediaFeedDir,
8090 prtMediaPathMaxMediaXFeedDir,
8091 prtMediaPathMinMediaFeedDir,
8092 prtMediaPathMinMediaXFeedDir, prtMediaPathType,
8093 prtMediaPathDescription, prtMediaPathStatus}
8094 STATUS current
8095 DESCRIPTION
8096 "The media path group."
8097 ::= { prtMIBGroups 13 }
8098
8099prtChannelGroup OBJECT-GROUP
8100 OBJECTS { prtChannelType, prtChannelProtocolVersion,
8101 prtChannelCurrentJobCntlLangIndex,
8102 prtChannelDefaultPageDescLangIndex, prtChannelState,
8103 prtChannelIfIndex, prtChannelStatus
8104 }
8105 STATUS current
8106 DESCRIPTION
8107 "The channel group."
8108 ::= { prtMIBGroups 14 }
8109
8110prtInterpreterGroup OBJECT-GROUP
8111 OBJECTS { prtInterpreterLangFamily, prtInterpreterLangLevel,
8112 prtInterpreterLangVersion, prtInterpreterDescription,
8113 prtInterpreterVersion, prtInterpreterDefaultOrientation,
8114 prtInterpreterFeedAddressability,
8115 prtInterpreterXFeedAddressability,
8116 prtInterpreterDefaultCharSetIn,
8117 prtInterpreterDefaultCharSetOut, prtInterpreterTwoWay }
8118 STATUS current
8119
8120
8121
8122Bergman, et al. Standards Track [Page 145]
8123\f
8124RFC 3805 Printer MIB v2 June 2004
8125
8126
8127 DESCRIPTION
8128 "The interpreter group."
8129 ::= { prtMIBGroups 15 }
8130
8131prtConsoleGroup OBJECT-GROUP
8132 OBJECTS { prtConsoleLocalization, prtConsoleNumberOfDisplayLines,
8133 prtConsoleNumberOfDisplayChars, prtConsoleDisable,
8134 prtConsoleDisplayBufferText, prtConsoleOnTime,
8135 prtConsoleOffTime, prtConsoleColor,
8136 prtConsoleDescription }
8137 STATUS current
8138 DESCRIPTION
8139 "The console group."
8140 ::= { prtMIBGroups 16 }
8141
8142prtAlertTableGroup OBJECT-GROUP
8143 OBJECTS { prtAlertSeverityLevel, prtAlertTrainingLevel,
8144 prtAlertGroup, prtAlertGroupIndex, prtAlertLocation,
8145 prtAlertCode, prtAlertDescription }
8146 STATUS current
8147 DESCRIPTION
8148 "The alert table group."
8149 ::= { prtMIBGroups 17 }
8150
8151prtAlertTimeGroup OBJECT-GROUP
8152 OBJECTS { prtAlertTime }
8153 STATUS current
8154 DESCRIPTION
8155 "The alert time group. Implementation of prtAlertTime is
8156 strongly RECOMMENDED."
8157 ::= { prtMIBGroups 18 }
8158
8159prtMIB2Groups OBJECT IDENTIFIER ::= { prtMIBConformance 4 }
8160-- These groups are unique to Printer MIB V2
8161
8162prtAuxiliarySheetGroup OBJECT-GROUP
8163 OBJECTS { prtAuxiliarySheetStartupPage,
8164 prtAuxiliarySheetBannerPage }
8165 STATUS current
8166 DESCRIPTION
8167 "The auxiliary sheet group."
8168 ::= { prtMIBGroups 19 }
8169
8170prtInputSwitchingGroup OBJECT-GROUP
8171 OBJECTS { prtInputMediaLoadTimeout, prtInputNextIndex }
8172 STATUS current
8173 DESCRIPTION
8174 "The input switching group."
8175
8176
8177
8178Bergman, et al. Standards Track [Page 146]
8179\f
8180RFC 3805 Printer MIB v2 June 2004
8181
8182
8183 ::= { prtMIBGroups 20 }
8184
8185prtGeneralV2Group OBJECT-GROUP
8186 OBJECTS { prtGeneralPrinterName, prtGeneralSerialNumber }
8187 STATUS current
8188 DESCRIPTION
8189 "The general printer group with new v2 objects."
8190 ::= { prtMIBGroups 21 }
8191
8192prtAlertTableV2Group OBJECT-GROUP
8193 OBJECTS { prtAlertIndex, prtAlertCriticalEvents, prtAlertAllEvents }
8194 STATUS current
8195 DESCRIPTION
8196 "The alert table group with new v2 objects and prtAlertIndex
8197 changed to MAX-ACCESS of 'read-only' for inclusion in the trap
8198 bindings (as originally defined in RFC 1759)."
8199
8200 ::= { prtMIBGroups 22 }
8201
8202prtChannelV2Group OBJECT-GROUP
8203 OBJECTS { prtChannelInformation }
8204 STATUS current
8205 DESCRIPTION
8206 "The channel group with a new v2 object."
8207 ::= { prtMIBGroups 23 }
8208
8209prtAlertTrapGroup NOTIFICATION-GROUP
8210 NOTIFICATIONS { printerV2Alert }
8211 STATUS current
8212 DESCRIPTION
8213 "The alert trap group."
8214 ::= { prtMIBGroups 24 }
8215
8216END
8217
82187. IANA Considerations
8219
8220 The initial version the IANA Printer MIB defined in section 5 of this
8221 document is to be archived by IANA and subsequently maintained
8222 according to the Process specified in section 2.4.1 of this document.
8223 The most current and authoritative version of the IANA Printer MIB is
8224 available at:
8225
8226 http://www.iana.org/assignments/ianaprinter-mib
8227
82288. Internationalization Considerations
8229
8230 See section 2.2.1.1, 'International Considerations'.
8231
8232
8233
8234Bergman, et al. Standards Track [Page 147]
8235\f
8236RFC 3805 Printer MIB v2 June 2004
8237
8238
82399. Security Considerations
8240
8241 There are a number of management objects defined in this MIB module
8242 with a MAX-ACCESS clause of read-write and/or read-create. Such
8243 objects may be considered sensitive or vulnerable in some network
8244 environments. The support for SET operations in a non-secure
8245 environment without proper protection can have a negative effect on
8246 network operations. These are the tables and objects and their
8247 sensitivity/vulnerability:
8248
8249 prtGeneralTable:
8250 prtGeneralCurrentLocalization - Possible data loss
8251 prtGeneralReset - Possible data loss
8252 prtGeneralCurrentOperator - Possible severe inconvenience
8253 prtGeneralServicePerson - Possible severe inconvenience
8254 prtInputDefaultIndex - Possible data loss
8255 prtOutputDefaultIndex - Possible minor inconvenience
8256 prtMarkerDefaultIndex - Possible minor inconvenience
8257 prtMediaPathDefaultIndex - Possible minor inconvenience
8258 prtConsoleLocalization - Possible severe inconvenience
8259 prtConsoleDisable - Possible severe inconvenience
8260 prtAuxiliarySheetStartupPage - Possible minor inconvenience
8261 prtAuxiliarySheetBannerPage - Possible minor inconvenience
8262 prtGeneralPrinterName - Possible severe inconvenience
8263 prtGeneralSerialNumber - Possible severe inconvenience
8264 prtInputTable:
8265 prtInputMediaDimFeedDirDeclared - Possible data loss
8266 prtInputMediaDimXFeedDirDeclared - Possible data loss
8267 prtInputMaxCapacity - Possible minor inconvenience
8268 prtInputCurrentLevel - Possible minor inconvenience
8269 prtInputMediaName - Possible minor inconvenience
8270 prtInputName - Possible minor inconvenience
8271 prtInputSecurity - Possible minor inconvenience
8272 prtInputMediaWeight - Possible minor inconvenience
8273 prtInputMediaType - Possible minor inconvenience
8274 prtInputMediaColor - Possible minor inconvenience
8275 prtInputMediaFormParts - Possible minor inconvenience
8276 prtInputMediaLoadTimeout - Possible minor inconvenience
8277 prtInputNextIndex - Possible minor inconvenience
8278 prtOutputTable
8279 prtOutputMaxCapacity - Possible minor inconvenience
8280 prtOutputRemainingCapacity - Possible minor inconvenience
8281 prtOutputName - Possible minor inconvenience
8282 prtOutputSecurity - Possible minor inconvenience
8283 prtOutputMaxDimFeedDir - Possible minor inconvenience
8284 prtOutputMaxDimXFeedDir - Possible minor inconvenience
8285 prtOutputMinDimFeedDir - Possible minor inconvenience
8286 prtOutputMinDimXFeedDir - Possible minor inconvenience
8287
8288
8289
8290Bergman, et al. Standards Track [Page 148]
8291\f
8292RFC 3805 Printer MIB v2 June 2004
8293
8294
8295 prtOutputStackingOrder - Possible minor inconvenience
8296 prtOutputPageDeliveryOrientation - Possible minor inconvenience
8297 prtOutputBursting - Possible minor inconvenience
8298 prtOutputDecollating - Possible minor inconvenience
8299 prtOutputPageCollated - Possible minor inconvenience
8300 prtOutputOffsetStacking - Possible minor inconvenience
8301 prtMarkerSuppliesTable
8302 prtMarkerSuppliesMaxCapacity - Possible minor inconvenience
8303 prtMarkerSuppliesLevel - Possible minor inconvenience
8304 prtChannelTable
8305 prtChannelCurrentJobCntlLangIndex - Possible data loss
8306 prtChannelDefaultPageDescLangIndex - Possible data loss
8307 prtChannelState - Possible minor inconvenience
8308 prtChannelIfIndex - Possible minor inconvenience
8309 prtInterpreterTable
8310 prtInterpreterDefaultOrientation - Possible data loss
8311 prtInterpreterDefaultCharSetIn - Possible data loss
8312 prtInterpreterDefaultCharSetOut - Possible minor inconvenience
8313 prtConsoleDisplayBufferTable
8314 prtConsoleDisplayBufferText - Possible minor inconvenience
8315 prtConsoleLightTable
8316 prtConsoleOnTime - Possible minor inconvenience
8317 prtConsoleOffTime - Possible minor inconvenience
8318
8319 SNMP versions prior to SNMPv3 did not include adequate security.
8320 Even if the network itself is secure (for example by using IPSec),
8321 even then, there is no control as to who on the secure network is
8322 allowed to access and GET/SET (read/change/create/delete) the objects
8323 in this MIB module.
8324
8325 It is RECOMMENDED that implementers consider the security features as
8326 provided by the SNMPv3 framework (see [RFC3410], section 8),
8327 including full support for the SNMPv3 cryptographic mechanisms (for
8328 authentication and privacy).
8329
8330 Further, deployment of SNMP versions prior to SNMPv3 is NOT
8331 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
8332 enable cryptographic security. It is then a customer/operator
8333 responsibility to ensure that the SNMP entity giving access to an
8334 instance of this MIB module is properly configured to give access to
8335 the objects only to those principals (users) that have legitimate
8336 rights to indeed GET or SET (change/create/delete) them.
8337
8338 Where the operational capability of the printing device are
8339 especially vulnerable or difficult to administer, certain objects
8340 within this MIB have been tagged as READ-ONLY, preventing
8341 modification. Further, for all READ-WRITE objects within the MIB,
8342 the working group has included specific conformance guidelines
8343
8344
8345
8346Bergman, et al. Standards Track [Page 149]
8347\f
8348RFC 3805 Printer MIB v2 June 2004
8349
8350
8351 stating that vendors are free to implement these objects as READ-
8352 ONLY. This conformance allowance should cover cases where specific
8353 vendor vulnerabilities may differ from product to product. (See
8354 conformance section with regards to MIN-ACCESS clauses).
8355
835610. References
8357
835810.1. Normative References
8359
8360 [ASCII] ANSI, "Coded Character Set - 7-bit American Standard Code
8361 for Information Interchange", ANSI X3.4-1986.
8362
8363 [CHARSET] IANA Character Set Registry:
8364 http://www.iana.org/assignments/character-sets
8365
8366 [CHARMIB] IANA Character Set MIB:
8367 http://www.iana.org/assignments/ianacharset-mib
8368
8369 [ISO10175] ISO, "Document Printing Application (DPA)", ISO 10175,
8370 1996.
8371
8372 [ISO10646] ISO, "Universal Multiple-Octet Coded Character Set (UCS) -
8373 Part 1: Architecture and Basic Multilingual Plane", ISO
8374 10646-1, September 2000. ISO, "Universal Multiple-Octet
8375 Coded Character Set (UCS) - Part 2: Supplemental Planes",
8376 ISO 10646-2, January 2001.
8377
8378 [PWGMEDIA] IEEE-ISTO PWG "The Printer Working Group Standard for
8379 Media Standardized Names", IEEE-ISTO PWG 5101.1-2002.
8380
8381 [RFC1213] McCloghrie, K. and M. Rose, "Management Information Base
8382 for Network Management of TCP/IP-based internets: MIB-II",
8383 STD 17, RFC 1213, March 1991.
8384
8385 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
8386 Requirement Levels", BCP 14, RFC 2119, March 1997.
8387
8388 [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
8389 Languages", BCP 18, RFC 2277, January 1998.
8390
8391 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
8392 10646", RFC 3629, November 2003.
8393
8394
8395
8396
8397
8398
8399
8400
8401
8402Bergman, et al. Standards Track [Page 150]
8403\f
8404RFC 3805 Printer MIB v2 June 2004
8405
8406
8407 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
8408 IANA Considerations Section in RFCs", BCP 26, RFC 2434,
8409 October 1998.
8410
8411 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
8412 "Structure of Management Information Version 2 (SMIv2)",
8413 STD 58, RFC 2578, April 1999.
8414
8415 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
8416 "Textual Conventions for SMIv2", STD 58, RFC 2579, April
8417 1999.
8418
8419 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
8420 "Conformance Statements for SMIv2", STD 58, RFC 2580,
8421 April 1999.
8422
8423 [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC
8424 2790, March 2000.
8425
8426 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
8427 MIB", RFC 2863, June 2000.
8428
8429 [RFC3806] Bergman, R., Lewis, H., and I. McDonald, "Printer
8430 Finishing MIB", RFC 3806, June 2004.
8431
843210.2. Informative References
8433
8434 [APPLEMAC] Apple staff, "Inside MacIntosh: Networking", 1994.
8435
8436 [RFC854] Postel, J. and J. Reynolds, "Telnet Protocol
8437 Specification", STD 8, RFC 854, May 1983.
8438
8439 [RFC959] Postel, J. and J. Reynolds, "File Transfer Protocol", STD
8440 9, RFC 959, October 1985.
8441
8442 [RFC1179] McLaughlin, L., "Line printer daemon protocol", RFC 1179,
8443 August 1990.
8444
8445 [RFC1350] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC
8446 1350, July 1992.
8447
8448 [RFC1945] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext
8449 Transfer Protocol - HTTP/1.0", RFC 1945, May 1996.
8450
8451 [RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
8452 RFC 2246, 1999.
8453
8454
8455
8456
8457
8458Bergman, et al. Standards Track [Page 151]
8459\f
8460RFC 3805 Printer MIB v2 June 2004
8461
8462
8463 [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
8464 Resource Identifiers (URI): Generic Syntax", RFC 2396,
8465 August 1998.
8466
8467 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
8468 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
8469 Transfer Protocol - HTTP/1.1", RFC 2616, June 1999.
8470
8471 [RFC2821] Klensin, J., Ed., "Simple Mail Transfer Protocol", RFC
8472 2821, April 2001.
8473
8474 [RFC2822] Resnick, P., Ed., "Internet Message Format", RFC 2822,
8475 April 2001.
8476
8477 [RFC2910] Herriot, R., Ed., Butler, S., Moore, P., Turner, R., and
8478 J. Wenn, "Internet Printing Protocol/1.1: Encoding and
8479 Transport", RFC 2910, September 2000.
8480
8481 [RFC2911] Hastings, T., Ed., Herriot, R., deBry, R., Isaacson, S.,
8482 and P. Powell, "Internet Printing Protocol/1.1: Model and
8483 Semantics", RFC 2911, September 2000.
8484
8485 [RFC2978] Freed, N. and J. Postel, "IANA Charset Registration
8486 Procedures", BCP 19, RFC 2978, October 2000.
8487
8488 [RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is
8489 Replaced by an On-line Database", RFC 3232, January 2002.
8490
8491 [RFC3285] Gahrns, M. and T. Hain, "Using Microsoft Word to create
8492 Internet Drafts and RFCs", RFC 3285, May 2002.
8493
8494 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
8495 "Introduction and Applicability Statements for Internet-
8496 Standard Management Framework", RFC 3410, December 2002.
8497
8498
8499
8500
8501
8502
8503
8504
8505
8506
8507
8508
8509
8510
8511
8512
8513
8514Bergman, et al. Standards Track [Page 152]
8515\f
8516RFC 3805 Printer MIB v2 June 2004
8517
8518
8519Appendix A - Glossary of Terms
8520
8521 Addressability - On the marker, the number of distinct marking units
8522 (pels) per unit of addressability unit that can be set; for example,
8523 300 dots per inch is expressed as 300 per 1000 Thousandths Of Inches
8524 and 4 dots per millimeter is 4 per 1000 Micrometers. Addressability
8525 is not resolution because marks that are one addressability position
8526 apart may not be independently resolvable by the eye due to factors
8527 such as gain in the area of marks so they overlap or nearly touch.
8528
8529 Alert - A reportable event for which there is an entry in the alert
8530 table.
8531
8532 Bin - An output sub-unit which may or may not be removable.
8533
8534 Binary Change Event - An event which comes in pairs; the leading edge
8535 event and the trailing edge event. The leading edge event enters a
8536 state from which there is only one exit. A binary change event may
8537 be critical or non-critical. See unary change event.
8538
8539 Bursting - The process by which continuous media is separated into
8540 individual sheets, typically by bursting along pre-formed
8541 perforations.
8542
8543 Channel - A term used to describe a single source of data which is
8544 presented to a printer. The model that we use in describing a
8545 printer allows for an arbitrary number of channels. Multiple
8546 channels can exist on the same physical port. This is commonly done
8547 over Ethernet ports where EtherTalk, TCP/IP, and SPX/IPX protocols
8548 can be supplying different data streams simultaneously to a single
8549 printer on the same physical port.
8550
8551 Collation - In multiple copy output, placing the pages from separate
8552 copies into separate ordered sets, ready for binding.
8553
8554 Control Language - A data syntax or language for controlling the
8555 printer through the print data channel.
8556
8557 Critical Alert - An alert triggered by an event which leads to a
8558 state in which printing is no longer possible; the printer is
8559 stopped.
8560
8561 Decollating - The process by which the individual parts within a
8562 multi-part form are separated and sorted into separate stacks for
8563 each part.
8564
8565 Description - Information about the configuration and capabilities of
8566 the printer and its various sub-units.
8567
8568
8569
8570Bergman, et al. Standards Track [Page 153]
8571\f
8572RFC 3805 Printer MIB v2 June 2004
8573
8574
8575 DPA - ISO 10175 Document Printing Application standard. A standard
8576 for a client server protocol for a print system, including (1)
8577 submitting print jobs to and (2) managing print jobs in a spooler.
8578
8579 Event - A state change in the printer.
8580
8581 Group - A collection of objects that represent a type of sub-unit of
8582 the printer.
8583
8584 Host Resources MIB - See [RFC2790].
8585
8586 IANA - Internet Assigned Numbers Authority. See [RFC3232].
8587
8588 Idempotent - Idempotence is the property of an operation that results
8589 in the same state no matter how many times it is executed (at least
8590 once). This is a property that is shared by true databases in which
8591 operations on data items only change the state of the data item and
8592 do not have other side effects. Because the SNMP data model is that
8593 of operations on a database, SNMP MIB objects should be assumed to be
8594 idempotent. If a MIB object is defined in a non-idempotent way, the
8595 this data model can break in subtle ways when faced with packet loss,
8596 multiple managers, and other common conditions.
8597
8598 In order to fulfill the common need for actions to result from
8599 SNMP Set operations, SNMP MIB objects can be modeled such that the
8600 change in state from one state to another has the side effect of
8601 causing an action. It is important to note that with this model,
8602 an SNMP operation that sets a value equal to its current value
8603 will cause no action. This retains the idempotence of a single
8604 command, while allowing actions to be initiated by SNMP SET
8605 requests.
8606
8607 Input - A tray or bin from which instances of the media are obtained
8608 and fed into the Media Path.
8609
8610 Interpreter - The embodiment of an algorithm that processes a data
8611 stream consisting of a Page Description Language (PDL) and/or a
8612 Control Language.
8613
8614 Localization - The specification of human language, country, and
8615 character set needed to present information to people in their native
8616 languages.
8617
8618 Management Application (a.k.a. Manager) - A program which queries and
8619 controls one or more managed nodes.
8620
8621 Management Station - A physical computer on which one or more
8622 management applications can run.
8623
8624
8625
8626Bergman, et al. Standards Track [Page 154]
8627\f
8628RFC 3805 Printer MIB v2 June 2004
8629
8630
8631 Media Path - The mechanisms that transport instances of the media
8632 from an input, through the marker, possibly through media buffers and
8633 duplex pathways, out to the output with optional finishing applied.
8634 The inputs and outputs are not part of the Media Path.
8635
8636 Non-critical Alert - An alert triggered by a reportable event which
8637 does not lead to a state in which printing is no longer possible;
8638 such an alert may lead to a state from which printing may no longer
8639 be possible in the future, such as the low toner state or the alert
8640 may be pure informational, such as a configuration change at the
8641 printer.
8642
8643 Output - A bin or stacker which accepts instances of media that have
8644 been processed by a printer.
8645
8646 Page Description Language (PDL) - A data syntax or language for the
8647 electronic representation of a document as a sequence of page images.
8648
8649 Printer - A physical device that takes media from an input source,
8650 produces marks on that media according to some page description or
8651 page control language and puts the result in some output destination,
8652 possibly with finishing applied.
8653
8654 Printing - The entire process of producing a printed document from
8655 generation of the file to be printed, choosing printing properties,
8656 selection of a printer, routing, queuing, resource management,
8657 scheduling, and finally printing including notifying the user.
8658
8659 Reportable event - An event that is deemed of interest to a
8660 management station watching the printer.
8661
8662 Status - Information regarding the current operating state of the
8663 printer and its various sub-units. This is an abstraction of the
8664 exact physical condition of the printer.
8665
8666 Sub-mechanism - A distinguishable part of a sub-unit.
8667
8668 Sub-unit - A part of the printer which may be a physical part, such
8669 as one of the input sources or a logical part such as an interpreter.
8670
8671 Tray - An input sub-unit which is typically removable.
8672
8673 Unary Change Event - An event that indicates a change of state of the
8674 printer, but to a state which is (often) just as valid as the state
8675 that was left, and from which no return is necessary. See binary
8676 change event.
8677
8678
8679
8680
8681
8682Bergman, et al. Standards Track [Page 155]
8683\f
8684RFC 3805 Printer MIB v2 June 2004
8685
8686
8687 Visible state - The portion of the state of the printer that can be
8688 examined by a management application.
8689
8690 Warning - A non-critical alert. See non-critical alert.
8691
8692Appendix B - Media Size Names
8693
8694 The PWG Standardized Media Names specification [PWGMEDIA], section 5
8695 Self Describing Names, contains the currently recommended media size
8696 names. This appendix lists the standardized media size names from
8697 ISO/IEC 10175 Document Printing Application (DPA), [ISO10175] as
8698 presented in RFC 1759. Management applications are encouraged to use
8699 the names from the PWG standard. However, many legacy systems exist
8700 that use the DPA names and they are presented here for the
8701 convenience of developers.
8702
8703 A printer implementing the Printer MIB has no knowledge of these
8704 names, however; all media sizes in the MIB are given in terms of
8705 media dimensions as the values of prtInputMediaDimFeedDirChosen and
8706 prtInputMediaDimXFeedDirChosen.
8707
8708 String name Description
8709
8710 other
8711
8712 unknown
8713 na-letter or letter North American letter size: 8.5 by 11 inches
8714 na-legal or legal North American legal size: 8.5 by 14 inches
8715 na-10x13-envelope North American 10x13 envelope
8716 size: 10 by 13 inches
8717 na-9x12-envelope North American 9x12 envelope
8718 size: 9 by 12 inches
8719 na-number-10-envelope North American number 10 business envelope
8720 size: 4.125 by 9.5 inches
8721 na-7x9-envelope North American 7x9 size: 7 by 9 inches
8722 na-9x11-envelope North American 9x11 size: 9 by 11 inches
8723 na-10x14-envelope North American 10x14 envelope
8724 size: 10 by 14 inches
8725 na-number-9-envelope North American number 9 business envelope
8726 size: 3.875 by 8.875 inches
8727 na-6x9-envelope North American 6x9 envelope
8728 size: 6 by 9 inches
8729 na-10x15-envelope North American 10x15 envelope
8730 size: 10 by 15 inches
8731 a engineering A size 8.5 inches by 11 inches
8732 b engineering B size 11 inches by 17 inches
8733 c engineering C size 17 inches by 22 inches
8734 d engineering D size 22 inches by 34 inches
8735
8736
8737
8738Bergman, et al. Standards Track [Page 156]
8739\f
8740RFC 3805 Printer MIB v2 June 2004
8741
8742
8743 e engineering E size 34 inches by 44 inches
8744 iso-a0 ISO A0 size: 841 mm by 1189 mm
8745 iso-a1 ISO A1 size: 594 mm by 841 mm
8746 iso-a2 ISO A2 size: 420 mm by 594 mm
8747 iso-a3 ISO A3 size: 297 mm by 420 mm
8748 iso-a4 ISO A4 size: 210 mm by 297 mm
8749 iso-a5 ISO A5 size: 148 mm by 210 mm
8750 iso-a6 ISO A6 size: 105 mm by 148 mm
8751 iso-a7 ISO A7 size: 74 mm by 105 mm
8752 iso-a8 ISO A8 size: 52 mm by 74 mm
8753 iso-a9 ISO A9 size: 37 mm by 52 mm
8754 iso-a10 ISO A10 size: 26 mm by 37 mm
8755 iso-b0 ISO B0 size: 1000 mm by 1414 mm
8756 iso-b1 ISO B1 size: 707 mm by 1000 mm
8757 iso-b2 ISO B2 size: 500 mm by 707 mm
8758 iso-b3 ISO B3 size: 353 mm by 500 mm
8759 iso-b4 ISO B4 size: 250 mm by 353 mm
8760 iso-b5 ISO B5 size: 176 mm by 250 mm
8761 iso-b6 ISO B6 size: 125 mm by 176 mm
8762 iso-b7 ISO B7 size: 88 mm by 125 mm
8763 iso-b8 ISO B8 size: 62 mm by 88 mm
8764 iso-b9 ISO B9 size: 44 mm by 62 mm
8765 iso-b10 ISO B10 size: 31 mm by 44 mm
8766 iso-c0 ISO C0 size: 917 mm by 1297 mm
8767 iso-c1 ISO C1 size: 648 mm by 917 mm
8768 iso-c2 ISO C2 size: 458 mm by 648 mm
8769 iso-c3 ISO C3 size: 324 mm by 458 mm
8770 iso-c4 ISO C4 size: 229 mm by 324 mm
8771 iso-c5 ISO C5 size: 162 mm by 229 mm
8772 iso-c6 ISO C6 size: 114 mm by 162 mm
8773 iso-c7 ISO C7 size: 81 mm by 114 mm
8774 iso-c8 ISO C8 size: 57 mm by 81 mm
8775 iso-designated ISO Designated Long
8776 size: 110 mm by 220 mm
8777 jis-b0 JIS B0 size 1030 mm by 1456 mm
8778 jis-b1 JIS B1 size 728 mm by 1030 mm
8779 jis-b2 JIS B2 size 515 mm by 728 mm
8780 jis-b3 JIS B3 size 364 mm by 515 mm
8781 jis-b4 JIS B4 size 257 mm by 364 mm
8782 jis-b5 JIS B5 size 182 mm by 257 mm
8783 jis-b6 JIS B6 size 128 mm by 182 mm
8784 jis-b7 JIS B7 size 91 mm by 128 mm
8785 jis-b8 JIS B8 size 64 mm by 91 mm
8786 jis-b9 JIS B9 size 45 mm by 64 mm
8787 jis-b10 JIS B10 size 32 mm by 45 mm
8788
8789
8790
8791
8792
8793
8794Bergman, et al. Standards Track [Page 157]
8795\f
8796RFC 3805 Printer MIB v2 June 2004
8797
8798
8799Appendix C - Media Names
8800
8801 For the convenience of management application developers, this
8802 appendix lists the standardized media names from ISO/IEC 10175
8803 Document Printing Application (DPA), [ISO10175]. Management
8804 applications that present a dialogue for choosing media may wish to
8805 use these names as an alternative to separately specifying, size,
8806 color, and/or type. New names may also be created using this format
8807 and the names defined in the PWG Standardized Media Names
8808 specification [PWGMEDIA].
8809
8810 Using standard media names will mean that a single management
8811 application dealing with printers from different vendors and under
8812 different system mangers will tend to use the same names for the same
8813 media. If selection of media by name is used, the attributes (size,
8814 type or color) implied by the name must be explicitly mapped to the
8815 appropriate object (prtInputMediaDimFeedDirDeclared,
8816 prtInputMediaDimXFeedDirDeclared, prtInputMediaType and
8817 prtInputMediaColor) in the MIB. The object prtInputMediaName is
8818 intended for display to an operator and is purely descriptive. The
8819 value in prtInputMediaName is not interpreted by the printer so using
8820 a standard name for this value will not change any of the other media
8821 attributes nor will it cause an alert if the media in the input sub-
8822 unit does not match the name.
8823
8824 Simple Name Descriptor Text
8825
8826 other
8827 unknown
8828 iso-a4-white Specifies the ISO A4 white medium with
8829 size: 210 mm by 297 mm as defined in ISO 216
8830 iso-a4-coloured Specifies the ISO A4 colored medium with
8831 size: 210 mm by 297 mm as defined in ISO 216
8832 iso-a4-transparent Specifies the ISO A4 transparent medium with
8833 size: 210 mm by 297 mm as defined in ISO 216
8834 iso-a3-white Specifies the ISO A3 white medium with
8835 size: 297 mm by 420 mm as defined in ISO 216
8836 iso-a3-coloured Specifies the ISO A3 colored medium with
8837 size: 297 mm by 420 mm as defined in ISO 216
8838 iso-a5-white Specifies the ISO A5 white medium with
8839 size: 148 mm by 210 mm as defined in ISO 216
8840 iso-a5-coloured Specifies the ISO A5 colored medium with
8841 size: 148 mm by 210 mm as defined in ISO 216
8842 iso-b4-white Specifies the ISO B4 white medium with
8843 size: 250 mm by 353 mm as defined in ISO 216
8844 iso-b4-coloured Specifies the ISO B4 colored medium with
8845 size: 250 mm by 353 mm as defined in ISO 216
8846
8847
8848
8849
8850Bergman, et al. Standards Track [Page 158]
8851\f
8852RFC 3805 Printer MIB v2 June 2004
8853
8854
8855 iso-b5-white Specifies the ISO B5 white medium with
8856 size: 176 mm by 250 mm as defined in ISO 216
8857 iso-b5-coloured Specifies the ISO B5 colored medium with
8858 size: 176 mm by 250 mm as defined in ISO 216
8859 jis-b4-white Specifies the JIS B4 white medium with
8860 size: 257 mm by 364 mm as defined in JIS P0138
8861 jis-b4-coloured Specifies the JIS B4 colored medium with
8862 size: 257 mm by 364 mm as defined in JIS P0138
8863 jis-b5-white Specifies the JIS B5 white medium with
8864 size: 182 mm by 257 mm as defined in JIS P0138
8865 jis-b5-coloured Specifies the JIS B5 colored medium with
8866 size: 182 mm by 257 mm as defined in JIS P0138
8867
8868 The following standard values are defined for North American media:
8869
8870 na-letter-white Specifies the North American letter white
8871 medium with size: 8.5 inches by 11 inches
8872 na-letter-coloured Specifies the North American letter colored
8873 medium with size: 8.5 inches by 11 inches
8874 na-letter-transparent
8875 Specifies the North American letter
8876 transparent medium with size: 8.5 inches
8877 by 11 inches
8878 na-legal-white Specifies the North American legal white
8879 medium with size: 8.5 inches by 14 inches
8880 na-legal-coloured Specifies the North American legal colored
8881 medium with size: 8.5 inches by 14 inches
8882
8883 The following standard values are defined for envelopes:
8884
8885 iso-b5-envelope Specifies the ISO B5 envelope medium
8886 with size: 176 mm by 250 mm
8887 as defined in ISO 216 and ISO 269
8888 iso-b4-envelope Specifies the ISO B4 envelope medium
8889 with size: 250 mm by 353 mm
8890 as defined in ISO 216
8891 iso-c4-envelope Specifies the ISO C4 envelope medium
8892 with size: 229 mm by 324 mm
8893 as defined in ISO 216 and ISO 269
8894 iso-c5-envelope Specifies the ISO C5 envelope medium
8895 with size: 162 mm by 229 mm
8896 as defined in ISO 269
8897 iso-designated-long-envelope
8898 Specifies the ISO Designated Long envelope
8899 medium with size: 110 mm by 220 mm
8900 as defined in ISO 269
8901
8902
8903
8904
8905
8906Bergman, et al. Standards Track [Page 159]
8907\f
8908RFC 3805 Printer MIB v2 June 2004
8909
8910
8911 na-10x13-envelope Specifies the North American 10x13 envelope
8912 medium with size: 10 inches by 13 inches
8913 na-9x12-envelope Specifies the North American 9x12 envelope
8914 medium with size: 9 inches by 12 inches
8915 na-number-10-envelope
8916 Specifies the North American number 10
8917 business envelope medium with size: 4.125
8918 inches by 9.5 inches
8919 na-7x9-envelope Specifies the North American 7x9 inch envelope
8920
8921 na-9x11-envelope Specifies the North American 9x11 inch envelope
8922
8923 na-10x14-envelope Specifies the North American 10x14 inch envelope
8924
8925 na-number-9-envelope
8926 Specifies the North American number 9
8927 business envelope 3.875 by 8.875 inches
8928 na-6x9-envelope Specifies the North American 6x9 inch envelope
8929
8930 na-10x15-envelope Specifies the North American 10x15 inch envelope
8931
8932 The following standard values are defined for the less commonly
8933 used media (white-only):
8934
8935 iso-a0-white Specifies the ISO A0 white medium
8936 with size: 841 mm by 1189 mm
8937 as defined in ISO 216
8938 iso-a1-white Specifies the ISO A1 white medium
8939 with size: 594 mm by 841 mm
8940 as defined in ISO 216
8941 iso-a2-white Specifies the ISO A2 white medium
8942 with size: 420 mm by 594 mm
8943 as defined in ISO 216
8944 iso-a6-white Specifies the ISO A6 white medium
8945 with size: 105 mm by 148 mm
8946 as defined in ISO 216
8947 iso-a7-white Specifies the ISO A7 white medium
8948 with size: 74 mm by 105 mm
8949 as defined in ISO 216
8950 iso-a8-white Specifies the ISO A8 white medium
8951 with size: 52 mm by 74 mm
8952 as defined in ISO 216
8953 iso-a9-white Specifies the ISO A9 white medium
8954 with size: 39 mm by 52 mm
8955 as defined in ISO 216
8956 iso-a10-white Specifies the ISO A10 white medium
8957 with size: 26 mm by 37 mm
8958 as defined in ISO 216
8959
8960
8961
8962Bergman, et al. Standards Track [Page 160]
8963\f
8964RFC 3805 Printer MIB v2 June 2004
8965
8966
8967 iso-b0-white Specifies the ISO B0 white medium
8968 with size: 1000 mm by 1414 mm
8969 as defined in ISO 216
8970 iso-b1-white Specifies the ISO B1 white medium
8971 with size: 707 mm by 1000 mm
8972 as defined in ISO 216
8973 iso-b2-white Specifies the ISO B2 white medium
8974 with size: 500 mm by 707 mm
8975 as defined in ISO 216
8976 iso-b3-white Specifies the ISO B3 white medium
8977 with size: 353 mm by 500 mm
8978 as defined in ISO 216
8979 iso-b6-white Specifies the ISO B6 white medium
8980 with size: 125 mm by 176 mm i
8981 as defined in ISO 216
8982 iso-b7-white Specifies the ISO B7 white medium
8983 with size: 88 mm by 125 mm
8984 as defined in ISO 216
8985 iso-b8-white Specifies the ISO B8 white medium
8986 with size: 62 mm by 88 mm
8987 as defined in ISO 216
8988 iso-b9-white Specifies the ISO B9 white medium
8989 with size: 44 mm by 62 mm
8990 as defined in ISO 216
8991 iso-b10-white Specifies the ISO B10 white medium
8992 with size: 31 mm by 44 mm
8993 as defined in ISO 216
8994 jis-b0-white Specifies the JIS B0 white medium with size:
8995 1030 mm by 1456 mm
8996 jis-b1-white Specifies the JIS B1 white medium with size:
8997 728 mm by 1030 mm
8998 jis-b2-white Specifies the JIS B2 white medium with size:
8999 515 mm by 728 mm
9000 jis-b3-white Specifies the JIS B3 white medium with size:
9001 364 mm by 515 mm
9002 jis-b6-white Specifies the JIS B6 white medium with size:
9003 257 mm by 364 mm
9004 jis-b7-white Specifies the JIS B7 white medium with size:
9005 182 mm by 257 mm
9006 jis-b8-white Specifies the JIS B8 white medium with size:
9007 128 mm by 182 mm
9008 jis-b9-white Specifies the JIS B9 white medium with size:
9009 91 mm by 128 mm
9010 jis-b10-white Specifies the JIS B10 white medium with size:
9011 64 mm by 91 mm
9012
9013
9014
9015
9016
9017
9018Bergman, et al. Standards Track [Page 161]
9019\f
9020RFC 3805 Printer MIB v2 June 2004
9021
9022
9023 The following standard values are defined for engineering media:
9024 a Specifies the engineering A size medium with
9025 size: 8.5 inches by 11 inches
9026 b Specifies the engineering B size medium with
9027 size: 11 inches by 17 inches
9028 c Specifies the engineering C size medium with
9029 size: 17 inches by 22 inches
9030 d Specifies the engineering D size medium with
9031 size: 22 inches by 34 inches
9032 e Specifies the engineering E size medium with
9033 size: 34 inches by 44 inches
9034
9035Appendix D - Roles of Users
9036
9037 Background
9038
9039 The need for "Role Models" stemmed in large part from the need to
9040 understand the importance of any given proposed object for the MIB.
9041 Many times the real world need for a proposed object would be debated
9042 within the group; the debate would typically result in the need to
9043 describe the potential usage of the object in terms of a "live"
9044 person performing some type of printing-related task.
9045
9046 Determining the value of a proposed object through identification of
9047 the associated human users was found to be so common that a more
9048 formalized model was required for consistent analysis. The model
9049 describing categories of human-oriented tasks is called "Role Models"
9050 in this document.
9051
9052 In developing the Role Models it was necessary to identify the
9053 common, primary tasks that humans typically face when interacting
9054 with a printer and its related printing system(s). It was expected
9055 that certain kinds of tasks would serve to identify the various Role
9056 Models.
9057
9058 In presenting the set of Role Models, the set of "Common Print System
9059 Tasks" are first presented, followed by the set of Role Model
9060 definitions. Finally, a simple matrix is presented in which Role
9061 Models and Tasks are cross-compared.
9062
9063 Common Print System Tasks
9064
9065 Upon researching the many tasks encountered by humans in dealing with
9066 printers and printing systems, the following were found to be
9067 pervasive within any operating environment:
9068
9069 Printer job state - Determine the status of a job without a printer.
9070
9071
9072
9073
9074Bergman, et al. Standards Track [Page 162]
9075\f
9076RFC 3805 Printer MIB v2 June 2004
9077
9078
9079 Printer capabilities - Determine the current capabilities of a
9080 printer, for example, the available media sizes, two-sided printing,
9081 a particular type of interpreter, etc.
9082
9083 Printer job submission - Submit a print job to a printer.
9084
9085 Printer job removal - Remove a job from a printer.
9086
9087 Notification of events - Receive notification of the existence of a
9088 defined printer event. An event can be of many types, including
9089 warnings, errors, job stage completion (e.g., "job done"), etc.
9090
9091 Printer configuration - Query the current configuration of a printer.
9092
9093 Printer consumables - Determine the current state of any and all
9094 consumables within a printer.
9095
9096 Print job identification - Determine the identification of a job
9097 within a printer.
9098
9099 Internal printer status - Determine the current status of the
9100 printer.
9101
9102 Printer identification - Determine the identity of a printer.
9103 Printer location - Determine the physical location of a printer.
9104
9105 Local system configuration - Determine various aspects of the current
9106 configuration of the local system involved with the operation of a
9107 printer.
9108
9109 These "tasks" cover a large spectrum of requirements surrounding the
9110 operation of a printer in a network environment. This list serves as
9111 the basis for defining the various Role Models described below.
9112
9113 Proposed Role Models
9114
9115 Following is the list of "Role Models" used to evaluate the
9116 requirements for any given Printer MIB object. Note that the keyword
9117 enclosed in parentheses represents an abbreviation for the particular
9118 Role Model in the matrix described later in this document.
9119
9120 User (USER) - A person or application that submits print jobs to the
9121 printer; typically viewed as the "end user" within the overall
9122 printing environment.
9123
9124
9125
9126
9127
9128
9129
9130Bergman, et al. Standards Track [Page 163]
9131\f
9132RFC 3805 Printer MIB v2 June 2004
9133
9134
9135 Operator (OP) - A person responsible for maintaining a printer on a
9136 day-to-day basis, including such tasks as filling empty media trays,
9137 emptying full output trays, replacing toner cartridges, clearing
9138 simple paper jams, etc.
9139
9140 Technician (TECH) - A person responsible for repairing a
9141 malfunctioning printer, performing routine preventive maintenance,
9142 and other tasks that typically require advanced training on the
9143 printer internals. An example of a "technician" would be a
9144 manufacturer's Field Service representative, or other person formally
9145 trained by the manufacturer or similar representative.
9146
9147 System Manager (MGR) - A person responsible for configuration and
9148 troubleshooting of components involved in the overall printing
9149 environment, including printers, print queues and network
9150 connectivity issues. This person is typically responsible for
9151 ensuring the overall operational integrity of the print system
9152 components, and is typically viewed as the central point of
9153 coordination among all other Role Models.
9154
9155 Help Desk (HELP) - A person responsible for supporting Users in
9156 their printing needs, including training Users and troubleshooting
9157 Users' printing problems.
9158
9159 Asset Manager (AM) - A person responsible for managing an
9160 organization's printing system assets (primarily printers). Such a
9161 person needs to be able to identify and track the location of
9162 printing assets on an ongoing basis.
9163
9164 Capacity Planner (CP) - A person responsible for tracking the usage
9165 of printing resources on an ongoing basis for the purpose of planning
9166 printer acquisitions and/or placement of printers based on usage
9167 trends.
9168
9169 Installer (INST) - A person or application responsible for
9170 installing or configuring printing system components on a local
9171 system.
9172
9173 Accountant (ACCT) - A person responsible for tracking the usage of
9174 printing resources on an ongoing basis for the purpose of charging
9175 Users for resources used.
9176
9177 Matrix of Common Print System Tasks and Role Models
9178
9179 To better understand the relationship between the set of defined
9180 "Common Print System Tasks" and the various "Role Models," the
9181 following matrix is provided.
9182
9183
9184
9185
9186Bergman, et al. Standards Track [Page 164]
9187\f
9188RFC 3805 Printer MIB v2 June 2004
9189
9190
9191 It is important to recognize that many of the tasks will appear to be
9192 applicable to many of the Role Models. However, when considering the
9193 actual context of a task, it is very important to realize that often
9194 the actual context of a task is such that the Role Model can change.
9195
9196 For example, it is obvious that a "System Manager" must be able to
9197 submit print jobs to a printer; however, when submitting a print job,
9198 a person identified as a "System Manager" is actually operating in
9199 the context of a "User" in this case; hence, the requirement to
9200 submit a print job is not listed as a requirement for a System
9201 Manager.
9202
9203 Conversely, while a "User" must be able to remove a job previously
9204 submitted to a printer, an "Operator" is often expected to be able to
9205 remove any print job from any printer; hence, print job removal is a
9206 (subtly different) requirement for both the "User" and "Operator"
9207 Role Models.
9208
9209 Role Models
9210 -----------
9211
9212 Requirement Area USER OP TECH MGR HELP AM CP INST ACCT
9213 Print job status xx xx xx xx xx
9214 Printer capabilities xx xx xx
9215 Print job submission xx
9216 Print job removal xx xx
9217 Notification of events xx xx
9218 Printer configuration xx xx
9219 Printer consumables xx xx xx
9220 Print job identification xx xx xx xx xx
9221 Internal printer status xx xx xx
9222 Printer identification xx xx xx xx xx xx xx
9223 Printer location xx
9224 Local system configuration xx xx
9225
9226Appendix E - Overall Printer Status Table
9227
9228 The Status Table establishes a convention for the top 25 printer
9229 errors. The table defines a suggested relationship between various
9230 printer states and the variables Printer hrDeviceStatus,
9231 hrPrinterStatus, hrPrinterDetectedErrorState, prtAlertGroup,
9232 prtAlertCode and various sub-unit status variables (prtInputStatus,
9233 prtOutputStatus, prtMarkerStatus, prtMediaPathStatus and
9234 prtChannelStatus). This table is the recommended implementation of
9235 these variables. It is provided to guide implementors of this MIB
9236 and users of the MIB by providing a sample set of states and the
9237 variable values that are expected to be produced as result of that
9238 state. This information supplements that provided in Section
9239
9240
9241
9242Bergman, et al. Standards Track [Page 165]
9243\f
9244RFC 3805 Printer MIB v2 June 2004
9245
9246
9247 2.2.13.2 "Overall Printer Status". This is not an exhaustive list
9248 rather it is a guideline.
9249
9250 The definition of PrtSubUnitStatusTC specifies that SubUnitStatus is
9251 an integer that is the sum of 5 distinct values/states: Availability,
9252 Critical, Non-Critical, On-line and Transitioning. Thus when a non-
9253 critical alert or alerts are present the values for Availability,
9254 On-Line and Transitioning will be summed with the Non- Critical
9255 Alerts (8) value.
9256
9257 The table was generated in landscape format and is located at
9258 ftp://ftp.pwg.org/pub/pwg/pmp/contributions/Top25Errors.pdf.
9259
9260Appendix F - Participants
9261
9262 The Printer MIB Working Group would like to extend a special thank
9263 you to the following individuals that put forth a significant effort
9264 to review this document and provide numerous suggestions for
9265 improvement.
9266
9267 David Harrington - Enterasys Networks
9268 Juergen Schoenwaelder - TU Braunschweig
9269 Bert Wijnen - Lucent Technologies and IETF Op & Mngmt, Area Director
9270
9271 This version of the Printer MIB would not be possible without the
9272 previous work that resulted in RFC 1759. The authors of the Printer
9273 MIB version 2 would like to acknowledge the following individuals for
9274 their efforts in developing the base for this document. A special
9275 recognition is also extended to Steve Waldbusser, who provided
9276 significant technical guidance in the development of the architecture
9277 of the Printer MIB.
9278
9279 Joel Gyllenskog - Microworks
9280 Tom Hastings - Xerox
9281 Jay Martin - Underscore, Inc.
9282 Ron Smith - Texas Instruments
9283 Steve Waldbusser - Lucent Technologies
9284 Don Wright - Lexmark
9285 Steve Zilles - Adobe
9286
9287 The following people attended at least one meeting of the Printer MIB
9288 Working Group for version 2; many attended most meetings.
9289
9290 Ron Bergman - Hitachi Printing Solutions
9291 Luis Cubero - Hewlett-Packard
9292 Jay Cummings - Novell
9293 Andy Davidson - Tektronix
9294 Lee Farrell - Canon
9295
9296
9297
9298Bergman, et al. Standards Track [Page 166]
9299\f
9300RFC 3805 Printer MIB v2 June 2004
9301
9302
9303 Tom Hastings - Xerox
9304 Scott Isaacson - Novell
9305 Binnur Al-Kazily - Hewlett-Packard
9306 Rick Landau - Digital Equipment Corporation
9307 David Kellerman - Northlake Software
9308 Harry Lewis - IBM
9309 Pete Loya - Hewlett-Packard
9310 Jay Martin - Underscore, Inc.
9311 Bob Pentecost - Hewlett-Packard
9312 Dave Roach - Unisys
9313 Stuart Rowley - Kyocera
9314 Bob Setterbo - Adobe
9315 Mike Timperman - Lexmark
9316 Randy Turner - 2Wire, Inc.
9317 Bill Wagner - NETsilicon, Inc.
9318 Chris Wellens - Interworking Labs
9319 Craig Whittle - Sharp Labs
9320 Don Wright - Lexmark
9321 Lloyd Young - Lexmark
9322 Atsushi Yuki - Kyocera
9323 Steve Zilles - Adobe
9324
9325
9326
9327
9328
9329
9330
9331
9332
9333
9334
9335
9336
9337
9338
9339
9340
9341
9342
9343
9344
9345
9346
9347
9348
9349
9350
9351
9352
9353
9354Bergman, et al. Standards Track [Page 167]
9355\f
9356RFC 3805 Printer MIB v2 June 2004
9357
9358
9359Significant Contributors
9360
9361 Ray Casterline
9362 Lighthouse Solutions, LLC
9363
9364 Phone: (716) 218-9910
9365 EMail: RayCasterline@lhsolutions.com
9366
9367 Gary Gocek
9368
9369 Phone: (585) 223-3826
9370 EMail: gary@gocek.org
9371
9372 Thomas N. Hastings
9373 Xerox Corporation
9374
9375 Phone: (310) 333-6413
9376 EMail: hastings@cp10.es.xerox.com
9377
9378 Scott Isaacson
9379 Novell
9380
9381 Phone: (801) 861-7366
9382 EMail: sisaacson@novell.com
9383
9384 Binnur Al-Kazily
9385 Hewlett-Packard, Inc.
9386
9387 Phone: (208) 396-6372
9388 EMail: binnur_al-kazily@hp.com
9389
9390 David Kellerman
9391 Northlake Software
9392
9393 Phone: (503) 228-3383
9394 EMail: kellerman@nls.com
9395
9396 Matt King
9397 Lexmark International
9398
9399 Phone: (859) 232-6907
9400 EMail: emking@lexmark.com
9401
9402 Jay Martin
9403 Underscore, Inc.
9404
9405 Phone: (603) 889-7000
9406 EMail: jkm@underscore.com
9407
9408
9409
9410Bergman, et al. Standards Track [Page 168]
9411\f
9412RFC 3805 Printer MIB v2 June 2004
9413
9414
9415
9416 Mike McKay
9417 Novell, Inc.
9418
9419 Bob Pentecost
9420 Hewlett-Packard
9421
9422 Phone: (208) 396-3312
9423 EMail: bpenteco@boi.hp.com
9424
9425 Stuart Rowley
9426 Kyocera
9427
9428 Phone: (510) 299-7206
9429 EMail: stuart.rowley@kyocera.com
9430
9431 Gail Songer
9432 Peerless Systems Networking
9433
9434 Phone: (650) 569-4414
9435 EMail: gsonger@peerless.com
9436
9437 Randy Turner
9438 2Wire, Inc.
9439
9440 Phone (408) 895-1216
9441 EMail: rturner@2wire.com
9442
9443 William Wagner
9444 NETsilicon, Inc.
9445
9446 Phone: (781) 398-4588
9447 EMail: WWagner@NetSilicon.com
9448
9449 Chris Wellens
9450 Interworking Labs
9451
9452 Phone: (408) 685-3190
9453 EMail: chrisw@iwl.com
9454
9455 F.D. Wright
9456 Lexmark International
9457
9458 Phone: (859) 232-4808
9459 EMail: don@lexmark.com
9460
9461
9462
9463
9464
9465
9466Bergman, et al. Standards Track [Page 169]
9467\f
9468RFC 3805 Printer MIB v2 June 2004
9469
9470
9471 Lloyd Young
9472 Lexmark International
9473
9474 Phone: (859) 232-5150
9475 EMail: lpyoung@lexmark.com
9476
9477 Stephen N. Zilles
9478 Adobe Systems, Inc.
9479
9480 Phone: (415) 962-4766
9481 EMail: szilles@adobe.com
9482
9483Authors' Addresses
9484
9485 Ron Bergman (Chairman)
9486 Hitachi Printing Solutions America
9487 2635 Park Center Drive
9488 Simi Valley, CA 93065-6209
9489
9490 Phone: (805) 578-4421
9491 EMail: Ron.Bergman@hitachi-ps.us
9492
9493
9494 Harry Lewis
9495 IBM
9496 6300 Diagonal Hwy.
9497 Boulder, CO 80301
9498
9499 Phone (303) 924-5337
9500 EMail: harryl@us.ibm.com
9501
9502
9503 Ira McDonald
9504 High North Inc
9505 P.O. Box 221
9506 Grand Marais, MI 49839
9507
9508 Phone: (906) 494-2434 or (906) 494-2697
9509 EMail: imcdonald@sharplabs.com
9510
9511
9512
9513
9514
9515
9516
9517
9518
9519
9520
9521
9522Bergman, et al. Standards Track [Page 170]
9523\f
9524RFC 3805 Printer MIB v2 June 2004
9525
9526
9527Full Copyright Statement
9528
9529 Copyright (C) The Internet Society (2004). This document is subject
9530 to the rights, licenses and restrictions contained in BCP 78, and
9531 except as set forth therein, the authors retain all their rights.
9532
9533 This document and the information contained herein are provided on an
9534 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
9535 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
9536 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
9537 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
9538 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
9539 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
9540
9541Intellectual Property
9542
9543 The IETF takes no position regarding the validity or scope of any
9544 Intellectual Property Rights or other rights that might be claimed to
9545 pertain to the implementation or use of the technology described in
9546 this document or the extent to which any license under such rights
9547 might or might not be available; nor does it represent that it has
9548 made any independent effort to identify any such rights. Information
9549 on the procedures with respect to rights in RFC documents can be
9550 found in BCP 78 and BCP 79.
9551
9552 Copies of IPR disclosures made to the IETF Secretariat and any
9553 assurances of licenses to be made available, or the result of an
9554 attempt made to obtain a general license or permission for the use of
9555 such proprietary rights by implementers or users of this
9556 specification can be obtained from the IETF on-line IPR repository at
9557 http://www.ietf.org/ipr.
9558
9559 The IETF invites any interested party to bring to its attention any
9560 copyrights, patents or patent applications, or other proprietary
9561 rights that may cover technology that may be required to implement
9562 this standard. Please address the information to the IETF at ietf-
9563 ipr@ietf.org.
9564
9565Acknowledgement
9566
9567 Funding for the RFC Editor function is currently provided by the
9568 Internet Society.
9569
9570
9571
9572
9573
9574
9575
9576
9577
9578Bergman, et al. Standards Track [Page 171]
9579\f
Unnamed repository; edit this file 'description' to name the repository.