idnits 2.17.1 draft-ietf-printmib-mib-info-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The abstract seems to indicate that this document obsoletes RFC1759, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 151 has weird spacing: '... system prin...' == Line 152 has weird spacing: '...manager opera...' == Line 721 has weird spacing: '...ritical warn...' == Line 730 has weird spacing: '...ailable dow...' == Line 1049 has weird spacing: '...alue in the o...' == (16 more instances...) == Unrecognized Status in '[Target Category: Standards Track]', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (8 October 2002) is 7871 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'CHARSET' is defined on line 7002, but no explicit reference was found in the text == Unused Reference: 'RFC2978' is defined on line 7135, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ASCII' -- Possible downref: Non-RFC (?) normative reference: ref. 'CHARSET' -- Possible downref: Non-RFC (?) normative reference: ref. 'CHARMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO10175' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO10646' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWGMEDIA' ** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCnnnn' -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2246 (Obsoleted by RFC 4346) -- Obsolete informational reference (is this intentional?): RFC 2396 (Obsoleted by RFC 3986) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 2571 (Obsoleted by RFC 3411) -- Obsolete informational reference (is this intentional?): RFC 2572 (Obsoleted by RFC 3412) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) -- Obsolete informational reference (is this intentional?): RFC 2821 (Obsoleted by RFC 5321) -- Obsolete informational reference (is this intentional?): RFC 2822 (Obsoleted by RFC 5322) -- Obsolete informational reference (is this intentional?): RFC 2910 (Obsoleted by RFC 8010) -- Obsolete informational reference (is this intentional?): RFC 2911 (Obsoleted by RFC 8011) -- Obsolete informational reference (is this intentional?): RFC 3285 (Obsoleted by RFC 5385) Summary: 4 errors (**), 0 flaws (~~), 10 warnings (==), 26 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Printer MIB Working Group Ron Bergman 3 [Request for Comments: XXXX] Hitachi Printing Solutions 4 [Obsoletes: RFC 1759] Harry Lewis 5 [Target Category: Standards Track] IBM Corp. 6 Ira McDonald 7 High North Inc 8 Expires 8 April 2003 8 October 2002 10 Printer MIB v2 11 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of Section 10 of RFC 2026 [RFC2026]. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that other 20 groups may also distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or made obsolete by other documents at 24 any time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/1id-abstracts.html 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 For tips on printing this document or on modifying the original 34 Microsoft Word source document, see [RFC3285]. 36 Copyright Notice 38 Copyright (C) The Internet Society (2002). All Rights Reserved. 40 Abstract 42 This document provides definitions of models and manageable objects 43 for printing environments. The objects included in this MIB apply to 44 physical, as well as logical entities within a printing device. This 45 document obsoletes RFC 1759. 47 Table of Contents 49 Status of this Memo..........................................1 50 Abstract.....................................................1 51 1. Introduction.............................................4 52 1.1 Network Printing Environment............................4 53 1.2 Printer Device Overview.................................5 54 1.3 Categories of Printer Information.......................6 55 1.3.1 Descriptions..........................................6 56 1.3.2 Status................................................6 57 1.3.3 Alerts................................................6 58 1.4 The SNMP Management Framework...........................7 59 1.5 Requirement Levels.......................................8 60 2. Printer Model............................................8 61 2.1 Overview of the Printer Model..........................11 62 2.2 Printer Sub-Units......................................11 63 2.2.1 General Printer......................................11 64 2.2.1.1 International Considerations.......................12 65 2.2.2 Inputs...............................................12 66 2.2.3 Media................................................13 67 2.2.4 Outputs..............................................13 68 2.2.5 Finishers............................................13 69 2.2.6 Markers..............................................14 70 2.2.7 Media Paths..........................................14 71 2.2.8 System Controller....................................15 72 2.2.9 Interfaces...........................................15 73 2.2.10 Print Job Delivery Channels.........................15 74 2.2.11 Interpreters........................................16 75 2.2.12 Console.............................................16 76 2.2.13 Alerts..............................................16 77 2.2.13.1 Status and Alerts.................................17 78 2.2.13.2 Overall Printer Status............................17 79 2.2.13.2.1 Host Resources MIB Printer Status...............19 80 2.2.13.2.2 Sub-unit Status.................................23 81 2.2.13.3 Alert Tables......................................24 82 2.2.13.4 Alert Table Management............................24 83 2.3 Read-Write Objects.....................................26 84 2.4 Enumerations...........................................27 85 2.4.1 Registering Additional Enumerated Values.............28 86 3. Groups from other MIB Specifications....................28 87 3.1 System Group...........................................28 88 3.2 System Controller......................................29 89 3.3 Interface Group objects................................29 90 3.3.1 Interface Types......................................29 91 4. Differences from RFC 1759...............................29 92 5. The IANA Printer MIB....................................33 93 6. The Printer MIB.........................................62 94 -- Textual conventions for this MIB module..................64 95 -- The General Printer Group................................72 96 -- The Responsible Party group..............................76 97 -- The Auxiliary Sheet Group................................79 98 -- Administrative section (The General V2 Group)...........80 99 -- General alert table section (Alert Table V2 Group)......80 100 -- The Cover Table..........................................81 101 -- The Localization Table...................................83 102 -- The System Resources Tables..............................84 103 -- The Input Group..........................................87 104 -- The Extended Input Group.................................93 105 -- The Input Media Group....................................94 106 -- The Input Switching Group................................96 107 -- The Output Group.........................................97 108 -- The Extended Output Group...............................101 109 -- The Output Dimensions Group.............................102 110 -- The Output Features Group...............................104 111 -- The Marker Group........................................106 112 -- The Marker Supplies Group...............................112 113 -- The Marker Colorant Group...............................115 114 -- The Media Path Group....................................118 115 -- The Print Job Delivery Channel Group....................122 116 -- The Interpreter Group...................................130 117 -- The Console Group.......................................134 118 -- The Alerts Group........................................139 119 -- Conformance Information.................................144 120 7. IANA Considerations....................................157 121 8. Internationalization Considerations....................157 122 9. Security Considerations................................157 123 10. Copyright Section.....................................158 124 11. Normative References..................................159 125 12. Informative References................................160 126 Appendix A - Glossary of Terms.............................162 127 Appendix B - Media Size Names..............................167 128 Appendix C - Media Names...................................169 129 Appendix D - Roles of Users................................174 130 Appendix E - Overall Printer Status Table..................178 131 Appendix F - Participants..................................179 132 Authors' Addresses.........................................179 134 1. Introduction 136 1.1 Network Printing Environment 138 The management of producing a printed document, in any computer 139 environment, is a complex subject. Basically, the task can be divided 140 into two overlapping pieces, the management of printing and the 141 management of the printer. Printing encompasses the entire process of 142 producing a printed document from generation of the file to be 143 printed, selection of a printer, choosing printing properties, 144 routing, queuing, resource management, scheduling, and final printing 145 including notifying the user. Most of the printing process is 146 outside the scope of the model presented here; only the management of 147 the printer is covered. 149 Figure 1 - One Printer's View of the Network 151 system printer asset user user user 152 manager operator manager 153 O O O O O O 154 /|\ /|\ /|\ /|\ /|\ /|\ 155 / \ / \ / \ / \ / \ / \ 156 | | | | | | 157 +---------+ +-------+ +-------+ +-------+ +-----------+ +-----------+ 158 |configur-| |printer| | asset | |printer| | user | | user | 159 |ator | |manager| |manager| |browser| |application| |application| 160 +---------+ +-------+ +-------+ +-------+ +-----------+ +-----------+ 161 ^ ^ ^ ^ | | 162 |R/W |R/W |R |R +-----------+ +-----------+ 163 | | | | | spooler | | spooler | 164 | | | | +-----------+ +-----------+ 165 | | | | | | 166 | | | | +-----------+ +-----------+ 167 | | | | |supervisor | |supervisor | 168 | | | | +-----------+ +-----------+ 169 | | | | ^ ^ ^ ^ 170 | | | | |R |R/W |R |R/W 171 v v | | | | | | 172 ================================================== | ===== | 173 | print| print| 174 |SNMP data| data| 175 +-----+ +-------+ PCL| PCL| 176 | MIB |<------>| agent | PostScript| PostScript| 177 +-----+ +-------+ NPAP| NPAP| 178 |unspecified etc.| etc.| 179 +=============+ +-----------------+ | | 180 | |--|channel/interface|<--+ | 181 | | +-----------------+ | 182 | PRINTER | | 183 | | +-----------------+ | 184 | |--|channel/interface|<----------------+ 185 +=============+ +-----------------+ 187 1.2 Printer Device Overview 189 A printer is the physical device that takes media from an input 190 source, produces marks on that media according to some page 191 description or page control language and puts the result in some 192 output destination, possibly with finishing applied. Printers are 193 complex devices that consume supplies, produce waste and may have 194 mechanical problems. In the management of the physical device the 195 description, status and alert information concerning the printer and 196 its various subparts has to be made available to the management 197 application so that it can be reported to the end user, key operators 198 for the replenishment of supplies or the repair or maintenance of the 199 device. The information needed in the management of the physical 200 printer and the management of a printing job overlap highly and many 201 of the tasks in each management area require the same or similar 202 information. 204 1.3 Categories of Printer Information 206 Information about printers is classified into three basic categories: 207 descriptions, status and alerts. 209 1.3.1 Descriptions 211 Descriptions convey information about the configuration and 212 capabilities of the printer and its various sub-units. This 213 information is largely static information and does not generally 214 change during the operation of the system but may change as the 215 printer is repaired, reconfigured or upgraded. The descriptions are 216 one part of the visible state of the printer where state means the 217 condition of being of the printer at any point in time. 219 1.3.2 Status 221 Status is the information regarding the current operating state of 222 the printer and its various sub-units. Status is the rest of the 223 visible state of the printer. As an example of the use of status, a 224 management application must be able to determine if the various sub- 225 units are ready to print or are in some state that prevents printing 226 or may prevent printing in the future. 228 1.3.3 Alerts 230 An Alert is the representation of a reportable event in the printer. 231 An event is a change in the state of the printer. Some of those state 232 changes are of interest to a management application and are therefore 233 reportable. Typically, these are the events that affect the printer's 234 ability to print. Alerts usually occur asynchronously to the 235 operation of the computer system(s) to which the printer is attached. 236 For convenience below, "alert" will be used for both the event caused 237 by a change in the printer's state and for the representation of that 238 event. 240 Alerts can be classified into two basic categories, critical and non- 241 critical. A critical alert is one that is triggered by entry into a 242 state in which the printer is stopped and printing can not continue 243 until the condition that caused the critical alert is eliminated. 244 "Out of paper", "toner empty" and "output bin full" are examples of 245 critical alerts. Non-critical alerts are triggered by those events 246 that enter a state in which printing is not stopped. Such a non- 247 critical state may, at some future time, lead to a state in which 248 printing may be stopped. Examples of these kinds of non-critical 249 alerts are "input media low", "toner low" and "output bin nearly 250 full". Or, a non-critical alert may simply provide information, such 251 as signaling a configuration changed in the printer. 253 Description, status and alert information about the printer can be 254 thought of as a database describing the printer. The management 255 application for a printer will want to view the printer data base 256 differently depending on how and for what purposes the information in 257 the database is needed. 259 1.4 The SNMP Management Framework 261 The SNMP Management Framework presently consists of five major 262 components: 264 o An overall architecture, described in RFC 2571 [RFC2571]. 266 o Mechanisms for describing and naming objects and events for the 267 purpose of management. The first version of this Structure of 268 Management Information (SMI) is called SMIv1 and described in STD 269 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 270 [RFC1215]. The second version, called SMIv2, is described in STD 271 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 272 2580 [RFC2580]. 274 o Message protocols for transferring management information. The 275 first version of the SNMP message protocol is called SNMPv1 and 276 described in STD 15, RFC 1157 [RFC1157]. A second version of the 277 SNMP message protocol, which is not an Internet standards track 278 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 279 and RFC 1906 [RFC1906]. The third version of the message protocol 280 is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 281 [RFC2572] and RFC 2574 [RFC2574]. 283 o Protocol operations for accessing management information. The 284 first set of protocol operations and associated PDU formats is 285 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 286 operations and associated PDU formats is described in RFC 1905 287 [RFC1905]. 289 o A set of fundamental applications described in RFC 2573 [RFC2573] 290 and the view-based access control mechanism described in RFC 2575 291 [RFC2575]. 293 A more detailed introduction to the current SNMP Management Framework 294 can be found in RFC 2570 [RFC2570]. 296 Managed objects are accessed via a virtual information store, termed 297 the Management Information Base or MIB. Objects in the MIB are 298 defined using the mechanisms defined in the SMI. 300 This memo specifies a MIB module that is compliant to the SMIv2. A 301 MIB conforming to the SMIv1 can be produced through the appropriate 302 translations. The resulting translated MIB must be semantically 303 equivalent, except where objects or events are omitted because no 304 translation is possible (use of Counter64). Some machine readable 305 information in SMIv2 will be converted into textual descriptions in 306 SMIv1 during the translation process. However, this loss of machine 307 readable information is not considered to change the semantics of the 308 MIB. 310 1.5 Requirement Levels 312 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 313 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 314 document are to be interpreted as described in [RFC2119]. 316 Compliant implementations must follow this specification. 318 2. Printer Model 320 In order to accomplish the management of the printer, an abstract 321 model of the printer is needed to represent the sub-units from which 322 the printer is composed. A printer can be described as consisting of 323 13 types of sub-units. It is important to note that the sub-units of 324 a printer do not necessarily relate directly to any physically 325 identifiable mechanism. Sub-units can also be a set of definable 326 logical processes, such as interpreters for page description 327 languages or command processors that set various operating modes of 328 the printer. 330 Figure 2 shows a block diagram of the printer and its basic 13 sub- 331 units. 333 Figure 2 - Printer Block Diagram 335 Physical Connections 336 | 337 +-----------+ 338 | | 339 +-------------+ | 340 | Interface |-+ 341 | MIB-II | 342 +-------------+ 343 | 344 +-----------+ 345 | | 346 +-------------+ | +-----------+ 347 | Channel |-+ | Operator | 348 | | | Console | 349 +-------------+ +-----------+ 350 | 351 +-----------+ +---------+ 352 | | | | 353 +-----------+ +-------------+ | +-----------+ | 354 | General | | Interpreter |-+ | Alerts |-+ 355 | Printer | | | | | 356 +-----------+ +-------------+ +-----------+ 357 | 358 +-------------------------------+ 359 | System Controller | 360 | HOST-RESOURCES-MIB | 361 +-------------------------------+ 363 +------+ +--------+ +--------+ 364 | | | | | | 365 +-------+ | +-------+ +---------+ | +-------+ +--------+ | 366 | Input |-+ +--------+| | Marker |-+ +--------+| | Output |-+ 367 | |===>| |+<==>| |<==>| |+==>| | 368 +-------+ +--+ +--+ +---------+ +--+ +--+ +--------+ 369 \ | || | || \ 370 \ | || | || \ 371 \ | || | || \ 372 +--------+ | |+-------------------------| || +---------+ 373 | | | +--------------------------+ || | | 374 +----------+ | | Media Path |+ +----------+ | 375 | Media |-+ +--------------------------------+ | Finisher |-+ 376 |(optional)| |(optional)| 377 +----------+ +----------+ 378 2.1 Overview of the Printer Model 380 The model has three basic parts: (1) the flow of a print file into an 381 interpreter and onto the marker, (2) the flow of media through the 382 marker and (3) the auxiliary sub-units that control and facilitate 383 the two prior flows. The flow of the print data comes through a 384 physical connection on which some form of transport protocol stack is 385 running. The data provided by the transport protocol (interface) 386 appears on a channel, which is the input to an interpreter. The 387 interpreter converts the print data into a form suitable for marking 388 on the media. 390 The media resides in Input sub-units from which the media is selected 391 and then transported via a Media Path first to a Marking sub-unit and 392 then onto an Output sub-unit with (optionally) some finishing 393 operations being performed. The auxiliary sub-units facilitate 394 control of the printer, inquiry/control of the operator panel, 395 reporting of alerts and the adaptation of the printer to various 396 natural languages and characters sets. All the software sub-units run 397 on the System Controller that represents the processor, memory and 398 storage systems of the Printer. Each of the sub-units is discussed 399 in more detail below. 401 All of the sub-units other than the Alerts report only state 402 information, either a description or a status. The Alerts sub-unit 403 reports event information. 405 2.2 Printer Sub-Units 407 A printer is composed of 13 types of sub-units, called groups. The 408 following sections describe the different types of sub-units. 410 2.2.1 General Printer 412 The general printer sub-unit is responsible for the overall control 413 and status of the printer. There is exactly one general printer sub- 414 unit in a printer. The General Printer Group in the model represents 415 the general printer sub-unit. In addition to the providing the status 416 of the whole printer and allowing the printer to be reset, this Group 417 provides information on the status of the packaging of the printer, 418 in particular, the covers. The general printer sub-unit is usually 419 implemented on the system controller. 421 2.2.1.1 International Considerations 423 The localization portion of the general printer sub-unit is 424 responsible for identifying the natural language, country, and 425 character set in which certain character strings are expressed in 426 this MIB. Character sets are identified in this MIB using the 427 IANACharset textual convention imported from the IANA Character Set 428 MIB [CHARMIB]. 430 There may be one or more localizations supported per printer. The 431 available localizations are specified in the Localization table. 432 Localization SHOULD only be performed on string objects which are 433 named 'xxxDescription' (sub-unit descriptions) or 434 'prtConsoleDisplayBufferText' (local console text). 436 The agent SHALL return all other character strings in coded character 437 sets in which code positions 0-127 (decimal) are US-ASCII [ASCII]. 438 The agent SHOULD return all other character strings in the UTF-8 439 [RFC2279] transform of ISO 10646 [ISO10646], to conform with the IETF 440 Policy on Character Sets and Languages [RFC2277]. Control codes (code 441 positions 0-31 and 127 decimal) SHALL NOT be used unless specifically 442 required in the DESCRIPTION of an object. 444 The character set portion of the general printer Localization table 445 is responsible for identifying the possible character sets for the 446 operator console, and network management requests for display 447 objects. There may be one or more character sets per printer. Default 448 coded character sets for interpreter unit and output octets are 449 described in the interpreter sub-unit by 450 prtInterpreterDefaultCharSetIn and prtInterpreterDefaultCharSetOut. 451 These input/output character sets may be overridden by commands in 452 the interpreter language itself. 454 2.2.2 Inputs 456 Input sub-units are mechanisms that feed media to be marked on into 457 the printer. A printer contains one or more input sub-units. The 458 Input Group in the model represents these. The model does not 459 distinguish fixed input bins from removable trays, except to report 460 when a removable tray has been removed. 462 There are as many input sub-units as there are distinctly selectable 463 input "addresses". For example, if one tray has both a manual and 464 auto feeding option, then this is two input sub-units if these two 465 sources can be (must be) separately selected. However, the above 466 would be considered one input sub-unit if putting a sheet in the 467 manual feed slot overrides feeding from the contents of the tray. In 468 the second case there is no way to separately select or address the 469 manual feed slot. 471 2.2.3 Media 473 An input sub-unit can hold one or more instances of the media on 474 which marking is to be done. Typically, there is a large set of 475 possible media that can be associated with an input. The Media Group 476 is an extension of the Input Group, which represents media in an 477 input sub-unit. The Media Group only describes the current contents 478 of each input and not the possible content of the input sub-unit. 480 2.2.4 Outputs 482 Output sub-units are mechanisms that receive media that has been 483 marked on. The Output Group in the model represents the one or more 484 output mechanisms contained by a printer. The model does not 485 distinguish fixed output bins from removable output bins, except to 486 report when a removable bin has been removed. 488 There are as many output sub-units as there are distinctly selectable 489 output "addresses". Output sub-units can be addressed in two 490 different ways: (1) as a set of "mailboxes" which are addressed by a 491 specific mailbox selector such as a bin number or a bin name, or (2) 492 as a set of "slots" into which multiple copies are collated. 493 Sometimes both modes of using the output sub-units can be used on the 494 same printer. All that is important from the viewpoint of the model 495 is that the output units can be separately selected. 497 2.2.5 Finishers 499 A finisher is a sub-unit that performs some operations on the media 500 other than marking. The Finisher Group in the model represents the 501 finisher sub-units. Some examples of finishing processes are 502 stapling, punching, binding, inserting, or folding. Finishing 503 processes may have supplies associated with the process. Stapling, 504 binding, and punching are examples of processes that have supplies. A 505 printer may have more than one finishing sub-unit and each finishing 506 sub-unit may be associated with one or more output sub-units. 507 Finishers are described in the companion Finisher MIB [RFCnnnn]. 508 Note to RFC Editor: Insert RFC number 'nnnn' when assigned. 510 The model does not specify the exact interaction and sequencing 511 between an output device and its associated finisher. It depends on 512 the type of finishing process and the exact implementation of the 513 printer system. This standard allows for the logical association of a 514 finishing process with an output device but does not put any 515 restrictions on the exact sequence or interaction with the associated 516 output device. The output and finisher sub-units may or may not be 517 separate identifiable physical mechanisms depending on the exact 518 implementation of a printer. In addition, a single output device may 519 be associated with multiple finishing sub-units and a single 520 finishing sub-unit may be associated with multiple output devices. 522 2.2.6 Markers 524 A marker is the mechanism that produces marks on the print media. The 525 Marker Group in the model represents the marker sub-units and their 526 associated supplies. A printer can contain one or more marking 527 mechanisms. Some examples of multiple marker sub-units are a printer 528 with separate markers for normal and magnetic ink or an imagesetter 529 that can output to both a proofing device and final film. Each 530 marking device can have its own set of characteristics associated 531 with it, such as marking technology and resolution. 533 In this model the marker sub-unit is viewed as very generalized and 534 encompasses all aspects of a marking process. For example, in a 535 xerographic process, the marking process as well as the fusing 536 process would be included in the generalized concept of the marker. 537 With the generalized concept of a marking process, the concept of 538 multiple marking supplies associated with a single marking sub-unit 539 results. For example, in the xerographic process, there is not only a 540 supply of toner, but there can also be other supplies such as a fuser 541 supply (e.g., fuser oil) that can be consumed and replaced 542 separately. In addition there can be multiple supplies of toner for a 543 single marker device, as in a color process. 545 2.2.7 Media Paths 547 The media paths encompass the mechanisms in the printer that move the 548 media through the printer and connect all other media related sub- 549 units: inputs, outputs, markers and finishers. A printer contains one 550 or more media paths. The Media Path Group in the model represents 551 these. The Media Path group has some objects that apply to all paths 552 plus a table of the separate media paths. 554 In general, the design of the media paths determines the maximum 555 speed of the printer as well as the maximum media size that the 556 printer can handle. Media paths are complex mechanisms and can 557 contain many different identifiable sub-mechanisms such as media 558 movement devices, media buffers, duplex units and interlocks. Not all 559 of the various sub-mechanisms reside on every media path. For 560 example, one media path may provide printing only on one surface of 561 the media (a simplex path) and another media path may have a sub- 562 mechanism that turns the media over and feeds it a second time 563 through the marker sub-unit (a duplex path). The duplex path may 564 even have a buffer sub-mechanism that allows multiple copies of the 565 obverse side to be held before the reverse side of all the copies is 566 marked. 568 2.2.8 System Controller 570 The System Controller is the sub-unit upon which the software 571 components of the Printer run. The Host Resources MIB [RFC2790] 572 represents the System Controller in the model. The Host Resources MIB 573 allows for the specification of the processor(s), memory, disk 574 storage, file system and other underlying sub-mechanisms of the 575 printer. The controller can range from simple single processor 576 systems to multiprocessor systems. In addition, controllers can have 577 a full range of resources such as hard disks. The printer is modeled 578 to have one system controller even though it may have more than one 579 processor and multiple other resources associated with it. 581 2.2.9 Interfaces 583 An interface is the communications port and associated protocols that 584 are responsible for the transport of data to the printer. A printer 585 has one or more interface sub-units. The interfaces are represented 586 by the Interfaces Group of MIB-II [RFC1213], [RFC2863]. Some examples 587 of interfaces are serial ports (with little or no protocol) and 588 Ethernet ports on which one might run Internet IP, Novell IPX, etc. 590 2.2.10 Print Job Delivery Channels 592 The print job delivery channel sub-units identify the independent 593 sources of print data (here print data is the information that is 594 used to construct printed pages and may have both data and control 595 aspects). A printer may have one or more channels. The channel sub- 596 units are represented by the Print Job Delivery Channel Group in the 597 Model. The electronic path typically identifies each channel and 598 service protocol used to deliver print data to the printer. A channel 599 sub-unit may be independently enabled (allowing print data to flow) 600 or disabled (stopping the flow of print data). It has a current 601 Control Language that can be used to specify which interpreter is to 602 be used for the print data and to query and change environment 603 variables used by the interpreters (and SNMP). There is also a 604 default interpreter that is to be used if an interpreter is not 605 explicitly specified using the Control Language. Print Job Delivery 606 Channel sub-units can, and usually are, based on an underlying 607 interface. 609 2.2.11 Interpreters 611 The interpreter sub-units are responsible for the conversion of a 612 description of intended print instances into images that are to be 613 marked on the media. A printer may have one or more interpreters. The 614 Interpreter Group in the Model represents the interpreter sub-units. 615 Each interpreter is generally implemented with software running on 616 the System Controller sub-unit. The Interpreter Table has one entry 617 per interpreter where the interpreters include both Page Description 618 Language (PDL) Interpreters and Control Language Interpreters. 620 2.2.12 Console 622 Many printers have a console on the printer, the operator console 623 that is used to display and modify the state of the printer. The 624 console can be as simple as a few indicators and switches or as 625 complicated as full screen displays and keyboards. There can be at 626 most one such console. The Console Group in the model represents 627 this console sub-unit. Although most of the information displayed 628 there is also available in the state of the printer as represented by 629 the various Groups, it is useful to be able to query and modify the 630 operator console remotely. For example, a management application 631 might like to display to its user the current message on the operator 632 console of the remote printer or the management application user 633 might like to modify the current message on the operators console of 634 the remote printer. As another example, one might have a remote 635 application that puts up a pseudo console on a workstation screen. 636 Since the rules by which the printer state is mapped onto the console 637 and vice versa are not standardized, it is not possible to reproduce 638 the console state or the action of console buttons and menus. 639 Therefore, the Console Group provides access to the console. The 640 operator console is usually implemented on the system controller with 641 additional hardware for input and display. 643 2.2.13 Alerts 645 The alert sub-unit is responsible for detecting reportable events, 646 making an entry in the alert table and, if and only if the event is a 647 critical event, initiating a trap. The exception to this rule is when 648 the "alertRemovalofBinaryChangeEntry" trap is generated. The alert 649 sub-unit is represented by the Alerts Group and, in particular, the 650 Alert Table. This table contains information on the severity, sub- 651 unit, and detailed location within the sub-unit, alert code and 652 description of each alert that is currently active within the 653 printer. Each reportable event causes an entry to be made in the 654 Alert Table. 656 2.2.13.1 Status and Alerts 658 Summary information about the state of the printer is reported at 659 three separate levels: (1) The status of the printer as a whole is 660 reported in the Host Resources MIB, (2) The status of various sub- 661 units is reported in the principle table of the Group that represents 662 the sub-unit, and (3) Alert codes are reported in the Alert Table. 664 2.2.13.2 Overall Printer Status 666 Of the many states a printer can be in, certain states are more 667 "interesting" because of the distinct actions they are likely to 668 provoke in the administrator. These states may be applied to the 669 printer as a whole, or to a particular sub-unit of the printer. These 670 named states are: 672 Non Critical Alert Active - For the printer this means that one or 673 more sub-units have a non-critical alert active. For a sub-unit, 674 this means that the sub-unit has a non-critical alert active. 676 Critical Alert Active - For the printer this means that one or more 677 sub-units have a critical alert active. For a sub-unit, this means 678 that the sub-unit has a critical alert active. 680 Unavailable - The printer or sub-unit is unavailable for use (this is 681 the same as "broken" or "down" in other terminology). A trained 682 service person is typically necessary to make it available. 684 Moving on-line or off-line - The printer is either off-line, in the 685 process of moving off-line or moving back on-line. For example, on 686 printers with motorized hoppers, reloading paper involves a 687 transition to off-line to open the paper bin, filling the hopper and, 688 finally, a transition back to on-line as the paper bin is 689 repositioned for printing. 691 Standby - The printer or sub-unit is not immediately available but 692 can accept new instructions. 694 Available - The printer or subunit is functioning normally. 696 Idle - The printer or subunit is immediately available. 698 Active - The printer or subunit is performing its primary function. 700 Busy - The printer or subunit is performing a function (not 701 necessarily its primary function) and is not immediately available 702 for its primary function. 704 The Host Resources MIB [RFC2790] provides three status objects that 705 can be used to describe the status of a printer: (1) hrDeviceStatus 706 in the entry in the hrDeviceTable; (2) hrPrinterStatus in the 707 hrPrinterTable; and (3) hrPrinterDetectedErrorState in the 708 hrPrinterTable. These objects describe many of the states that a 709 printer can be in. The following table shows how the values of the 710 three printer-related objects in the Host Resources MIB relate to the 711 states named above: 713 Printer hrDeviceStatus hrPrinterStatus hrPrinterDetected- 714 Status ErrorState 716 Idle running(2) idle(3) none set 718 Busy/ running(2) printing(4) 719 Active 721 Non Critical warning(3) idle(3) or could be: lowPaper, 722 Alert Active printing(4) lowToner, or 723 serviceRequested 725 Critical down(5) other(1) could be: jammed, 726 Alert Active noPaper, noToner, 727 coverOpen, or 728 serviceRequested 730 Unavailable down(5) other(1) 732 Moving off- warning(3) idle(3) or offline 733 line printing(4) 734 Off-line down(5) other(1) offline 736 Moving down(5) warmup(5) 737 on-line 739 Standby running(2) other(1) 741 These named states are only a subset of the possible states - they 742 are not an exhaustive list of the possible states. Nevertheless, 743 several things should be noted. When using these states, it is not 744 possible to detect when both critical and non-critical alerts are 745 pending - if both are pending, the Critical Alert Active state will 746 prevail. In addition, a printer in the Standby state will be 747 represented in the Host Resources MIB with a device status of 748 running(2) and a printer status of other(1), a set of states that 749 don't uniquely distinguish this important printer state. 751 Detailed status per sub-unit is reported in the sub-unit status 752 fields. 754 2.2.13.2.1 Host Resources MIB Printer Status 756 For completeness, the definitions of the Printer Status objects of 757 the Host Resources MIB [RFC2790] are given below: 759 hrDeviceStatus OBJECT-TYPE 760 SYNTAX INTEGER { 761 unknown(1), 762 running(2), 763 warning(3), 764 testing(4), 765 down(5) 766 } 767 ACCESS read-only 768 STATUS mandatory 769 DESCRIPTION 770 "The current operational state of the device 771 described by this row of the table. A value 772 unknown(1) indicates that the current state of the 773 device is unknown. running(2) indicates that the 774 device is up and running and that no unusual error 775 conditions are known. The warning(3) state 776 indicates that agent has been informed of an 777 unusual error condition by the operational software 778 (e.g., a disk device driver) but that the device 779 is still 'operational'. An example would be high 780 number of soft errors on a disk. A value of 781 testing(4), indicates that the device is not 782 available for use because it is in the testing 783 state. The state of down(5) is used only when 784 the agent has been informed that the device is 785 not available for any use." 786 ::= { hrDeviceEntry 5 } 788 hrPrinterStatus OBJECT-TYPE 789 SYNTAX INTEGER { 790 other(1), 791 unknown(2), 792 idle(3), 793 printing(4), 794 warmup(5) 795 } 796 ACCESS read-only 797 STATUS mandatory 798 DESCRIPTION 799 "The current status of this printer device. When in the 800 idle(3), printing(4), or warmup(5) state, the corresponding 801 hrDeviceStatus should be running(2) or warning(3). When in 802 the unknown(2) state, the corresponding hrDeviceStatus 803 should be unknown(1)." 804 ::= { hrPrinterEntry 1 } 806 hrPrinterDetectedErrorState OBJECT-TYPE 807 SYNTAX OCTET STRING (0..128) 808 ACCESS read-only 809 STATUS mandatory 810 DESCRIPTION 811 "This object represents any error conditions detected by the 812 printer. The error conditions are encoded as an OCTET STRING 813 with the following definitions: 815 Condition Bit # 817 lowPaper 0 818 noPaper 1 819 lowToner 2 820 noToner 3 821 doorOpen 4 822 jammed 5 823 offline 6 824 serviceRequested 7 826 inputTrayMissing 8 827 outputTrayMissing 9 828 markerSupplyMissing 10 829 outputNearFull 11 830 outputFull 12 831 inputTrayEmpty 13 832 overduePreventMaint 14 834 Bit # 15 is not assigned. 835 If multiple conditions are currently detected and the 836 hrDeviceStatus would not otherwise be unknown(1) or 837 testing(4), the hrDeviceStatus shall correspond to the worst 838 state of those indicated, where down(5) is worse than 839 warning(3), which is worse than running(2). 841 Bits are numbered starting with the most significant bit of 842 the first byte being bit 0, the least significant bit of the 843 first byte being bit 7, the most significant bit of the 844 second byte being bit 8, and so on. A one bit encodes that 845 the condition was detected, while a zero bit encodes that 846 the condition was not detected. 848 This object is useful for alerting an operator to specific 849 warning or error conditions that may occur, especially those 850 requiring human intervention." 852 ::= { hrPrinterEntry 2 } 854 2.2.13.2.2 Sub-unit Status 856 Sub-unit status is reported in the entries of the principle table in 857 the Group that represents the sub-unit. For sub-units that report a 858 status, there is a status column in the table and the value of this 859 column is always an integer formed in the following way. 861 The SubUnitStatus is an integer that is the sum of 5 distinct values, 862 Availability, Non-Critical, Critical, On-line, and Transitioning. 863 These values are: 865 Availability value 867 Available and Idle 0 000'b 868 Available and Standby 2 010'b 869 Available and Active 4 100'b 870 Available and Busy 6 110'b 871 Unavailable and OnRequest 1 001'b 872 Unavailable because Broken 3 011'b 873 Unknown 5 101'b 875 Non-Critical 877 No Non-Critical Alerts 0 878 Non-Critical Alerts 8 880 Critical 882 No Critical Alerts 0 883 Critical Alerts 16 885 On-Line 887 State is On-Line 0 888 State is Off-Line 32 890 Transitioning 892 At intended state 0 893 Transitioning to intended state 64 895 For example, an input (tray) that jammed on the next to the last page 896 may show a status of 27 (unavailable because broken (3) + a critical 897 state (16), jammed, and a noncritical state (8), low paper). 899 2.2.13.3 Alert Tables 901 The Alert Group consists of a single table in which all active alerts 902 are represented. This section provides an overview of the table and 903 a description of how it is managed. The basic content of the alert 904 table is the severity (critical or non-critical) of the alert, the 905 Group and entry where a state change caused the alert, additional 906 information about the alert (a more detailed location, an alert code, 907 and a description), and an indication of the level of training needed 908 to service the alert. 910 The Alert Table contains some information that is redundant, for 911 example that an event has occurred, and some information that is only 912 represented in the Alert Table, for example the additional 913 information. A single table was used because a single entry in a 914 group could cause more than one alert, for example paper jams in more 915 than one place in a media path. Associating the additional 916 information with the entry in the affected group would only allow one 917 report where associating the additional information with the alert 918 makes multiple reports possible. Every time an alert occurs in the 919 printer, the printer makes one or more entries into the Alert Table. 920 The printer determines if an event is to be classified as critical or 921 non-critical. If the severity of the Alert is "critical", the printer 922 sends a trap or event notification to the host indicating that the 923 table has changed. Whether or not a trap is sent, the management 924 application is expected to poll the printer on a regular basis and to 925 read and parse the table to determine what conditions have changed, 926 in order to provide reliable information to the management 927 application user. 929 2.2.13.4 Alert Table Management 931 The alert tables are sparsely populated tables. This means the tables 932 will only contain entries of the alerts that are currently active and 933 the number of rows, or entries in the table will be dynamic. More 934 than one event can be added or removed from the event tables at a 935 time depending on the implementation of the printer. 937 There are basically two kinds of events that produce alerts: binary 938 change events and unary change events. Binary change events come in 939 pairs: the leading edge event and the trailing edge event. The 940 leading edge event enters a state from which there is only one exit; 941 for example, going from running to stopped with a paper jam. The only 942 exit from this state is fixing the paper jam and it is clear when 943 that is accomplished. The trailing edge event exits the state that 944 was entered by the leading edge event. In the example above, fixing 945 the paper jam is the trailing edge event. 947 It is relatively straightforward to manage binary change events in 948 the Alert Table. Only the leading edge event makes an entry in the 949 alert table. This entry persists in the Alert Table until the 950 trailing edge event occurs at which point this event is signaled by 951 the removal of the leading edge event entry in the Alert Table. That 952 is, a trailing edge event does not create an entry; it removes the 953 corresponding leading edge event. Removing the leading edge entry may 954 cause the unary change event "alertRemovalofBinaryChangeEntry" to be 955 added to the table. With binary change events it is possible to 956 compute the maximum number that can occur at the same time and 957 construct an Alert Table that would hold that many events. There 958 would be no possibility of table overflow and no information about 959 outstanding events would be lost. 961 Unfortunately, there are some events that are not binary changes. 962 This other category of event, the unary change event, is illustrated 963 by the configuration change event. With this kind of event the state 964 of the machine has changed, but to a state which is (often) just as 965 valid as the state that was left and from which no return is 966 necessary. For example, an operator may change the paper that is in 967 the primary input source from letter to legal. At some time in the 968 future the paper may be changed back to letter, but it might be 969 changed to executive instead. This is where the problem occurs. It 970 is not obvious how long to keep unary change event entries in the 971 Alert Table. If they were never removed, the Alert Table would 972 continue to grow indefinitely. 974 The agent needs to have an algorithm implemented for the management 975 of the alert table, especially in the face of combinations of binary 976 and unary alerts that would overflow the storage capacity of the 977 table. When the table is full and new alerts need to be added, an 978 old alert to be deleted should be chosen using the following rules: 980 1. Find a non-critical unary alert and delete it. If there are 981 multiple non-critical unary alerts, it is suggested that the oldest 982 one is chosen. If there are no non-critical unary alerts, then, 984 2. Find a non-critical binary alert and delete it. If there are 985 multiple non-critical binary alerts, it is suggested that the oldest 986 one is chosen. If there are no non-critical binary alerts, then, 987 3. Find a critical (binary) alert and delete it. If there are 988 multiple critical alerts, it is suggested that the oldest one be 989 chosen. Agent implementers are encouraged to provide at least enough 990 storage space for the maximum number of critical alerts that could 991 occur simultaneously. Note that all critical alerts are binary. 993 In the event that a critical binary alert has been deleted out of the 994 alert table; when space allows and the alert condition still exists, 995 the alert should be re-added to the alert table even if there was no 996 subsequent transition into the associated state. It is recommended 997 that this be done for non-critical binary alerts as well. Note that 998 the new alert entry will not have the same index as the original 999 entry that was moved out of the table. 1001 Note that because the Alert Index is a monotonically increasing 1002 integer there will be gaps in the values in the table when an alert 1003 is deleted. The management application may want to re-acquire the 1004 Printer state and check for state changes that it did not observe in 1005 the Alert Table if such gaps are detected. 1007 2.3 Read-Write Objects 1009 Some objects in the printer MIB reflect the existence or amount of a 1010 given resource within the printer. Some examples of such resources 1011 are the size and number of sheets in a paper tray or the existence of 1012 certain output options. Some printers have automatic sensors for 1013 these resources. Most printers lack sensors for every property of 1014 every resource. The management application is allowed to write into 1015 objects that hold descriptive or existence values for printers that 1016 cannot sense these values. The ability to change the value of a read- 1017 write object may depend on the implementation of the agent. Many 1018 objects in the MIB are given read-write access, but a printer 1019 implementation might only permit a management application to change 1020 the value if the printer can not sense the value itself. Note that 1021 even though some objects explicitly state the behavior of conditional 1022 ability to change values, any read-write object may act this way. 1024 Generally, an object is given read-write access in the Printer MIB 1025 specification if: 1027 1. The object involves installation of a resource that some printers 1028 cannot themselves detect. Therefore, external means are needed to 1029 inform the printer of the installation. (Here external means include 1030 using the operator console, or remote management application) and 1031 2. The printer will behave differently if the installation of the 1032 resource is reported than the printer would if the installation were 1033 not reported; that is, the object is not to be used as a place to put 1034 information not used by the printer, i.e., not a "sticky-note". 1035 Another way of saying this is that the printer believes that 1036 information given it and acts as if the information were true. For 1037 example, on a printer that cannot sense the size, if one paper size 1038 is loaded, but another size is set into the paper size object, then 1039 the printer will use the size that was set as its current paper size 1040 in its imaging and paper handling. 1042 3. The printer may get hints that it may not know about the existence 1043 or properties of certain resources. For example, a paper tray may be 1044 removed and re-inserted. When this removal and insertion happens, 1045 the printer may either assume that a property, such as the size of 1046 paper in the tray, has not changed or the printer may change the 1047 value of the associated object to "unknown", as might be done for the 1048 amount of paper in the tray. As long as the printer acts according 1049 to the value in the object either strategy is acceptable. 1051 4. It is an implementation-specific matter as to whether or not MIB 1052 object values are persistent across power cycles or cold starts. It 1053 is particularly important that the values of the prtMarkerLifeCount 1054 object persist throughout the lifetime of the printer. Therefore, if 1055 the value of any MIB object persists across power cycles, then the 1056 prtMarkerLifeCount object must also persist. 1058 2.4 Enumerations 1060 Enumerations (enums) are sets of symbolic values defined for use with 1061 one or more objects. Some common enumeration sets are assigned a 1062 symbolic data type name (textual convention). These enumerations are 1063 listed at the beginning of this specification. All of the 1064 enumerations in the Printer MIB which are defined in textual 1065 conventions are: 1067 a) used more than once in the Printer MIB itself; or 1069 b) imported and used in the companion Finisher MIB; or 1071 c) imported and used in vendor private MIBs. 1073 The Printer MIB also has defined the following enumeration set for 1074 use with objects of the syntax "Integer32", to define conditions that 1075 are outside of the normal numeric range; other(-1) and unknown(-2). 1076 The Integer32 range field indicates in which objects these 1077 enumeration values are valid. 1079 2.4.1 Registering Additional Enumerated Values 1081 This working group has defined several type of enumerations. These 1082 enumerations differ in the method employed to control the addition of 1083 new enumerations. Throughout this document, references to 1084 "enumeration (n)", where n can be 1, 2 or 3 can be found in the 1085 various tables. The definitions of these types of enumerations are: 1087 enumeration (1) All the values are defined in the Printer MIB 1088 specification (RFC for the Printer MIB). Additional enumerated 1089 values require a new RFC. 1091 enumeration (2) An initial set of values are defined in the 1092 Printer MIB specification. Additional enumerated values are 1093 registered after review by this working group. The initial 1094 versions of the MIB will contain the values registered so far. 1095 After the MIB is approved, additional values will be registered 1096 through IANA after approval by this working group. 1098 enumeration (3) An initial set of values are defined in the 1099 Printer MIB specification. Additional enumerated values are 1100 registered without working group review. The initial versions of 1101 the MIB will contain the values registered so far. After the MIB 1102 is approved, additional values will be registered through IANA 1103 without approval by this working group. 1105 3. Groups from other MIB Specifications 1107 This section identifies the groups from other MIBs that shall be 1108 supported to supplement and complete a printer MIB implementation. 1109 The section also describes some of the less obvious characteristics 1110 of the Printer MIB structure that are related to the inclusion of 1111 these other MIB groups. 1113 3.1 System Group 1115 All objects in the system group of MIB-II [RFC1213] shall be 1116 implemented; however, as described in paragraph 2.4, implementers 1117 should carefully consider what constitutes the "system". 1119 3.2 System Controller 1121 The storage and device groups of the Host Resources MIB [RFC2790] 1122 shall be implemented to support the printer(s) system controller, and 1123 any supporting devices. If deemed appropriate by the implementer, 1124 other groups of the Host Resources MIB (System, Running Software, 1125 Running Software Performance, and Installed Software) may be 1126 implemented. 1127 Because of the structure of the Host Resources MIB, the devices 1128 constituting the system controller are at the same level as the 1129 printer. 1131 3.3 Interface Group objects 1133 All objects in the Interfaces Group of MIB-II [RFC1213] shall be 1134 implemented for all print information interfaces to the printer, 1135 including non-network interfaces. 1137 3.3.1 Interface Types 1139 The interfaces group of RFC 1213 [RFC1213] contains only a partial 1140 list of interface types that can be specified in the "ifType" object. 1141 For a complete list of interface types, refer to the IANA registry at 1142 "ftp://ftp.isi.edu/mib/iana.mib/ianaiftype.mib" 1144 4. Differences from RFC 1759 1146 This document supercedes and replaces RFC 1759. However, a compliant 1147 implementation of RFC 1759 is also compliant with this document. The 1148 following changes to RFC 1759 are included: 1150 - Minor editorial corrections and changes. Updated the cover page 1151 and added the "SNMP Management Framework" boilerplate to section 1. 1153 - Updated figure 2 to use MIB names instead of RFC numbers. 1155 - Updated Coded Character Set description and IANA registration 1156 process. 1158 - Change hrPrinterDetectedErrorState "coverOpen" (bit 4) to 1159 "doorOpen" per RFC 2790. 1161 - Added second octet of hrPrinterDetectedErrorState as partially 1162 described and assigned in the updated Host Resources MIB (RFC 2790). 1164 - Remove fixed association of hrDeviceStatus (warning/down) from 1165 hrPrinterDetetctedErrorState per RFC 2790. 1167 - Instead of showing bit 15 as "not assigned" in the quote from RFC 1168 2790 in the hrPrinterDetectedErrorState object, removed that from the 1169 tabular form and added it as a sentence, because the RFC doesn't show 1170 bit 15 in the tabular form. 1172 - Clarified the international considerations. 1174 - Added prtChannelInformation to the Channel Group textual- 1175 conventions on a per channel basis to clarify the channel description 1176 and enhance interoperability. 1178 - Deprecated some obsolete channel types. 1180 - Extended the Alert Table and PrtMarkerSuppliesSupplyUnit textual 1181 conventions to include values from the Finisher MIB. 1183 - Clarified alerts based on unary vs. binary change events. 1185 - Added (optional) unary change event 1186 alertRemovalOfBinaryChangeEntry(1801). 1188 - Establish a convention for contact information for 1189 prtGeneralCurrentOperator and prtGeneralServicePerson. 1191 - Added prtAuxiliarySheetStartupPage PresentOnOff 1193 - Added prtAuxiliarySheetBannerPage PresentOnOff 1195 - Added prtGeneralPrinterName OCTET STRING 1197 - Added prtGeneralSerialNumber OCTET STRING 1199 - Added prtInputNextIndex Integer32 1201 - Added the Input Switching Group 1203 - Added prtAlertCriticalEvents Counter32 1205 - Added prtAlertAllEvents Counter32 1207 - Updated PrtAlertCode enums including generic alert codes. 1209 - Created five OBJECT-GROUPs (prtAuxilliarySheetGroup, 1210 prtInputSwitchingGroup, prtGeneralV2Group, prtAlertTableV2Group, 1211 prtChannelV2Group). Added the nine new objects to them 1212 (prtAuxiliarySheetStartupPage, prtAuxiliarySheetBannerPage, 1213 prtGeneralPrinterName, prtGeneralSerialNumber, 1214 prtAlertCriticalEvents, prtAlertAllEvents, prtInputMediaLoadTimeout, 1215 prtInputNextIndex, prtChannelInformation). Created one new 1216 NOTIFICATION-GROUP (prtAlertTrapGroup) to contain printerV2Alert. 1217 Included the new OBJECT-GROUPs and the NOTIFICATION_GROUP in 1218 prtMIBCompliance, all in GROUP (not MANDATORY-GROUP) clauses. The 1219 nine new objects are optional, i.e., this draft is backward 1220 compatible with RFC 1759. 1222 - prtAlertTime is strongly recommended. 1224 - Deprecated the use of alert codes doorOpen(501) and 1225 doorClosed(502), in favor of coverOpened(3) and coverClosed(4). 1227 - Added the PrtConsoleDisableTC and PrtMarkerAddressabilityUnitTC 1228 textual conventions, and changed the PrtConsoleDisable and 1229 PrtMarkerAddressabilityUnit objects' syntax to use those TCs, and 1230 changed the PrtGeneralEntry and PrtMarkerColorantEntry SEQUENCEs to 1231 reflect the new syntax. 1233 - Added textual conventions "PrtLocalizedDescriptionStringTC" and 1234 "PrtConsoleDescriptionStringTC" and updated several objects to use 1235 them. 1237 - Changed most enumerations to textual conventions and therefore 1238 changed the SYNTAX of many objects from RFC 1759 to specify the 1239 appropriate textual conventions. (28 TCs were added.) 1241 - Changed the TC names "MediaUnit" to "PrtMediaUnitTC", 1242 "CapacityUnit" to "PrtCapacityUnitTC", and "SubUnitStatus" to 1243 "PrtSubUnitStatusTC" 1245 - All objects with a MAX-ACCESS of read-write now have a MIN-ACCESS 1246 of read-only. 1248 - Added 'IANA Considerations' and 'Internationalization 1249 Considerations' as top level sections, per IETF guidelines. 1251 - Updated Security and Copyright sections. 1253 - Updated references. 1255 - Added Appendix E - Overall Printer Status Table. 1257 - Updated participant and contact information. 1259 - Removed CodedCharSet Textual Convention, replaced with an import of 1260 the IANACharset. 1262 - Removed all comment statements that indicated objects or groups are 1263 mandatory or optional. Avoids any potential conflicts with the 1264 conformance section. 1266 - Added text to empty description clauses. (prtStorageRefTable, 1267 prtDeviceRefTable, prtMarkerTable, prtMediaPathTable, 1268 prtChannelTable, prtInterpreterTable, prtConsoleLightTable, and 1269 prtAlertTable) 1271 - Added "DEFVAL { unknown }" to prtInterpreterDefaultCharSetIn and 1272 prtInterpreterDefaultCharSetOut. 1274 - Changed "...values are expected to remain stable..." to "...values 1275 SHOULD remain stable..." in the description clauses for the index 1276 object in all tables. 1278 - Added ranges to all objects with a syntax of Integer32. 1280 - Revised the description clause for prtAlertGroupIndex. 1282 - Added additional text to the description clause for 1283 prtMediaPathEntry, prtChannelEntry, prtInterpreterEntry, and 1284 printerV2Alert. 1286 - Added text to section 2.4 to explain the usage of textual 1287 conventions in this MIB and others. Also added a note defining the 1288 common usage of the enumerations 'other(-1)' and 'unknown(-2)' 1290 - Changed range of prtStorageRefSeqNumber, prtDeviceRefSeqNumber, and 1291 prtConsoleLightIndex from (0..65535) to (1..65535) since index values 1292 cannot be zero. (Typo in RFC 1759) 1294 - The PWG Standard for Standardized Media Names is now recommended 1295 for the objects prtInputMediaName, prtInputMediaColor, and 1296 prtInputMediaType. 1298 - Added chSMTP(45) to prtChannelTypeTC. 1300 5. The IANA Printer MIB 1302 IANA-PRINTER-MIB DEFINITIONS ::= BEGIN 1304 IMPORTS 1305 MODULE-IDENTITY, 1306 mib-2 1307 FROM SNMPv2-SMI 1308 TEXTUAL-CONVENTION 1309 FROM SNMPv2-TC; 1311 ianaPrinter MODULE-IDENTITY 1312 LAST-UPDATED "200210080000Z" -- October 8, 2002 1313 ORGANIZATION "IANA" 1314 CONTACT-INFO "Internet Assigned Numbers Authority 1316 Postal: ICANN 1317 4676 Admiralty Way, Suite 330 1318 Marina del Rey, CA 90292 1320 Tel: +1 310 823 9358 1321 E-Mail: iana@iana.org" 1323 DESCRIPTION "The Printer MIB defines three categories of textual 1324 Conventions: 1325 Type 1 TCs are defined within the MIB specification 1326 and new values can be defined only by publishing a new 1327 version of the RFC. 1328 Type 2 TCs require approval by the Working Group 1329 for any additional values. 1330 Type 3 TCs may be extended without the approval of 1331 the Working Group. 1333 This MIB module defines IANA-maintained textual 1334 conventions that are imported by the Printer MIB." 1336 -- revision history 1338 REVISION "200210080000Z" -- October 8, 2002 1339 DESCRIPTION "Original version transferred from Printer MIB." 1341 ::= { mib-2 998 } -- [[to be assigned by IANA - standards track]] 1343 -- 1344 -- Generic textual conventions 1345 -- 1347 PrtCoverStatusTC ::= TEXTUAL-CONVENTION 1348 -- This is a type 2 enumeration. This TC was extracted from 1349 -- prtCoverStatus in RFC 1759. "coverOpen" and "coverClosed" in 1350 -- this MIB version were "doorOpen" and "doorClosed" in RFC 1759. 1351 -- A name change is not formally allowed in SNMP, but was agreed 1352 -- to by the WG group since a door has a more restrictive meaning 1353 -- than a cover and Cover group is intended to support doors as a 1354 -- subset of covers. 1355 STATUS current 1356 DESCRIPTION 1357 "Values for encoding the state of a particular cover or 1358 access panel on the printer case or enclosure." 1359 SYNTAX INTEGER { 1360 other(1), 1361 coverOpen(3), 1362 coverClosed(4), 1363 interlockOpen(5), 1364 interlockClosed(6) 1365 } 1367 -- 1368 -- General Group textual conventions 1369 -- 1371 PrtGeneralResetTC ::= TEXTUAL-CONVENTION 1372 -- This is a type 3 enumeration. This TC was extracted from 1373 -- prtGeneralReset in RFC 1759. 1374 STATUS current 1375 DESCRIPTION 1376 "Values for reading and writing the prtGeneralReset object. 1378 If a device does not have NVRAM, the device shall none the 1379 less respond to a SET with the value resetToNVRAM(5) with a 1380 sort of warm reset that resets the device to implementation- 1381 defined state that is preferably under control of the system 1382 administrator by some means outside the scope of the Printer 1383 MIB specification." 1385 SYNTAX INTEGER { 1386 notResetting(3), 1387 powerCycleReset(4), -- Cold Start 1388 resetToNVRAM(5), -- Warm Start 1389 resetToFactoryDefaults(6) -- Reset contents of 1390 -- NVRAM to factory 1391 -- defaults 1392 } 1394 -- 1395 -- Channel Group textual conventions 1396 -- 1398 PrtChannelTypeTC ::= TEXTUAL-CONVENTION 1399 -- This is a type 2 enumeration. This TC was extracted from 1400 -- prtChannelType in RFC 1759. 1401 STATUS current 1402 DESCRIPTION 1403 "This enumeration indicates the type of channel that is 1404 receiving jobs." 1405 SYNTAX INTEGER { 1406 other(1), 1407 chSerialPort(3), 1408 chParallelPort(4), 1409 chIEEE1284Port(5), 1410 chSCSIPort(6), 1411 chAppleTalkPAP(7), 1412 -- AppleTalk Printer 1413 -- Access Protocol (PAP) 1414 -- 1415 -- prtChannelInformation entry: 1416 -- 1417 -- Printer Name 1418 -- Keyword: Name 1419 -- Syntax: Name 1420 -- Status: Optional 1421 -- Multiplicity: Single 1422 -- Description: The name of the printer 1423 -- within the AppleTalk naming scope 1424 chLPDServer(8), 1425 -- prtChannelInformation entry: 1426 -- 1427 -- Printer queue name 1428 -- Keyword: Queue 1429 -- Syntax: Name 1430 -- Status: Mandatory 1431 -- Multiplicity: Single 1432 -- Description: queue name as 1433 -- defined in [RFC1179]. 1435 chNetwareRPrinter(9), 1436 -- Novell, Inc. 1437 -- For each entry of this type, the 1438 -- prtChannelInformation must have a pair of 1439 -- keywords. For Netware 3.x channels this must 1440 -- be a (PServer, Printer) pair. For Netware 1441 -- 4.x channels and for IntranetWare channels 1442 -- this must be a (NDSTree, NDSPrinter) pair. 1443 -- 1444 -- prtChannelInformation entries: 1446 -- Print Server Name 1447 -- Keyword: PServer 1448 -- Syntax: Name 1449 -- Status: Mandatory 1450 -- Multiplicity: Single 1451 -- Description: The Pserver's SAP name 1452 -- 1453 -- Printer Number 1454 -- Keyword: Printer 1455 -- Syntax: Integer 1456 -- Status: Mandatory 1457 -- Multiplicity: Single 1458 -- Description: The printer number 1459 -- 1460 -- NDSTree 1461 -- Keyword: NDSTree 1462 -- Syntax: Name 1463 -- Multiplicity: Single 1464 -- Description: The tree's SAP name 1465 -- 1466 -- NDS Printer object 1467 -- Keyword: NDSPrinter 1468 -- Syntax: Text (Unicode) 1469 -- Status: Mandatory 1470 -- Multiplicity: Single 1471 -- Description: The fully qualified 1472 -- name of the Printer 1473 -- 1474 -- In the Netware 3.x environment, the 1475 -- client checks the Bindery object 1476 -- representing the named PServer. The 1477 -- client then checks for queues which 1478 -- are associated with the numbered 1479 -- printer. In the 4.x and IntraNetware 1480 -- environment, the client looks up the 1481 -- queues which are associated with the 1482 -- NDS Printer Object in the named Tree. 1483 -- Depending on client access rights to 1484 -- those queues, the client submits jobs 1485 -- to the appropriate queue. 1486 chNetwarePServer(10), 1487 -- Novell,Inc. 1488 -- For each entry of this type, the 1489 -- prtChannelInformation must have a pair 1490 -- of keywords. For Netware 3.x channels 1491 -- this must be a (Server, PServer) pair. 1492 -- For Netware 4.x and IntranetWare 1493 -- channels, this must be a 1494 -- (NDSTree, NDSPServer) pair. 1495 -- 1496 -- prtChannelInformation entries: 1497 -- 1498 -- Server Name 1499 -- Keyword: Server 1500 -- Syntax: Name 1501 -- Status: Mandatory 1502 -- Multiplicity: Single 1503 -- Description: The SAP name of the 1504 -- server for which the PServer is defined. 1505 -- 1506 -- PServer 1507 -- Keyword: PServer 1508 -- Syntax: Name 1509 -- Status: Mandatory 1510 -- Multiplicity: Single 1511 -- Description: The bindery name of 1512 -- the PServer 1513 -- 1514 -- NDS Tree 1515 -- Keyword: NDSTree 1516 -- Syntax: Name 1517 -- Status: Mandatory 1518 -- Multiplicity: Single 1519 -- Description: The NDS Tree name 1520 -- 1521 -- PServer 1522 -- Keyword: NDSPServer 1523 -- Syntax: Text (Unicode) 1524 -- Status: Mandatory 1525 -- Multiplicity: Single 1526 -- Description: The fully qualified 1527 -- name of the PServer object in the tree. 1528 -- 1529 -- In the 3.x environment, the client 1530 -- checks the bindery object 1531 -- representing the named PServer on the 1532 -- named Server. In the 4.x and 1533 -- IntranetWare environment, 1534 -- the client checks the NDS object 1535 -- representing the named PServer in the 1536 -- named Tree. In either case, the 1537 -- client then checks for all queues 1538 -- associated with the Pserver object. 1539 -- Depending on client access rights 1540 -- to those queues, the client submits 1541 -- jobs to the appropriate queue. 1542 chPort9100(11), 1543 -- DEPRECATED 1544 -- (see chPortTCP - 37; chBidirPortTCP - 38) 1545 chAppSocket(12), 1546 -- A bi-directional, LPD-like, protocol using 1547 -- 9101 for control and 9100 for data. 1548 -- Adobe Systems, Inc. 1549 chFTP(13), -- [RFC959] 1550 chTFTP(14), -- [RFC1350] 1551 chDLCLLCPort(15), 1552 chIBM3270(16), -- IBM Coax 1553 chIBM5250(17), -- IBM Twinax 1554 chFax(18), 1555 chIEEE1394(19), 1556 chTransport1(20), 1557 -- TCP port 35, for reserved TCP port list see 1558 -- [RFC3232]. This RFC should also be 1559 -- referenced for other channel 1560 -- enumerations utilizing TCP port 1561 -- numbers 0 through 1024. 1562 chCPAP(21), -- TCP port 170 1563 -- Digital Equipment Corp. 1564 chDCERemoteProcCall(22), -- OSF 1565 -- DEPRECATED 1566 chONCRemoteProcCall(23), -- SUN Microsystems 1567 -- DEPRECATED 1568 chOLE(24), -- Microsoft 1569 -- DEPRECATED 1571 chNamedPipe(25), 1572 chPCPrint(26), -- Banyan 1573 chServerMessageBlock(27), 1574 -- File/Print sharing protocol used by 1575 -- various network operating systems 1576 -- from IBM 3Com, Microsoft and others 1577 -- 1578 -- prtChannelInformation entry: 1579 -- 1580 -- Service Name 1581 -- Keyword: Name 1582 -- Syntax: Name 1583 -- Status: Optional 1584 -- Multiplicity: Single 1585 -- Description: The service name of 1586 -- the printer 1587 chDPMF(28), -- IBM Infoprint 1588 chDLLAPI(29), -- Microsoft 1589 -- DEPRECATED 1590 chVxDAPI(30), -- Microsoft 1591 -- DEPRECATED 1592 chSystemObjectManager(31), -- IBM 1593 chDECLAT(32), 1594 -- Digital Equipment Corp. 1595 -- 1596 -- prtChannelInformation entries: 1597 -- 1598 -- Port Name 1599 -- Keyword: Port 1600 -- Syntax: Name 1601 -- Status: Conditionally 1602 -- Mandatory 1603 -- (see note below) 1604 -- Multiplicity: Single 1605 -- Description: LAT port name 1606 -- 1607 -- Service Name 1608 -- Keyword: Service 1609 -- Syntax: Name 1610 -- Status: Conditionally 1611 -- Mandatory 1612 -- Multiplicity: Single 1613 -- Description: LAT service name 1614 -- 1615 -- The LAT channel may be 1616 -- identified by either a port or 1617 -- service, so either a 1618 -- Port or Service entry must be 1619 -- specified, but not both. 1620 chNPAP(33), 1621 chUSB(34), -- Not in RFC 1759 1622 -- Universal Serial Bus 1623 chIRDA(35), -- Not in RFC 1759 1624 -- Infrared Data Assoc. Prot. 1625 chPrintXChange(36), -- Not in RFC 1759 1626 -- PrintXChange Protocol 1627 chPortTCP(37), -- Not in RFC 1759 1628 -- A unidirectional "raw" TCP 1629 -- channel that uses an administratively 1630 -- assigned TCP port address. 1631 -- 1632 -- prtChannelInformation entry: 1633 -- 1634 -- Port Number 1635 -- Keyword: Port 1636 -- Syntax: decimal number 1637 -- Status: Mandatory 1638 -- Multiplicity: Single 1639 -- Description: TCP port number 1640 chBidirPortTCP(38), -- Not in RFC 1759 1641 -- A bi-directional version of chPortTCP 1642 -- 1643 -- prtChannelInformation entries: 1644 -- (See chPortTCP) 1645 chUNPP(39), -- Not in RFC 1759 1646 -- Universal Network Printing 1647 -- Protocol(UNPP). A bi-directional, 1648 -- multiport network printing 1649 -- application protocol available on 1650 -- multiple transport protocols. 1651 -- Underscore, Inc. 1652 -- Contact: info@underscore.com 1653 chAppleTalkADSP(40), -- Not in RFC 1759 1654 -- AppleTalk Data Stream Protocol. 1655 -- ADSP is part of the AppleTalk 1656 -- suite of protocols. 1657 -- It is a symmetric, connection- 1658 -- oriented protocol that makes 1659 -- possible the establishment 1660 -- and maintenance of full-duplex 1661 -- streams of data bytes between 1662 -- two sockets in an AppleTalk 1663 -- internet. 1664 -- See [APPLEMAC]. 1665 chPortSPX(41), -- Not in RFC 1759 1666 -- Sequenced Packet Exchange (SPX) 1667 -- socket. 1668 -- Novell, Inc. Similar to TCP, a 1669 -- bi-directional data pipe using 1670 -- Novell SPX as a transport. 1671 -- 1672 -- prtChannelInformation entries: 1673 -- 1674 -- Network Number 1675 -- Keyword: Net 1676 -- Syntax: HexString 1677 -- Status: Mandatory 1678 -- Multiplicity: Single 1679 -- Description: The network number 1680 -- 1681 -- Node Number 1682 -- Keyword: Node 1683 -- Syntax: HexString 1684 -- Status: Mandatory 1685 -- Multiplicity: Single 1686 -- Description: The node number 1687 -- 1688 -- Socket Number 1689 -- Keyword: Socket 1690 -- Syntax: HexString 1691 -- Status: Mandatory 1692 -- Multiplicity: Single 1693 -- Description: The SPX socket number 1694 -- 1695 -- There must be exactly one "Net" and 1696 -- one "Node" and one "Socket" entry. A 1697 -- HexString is a binary value 1698 -- represented as a string of 1699 -- ASCII characters using hexadecimal 1700 -- notation. 1701 chPortHTTP(42), -- Not in RFC 1759 1702 -- Hypertext Transfer Protocol. See [RFC1945] 1703 -- and [RFC2616]. 1704 chNDPS(43), -- Not in RFC 1759 1705 -- Novell, Inc. 1707 -- 1708 -- prtChannelInformation entry: 1709 -- 1710 -- Printer Agent Name 1711 -- Keyword: PA 1712 -- Syntax: Name 1713 -- Status: Mandatory 1714 -- Multiplicity: Single 1715 -- Description: The NDPS Printer 1716 -- Agent Name 1717 chIPP(44), -- Not in RFC 1759 1718 -- Internet Printing Protocol (IPP), 1719 -- (IPP/1.1 - see [RFC2910] and [RFC2911]) 1720 -- also applies to all future versions of IPP. 1721 -- 1722 -- IPP Printer URI 1723 -- Keyword: URI 1724 -- Syntax: URI (Unicode UTF-8 per 1725 -- [RFC2396]) 1726 -- Status: Mandatory 1727 -- Multiplicity: Single 1728 -- Default: not applicable 1729 -- Description: URI of this IPP Printer 1730 -- within Internet naming scope. Unicode 1731 -- UTF-8 [RFC2279] string with 1732 -- hexadecimal escapes for any non-ASCII 1733 -- characters (per [RFC2396]). 1734 -- Conformance: An IPP Printer shall list all 1735 -- IPP URI it supports (one per IPP Channel 1736 -- entry). If a URI contains the 'http:' 1737 -- scheme it must have an explicit port. 1738 -- See: [RFC2279], [RFC2396], [RFC2910], 1739 -- [RFC2911]. 1740 -- 1741 -- IPP Printer Client Authentication 1742 -- Keyword: Auth 1743 -- Syntax: Keyword 1744 -- Status: Optional 1745 -- Multiplicity: Single 1746 -- Default: 'none' 1747 -- Description: A client authentication 1748 -- mechanism supported for this IPP Printer 1749 -- URI: 1750 -- 'none' 1751 -- no client authentication mechanism 1752 -- 'requesting-user-name' 1753 -- authenticated user in 'requesting- 1754 -- user-name' 1755 -- 'basic' 1756 -- authenticated user via HTTP Basic 1757 -- mechanism 1758 -- 'digest' 1759 -- authenticated user via HTTP Digest 1760 -- mechanism 1761 -- 'certificate' 1762 -- authenticated user via certificate 1763 -- mechanism 1764 -- Conformance: An IPP Printer should list 1765 -- all IPP client authentication mechanisms 1766 -- it supports (one per IPP Channel entry). 1767 -- See: [RFC2911] and [RFC2910]. 1768 -- 1769 -- IPP Printer Security 1770 -- Keyword: Security 1771 -- Syntax: Keyword 1772 -- Status: Optional 1773 -- Multiplicity: Single 1774 -- Default: 'none' 1775 -- Description: A security mechanism 1776 -- supported for this IPP Printer URI: 1777 -- 'none' 1778 -- no security mechanism 1779 -- 'ssl3' 1780 -- SSL3 secure communications channel 1781 -- protocol 1782 -- 'tls' 1783 -- TLS secure communications channel 1784 -- protocol 1785 -- Conformance: An IPP Printer should list 1786 -- all IPP security mechanisms it supports 1787 -- (one per IPP Channel entry). 1788 -- See: [RFC2246], [RFC2911]. 1789 -- 1790 -- IPP Printer Protocol Version 1791 -- Keyword: Version 1792 -- Syntax: Keyword 1793 -- Status: Optional 1794 -- Multiplicity: Multiple 1795 -- Default: '1.1' 1796 -- Description: All of the IPP protocol 1797 -- versions (major.minor) supported for 1798 -- this IPP Printer URI: 1799 -- '1.0' 1800 -- IPP/1.0 conforming Printer 1801 -- '1.1' 1802 -- IPP/1.1 conforming Printer 1803 -- Conformance: An IPP Printer should list 1804 -- all IPP versions it supports (all listed 1805 -- in each IPP Channel entry). An IPP 1806 -- Client should select the highest 1807 -- numbered version the IPP Client supports 1808 -- for use in all IPP Requests (for optimum 1809 -- interworking). 1810 -- See: [RFC2911]. 1811 chSMTP(45) 1812 -- Print Job submission via Simple Mail 1813 -- Transfer Protocol (SMTP) - see [RFC2821] 1814 -- 1815 -- prtChannelInformation entry: 1816 -- 1817 -- Keyword: Mailto 1818 -- Syntax: Name 1819 -- Status: Mandatory 1820 -- Multiplicity: Single 1821 -- Default: not applicable 1822 -- Description: The SMTP URL of the printer. 1823 } 1825 -- 1826 -- Interpreter Group textual conventions 1827 -- 1829 PrtInterpreterLangFamilyTC ::= TEXTUAL-CONVENTION 1830 -- This is a type 2 enumeration. This TC was extracted from 1831 -- prtInterpreterLangFamily in RFC 1759. 1832 STATUS current 1833 DESCRIPTION 1834 "This enumeration indicates the type of interpreter that is 1835 receiving jobs." 1836 SYNTAX INTEGER { 1837 other(1), 1838 unknown(2), -- Not in RFC 1759 1839 langPCL(3), -- PCL. Starting with PCL version 5, 1840 -- HP-GL/2 is included as part of the 1841 -- PCL language. 1843 -- PCL and HP-GL/2 are registered 1844 -- trademarks of Hewlett-Packard 1845 -- Company. 1846 langHPGL(4), -- Hewlett-Packard Graphics Language. 1847 -- HP-GL is a registered trademark of 1848 -- Hewlett-Packard Company. 1849 langPJL(5), -- Peripheral Job Language. Appears in 1850 -- the data stream between data intended 1851 -- for a page description language. 1852 -- Hewlett-Packard Co. 1853 langPS(6), -- PostScript (tm) Language 1854 -- Postscript - a trademark of Adobe 1855 -- Systems Incorporated which may be 1856 -- registered in certain jurisdictions 1857 langIPDS(7), -- Intelligent Printer Data Stream 1858 -- Bi-directional print data stream for 1859 -- documents consisting of data objects 1860 -- (text, image, graphics, bar codes), 1861 -- resources (fonts, overlays) and page, 1862 -- form and finishing instructions. 1863 -- Facilitates system level device 1864 -- control, document tracking and error 1865 -- recovery throughout the print 1866 -- process. 1867 -- IBM Corporation. 1868 langPPDS(8), -- IBM Personal Printer Data Stream. 1869 -- Originally called IBM ASCII, the name 1870 -- was changed to PPDS when the Laser 1871 -- Printer was introduced in 1989. 1872 -- Lexmark International, Inc. 1873 langEscapeP(9), -- Epson Corp. 1874 langEpson(10), 1875 langDDIF(11), -- Digital Document Interchange Format 1876 -- Digital Equipment Corp., Maynard MA 1877 langInterpress(12), 1878 -- Xerox Corp. 1879 langISO6429(13), -- ISO 6429. Control functions for 1880 -- Coded Character Sets (has ASCII 1881 -- control characters, plus additional 1882 -- controls for 1883 -- character imaging devices.) 1884 langLineData(14), -- line-data: Lines of data as 1885 -- separate ASCII or EBCDIC records 1886 -- and containing no control functions 1887 -- (no CR, LF, HT, FF, etc.) 1888 -- For use with traditional line 1889 -- printers. May use CR and/or LF to 1890 -- delimit lines, instead of records. 1891 -- See ISO 10175 Document Printing 1892 -- Application (DPA) [ISO10175]. 1893 langMODCA(15), -- Mixed Object Document Content 1894 -- Architecture 1895 -- Definitions that allow the 1896 -- composition, interchange, and 1897 -- presentation of final form 1898 -- documents as a collection of data 1899 -- objects (text, image, graphics, bar 1900 -- codes), resources (fonts, overlays) 1901 -- and page, form and finishing 1902 -- instructions. 1903 -- IBM Corporation. 1904 langREGIS(16), -- Remote Graphics Instruction Set, 1905 -- Digital Equipment Corp., Maynard MA 1906 langSCS(17), -- SNA Character String 1907 -- Bi-directional print data stream for 1908 -- SNA LU-1 mode of communication. 1909 -- IBM 1910 langSPDL(18), -- ISO 10180 Standard Page Description 1911 -- Language 1912 -- ISO Standard 1913 langTEK4014(19), -- Tektronix Corp. 1914 langPDS(20), 1915 langIGP(21), -- Printronix Corp. 1916 langCodeV(22), -- Magnum Code-V, Image and printer 1917 -- control language used to control 1918 -- impact/dot-matrix printers. 1919 -- QMS, Inc., Mobile AL 1920 langDSCDSE(23), -- DSC-DSE: Data Stream Compatible and 1921 -- Emulation Bi-directional print data 1922 -- stream for non-SNA (DSC) and SNA LU-3 1923 -- 3270 controller (DSE) communications 1924 -- IBM 1925 langWPS(24), -- Windows Printing System, Resource 1926 -- based command/data stream used by 1927 -- Microsoft At Work Peripherals. 1928 -- Developed by the Microsoft 1929 -- Corporation. 1930 langLN03(25), -- Early DEC-PPL3, Digital Equipment 1931 -- Corp. 1932 langCCITT(26), 1933 langQUIC(27), -- QUIC (Quality Information Code), Page 1934 -- Description Language for laser 1935 -- printers. Included graphics, printer 1936 -- control capability and emulation of 1937 -- other well-known printer. 1938 -- QMS, Inc. 1939 langCPAP(28), -- Common Printer Access Protocol 1940 -- Digital Equipment Corp. 1941 langDecPPL(29), -- Digital ANSI-Compliant Printing 1942 -- Protocol 1943 -- (DEC-PPL) 1944 -- Digital Equipment Corp. 1945 langSimpleText(30), 1946 -- simple-text: character coded data, 1947 -- including NUL, CR , LF, HT, and FF 1948 -- control characters. See ISO 10175 1949 -- Document Printing Application (DPA) 1950 -- [ISO10175]. 1951 langNPAP(31), -- Network Printer Alliance Protocol 1952 -- (NPAP). This protocol has been 1953 -- superseded by the IEEE 1284.1 TIPSI 1954 -- Std (ref. LangTIPSI(49)). 1955 langDOC(32), -- Document Option Commands, Appears in 1956 -- the data stream between data 1957 -- intended for a page description. 1958 -- QMS, Inc. 1959 langimPress(33), -- imPRESS, Page description language 1960 -- originally developed for the 1961 -- ImageServer product line. A binary 1962 -- language providing representations 1963 -- of text, simple graphics, and some 1964 -- large forms (simple 1965 -- bit-map and CCITT group 3/4 1966 -- encoded).The 1967 -- language was intended to be sent over 1968 -- an 8-bit channel and supported early 1969 -- document preparation languages (e.g., 1970 -- TeX and TROFF). 1971 -- QMS, Inc. 1972 langPinwriter(34), 1973 -- 24 wire dot matrix printer for 1974 -- USA, Europe, and Asia except 1975 -- Japan. 1976 -- More widely used in Germany, and 1977 -- some Asian countries than in US. 1979 -- NEC 1980 langNPDL(35), -- Page printer for Japanese market. 1981 -- NEC 1982 langNEC201PL(36), -- Serial printer language used in 1983 -- the Japanese market. 1984 -- NEC 1985 langAutomatic(37), 1986 -- Automatic PDL sensing. Automatic 1987 -- sensing of the interpreter 1988 -- language family by the printer 1989 -- examining the document content. 1990 -- Which actual interpreter language 1991 -- families are sensed depends on 1992 -- the printer implementation. 1993 langPages(38), -- Page printer Advanced Graphic 1994 -- Escape Set 1995 -- IBM Japan 1996 langLIPS(39), -- LBP Image Processing System 1997 langTIFF(40), -- Tagged Image File Format (Aldus) 1998 langDiagnostic(41), 1999 -- A hex dump of the input to the 2000 -- interpreter 2001 langPSPrinter(42), 2002 -- The PostScript Language used for 2003 -- control (with any PDLs) 2004 -- Adobe Systems Incorporated 2005 langCaPSL(43), -- Canon Print Systems Language 2006 langEXCL(44), -- Extended Command Language 2007 -- Talaris Systems Inc. 2008 langLCDS(45), -- Line Conditioned Data Stream 2009 -- Xerox Corporation 2010 langXES(46), -- Xerox Escape Sequences 2011 -- Xerox Corporation 2012 langPCLXL(47), -- Not in RFC 1759 2013 -- Printer Control Language. Extended 2014 -- language features for printing, and 2015 -- printer control. 2016 -- Hewlett-Packard Co. 2017 langART(48), -- Not in RFC 1759 2018 -- Advanced Rendering Tools (ART). 2019 -- Page Description language 2020 -- originally developed for the Laser 2021 -- Press printers. 2022 -- Technical reference manual: "ART IV 2023 -- Reference Manual", No F33M. 2025 -- Fuji Xerox Co., Ltd. 2026 langTIPSI(49), -- Not in RFC 1759 2027 -- Transport Independent Printer 2028 -- System Interface (ref. IEEE Std. 2029 -- 1284.1) 2030 langPrescribe(50), -- Not in RFC 1759 2031 -- Page description and printer 2032 -- control language. It can be 2033 -- described with ordinary ASCII 2034 -- Technical reference manual: 2035 -- "PRESCRIBE II Programming Manual" 2036 langLinePrinter(51), -- Not in RFC 1759 2037 -- A simple-text character stream which 2038 -- supports the control codes LF, VT, 2039 -- FF, and plus Centronics or 2040 -- Dataproducts Vertical Format Unit 2041 -- (VFU) language is commonly used on 2042 -- many older model line and matrix 2043 -- printers. 2044 langIDP(52), -- Not in RFC 1759 2045 -- Imaging Device Protocol 2046 -- Apple Computer. 2047 langXJCL(53), -- Not in RFC 1759 2048 -- Xerox Job Control Language (JCL). 2049 -- A Job Control language originally 2050 -- developed for the LaserPress printers 2051 -- and is capable of switching PDLs. 2052 -- Technical reference manual: 2053 -- "ART IV Reference Manual", No F33M. 2054 -- Fuji Xerox Co., Ltd. 2055 langPDF(54), -- Not in RFC 1759 2056 -- Adobe Portable Document Format 2057 -- Adobe Systems, Inc. 2058 langRPDL(55), -- Not in RFC 1759 2059 -- Ricoh Page Description Language for 2060 -- printers. 2061 -- Technical manual "RPDL command 2062 -- reference" No.307029 2063 -- RICOH, Co. LTD 2064 langIntermecIPL(56), -- Not in RFC 1759 2065 -- Intermec Printer Language for label 2066 -- printers. 2067 -- Technical Manual: "IPL Programmers 2068 -- Reference Manual" 2069 -- Intermec Corporation 2071 langUBIFingerprint(57), -- Not in RFC 1759 2072 -- An intelligent basic-like programming 2073 -- language for label printers. 2074 -- Reference Manual: "UBI Fingerprint 2075 -- 7.1", No. 1-960434-00 2076 -- United Barcode Industries 2077 langUBIDirectProtocol(58), -- Not in RFC 1759 2078 -- An intelligent control language for 2079 -- label printers. 2080 -- Programmers guide: " UBI Direct 2081 -- Protocol", No. 1-960419-00 2082 -- United Barcode Industries 2083 langFujitsu(59), -- Not in RFC 1759 2084 -- Fujitsu Printer Language 2085 -- Reference Manual: 2086 -- "FM Printer Sequence" No. 80HP-0770 2087 -- FUJITSU LIMITED 2088 langCGM(60), -- Not in RFC 1759 2089 -- Computer Graphics Metafile 2090 -- MIME type 'image/cgm' 2091 langJPEG(61), -- Not in RFC 1759 2092 -- Joint Photographic Experts Group 2093 -- MIME type 'image/jpeg' 2094 langCALS1(62), -- Not in RFC 1759 2095 -- US DOD CALS1 (see MIL-STD-1840) 2096 -- MIME type 'application/cals-1840' 2097 langCALS2(63), -- Not in RFC 1759 2098 -- US DOD CALS2 (see MIL-STD-1840) 2099 -- MIME type 'application/cals-1840' 2100 langNIRS(64), -- Not in RFC 1759 2101 -- US DOD NIRS (see MIL-STD-1840) 2102 -- MIME type 'application/cals-1840' 2103 langC4(65) -- Not in RFC 1759 2104 -- US DOD C4 (see MIL-STD-1840) 2105 -- MIME type 'application/cals-1840' 2106 } 2108 -- 2109 -- Input/Output Group textual conventions 2110 -- 2112 PrtInputTypeTC ::= TEXTUAL-CONVENTION 2113 -- This is a type 2 enumeration. This TC was extracted from 2114 -- prtInputType in RFC 1759. 2115 STATUS current 2116 DESCRIPTION 2117 "The type of technology (discriminated primarily according to 2118 feeder mechanism type) employed by a specific component or 2119 components." 2120 SYNTAX INTEGER { 2121 other(1), 2122 unknown(2), 2123 sheetFeedAutoRemovableTray(3), 2124 sheetFeedAutoNonRemovableTray(4), 2125 sheetFeedManual(5), 2126 continuousRoll(6), 2127 continuousFanFold(7) 2128 } 2130 PrtOutputTypeTC ::= TEXTUAL-CONVENTION 2131 -- This is a type 2 enumeration. This TC was extracted from 2132 -- prtOutputType in RFC 1759. 2133 STATUS current 2134 DESCRIPTION 2135 "The Type of technology supported by this output subunit." 2136 SYNTAX INTEGER { 2137 other(1), 2138 unknown(2), 2139 removableBin(3), 2140 unRemovableBin(4), 2141 continuousRollDevice(5), 2142 mailBox(6), 2143 continuousFanFold(7) 2144 } 2146 -- 2147 -- Marker Group textual conventions 2148 -- 2150 PrtMarkerMarkTechTC ::= TEXTUAL-CONVENTION 2151 -- This is a type 2 enumeration. This TC was extracted from 2152 -- prtMarkerMarkTech in RFC 1759. 2153 STATUS current 2154 DESCRIPTION 2155 "The type of marking technology used for this marking 2156 subunit." 2157 SYNTAX INTEGER { 2158 other(1), 2159 unknown(2), 2160 electrophotographicLED(3), 2161 electrophotographicLaser(4), 2162 electrophotographicOther(5), 2163 impactMovingHeadDotMatrix9pin(6), 2164 impactMovingHeadDotMatrix24pin(7), 2165 impactMovingHeadDotMatrixOther(8), 2166 impactMovingHeadFullyFormed(9), 2167 impactBand(10), 2168 impactOther(11), 2169 inkjetAqueous(12), 2170 inkjetSolid(13), 2171 inkjetOther(14), 2172 pen(15), 2173 thermalTransfer(16), 2174 thermalSensitive(17), 2175 thermalDiffusion(18), 2176 thermalOther(19), 2177 electroerosion(20), 2178 electrostatic(21), 2179 photographicMicrofiche(22), 2180 photographicImagesetter(23), 2181 photographicOther(24), 2182 ionDeposition(25), 2183 eBeam(26), 2184 typesetter(27) 2185 } 2187 PrtMarkerSuppliesTypeTC ::= TEXTUAL-CONVENTION 2188 -- This is a type 3 enumeration. This TC was extracted from 2189 -- prtMarkerSuppliesType in RFC 1759. 2190 STATUS current 2191 DESCRIPTION 2192 "The type of this supply." 2193 SYNTAX INTEGER { 2194 other(1), 2195 unknown(2), 2196 -- Values for Printer MIB 2197 toner(3), 2198 wasteToner(4), 2199 ink(5), 2200 inkCartridge(6), 2201 inkRibbon(7), 2202 wasteInk(8), 2203 opc(9), -- photo conductor 2204 developer(10), 2205 fuserOil(11), 2206 solidWax(12), 2207 ribbonWax(13), 2208 wasteWax(14), 2209 fuser(15), -- Not in RFC 1759 2210 coronaWire(16), -- Not in RFC 1759 2211 fuserOilWick(17), -- Not in RFC 1759 2212 cleanerUnit(18), -- Not in RFC 1759 2213 fuserCleaningPad(19), -- Not in RFC 1759 2214 transferUnit(20), -- Not in RFC 1759 2215 tonerCartridge(21), -- Not in RFC 1759 2216 fuserOiler(22), -- Not in RFC 1759 2217 -- End of values for Printer MIB 2218 -- Values for Finisher MIB 2219 water(23), -- Not in RFC 1759 2220 wasteWater(24), -- Not in RFC 1759 2221 glueWaterAdditive(25),-- Not in RFC 1759 2222 wastePaper(26), -- Not in RFC 1759 2223 bindingSupply(27), -- Not in RFC 1759 2224 bandingSupply(28), -- Not in RFC 1759 2225 stitchingWire(29), -- Not in RFC 1759 2226 shrinkWrap(30), -- Not in RFC 1759 2227 paperWrap(31), -- Not in RFC 1759 2228 staples(32), -- Not in RFC 1759 2229 inserts(33), -- Not in RFC 1759 2230 covers(34) -- Not in RFC 1759 2231 -- End of values for Finisher MIB 2232 } 2234 -- 2235 -- Media Path textual conventions 2236 -- 2238 PrtMediaPathTypeTC ::= TEXTUAL-CONVENTION 2239 -- This is a type 2 enumeration. This TC was extracted from 2240 -- prtMediaPathType in RFC 1759. 2241 STATUS current 2242 DESCRIPTION 2243 "The type of the media path for this media path." 2244 SYNTAX INTEGER { 2245 other(1), 2246 unknown(2), 2247 longEdgeBindingDuplex(3), 2248 shortEdgeBindingDuplex(4), 2249 simplex(5) 2250 } 2252 -- 2253 -- Console Group textual conventions 2254 -- 2256 PrtConsoleColorTC ::= TEXTUAL-CONVENTION 2257 -- This is a type 2 enumeration. This TC was extracted from 2258 -- prtConsoleColor in RFC 1759. 2259 STATUS current 2260 DESCRIPTION 2261 "The color of this light." 2262 SYNTAX INTEGER { 2263 other(1), 2264 unknown(2), 2265 white(3), 2266 red(4), 2267 green(5), 2268 blue(6), 2269 cyan(7), 2270 magenta(8), 2271 yellow(9), 2272 orange(10) -- Not in RFC 1759 2273 } 2275 PrtConsoleDisableTC ::= TEXTUAL-CONVENTION 2276 -- This is a type 2 enumeration. This TC was extracted from 2277 -- prtConsoleDisable in RFC 1759. 2278 STATUS current 2279 DESCRIPTION 2280 "This value indicates whether or not input is accepted from 2281 the operator console. A value of 'enabled' indicates that 2282 input is accepted from the console, and a value of 'disabled' 2283 indicates that input is not accepted from the console. " 2284 SYNTAX INTEGER { 2285 enabled(3), 2286 disabled(4) 2287 } 2289 -- 2290 -- Alert Group textual conventions 2291 -- 2293 PrtAlertTrainingLevelTC ::= TEXTUAL-CONVENTION 2294 -- This is a type 2 enumeration. This TC was extracted from 2295 -- prtAlertTrainingLevel in RFC 1759. 2296 STATUS current 2297 DESCRIPTION 2298 "The level of training required to handle this alert, if 2299 human intervention is required. The noInterventionRequired 2300 value should be used if the event does not require any human 2301 intervention. The training level is an enumeration that is 2302 determined and assigned by the printer manufacturer based on 2303 the information or training required to handle this alert. 2304 The printer will break alerts into these different training 2305 levels. It is the responsibility of a management application 2306 in the system to determine how a particular alert is handled 2307 and how and to whom that alert is routed. The following are 2308 the four training levels of alerts: 2310 Field Service - Alerts that typically require advanced 2311 training and technical knowledge of the printer and its 2312 subunits. An example of a technical person would be a 2313 manufacturer's Field Service representative, or other 2314 person formally trained by the manufacturer or similar 2315 representative. 2316 Trained - Alerts that require an intermediate or moderate 2317 knowledge of the printer and its subunits. A typical 2318 example of such an alert is replacing a toner cartridge. 2319 Untrained - Alerts that can be fixed without prior 2320 training either because the action to correct the alert 2321 is obvious or the printer can help the untrained person 2322 fix the problem. A typical example of such an alert is 2323 reloading paper trays or emptying output bins on a low 2324 end printer. 2325 Management - Alerts that have to do with overall operation 2326 of and configuration of the printer. Examples of such 2327 management events are configuration change of subunits." 2328 SYNTAX INTEGER { 2329 other(1), 2330 unknown(2), 2331 untrained(3), 2332 trained(4), 2333 fieldService(5), 2334 management(6), 2335 noInterventionRequired(7) 2336 } 2338 PrtAlertGroupTC ::= TEXTUAL-CONVENTION 2339 -- This is a type 2 enumeration. Values in the range 1 to 29 2340 -- must not be IANA-assigned without re-publishing Printer MIB. 2341 -- Values of 30 and greater are for use in MIBs that augment 2342 -- the Printer MIB, such as the Finisher MIB. 2343 -- This TC extracted from prtAlertGroup in RFC 1759. 2344 -- NOTE: This TC has been changed from a type 1 (in RFC 1759) 2345 -- to a type 2 enumeration to allow IANA-assigned extensions. 2346 -- 2347 STATUS current 2348 DESCRIPTION 2349 "The type of subunit within the printer model that this alert 2350 is related. Input, output, and markers are examples of 2351 printer model groups, i.e., examples of types of subunits. 2352 Wherever possible, the enumerations match the sub-identifier 2353 that identifies the relevant table in the Printer MIB. 2355 NOTE: Alert type codes have been added for the Host Resources 2356 MIB storage table and device table. These additional types 2357 are for situations in which the printer's storage and device 2358 objects must generate alerts (and possibly traps for critical 2359 alerts)." 2360 SYNTAX INTEGER { 2361 other(1), 2362 -- Values for Host Resources MIB 2363 hostResourcesMIBStorageTable(3), 2364 hostResourcesMIBDeviceTable(4), 2365 -- Values for Printer MIB 2366 generalPrinter(5), 2367 cover(6), 2368 localization(7), 2369 input(8), 2370 output(9), 2371 marker(10), 2372 markerSupplies(11), 2373 markerColorant(12), 2374 mediaPath(13), 2375 channel(14), 2376 interpreter(15), 2377 consoleDisplayBuffer(16), 2378 consoleLights(17), 2379 alert(18), 2380 -- Values (5) to (29) reserved for Printer MIB 2381 -- Values for Finisher MIB 2382 finDevice(30), -- Not in RFC 1759 2383 finSupply(31), -- Not in RFC 1759 2384 finSupplyMediaInput(32), -- Not in RFC 1759 2385 finAttribute(33) -- Not in RFC 1759 2386 -- Values (30) to (39) reserved for Finisher MIB 2387 } 2389 PrtAlertCodeTC ::= TEXTUAL-CONVENTION 2390 -- This is a type 2 enumeration. This TC was extracted from 2391 -- prtAlertCode in RFC 1759. 2392 STATUS current 2393 DESCRIPTION 2394 "The code that describes the type of alert for this entry in 2395 the table. Binary change event alerts describe states of the 2396 subunit while unary change event alerts describe a single 2397 event. The same alert code can be used for a binary change 2398 event or a unary change event, depending on implementation. 2399 Also, the same alert code can be used to indicate a critical 2400 or non-critical (warning) alert, depending on implementation. 2401 The value of prtAlertSeverityLevel specifies binary vs. unary 2402 and critical vs. non-critical for each event for the 2403 implementation. 2405 While there are some specific codes for many subunits, the 2406 generic codes should be used for most subunit alerts. The 2407 network management station can then query the subunit 2408 specified by prtAlertGroup to determine further subunit 2409 status and other subunit information. 2411 An agent shall not add two entries to the alert table for the 2412 same event, one containing a generic event code and the other 2413 containing a specific event code; the agent shall add only 2414 one entry in the alert table for each event; either generic 2415 (preferred) or specific, not both. 2417 Implementation of the unary change event 2418 alertRemovalOfBinaryChangeEntry(1801) is optional. When 2419 implemented, this alert code shall indicate to network 2420 management stations that the trailing edge of a binary change 2421 event has occurred and the corresponding alert entry has been 2422 removed from the alert table. As with all events, the 2423 alertRemovalOfBinaryChangeEntry(1801) alert shall be placed 2424 at the end of the alert table. Such an alert table entry 2425 shall specify the following information: 2427 prtAlertSeverityLevel warningUnaryChangeEvent(4) 2428 prtAlertTrainingLevel noInterventionRequired(7) 2429 prtAlertGroup alert(18) 2430 prtAlertGroupIndex the index of the row in the 2431 alert table of the binary 2432 change event that this event 2433 has removed. 2434 prtAlertLocation unknown (-2) 2435 prtAlertCode alertRemovalOfBinaryChangeEntry(1801) 2436 prtAlertDescription 2437 prtAlertTime the value of sysUpTime at 2438 the time of the removal of the 2439 binary change event from the 2440 alert table. 2442 Optionally, the agent may generate a trap coincident with 2443 removing the binary change event and placing the unary change 2444 event alertRemovalOfBinaryChangeEntry(1801) in the alert 2445 table. For such a trap, the prtAlertIndex sent with the above 2446 trap parameters shall be the index of the 2447 alertRemovalOfBinaryChangeEvent row that was added to the 2448 prtAlertTable; not the index of the row that was removed from 2449 the prtAlertTable." 2450 SYNTAX INTEGER { 2451 other(1), 2452 -- an event that is not represented 2453 -- by one of the alert codes 2454 -- specified below. 2455 unknown(2), 2456 -- The following generic codes are common to 2457 -- multiple groups. The NMS may examine the 2458 -- prtAlertGroup object to determine what group 2459 -- to query for further information. 2460 coverOpen(3), 2461 coverClosed(4), 2462 interlockOpen(5), 2463 interlockClosed(6), 2464 configurationChange(7), 2465 jam(8), 2466 subunitMissing(9), -- Not in RFC 1759 2467 -- The subunit tray, bin, etc. 2468 -- has been removed. 2469 subunitLifeAlmostOver(10), -- Not in RFC 1759 2470 subunitLifeOver(11), -- Not in RFC 1759 2471 subunitAlmostEmpty(12), -- Not in RFC 1759 2472 subunitEmpty(13), -- Not in RFC 1759 2473 subunitAlmostFull(14), -- Not in RFC 1759 2474 subunitFull(15), -- Not in RFC 1759 2475 subunitNearLimit(16), -- Not in RFC 1759 2476 subunitAtLimit(17), -- Not in RFC 1759 2477 subunitOpened(18), -- Not in RFC 1759 2478 subunitClosed(19), -- Not in RFC 1759 2479 subunitTurnedOn(20), -- Not in RFC 1759 2480 subunitTurnedOff(21), -- Not in RFC 1759 2481 subunitOffline(22), -- Not in RFC 1759 2482 subunitPowerSaver(23), -- Not in RFC 1759 2483 subunitWarmingUp(24), -- Not in RFC 1759 2484 subunitAdded(25), -- Not in RFC 1759 2485 subunitRemoved(26), -- Not in RFC 1759 2486 subunitResourceAdded(27), -- Not in RFC 1759 2487 subunitResourceRemoved(28), -- Not in RFC 1759 2488 subunitRecoverableFailure(29), 2489 -- Not in RFC 1759 2490 subunitUnrecoverableFailure(30), 2491 -- Not in RFC 1759 2492 subunitRecoverableStorageError(31), 2493 -- Not in RFC 1759 2494 subunitUnrecoverableStorageError(32), 2495 -- Not in RFC 1759 2496 subunitMotorFailure(33), -- Not in RFC 1759 2497 subunitMemoryExhausted(34), -- Not in RFC 1759 2498 subunitUnderTemperature(35), -- Not in RFC 1759 2499 subunitOverTemperature(36), -- Not in RFC 1759 2500 subunitTimingFailure(37), -- Not in RFC 1759 2501 subunitThermistorFailure(38), -- Not in RFC 1759 2503 -- General Printer group 2504 doorOpen(501), -- DEPRECATED 2505 -- Use coverOpened(3) 2506 doorClosed(502), -- DEPRECATED 2507 -- Use coverClosed(4) 2508 powerUp(503), 2509 powerDown(504), 2510 printerNMSReset(505), -- Not in RFC 1759 2511 -- The printer has been reset by some 2512 -- network management station(NMS) 2513 -- writing into 'prtGeneralReset'. 2514 printerManualReset(506), -- Not in RFC 1759 2515 -- The printer has been reset manually. 2516 printerReadyToPrint(507), -- Not in RFC 1759 2517 -- The printer is ready to print. (i.e., 2518 -- not warming up, not in power save 2519 -- state, not adjusting print quality, 2520 -- etc.). 2522 -- Input Group 2523 inputMediaTrayMissing(801), 2524 inputMediaSizeChange(802), 2525 inputMediaWeightChange(803), 2526 inputMediaTypeChange(804), 2527 inputMediaColorChange(805), 2528 inputMediaFormPartsChange(806), 2529 inputMediaSupplyLow(807), 2530 inputMediaSupplyEmpty(808), 2531 inputMediaChangeRequest(809), -- Not in RFC 1759 2532 -- An interpreter has detected that a 2533 -- different medium is need in this input 2534 -- tray subunit. The prtAlertDescription may 2535 -- be used to convey a human readable 2536 -- description of the medium required to 2537 -- satisfy the request. 2538 inputManualInputRequest(810), -- Not in RFC 1759 2539 -- An interpreter has detected that manual 2540 -- input is required in this subunit. The 2541 -- prtAlertDescription may be used to convey 2542 -- a human readable description of the medium 2543 -- required to satisfy the request. 2544 inputTrayPositionFailure(811), -- Not in RFC 1759 2545 -- The input tray failed to position correctly. 2546 inputTrayElevationFailure(812), 2547 -- Not in RFC 1759 2548 inputCannotFeedSizeSelected(813), 2549 -- Not in RFC 1759 2550 -- Output Group 2551 outputMediaTrayMissing(901), 2552 outputMediaTrayAlmostFull(902), 2553 outputMediaTrayFull(903), 2554 outputMailboxSelectFailure(904), 2555 -- Not in RFC 1759 2556 -- Marker group 2557 markerFuserUnderTemperature(1001), 2558 markerFuserOverTemperature(1002), 2559 markerFuserTimingFailure(1003), 2560 -- Not in RFC 1759 2561 markerFuserThermistorFailure(1004), 2562 -- Not in RFC 1759 2563 markerAdjustingPrintQuality(1005), 2564 -- Not in RFC 1759 2565 -- Marker Supplies group 2566 markerTonerEmpty(1101), 2567 markerInkEmpty(1102), 2568 markerPrintRibbonEmpty(1103), 2569 markerTonerAlmostEmpty(1104), 2570 markerInkAlmostEmpty(1105), 2571 markerPrintRibbonAlmostEmpty(1106), 2572 markerWasteTonerReceptacleAlmostFull(1107), 2573 markerWasteInkReceptacleAlmostFull(1108), 2574 markerWasteTonerReceptacleFull(1109), 2575 markerWasteInkReceptacleFull(1110), 2576 markerOpcLifeAlmostOver(1111), 2577 markerOpcLifeOver(1112), 2578 markerDeveloperAlmostEmpty(1113), 2579 markerDeveloperEmpty(1114), 2580 markerTonerCartridgeMissing(1115), 2581 -- Not in RFC 1759 2582 -- Media Path Device Group 2583 mediaPathMediaTrayMissing(1301), 2584 mediaPathMediaTrayAlmostFull(1302), 2585 mediaPathMediaTrayFull(1303), 2586 mediaPathCannotDuplexMediaSelected(1304), 2587 -- Not in RFC 1759 2588 -- Interpreter Group 2589 interpreterMemoryIncrease(1501), 2590 interpreterMemoryDecrease(1502), 2591 interpreterCartridgeAdded(1503), 2592 interpreterCartridgeDeleted(1504), 2593 interpreterResourceAdded(1505), 2594 interpreterResourceDeleted(1506), 2595 interpreterResourceUnavailable(1507), 2596 interpreterComplexPageEncountered(1509), 2597 -- Not in RFC 1759 2598 -- The interpreter has encountered a page 2599 -- that is too complex for the resources that 2600 -- are available. 2601 -- Alert Group 2602 alertRemovalOfBinaryChangeEntry(1801) 2603 -- Not in RFC 1759 2604 -- A binary change event entry has been 2605 -- removed from the alert table. This unary 2606 -- change alert table entry is added to the 2607 -- end of the alert table. 2608 } 2610 END 2612 6. The Printer MIB 2614 Printer-MIB DEFINITIONS ::= BEGIN 2616 IMPORTS 2617 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, TimeTicks, 2618 NOTIFICATION-TYPE, OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI 2619 TEXTUAL-CONVENTION FROM SNMPv2-TC 2620 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM 2621 SNMPv2-CONF 2622 hrDeviceIndex, hrStorageIndex FROM HOST-RESOURCES-MIB 2623 InterfaceIndexOrZero FROM IF-MIB 2624 PrtCoverStatusTC, PrtGeneralResetTC, PrtChannelTypeTC, 2625 PrtInterpreterLangFamilyTC, PrtInputTypeTC, PrtOutputTypeTC, 2626 PrtMarkerMarkTechTC, PrtMarkerSuppliesTypeTC, PrtConsoleColorTC, 2627 PrtConsoleDisableTC, PrtMediaPathTypeTC, PrtAlertGroupTC, 2628 PrtAlertTrainingLevelTC, PrtAlertCodeTC FROM IANA-PRINTER-MIB 2629 IANACharset FROM IANA-CHARSET-MIB; 2631 -- Note: RFC 1759 contained a CodedCharSet TC that referenced a 2632 -- non-existant IANA document. This is now an official IANA MIB 2633 -- and the CodedCharSet TC has been removed from this version of 2634 -- the MIB. 2636 printmib MODULE-IDENTITY 2637 LAST-UPDATED "200210080000Z" 2638 ORGANIZATION "PWG IEEE/ISTO Printer Working Group" 2639 CONTACT-INFO 2640 "Harry Lewis 2641 IBM 2642 Phone (303) 924-5337 2643 Email: harryl@us.ibm.com 2644 http://www.pwg.org/mib/index.html" 2645 DESCRIPTION 2646 "The MIB module for management of printers." 2647 REVISION "200210080000Z" 2648 DESCRIPTION 2649 "Printer MIB v2. 2650 Moved all TCs to be maintained by IANA into the ianaPrinter MIB 2651 which is contained in this document. 2652 Five new OBJECT-GROUPs: prtAuxilliarySheetGroup, 2653 prtInputSwitchingGroup, prtGeneralV2Group, 2654 prtAlertTableV2Group, prtChannelV2Group. 2655 Nine new objects added to those groups: 2656 prtAuxiliarySheetStartupPage, prtAuxiliarySheetBannerPage, 2657 prtGeneralPrinterName, prtGeneralSerialNumber, 2658 prtAlertCriticalEvents, prtAlertAllEvents, 2659 prtInputMediaLoadTimeout, prtInputNextIndex, 2660 prtChannelInformation. 2661 SYNTAX range changed from (0..65535) to (1..65535) for the 2662 index objects prtStorageRefSeqNumber and 2663 prtDeviceRefSeqNumber. 2664 SYNTAX range changed from (0..65535) to (0..2147483647) for the 2665 objects prtStorageRefIndex and prtDeviceRefIndex to agree 2666 with the Host Resources MIB. 2667 Defined a range for the objects with a SYNTAX of Integer32: 2668 prtOutputDefaultIndex, prtInputMediaDimFeedDirDeclared, 2669 prtInputMediaDimXFeedDirDeclared, prtInputMaxCapacity, 2670 prtInputCurrentLevel, prtInputMediaDimFeedDirChosen, 2671 prtInputMediaDimXFeedDirChosen, prtInputMediaWeight, 2672 prtInputMediaFormParts, prtOutputIndex, 2673 prtOutputMaxCapacity, prtOutputRemainingCapacity, 2674 prtOutputMaxDimFeedDir, prtOutputMaxDimXFeedDir, 2675 prtOutputMinDimFeedDir, prtOutputMinDimXFeedDir, 2676 prtMarkerAddressibilityFeedDir, 2677 prtMarkerAddressibilityXFeedDir, prtMarkerNorthMargin, 2678 prtMarkerSouthMargin, prtMarkerWestMargin, 2679 prtMarkerEastMargin, prtMarkerSuppliesMaxCapacity, 2680 prtMarkerSuppliesLevel, prtMarkerColorantTonality, 2681 prtMediaPathMaxSpeed, prtMediaPathMaxMediaFeedDir, 2682 prtMediaPathMaxMediaXFeedDir, prtMediaPathMinMediaFeedDir, 2683 prtMediaPathMinMediaXFeedDir, prtChannelIndex, 2684 prtChannelCurrentJobCntlLangIndex, prtInterpreterIndex, 2685 prtChannelDefaultPageDescLangIndex, prtConsoleOnTime, 2686 prtInterpreterFeedAddressibility, prtConsoleOffTime, 2687 prtInterpreterXFeedAddressibility, prtAlertIndex, 2688 prtAlertGroupIndex, prtAlertLocation. 2689 Changed SYNTAX from Integer32 to InterfaceIndexOrZero for 2690 prtChannelIfIndex. 2691 One new NOTIFICATION-GROUP: prtAlertTrapGroup which contains 2692 printerV2Alert. 2693 In MODULE-COMPLIANCE prtMIBCompliance, new OBJECT-GROUPs and 2694 the NOTIFICATION_GROUP, all in GROUP (not MANDATORY-GROUP) 2695 clauses. The nine new objects are optional, i.e., this 2696 draft is backward compatible with RFC 1759." 2697 REVISION "199411250000Z" 2698 DESCRIPTION 2699 "The original version of this MIB, published as RFC1759." 2700 ::= { mib-2 43 } 2702 -- Textual conventions for this MIB module 2703 -- 2704 -- Generic unspecific textual conventions 2705 -- 2707 PrtMediaUnitTC ::= TEXTUAL-CONVENTION 2708 -- This is a type 1 enumeration. Replaces MediaUnit in RFC 1759. 2709 -- Even though it is formally not allowed to change TC names, the WG 2710 -- decided this name change was necessary to clearly indicate this 2711 -- TC is from the Printer MIB. 2713 STATUS current 2714 DESCRIPTION 2715 "Units of measure for media dimensions." 2716 SYNTAX INTEGER { 2717 tenThousandthsOfInches(3), -- .0001 2718 micrometers(4) 2719 } 2721 MediaUnit ::= TEXTUAL-CONVENTION 2722 -- Replaced by prtMediaUnitTC. 2723 STATUS deprecated 2724 DESCRIPTION 2725 "Units of measure for media dimensions." 2726 SYNTAX INTEGER { 2727 tenThousandthsOfInches(3), -- .0001 2728 micrometers(4) 2729 } 2731 PrtCapacityUnitTC ::= TEXTUAL-CONVENTION 2732 -- This is a type 1 enumeration. Replaces CapacityUnit in RFC 1759. 2733 -- Even though it is formally not allowed to change TC names, the WG 2734 -- decided this name change was necessary due to the added values 2735 -- and to clearly indicate this TC is from the Printer MIB. 2736 STATUS current 2737 DESCRIPTION 2738 "Units of measure for media capacity." 2739 SYNTAX INTEGER { 2740 other(1), -- New, not in RFC 1759 2741 unknown(2), -- New, not in RFC 1759 2742 tenThousandthsOfInches(3), -- .0001 2743 micrometers(4), 2744 sheets(8), 2745 feet(16), 2746 meters(17), 2747 -- Values for Finisher MIB 2748 items(18), -- New, not in RFC 1759 2749 percent(19) -- New, not in RFC 1759 2750 } 2752 CapacityUnit ::= TEXTUAL-CONVENTION 2753 -- Replaced by prtCapacityUnitTC. 2754 STATUS deprecated 2755 DESCRIPTION 2756 "Units of measure for media capacity." 2757 SYNTAX INTEGER { 2758 tenThousandthsOfInches(3), -- .0001 2759 micrometers(4), 2760 sheets(8), 2761 feet(16), 2762 meters(17) 2763 } 2765 PrtPrintOrientationTC ::= TEXTUAL-CONVENTION 2766 -- This value is a type 1 enumeration. 2767 STATUS current 2768 DESCRIPTION 2769 "A generic representation for printing orientation on a 2770 'page'." 2771 SYNTAX INTEGER { 2772 other(1), 2773 portrait(3), 2774 landscape(4) 2775 } 2777 PrtSubUnitStatusTC ::= TEXTUAL-CONVENTION 2778 -- This is a type 1 enumeration. Replaces SubUnitStatus in RFC 2779 -- 1759. Even though it is formally not allowed to change TC names, 2780 -- the WG decided this name change was necessary to indicate this TC 2781 -- is from the Printer MIB. 2783 STATUS current 2784 DESCRIPTION 2785 "Status of a printer sub-unit. 2787 The SubUnitStatus is an integer that is the sum of 5 distinct 2788 values, Availability, Non-Critical, Critical, On-line, and 2789 Transitioning. These values are: 2791 Availability Value 2793 Available and Idle 0 0000'b 2794 Available and Standby 2 0010'b 2795 Available and Active 4 0100'b 2796 Available and Busy 6 0110'b 2797 Unavailable and OnRequest 1 0001'b 2798 Unavailable because Broken 3 0011'b 2799 Unknown 5 0101'b 2801 Non-Critical 2802 No Non-Critical Alerts 0 0000'b 2803 Non-Critical Alerts 8 1000'b 2805 Critical 2807 No Critical Alerts 0 0000'b 2808 Critical Alerts 16 1 0000'b 2810 On-Line 2812 State is On-Line 0 0000'b 2813 State is Off-Line 32 10 0000'b 2815 Transitioning 2817 At intended state 0 0000'b 2818 Transitioning to intended state 64 100 0000'b" 2820 SYNTAX INTEGER (0..126) 2822 SubUnitStatus ::= TEXTUAL-CONVENTION 2823 -- Replaced by prtSubUnitStatusTC. 2824 STATUS deprecated 2825 DESCRIPTION 2826 "Status of a printer sub-unit. 2828 The SubUnitStatus is an integer that is the sum of 5 distinct 2829 values, Availability, Non-Critical, Critical, On-line, and 2830 Transitioning. These values are: 2832 Availability Value 2833 Available and Idle 0 0000'b 2834 Available and Standby 2 0010'b 2835 Available and Active 4 0100'b 2836 Available and Busy 6 0110'b 2837 Unavailable and OnRequest 1 0001'b 2838 Unavailable because Broken 3 0011'b 2839 Unknown 5 0101'b 2841 Non-Critical 2842 No Non-Critical Alerts 0 0000'b 2843 Non-Critical Alerts 8 1000'b 2845 Critical 2847 No Critical Alerts 0 0000'b 2848 Critical Alerts 16 1 0000'b 2850 On-Line 2852 State is On-Line 0 0000'b 2853 State is Off-Line 32 10 0000'b 2855 Transitioning 2857 At intended state 0 0000'b 2858 Transitioning to intended state 64 100 0000'b" 2860 SYNTAX INTEGER (0..126) 2862 PresentOnOff ::= TEXTUAL-CONVENTION 2863 -- This is a type 1 enumeration. 2864 STATUS current 2865 DESCRIPTION 2866 "Presence and configuration of a device or feature." 2867 SYNTAX INTEGER { 2868 other(1), 2869 on(3), 2870 off(4), 2871 notPresent(5) 2872 } 2874 PrtLocalizedDescriptionStringTC ::= TEXTUAL-CONVENTION 2875 -- This TC did not appear in RFC 1759. 2876 STATUS current 2877 DESCRIPTION 2878 "An object MUST use this textual convention when its 2879 'charset' is controlled by the value of 2880 prtGeneralCurrentLocalization." 2881 SYNTAX OCTET STRING (SIZE(0..255)) 2883 PrtConsoleDescriptionStringTC ::= TEXTUAL-CONVENTION 2884 -- This TC did not appear in RFC 1759. 2885 STATUS current 2886 DESCRIPTION 2887 "An object MUST use this textual convention when its 2888 'charset' is controlled by the value of 2889 prtConsoleLocalization." 2890 SYNTAX OCTET STRING (SIZE(0..255)) 2892 -- 2893 -- Channel Group textual-conventions 2894 -- 2896 PrtChannelStateTC ::= TEXTUAL-CONVENTION 2897 -- This value is a type 1 enumeration. This TC was extracted from 2898 -- prtChannelState in RFC 1759. 2899 STATUS current 2900 DESCRIPTION 2901 "The state of this print job delivery channel. The value 2902 determines whether print data is allowed through this channel." 2903 SYNTAX INTEGER { 2904 other(1), 2905 printDataAccepted(3), 2906 noDataAccepted(4) 2907 } 2909 -- 2910 -- Input/Output Group Textual Conventions 2911 -- 2913 PrtOutputStackingOrderTC ::= TEXTUAL-CONVENTION 2914 -- This is a type 1 enumeration. This TC was extracted from 2915 -- prtOutputStackingOrder in RFC 1759. 2916 STATUS current 2917 DESCRIPTION 2918 "The current state of the stacking order for the associated 2919 output sub-unit. 'firstToLast' means that as pages are output, 2920 the front of the next page is placed against the back of the 2921 previous page. 'lastToFirst' means that as pages are output, 2922 the back of the next page is placed against the front of the 2923 previous page." 2924 SYNTAX INTEGER { 2925 unknown(2), 2926 firstToLast(3), 2927 lastToFirst(4) 2928 } 2930 PrtOutputPageDeliveryOrientationTC ::= TEXTUAL-CONVENTION 2931 -- This is a type 1 enumeration. This TC was extracted from 2932 -- prtOutputPageDeliveryOrientation in RFC 1759. 2933 STATUS current 2934 DESCRIPTION 2935 "The reading surface that will be 'up' when pages are delivered 2936 to the associated output sub-unit. Values are Face-Up and Face 2937 Down (Note: interpretation of these values is, in general, 2938 context-dependent based on locale; presentation of these values 2939 to an end-user should be normalized to the expectations of the 2940 user." 2941 SYNTAX INTEGER { 2942 faceUp(3), 2943 faceDown(4) 2944 } 2946 -- 2947 -- Marker Group Textual Conventions 2948 -- 2950 PrtMarkerCounterUnitTC ::= TEXTUAL-CONVENTION 2951 -- This value is a type 1 enumeration. This TC was extracted from 2952 -- prtMarkerCounterUnit in RFC 1759. 2953 STATUS current 2954 DESCRIPTION 2955 "The unit that will be used by the printer when reporting 2956 counter values for this marking sub-unit. The 2957 time units of measure are provided for a device like a 2958 strip recorder that does not or cannot track the physical 2959 dimensions of the media and does not use characters, 2960 lines or sheets." 2962 SYNTAX INTEGER { 2963 tenThousandthsOfInches(3), -- .0001 2964 micrometers(4), 2965 characters(5), 2966 lines(6), 2967 impressions(7), 2968 sheets(8), 2969 dotRow(9), 2970 hours(11), 2971 feet(16), 2972 meters(17) 2973 } 2975 PrtMarkerSuppliesSupplyUnitTC ::= TEXTUAL-CONVENTION 2976 -- This value is a type 1 enumeration. This TC was extracted from 2977 -- prtMarkerSuppliesSupplyUnit in RFC 1759. 2978 STATUS current 2979 DESCRIPTION 2980 "Unit of this marker supply container/receptacle." 2981 SYNTAX INTEGER { 2982 other(1), -- New, not in RFC 1759 2983 unknown(2), -- New, not in RFC 1759 2984 tenThousandthsOfInches(3), -- .0001 2985 micrometers(4), 2986 impressions(7), -- New, not in RFC 1759 2987 sheets(8), -- New, not in RFC 1759 2988 hours(11), -- New, not in RFC 1759 2989 thousandthsOfOunces(12), 2990 tenthsOfGrams(13), 2991 hundrethsOfFluidOunces(14), 2992 tenthsOfMilliliters(15), 2993 feet(16), -- New, not in RFC 1759 2994 meters(17), -- New, not in RFC 1759 2995 -- Values for Finisher MIB 2996 items(18), -- e.g. #staples. New, not in RFC 1759 2997 percent(19) -- New, not in RFC 1759 2998 } 3000 PrtMarkerSuppliesClassTC ::= TEXTUAL-CONVENTION 3001 -- This value is a type 1 enumeration. This TC was extracted from 3002 -- prtMarkerSuppliesClass in RFC 1759. 3003 STATUS current 3004 DESCRIPTION 3005 "Indicates whether this supply entity represents a supply 3006 that is consumed or a receptacle that is filled." 3007 SYNTAX INTEGER { 3008 other(1), 3009 supplyThatIsConsumed(3), 3010 receptacleThatIsFilled(4) 3011 } 3013 PrtMarkerColorantRoleTC ::= TEXTUAL-CONVENTION 3014 -- This value is a type 1 enumeration. This TC was extracted from 3015 -- prtMarkerColorantRole in RFC 1759. 3016 STATUS current 3017 DESCRIPTION 3018 "The role played by this colorant." 3019 SYNTAX INTEGER { -- Colorant Role 3020 other(1), 3021 process(3), 3022 spot(4) 3023 } 3025 PrtMarkerAddressabilityUnitTC ::= TEXTUAL-CONVENTION 3026 -- This value is a type 1 enumeration. This TC was extracted from 3027 -- prtMarkerAddressabilityUnit in RFC 1759. 3028 STATUS current 3029 DESCRIPTION 3030 "The unit of measure of distances, as applied to the marker's 3031 resolution." 3032 SYNTAX INTEGER { 3033 tenThousandthsOfInches(3), -- .0001 3034 micrometers(4) 3035 } 3037 -- 3038 -- Media Path Textual Conventions 3039 -- 3041 PrtMediaPathMaxSpeedPrintUnitTC ::= TEXTUAL-CONVENTION 3042 -- This value is a type 1 enumeration. This TC was extracted from 3043 -- prtMediaPathMaxSpeedPrintUnit in RFC 1759. 3044 STATUS current 3045 DESCRIPTION 3046 "The unit of measure used in specifying the speed of all 3047 media paths in the printer." 3048 SYNTAX INTEGER { 3049 tenThousandthsOfInchesPerHour(3),-- .0001/hour 3050 micrometersPerHour(4), 3051 charactersPerHour(5), 3052 linesPerHour(6), 3053 impressionsPerHour(7), 3054 sheetsPerHour(8), 3055 dotRowPerHour(9), 3056 feetPerHour(16), 3057 metersPerHour(17) 3059 } 3061 -- 3062 -- Interpreter Group Textual Conventions 3063 -- 3065 PrtInterpreterTwoWayTC ::= TEXTUAL-CONVENTION 3066 -- This is a type 1 enumeration. This TC was extracted from 3067 -- prtInterpreterTwoWay in RFC 1759. 3068 STATUS current 3069 DESCRIPTION 3070 "Indicates whether or not this interpreter returns information 3071 back to the host." 3072 SYNTAX INTEGER { 3073 yes(3), 3074 no(4) 3075 } 3077 -- 3078 -- Alert Group Textual Conventions 3079 -- 3081 PrtAlertSeverityLevelTC ::= TEXTUAL-CONVENTION 3082 -- This value is a type 1 enumeration. This TC was extracted from 3083 -- prtAlertSeverityLevel in RFC 1759. 3084 STATUS current 3085 DESCRIPTION 3086 "The level of severity of this alert table entry. The printer 3087 determines the severity level assigned to each entry in the 3088 table. A critical alert is binary by nature and definition. A 3089 warning is defined to be a non-critical alert. The original and 3090 most common warning is unary. The binary warning was added later 3091 and given a more distinguished name." 3092 SYNTAX INTEGER { 3093 other(1), 3094 critical(3), 3095 warning(4), 3096 warningBinaryChangeEvent(5) -- New, not in RFC 1759 3097 } 3099 -- The General Printer Group 3100 -- 3101 -- The general printer sub-unit is responsible for the overall 3102 -- control and status of the printer. There is exactly one 3103 -- general printer sub-unit in a printer. 3105 prtGeneral OBJECT IDENTIFIER ::= { printmib 5 } 3107 prtGeneralTable OBJECT-TYPE 3108 SYNTAX SEQUENCE OF PrtGeneralEntry 3109 MAX-ACCESS not-accessible 3110 STATUS current 3111 DESCRIPTION 3112 "A table of general information per printer. 3113 Objects in this table are defined in various 3114 places in the MIB, nearby the groups to 3115 which they apply. They are all defined 3116 here to minimize the number of tables that would 3117 otherwise need to exist." 3118 ::= { prtGeneral 1 } 3120 prtGeneralEntry OBJECT-TYPE 3121 SYNTAX PrtGeneralEntry 3122 MAX-ACCESS not-accessible 3123 STATUS current 3124 DESCRIPTION 3125 "An entry exists in this table for each device entry in the 3126 host resources MIB device table with a device type of 3127 'printer'. 3129 NOTE: The above description has been modified from RFC 1759 3130 for clarification." 3131 INDEX { hrDeviceIndex } 3132 ::= { prtGeneralTable 1 } 3134 PrtGeneralEntry ::= SEQUENCE { 3135 -- Note that not all of the objects in this sequence are in 3136 -- the general printer group. The group to which an 3137 -- object belongs is tagged with a label "General", "Input" 3138 -- "Output", etc. after each entry in the following sequence. 3139 -- 3140 prtGeneralConfigChanges Counter32, -- General 3141 prtGeneralCurrentLocalization Integer32, -- General 3142 prtGeneralReset PrtGeneralResetTC, 3143 -- General 3144 prtGeneralCurrentOperator OCTET STRING, 3145 -- Responsible Party 3146 prtGeneralServicePerson OCTET STRING, 3147 -- Responsible Party 3148 prtInputDefaultIndex Integer32, -- Input 3149 prtOutputDefaultIndex Integer32, -- Output 3150 prtMarkerDefaultIndex Integer32, -- Marker 3151 prtMediaPathDefaultIndex Integer32, -- Media Path 3152 prtConsoleLocalization Integer32, -- Console 3153 prtConsoleNumberOfDisplayLines Integer32, -- Console 3154 prtConsoleNumberOfDisplayChars Integer32, -- Console 3155 prtConsoleDisable PrtConsoleDisableTC, 3156 -- Console, 3157 prtAuxiliarySheetStartupPage PresentOnOff, 3158 -- AuxiliarySheet 3159 prtAuxiliarySheetBannerPage PresentOnOff, 3160 -- AuxiliarySheet 3161 prtGeneralPrinterName OCTET STRING, 3162 -- General V2 3163 prtGeneralSerialNumber OCTET STRING, 3164 -- General V2 3165 prtAlertCriticalEvents Counter32, -- Alert V2 3166 prtAlertAllEvents Counter32 -- Alert V2 3167 } 3169 prtGeneralConfigChanges OBJECT-TYPE 3170 SYNTAX Counter32 3171 MAX-ACCESS read-only 3172 STATUS current 3173 DESCRIPTION 3174 "Counts configuration changes within the printer. A 3175 configuration change is defined to be an action that results in 3176 a change to any MIB object other than those that reflect status 3177 or level, or those that act as counters or gauges. In addition, 3178 any action that results in a row being added or deleted from 3179 any table in the Printer MIB is considered a configuration 3180 change. Such changes will often affect the capability of the 3181 printer to service certain types of print jobs. Management 3182 applications may cache infrequently changed configuration 3183 information about sub units within the printer. This object 3184 should be incremented whenever the agent wishes to notify 3185 management applications that any cached configuration 3186 information for this device is to be considered 'stale'. At 3187 this point, the management application should flush any 3188 configuration information cached about this device and fetch 3189 new configuration information. 3191 The following are examples of actions that would cause the 3192 prtGeneralConfigChanges object to be incremented: 3194 - Adding an output bin 3195 - Changing the media in a sensing input tray 3196 - Changing the value of prtInputMediaType 3198 Note that the prtGeneralConfigChanges counter would not be 3199 incremented when an input tray is temporarily removed to load 3200 additional paper or when the level of an input device changes. 3202 NOTE: The above description has been modified from RFC 1759 3203 for clarification." 3205 ::= { prtGeneralEntry 1 } 3207 prtGeneralCurrentLocalization OBJECT-TYPE 3208 SYNTAX Integer32 (1..65535) 3209 MAX-ACCESS read-write 3210 STATUS current 3211 DESCRIPTION 3212 "The value of the prtLocalizationIndex corresponding to the 3213 current language, country, and character set to be used for 3214 localized string values that are identified as being dependent 3215 on the value of this object. Note that this object does not 3216 apply to localized strings in the prtConsole group or to any 3217 object that is not explicitly identified as being localized 3218 according to prtGeneralCurrentLocalization. When an object's 3219 'charset' is controlled by the value of 3220 prtGeneralCurrentLocalization, it MUST specify 3221 PrtLocalizedDescriptionStringTC as its syntax. 3223 NOTE: The above description has been modified from RFC 1759 3224 for clarification." 3225 ::= { prtGeneralEntry 2 } 3227 prtGeneralReset OBJECT-TYPE 3228 -- NOTE: In RFC 1759, the enumeration values were implicitly defined 3229 -- by this object. 3230 SYNTAX PrtGeneralResetTC 3231 MAX-ACCESS read-write 3232 STATUS current 3233 DESCRIPTION 3234 "Setting this value to 'powerCycleReset', 'resetToNVRAM', or 3235 'resetToFactoryDefaults' will result in the resetting of the 3236 printer. When read, this object will always have the value 3237 'notResetting(3)', and a SET of the value 'notResetting' shall 3238 have no effect on the printer. Some of the defined values are 3239 optional. However, every implementation must support at least 3240 the values 'notResetting' and 'resetToNVRAM'." 3241 ::= { prtGeneralEntry 3 } 3243 -- The Responsible Party group 3245 prtGeneralCurrentOperator OBJECT-TYPE 3246 SYNTAX OCTET STRING (SIZE(0..127)) 3247 MAX-ACCESS read-write 3248 STATUS current 3249 DESCRIPTION 3250 "The name of the person who is responsible for operating 3251 this printer. It is suggested that this string include 3252 information that would enable other humans to reach the 3253 operator, such as a phone number. As a convention to 3254 facilitate automatic notification of the operator by the 3255 agent or network management station, the phone number, 3256 fax number or email address should be indicated by the 3257 URL schemes 'tel:', 'fax:' and 'mailto:', respectively. 3258 If either the phone, fax, or email information is not 3259 available, then a line should not be included for this 3260 information. 3262 NOTE: For interoperability purposes, it is advisable to 3263 use email addresses formatted according to [RFC2822] 3264 requirements. 3266 NOTE: The above description has been modified from RFC 1759 3267 for clarification." 3268 ::= { prtGeneralEntry 4 } 3270 prtGeneralServicePerson OBJECT-TYPE 3271 SYNTAX OCTET STRING (SIZE(0..127)) 3272 MAX-ACCESS read-write 3273 STATUS current 3274 DESCRIPTION 3275 "The name of the person responsible for servicing this 3276 printer. It is suggested that this string include 3277 information that would enable other humans to reach the 3278 service person, such as a phone number. As a convention 3279 to facilitate automatic notification of the operator by 3280 the agent or network management station, the phone 3281 number, fax number or email address should be indicated 3282 by the URL schemes 'tel:', 'fax:' and 'mailto:', 3283 respectively. If either the phone, fax, or email 3284 information is not available, then a line should not 3285 be included for this information. 3287 NOTE: For interoperability purposes, it is advisable to use 3288 email addresses formatted per [RFC2822] requirements. 3290 NOTE: The above description has been modified from RFC 1759 3291 for clarification." 3293 ::= { prtGeneralEntry 5 } 3295 -- Default indexes section 3296 -- 3297 -- The following four objects are used to specify the indexes of 3298 -- certain subunits used as defaults during the printing process. 3300 prtInputDefaultIndex OBJECT-TYPE 3301 SYNTAX Integer32 (1..65535) 3302 MAX-ACCESS read-write 3303 STATUS current 3304 DESCRIPTION 3305 "The value of prtInputIndex corresponding to the default input 3306 sub-unit: that is, this object selects the default source of 3307 input media." 3308 ::= { prtGeneralEntry 6 } 3310 prtOutputDefaultIndex OBJECT-TYPE 3311 -- A range has been added to the SYNTAX clause that was not in 3312 -- RFC 1759. Although this violates SNMP compatibility rules, 3313 -- it provides a more reasonable guide for SNMP managers. 3314 SYNTAX Integer32 (1..65535) 3315 MAX-ACCESS read-write 3316 STATUS current 3317 DESCRIPTION 3318 "The value of prtOutputIndex corresponding to the default 3319 output sub-unit; that is, this object selects the default 3320 output destination." 3321 ::= { prtGeneralEntry 7 } 3323 prtMarkerDefaultIndex OBJECT-TYPE 3324 SYNTAX Integer32 (1..65535) 3325 MAX-ACCESS read-write 3326 STATUS current 3327 DESCRIPTION 3328 "The value of prtMarkerIndex corresponding to the 3329 default marker sub-unit; that is, this object selects the 3330 default marker." 3331 ::= { prtGeneralEntry 8 } 3333 prtMediaPathDefaultIndex OBJECT-TYPE 3334 SYNTAX Integer32 (1..65535) 3335 MAX-ACCESS read-write 3336 STATUS current 3337 DESCRIPTION 3338 "The value of prtMediaPathIndex corresponding to 3339 the default media path; that is, the selection of the 3340 default media path." 3341 ::= { prtGeneralEntry 9 } 3343 -- Console general section 3344 -- 3345 -- The following four objects describe overall parameters of the 3346 -- printer console subsystem. 3348 prtConsoleLocalization OBJECT-TYPE 3349 SYNTAX Integer32 (1..65535) 3350 MAX-ACCESS read-write 3351 STATUS current 3352 DESCRIPTION 3353 "The value of the prtLocalizationIndex corresponding to 3354 the language, country, and character set to be used for the 3355 console. This localization applies both to the actual display 3356 on the console as well as the encoding of these console objects 3357 in management operations. When an object's 'charset' is 3358 controlled by the value of prtConsoleLocalization, it MUST 3359 specify PrtConsoleDescriptionStringTC as its syntax. 3361 NOTE: The above description has been modified from RFC 1759 3362 for clarification." 3363 ::= { prtGeneralEntry 10 } 3365 prtConsoleNumberOfDisplayLines OBJECT-TYPE 3366 SYNTAX Integer32 (0..65535) 3367 MAX-ACCESS read-only 3368 STATUS current 3369 DESCRIPTION 3370 "The number of lines on the printer's physical 3371 display. This value is 0 if there are no lines on the 3372 physical display or if there is no physical display" 3373 ::= { prtGeneralEntry 11 } 3375 prtConsoleNumberOfDisplayChars OBJECT-TYPE 3376 SYNTAX Integer32 (0..65535) 3377 MAX-ACCESS read-only 3378 STATUS current 3379 DESCRIPTION 3380 "The number of characters per line displayed on the physical 3381 display. This value is 0 if there are no lines on the physical 3382 display or if there is no physical display" 3383 ::= { prtGeneralEntry 12 } 3385 prtConsoleDisable OBJECT-TYPE 3386 -- In RFC 1759, the enumeration values were implicitly defined 3387 -- by this object. 3388 SYNTAX PrtConsoleDisableTC 3389 MAX-ACCESS read-write 3390 STATUS current 3391 DESCRIPTION 3392 "This value indicates how input is (or is not) accepted from 3393 the operator console. 3395 NOTE: The above description has been modified from RFC 1759 3396 for clarification." 3397 ::= { prtGeneralEntry 13 } 3399 -- The Auxiliary Sheet Group 3400 -- 3401 -- The auxiliary sheet group allows the administrator to control 3402 -- the production of auxiliary sheets by the printer. This group 3403 -- contains only the "prtAuxiliarySheetStartupPage" and 3404 -- "prtAuxiliarySheetBannerPage" objects. 3406 prtAuxiliarySheetStartupPage OBJECT-TYPE 3407 SYNTAX PresentOnOff 3408 MAX-ACCESS read-write 3409 STATUS current 3410 DESCRIPTION 3411 "Used to enable or disable printing a startup page. If enabled, 3412 a startup page will be printed shortly after power-up, when the 3413 device is ready. Typical startup pages include test patterns 3414 and/or printer configuration information." 3415 ::= { prtGeneralEntry 14 } 3417 prtAuxiliarySheetBannerPage OBJECT-TYPE 3418 SYNTAX PresentOnOff 3419 MAX-ACCESS read-write 3420 STATUS current 3421 DESCRIPTION 3422 "Used to enable or disable printing banner pages at the 3423 beginning of jobs. This is a master switch which applies to all 3424 jobs, regardless of interpreter." 3425 ::= { prtGeneralEntry 15 } 3427 -- Administrative section (The General V2 Group) 3428 -- 3429 -- The following two objects are used to specify administrative 3430 -- information assigned to the printer. 3432 prtGeneralPrinterName OBJECT-TYPE 3433 SYNTAX OCTET STRING (SIZE (0..127)) 3434 MAX-ACCESS read-write 3435 STATUS current 3436 DESCRIPTION 3437 "An administrator-specified name for this printer. Depending 3438 upon implementation of this printer, the value of this object 3439 may or may not be same as the value for the MIB-II 'SysName' 3440 object." 3441 ::= { prtGeneralEntry 16 } 3443 prtGeneralSerialNumber OBJECT-TYPE 3444 SYNTAX OCTET STRING (SIZE (0..255)) 3445 MAX-ACCESS read-write 3446 STATUS current 3447 DESCRIPTION 3448 "A recorded serial number for this device that indexes some 3449 type device catalog or inventory. This value is usually set by 3450 the device manufacturer but the MIB supports the option of 3451 writing for this object for site-specific administration of 3452 device inventory or tracking." 3453 ::= { prtGeneralEntry 17 } 3455 -- General alert table section (Alert Table V2 Group) 3456 -- 3457 -- The following two objects are used to specify counters 3458 -- associated with the Alert Table. 3460 prtAlertCriticalEvents OBJECT-TYPE 3461 SYNTAX Counter32 3462 MAX-ACCESS read-only 3463 STATUS current 3464 DESCRIPTION 3465 "A running counter of the number of critical alert events that 3466 have been recorded in the alert table. The value of this object 3467 is RESET in the event of a power cycle operation (i.e., the 3468 value is not persistent." 3469 ::= { prtGeneralEntry 18 } 3471 prtAlertAllEvents OBJECT-TYPE 3472 SYNTAX Counter32 3473 MAX-ACCESS read-only 3474 STATUS current 3475 DESCRIPTION 3476 "A running counter of the total number of alert event entries 3477 (critical and non-critical) that have been recorded in the 3478 alert table" 3479 ::= { prtGeneralEntry 19 } 3481 -- The Cover Table 3482 -- 3483 -- The cover portion of the General print sub-unit describes the 3484 -- covers and interlocks of the printer. The Cover Table has an 3485 -- entry for each cover and interlock. 3487 prtCover OBJECT IDENTIFIER ::= { printmib 6 } 3489 prtCoverTable OBJECT-TYPE 3490 SYNTAX SEQUENCE OF PrtCoverEntry 3491 MAX-ACCESS not-accessible 3492 STATUS current 3493 DESCRIPTION 3494 "A table of the covers and interlocks of the printer." 3495 ::= { prtCover 1 } 3497 prtCoverEntry OBJECT-TYPE 3498 SYNTAX PrtCoverEntry 3499 MAX-ACCESS not-accessible 3500 STATUS current 3501 DESCRIPTION 3502 "Information about a cover or interlock. 3503 Entries may exist in the table for each device 3504 index with a device type of 'printer'. 3506 NOTE: The above description has been modified from RFC 1759 3507 for clarification." 3508 INDEX { hrDeviceIndex, prtCoverIndex } 3509 ::= { prtCoverTable 1 } 3511 PrtCoverEntry ::= SEQUENCE { 3512 prtCoverIndex Integer32, 3513 prtCoverDescription PrtLocalizedDescriptionStringTC, 3514 prtCoverStatus PrtCoverStatusTC 3515 } 3517 prtCoverIndex OBJECT-TYPE 3518 SYNTAX Integer32 (1..65535) 3519 MAX-ACCESS not-accessible 3520 STATUS current 3521 DESCRIPTION 3522 "A unique value used by the printer to identify this Cover sub 3523 unit. Although these values may change due to a major 3524 reconfiguration of the device (e.g. the addition of new cover 3525 sub-units to the printer), values SHOULD remain stable across 3526 successive printer power cycles. 3528 NOTE: The above description has been modified from RFC 1759 3529 for clarification." 3530 ::= { prtCoverEntry 1 } 3532 prtCoverDescription OBJECT-TYPE 3533 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 3534 -- to a TC to better support localization of the object. 3535 SYNTAX PrtLocalizedDescriptionStringTC 3536 MAX-ACCESS read-only 3537 STATUS current 3538 DESCRIPTION 3539 "The manufacturer provided cover sub-mechanism name in the 3540 localization specified by prtGeneralCurrentLocalization." 3541 ::= { prtCoverEntry 2 } 3543 prtCoverStatus OBJECT-TYPE 3544 -- NOTE: In RFC 1759, the enumeration values were implicitly defined 3545 -- by this object. 3546 SYNTAX PrtCoverStatusTC 3547 MAX-ACCESS read-only 3548 STATUS current 3549 DESCRIPTION 3550 "The status of this cover sub-unit." 3551 ::= { prtCoverEntry 3 } 3553 -- The Localization Table 3554 -- 3555 -- The localization portion of the General printer sub-unit is 3556 -- responsible for identifying the natural language, country, and 3557 -- character set in which character strings are expressed. There 3558 -- may be one or more localizations supported per printer. The 3559 -- available localizations are represented by the Localization 3560 -- table. 3562 prtLocalization OBJECT IDENTIFIER ::= { printmib 7 } 3564 prtLocalizationTable OBJECT-TYPE 3565 SYNTAX SEQUENCE OF PrtLocalizationEntry 3566 MAX-ACCESS not-accessible 3567 STATUS current 3568 DESCRIPTION 3569 "The available localizations in this printer." 3570 ::= { prtLocalization 1 } 3572 prtLocalizationEntry OBJECT-TYPE 3573 SYNTAX PrtLocalizationEntry 3574 MAX-ACCESS not-accessible 3575 STATUS current 3576 DESCRIPTION 3577 "A description of a localization. 3578 Entries may exist in the table for each device 3579 index with a device type of 'printer'. 3581 NOTE: The above description has been modified from RFC 1759 3582 for clarification." 3583 INDEX { hrDeviceIndex, prtLocalizationIndex } 3584 ::= { prtLocalizationTable 1 } 3586 PrtLocalizationEntry ::= SEQUENCE { 3587 prtLocalizationIndex Integer32, 3588 prtLocalizationLanguage OCTET STRING, 3589 prtLocalizationCountry OCTET STRING, 3590 prtLocalizationCharacterSet IANACharset 3591 } 3593 prtLocalizationIndex OBJECT-TYPE 3594 SYNTAX Integer32 (1..65535) 3595 MAX-ACCESS not-accessible 3596 STATUS current 3597 DESCRIPTION 3598 "A unique value used by the printer to identify this 3599 localization entry. Although these values may change due to a 3600 major reconfiguration of the device (e.g., the addition of new 3601 localization data to the printer), values SHOULD remain 3602 stable across successive printer power cycles. 3604 NOTE: The above description has been modified from RFC 1759 3605 for clarification." 3606 ::= { prtLocalizationEntry 1 } 3608 prtLocalizationLanguage OBJECT-TYPE 3609 -- Note: The size is fixed, was incorrectly 0..2 in RFC 1759. 3610 SYNTAX OCTET STRING (SIZE(2)) 3611 MAX-ACCESS read-only 3612 STATUS current 3613 DESCRIPTION 3614 "A two character language code from ISO 639. Examples en, 3615 es, fr, de. NOTE: These examples were shown as upper case in 3616 RFC 1759 and are now shown as lower case to agree with ISO 639." 3617 ::= { prtLocalizationEntry 2 } 3619 prtLocalizationCountry OBJECT-TYPE 3620 -- Note: The size is fixed, was incorrectly 0..2 in RFC 1759. 3621 SYNTAX OCTET STRING (SIZE(2)) 3622 MAX-ACCESS read-only 3623 STATUS current 3624 DESCRIPTION 3625 "A two character country code from ISO 3166, a blank string 3626 (two space characters) shall indicate that the country is not 3627 defined. Examples: US, GB, FR, DE, ..." 3628 ::= { prtLocalizationEntry 3 } 3630 prtLocalizationCharacterSet OBJECT-TYPE 3631 SYNTAX IANACharset 3632 MAX-ACCESS read-only 3633 STATUS current 3634 DESCRIPTION 3635 "The coded character set used for this localization." 3636 ::= { prtLocalizationEntry 4 } 3638 -- The System Resources Tables 3639 -- 3640 -- The Printer MIB makes use of the Host Resources MIB to 3641 -- define system resources by referencing the storage 3642 -- and device groups of the print group. 3644 prtStorageRefTable OBJECT-TYPE 3645 SYNTAX SEQUENCE OF PrtStorageRefEntry 3646 MAX-ACCESS not-accessible 3647 STATUS current 3648 DESCRIPTION 3649 "This table defines which printer, amongst multiple printers 3650 serviced by one agent, owns which storage units. 3652 NOTE: The above description has been modified from RFC 1759 3653 for clarification." 3654 ::= { prtGeneral 2 } 3656 prtStorageRefEntry OBJECT-TYPE 3657 SYNTAX PrtStorageRefEntry 3658 MAX-ACCESS not-accessible 3659 STATUS current 3660 DESCRIPTION 3661 "This table will have an entry for each entry in the Host 3662 Resources MIB storage table that represents storage associated 3663 with a printer managed by this agent. 3665 NOTE: The above description has been modified from RFC 1759 3666 for clarification." 3667 INDEX { hrStorageIndex, prtStorageRefSeqNumber } 3668 ::= { prtStorageRefTable 1 } 3670 PrtStorageRefEntry ::= SEQUENCE { 3671 prtStorageRefSeqNumber Integer32, 3672 prtStorageRefIndex Integer32 3673 } 3675 prtStorageRefSeqNumber OBJECT-TYPE 3676 -- NOTE: The range has been changed from RFC 1759, which allowed a 3677 -- minumum value of zero. This was incorrect, since zero is not a 3678 -- valid index. 3679 SYNTAX Integer32 (1..65535) 3680 MAX-ACCESS not-accessible 3681 STATUS current 3682 DESCRIPTION 3683 "This value will be unique amongst all entries with a common 3684 value of hrStorageIndex. This object allows a storage entry to 3685 point to the multiple printer devices with which it is 3686 associated." 3687 ::= { prtStorageRefEntry 1 } 3689 prtStorageRefIndex OBJECT-TYPE 3690 -- NOTE: The range has been changed from RFC 1759 to be compatible 3691 -- with the defined range of hrDeviceIndex. 3692 SYNTAX Integer32 (0..2147483647) 3693 MAX-ACCESS read-only 3694 STATUS current 3695 DESCRIPTION 3696 "The value of the hrDeviceIndex of the printer device that this 3697 storageEntry is associated with." 3698 ::= { prtStorageRefEntry 2 } 3700 prtDeviceRefTable OBJECT-TYPE 3701 SYNTAX SEQUENCE OF PrtDeviceRefEntry 3702 MAX-ACCESS not-accessible 3703 STATUS current 3704 DESCRIPTION 3705 "This table defines which printer, amongst multiple printers 3706 serviced by one agent, is associated with which devices. 3708 NOTE: The above description has been modified from RFC 1759 3709 for clarification." 3710 ::= { prtGeneral 3 } 3712 prtDeviceRefEntry OBJECT-TYPE 3713 SYNTAX PrtDeviceRefEntry 3714 MAX-ACCESS not-accessible 3715 STATUS current 3716 DESCRIPTION 3717 "This table will have an entry for each entry in the Host 3718 Resources MIB device table that represents a device associated 3719 with a printer managed by this agent. 3721 NOTE: The above description has been modified from RFC 1759 3722 for clarification." 3723 INDEX { hrDeviceIndex, prtDeviceRefSeqNumber } 3724 ::= { prtDeviceRefTable 1 } 3726 PrtDeviceRefEntry ::= SEQUENCE { 3727 prtDeviceRefSeqNumber Integer32, 3728 prtDeviceRefIndex Integer32 3729 } 3731 prtDeviceRefSeqNumber OBJECT-TYPE 3732 -- NOTE: The range has been changed from RFC 1759, which allowed a 3733 -- minumum value of zero. This was incorrect, since zero is not a 3734 -- valid index. 3735 SYNTAX Integer32 (1..65535) 3736 MAX-ACCESS not-accessible 3737 STATUS current 3738 DESCRIPTION 3739 "This value will be unique amongst all entries with a common 3740 value of hrDeviceIndex. This object allows a device entry to 3741 point to the multiple printer devices with which it is 3742 associated." 3743 ::= { prtDeviceRefEntry 1 } 3745 prtDeviceRefIndex OBJECT-TYPE 3746 -- NOTE: The range has been changed from RFC 1759 to be compatible 3747 -- with the defined range of hrDeviceIndex. 3748 SYNTAX Integer32 (0..2147483647) 3749 MAX-ACCESS read-only 3750 STATUS current 3751 DESCRIPTION 3752 "The value of the hrDeviceIndex of the printer device that this 3753 deviceEntry is associated with." 3754 ::= { prtDeviceRefEntry 2 } 3756 -- The Input Group 3757 -- 3758 -- Input sub-units are managed as a tabular, indexed collection 3759 -- of possible devices capable of providing media for input to 3760 -- the printing process. Input sub-units typically have a 3761 -- location, a type, an identifier, a set of constraints on 3762 -- possible media sizes and potentially other media 3763 -- characteristics, and may be capable of indicating current 3764 -- status or capacity. 3766 prtInput OBJECT IDENTIFIER ::= { printmib 8 } 3768 prtInputTable OBJECT-TYPE 3769 SYNTAX SEQUENCE OF PrtInputEntry 3770 MAX-ACCESS not-accessible 3771 STATUS current 3772 DESCRIPTION 3773 "A table of the devices capable of providing media for input to 3774 the printing process." 3775 ::= { prtInput 2 } 3777 prtInputEntry OBJECT-TYPE 3778 SYNTAX PrtInputEntry 3779 MAX-ACCESS not-accessible 3780 STATUS current 3781 DESCRIPTION 3782 "Attributes of a device capable of providing media for input to 3783 the printing process. Entries may exist in the table for each 3784 device index with a device type of 'printer'. 3786 NOTE: The above description has been modified from RFC 1759 3787 for clarification." 3788 INDEX { hrDeviceIndex, prtInputIndex } 3789 ::= { prtInputTable 1 } 3791 PrtInputEntry ::= SEQUENCE { 3792 prtInputIndex Integer32, 3793 prtInputType PrtInputTypeTC, 3794 prtInputDimUnit PrtMediaUnitTC, 3795 prtInputMediaDimFeedDirDeclared Integer32, 3796 prtInputMediaDimXFeedDirDeclared Integer32, 3797 prtInputMediaDimFeedDirChosen Integer32, 3798 prtInputMediaDimXFeedDirChosen Integer32, 3799 prtInputCapacityUnit PrtCapacityUnitTC, 3800 prtInputMaxCapacity Integer32, 3801 prtInputCurrentLevel Integer32, 3802 prtInputStatus PrtSubUnitStatusTC, 3803 prtInputMediaName OCTET STRING, 3804 prtInputName OCTET STRING, 3805 prtInputVendorName OCTET STRING, 3806 prtInputModel OCTET STRING, 3807 prtInputVersion OCTET STRING, 3808 prtInputSerialNumber OCTET STRING, 3809 prtInputDescription PrtLocalizedDescriptionStringTC, 3810 prtInputSecurity PresentOnOff, 3811 prtInputMediaWeight Integer32, 3812 prtInputMediaType OCTET STRING, 3813 prtInputMediaColor OCTET STRING, 3814 prtInputMediaFormParts Integer32, 3815 prtInputMediaLoadTimeout Integer32, 3816 prtInputNextIndex Integer32 3817 } 3819 prtInputIndex OBJECT-TYPE 3820 SYNTAX Integer32 (1..65535) 3821 MAX-ACCESS not-accessible 3822 STATUS current 3823 DESCRIPTION 3824 "A unique value used by the printer to identify this input 3825 sub-unit. Although these values may change due to a major 3826 reconfiguration of the device (e.g. the addition of new input 3827 sub-units to the printer), values SHOULD remain stable across 3828 successive printer power cycles. 3830 NOTE: The above description has been modified from RFC 1759 3831 for clarification." 3832 ::= { prtInputEntry 1 } 3834 prtInputType OBJECT-TYPE 3835 -- NOTE: In RFC 1759, the enumeration values were implicitly 3836 -- defined by this object. 3837 SYNTAX PrtInputTypeTC 3838 MAX-ACCESS read-only 3839 STATUS current 3840 DESCRIPTION 3841 "The type of technology (discriminated primarily according to 3842 feeder mechanism type) employed by the input sub-unit. Note, 3843 the Input Class provides for a descriptor field to further 3844 qualify the other choice." 3845 ::= { prtInputEntry 2 } 3847 prtInputDimUnit OBJECT-TYPE 3848 SYNTAX PrtMediaUnitTC 3849 MAX-ACCESS read-only 3850 STATUS current 3851 DESCRIPTION 3852 "The unit of measurement for use calculating and relaying 3853 dimensional values for this input sub-unit." 3854 ::= { prtInputEntry 3 } 3856 prtInputMediaDimFeedDirDeclared OBJECT-TYPE 3857 -- NOTE: In RFC 1759, the range was not defined. 3858 SYNTAX Integer32 (-2..2147483647) 3859 MAX-ACCESS read-write 3860 STATUS current 3861 DESCRIPTION 3862 "This object provides the value of the declared dimension, in 3863 the feed direction, of the media that is (or, if empty, was or 3864 will be) in this input sub-unit. The feed direction is the 3865 direction in which the media is fed on this sub-unit. This 3866 dimension is measured in input sub-unit dimensional units 3867 (controlled by prtInputDimUnit, which uses PrtMediaUnitTC). If 3868 this input sub-unit can reliably sense this value, the value is 3869 sensed by the printer and may not be changed by management 3870 requests. Otherwise, the value may be changed. The value (-1) 3871 means other and specifically means that this sub-unit places no 3872 restriction on this parameter. The value (-2) indicates 3873 unknown." 3874 ::= { prtInputEntry 4 } 3876 prtInputMediaDimXFeedDirDeclared OBJECT-TYPE 3877 -- NOTE: In RFC 1759, the range was not defined. 3878 SYNTAX Integer32 (-2..2147483647) 3879 MAX-ACCESS read-write 3880 STATUS current 3881 DESCRIPTION 3882 "This object provides the value of the declared dimension, in 3883 the cross feed direction, of the media that is (or, if empty, 3884 was or will be) in this input sub-unit. The cross feed 3885 direction is ninety degrees relative to the feed direction 3886 associated with this sub-unit. This dimension is measured in 3887 input sub-unit dimensional units (controlled by 3888 prtInputDimUnit,which uses PrtMediaUnitTC). If this input sub- 3889 unit can reliably sense this value, the value is sensed by the 3890 printer and may not be changed by management requests. 3891 Otherwise, the value may be changed. The value (-1) means other 3892 and specifically means that this sub-unit places no restriction 3893 on this parameter. The value (-2) indicates unknown." 3894 ::= { prtInputEntry 5 } 3896 prtInputMediaDimFeedDirChosen OBJECT-TYPE 3897 -- NOTE: In RFC 1759, the range was not defined. 3898 SYNTAX Integer32 (-2..2147483647) 3899 MAX-ACCESS read-only 3900 STATUS current 3901 DESCRIPTION 3902 "The printer will act as if media of the chosen dimension (in 3903 the feed direction) is present in this input source. Note that 3904 this value will be used even if the input tray is empty. Feed 3905 dimension measurements are taken relative to the feed direction 3906 associated with that sub-unit and are in input sub-unit 3907 dimensional units (controlled by prtInputDimUnit, which uses 3908 PrtMediaUnitTC). If the printer supports the declared 3909 dimension,the granted dimension is the same as the declared 3910 dimension. If not, the granted dimension is set to the closest 3911 dimension that the printer supports when the declared dimension 3912 is set. The value (-1) means other and specifically indicates 3913 that this sub-unit places no restriction on this parameter. The 3914 value (-2)indicates unknown." 3915 ::= { prtInputEntry 6 } 3917 prtInputMediaDimXFeedDirChosen OBJECT-TYPE 3918 -- NOTE: In RFC 1759, the range was not defined. 3919 SYNTAX Integer32 (-2..2147483647) 3920 MAX-ACCESS read-only 3921 STATUS current 3922 DESCRIPTION 3923 "The printer will act as if media of the chosen dimension (in 3924 the cross feed direction) is present in this input source. Note 3925 that this value will be used even if the input tray is empty. 3926 The cross feed direction is ninety degrees relative to the feed 3927 direction associated with this sub-unit. This dimension is 3928 measured in input sub-unit dimensional units (controlled by 3929 prtInputDimUnit, which uses PrtMediaUnitTC). If the printer 3930 supports the declare dimension, the granted dimension is the 3931 same as the declared dimension. If not, the granted dimension 3932 is set to the closest dimension that the printer supports when 3933 the declared dimension is set. The value (-1) means other and 3934 specifically indicates that this sub-unit places no restriction 3935 on this parameter. The value (-2) indicates unknown." 3936 ::= { prtInputEntry 7 } 3938 prtInputCapacityUnit OBJECT-TYPE 3939 -- NOTE: In RFC 1759, the enumeration values were implicitly 3940 -- defined by this object. 3941 SYNTAX PrtCapacityUnitTC 3942 MAX-ACCESS read-only 3943 STATUS current 3944 DESCRIPTION 3945 "The unit of measurement for use in calculating and relaying 3946 capacity values for this input sub-unit." 3947 ::= { prtInputEntry 8 } 3949 prtInputMaxCapacity OBJECT-TYPE 3950 -- NOTE: In RFC 1759, the range was not defined. 3951 SYNTAX Integer32 (-2..2147483647) 3952 MAX-ACCESS read-write 3953 STATUS current 3954 DESCRIPTION 3955 "The maximum capacity of the input sub-unit in input sub-unit 3956 capacity units (PrtCapacityUnitTC). There is no convention 3957 associated with the media itself so this value reflects claimed 3958 capacity. If this input sub-unit can reliably sense this value, 3959 the value is sensed by the printer and may not be changed by 3960 management requests; otherwise, the value may be written (by a 3961 Remote Control Panel or a Management Application). The value 3962 (-1) means other and specifically indicates that the sub-unit 3963 places no restrictions on this parameter. The value (-2) means 3964 unknown." 3965 ::= { prtInputEntry 9 } 3967 prtInputCurrentLevel OBJECT-TYPE 3968 -- NOTE: In RFC 1759, the range was not defined. 3969 SYNTAX Integer32 (-3..2147483647) -- in capacity units 3970 -- (PrtCapacityUnitTC). 3971 MAX-ACCESS read-write 3972 STATUS current 3973 DESCRIPTION 3974 "The current capacity of the input sub-unit in input sub-unit 3975 capacity units (PrtCapacityUnitTC). If this input sub-unit can 3976 reliably sense this value, the value is sensed by the printer 3977 and may not be changed by management requests; otherwise, the 3978 value may be written (by a Remote Control Panel or a Management 3979 Application). The value (-1) means other and specifically 3980 indicates that the sub-unit places no restrictions on this 3981 parameter. The value (-2) means unknown. The value (-3) means 3982 that the printer knows that at least one unit remains." 3983 ::= { prtInputEntry 10 } 3985 prtInputStatus OBJECT-TYPE 3986 SYNTAX PrtSubUnitStatusTC 3987 MAX-ACCESS read-only 3988 STATUS current 3989 DESCRIPTION 3990 "The current status of this input sub-unit." 3991 ::= { prtInputEntry 11 } 3993 prtInputMediaName OBJECT-TYPE 3994 SYNTAX OCTET STRING (SIZE(0..63)) 3995 MAX-ACCESS read-write 3996 STATUS current 3997 DESCRIPTION 3998 "A description of the media contained in this input sub-unit; 3999 This description is to be used by a client to format and 4000 Localize a string for display to a human operator. This 4001 description is not processed by the printer. It is used to 4002 provide information not expressible in terms of the other 4003 media attributes (e.g. prtInputMediaDimFeedDirChosen, 4004 prtInputMediaDimXFeedDirChosen, prtInputMediaWeight, 4005 prtInputMediaType)." 4006 -- The following reference was not included in RFC 1759. 4007 REFERENCE 4008 "The PWG Standardized Media Names specification [PWGMEDIA] 4009 contains the recommended values for this object. See also 4010 RFC XXXX Appendix C,'Media Names', which lists the values 4011 Of standardized media names defined in ISO/IEC 10175. 4012 RFC Editor: Replace XXXX with the number assigned to this document." 4013 ::= { prtInputEntry 12 } 4015 -- INPUT MEASUREMENT 4016 -- 4017 -- _______ | | 4018 -- ^ | | 4019 -- | | | | 4020 -- | |_ _ _ _ _ _ _ _| _______________ |direction 4021 -- | | | ^ v 4022 -- MaxCapacity | Sheets | | 4023 -- | | left | CurrentLevel 4024 -- | | in | | 4025 -- v | tray | v 4026 -- _______ +_______________+ _______ 4028 -- The Extended Input Group 4030 prtInputName OBJECT-TYPE 4031 SYNTAX OCTET STRING (SIZE(0..63)) 4032 MAX-ACCESS read-write 4033 STATUS current 4034 DESCRIPTION 4035 "The name assigned to this input sub-unit." 4036 ::= { prtInputEntry 13 } 4038 prtInputVendorName OBJECT-TYPE 4039 SYNTAX OCTET STRING (SIZE(0..63)) 4040 MAX-ACCESS read-only 4041 STATUS current 4042 DESCRIPTION 4043 "The vendor name of this input sub-unit." 4044 ::= { prtInputEntry 14 } 4046 prtInputModel OBJECT-TYPE 4047 SYNTAX OCTET STRING (SIZE(0..63)) 4048 MAX-ACCESS read-only 4049 STATUS current 4050 DESCRIPTION 4051 "The model name of this input sub-unit." 4052 ::= { prtInputEntry 15 } 4054 prtInputVersion OBJECT-TYPE 4055 SYNTAX OCTET STRING (SIZE(0..63)) 4056 MAX-ACCESS read-only 4057 STATUS current 4058 DESCRIPTION 4059 "The version of this input sub-unit." 4060 ::= { prtInputEntry 16 } 4062 prtInputSerialNumber OBJECT-TYPE 4063 SYNTAX OCTET STRING (SIZE(0..32)) 4064 MAX-ACCESS read-only 4065 STATUS current 4066 DESCRIPTION 4067 "The serial number assigned to this input sub-unit." 4068 ::= { prtInputEntry 17 } 4070 prtInputDescription OBJECT-TYPE 4071 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 4072 -- to a TC to better support localization of the object. 4073 SYNTAX PrtLocalizedDescriptionStringTC 4074 MAX-ACCESS read-only 4075 STATUS current 4076 DESCRIPTION 4077 "A free-form text description of this input sub-unit in the 4078 localization specified by prtGeneralCurrentLocalization." 4079 ::= { prtInputEntry 18 } 4081 prtInputSecurity OBJECT-TYPE 4082 SYNTAX PresentOnOff 4083 MAX-ACCESS read-write 4084 STATUS current 4085 DESCRIPTION 4086 "Indicates if this input sub-unit has some security associated 4087 with it." 4088 ::= { prtInputEntry 19 } 4090 -- The Input Media Group 4091 -- 4092 -- The Input Media Group supports identification of media 4093 -- installed or available for use on a printing device. 4094 -- Medium resources are identified by name, and include a 4095 -- collection of characteristic attributes that may further be 4096 -- used for selection and management of them. 4097 -- The Input Media group consists of a set of optional 4098 -- "columns" in the Input Table. In this manner, a minimally 4099 -- conforming implementation may choose to not support reporting 4100 -- of media resources if it cannot do so. 4102 prtInputMediaWeight OBJECT-TYPE 4103 -- NOTE: In RFC 1759, the range was not defined. 4104 SYNTAX Integer32 (-2..2147483647) 4105 MAX-ACCESS read-write 4106 STATUS current 4107 DESCRIPTION 4108 "The weight of the medium associated with this input sub-unit 4109 in grams / per meter squared. The value (-2) means unknown." 4110 ::= { prtInputEntry 20 } 4112 prtInputMediaType OBJECT-TYPE 4113 SYNTAX OCTET STRING (SIZE(0..63)) 4114 MAX-ACCESS read-write 4115 STATUS current 4116 DESCRIPTION 4117 "The name of the type of medium associated with this input sub 4118 unit. This name need not be processed by the printer; it might 4119 simply be displayed to an operator. 4121 NOTE: The above description has been modified from RFC 1759." 4122 -- The following reference was not included in RFC 1759. 4123 REFERENCE 4124 "The PWG Standardized Media Names specification [PWGMEDIA], 4125 section 3 Media Type Names, contains the recommended values for 4126 this object. Implementers may add additional string values. The 4127 naming conventions in ISO 9070 are recommended in order to 4128 avoid potential name clashes." 4129 ::= { prtInputEntry 21 } 4131 prtInputMediaColor OBJECT-TYPE 4132 SYNTAX OCTET STRING (SIZE(0..63)) 4133 MAX-ACCESS read-write 4134 STATUS current 4135 DESCRIPTION 4136 "The name of the color of the medium associated with 4137 this input sub-unit using standardized string values. 4139 NOTE: The above description has been modified from RFC 1759." 4140 -- The following reference was not included in RFC 1759. 4141 REFERENCE 4142 "The PWG Standardized Media Names specification [PWGMEDIA], 4143 section 4 Media Color Names, contains the recommended values 4144 for this object. Implementers may add additional string values. 4145 The naming conventions in ISO 9070 are recommended in order to 4146 avoid potential name clashes." 4147 ::= { prtInputEntry 22 } 4149 prtInputMediaFormParts OBJECT-TYPE 4150 -- NOTE: In RFC 1759, the range was not defined. 4151 SYNTAX Integer32 (-2..2147483647) 4152 MAX-ACCESS read-write 4153 STATUS current 4154 DESCRIPTION 4155 "The number of parts associated with the medium 4156 associated with this input sub-unit if the medium is a 4157 multi-part form. The value (-1) means other and 4158 specifically indicates that the device places no 4159 restrictions on this parameter. The value (-2) means 4160 unknown." 4161 ::= { prtInputEntry 23 } 4163 -- The Input Switching Group 4164 -- 4165 -- The input switching group allows the administrator to set the 4166 -- input subunit time-out for the printer and to control the 4167 -- automatic input subunit switching by the printer when an input 4168 -- subunit becomes empty. 4170 prtInputMediaLoadTimeout OBJECT-TYPE 4171 SYNTAX Integer32 (-2..2147483647) 4172 MAX-ACCESS read-write 4173 STATUS current 4174 DESCRIPTION 4175 "When the printer is not able to print due to a subunit being 4176 empty or the requested media must be manually loaded, the 4177 printer will wait for the duration (in seconds) specified by 4178 this object. Upon expiration of the time-out, the printer will 4179 take the action specified by prtInputNextIndex. 4181 The event which causes the printer to enter the waiting state 4182 is product specific. If the printer is not waiting for manually 4183 fed media, it may switch from an empty subunit to a different 4184 subunit without waiting for the time-out to expire. 4186 A value of (-1) implies 'other' or 'infinite' which translates 4187 to 'wait forever'. The action which causes printing to continue 4188 is product specific. A value of (-2) implies 'unknown'." 4189 ::= { prtInputEntry 24 } 4191 prtInputNextIndex OBJECT-TYPE 4192 SYNTAX Integer32 (-3..2147483647) 4193 MAX-ACCESS read-write 4194 STATUS current 4195 DESCRIPTION 4196 "The value of prtInputIndex corresponding to the input subunit 4197 which will be used when this input subunit is emptied and the 4198 time-out specified by prtInputMediaLoadTimeout expires. A value 4199 of zero(0) indicates that auto input switching will not occur 4200 when this input subunit is emptied. If the time-out specified 4201 by prtInputLoadMediaTimeout expires and this value is zero(0), 4202 the job will be aborted. A value of (-1) means other. The value 4203 (-2)means 'unknown' and specifically indicates that an 4204 implementation specific method will determine the next input 4205 subunit to use at the time this subunit is emptied and the time 4206 out expires. The value(-3) means input switching is not 4207 supported for this subunit." 4208 ::= { prtInputEntry 25 } 4210 -- The Output Group 4211 -- 4212 -- Output sub-units are managed as a tabular, indexed collection 4213 -- of possible devices capable of receiving media delivered from 4214 -- the printing process. Output sub-units typically have a 4215 -- location, a type, an identifier, a set of constraints on 4216 -- possible media sizes and potentially other characteristics, 4217 -- and may be capable of indicating current status or capacity. 4219 prtOutput OBJECT IDENTIFIER ::= { printmib 9 } 4221 prtOutputTable OBJECT-TYPE 4222 SYNTAX SEQUENCE OF PrtOutputEntry 4223 MAX-ACCESS not-accessible 4224 STATUS current 4225 DESCRIPTION 4226 "A table of the devices capable of receiving media delivered 4227 from the printing process." 4229 ::= { prtOutput 2 } 4231 prtOutputEntry OBJECT-TYPE 4232 SYNTAX PrtOutputEntry 4233 MAX-ACCESS not-accessible 4234 STATUS current 4235 DESCRIPTION 4236 "Attributes of a device capable of receiving media delivered 4237 from the printing process. Entries may exist in the table for 4238 each device index with a device type of 'printer'. 4240 NOTE: The above description has been modified from RFC 1759 4241 for clarification." 4242 INDEX { hrDeviceIndex, prtOutputIndex } 4243 ::= { prtOutputTable 1 } 4245 PrtOutputEntry ::= SEQUENCE { 4246 prtOutputIndex Integer32, 4247 prtOutputType PrtOutputTypeTC, 4248 prtOutputCapacityUnit PrtCapacityUnitTC, 4249 prtOutputMaxCapacity Integer32, 4250 prtOutputRemainingCapacity Integer32, 4251 prtOutputStatus PrtSubUnitStatusTC, 4252 prtOutputName OCTET STRING, 4253 prtOutputVendorName OCTET STRING, 4254 prtOutputModel OCTET STRING, 4255 prtOutputVersion OCTET STRING, 4256 prtOutputSerialNumber OCTET STRING, 4257 prtOutputDescription PrtLocalizedDescriptionStringTC, 4258 prtOutputSecurity PresentOnOff, 4259 prtOutputDimUnit PrtMediaUnitTC, 4260 prtOutputMaxDimFeedDir Integer32, 4261 prtOutputMaxDimXFeedDir Integer32, 4262 prtOutputMinDimFeedDir Integer32, 4263 prtOutputMinDimXFeedDir Integer32, 4264 prtOutputStackingOrder PrtOutputStackingOrderTC, 4265 prtOutputPageDeliveryOrientation 4266 PrtOutputPageDeliveryOrientationTC, 4267 prtOutputBursting PresentOnOff, 4268 prtOutputDecollating PresentOnOff, 4269 prtOutputPageCollated PresentOnOff, 4270 prtOutputOffsetStacking PresentOnOff 4271 } 4273 prtOutputIndex OBJECT-TYPE 4274 -- NOTE: In RFC 1759, the range was not defined. 4275 SYNTAX Integer32 (1..65535) 4276 MAX-ACCESS not-accessible 4277 STATUS current 4278 DESCRIPTION 4279 "A unique value used by this printer to identify this output 4280 sub-unit. Although these values may change due to a major 4281 reconfiguration of the sub-unit (e.g. the addition of new 4282 output devices to the printer), values SHOULD remain stable 4283 across successive printer power cycles. 4285 NOTE: The above description has been modified from RFC 1759 4286 for clarification." 4287 ::= { prtOutputEntry 1 } 4289 prtOutputType OBJECT-TYPE 4290 -- NOTE: In RFC 1759, the enumeration values were implicitly defined 4291 -- by this object. 4292 SYNTAX PrtOutputTypeTC 4293 MAX-ACCESS read-only 4294 STATUS current 4295 DESCRIPTION 4296 "The type of technology supported by this output sub-unit." 4297 ::= { prtOutputEntry 2 } 4299 prtOutputCapacityUnit OBJECT-TYPE 4300 SYNTAX PrtCapacityUnitTC 4301 MAX-ACCESS read-only 4302 STATUS current 4303 DESCRIPTION 4304 "The unit of measurement for use in calculating and relaying 4305 capacity values for this output sub-unit." 4306 ::= { prtOutputEntry 3 } 4308 prtOutputMaxCapacity OBJECT-TYPE 4309 -- NOTE: In RFC 1759, the range was not defined. 4310 SYNTAX Integer32 (-2..2147483647) 4311 MAX-ACCESS read-write 4312 STATUS current 4313 DESCRIPTION 4314 "The maximum capacity of this output sub-unit in output sub- 4315 unit capacity units (PrtCapacityUnitTC). There is no convention 4316 associated with the media itself so this value essentially 4317 reflects claimed capacity. If this output sub-unit can reliably 4318 sense this value, the value is sensed by the printer and may 4319 not be changed by management requests; otherwise, the value may 4320 be written (by a Remote Control Panel or a Management 4321 Application). The value (-1) means other and specifically 4322 indicates that the sub-unit places no restrictions on this 4323 parameter. The value (-2) means unknown." 4324 ::= { prtOutputEntry 4 } 4326 prtOutputRemainingCapacity OBJECT-TYPE 4327 -- NOTE: In RFC 1759, the range was not defined. 4328 SYNTAX Integer32 (-3..2147483647) 4329 MAX-ACCESS read-write 4330 STATUS current 4331 DESCRIPTION 4332 "The remaining capacity of the possible output sub-unit 4333 capacity in output sub-unit capacity units 4334 (PrtCapacityUnitTC)of this output sub-unit. If this output sub- 4335 unit can reliably sense this value, the value is sensed by the 4336 printer and may not be modified by management requests; 4337 otherwise, the value may be written (by a Remote Control Panel 4338 or a Management Application). The value (-1) means other and 4339 specifically indicates that the sub-unit places no restrictions 4340 on this parameter. The value (-2) means unknown. The value 4341 (-3) means that the printer knows that there remains capacity 4342 for at least one unit." 4343 ::= { prtOutputEntry 5 } 4345 prtOutputStatus OBJECT-TYPE 4346 SYNTAX PrtSubUnitStatusTC 4347 MAX-ACCESS read-only 4348 STATUS current 4349 DESCRIPTION 4350 "The current status of this output sub-unit." 4351 ::= { prtOutputEntry 6 } 4353 -- OUTPUT MEASUREMENT 4354 -- 4355 -- _______ | | ________ 4356 -- ^ | | ^ 4357 -- | | | | 4358 -- | | |RemainingCapacity 4359 -- MaxCapacity| | | 4360 -- | | | v ^ 4361 -- | |_ _ _ _ _ _ _ _ | _______________ |direction 4362 -- | | Sheets | | 4363 -- | | in | 4364 -- v | Output | 4365 -- _______ +________________+ 4367 -- The Extended Output Group 4369 prtOutputName OBJECT-TYPE 4370 SYNTAX OCTET STRING (SIZE(0..63)) 4371 MAX-ACCESS read-write 4372 STATUS current 4373 DESCRIPTION 4374 "The name assigned to this output sub-unit." 4375 ::= { prtOutputEntry 7 } 4377 prtOutputVendorName OBJECT-TYPE 4378 SYNTAX OCTET STRING (SIZE(0..63)) 4379 MAX-ACCESS read-only 4380 STATUS current 4381 DESCRIPTION 4382 "The vendor name of this output sub-unit." 4383 ::= { prtOutputEntry 8 } 4385 prtOutputModel OBJECT-TYPE 4386 SYNTAX OCTET STRING (SIZE(0..63)) 4387 MAX-ACCESS read-only 4388 STATUS current 4389 DESCRIPTION 4390 "The model name assigned to this output sub-unit. 4392 NOTE: The above description has been modified from RFC 1759 4393 for clarification." 4394 ::= { prtOutputEntry 9 } 4396 prtOutputVersion OBJECT-TYPE 4397 SYNTAX OCTET STRING (SIZE(0..63)) 4398 MAX-ACCESS read-only 4399 STATUS current 4400 DESCRIPTION 4401 "The version of this output sub-unit." 4402 ::= { prtOutputEntry 10 } 4404 prtOutputSerialNumber OBJECT-TYPE 4405 SYNTAX OCTET STRING (SIZE(0..63)) 4406 MAX-ACCESS read-only 4407 STATUS current 4408 DESCRIPTION 4409 "The serial number assigned to this output sub-unit." 4410 ::= { prtOutputEntry 11 } 4412 prtOutputDescription OBJECT-TYPE 4413 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 4414 -- to a TC to better support localization of the object. 4415 SYNTAX PrtLocalizedDescriptionStringTC 4416 MAX-ACCESS read-only 4417 STATUS current 4418 DESCRIPTION 4419 "A free-form text description of this output sub-unit in the 4420 localization specified by prtGeneralCurrentLocalization." 4421 ::= { prtOutputEntry 12 } 4423 prtOutputSecurity OBJECT-TYPE 4424 SYNTAX PresentOnOff 4425 MAX-ACCESS read-write 4426 STATUS current 4427 DESCRIPTION 4428 "Indicates if this output sub-unit has some security associated 4429 with it and if that security is enabled or not." 4430 ::= { prtOutputEntry 13 } 4432 -- The Output Dimensions Group 4434 prtOutputDimUnit OBJECT-TYPE 4435 SYNTAX PrtMediaUnitTC 4436 MAX-ACCESS read-only 4437 STATUS current 4438 DESCRIPTION 4439 "The unit of measurement for use in calculating and relaying 4440 dimensional values for this output sub-unit." 4441 ::= { prtOutputEntry 14 } 4443 prtOutputMaxDimFeedDir OBJECT-TYPE 4444 -- NOTE: In RFC 1759, the range was not defined. 4445 SYNTAX Integer32 (-2..2147483647) 4446 MAX-ACCESS read-write 4447 STATUS current 4448 DESCRIPTION 4449 "The maximum dimensions supported by this output sub-unit 4450 for measurements taken parallel relative to the feed 4451 direction associated with that sub-unit in output 4452 sub-unit dimensional units (controlled by prtOutputDimUnit, 4453 which uses PrtMediaUnitTC). If this output sub-unit can 4454 reliably sense this value, the value is sensed by the printer 4455 and may not be changed with management protocol operations. 4456 The value (-1) means other and specifically indicates that the 4457 sub-unit places no restrictions on this parameter. The value 4458 (-2) means unknown. 4460 NOTE: The above description has been modified from RFC 1759 4461 for clarification and to explain the purpose of (-1) and (-2)." 4462 ::= { prtOutputEntry 15 } 4464 prtOutputMaxDimXFeedDir OBJECT-TYPE 4465 -- NOTE: In RFC 1759, the range was not defined. 4466 SYNTAX Integer32 (-2..2147483647) 4467 MAX-ACCESS read-write 4468 STATUS current 4469 DESCRIPTION 4470 "The maximum dimensions supported by this output sub-unit 4471 for measurements taken ninety degrees relative to the 4472 feed direction associated with that sub-unit in output 4473 sub-unit dimensional units (controlled by prtOutputDimUnit, 4474 which uses PrtMediaUnitTC). If this output sub-unit can 4475 reliably sense this value, the value is sensed by the printer 4476 and may not be changed with management protocol operations. 4477 The value (-1) means other and specifically indicates that the 4478 sub-unit places no restrictions on this parameter. The value 4479 (-2) means unknown. 4481 NOTE: The above description has been modified from RFC 1759 4482 for clarification and to explain the purpose of (-1) and (-2)." 4483 ::= { prtOutputEntry 16 } 4485 prtOutputMinDimFeedDir OBJECT-TYPE 4486 -- NOTE: In RFC 1759, the range was not defined. 4487 SYNTAX Integer32 (-2..2147483647) 4488 MAX-ACCESS read-write 4489 STATUS current 4490 DESCRIPTION 4491 "The minimum dimensions supported by this output sub-unit 4492 for measurements taken parallel relative to the feed 4493 direction associated with that sub-unit in output 4494 sub-unit dimensional units (controlled by prtOutputDimUnit, 4495 which uses PrtMediaUnitTC). If this output sub-unit can 4496 reliably sense this value, the value is sensed by the printer 4497 and may not be changed with management protocol operations. 4498 The value (-1) means other and specifically indicates that the 4499 sub-unit places no restrictions on this parameter. The value 4500 (-2) means unknown. 4502 NOTE: The above description has been modified from RFC 1759 4503 for clarification and to explain the purpose of (-1) and (-2)." 4504 ::= { prtOutputEntry 17 } 4506 prtOutputMinDimXFeedDir OBJECT-TYPE 4507 -- NOTE: In RFC 1759, the range was not defined. 4508 SYNTAX Integer32 (-2..2147483647) 4509 MAX-ACCESS read-write 4510 STATUS current 4511 DESCRIPTION 4512 "The minimum dimensions supported by this output sub-unit 4513 for measurements taken ninety degrees relative to the 4514 feed direction associated with that sub-unit in output 4515 sub-unit dimensional units (controlled by prtOutputDimUnit, 4516 which uses PrtMediaUnitTC). If this output sub-unit can 4517 reliably sense this value, the value is sensed by the printer 4518 and may not be changed with management protocol operations. 4519 The value (-1) means other and specifically indicates that the 4520 sub-unit places no restrictions on this parameter. The value 4521 (-2) means unknown. 4523 NOTE: The above description has been modified from RFC 1759 4524 for clarification and to explain the purpose of (-1) and (-2)." 4525 ::= { prtOutputEntry 18 } 4527 -- The Output Features Group 4529 prtOutputStackingOrder OBJECT-TYPE 4530 -- NOTE: In RFC 1759, the enumeration values were implicitly 4531 -- defined by this object. 4532 SYNTAX PrtOutputStackingOrderTC 4533 MAX-ACCESS read-write 4534 STATUS current 4535 DESCRIPTION 4536 "The current state of the stacking order for the 4537 associated output sub-unit. 'FirstToLast' means 4538 that as pages are output the front of the next page is 4539 placed against the back of the previous page. 4540 'LasttoFirst' means that as pages are output the back 4541 of the next page is placed against the front of the 4542 previous page." 4543 ::= { prtOutputEntry 19 } 4545 prtOutputPageDeliveryOrientation OBJECT-TYPE 4546 -- NOTE: In RFC 1759, the enumeration values were implicitly 4547 -- defined by this object. 4548 SYNTAX PrtOutputPageDeliveryOrientationTC 4549 MAX-ACCESS read-write 4550 STATUS current 4551 DESCRIPTION 4552 "The reading surface that will be 'up' when pages are 4553 delivered to the associated output sub-unit. Values are 4554 faceUp and faceDown. (Note: interpretation of these 4555 values is in general context-dependent based on locale; 4556 presentation of these values to an end-user should be 4557 normalized to the expectations of the user)." 4558 ::= { prtOutputEntry 20 } 4560 prtOutputBursting OBJECT-TYPE 4561 SYNTAX PresentOnOff 4562 MAX-ACCESS read-write 4563 STATUS current 4564 DESCRIPTION 4565 "This object indicates that the outputting sub-unit supports 4566 bursting, and if so, whether the feature is enabled. Bursting 4567 is the process by which continuous media is separated into 4568 individual sheets, typically by bursting along pre-formed 4569 perforations." 4570 ::= { prtOutputEntry 21 } 4572 prtOutputDecollating OBJECT-TYPE 4573 SYNTAX PresentOnOff 4574 MAX-ACCESS read-write 4575 STATUS current 4576 DESCRIPTION 4577 "This object indicates that the output supports decollating, 4578 and if so, whether the feature is enabled. Decollating is the 4579 process by which the individual parts within a multi-part form 4580 are separated and sorted into separate stacks for each part." 4581 ::= { prtOutputEntry 22 } 4583 prtOutputPageCollated OBJECT-TYPE 4584 SYNTAX PresentOnOff 4585 MAX-ACCESS read-write 4586 STATUS current 4587 DESCRIPTION 4588 "This object indicates that the output sub-unit supports page 4589 collation, and if so, whether the feature is enabled. See RFC 4590 XXXX Appendix A, Glossary Of Terms, for definition of how this 4591 RFC Editor: change XXXX to the number assigned to this document. 4592 document defines collation. 4594 NOTE: The above description has been modified from RFC 1759 4595 for clarification." 4596 ::= { prtOutputEntry 23 } 4598 prtOutputOffsetStacking OBJECT-TYPE 4599 SYNTAX PresentOnOff 4600 MAX-ACCESS read-write 4601 STATUS current 4602 DESCRIPTION 4603 "This object indicates that the output supports offset 4604 stacking,and if so, whether the feature is enabled. See RFC 4605 XXXX Appendix A, Glossary Of Terms, for how Offset Stacking is 4606 RFC Editor: change XXXX to the number assigned to this document. 4607 defined by this document. 4609 NOTE: The above description has been modified from RFC 1759 4610 for clarification." 4611 ::= { prtOutputEntry 24 } 4613 -- The Marker Group 4614 -- 4615 -- A marker is the mechanism that produces marks on the print 4616 -- media. The marker sub-units and their associated supplies are 4617 -- represented by the Marker Group in the model. A printer can 4618 -- contain one or more marking mechanisms. Some examples of 4619 -- multiple marker sub-units are: a printer 4620 -- with separate markers for normal and magnetic ink or an 4621 -- imagesetter that can output to both a proofing device and 4622 -- final film. Each marking device can have its own set of 4623 -- characteristics associated with it, such as marking technology 4624 -- and resolution. 4626 prtMarker OBJECT IDENTIFIER ::= { printmib 10 } 4628 -- The printable area margins as listed below define an area of 4629 -- the print media which is guaranteed to be printable for all 4630 -- combinations of input, media paths, and interpreters for this 4631 -- marker. 4633 prtMarkerTable OBJECT-TYPE 4634 SYNTAX SEQUENCE OF PrtMarkerEntry 4635 MAX-ACCESS not-accessible 4636 STATUS current 4637 DESCRIPTION 4638 "The marker table provides a description of each marker 4639 sub-unit contained within the printer. 4641 NOTE: The above description has been modified from RFC 1759 4642 for clarification." 4643 ::= { prtMarker 2 } 4645 prtMarkerEntry OBJECT-TYPE 4646 SYNTAX PrtMarkerEntry 4647 MAX-ACCESS not-accessible 4648 STATUS current 4649 DESCRIPTION 4650 "Entries in this table define the characteristics and status 4651 of each marker sub-unit in the printer. 4653 NOTE: The above description has been modified from RFC 1759 4654 for clarification." 4655 INDEX { hrDeviceIndex, prtMarkerIndex } 4656 ::= { prtMarkerTable 1 } 4658 PrtMarkerEntry ::= SEQUENCE { 4659 prtMarkerIndex Integer32, 4660 prtMarkerMarkTech PrtMarkerMarkTechTC, 4661 prtMarkerCounterUnit PrtMarkerCounterUnitTC, 4662 prtMarkerLifeCount Counter32, 4663 prtMarkerPowerOnCount Counter32, 4664 prtMarkerProcessColorants Integer32, 4665 prtMarkerSpotColorants Integer32, 4666 prtMarkerAddressabilityUnit PrtMarkerAddressabilityUnitTC, 4667 prtMarkerAddressabilityFeedDir Integer32, 4668 prtMarkerAddressabilityXFeedDir Integer32, 4669 prtMarkerNorthMargin Integer32, 4670 prtMarkerSouthMargin Integer32, 4671 prtMarkerWestMargin Integer32, 4672 prtMarkerEastMargin Integer32, 4673 prtMarkerStatus PrtSubUnitStatusTC 4674 } 4676 prtMarkerIndex OBJECT-TYPE 4677 SYNTAX Integer32 (1..65535) 4678 MAX-ACCESS not-accessible 4679 STATUS current 4680 DESCRIPTION 4681 "A unique value used by the printer to identify this marking 4682 SubUnit. Although these values may change due to a major 4683 reconfiguration of the device (e.g. the addition of new marking 4684 sub-units to the printer), values SHOULD remain stable across 4685 successive printer power cycles. 4687 NOTE: The above description has been modified from RFC 1759 4688 for clarification." 4689 ::= { prtMarkerEntry 1 } 4691 prtMarkerMarkTech OBJECT-TYPE 4692 -- NOTE: In RFC 1759, the enumeration values were implicitly 4693 -- defined by this object. 4694 SYNTAX PrtMarkerMarkTechTC 4695 MAX-ACCESS read-only 4696 STATUS current 4697 DESCRIPTION 4698 "The type of marking technology used for this marking 4699 sub-unit." 4700 ::= { prtMarkerEntry 2 } 4702 prtMarkerCounterUnit OBJECT-TYPE 4703 -- NOTE: In RFC 1759, the enumeration values were implicitly 4704 -- defined by this object. 4705 SYNTAX PrtMarkerCounterUnitTC 4706 MAX-ACCESS read-only 4707 STATUS current 4708 DESCRIPTION 4709 "The unit that will be used by the printer when reporting 4710 counter values for this marking sub-unit. The time units of 4711 measure are provided for a device like a strip recorder that 4712 does not or cannot track the physical dimensions of the media 4713 and does not use characters, lines or sheets." 4714 ::= { prtMarkerEntry 3 } 4716 prtMarkerLifeCount OBJECT-TYPE 4717 SYNTAX Counter32 4718 MAX-ACCESS read-only 4719 STATUS current 4720 DESCRIPTION 4721 "The count of the number of units of measure counted during the 4722 life of printer using units of measure as specified by 4723 prtMarkerCounterUnit. 4725 Note: This object should be implemented as a persistent object 4726 with a reliable value throughout the lifetime of the printer." 4727 ::= { prtMarkerEntry 4 } 4729 prtMarkerPowerOnCount OBJECT-TYPE 4730 SYNTAX Counter32 4731 MAX-ACCESS read-only 4732 STATUS current 4733 DESCRIPTION 4734 "The count of the number of units of measure counted since the 4735 equipment was most recently powered on using units of measure 4736 as specified by prtMarkerCounterUnit." 4737 ::= { prtMarkerEntry 5 } 4739 prtMarkerProcessColorants OBJECT-TYPE 4740 SYNTAX Integer32 (0..65535) 4741 MAX-ACCESS read-only 4742 STATUS current 4743 DESCRIPTION 4744 "The number of process colors supported by this marker. A 4745 process color of 1 implies monochrome. The value of this 4746 object and prtMarkerSpotColorants cannot both be 0. The value 4747 of prtMarkerProcessColorants must be 0 or greater. 4749 NOTE: The above description has been modified from RFC 1759 4750 for clarification." 4751 ::= { prtMarkerEntry 6 } 4753 prtMarkerSpotColorants OBJECT-TYPE 4754 SYNTAX Integer32 (0..65535) 4755 MAX-ACCESS read-only 4756 STATUS current 4757 DESCRIPTION 4758 "The number of spot colors supported by this marker. The value 4759 of this object and prtMarkerProcessColorants cannot both be 0. 4760 Must be 0 or greater. 4762 NOTE: The above description has been modified from RFC 1759 4763 for clarification." 4764 ::= { prtMarkerEntry 7 } 4766 prtMarkerAddressabilityUnit OBJECT-TYPE 4767 -- NOTE: In RFC 1759, the enumeration values were implicitly 4768 -- defined by this object. 4770 SYNTAX PrtMarkerAddressabilityUnitTC 4771 MAX-ACCESS read-only 4772 STATUS current 4773 DESCRIPTION 4774 "The unit of measure of distances, as applied to the marker's 4775 resolution. 4777 NOTE: The above description has been modified from RFC 1759 4778 for clarification." 4779 ::= { prtMarkerEntry 8 } 4781 prtMarkerAddressabilityFeedDir OBJECT-TYPE 4782 -- NOTE: In RFC 1759, the range was not defined. 4783 SYNTAX Integer32 (-2..2147483647) 4784 MAX-ACCESS read-only 4785 STATUS current 4786 DESCRIPTION 4787 "The maximum number of addressable marking positions in the 4788 feed direction per 10000 units of measure specified by 4789 prtMarkerAddressabilityUnit. A value of (-1) implies 'other' 4790 or 'infinite' while a value of (-2) implies 'unknown'. 4792 NOTE: The above description has been modified from RFC 1759 4793 for clarification." 4794 ::= { prtMarkerEntry 9 } 4796 prtMarkerAddressabilityXFeedDir OBJECT-TYPE 4797 -- NOTE: In RFC 1759, the range was not defined. 4798 SYNTAX Integer32 (-2..2147483647) 4799 MAX-ACCESS read-only 4800 STATUS current 4801 DESCRIPTION 4802 "The maximum number of addressable marking positions in the 4803 cross feed direction in 10000 units of measure specified by 4804 prtMarkerAddressabilityUnit. A value of (-1) implies 'other' 4805 or 'infinite' while a value of (-2) implies 'unknown'. 4807 NOTE: The above description has been modified from RFC 1759 4808 for clarification." 4809 ::= { prtMarkerEntry 10 } 4811 prtMarkerNorthMargin OBJECT-TYPE 4812 -- NOTE: In RFC 1759, the range was not defined. 4813 SYNTAX Integer32 (-2..2147483647) 4814 MAX-ACCESS read-only 4815 STATUS current 4816 DESCRIPTION 4817 "The margin, in units identified by prtMarkerAddressabilityUnit, 4818 from the leading edge of the medium as the medium flows through 4819 the marking engine with the side to be imaged facing the 4820 observer. The leading edge is the North edge and the other 4821 edges are defined by the normal compass layout of directions 4822 with the compass facing the observer. Printing within the area 4823 bounded by all four margins is guaranteed for all interpreters. 4824 The value (-2) means unknown." 4825 ::= { prtMarkerEntry 11 } 4827 prtMarkerSouthMargin OBJECT-TYPE 4828 -- NOTE: In RFC 1759, the range was not defined. 4829 SYNTAX Integer32 (-2..2147483647) 4830 MAX-ACCESS read-only 4831 STATUS current 4832 DESCRIPTION 4833 "The margin from the South edge (see prtMarkerNorthMargin) of 4834 the medium in units identified by prtMarkerAddressabilityUnit. 4835 Printing within the area bounded by all four margins is 4836 guaranteed for all interpreters. The value (-2) means unknown." 4837 ::= { prtMarkerEntry 12 } 4839 prtMarkerWestMargin OBJECT-TYPE 4840 -- NOTE: In RFC 1759, the range was not defined. 4841 SYNTAX Integer32 (-2..2147483647) 4842 MAX-ACCESS read-only 4843 STATUS current 4844 DESCRIPTION 4845 "The margin from the West edge (see prtMarkerNorthMargin) of 4846 the medium in units identified by prtMarkerAddressabilityUnit. 4847 Printing within the area bounded by all four margins is 4848 guaranteed for all interpreters. The value (-2) means unknown." 4849 ::= { prtMarkerEntry 13 } 4851 prtMarkerEastMargin OBJECT-TYPE 4852 -- NOTE: In RFC 1759, the range was not defined. 4853 SYNTAX Integer32 (-2..2147483647) 4854 MAX-ACCESS read-only 4855 STATUS current 4856 DESCRIPTION 4857 "The margin from the East edge (see prtMarkerNorthMargin) of 4858 the medium in units identified by prtMarkerAddressabilityUnit. 4859 Printing within the area bounded by all four margins is 4860 guaranteed for all interpreters. The value (-2) means unknown." 4861 ::= { prtMarkerEntry 14 } 4863 prtMarkerStatus OBJECT-TYPE 4864 SYNTAX PrtSubUnitStatusTC 4865 MAX-ACCESS read-only 4866 STATUS current 4867 DESCRIPTION 4868 "The current status of this marker sub-unit." 4869 ::= { prtMarkerEntry 15 } 4871 -- The Marker Supplies Group 4873 prtMarkerSupplies OBJECT IDENTIFIER ::= { printmib 11 } 4875 prtMarkerSuppliesTable OBJECT-TYPE 4876 SYNTAX SEQUENCE OF PrtMarkerSuppliesEntry 4877 MAX-ACCESS not-accessible 4878 STATUS current 4879 DESCRIPTION 4880 "A table of the marker supplies available on this printer." 4881 ::= { prtMarkerSupplies 1 } 4883 prtMarkerSuppliesEntry OBJECT-TYPE 4884 SYNTAX PrtMarkerSuppliesEntry 4885 MAX-ACCESS not-accessible 4886 STATUS current 4887 DESCRIPTION 4888 "Attributes of a marker supply. Entries may exist in the table 4889 for each device index with a device type of 'printer'. 4891 NOTE: The above description has been modified from RFC 1759 4892 for clarification." 4893 INDEX { hrDeviceIndex, prtMarkerSuppliesIndex } 4894 ::= { prtMarkerSuppliesTable 1 } 4896 PrtMarkerSuppliesEntry ::= SEQUENCE { 4897 prtMarkerSuppliesIndex Integer32, 4898 prtMarkerSuppliesMarkerIndex Integer32, 4899 prtMarkerSuppliesColorantIndex Integer32, 4900 prtMarkerSuppliesClass PrtMarkerSuppliesClassTC, 4901 prtMarkerSuppliesType PrtMarkerSuppliesTypeTC, 4902 prtMarkerSuppliesDescription PrtLocalizedDescriptionStringTC, 4903 prtMarkerSuppliesSupplyUnit PrtMarkerSuppliesSupplyUnitTC, 4904 prtMarkerSuppliesMaxCapacity Integer32, 4905 prtMarkerSuppliesLevel Integer32 4906 } 4908 prtMarkerSuppliesIndex OBJECT-TYPE 4909 SYNTAX Integer32 (1..65535) 4910 MAX-ACCESS not-accessible 4911 STATUS current 4912 DESCRIPTION 4913 "A unique value used by the printer to identify this marker 4914 supply. Although these values may change due to a major 4915 reconfiguration of the device (e.g. the addition of new marker 4916 supplies to the printer), values SHOULD remain stable across 4917 successive printer power cycles. 4919 NOTE: The above description has been modified from RFC 1759 4920 for clarification." 4921 ::= { prtMarkerSuppliesEntry 1 } 4923 prtMarkerSuppliesMarkerIndex OBJECT-TYPE 4924 SYNTAX Integer32 (0..65535) 4925 MAX-ACCESS read-only 4926 STATUS current 4927 DESCRIPTION 4928 "The value of prtMarkerIndex corresponding to the marking sub 4929 unit with which this marker supply sub-unit is associated." 4930 ::= { prtMarkerSuppliesEntry 2 } 4932 prtMarkerSuppliesColorantIndex OBJECT-TYPE 4933 SYNTAX Integer32 (0..65535) 4934 MAX-ACCESS read-only 4935 STATUS current 4936 DESCRIPTION 4937 "The value of prtMarkerColorantIndex corresponding to the 4938 colorant with which this marker supply sub-unit is associated. 4939 This value shall be 0 if there is no colorant table or if this 4940 supply does not depend on a single specified colorant. 4942 NOTE: The above description has been modified from RFC 1759 4943 for clarification." 4944 ::= { prtMarkerSuppliesEntry 3 } 4946 prtMarkerSuppliesClass OBJECT-TYPE 4947 -- NOTE: In RFC 1759, the enumeration values were implicitly 4948 -- defined by this object. 4949 SYNTAX PrtMarkerSuppliesClassTC 4950 MAX-ACCESS read-only 4951 STATUS current 4952 DESCRIPTION 4953 "Indicates whether this supply entity represents a supply that 4954 is consumed or a receptacle that is filled. 4956 NOTE: The above description has been modified from RFC 1759 4957 for clarification." 4958 ::= { prtMarkerSuppliesEntry 4 } 4960 prtMarkerSuppliesType OBJECT-TYPE 4961 -- NOTE: In RFC 1759, the enumeration values were implicitly 4962 -- defined by this object. 4963 SYNTAX PrtMarkerSuppliesTypeTC 4964 MAX-ACCESS read-only 4965 STATUS current 4966 DESCRIPTION 4967 "The type of this supply." 4968 ::= { prtMarkerSuppliesEntry 5 } 4970 prtMarkerSuppliesDescription OBJECT-TYPE 4971 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 4972 -- to a TC to better support localization of the object. 4973 SYNTAX PrtLocalizedDescriptionStringTC 4974 MAX-ACCESS read-only 4975 STATUS current 4976 DESCRIPTION 4977 "The description of this supply container/receptacle in the 4978 localization specified by prtGeneralCurrentLocalization." 4979 ::= { prtMarkerSuppliesEntry 6 } 4981 prtMarkerSuppliesSupplyUnit OBJECT-TYPE 4982 -- NOTE: In RFC 1759, the enumeration values were implicitly 4983 -- defined by this object. 4984 SYNTAX PrtMarkerSuppliesSupplyUnitTC 4985 MAX-ACCESS read-only 4986 STATUS current 4987 DESCRIPTION 4988 "Unit of measure of this marker supply container/receptacle. 4990 NOTE: The above description has been modified from RFC 1759 4991 for clarification." 4992 ::= { prtMarkerSuppliesEntry 7 } 4994 prtMarkerSuppliesMaxCapacity OBJECT-TYPE 4995 -- NOTE: In RFC 1759, the range was not defined. 4996 SYNTAX Integer32 (-2..2147483647) 4997 MAX-ACCESS read-write 4998 STATUS current 4999 DESCRIPTION 5000 "The maximum capacity of this supply container/receptacle 5001 expressed in prtMarkerSuppliesSupplyUnit. If this supply 5002 container/receptacle can reliably sense this value, the value 5003 is reported by the printer and is read-only; otherwise, the 5004 value may be written (by a Remote Control Panel or a Management 5005 Application). The value (-1) means other and specifically 5006 indicates that the sub-unit places no restrictions on this 5007 parameter. The value (-2) means unknown." 5008 ::= { prtMarkerSuppliesEntry 8 } 5010 prtMarkerSuppliesLevel OBJECT-TYPE 5011 -- NOTE: In RFC 1759, the range was not defined. 5012 SYNTAX Integer32 (-3..2147483647) 5013 MAX-ACCESS read-write 5014 STATUS current 5015 DESCRIPTION 5016 "The current level if this supply is a container; the remaining 5017 space if this supply is a receptacle. If this supply 5018 container/receptacle can reliably sense this value, the value 5019 is reported by the printer and is read-only; otherwise, the 5020 value may be written (by a Remote Control Panel or a Management 5021 Application). The value (-1) means other and specifically 5022 indicates that the sub-unit places no restrictions on this 5023 parameter. The value (-2) means unknown. A value of (-3) means 5024 that the printer knows that there is some supply/remaining 5025 space, respectively." 5026 ::= { prtMarkerSuppliesEntry 9 } 5028 -- The Marker Colorant Group 5030 prtMarkerColorant OBJECT IDENTIFIER ::= { printmib 12 } 5032 prtMarkerColorantTable OBJECT-TYPE 5033 SYNTAX SEQUENCE OF PrtMarkerColorantEntry 5034 MAX-ACCESS not-accessible 5035 STATUS current 5036 DESCRIPTION 5037 "A table of all of the colorants available on the printer." 5038 ::= { prtMarkerColorant 1 } 5040 prtMarkerColorantEntry OBJECT-TYPE 5041 SYNTAX PrtMarkerColorantEntry 5042 MAX-ACCESS not-accessible 5043 STATUS current 5044 DESCRIPTION 5045 "Attributes of a colorant available on the printer. Entries may 5046 exist in the table for each device index with a device type of 5047 'printer'. 5049 NOTE: The above description has been modified from RFC 1759 5050 for clarification." 5051 INDEX { hrDeviceIndex, prtMarkerColorantIndex } 5052 ::= { prtMarkerColorantTable 1 } 5054 PrtMarkerColorantEntry ::= SEQUENCE { 5055 prtMarkerColorantIndex Integer32, 5056 prtMarkerColorantMarkerIndex Integer32, 5057 prtMarkerColorantRole PrtMarkerColorantRoleTC, 5058 prtMarkerColorantValue OCTET STRING, 5059 prtMarkerColorantTonality Integer32 5060 } 5062 prtMarkerColorantIndex OBJECT-TYPE 5063 SYNTAX Integer32 (1..65535) 5064 MAX-ACCESS not-accessible 5065 STATUS current 5066 DESCRIPTION 5067 "A unique value used by the printer to identify this colorant. 5068 Although these values may change due to a major reconfiguration 5069 of the device (e.g. the addition of new colorants to the 5070 printer) , values SHOULD remain stable across successive 5071 printer power cycles. 5073 NOTE: The above description has been modified from RFC 1759 5074 for clarification." 5075 ::= { prtMarkerColorantEntry 1 } 5077 prtMarkerColorantMarkerIndex OBJECT-TYPE 5078 SYNTAX Integer32 (0..65535) 5079 MAX-ACCESS read-only 5080 STATUS current 5081 DESCRIPTION 5082 "The value of prtMarkerIndex corresponding to the marker sub 5083 unit with which this colorant entry is associated." 5084 ::= { prtMarkerColorantEntry 2 } 5086 prtMarkerColorantRole OBJECT-TYPE 5087 -- NOTE: In RFC 1759, the enumeration values were implicitly 5088 -- defined by this object. 5089 SYNTAX PrtMarkerColorantRoleTC 5090 MAX-ACCESS read-only 5091 STATUS current 5092 DESCRIPTION 5093 "The role played by this colorant." 5094 ::= { prtMarkerColorantEntry 3 } 5096 prtMarkerColorantValue OBJECT-TYPE 5097 -- NOTE: The string length range has been increased from RFC 1759. 5098 SYNTAX OCTET STRING (SIZE(0..255)) 5099 MAX-ACCESS read-only 5100 STATUS current 5101 DESCRIPTION 5102 "The name of the color of this colorant using standardized 5103 string names from ISO 10175 (DPA) and ISO 10180 (SPDL) such as: 5104 other 5105 unknown 5106 white 5107 red 5108 green 5109 blue 5110 cyan 5111 magenta 5112 yellow 5113 black 5114 Implementers may add additional string values. The naming 5115 conventions in ISO 9070 are recommended in order to avoid 5116 potential name clashes" 5117 ::= { prtMarkerColorantEntry 4 } 5119 prtMarkerColorantTonality OBJECT-TYPE 5120 -- NOTE: In RFC 1759, the range was not defined. 5121 SYNTAX Integer32 (2..2147483647) 5122 MAX-ACCESS read-only 5123 STATUS current 5124 DESCRIPTION 5125 "The distinct levels of tonality realizable by a marking sub 5126 unit when using this colorant. This value does not include the 5127 number of levels of tonal difference that an interpreter can 5128 obtain by techniques such as half toning. This value must be at 5129 least 2." 5131 ::= { prtMarkerColorantEntry 5 } 5133 -- The Media Path Group 5134 -- 5135 -- The media paths encompass the mechanisms in the printer that 5136 -- move the media through the printer and connect all other media 5137 -- related sub-units: inputs, outputs, markers and finishers. A 5138 -- printer contains one or more media paths. These are 5139 -- represented by the Media Path Group in the model. 5141 prtMediaPath OBJECT IDENTIFIER ::= { printmib 13 } 5143 prtMediaPathTable OBJECT-TYPE 5144 SYNTAX SEQUENCE OF PrtMediaPathEntry 5145 MAX-ACCESS not-accessible 5146 STATUS current 5147 DESCRIPTION 5148 "The media path table includes both physical and logical paths 5149 within the printer. 5151 NOTE: The above description has been modified from RFC 1759 5152 for clarification." 5153 ::= { prtMediaPath 4 } 5155 prtMediaPathEntry OBJECT-TYPE 5156 SYNTAX PrtMediaPathEntry 5157 MAX-ACCESS not-accessible 5158 STATUS current 5159 DESCRIPTION 5160 "Entries may exist in the table for each device index with a 5161 device type of 'printer' Each entry defines the physical 5162 characteristics of and the status of the media path. The data 5163 provided indicates the maximum throughput and the media 5164 size limitations of these subunits. 5166 NOTE: The above description has been modified from RFC 1759 5167 for clarification." 5168 INDEX { hrDeviceIndex, prtMediaPathIndex } 5169 ::= { prtMediaPathTable 1 } 5171 PrtMediaPathEntry ::= SEQUENCE { 5172 prtMediaPathIndex Integer32, 5173 prtMediaPathMaxSpeedPrintUnit PrtMediaPathMaxSpeedPrintUnitTC, 5174 prtMediaPathMediaSizeUnit PrtMediaUnitTC, 5175 prtMediaPathMaxSpeed Integer32, 5176 prtMediaPathMaxMediaFeedDir Integer32, 5177 prtMediaPathMaxMediaXFeedDir Integer32, 5178 prtMediaPathMinMediaFeedDir Integer32, 5179 prtMediaPathMinMediaXFeedDir Integer32, 5180 prtMediaPathType PrtMediaPathTypeTC, 5181 prtMediaPathDescription PrtLocalizedDescriptionStringTC, 5182 prtMediaPathStatus PrtSubUnitStatusTC 5183 } 5185 prtMediaPathIndex OBJECT-TYPE 5186 SYNTAX Integer32 (1..65535) 5187 MAX-ACCESS not-accessible 5188 STATUS current 5189 DESCRIPTION 5190 "A unique value used by the printer to identify this media 5191 path.Although these values may change due to a major 5192 reconfiguration of the device (e.g. the addition of new media 5193 paths to the printer), values SHOULD remain stable across 5194 successive printer power cycles. 5196 NOTE: The above description has been modified from RFC 1759 5197 for clarification." 5198 ::= { prtMediaPathEntry 1 } 5200 prtMediaPathMaxSpeedPrintUnit OBJECT-TYPE 5201 -- NOTE: In RFC 1759, the enumeration values were implicitly 5202 -- defined by this object. 5203 SYNTAX PrtMediaPathMaxSpeedPrintUnitTC 5204 MAX-ACCESS read-only 5205 STATUS current 5206 DESCRIPTION 5207 "The unit of measure used in specifying the speed of all media 5208 paths in the printer." 5209 ::= { prtMediaPathEntry 2 } 5211 prtMediaPathMediaSizeUnit OBJECT-TYPE 5212 SYNTAX PrtMediaUnitTC 5213 MAX-ACCESS read-only 5214 STATUS current 5215 DESCRIPTION 5216 "The units of measure of media size for use in calculating and 5217 relaying dimensional values for all media paths in the 5218 printer." 5219 ::= { prtMediaPathEntry 3 } 5221 prtMediaPathMaxSpeed OBJECT-TYPE 5222 -- NOTE: In RFC 1759, the range was not defined. 5223 SYNTAX Integer32 (-2..2147483647) 5224 MAX-ACCESS read-only 5225 STATUS current 5226 DESCRIPTION 5227 "The maximum printing speed of this media path expressed in 5228 prtMediaPathMaxSpeedUnit's. A value of (-1) implies 'other'." 5229 ::= { prtMediaPathEntry 4 } 5231 prtMediaPathMaxMediaFeedDir OBJECT-TYPE 5232 -- NOTE: In RFC 1759, the range was not defined. 5233 SYNTAX Integer32 (-2..2147483647) 5234 MAX-ACCESS read-only 5235 STATUS current 5236 DESCRIPTION 5237 "The maximum physical media size in the feed direction of this 5238 media path expressed in units of measure specified by 5239 PrtMediaPathMediaSizeUnit. A value of (-1) implies 'unlimited' 5240 a value of (-2) implies 'unknown'. 5242 NOTE: The above description has been modified from RFC 1759 5243 for clarification." 5244 ::= { prtMediaPathEntry 5 } 5246 prtMediaPathMaxMediaXFeedDir OBJECT-TYPE 5247 -- NOTE: In RFC 1759, the range was not defined. 5248 SYNTAX Integer32 (-2..2147483647) 5249 MAX-ACCESS read-only 5250 STATUS current 5251 DESCRIPTION 5252 "The maximum physical media size across the feed direction of 5253 this media path expressed in units of measure specified by 5254 prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'. 5256 NOTE: The above description has been modified from RFC 1759 5257 for clarification." 5258 ::= { prtMediaPathEntry 6 } 5260 prtMediaPathMinMediaFeedDir OBJECT-TYPE 5261 -- NOTE: In RFC 1759, the range was not defined. 5262 SYNTAX Integer32 (-2..2147483647) 5263 MAX-ACCESS read-only 5264 STATUS current 5265 DESCRIPTION 5266 "The minimum physical media size in the feed direction of this 5267 media path expressed in units of measure specified by 5268 prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'. 5270 NOTE: The above description has been modified from RFC 1759 5271 for clarification." 5272 ::= { prtMediaPathEntry 7 } 5274 prtMediaPathMinMediaXFeedDir OBJECT-TYPE 5275 -- NOTE: In RFC 1759, the range was not defined. 5276 SYNTAX Integer32 (-2..2147483647) 5277 MAX-ACCESS read-only 5278 STATUS current 5279 DESCRIPTION 5280 "The minimum physical media size across the feed direction of 5281 this media path expressed in units of measure specified by 5282 prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'. 5284 NOTE: The above description has been modified from RFC 1759 5285 for clarification." 5286 ::= { prtMediaPathEntry 8 } 5288 prtMediaPathType OBJECT-TYPE 5289 -- NOTE: In RFC 1759, the enumeration values were implicitly 5290 -- defined by this object. 5291 SYNTAX PrtMediaPathTypeTC 5292 MAX-ACCESS read-only 5293 STATUS current 5294 DESCRIPTION 5295 "The type of the media path for this media path." 5296 ::= { prtMediaPathEntry 9 } 5298 prtMediaPathDescription OBJECT-TYPE 5299 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 5300 -- to a TC to better support localization of the object. 5301 SYNTAX PrtLocalizedDescriptionStringTC 5302 MAX-ACCESS read-only 5303 STATUS current 5304 DESCRIPTION 5305 "The manufacturer-provided description of this media path in 5306 the localization specified by prtGeneralCurrentLocalization." 5307 ::= { prtMediaPathEntry 10 } 5309 prtMediaPathStatus OBJECT-TYPE 5310 SYNTAX PrtSubUnitStatusTC 5311 MAX-ACCESS read-only 5312 STATUS current 5313 DESCRIPTION 5314 "The current status of this media path." 5315 ::= { prtMediaPathEntry 11 } 5317 -- The Print Job Delivery Channel Group 5318 -- 5319 -- Print Job Delivery Channels are independent sources of print 5320 -- data. Here, print data is the term used for the information 5321 -- that is used to construct printed pages and may have both data 5322 -- and control aspects. The output of a channel is in a form 5323 -- suitable for input to one of the interpreters as a 5324 -- stream. A channel may be independently enabled (allowing 5325 -- print data to flow) or disabled (stopping the flow of 5326 -- print data). A printer may have one or more channels. 5327 -- 5328 -- The Print Job Delivery Channel table describes the 5329 -- capabilities of the printer and not what is currently being 5330 -- performed by the printer 5331 -- 5332 -- Basically, the print job delivery channel abstraction 5333 -- describes the final processing step of getting the print data 5334 -- to an interpreter. It might include some level of 5335 -- decompression or decoding of print stream data. 5336 -- channel. All of these aspects are hidden in the channel 5337 -- abstraction. 5338 -- 5339 -- There are many kinds of print job delivery channels; some of 5340 -- which are based on networks and others which are not. For 5341 -- example, a channel can be a serial (or parallel) connection; 5342 -- it can be a service, such as the UNIX Line Printer Daemon 5343 -- (LPD), offering services over a network connection; or 5344 -- it could be a disk drive into which a floppy disk with 5345 -- the print data is inserted. Each print job delivery channel is 5346 -- identified by the electronic path and/or service protocol 5347 -- used to deliver print data to a print data interpreter. 5348 -- 5349 -- Channel example Implementation 5350 -- 5351 -- serial port channel bi-directional data channel 5352 -- parallel port channel often uni-directional channel 5353 -- IEEE 1284 port channel bi-directional channel 5354 -- SCSI port channel bi-directional 5355 -- Apple PAP channel may be based on LocalTalk, 5356 -- Ethernet or Tokentalk 5357 -- LPD Server channel TCP/IP based, port 515 5358 -- Netware Remote Printer SPX/IPX based channel 5359 -- Netware Print Server SPX/IPX based channel 5360 -- 5361 -- It is easy to note that this is a mixed bag. There are 5362 -- some physical connections over which no (or very meager) 5363 -- protocols are run (e.g. the serial or old parallel ports) 5364 -- and there are services which often have elaborate 5365 -- protocols that run over a number of protocol stacks. In 5366 -- the end, what is important is the delivery of print data 5367 -- through the channel. 5368 -- 5369 -- The print job delivery channel sub-units are represented by 5370 -- the Print Job Delivery Channel Group in the Model. It has a 5371 -- current print job control language, which can be used to 5372 -- specify which interpreter is to be used for the print data and 5373 -- to query and change environment variables used by the 5374 -- interpreters (and Management Applications). There is also a 5375 -- default interpreter that is to be used if an interpreter is 5376 -- not explicitly specified using the Control Language. 5378 -- The first seven items in the Print Job Delivery Channel Table 5379 -- define the "channel" itself. A channel typically depends on 5380 -- other protocols and interfaces to provide the data that flows 5381 -- through the channel. 5382 -- 5383 -- Control of a print job delivery channel is largely limited to 5384 -- enabling or disabling the entire channel itself. It is likely 5385 -- that more control of the process of accessing print data 5386 -- will be needed over time. Thus, the ChannelType will 5387 -- allow type-specific data to be associated with each 5388 -- channel (using ChannelType specific groups in a fashion 5389 -- analogous to the media specific MIBs that are associated 5390 -- with the IANAIfType in the Interfaces Table). As a first 5391 -- step in this direction, each channel will identify the 5392 -- underlying Interface on which it is based. This is the 5393 -- eighth object in each row of the table. 5395 -- The Print Job Delivery Channel Table 5397 prtChannel OBJECT IDENTIFIER ::= { printmib 14 } 5399 prtChannelTable OBJECT-TYPE 5400 SYNTAX SEQUENCE OF PrtChannelEntry 5401 MAX-ACCESS not-accessible 5402 STATUS current 5403 DESCRIPTION 5404 "The channel table represents the set of input data sources 5405 which can provide print data to one or more of the 5406 interpreters available on a printer. 5408 NOTE: The above description has been modified from RFC 1759 5409 for clarification." 5410 ::= { prtChannel 1 } 5412 prtChannelEntry OBJECT-TYPE 5413 SYNTAX PrtChannelEntry 5414 MAX-ACCESS not-accessible 5415 STATUS current 5416 DESCRIPTION 5417 "Entries may exist in the table for each device index with a 5418 device type of 'printer'. Each channel table entry is 5419 characterized by a unique protocol stack and/or addressing. 5420 The channel may also have printer dependent features that are 5421 associated with a printing language. 5423 NOTE: The above description has been modified from RFC 1759 5424 for clarification." 5425 INDEX { hrDeviceIndex, prtChannelIndex } 5426 ::= { prtChannelTable 1 } 5428 PrtChannelEntry ::= SEQUENCE { 5429 prtChannelIndex Integer32, 5430 prtChannelType PrtChannelTypeTC, 5431 prtChannelProtocolVersion OCTET STRING, 5432 prtChannelCurrentJobCntlLangIndex Integer32, 5433 prtChannelDefaultPageDescLangIndex Integer32, 5434 prtChannelState PrtChannelStateTC, 5435 prtChannelIfIndex InterfaceIndexOrZero, 5436 prtChannelStatus PrtSubUnitStatusTC, 5437 prtChannelInformation OCTET STRING 5438 } 5440 prtChannelIndex OBJECT-TYPE 5441 -- NOTE: In RFC 1759, the range was not defined. 5442 SYNTAX Integer32 (1..65535) 5443 MAX-ACCESS not-accessible 5444 STATUS current 5445 DESCRIPTION 5446 "A unique value used by the printer to identify this data 5447 channel. Although these values may change due to a major 5448 reconfiguration of the device (e.g. the addition of new data 5449 channels to the printer), values SHOULD remain stable across 5450 successive printer power cycles. 5452 NOTE: The above description has been modified from RFC 1759 5453 for clarification." 5454 ::= { prtChannelEntry 1 } 5456 prtChannelType OBJECT-TYPE 5457 -- NOTE: In RFC 1759, the enumeration values were implicitly 5458 -- defined by this object. 5459 SYNTAX PrtChannelTypeTC 5460 MAX-ACCESS read-only 5461 STATUS current 5462 DESCRIPTION 5463 "The type of this print data channel. This object provides the 5464 linkage to ChannelType-specific groups that may (conceptually) 5465 extend the prtChannelTable with additional details about that 5466 channel." 5467 ::= { prtChannelEntry 2 } 5469 prtChannelProtocolVersion OBJECT-TYPE 5470 SYNTAX OCTET STRING (SIZE(0..63)) 5471 MAX-ACCESS read-only 5472 STATUS current 5473 DESCRIPTION 5474 "The version of the protocol used on this channel. The format 5475 used for version numbering depends on prtChannelType." 5476 ::= { prtChannelEntry 3 } 5478 prtChannelCurrentJobCntlLangIndex OBJECT-TYPE 5479 -- NOTE: In RFC 1759, the range was not defined. 5480 SYNTAX Integer32 (0..65535) 5481 MAX-ACCESS read-write 5482 STATUS current 5483 DESCRIPTION 5484 "The value of prtInterpreterIndex corresponding to the Control 5485 Language Interpreter for this channel. This interpreter defines 5486 the syntax used for control functions, such as querying or 5487 changing environment variables and identifying job boundaries 5488 (e.g. PJL, PostScript, NPAP). A value of zero indicates that 5489 there is no current Job Control Language Interpreter for this 5490 channel. 5492 NOTE: The above description has been modified from RFC 1759 5493 for clarification." 5494 ::= { prtChannelEntry 4 } 5496 prtChannelDefaultPageDescLangIndex OBJECT-TYPE 5497 -- NOTE: In RFC 1759, the range was not defined. 5498 SYNTAX Integer32 (0..65535) 5499 MAX-ACCESS read-write 5500 STATUS current 5501 DESCRIPTION 5502 "The value of prtInterpreterIndex corresponding to the Page 5503 Description Language Interpreter for this channel. This 5504 interpreter defines the default Page Description Language 5505 interpreter to be used for the print data unless the Control 5506 Language is used to select a specific interpreter (e.g., PCL, 5507 PostScript Language, auto-sense). A value of zero indicates 5508 that there is no default page description language interpreter 5509 for this channel. 5511 NOTE: The above description has been modified from RFC 1759 5512 for clarification." 5513 ::= { prtChannelEntry 5 } 5515 prtChannelState OBJECT-TYPE 5516 -- NOTE: In RFC 1759, the enumeration values were implicitly 5517 -- defined by this object. 5518 SYNTAX PrtChannelStateTC 5519 MAX-ACCESS read-write 5520 STATUS current 5521 DESCRIPTION 5522 "The state of this print data channel. The value determines 5523 whether control information and print data is allowed through 5524 this channel or not." 5525 ::= { prtChannelEntry 6 } 5527 prtChannelIfIndex OBJECT-TYPE 5528 SYNTAX InterfaceIndexOrZero -- Was Integer32 in RFC 1759. 5529 MAX-ACCESS read-write 5530 STATUS current 5531 DESCRIPTION 5532 "The value of ifIndex in the ifTable; see the Interfaces Group 5533 MIB [RFC2863] which corresponds to this channel. 5534 When more than one row of the ifTable is relevant, this is the 5535 index of the row representing the topmost layer in the 5536 interface hierarchy. A value of zero indicates that no 5537 interface is associated with this channel. 5539 NOTE: The above description has been modified from RFC 1759 5540 for clarification." 5541 ::= { prtChannelEntry 7 } 5543 prtChannelStatus OBJECT-TYPE 5544 SYNTAX PrtSubUnitStatusTC 5545 MAX-ACCESS read-only 5546 STATUS current 5547 DESCRIPTION 5548 "The current status of the channel." 5549 ::= { prtChannelEntry 8 } 5551 prtChannelInformation OBJECT-TYPE 5552 SYNTAX OCTET STRING (SIZE (0..255)) 5553 MAX-ACCESS read-only 5554 STATUS current 5555 DESCRIPTION 5556 "Auxiliary information to allow a printing application to use 5557 the channel for data submission to the printer. An application 5558 capable of using a specific PrtChannelType should be able to 5559 use the combined information from the prtChannelInformation and 5560 other channel and interface group objects to 'bootstrap' its 5561 use of the channel. prtChannelInformation is not intended to 5562 provide a general channel description, nor to provide 5563 information that is available once the channel is in use. 5565 The encoding and interpretation of the prtChannelInformation 5566 object is specific to channel type. The description of each 5567 PrtChannelType enum value for which prtChannelInformation is 5568 defined specifies the appropriate encoding and interpretation, 5569 including interaction with other objects. For channel types 5570 that do not specify a prtChannelInformation value, its value 5571 shall be null (0 length). 5573 When a new PrtChannelType enumeration value is registered, its 5574 accompanying description must specify the encoding and 5575 interpretation of the prtChannelInformation value for the 5576 channel type. prtChannelInformation semantics for an existing 5577 PrtChannelType may be added or amended in the same manner as 5578 described in section 2.4.1 for type 2 enumeration values. 5580 The prtChannelInformation specifies values for a collection of 5581 channel attributes, represented as text according to the 5582 following rules: 5584 1. The prtChannelInformation is not affected by localization. 5586 2. The prtChannelInformation is a list of entries representing 5587 the attribute values. Each entry consists of the following 5588 items, in order: 5590 a. A keyword, composed of alphabetic characters (A-Z, a-z) 5591 represented by their NVT ASCII [RFC854] codes, that 5592 identifies a channel attribute, 5594 b. The NVT ASCII code for an Equals Sign (=) (code 61) to 5595 delimit the keyword, 5597 c. A data value encoded using rules specific to the 5598 PrtChannelType to with the prtChannelInformation applies which 5599 must in no case allow an octet with value 10 (the NVT ASCII 5600 Line Feed code), 5602 d. the NVT ASCII code for a Line Feed character (code 10) to 5603 delimit the data value. 5605 No other octets shall be present. 5607 Keywords are case-sensitive. Conventionally, keywords are 5608 capitalized (including each word of a multi-word keyword) and 5609 since they occupy space in the prtChannelInformation, they are 5610 kept short. 5612 3. If a channel attribute has multiple values, it is 5613 represented by multiple entries with the same keyword, each 5614 specifying one value. Otherwise, there shall be at most one 5615 entry for each attribute. 5617 4. By default, entries may appear in any order. If there are 5618 ordering constraints for particular entries, these must be 5619 specified in their definitions. 5621 5. The prtChannelInformation value by default consists of text 5622 represented by NVT ASCII graphics character codes. However, 5623 other representations may be specified: 5625 a. In cases where the prtChannelInformation value contains 5626 information not normally coded in textual form, whatever 5627 symbolic representation is conventionally used for the 5628 information should be used for encoding the 5629 prtChannelInformation value. (For instance, a binary port value 5630 might be represented as a decimal number using NVT ASCII 5631 codes.) Such encoding must be specified in the definition of 5632 the value. 5634 b. The value may contain textual information in a character set 5635 other than NVT ASCII graphics characters. (For instance, an 5636 identifier might consist of ISO 10646 text encoded using the 5637 UTF-8 encoding scheme.) Such a character set and its encoding 5638 must be specified in the definition of the value. 5640 6. For each PrtChannelType for which prtChannelInformation 5641 entries are defined, the descriptive text associated with the 5642 PrtChannelType enumeration value shall specify the following 5643 information for each entry: 5645 Title: Brief description phrase, e.g.: 'Port name', 5646 'Service Name', etc. 5648 Keyword: The keyword value, e.g.: 'Port' or 'Service' 5650 Syntax: The encoding of the entry value if it cannot be 5651 directly represented by NVT ASCII. 5653 Status: 'Mandatory', 'Optional', or 'Conditionally 5654 Mandatory' 5656 Multiplicity: 'Single' or 'Multiple' to indicate whether the 5657 entry may be present multiple times. 5659 Description: Description of the use of the entry, other 5660 information required to complete the definition 5661 (e.g.: ordering constraints, interactions between 5662 entries). 5664 Applications that interpret prtChannelInformation should ignore 5665 unrecognized entries, so they are not affected if new entry 5666 types are added." 5668 ::= { prtChannelEntry 9 } 5670 -- The Interpreter Group 5671 -- 5672 -- The interpreter sub-units are responsible for the conversion 5673 -- of a description of intended print instances into images that 5674 -- are to be marked on the media. A printer may have one or more 5675 -- interpreters. The interpreter sub-units are represented by the 5676 -- Interpreter Group in the Model. Each interpreter is generally 5677 -- implemented with software running on the System Controller 5678 -- sub-unit. The Interpreter Table has one entry per interpreter 5679 -- where the interpreters include both Page Description Language 5680 -- (PDL) Interpreters and Control Language Interpreters. 5682 prtInterpreter OBJECT IDENTIFIER ::= { printmib 15 } 5684 -- Interpreter Table 5686 prtInterpreterTable OBJECT-TYPE 5687 SYNTAX SEQUENCE OF PrtInterpreterEntry 5688 MAX-ACCESS not-accessible 5689 STATUS current 5690 DESCRIPTION 5691 "The interpreter table is a table representing the 5692 interpreters in the printer. An entry shall be placed in the 5693 interpreter table for each interpreter on the printer. 5695 NOTE: The above description has been modified from RFC 1759 5696 for clarification." 5697 ::= { prtInterpreter 1 } 5699 prtInterpreterEntry OBJECT-TYPE 5700 SYNTAX PrtInterpreterEntry 5701 MAX-ACCESS not-accessible 5702 STATUS current 5703 DESCRIPTION 5704 "Entries may exist in the table for each device index with a 5705 device type of 'printer'. Each table entry provides a complete 5706 description of the interpreter, including version information, 5707 rendering resolutions, default character sets, output 5708 orientation, and communication capabilities. 5710 NOTE: The above description has been modified from RFC 1759 5711 for clarification." 5712 INDEX { hrDeviceIndex, prtInterpreterIndex } 5713 ::= { prtInterpreterTable 1 } 5715 PrtInterpreterEntry ::= SEQUENCE { 5716 prtInterpreterIndex Integer32, 5717 prtInterpreterLangFamily PrtInterpreterLangFamilyTC, 5718 prtInterpreterLangLevel OCTET STRING, 5719 prtInterpreterLangVersion OCTET STRING, 5720 prtInterpreterDescription PrtLocalizedDescriptionStringTC, 5721 prtInterpreterVersion OCTET STRING, 5722 prtInterpreterDefaultOrientation PrtPrintOrientationTC, 5723 prtInterpreterFeedAddressability Integer32, 5724 prtInterpreterXFeedAddressability Integer32, 5725 prtInterpreterDefaultCharSetIn IANACharset, 5726 prtInterpreterDefaultCharSetOut IANACharset, 5727 prtInterpreterTwoWay PrtInterpreterTwoWayTC 5728 } 5730 prtInterpreterIndex OBJECT-TYPE 5731 -- NOTE: In RFC 1759, the range was not defined. 5732 SYNTAX Integer32 (1..65535) 5733 MAX-ACCESS not-accessible 5734 STATUS current 5735 DESCRIPTION 5736 "A unique value for each PDL or control language for which 5737 there exists an interpreter or emulator in the printer. The 5738 value is used to identify this interpreter. Although these 5739 values may change due to a major reconfiguration of the device 5740 (e.g. the addition of new interpreters to the printer), values 5741 SHOULD remain stable across successive printer power cycles. 5743 NOTE: The above description has been modified from RFC 1759 5744 for clarification." 5745 ::= { prtInterpreterEntry 1 } 5747 prtInterpreterLangFamily OBJECT-TYPE 5748 -- NOTE: In RFC 1759, the enumeration values were implicitly 5749 -- defined by this object. 5750 SYNTAX PrtInterpreterLangFamilyTC 5751 MAX-ACCESS read-only 5752 STATUS current 5753 DESCRIPTION 5754 "The family name of a Page Description Language (PDL) or 5755 control language which this interpreter in the printer can 5756 interpret or emulate. 5758 NOTE: The above description has been modified from RFC 1759 5759 for clarification." 5761 ::= { prtInterpreterEntry 2 } 5763 prtInterpreterLangLevel OBJECT-TYPE 5764 SYNTAX OCTET STRING (SIZE(0..31)) 5765 MAX-ACCESS read-only 5766 STATUS current 5767 DESCRIPTION 5768 "The level of the language which this interpreter is 5769 interpreting or emulating. This might contain a value like 5770 '5e'for an interpreter which is emulating level 5e of the PCL 5771 language. It might contain '2' for an interpreter which is 5772 emulating level 2 of the PostScript language. Similarly it 5773 might contain '2' for an interpreter which is emulating level 2 5774 of the HPGL language." 5775 ::= { prtInterpreterEntry 3 } 5777 prtInterpreterLangVersion OBJECT-TYPE 5778 SYNTAX OCTET STRING (SIZE(0..31)) 5779 MAX-ACCESS read-only 5780 STATUS current 5781 DESCRIPTION 5782 "The date code or version of the language which this 5783 interpreter is interpreting or emulating." 5784 ::= { prtInterpreterEntry 4 } 5786 prtInterpreterDescription OBJECT-TYPE 5787 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 5788 -- to a TC to better support localization of the object. 5789 SYNTAX PrtLocalizedDescriptionStringTC 5790 MAX-ACCESS read-only 5791 STATUS current 5792 DESCRIPTION 5793 "A string to identify this interpreter in the localization 5794 specified by prtGeneralCurrentLocalization as opposed to the 5795 language which is being interpreted. It is anticipated that 5796 this string will allow manufacturers to unambiguously identify 5797 their interpreters." 5798 ::= { prtInterpreterEntry 5 } 5800 prtInterpreterVersion OBJECT-TYPE 5801 SYNTAX OCTET STRING (SIZE(0..31)) 5802 MAX-ACCESS read-only 5803 STATUS current 5804 DESCRIPTION 5805 "The date code, version number, or other product specific 5806 information tied to this interpreter. This value is associated 5807 with the interpreter, rather than with the version of the 5808 language which is being interpreted or emulated." 5809 ::= { prtInterpreterEntry 6 } 5811 prtInterpreterDefaultOrientation OBJECT-TYPE 5812 -- NOTE: In RFC 1759, the enumeration values were implicitly 5813 -- defined by this object. 5814 SYNTAX PrtPrintOrientationTC 5815 MAX-ACCESS read-write 5816 STATUS current 5817 DESCRIPTION 5818 "The current orientation default for this interpreter. This 5819 value may be overridden for a particular job (e.g., by a 5820 command in the input data stream)." 5821 ::= { prtInterpreterEntry 7 } 5823 prtInterpreterFeedAddressability OBJECT-TYPE 5824 -- NOTE: In RFC 1759, the range was not defined. 5825 SYNTAX Integer32 (-2..2147483647) 5826 MAX-ACCESS read-only 5827 STATUS current 5828 DESCRIPTION 5829 "The maximum interpreter addressability in the feed 5830 direction in 10000 prtMarkerAddressabilityUnits (as specified 5831 by prtMarkerDefaultIndex) for this interpreter. The 5832 value (-1) means other and specifically indicates that the 5833 sub-unit places no restrictions on this parameter. The value 5834 (-2) means unknown. 5836 NOTE: The above description has been modified from RFC 1759 5837 for clarification." 5838 ::= { prtInterpreterEntry 8 } 5840 prtInterpreterXFeedAddressability OBJECT-TYPE 5841 -- NOTE: In RFC 1759, the range was not defined. 5842 SYNTAX Integer32 (-2..2147483647) 5843 MAX-ACCESS read-only 5844 STATUS current 5845 DESCRIPTION 5846 "The maximum interpreter addressability in the cross feed 5847 direction in 10000 prtMarkerAddressabilityUnits (as specified 5848 by prtMarkerDefaultIndex) for this interpreter. The 5849 value (-1) means other and specifically indicates that the 5850 sub-unit places no restrictions on this parameter. The value 5851 (-2) means unknown. 5853 NOTE: The above description has been modified from RFC 1759 5854 for clarification." 5855 ::= { prtInterpreterEntry 9 } 5857 prtInterpreterDefaultCharSetIn OBJECT-TYPE 5858 SYNTAX IANACharset 5859 MAX-ACCESS read-write 5860 STATUS current 5861 DESCRIPTION 5862 "The default coded character set for input octets encountered 5863 outside a context in which the Page Description Language 5864 established the interpretation of the octets. (Input octets are 5865 presented to the interpreter through a path defined in the 5866 channel group.)" 5867 ::= { prtInterpreterEntry 10 } 5869 prtInterpreterDefaultCharSetOut OBJECT-TYPE 5870 SYNTAX IANACharset 5871 MAX-ACCESS read-write 5872 STATUS current 5873 DESCRIPTION 5874 "The default character set for data coming from this 5875 interpreter through the printer's output channel (i.e. the 5876 'backchannel')." 5877 ::= { prtInterpreterEntry 11 } 5879 prtInterpreterTwoWay OBJECT-TYPE 5880 -- NOTE: In RFC 1759, the enumeration values were implicitly 5881 -- defined by this object. 5882 SYNTAX PrtInterpreterTwoWayTC 5883 MAX-ACCESS read-only 5884 STATUS current 5885 DESCRIPTION 5886 "Indicates whether or not this interpreter returns information 5887 back to the host." 5888 ::= { prtInterpreterEntry 12 } 5890 -- The Console Group 5891 -- 5892 -- Many printers have a console on the printer, the operator 5893 -- console, that is used to display and modify the state of the 5894 -- printer. The console can be as simple as a few indicators and 5895 -- switches or as complicated as full screen displays and 5896 -- keyboards. There can be at most one such console. 5898 -- The Display Buffer Table 5900 prtConsoleDisplayBuffer OBJECT IDENTIFIER ::= { printmib 16 } 5902 prtConsoleDisplayBufferTable OBJECT-TYPE 5903 SYNTAX SEQUENCE OF PrtConsoleDisplayBufferEntry 5904 MAX-ACCESS not-accessible 5905 STATUS current 5906 DESCRIPTION 5907 "Physical display buffer for printer console display or 5908 operator panel 5910 NOTE: The above description has been modified from RFC 1759 5911 for clarification." 5912 ::= { prtConsoleDisplayBuffer 5 } 5914 prtConsoleDisplayBufferEntry OBJECT-TYPE 5915 SYNTAX PrtConsoleDisplayBufferEntry 5916 MAX-ACCESS not-accessible 5917 STATUS current 5918 DESCRIPTION 5919 "This table contains one entry for each physical line on 5920 the display. Lines cannot be added or deleted. Entries may 5921 exist in the table for each device index with a device type of 5922 'printer'. 5924 NOTE: The above description has been modified from RFC 1759 5925 for clarification." 5926 INDEX { hrDeviceIndex, prtConsoleDisplayBufferIndex } 5927 ::= { prtConsoleDisplayBufferTable 1 } 5929 PrtConsoleDisplayBufferEntry ::= SEQUENCE { 5930 prtConsoleDisplayBufferIndex Integer32, 5931 prtConsoleDisplayBufferText PrtConsoleDescriptionStringTC 5932 } 5934 prtConsoleDisplayBufferIndex OBJECT-TYPE 5935 SYNTAX Integer32 (1..65535) 5936 MAX-ACCESS not-accessible 5937 STATUS current 5938 DESCRIPTION 5939 "A unique value for each console line in the printer. The value 5940 is used to identify this console line. Although these values 5941 may change due to a major reconfiguration of the device (e.g. 5942 the addition of new console lines to the printer). Values 5943 SHOULD remain stable across successive printer power cycles. 5945 NOTE: The above description has been modified from RFC 1759 5946 for clarification." 5947 ::= { prtConsoleDisplayBufferEntry 1 } 5949 prtConsoleDisplayBufferText OBJECT-TYPE 5950 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 5951 -- to a TC to better support localization of the object. 5952 SYNTAX PrtConsoleDescriptionStringTC 5953 MAX-ACCESS read-write 5954 STATUS current 5955 DESCRIPTION 5956 "The content of a line in the logical display buffer of 5957 the operator's console of the printer. When a write 5958 operation occurs, normally a critical message, to one of 5959 the LineText strings, the agent should make that line 5960 displayable if a physical display is present. Writing a zero 5961 length string clears the line. It is an implementation- 5962 specific matter as to whether the agent allows a line to be 5963 overwritten before it has been cleared. Printer generated 5964 strings shall be in the localization specified by 5965 prtConsoleLocalization.Management Application generated strings 5966 should be localized by the Management Application." 5967 ::= { prtConsoleDisplayBufferEntry 2 } 5969 -- The Console Light Table 5971 prtConsoleLights OBJECT IDENTIFIER ::= { printmib 17 } 5973 prtConsoleLightTable OBJECT-TYPE 5974 SYNTAX SEQUENCE OF PrtConsoleLightEntry 5975 MAX-ACCESS not-accessible 5976 STATUS current 5977 DESCRIPTION 5978 "The console light table provides a description and state 5979 information for each light present on the printer console. 5981 NOTE: The above description has been modified from RFC 1759 5982 for clarification." 5983 ::= { prtConsoleLights 6 } 5985 prtConsoleLightEntry OBJECT-TYPE 5986 SYNTAX PrtConsoleLightEntry 5987 MAX-ACCESS not-accessible 5988 STATUS current 5989 DESCRIPTION 5990 "Entries may exist in the table for each device index with a 5991 device type of 'printer'. 5993 NOTE: The above description has been modified from RFC 1759 5994 for clarification." 5995 INDEX { hrDeviceIndex, prtConsoleLightIndex } 5996 ::= { prtConsoleLightTable 1 } 5998 PrtConsoleLightEntry ::= SEQUENCE { 5999 prtConsoleLightIndex Integer32, 6000 prtConsoleOnTime Integer32, 6001 prtConsoleOffTime Integer32, 6002 prtConsoleColor PrtConsoleColorTC, 6003 prtConsoleDescription PrtConsoleDescriptionStringTC 6004 } 6006 prtConsoleLightIndex OBJECT-TYPE 6007 SYNTAX Integer32 (1..65535) -- Lower limit invalid in RFC 1759 6008 MAX-ACCESS not-accessible 6009 STATUS current 6010 DESCRIPTION 6011 "A unique value used by the printer to identify this light. 6012 Although these values may change due to a major 6013 reconfiguration of the device (e.g. the addition of new lights 6014 to the printer). Values SHOULD remain stable across successive 6015 printer power cycles. 6017 NOTE: The above description has been modified from RFC 1759 6018 for clarification." 6019 ::= { prtConsoleLightEntry 1 } 6021 prtConsoleOnTime OBJECT-TYPE 6022 -- NOTE: In RFC 1759, the range was not defined. 6023 SYNTAX Integer32 (0..2147483647) 6024 MAX-ACCESS read-write 6025 STATUS current 6026 DESCRIPTION 6027 "This object, in conjunction with prtConsoleOffTime, defines 6028 the current status of the light. If both prtConsoleOnTime and 6029 prtConsoleOffTime are non-zero, the lamp is blinking and the 6030 values presented define the on time and off time, respectively, 6031 in milliseconds. If prtConsoleOnTime is zero and 6032 prtConsoleOffTime is non-zero, the lamp is off. If 6033 prtConsoleOffTime is zero and prtConsoleOnTime is non-zero, the 6034 lamp is on. If both values are zero the lamp is off. 6036 NOTE: The above description has been modified from RFC 1759 6037 for clarification." 6038 ::= { prtConsoleLightEntry 2 } 6040 prtConsoleOffTime OBJECT-TYPE 6041 -- NOTE: In RFC 1759, the range was not defined. 6042 SYNTAX Integer32 (0..2147483647) 6043 MAX-ACCESS read-write 6044 STATUS current 6045 DESCRIPTION 6046 "This object, in conjunction with prtConsoleOnTime, defines the 6047 current status of the light. If both prtConsoleOnTime and 6048 prtConsoleOffTime are non-zero, the lamp is blinking and the 6049 values presented define the on time and off time, respectively, 6050 in milliseconds. If prtConsoleOnTime is zero and 6051 prtConsoleOffTime is non-zero, the lamp is off. If 6052 prtConsoleOffTime is zero and prtConsoleOnTime is non-zero, the 6053 lamp is on. If both values are zero the lamp is off. 6055 NOTE: The above description has been modified from RFC 1759 6056 for clarification." 6057 ::= { prtConsoleLightEntry 3 } 6059 prtConsoleColor OBJECT-TYPE 6060 -- NOTE: In RFC 1759, the enumeration values were implicitly 6061 -- defined by this object. 6062 SYNTAX PrtConsoleColorTC 6063 MAX-ACCESS read-only 6064 STATUS current 6065 DESCRIPTION 6066 "The color of this light." 6067 ::= { prtConsoleLightEntry 4 } 6069 prtConsoleDescription OBJECT-TYPE 6070 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 6071 -- to a TC to better support localization of the object. 6072 SYNTAX PrtConsoleDescriptionStringTC 6073 MAX-ACCESS read-only 6074 STATUS current 6075 DESCRIPTION 6076 "The vendor description or label of this light in the 6077 localization specified by prtConsoleLocalization." 6078 ::= { prtConsoleLightEntry 5 } 6080 -- The Alerts Group 6081 -- 6082 -- The table contains information on the severity, component, 6083 -- detail location within the component, alert code and 6084 -- description of each critical alert that is currently active 6085 -- within the printer. See 2.2.13 for a more complete 6086 -- description of the alerts table and its management. 6087 -- 6088 -- Each parameter in the Trap PDU is a full OID which itself is 6089 -- indexed by the host resources MIB "hrDeviceIndex" object. In 6090 -- order for a management station to obtain the correct 6091 -- "hrDeviceIndex" associated with a particular Trap PDU, the 6092 -- "hrDeviceIndex" value can be extracted from the returned OID 6093 -- value in the Trap PDU when the PDU is received by the 6094 -- Management station. 6096 prtAlert OBJECT IDENTIFIER ::= { printmib 18 } 6098 prtAlertTable OBJECT-TYPE 6099 SYNTAX SEQUENCE OF PrtAlertEntry 6100 MAX-ACCESS not-accessible 6101 STATUS current 6102 DESCRIPTION 6103 "The prtAlertTable lists all the critical and non-critical 6104 alerts currently active in the printer. A critical alert is 6105 one that stops the printer from printing immediately and 6106 printing can not continue until the critical alert condition 6107 is eliminated. Non-critical alerts are those items that do 6108 not stop printing but may at some future time. 6110 NOTE: The above description has been modified from RFC 1759 6111 for clarification." 6112 ::= { prtAlert 1 } 6114 prtAlertEntry OBJECT-TYPE 6115 SYNTAX PrtAlertEntry 6116 MAX-ACCESS not-accessible 6117 STATUS current 6118 DESCRIPTION 6119 "Entries may exist in the table for each device 6120 index with a device type of 'printer'. 6122 NOTE: The above description has been modified from RFC 1759 6123 for clarification." 6124 INDEX { hrDeviceIndex, prtAlertIndex } 6125 ::= { prtAlertTable 1 } 6127 PrtAlertEntry ::= SEQUENCE { 6128 prtAlertIndex Integer32, 6129 prtAlertSeverityLevel PrtAlertSeverityLevelTC, 6130 prtAlertTrainingLevel PrtAlertTrainingLevelTC, 6131 prtAlertGroup PrtAlertGroupTC, 6132 prtAlertGroupIndex Integer32, 6133 prtAlertLocation Integer32, 6134 prtAlertCode PrtAlertCodeTC, 6135 prtAlertDescription PrtLocalizedDescriptionStringTC, 6136 prtAlertTime TimeTicks 6137 } 6139 prtAlertIndex OBJECT-TYPE 6140 -- NOTE: In RFC 1759, the range was not defined. 6141 SYNTAX Integer32 (1..2147483647) 6142 MAX-ACCESS not-accessible 6143 STATUS current 6144 DESCRIPTION 6145 "The index value used to determine which alerts have been added 6146 or removed from the alert table. This is an incrementing 6147 integer initialized to 1 when the printer is reset. (i.e. The 6148 first event placed in the alert table after a reset of the 6149 printer shall have an index value of 1.) When the printer adds 6150 an alert to the table, that alert is assigned the next higher 6151 integer value from the last item entered into the table. If 6152 the index value reaches its maximum value, the next index value 6153 used must be 1. 6155 NOTE: The management application will read the alert table when 6156 a trap or event notification occurs or at a periodic rate and 6157 then parse the table to determine if any new entries were added 6158 by comparing the last known index value with the current 6159 highest index value. The management application will then 6160 update its copy of the alert table. When the printer discovers 6161 that an alert is no longer active, the printer shall remove the 6162 row for that alert from the table and shall reduce the number 6163 of rows in the table. The printer may add or delete any number 6164 of rows from the table at any time. The management station can 6165 detect when binary change alerts have been deleted by 6166 requesting an attribute of each alert, and noting alerts as 6167 deleted when that retrieval is not possible. The objects 6168 'prtAlertCriticalEvents'and 'prtAlertAllEvents' in the 6169 'prtGeneralTable' reduce the need for management applications 6170 to scan the 'prtAlertTable'. 6172 NOTE: The above description has been modified from RFC 1759 6173 for clarification." 6174 ::= { prtAlertEntry 1 } 6176 prtAlertSeverityLevel OBJECT-TYPE 6177 -- NOTE: In RFC 1759, the enumeration values were implicitly 6178 -- defined by this object. 6179 SYNTAX PrtAlertSeverityLevelTC 6180 MAX-ACCESS read-only 6181 STATUS current 6182 DESCRIPTION 6183 "The level of severity of this alert table entry. The printer 6184 determines the severity level assigned to each entry into the 6185 table." 6186 ::= { prtAlertEntry 2 } 6188 prtAlertTrainingLevel OBJECT-TYPE 6189 -- NOTE: In RFC 1759, the enumeration values were implicitly 6190 -- defined by this object. 6191 SYNTAX PrtAlertTrainingLevelTC 6192 MAX-ACCESS read-only 6193 STATUS current 6194 DESCRIPTION 6195 "See textual convention PrtAlertTrainingLevelTC. 6197 NOTE: The above description has been modified from RFC 1759 6198 for clarification." 6199 ::= { prtAlertEntry 3 } 6201 prtAlertGroup OBJECT-TYPE 6202 -- NOTE: In RFC 1759, the enumeration values were implicitly 6203 -- defined by this object. 6204 SYNTAX PrtAlertGroupTC 6205 MAX-ACCESS read-only 6206 STATUS current 6207 DESCRIPTION 6208 "The type of sub-unit within the printer model that this alert 6209 is related. Input, output, and markers are examples of printer 6210 model groups, i.e., examples of types of sub-units. Wherever 6211 possible, these enumerations match the sub-identifier that 6212 identifies the relevant table in the printmib." 6213 ::= { prtAlertEntry 4 } 6215 prtAlertGroupIndex OBJECT-TYPE 6216 -- NOTE: In RFC 1759, the range was not defined. 6217 SYNTAX Integer32 (-1..2147483647) 6218 MAX-ACCESS read-only 6219 STATUS current 6220 DESCRIPTION 6221 "The low-order index of the row within the table identified 6222 by prtAlertGroup that represents the sub-unit of the printer 6223 that caused this alert, or -1 if not applicable. The 6224 combination of the prtAlertGroup and the prtAlertGroupIndex 6225 defines exactly which printer sub-unit caused the alert; for 6226 example, Input #3, Output#2, and Marker #1. Every object in 6227 this MIB is indexed with hrDeviceIndex and optionally, another 6228 index variable. If this other index variable is present in the 6229 table that generated the alert, it will be used as the value 6230 for this object. Otherwise, this value shall be -1. 6232 NOTE: The above description has been modified from RFC 1759 6233 for clarification." 6234 ::= { prtAlertEntry 5 } 6236 prtAlertLocation OBJECT-TYPE 6237 -- NOTE: In RFC 1759, the range was not defined. 6238 SYNTAX Integer32 (-2..2147483647) 6239 MAX-ACCESS read-only 6240 STATUS current 6241 DESCRIPTION 6242 "The sub-unit location that is defined by the printer 6243 manufacturer to further refine the location of this alert 6244 within the designated sub-unit. The location is used in 6245 conjunction with the Group and GroupIndex values; for example, 6246 there is an alert in Input #2 at location number 7. The value 6247 (-2) indicates unknown. 6249 NOTE: The above description has been modified from RFC 1759 6250 for clarification." 6251 ::= { prtAlertEntry 6 } 6253 prtAlertCode OBJECT-TYPE 6254 -- NOTE: In RFC 1759, the enumeration values were implicitly 6255 -- defined by this object. 6257 SYNTAX PrtAlertCodeTC 6258 MAX-ACCESS read-only 6259 STATUS current 6260 DESCRIPTION 6261 "See associated textual convention PrtAlertCodeTC. 6263 NOTE: The above description has been modified from RFC 1759 6264 for clarification." 6265 ::= { prtAlertEntry 7 } 6267 prtAlertDescription OBJECT-TYPE 6268 -- In RFC 1759, the SYNTAX was OCTET STRING. This has been changed 6269 -- to a TC to better support localization of the object. 6270 SYNTAX PrtLocalizedDescriptionStringTC 6271 MAX-ACCESS read-only 6272 STATUS current 6273 DESCRIPTION 6274 "A description of this alert entry in the localization 6275 specified by prtGeneralCurrentLocalization. The description is 6276 provided by the printer to further elaborate on the enumerated 6277 alert or provide information in the case where the code is 6278 classified as 'other' or 'unknown'. The printer is required to 6279 return a description string but the string may be a null 6280 string." 6281 ::= { prtAlertEntry 8 } 6283 prtAlertTime OBJECT-TYPE 6284 SYNTAX TimeTicks 6285 MAX-ACCESS read-only 6286 STATUS current 6287 DESCRIPTION 6288 "The value of sysUpTime at the time that this alert was 6289 generated." 6290 ::= { prtAlertEntry 9 } 6292 printerV1Alert OBJECT-IDENTITY 6293 STATUS current 6294 DESCRIPTION 6295 "The value of the enterprise-specific OID in an SNMPv1 trap 6296 sent signaling a critical event in the prtAlertTable." 6297 ::= { prtAlert 2 } 6299 printerV2AlertPrefix OBJECT IDENTIFIER ::= { printerV1Alert 0 } 6301 printerV2Alert NOTIFICATION-TYPE 6302 OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, 6303 prtAlertGroupIndex, prtAlertLocation, prtAlertCode } 6304 STATUS current 6305 DESCRIPTION 6306 "This trap is sent whenever a critical event is added to the 6307 prtAlertTable. 6309 NOTE: The prtAlertIndex object was redundantly included in the 6310 bindings of the 'printerV2Alert' notification in RFC 1759, even 6311 though the value exists in the instance qualifier of all the 6312 other bindings. This object has been retained to provide 6313 compatiblity with existing RFC 1759 implementaions." 6314 ::= { printerV2AlertPrefix 1 } 6316 -- Note that the SNMPv2 to SNMPv1 translation rules dictate that 6317 -- the preceding structure will result in SNMPv1 traps of the 6318 -- following form: 6319 -- 6320 -- printerAlert TRAP-TYPE 6321 -- ENTERPRISE printerV1Alert 6322 -- VARIABLES { prtAlertIndex, prtAlertSeverityLevel, 6323 -- prtAlertGroup, prtAlertGroupIndex, 6324 -- prtAlertLocation, prtAlertCode } 6325 -- DESCRIPTION 6326 -- "This trap is sent whenever a critical event is added 6327 -- to the prtAlertTable." 6328 -- ::= 1 6330 -- Conformance Information 6332 prtMIBConformance OBJECT IDENTIFIER ::= { printmib 2 } 6334 -- compliance statements 6336 prtMIBCompliance MODULE-COMPLIANCE 6337 STATUS current 6338 DESCRIPTION 6339 "The compliance statement for agents that implement the 6340 printer MIB." 6341 MODULE -- this module 6342 MANDATORY-GROUPS { prtGeneralGroup, prtInputGroup, 6343 prtOutputGroup, 6344 prtMarkerGroup, prtMediaPathGroup, 6345 prtChannelGroup, prtInterpreterGroup, 6346 prtConsoleGroup, prtAlertTableGroup } 6348 OBJECT prtGeneralReset 6349 SYNTAX INTEGER { 6350 notResetting(3), 6351 resetToNVRAM(5) 6352 } 6353 DESCRIPTION 6354 "It is conformant to implement just these two states in this 6355 object. Any additional states are optional." 6357 OBJECT prtGeneralCurrentLocalization 6358 MIN-ACCESS read-only 6359 DESCRIPTION 6360 "It is conformant to implement this object as read-only" 6362 OBJECT prtGeneralCurrentOperator 6363 MIN-ACCESS read-only 6364 DESCRIPTION 6365 "It is conformant to implement this object as read-only" 6367 OBJECT prtGeneralServicePerson 6368 MIN-ACCESS read-only 6369 DESCRIPTION 6370 "It is conformant to implement this object as read-only" 6372 OBJECT prtGeneralPrinterName 6373 MIN-ACCESS read-only 6374 DESCRIPTION 6375 "It is conformant to implement this object as read-only" 6377 OBJECT prtGeneralSerialNumber 6378 MIN-ACCESS read-only 6379 DESCRIPTION 6380 "It is conformant to implement this object as read-only" 6382 OBJECT prtInputDefaultIndex 6383 MIN-ACCESS read-only 6384 DESCRIPTION 6385 "It is conformant to implement this object as read-only" 6387 OBJECT prtInputMediaDimFeedDirDeclared 6388 MIN-ACCESS read-only 6389 DESCRIPTION 6390 "It is conformant to implement this object as read-only" 6392 OBJECT prtInputMaxCapacity 6393 MIN-ACCESS read-only 6394 DESCRIPTION 6395 "It is conformant to implement this object as read-only" 6397 OBJECT prtInputCurrentLevel 6398 MIN-ACCESS read-only 6399 DESCRIPTION 6400 "It is conformant to implement this object as read-only" 6402 OBJECT prtInputMediaName 6403 MIN-ACCESS read-only 6404 DESCRIPTION 6405 "It is conformant to implement this object as read-only" 6407 OBJECT prtInputName 6408 MIN-ACCESS read-only 6409 DESCRIPTION 6410 "It is conformant to implement this object as read-only" 6412 OBJECT prtInputSecurity 6413 MIN-ACCESS read-only 6414 DESCRIPTION 6415 "It is conformant to implement this object as read-only" 6417 OBJECT prtInputMediaWeight 6418 MIN-ACCESS read-only 6419 DESCRIPTION 6420 "It is conformant to implement this object as read-only" 6422 OBJECT prtInputMediaType 6423 MIN-ACCESS read-only 6424 DESCRIPTION 6425 "It is conformant to implement this object as read-only" 6427 OBJECT prtInputMediaColor 6428 MIN-ACCESS read-only 6429 DESCRIPTION 6430 "It is conformant to implement this object as read-only" 6432 OBJECT prtInputMediaFormParts 6433 MIN-ACCESS read-only 6434 DESCRIPTION 6435 "It is conformant to implement this object as read-only" 6437 OBJECT prtOutputDefaultIndex 6438 MIN-ACCESS read-only 6439 DESCRIPTION 6440 "It is conformant to implement this object as read-only" 6442 OBJECT prtOutputMaxCapacity 6443 MIN-ACCESS read-only 6444 DESCRIPTION 6445 "It is conformant to implement this object as read-only" 6447 OBJECT prtOutputRemainingCapacity 6448 MIN-ACCESS read-only 6449 DESCRIPTION 6450 "It is conformant to implement this object as read-only" 6452 OBJECT prtOutputName 6453 MIN-ACCESS read-only 6454 DESCRIPTION 6455 "It is conformant to implement this object as read-only" 6457 OBJECT prtOutputSecurity 6458 MIN-ACCESS read-only 6459 DESCRIPTION 6460 "It is conformant to implement this object as read-only" 6462 OBJECT prtOutputMaxDimFeedDir 6463 MIN-ACCESS read-only 6464 DESCRIPTION 6465 "It is conformant to implement this object as read-only" 6467 OBJECT prtOutputMaxDimXFeedDir 6468 MIN-ACCESS read-only 6469 DESCRIPTION 6470 "It is conformant to implement this object as read-only" 6472 OBJECT prtOutputMinDimFeedDir 6473 MIN-ACCESS read-only 6474 DESCRIPTION 6475 "It is conformant to implement this object as read-only" 6477 OBJECT prtOutputMinDimXFeedDir 6478 MIN-ACCESS read-only 6479 DESCRIPTION 6480 "It is conformant to implement this object as read-only" 6482 OBJECT prtOutputStackingOrder 6483 MIN-ACCESS read-only 6484 DESCRIPTION 6485 "It is conformant to implement this object as read-only" 6487 OBJECT prtOutputPageDeliveryOrientation 6488 MIN-ACCESS read-only 6489 DESCRIPTION 6490 "It is conformant to implement this object as read-only" 6492 OBJECT prtOutputBursting 6493 MIN-ACCESS read-only 6494 DESCRIPTION 6495 "It is conformant to implement this object as read-only" 6497 OBJECT prtOutputDecollating 6498 MIN-ACCESS read-only 6499 DESCRIPTION 6500 "It is conformant to implement this object as read-only" 6502 OBJECT prtOutputPageCollated 6503 MIN-ACCESS read-only 6504 DESCRIPTION 6505 "It is conformant to implement this object as read-only" 6507 OBJECT prtOutputOffsetStacking 6508 MIN-ACCESS read-only 6509 DESCRIPTION 6510 "It is conformant to implement this object as read-only" 6512 OBJECT prtMarkerDefaultIndex 6513 MIN-ACCESS read-only 6514 DESCRIPTION 6515 "It is conformant to implement this object as read-only" 6517 OBJECT prtMarkerSuppliesMaxCapacity 6518 MIN-ACCESS read-only 6519 DESCRIPTION 6520 "It is conformant to implement this object as read-only" 6522 OBJECT prtMarkerSuppliesLevel 6523 MIN-ACCESS read-only 6524 DESCRIPTION 6525 "It is conformant to implement this object as read-only" 6527 OBJECT prtMediaPathDefaultIndex 6528 MIN-ACCESS read-only 6529 DESCRIPTION 6530 "It is conformant to implement this object as read-only" 6532 OBJECT prtChannelCurrentJobCntlLangIndex 6533 MIN-ACCESS read-only 6534 DESCRIPTION 6535 "It is conformant to implement this object as read-only" 6537 OBJECT prtChannelDefaultPageDescLangIndex 6538 MIN-ACCESS read-only 6539 DESCRIPTION 6540 "It is conformant to implement this object as read-only" 6542 OBJECT prtChannelState 6543 MIN-ACCESS read-only 6544 DESCRIPTION 6545 "It is conformant to implement this object as read-only" 6547 OBJECT prtChannelIfIndex 6548 MIN-ACCESS read-only 6549 DESCRIPTION 6550 "It is conformant to implement this object as read-only" 6552 OBJECT prtInterpreterDefaultOrientation 6553 MIN-ACCESS read-only 6554 DESCRIPTION 6555 "It is conformant to implement this object as read-only" 6557 OBJECT prtInterpreterDefaultCharSetIn 6558 MIN-ACCESS read-only 6559 DESCRIPTION 6560 "It is conformant to implement this object as read-only" 6562 OBJECT prtInterpreterDefaultCharSetOut 6563 MIN-ACCESS read-only 6564 DESCRIPTION 6565 "It is conformant to implement this object as read-only" 6567 OBJECT prtConsoleLocalization 6568 MIN-ACCESS read-only 6569 DESCRIPTION 6570 "It is conformant to implement this object as read-only" 6572 OBJECT prtConsoleDisable 6573 MIN-ACCESS read-only 6574 DESCRIPTION 6575 "It is conformant to implement this object as read-only" 6577 OBJECT prtConsoleDisplayBufferText 6578 MIN-ACCESS read-only 6579 DESCRIPTION 6580 "It is conformant to implement this object as read-only" 6582 OBJECT prtConsoleOnTime 6583 MIN-ACCESS read-only 6584 DESCRIPTION 6585 "It is conformant to implement this object as read-only" 6587 OBJECT prtConsoleOffTime 6588 MIN-ACCESS read-only 6589 DESCRIPTION 6590 "It is conformant to implement this object as read-only" 6592 GROUP prtResponsiblePartyGroup 6593 DESCRIPTION 6594 "This group is unconditionally optional." 6596 GROUP prtExtendedInputGroup 6597 DESCRIPTION 6598 "This group is unconditionally optional." 6600 GROUP prtInputMediaGroup 6601 DESCRIPTION 6602 "This group is unconditionally optional." 6604 GROUP prtExtendedOutputGroup 6605 DESCRIPTION 6606 "This group is unconditionally optional." 6608 GROUP prtOutputDimensionsGroup 6609 DESCRIPTION 6610 "This group is unconditionally optional." 6612 GROUP prtOutputFeaturesGroup 6613 DESCRIPTION 6614 "This group is unconditionally optional." 6616 GROUP prtMarkerSuppliesGroup 6617 DESCRIPTION 6618 "This group is unconditionally optional." 6620 GROUP prtMarkerColorantGroup 6621 DESCRIPTION 6622 "This group is unconditionally optional." 6624 GROUP prtAlertTimeGroup 6625 DESCRIPTION 6626 "This group is unconditionally optional." 6628 -- the prtResponsiblePartyGroup, prtExtendedInputGroup, 6629 -- prtInputMediaGroup, prtExtendedOutputGroup, 6630 -- prtOutputDimensionsGroup, prtOutputFeaturesGroup, 6631 -- prtMarkerSuppliesGroup, prtMarkerColorantGroup, and the 6632 -- prtAlertTimeGroup are completely optional. However, it is 6633 -- strongly RECOMMENDED that the prtAlertTimeGroup be implemented. 6635 -- New to version 2 of this printer MIB: 6636 OBJECT prtAuxiliarySheetStartupPage 6637 MIN-ACCESS read-only 6638 DESCRIPTION 6639 "It is conformant to implement this object as read-only" 6641 OBJECT prtAuxiliarySheetBannerPage 6642 MIN-ACCESS read-only 6643 DESCRIPTION 6644 "It is conformant to implement this object as read-only" 6646 OBJECT prtInputMediaLoadTimeout 6647 MIN-ACCESS read-only 6648 DESCRIPTION 6649 "It is conformant to implement this object as read-only" 6651 OBJECT prtInputNextIndex 6652 MIN-ACCESS read-only 6653 DESCRIPTION 6654 "It is conformant to implement this object as read-only" 6656 GROUP prtAuxiliarySheetGroup 6657 DESCRIPTION 6658 "This group is unconditionally optional." 6660 GROUP prtInputSwitchingGroup 6661 DESCRIPTION 6662 "This group is unconditionally optional." 6664 GROUP prtGeneralV2Group 6665 DESCRIPTION 6666 "This group is unconditionally optional." 6668 GROUP prtAlertTableV2Group 6669 DESCRIPTION 6670 "This group is unconditionally optional." 6672 GROUP prtChannelV2Group 6673 DESCRIPTION 6674 "This group is unconditionally optional." 6676 GROUP prtAlertTrapGroup 6677 DESCRIPTION 6678 "This group is unconditionally optional." 6679 ::= { prtMIBConformance 1 } 6681 prtMIBGroups OBJECT IDENTIFIER ::= { prtMIBConformance 2 } 6683 prtGeneralGroup OBJECT-GROUP 6684 OBJECTS { prtGeneralConfigChanges, 6685 prtGeneralCurrentLocalization, 6686 prtGeneralReset, prtCoverDescription, 6687 prtCoverStatus, 6688 prtLocalizationLanguage, prtLocalizationCountry, 6689 prtLocalizationCharacterSet, prtStorageRefIndex, 6690 prtDeviceRefIndex } 6691 STATUS current 6692 DESCRIPTION 6693 "The general printer group." 6694 ::= { prtMIBGroups 1 } 6696 prtResponsiblePartyGroup OBJECT-GROUP 6697 OBJECTS { prtGeneralCurrentOperator, prtGeneralServicePerson } 6698 STATUS current 6699 DESCRIPTION 6700 "The responsible party group contains contact information for 6701 humans responsible for the printer." 6702 ::= { prtMIBGroups 2 } 6704 prtInputGroup OBJECT-GROUP 6705 OBJECTS { prtInputDefaultIndex, prtInputType, prtInputDimUnit, 6706 prtInputMediaDimFeedDirDeclared, 6707 prtInputMediaDimXFeedDirDeclared, 6708 prtInputMediaDimFeedDirChosen, 6709 prtInputMediaDimXFeedDirChosen, prtInputCapacityUnit, 6710 prtInputMaxCapacity, prtInputCurrentLevel, prtInputStatus, 6711 prtInputMediaName } 6712 STATUS current 6713 DESCRIPTION 6714 "The input group." 6715 ::= { prtMIBGroups 3 } 6717 prtExtendedInputGroup OBJECT-GROUP 6718 OBJECTS { prtInputName, prtInputVendorName, prtInputModel, 6719 prtInputVersion, prtInputSerialNumber, 6720 prtInputDescription, prtInputSecurity } 6721 STATUS current 6722 DESCRIPTION 6723 "The extended input group." 6724 ::= { prtMIBGroups 4 } 6726 prtInputMediaGroup OBJECT-GROUP 6727 OBJECTS { prtInputMediaWeight, prtInputMediaType, 6728 prtInputMediaColor, prtInputMediaFormParts } 6729 STATUS current 6730 DESCRIPTION 6731 "The input media group." 6732 ::= { prtMIBGroups 5 } 6734 prtOutputGroup OBJECT-GROUP 6735 OBJECTS { prtOutputDefaultIndex, prtOutputType, 6736 prtOutputCapacityUnit, prtOutputMaxCapacity, 6737 prtOutputRemainingCapacity, prtOutputStatus } 6738 STATUS current 6739 DESCRIPTION 6740 "The output group." 6741 ::= { prtMIBGroups 6 } 6743 prtExtendedOutputGroup OBJECT-GROUP 6744 OBJECTS { prtOutputName, prtOutputVendorName, prtOutputModel, 6745 prtOutputVersion, prtOutputSerialNumber, 6746 prtOutputDescription, prtOutputSecurity } 6747 STATUS current 6748 DESCRIPTION 6749 "The extended output group." 6750 ::= { prtMIBGroups 7 } 6752 prtOutputDimensionsGroup OBJECT-GROUP 6753 OBJECTS { prtOutputDimUnit, prtOutputMaxDimFeedDir, 6754 prtOutputMaxDimXFeedDir, prtOutputMinDimFeedDir, 6755 prtOutputMinDimXFeedDir } 6756 STATUS current 6757 DESCRIPTION 6758 "The output dimensions group" 6759 ::= { prtMIBGroups 8 } 6761 prtOutputFeaturesGroup OBJECT-GROUP 6762 OBJECTS { prtOutputStackingOrder, 6763 prtOutputPageDeliveryOrientation, prtOutputBursting, 6764 prtOutputDecollating, prtOutputPageCollated, 6765 prtOutputOffsetStacking } 6766 STATUS current 6767 DESCRIPTION 6768 "The output features group." 6769 ::= { prtMIBGroups 9 } 6771 prtMarkerGroup OBJECT-GROUP 6772 OBJECTS { prtMarkerDefaultIndex, prtMarkerMarkTech, 6773 prtMarkerCounterUnit, prtMarkerLifeCount, 6774 prtMarkerPowerOnCount, prtMarkerProcessColorants, 6775 prtMarkerSpotColorants, prtMarkerAddressabilityUnit, 6776 prtMarkerAddressabilityFeedDir, 6777 prtMarkerAddressabilityXFeedDir, prtMarkerNorthMargin, 6778 prtMarkerSouthMargin, prtMarkerWestMargin, 6779 prtMarkerEastMargin, prtMarkerStatus } 6780 STATUS current 6781 DESCRIPTION 6782 "The marker group." 6783 ::= { prtMIBGroups 10 } 6785 prtMarkerSuppliesGroup OBJECT-GROUP 6786 OBJECTS { prtMarkerSuppliesMarkerIndex, 6787 prtMarkerSuppliesColorantIndex, prtMarkerSuppliesClass, 6788 prtMarkerSuppliesType, prtMarkerSuppliesDescription, 6789 prtMarkerSuppliesSupplyUnit, 6790 prtMarkerSuppliesMaxCapacity, prtMarkerSuppliesLevel } 6791 STATUS current 6792 DESCRIPTION 6793 "The marker supplies group." 6794 ::= { prtMIBGroups 11 } 6796 prtMarkerColorantGroup OBJECT-GROUP 6797 OBJECTS { prtMarkerColorantMarkerIndex, prtMarkerColorantRole, 6798 prtMarkerColorantValue, prtMarkerColorantTonality } 6799 STATUS current 6800 DESCRIPTION 6801 "The marker colorant group." 6802 ::= { prtMIBGroups 12 } 6804 prtMediaPathGroup OBJECT-GROUP 6805 OBJECTS { prtMediaPathDefaultIndex, prtMediaPathMaxSpeedPrintUnit, 6806 prtMediaPathMediaSizeUnit, prtMediaPathMaxSpeed, 6807 prtMediaPathMaxMediaFeedDir, 6808 prtMediaPathMaxMediaXFeedDir, 6809 prtMediaPathMinMediaFeedDir, 6810 prtMediaPathMinMediaXFeedDir, prtMediaPathType, 6811 prtMediaPathDescription, prtMediaPathStatus} 6812 STATUS current 6813 DESCRIPTION 6814 "The media path group." 6815 ::= { prtMIBGroups 13 } 6817 prtChannelGroup OBJECT-GROUP 6818 OBJECTS { prtChannelType, prtChannelProtocolVersion, 6819 prtChannelCurrentJobCntlLangIndex, 6820 prtChannelDefaultPageDescLangIndex, prtChannelState, 6821 prtChannelIfIndex, prtChannelStatus 6822 } 6823 STATUS current 6824 DESCRIPTION 6825 "The channel group." 6826 ::= { prtMIBGroups 14 } 6828 prtInterpreterGroup OBJECT-GROUP 6829 OBJECTS { prtInterpreterLangFamily, prtInterpreterLangLevel, 6830 prtInterpreterLangVersion, prtInterpreterDescription, 6831 prtInterpreterVersion, prtInterpreterDefaultOrientation, 6832 prtInterpreterFeedAddressability, 6833 prtInterpreterXFeedAddressability, 6834 prtInterpreterDefaultCharSetIn, 6835 prtInterpreterDefaultCharSetOut, prtInterpreterTwoWay } 6836 STATUS current 6837 DESCRIPTION 6838 "The interpreter group." 6839 ::= { prtMIBGroups 15 } 6841 prtConsoleGroup OBJECT-GROUP 6842 OBJECTS { prtConsoleLocalization, prtConsoleNumberOfDisplayLines, 6843 prtConsoleNumberOfDisplayChars, prtConsoleDisable, 6844 prtConsoleDisplayBufferText, prtConsoleOnTime, 6845 prtConsoleOffTime, prtConsoleColor, 6846 prtConsoleDescription } 6847 STATUS current 6848 DESCRIPTION 6849 "The console group." 6850 ::= { prtMIBGroups 16 } 6852 prtAlertTableGroup OBJECT-GROUP 6853 OBJECTS { prtAlertSeverityLevel, prtAlertTrainingLevel, 6854 prtAlertGroup, prtAlertGroupIndex, prtAlertLocation, 6855 prtAlertCode, prtAlertDescription } 6856 STATUS current 6857 DESCRIPTION 6858 "The alert table group." 6859 ::= { prtMIBGroups 17 } 6861 prtAlertTimeGroup OBJECT-GROUP 6862 OBJECTS { prtAlertTime } 6863 STATUS current 6864 DESCRIPTION 6865 "The alert time group. Implementation of prtAlertTime is 6866 strongly RECOMMENDED." 6867 ::= { prtMIBGroups 18 } 6869 prtAuxiliarySheetGroup OBJECT-GROUP 6870 OBJECTS { prtAuxiliarySheetStartupPage, 6871 prtAuxiliarySheetBannerPage } 6872 STATUS current 6873 DESCRIPTION 6874 "The auxiliary sheet group." 6875 ::= { prtMIBGroups 19 } 6877 prtInputSwitchingGroup OBJECT-GROUP 6878 OBJECTS { prtInputMediaLoadTimeout, prtInputNextIndex } 6879 STATUS current 6880 DESCRIPTION 6881 "The input switching group." 6882 ::= { prtMIBGroups 20 } 6884 prtGeneralV2Group OBJECT-GROUP 6885 OBJECTS { prtGeneralPrinterName, prtGeneralSerialNumber } 6886 STATUS current 6887 DESCRIPTION 6888 "The general printer group with new v2 objects." 6889 ::= { prtMIBGroups 21 } 6891 prtAlertTableV2Group OBJECT-GROUP 6892 OBJECTS { prtAlertCriticalEvents, prtAlertAllEvents } 6893 STATUS current 6894 DESCRIPTION 6895 "The alert table group with new v2 objects." 6896 ::= { prtMIBGroups 22 } 6898 prtChannelV2Group OBJECT-GROUP 6899 OBJECTS { prtChannelInformation } 6900 STATUS current 6901 DESCRIPTION 6902 "The channel group with a new v2 object." 6903 ::= { prtMIBGroups 23 } 6905 prtAlertTrapGroup NOTIFICATION-GROUP 6906 NOTIFICATIONS { printerV2Alert } 6907 STATUS current 6908 DESCRIPTION 6909 "The alert trap group." 6910 ::= { prtMIBGroups 24 } 6912 END 6914 7. IANA Considerations 6916 The initial version the IANA Printer MIB defined in section 5 of this 6917 document is to be archived by IANA and subsequently maintained 6918 according to the Process specified in section 2.4.1 of this document. 6920 8. Internationalization Considerations 6922 See section 2.2.1.1, 'International Considerations'. 6924 9. Security Considerations 6926 The Printer MIB specifies a database and not necessarily a protocol 6927 for accessing the database. With regards to the security of the 6928 information within the database, it is anticipated that the primary 6929 vehicle for accessing this data will be through the use of the Simple 6930 Network Protocol (SNMP). There are a number of management objects 6931 defined in this MIB that have a MAX-ACCESS clause of read-write. 6932 Such objects may be considered sensitive or vulnerable in some 6933 network environments. The support for SET operations in a non-secure 6934 environment without proper protection can have a negative effect on 6935 network operations. 6937 SNMPv1 by itself is not a secure environment. Even if the network is 6938 secure (for example by using IPSec), there is no control as to who on 6939 the secure network is allowed to access and GET/SET (read/change) the 6940 objects in this MIB. 6942 It is recommended that implementers consider the security features 6943 provided by the SNMPv3 framework. Specifically, the use of the User- 6944 based Security Model [RFC2574]) and the View-based Access Control 6945 Model [RFC2575] is recommended. 6947 It is then a customer/user responsibility to ensure that the SNMP 6948 entity giving access to an instance of this MIB, is properly 6949 configured to give access to the objects only to those principals 6950 (users) that have legitimate rights to indeed GET or SET them. 6952 Where the operational capability of the printing device are 6953 especially vulnerable or difficult to administer, certain objects 6954 within this MIB have been tagged as READ-ONLY, preventing 6955 modification. Further, for all READ-WRITE objects within the MIB, the 6956 working group has included specific conformance guidelines stating 6957 that vendors are free to implement these objects as READ-ONLY. This 6958 conformance allowance should cover cases where specific vendor 6959 vulnerabilities may differ from product to product. (See conformance 6960 section with regards to MIN-ACCESS clauses). 6962 10. Copyright Section 6964 "Copyright (C) The Internet Society 1995, 1997, 2002. All Rights 6965 Reserved. 6967 This document and translations of it may be copied and furnished to 6968 others, and derivative works that comment on or otherwise explain or 6969 assist in its implementation may be prepared, copied, published and 6970 distributed, in whole or in part, without restriction of any kind, 6971 provided that the above copyright notice and this paragraph are 6972 included on all such copies and derivative works. However, this 6973 document itself may not be modified in any way, such as by removing 6974 the copyright notice or references to the Internet Society or other 6975 Internet organizations, except as needed for the purpose of 6976 developing Internet standards in which case the procedures for 6977 copyrights defined in the Internet Standards process must be 6978 followed, or as required to translate it into languages other than 6979 English. 6981 The limited permissions granted above are perpetual and will not be 6982 revoked by the Internet Society or its successors or assigns. 6984 This document and the information contained herein is provided on an 6985 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 6986 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 6987 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 6988 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 6989 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 6991 11. Normative References 6993 Find IETF (Internet Engineering Task Force) RFCs at www.ietf.org. 6994 Find IANA (Internet Assigned Numbers Authority) at www.iana.org. 6995 Find ISO (International Organization for Standardization) at 6996 www.iso.ch. 6997 Find PWG (IEEE/ISTO Printer Working Group) at www.pwg.org. 6999 [ASCII] ANSI, "Coded Character Set - 7-bit American Standard Code 7000 for Information Interchange", ANSI X3.4-1986. 7002 [CHARSET] IANA Character Set Registry: 7003 http://www.iana.org/assignments/character-sets 7005 [CHARMIB] IANA Character Set MIB: 7006 http://www.iana.org/assignments/ianacharset-mib 7008 [ISO10175] ISO, "Document Printing Application (DPA)", ISO 10175, 7009 1996. 7011 [ISO10646] ISO, "Universal Multiple-Octet Coded Character Set 7012 (UCS) - Part 1: Architecture and Basic Multilingual Plane", ISO 7013 10646-1, September 2000. 7014 ISO, "Universal Multiple-Octet Coded Character Set (UCS) - 7015 Part 2: Supplemental Planes", ISO 10646-2, January 2001. 7017 [PWGMEDIA] IEEE-ISTO "The Printer Working Group Standard for Media 7018 Standardized Names", IEEE-ISTO 5101.1-2002. 7020 [RFC1213] McCloghrie & Rose, "Management Information Base for 7021 Network Management of TCP/IP-based internets: MIB-II", RFC 1213, 7022 1991. 7024 [RFC2026] Bradner, "The Internet Standards Process - Revision 3", 7025 RFC 2026, 1996. 7027 [RFC2119] Bradner, "Key words for use in RFCs to Indicate 7028 Requirement Levels", BCP 14, RFC 2119, March 1997. 7030 [RFC2277] Alvestrand, "IETF Policy on Character Sets and Languages", 7031 BCP 18, RFC 2277, 1998. 7033 [RFC2279] Yergeau, "UTF-8, a transformation format of ISO 10646", 7034 RFC 2279, 1998. 7036 [RFC2790] Waldbusser & Grillo, "Host Resources MIB", RFC 2790, 2000. 7038 [RFC2863] McCloghrie & Kastenholz, "The Interfaces Group MIB", RFC 7039 2863, June 2000. 7041 Note to RFC Editor: Insert RFC number 'nnnn' when assigned. 7042 [RFCnnnn] Bergman & Lewis, "Printer Finishing MIB", RFC nnnn, 2002. 7044 12. Informative References 7046 Find IETF (Internet Engineering Task Force) RFCs at www.ietf.org. 7048 [APPLEMAC] Apple staff, "Inside MacIntosh: Networking", 1994. 7050 [RFC854] Postel & Reynolds, "Telnet Protocol Specification", RFC 7051 854, 1983. 7053 [RFC959] Postel & Reynolds, "File Transfer Protocol", RFC 959, 1985. 7055 [RFC1155] Rose & McCloghrie, "Structure and Identification of 7056 Management Information for TCP/IP-based internets", 7058 [RFC1157] Case et al, "Simple Network Management Protocol", STD 15, 7059 RFC 1157, May 1990. 7061 [RFC1179] McLaughlin, "Line printer daemon protocol", RFC 1179, 7062 1990. 7064 [RFC1212] Rose & McCloghrie, "Concise MIB Definitions", STD 16, RFC 7065 1212, March 1991. 7067 [RFC1215] Rose, "A Convention for Defining Traps for use with the 7068 SNMP", RFC 1215, March 1991. 7070 [RFC1350] Sollins, "The TFTP Protocol (Revision 2)", RFC 1350, 1991. 7072 [RFC1901] Case et al, "Introduction to Community-based SNMPv2", RFC 7073 1901, January 1996. 7075 [RFC1905] Case et al, "Protocol Operations for Version 2 of the 7076 Simple Network Management Protocol (SNMPv2)", RFC 1905, January 7077 1996. 7079 [RFC1906] Case et al, "Transport Mappings for Version 2 of the 7080 Simple Network Management Protocol (SNMPv2)", RFC 1906, January 7081 1996. 7083 [RFC1945] Berners-Lee et al, "Hypertext Transfer Protocol - 7084 HTTP/1.0", RFC 1945, 1996. 7086 [RFC2246] Dierks & Allen, "The TLS Protocol Version 1.0", RFC 2246, 7087 1999. 7089 [RFC2396] Berners-Lee et al, "Uniform Resource Identifiers (URI): 7090 Generic Syntax", RFC 2396, 1998. 7092 [RFC2570] Case et al, "Introduction to Version 3 of the 7093 Internet-standard Network Management Framework", RFC 2570, April 7094 1999. 7096 [RFC2571] Harrington et al, "An Architecture for Describing SNMP 7097 Management Frameworks", RFC 2571, April 1999. 7099 [RFC2572] Case et al, "Message Processing and Dispatching for the 7100 Simple Network Management Protocol (SNMP)", RFC 2572, April 7101 1999. 7103 [RFC2573] Levi et al,"SNMPv3 Applications", RFC 2573, April 1999. 7105 [RFC2574] Blumenthal & Wijnen, "User-based Security Model (USM) for 7106 version 3 of the Simple Network Management Protocol (SNMPv3)", 7107 RFC 2574, April 1999. 7109 [RFC2575] Wijnen et al, "View-based Access Control Model (VACM) for 7110 the Simple Network Management Protocol (SNMP)", RFC 2575, April 7111 1999. 7113 [RFC2578] McCloghrie et al, "Structure of Management Information 7114 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 7116 [RFC2579] McCloghrie et al, "Textual Conventions for SMIv2", STD 58, 7117 RFC 2579, April 1999. 7119 [RFC2580] McCloghrie et al, "Conformance Statements for SMIv2", STD 7120 58, RFC 2580, April 1999. 7122 [RFC2616] Fielding et al, "Hypertext Transfer Protocol - HTTP/1.1", 7123 RFC 2616, 1999. 7125 [RFC2821] Klensin, "Simple Mail Transfer Protocol", RFC 2821, 2001. 7127 [RFC2822] Resnick, "Internet Message Format", RFC 2822, April 2001. 7129 [RFC2910] Herriot et al, "Internet Printing Protocol/1.1: Encoding 7130 and Transport", RFC 2910, 2000. 7132 [RFC2911] Hastings et al, "Internet Printing Protocol/1.1: Model 7133 and Semantics", RFC 2911, 2000. 7135 [RFC2978] Freed & Postel, "IANA Charset Registration Procedures", 7136 BCP 19, RFC 2978, 2000. 7138 [RFC3232] Reynolds, "Assigned Numbers: RFC 1700 is Replaced by an 7139 On-line Database", RFC 3232, January 2002. 7141 [RFC3285] Gahrns & Hain, "Using Microsoft Word to create Internet 7142 Drafts and RFCs", RFC 3285, May 2002. 7144 Appendix A - Glossary of Terms 7146 Addressability - On the marker, the number of distinct marking units 7147 (pels) per unit of addressability unit that can be set; for example, 7148 300 dots per inch is expressed as 300 per 1000 Thousandths Of Inches 7149 and 4 dots per millimeter is 4 per 1000 Micrometers. Addressability 7150 is not resolution because marks that are one addressability position 7151 apart may not be independently resolvable by the eye due to factors 7152 such as gain in the area of marks so they overlap or nearly touch. 7154 Alert - A reportable event for which there is an entry in the alert 7155 table. 7157 Bin - An output sub-unit which may or may not be removable. 7159 Binary Change Event - An event which comes in pairs; the leading edge 7160 event and the trailing edge event. The leading edge event enters a 7161 state from which there is only one exit. A binary change event may be 7162 critical or non-critical. See unary change event. 7164 Bursting - The process by which continuous media is separated into 7165 individual sheets, typically by bursting along pre-formed 7166 perforations. 7168 Channel - A term used to describe a single source of data which is 7169 presented to a printer. The model that we use in describing a 7170 printer allows for an arbitrary number of channels. Multiple 7171 channels can exist on the same physical port. This is commonly done 7172 over Ethernet ports where EtherTalk, TCP/IP, and SPX/IPX protocols 7173 can be supplying different data streams simultaneously to a single 7174 printer on the same physical port. 7176 Collation - In multiple copy output, placing the pages from separate 7177 copies into separate ordered sets, ready for binding. 7179 Control Language - A data syntax or language for controlling the 7180 printer through the print data channel. 7182 Critical Alert - An alert triggered by an event which leads to a 7183 state in which printing is no longer possible; the printer is 7184 stopped. 7186 Decollating - The process by which the individual parts within a 7187 multi-part form are separated and sorted into separate stacks for 7188 each part. 7190 Description - Information about the configuration and capabilities of 7191 the printer and its various sub-units. 7193 DPA - ISO 10175 Document Printing Application standard. A standard 7194 for a client server protocol for a print system, including (1) 7195 submitting print jobs to and (2) managing print jobs in a spooler. 7197 Event - A state change in the printer. 7199 Group - A collection of objects that represent a type of sub-unit of 7200 the printer. 7202 Host Resources MIB - See [RFC2790]. 7204 IANA - Internet Assigned Numbers Authority. See [RFC3232]. 7206 Idempotent - Idempotence is the property of an operation that results 7207 in the same state no matter how many times it is executed (at least 7208 once). This is a property that is shared by true databases in which 7209 operations on data items only change the state of the data item and 7210 do not have other side effects. Because the SNMP data model is that 7211 of operations on a database, SNMP MIB objects should be assumed to be 7212 idempotent. If a MIB object is defined in a non-idempotent way, the 7213 this data model can break in subtle ways when faced with packet loss, 7214 multiple managers, and other common conditions. 7216 In order to fulfill the common need for actions to result from 7217 SNMP Set operations, SNMP MIB objects can be modeled such that the 7218 change in state from one state to another has the side effect of 7219 causing an action. It is important to note that with this model, 7220 an SNMP operation that sets a value equal to its current value 7221 will cause no action. This retains the idempotence of a single 7222 command, while allowing actions to be initiated by SNMP SET 7223 requests. 7225 Input - A tray or bin from which instances of the media are obtained 7226 and fed into the Media Path. 7228 Interpreter - The embodiment of an algorithm that processes a data 7229 stream consisting of a Page Description Language (PDL) and/or a 7230 Control Language. 7232 Localization - The specification of human language, country, and 7233 character set needed to present information to people in their native 7234 languages. 7236 Management Application (a.k.a. Manager) - A program which queries and 7237 controls one or more managed nodes. 7239 Management Station - A physical computer on which one or more 7240 management applications can run. 7242 Media Path - The mechanisms that transport instances of the media 7243 from an input, through the marker, possibly through media buffers and 7244 duplex pathways, out to the output with optional finishing applied. 7245 The inputs and outputs are not part of the Media Path. 7247 Non-critical Alert - An alert triggered by a reportable event which 7248 does not lead to a state in which printing is no longer possible; 7249 such an alert may lead to a state from which printing may no longer 7250 be possible in the future, such as the low toner state or the alert 7251 may be pure informational, such as a configuration change at the 7252 printer. 7254 Output - A bin or stacker which accepts instances of media that have 7255 been processed by a printer. 7257 Page Description Language (PDL) - A data syntax or language for the 7258 electronic representation of a document as a sequence of page images. 7260 Printer - A physical device that takes media from an input source, 7261 produces marks on that media according to some page description or 7262 page control language and puts the result in some output destination, 7263 possibly with finishing applied. 7265 Printing - The entire process of producing a printed document from 7266 generation of the file to be printed, choosing printing properties, 7267 selection of a printer, routing, queuing, resource management, 7268 scheduling, and finally printing including notifying the user. 7270 Reportable event - An event that is deemed of interest to a 7271 management station watching the printer. 7273 Status - Information regarding the current operating state of the 7274 printer and its various sub-units. This is an abstraction of the 7275 exact physical condition of the printer. 7277 Sub-mechanism - A distinguishable part of a sub-unit. 7279 Sub-unit - A part of the printer which may be a physical part, such 7280 as one of the input sources or a logical part such as an interpreter. 7282 Tray - An input sub-unit which is typically removable. 7284 Unary Change Event - An event that indicates a change of state of the 7285 printer, but to a state which is (often) just as valid as the state 7286 that was left, and from which no return is necessary. See binary 7287 change event. 7289 Visible state - The portion of the state of the printer that can be 7290 examined by a management application. 7292 Warning - A non-critical alert. See non-critical alert. 7294 Appendix B - Media Size Names 7296 The PWG Standardized Media Names specification [PWGMEDIA], section 5 7297 Self Describing Names, contains the currently recommended media size 7298 names. This appendix lists the standardized media size names from 7299 ISO/IEC 10175 Document Printing Application (DPA), [ISO10175] as 7300 presented in RFC 1759. Management applications are encouraged to use 7301 the names from the PWG standard. However, many legacy systems exist 7302 that use the DPA names and they are presented here for the 7303 convenience of developers. 7305 A printer implementing the Printer MIB has no knowledge of these 7306 names, however; all media sizes in the MIB are given in terms of 7307 media dimensions as the values of prtInputMediaDimFeedDirChosen and 7308 prtInputMediaDimXFeedDirChosen. 7310 String name Description 7312 other 7314 unknown 7315 na-letter or letter North American letter size: 8.5 by 11 inches 7316 na-legal or legal North American legal size: 8.5 by 14 inches 7317 na-10x13-envelope North American 10x13 envelope 7318 size: 10 by 13 inches 7319 na-9x12-envelope North American 9x12 envelope 7320 size: 9 by 12 inches 7321 na-number-10-envelope North American number 10 business envelope 7322 size: 4.125 by 9.5 inches 7323 na-7x9-envelope North American 7x9 size: 7 by 9 inches 7324 na-9x11-envelope North American 9x11 size: 9 by 11 inches 7325 na-10x14-envelope North American 10x14 envelope 7326 size: 10 by 14 inches 7327 na-number-9-envelope North American number 9 business envelope 7328 size: 3.875 by 8.875 inches 7329 na-6x9-envelope North American 6x9 envelope 7330 size: 6 by 9 inches 7331 na-10x15-envelope North American 10x15 envelope 7332 size: 10 by 15 inches 7333 a engineering A size 8.5 inches by 11 inches 7334 b engineering B size 11 inches by 17 inches 7335 c engineering C size 17 inches by 22 inches 7336 d engineering D size 22 inches by 34 inches 7337 e engineering E size 34 inches by 44 inches 7338 iso-a0 ISO A0 size: 841 mm by 1189 mm 7339 iso-a1 ISO A1 size: 594 mm by 841 mm 7340 iso-a2 ISO A2 size: 420 mm by 594 mm 7341 iso-a3 ISO A3 size: 297 mm by 420 mm 7342 iso-a4 ISO A4 size: 210 mm by 297 mm 7343 iso-a5 ISO A5 size: 148 mm by 210 mm 7344 iso-a6 ISO A6 size: 105 mm by 148 mm 7345 iso-a7 ISO A7 size: 74 mm by 105 mm 7346 iso-a8 ISO A8 size: 52 mm by 74 mm 7347 iso-a9 ISO A9 size: 37 mm by 52 mm 7348 iso-a10 ISO A10 size: 26 mm by 37 mm 7349 iso-b0 ISO B0 size: 1000 mm by 1414 mm 7350 iso-b1 ISO B1 size: 707 mm by 1000 mm 7351 iso-b2 ISO B2 size: 500 mm by 707 mm 7352 iso-b3 ISO B3 size: 353 mm by 500 mm 7353 iso-b4 ISO B4 size: 250 mm by 353 mm 7354 iso-b5 ISO B5 size: 176 mm by 250 mm 7355 iso-b6 ISO B6 size: 125 mm by 176 mm 7356 iso-b7 ISO B7 size: 88 mm by 125 mm 7357 iso-b8 ISO B8 size: 62 mm by 88 mm 7358 iso-b9 ISO B9 size: 44 mm by 62 mm 7359 iso-b10 ISO B10 size: 31 mm by 44 mm 7360 iso-c0 ISO C0 size: 917 mm by 1297 mm 7361 iso-c1 ISO C1 size: 648 mm by 917 mm 7362 iso-c2 ISO C2 size: 458 mm by 648 mm 7363 iso-c3 ISO C3 size: 324 mm by 458 mm 7364 iso-c4 ISO C4 size: 229 mm by 324 mm 7365 iso-c5 ISO C5 size: 162 mm by 229 mm 7366 iso-c6 ISO C6 size: 114 mm by 162 mm 7367 iso-c7 ISO C7 size: 81 mm by 114 mm 7368 iso-c8 ISO C8 size: 57 mm by 81 mm 7369 iso-designated ISO Designated Long 7370 size: 110 mm by 220 mm 7371 jis-b0 JIS B0 size 1030 mm by 1456 mm 7372 jis-b1 JIS B1 size 728 mm by 1030 mm 7373 jis-b2 JIS B2 size 515 mm by 728 mm 7374 jis-b3 JIS B3 size 364 mm by 515 mm 7375 jis-b4 JIS B4 size 257 mm by 364 mm 7376 jis-b5 JIS B5 size 182 mm by 257 mm 7377 jis-b6 JIS B6 size 128 mm by 182 mm 7378 jis-b7 JIS B7 size 91 mm by 128 mm 7379 jis-b8 JIS B8 size 64 mm by 91 mm 7380 jis-b9 JIS B9 size 45 mm by 64 mm 7381 jis-b10 JIS B10 size 32 mm by 45 mm 7383 Appendix C - Media Names 7385 For the convenience of management application developers, this 7386 appendix lists the standardized media names from ISO/IEC 10175 7387 Document Printing Application (DPA), [ISO10175]. Management 7388 applications that present a dialogue for choosing media may wish to 7389 use these names as an alternative to separately specifying, size, 7390 color, and/or type. New names may also be created using this format 7391 and the names defined in the PWG Standardized Media Names 7392 specification [PWGMEDIA]. 7394 Using standard media names will mean that a single management 7395 application dealing with printers from different vendors and under 7396 different system mangers will tend to use the same names for the same 7397 media. If selection of media by name is used, the attributes (size, 7398 type or color) implied by the name must be explicitly mapped to the 7399 appropriate object (prtInputMediaDimFeedDirDeclared, 7400 prtInputMediaDimXFeedDirDeclared, prtInputMediaType and 7401 prtInputMediaColor) in the MIB. The object prtInputMediaName is 7402 intended for display to an operator and is purely descriptive. The 7403 value in prtInputMediaName is not interpreted by the printer so using 7404 a standard name for this value will not change any of the other media 7405 attributes nor will it cause an alert if the media in the input sub- 7406 unit does not match the name. 7408 Simple Name Descriptor Text 7410 other 7411 unknown 7412 iso-a4-white Specifies the ISO A4 white medium with 7413 size: 210 mm by 297 mm as defined in ISO 216 7414 iso-a4-coloured Specifies the ISO A4 colored medium with 7415 size: 210 mm by 297 mm as defined in ISO 216 7416 iso-a4-transparent Specifies the ISO A4 transparent medium with 7417 size: 210 mm by 297 mm as defined in ISO 216 7418 iso-a3-white Specifies the ISO A3 white medium with 7419 size: 297 mm by 420 mm as defined in ISO 216 7420 iso-a3-coloured Specifies the ISO A3 colored medium with 7421 size: 297 mm by 420 mm as defined in ISO 216 7422 iso-a5-white Specifies the ISO A5 white medium with 7423 size: 148 mm by 210 mm as defined in ISO 216 7424 iso-a5-coloured Specifies the ISO A5 colored medium with 7425 size: 148 mm by 210 mm as defined in ISO 216 7426 iso-b4-white Specifies the ISO B4 white medium with 7427 size: 250 mm by 353 mm as defined in ISO 216 7429 iso-b4-coloured Specifies the ISO B4 colored medium with 7430 size: 250 mm by 353 mm as defined in ISO 216 7431 iso-b5-white Specifies the ISO B5 white medium with 7432 size: 176 mm by 250 mm as defined in ISO 216 7433 iso-b5-coloured Specifies the ISO B5 colored medium with 7434 size: 176 mm by 250 mm as defined in ISO 216 7435 jis-b4-white Specifies the JIS B4 white medium with 7436 size: 257 mm by 364 mm as defined in JIS P0138 7437 jis-b4-coloured Specifies the JIS B4 colored medium with 7438 size: 257 mm by 364 mm as defined in JIS P0138 7439 jis-b5-white Specifies the JIS B5 white medium with 7440 size: 182 mm by 257 mm as defined in JIS P0138 7441 jis-b5-coloured Specifies the JIS B5 colored medium with 7442 size: 182 mm by 257 mm as defined in JIS P0138 7444 The following standard values are defined for North American media: 7446 na-letter-white Specifies the North American letter white 7447 medium with size: 8.5 inches by 11 inches 7448 na-letter-coloured Specifies the North American letter colored 7449 medium with size: 8.5 inches by 11 inches 7450 na-letter-transparent 7451 Specifies the North American letter 7452 transparent medium with size: 8.5 inches 7453 by 11 inches 7454 na-legal-white Specifies the North American legal white 7455 medium with size: 8.5 inches by 14 inches 7456 na-legal-coloured Specifies the North American legal colored 7457 medium with size: 8.5 inches by 14 inches 7459 The following standard values are defined for envelopes: 7461 iso-b5-envelope Specifies the ISO B5 envelope medium 7462 with size: 176 mm by 250 mm 7463 as defined in ISO 216 and ISO 269 7464 iso-b4-envelope Specifies the ISO B4 envelope medium 7465 with size: 250 mm by 353 mm 7466 as defined in ISO 216 7467 iso-c4-envelope Specifies the ISO C4 envelope medium 7468 with size: 229 mm by 324 mm 7469 as defined in ISO 216 and ISO 269 7470 iso-c5-envelope Specifies the ISO C5 envelope medium 7471 with size: 162 mm by 229 mm 7472 as defined in ISO 269 7473 iso-designated-long-envelope 7474 Specifies the ISO Designated Long envelope 7475 medium with size: 110 mm by 220 mm 7476 as defined in ISO 269 7478 na-10x13-envelope Specifies the North American 10x13 envelope 7479 medium with size: 10 inches by 13 inches 7480 na-9x12-envelope Specifies the North American 9x12 envelope 7481 medium with size: 9 inches by 12 inches 7482 na-number-10-envelope 7483 Specifies the North American number 10 7484 business envelope medium with size: 4.125 7485 inches by 9.5 inches 7486 na-7x9-envelope Specifies the North American 7x9 inch envelope 7488 na-9x11-envelope Specifies the North American 9x11 inch envelope 7490 na-10x14-envelope Specifies the North American 10x14 inch envelope 7492 na-number-9-envelope 7493 Specifies the North American number 9 7494 business envelope 3.875 by 8.875 inches 7495 na-6x9-envelope Specifies the North American 6x9 inch envelope 7497 na-10x15-envelope Specifies the North American 10x15 inch envelope 7499 The following standard values are defined for the less commonly 7500 used media (white-only): 7502 iso-a0-white Specifies the ISO A0 white medium 7503 with size: 841 mm by 1189 mm 7504 as defined in ISO 216 7505 iso-a1-white Specifies the ISO A1 white medium 7506 with size: 594 mm by 841 mm 7507 as defined in ISO 216 7508 iso-a2-white Specifies the ISO A2 white medium 7509 with size: 420 mm by 594 mm 7510 as defined in ISO 216 7511 iso-a6-white Specifies the ISO A6 white medium 7512 with size: 105 mm by 148 mm 7513 as defined in ISO 216 7514 iso-a7-white Specifies the ISO A7 white medium 7515 with size: 74 mm by 105 mm 7516 as defined in ISO 216 7517 iso-a8-white Specifies the ISO A8 white medium 7518 with size: 52 mm by 74 mm 7519 as defined in ISO 216 7520 iso-a9-white Specifies the ISO A9 white medium 7521 with size: 39 mm by 52 mm 7522 as defined in ISO 216 7523 iso-a10-white Specifies the ISO A10 white medium 7524 with size: 26 mm by 37 mm 7525 as defined in ISO 216 7526 iso-b0-white Specifies the ISO B0 white medium 7527 with size: 1000 mm by 1414 mm 7528 as defined in ISO 216 7529 iso-b1-white Specifies the ISO B1 white medium 7530 with size: 707 mm by 1000 mm 7531 as defined in ISO 216 7532 iso-b2-white Specifies the ISO B2 white medium 7533 with size: 500 mm by 707 mm 7534 as defined in ISO 216 7535 iso-b3-white Specifies the ISO B3 white medium 7536 with size: 353 mm by 500 mm 7537 as defined in ISO 216 7538 iso-b6-white Specifies the ISO B6 white medium 7539 with size: 125 mm by 176 mm i 7540 as defined in ISO 216 7541 iso-b7-white Specifies the ISO B7 white medium 7542 with size: 88 mm by 125 mm 7543 as defined in ISO 216 7544 iso-b8-white Specifies the ISO B8 white medium 7545 with size: 62 mm by 88 mm 7546 as defined in ISO 216 7547 iso-b9-white Specifies the ISO B9 white medium 7548 with size: 44 mm by 62 mm 7549 as defined in ISO 216 7550 iso-b10-white Specifies the ISO B10 white medium 7551 with size: 31 mm by 44 mm 7552 as defined in ISO 216 7553 jis-b0-white Specifies the JIS B0 white medium with size: 7554 1030 mm by 1456 mm 7555 jis-b1-white Specifies the JIS B1 white medium with size: 7556 728 mm by 1030 mm 7557 jis-b2-white Specifies the JIS B2 white medium with size: 7558 515 mm by 728 mm 7559 jis-b3-white Specifies the JIS B3 white medium with size: 7560 364 mm by 515 mm 7561 jis-b6-white Specifies the JIS B6 white medium with size: 7562 257 mm by 364 mm 7563 jis-b7-white Specifies the JIS B7 white medium with size: 7565 182 mm by 257 mm 7566 jis-b8-white Specifies the JIS B8 white medium with size: 7567 128 mm by 182 mm 7568 jis-b9-white Specifies the JIS B9 white medium with size: 7569 91 mm by 128 mm 7570 jis-b10-white Specifies the JIS B10 white medium with size: 7571 64 mm by 91 mm 7573 The following standard values are defined for engineering media: 7574 a Specifies the engineering A size medium with 7575 size: 8.5 inches by 11 inches 7576 b Specifies the engineering B size medium with 7577 size: 11 inches by 17 inches 7578 c Specifies the engineering C size medium with 7579 size: 17 inches by 22 inches 7580 d Specifies the engineering D size medium with 7581 size: 22 inches by 34 inches 7582 e Specifies the engineering E size medium with 7583 size: 34 inches by 44 inches 7585 Appendix D - Roles of Users 7587 Background 7589 The need for "Role Models" stemmed in large part from the need to 7590 understand the importance of any given proposed object for the MIB. 7591 Many times the real world need for a proposed object would be debated 7592 within the group; the debate would typically result in the need to 7593 describe the potential usage of the object in terms of a "live" 7594 person performing some type of printing-related task. 7596 Determining the value of a proposed object through identification of 7597 the associated human users was found to be so common that a more 7598 formalized model was required for consistent analysis. The model 7599 describing categories of human-oriented tasks is called "Role Models" 7600 in this document. 7602 In developing the Role Models it was necessary to identify the 7603 common, primary tasks that humans typically face when interacting 7604 with a printer and its related printing system(s). It was expected 7605 that certain kinds of tasks would serve to identify the various Role 7606 Models. 7608 In presenting the set of Role Models, the set of "Common Print System 7609 Tasks" are first presented, followed by the set of Role Model 7610 definitions. Finally, a simple matrix is presented in which Role 7611 Models and Tasks are cross-compared. 7613 Common Print System Tasks 7615 Upon researching the many tasks encountered by humans in dealing with 7616 printers and printing systems, the following were found to be 7617 pervasive within any operating environment: 7619 Printer job state - Determine the status of a job without a printer. 7621 Printer capabilities - Determine the current capabilities of a 7622 printer, for example, the available media sizes, two-sided printing, 7623 a particular type of interpreter, etc. 7625 Printer job submission - Submit a print job to a printer. 7627 Printer job removal - Remove a job from a printer. 7629 Notification of events - Receive notification of the existence of a 7630 defined printer event. An event can be of many types, including 7631 warnings, errors, job stage completion (e.g., "job done"), etc. 7633 Printer configuration - Query the current configuration of a printer. 7635 Printer consumables - Determine the current state of any and all 7636 consumables within a printer. 7638 Print job identification - Determine the identification of a job 7639 within a printer. 7641 Internal printer status - Determine the current status of the 7642 printer. 7644 Printer identification - Determine the identity of a printer. 7645 Printer location - Determine the physical location of a printer. 7647 Local system configuration - Determine various aspects of the current 7648 configuration of the local system involved with the operation of a 7649 printer. 7651 These "tasks" cover a large spectrum of requirements surrounding the 7652 operation of a printer in a network environment. This list serves as 7653 the basis for defining the various Role Models described below. 7655 Proposed Role Models 7657 Following is the list of "Role Models" used to evaluate the 7658 requirements for any given Printer MIB object. Note that the keyword 7659 enclosed in parentheses represents an abbreviation for the particular 7660 Role Model in the matrix described later in this document. 7662 User (USER) - A person or application that submits print jobs to the 7663 printer; typically viewed as the "end user" within the overall 7664 printing environment. 7666 Operator (OP) - A person responsible for maintaining a printer on a 7667 day-to-day basis, including such tasks as filling empty media trays, 7668 emptying full output trays, replacing toner cartridges, clearing 7669 simple paper jams, etc. 7671 Technician (TECH) - A person responsible for repairing a 7672 malfunctioning printer, performing routine preventive maintenance, 7673 and other tasks that typically require advanced training on the 7674 printer internals. An example of a "technician" would be a 7675 manufacturer's Field Service representative, or other person formally 7676 trained by the manufacturer or similar representative. 7678 System Manager (MGR) - A person responsible for configuration and 7679 troubleshooting of components involved in the overall printing 7680 environment, including printers, print queues and network 7681 connectivity issues. This person is typically responsible for 7682 ensuring the overall operational integrity of the print system 7683 components, and is typically viewed as the central point of 7684 coordination among all other Role Models. 7686 Help Desk (HELP) - A person responsible for supporting Users in 7687 their printing needs, including training Users and troubleshooting 7688 Users' printing problems. 7690 Asset Manager (AM) - A person responsible for managing an 7691 organization's printing system assets (primarily printers). Such a 7692 person needs to be able to identify and track the location of 7693 printing assets on an ongoing basis. 7695 Capacity Planner (CP) - A person responsible for tracking the usage 7696 of printing resources on an ongoing basis for the purpose of planning 7697 printer acquisitions and/or placement of printers based on usage 7698 trends. 7700 Installer (INST) - A person or application responsible for 7701 installing or configuring printing system components on a local 7702 system. 7704 Accountant (ACCT) - A person responsible for tracking the usage of 7705 printing resources on an ongoing basis for the purpose of charging 7706 Users for resources used. 7708 Matrix of Common Print System Tasks and Role Models 7710 To better understand the relationship between the set of defined 7711 "Common Print System Tasks" and the various "Role Models," the 7712 following matrix is provided. 7714 It is important to recognize that many of the tasks will appear to be 7715 applicable to many of the Role Models. However, when considering the 7716 actual context of a task, it is very important to realize that often 7717 the actual context of a task is such that the Role Model can change. 7719 For example, it is obvious that a "System Manager" must be able to 7720 submit print jobs to a printer; however, when submitting a print job, 7721 a person identified as a "System Manager" is actually operating in 7722 the context of a "User" in this case; hence, the requirement to 7723 submit a print job is not listed as a requirement for a System 7724 Manager. 7726 Conversely, while a "User" must be able to remove a job previously 7727 submitted to a printer, an "Operator" is often expected to be able to 7728 remove any print job from any printer; hence, print job removal is a 7729 (subtly different) requirement for both the "User" and "Operator" 7730 Role Models. 7732 Role Models 7733 ----------- 7735 Requirement Area USER OP TECH MGR HELP AM CP INST ACCT 7736 Print job status xx xx xx xx xx 7737 Printer capabilities xx xx xx 7738 Print job submission xx 7739 Print job removal xx xx 7740 Notification of events xx xx 7741 Printer configuration xx xx 7742 Printer consumables xx xx xx 7743 Print job identification xx xx xx xx xx 7744 Internal printer status xx xx xx 7745 Printer identification xx xx xx xx xx xx xx 7746 Printer location xx 7747 Local system configuration xx xx 7749 Appendix E - Overall Printer Status Table 7751 The Status Table establishes a convention for the top 25 printer 7752 errors. The table defines a suggested relationship between various 7753 printer states and the variables Printer hrDeviceStatus, 7754 hrPrinterStatus, hrPrinterDetectedErrorState, prtAlertGroup, 7755 prtAlertCode and various sub-unit status variables (prtInputStatus, 7756 prtOutputStatus, prtMarkerStatus, prtMediaPathStatus and 7757 prtChannelStatus). This table is the recommended implementation of 7758 these variables. It is provided to guide implementors of this MIB and 7759 users of the MIB by providing a sample set of states and the variable 7760 values that are expected to be produced as result of that state. This 7761 information supplements that provided in Section 2.2.13.2 "Overall 7762 Printer Status". This is not an exhaustive list rather it is a 7763 guideline. 7765 The definition of PrtSubUnitStatusTC specifies that SubUnitStatus is 7766 an integer that is the sum of 5 distinct values/states: Availability, 7767 Critical, Non-Critical, On-line and Transitioning. 7768 Thus when a non-critical alert or alerts are present the values for 7769 Availability, On-Line and Transitioning will be summed with the Non- 7770 Critical Alerts (8) value. 7772 The table was generated in landscape format and is located at 7773 ftp://ftp.pwg.org/pub/pwg/pmp/contributions/Top25Errors.pdf. 7775 Appendix F - Participants 7777 The following people attended at least one meeting of the Printer 7778 Working Group; many attended most meetings. 7780 Ron Bergman - Hitachi Printing Solutions 7781 Luis Cubero - Hewlett-Packard 7782 Jay Cummings - Novell 7783 Andy Davidson - Tektronix 7784 Lee Farrell - Canon 7785 Joel Gyllenskog - Microworks 7786 Tom Hastings - Xerox 7787 Scott Isaacson - Novell 7788 Binnur Al-Kazily - Hewlett-Packard 7789 Rick Landau - Digital Equipment Corporation 7790 David Kellerman - Northlake Software 7791 Harry Lewis - IBM 7792 Pete Loya - Hewlett-Packard 7793 Jay Martin - Underscore, Inc. 7794 Bob Pentecost - Hewlett-Packard 7795 Dave Roach - Unisys 7796 Stuart Rowley - Kyocera 7797 Bob Setterbo - Adobe 7798 Ron Smith - Texas Instruments 7799 Mike Timperman - Lexmark 7800 Randy Turner - 2Wire, Inc. 7801 Bill Wagner - NETsilicon, Inc. 7802 Chris Wellens - Interworking Labs 7803 Craig Whittle - Sharp Labs 7804 Don Wright - Lexmark 7805 Lloyd Young - Lexmark 7806 Atsushi Yuki - Kyocera 7807 Steve Zilles - Adobe 7809 Authors' Addresses 7811 Ron Bergman (Chairman) 7812 Hitachi Printing Solutions America 7813 1757 Tapo Canyon Road 7814 Simi Valley, CA 93063-3394 7815 Phone: (805) 578-4421 7816 Email: Ron.Bergman@hitachi-ps.us 7817 Harry Lewis 7818 IBM 7819 6300 Diagonal Hwy. 7820 Boulder, CO 80301 7821 Phone (303) 924-5337 7822 Email: harryl@us.ibm.com 7824 Ira McDonald 7825 High North Inc 7826 Phone: (906) 494-2434 or (906) 494-2697 7827 Email: imcdonald@sharplabs.com 7829 Significant contributors 7831 Ray Casterline 7832 Lighthouse Solutions, LLC 7833 Phone: (716) 218-9910 7834 Email: RayCasterline@lhsolutions.com 7836 Gary Gocek 7837 Phone: (585) 223-3826 7838 Email: gary@gocek.org 7840 Joel Gyllenskog 7841 Microworks, Inc. 7842 Phone: (208) 375-1234 7843 Email: joelgyllen@aol.com 7845 Thomas N. Hastings 7846 Xerox Corporation 7847 Phone: (310) 333-6413 7848 Email: hastings@cp10.es.xerox.com 7850 Scott Isaacson 7851 Novell 7852 Phone: (801) 861-7366 7853 Email: sisaacson@novell.com 7855 Binnur Al-Kazily 7856 Hewlett-Packard, Inc. 7857 Phone: (208) 396-6372 7858 Email: binnur_al-kazily@hp.com 7859 David Kellerman 7860 Northlake Software 7861 Phone: (503) 228-3383 7862 Email: kellerman@nls.com 7864 Matt King 7865 Lexmark International 7866 Phone: (859) 232-6907 7867 Email: emking@lexmark.com 7869 Jay Martin 7870 Underscore, Inc. 7871 Phone: (603) 889-7000 7872 Email: jkm@underscore.com 7874 Mike McKay 7875 Novell, Inc. 7877 Bob Pentecost 7878 Hewlett-Packard 7879 Phone: (208) 396-3312 7880 Email: bpenteco@boi.hp.com 7882 Stuart Rowley 7883 Kyocera 7884 Phone: (510) 299-7206 7885 Email: stuart.rowley@kyocera.com 7887 Ronald L. Smith 7888 Texas Instruments 7889 Phone: (817) 774-6151 7890 Email: rlsmith@nb.ppd.ti.com 7892 Gail Songer 7893 Peerless Systems Networking 7894 Phone: (650) 569-4414 7895 Email: gsonger@peerless.com 7897 Randy Turner 7898 2Wire, Inc. 7899 Phone (408) 895-1216 7900 Email: rturner@2wire.com 7901 William Wagner 7902 NETsilicon, Inc. 7903 Phone: (781) 398-4588 7904 Email: bwagner@digprod.com 7906 Steve Waldbusser 7907 Lucent Technologies 7908 Phone: (650) 318-1251 x1251 7909 Email: swaldbusser@lucent.com 7911 Chris Wellens 7912 Interworking Labs 7913 Phone: (408) 685-3190 7914 Email: chrisw@iwl.com 7916 F.D. Wright 7917 Lexmark International 7918 Phone: (859) 232-4808 7919 Email: don@lexmark.com 7921 Lloyd Young 7922 Lexmark International 7923 Phone: (859) 232-5150 7924 Email: lpyoung@lexmark.com 7926 Stephen N. Zilles 7927 Adobe Systems, Inc. 7928 Phone: (415) 962-4766 7929 Email: szilles@mv.us.adobe.com