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