idnits 2.17.1 draft-ietf-printmib-finishing-16.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: ---------------------------------------------------------------------------- ** 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. == The page length should not exceed 58 lines per page, but there was 11 longer pages, the longest (page 3) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 185 has weird spacing: '...t. Many objec...' == Line 213 has weird spacing: '...alue in the o...' == Line 1667 has weird spacing: '... sensed and i...' == 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: Informational]', 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 August 2003) is 7549 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'DPA' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMO' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWGMEDIA' ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCnnnn' -- Obsolete informational reference (is this intentional?): RFC 2911 (Obsoleted by RFC 8011) Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Ron Bergman 3 [Request for Comments: XXXX] Hitachi Printing Solutions 4 [Target Category: Informational] Harry Lewis 5 IBM Corporation 6 Ira McDonald 7 High North Inc 8 19 February 2003 10 Printer Finishing MIB 12 14 Expires 19 August 2003 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with all 19 provisions of section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet Engineering Task 22 Force (IETF), its areas, and its working groups. Note that other groups 23 may also distribute working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference material 28 or to cite them other than as "work in progress". 30 To learn the current status of any Internet-Draft, please check the 31 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 32 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 33 munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or 34 ftp.isi.edu (US West Coast). 36 Copyright Notice 38 Copyright (C) The Internet Society (2003). All Rights Reserved. 40 Abstract 42 This document defines a MIB module for the management of printer 43 finishing device subunits. The finishing device subunits applicable 44 to this MIB are an integral part of the Printer System. This MIB 45 does not apply to a Finisher Device that is not connected to a 46 Printer System. 48 TABLE OF CONTENTS 50 1. INTRODUCTION.......................................................2 51 1.1 Scope.............................................................3 52 1.2 Rational..........................................................3 53 1.3 The Internet-Standard Management Framework........................4 54 1.4 Read-Write Objects................................................4 55 2. TERMINOLOGY........................................................5 56 2.1 General Terminology...............................................5 57 2.2 Process Specific Terminology......................................9 58 3. FINISHER SUBUNITS INTEGRATED INTO THE PRINTER MODEL...............11 59 4. FINISHING SPECIFICATIONS..........................................12 60 4.1 Multiple finDeviceTable Entries..................................12 61 4.2.1 FinPunchPatternTC..............................................13 62 4.2.2 FinPunchHoleTypeTC, punchHoleSizeMaxDim, punchHoleSizeMinDim...14 63 5. THE ATTRIBUTE MECHANISM...........................................14 64 5.1 Conformance of Attribute Implementation..........................15 65 5.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes.15 66 5.3 Data Sub-types and Attribute Naming Conventions..................16 67 5.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes.....16 68 5.6 Index Value Attributes...........................................16 69 5.7 Attribute Specifications.........................................17 70 6. ENUMERATIONS......................................................22 71 7. IANA PRINTER FINISHING MIB SPECIFICATION..........................22 72 8. PRINTER FINISHING MIB SPECIFICATION...............................28 73 9. IANA CONSIDERATIONS...............................................45 74 10. INTELLECTUAL PROPERTY............................................45 75 11. INTERNATIONALIZATION CONSIDERATIONS..............................45 76 12. NORMATIVE REFERENCES.............................................46 77 13. INFORMATIVE REFERENCES...........................................46 78 14. SECURITY CONSIDERATIONS..........................................47 79 15. FULL COPYRIGHT STATEMENT.........................................48 80 16. AUTHORS..........................................................48 82 1. INTRODUCTION 84 This document describes an SNMP Management Information Base (MIB) to 85 provide for the management of in-line post-processing in a fashion 86 that is currently provided for printers, using the Printer MIB 87 [RFCnnnn]. The Printer Finishing MIB includes the following features: 89 Note to RFC Editor: Insert RFC number 'nnnn' when assigned to the 90 Printer MIB. See also the following paragraph. 92 - Provides the status of the finishing device. 93 - Queries and controls the features and configuration of the 94 finishing device. 95 - Enables and disables the finishing processes. 96 - Allows unsolicited status from the finishing device. 98 The Finisher MIB is defined as an extension of the Printer MIB 100 [RFCnnnn] and it is expected that the information defined in this 101 document will be incorporated into a future update of the Printer 102 MIB. 104 Note to RFC Editor: Insert RFC number 'nnnn' when assigned to the 105 Printer MIB. 107 1.1 Scope 109 This document provides a robust set of finishing devices, features, 110 and functions, based upon today's state of the art of in-line 111 finishing. Since finishing typically accompanies higher speed 112 network printers and copiers, in contrast to simple desktop devices, 113 no attempt is made to limit the scope to "bare minimum". On the 114 other hand, the Printer Finishing MIB does not duplicate the 115 production mail preparation, custom insertion, franking, and reprints 116 that are covered by the DMTF Large Mailing Operations standard [LMO]. 118 Information supplied by the Printer Finishing MIB may be utilized by 119 printer and finisher management applications engaged in monitoring 120 status and managing configuration, and also used by print and 121 finishing submission applications which are engaged in: 123 - print-job-level finishing processes that are applied to a 124 complete print job, 126 - document-level finishing processes that are applied individually 127 to each document in the print job, 129 - document-level finishing processes that are applied to a selected 130 document in the print job. 132 Note that not all combinations of finishing processes are 133 permitted. Compatible combinations of finishing processes are 134 implementation specific. The MIB allows invalid combinations to be 135 identified. 137 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 138 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 139 document are to be interpreted as described in [RFC2119]. 141 1.2 Rational 143 The Printer MIB [RFCnnnn] is now successfully deployed in a large 144 segment of the network printer market. SNMP and/or HTTP enabled 145 printers and software management applications are growing in numbers. 147 Note to RFC Editor: Insert RFC number 'nnnn' when assigned to the 148 Printer MIB. 150 There is an increase in the availability of network printers and 151 copiers that include in-line finishing processes. Thus a well 152 defined and ordered set of finishing objects is now necessary for 153 printer management. 155 The printer model defined in the Printer MIB includes finishing 156 processes and the MIB was designed to later incorporate finisher 157 objects or to be referenced by a future Finisher MIB. 159 1.3 The Internet-Standard Management Framework 161 For a detailed overview of the documents that describe the current 162 Internet-Standard Management Framework, please refer to section 7 of 163 RFC 3410 [RFC3410]. 165 Managed objects are accessed via a virtual information store, termed 166 the Management Information Base or MIB. MIB objects are generally 167 accessed through the Simple Network Management Protocol (SNMP). 168 Objects in the MIB are defined using the mechanisms defined in the 169 Structure of Management Information (SMI). This memo specifies a MIB 170 module that is compliant to the SMIv2, which is described in STD 58, 171 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 172 [RFC2580]. 174 1.4 Read-Write Objects 176 Some objects in the Finisher MIB reflect the existence or amount of a 177 given resource within the finisher. Some examples of such resources 178 are the size and number of sheets in an inserter tray or the 179 existence of certain finisher options. Some finishers have automatic 180 sensors for these resources. Most finishers lack sensors for every 181 property of every resource. The management application is allowed to 182 write into objects that hold descriptive or existence values for 183 finishers that cannot sense these values. The ability to change the 184 value of a read-write object may depend on the implementation of the 185 agent. Many objects in the MIB are given read-write access, but an 186 implementation might only permit a management application to change 187 the value if the finisher can not sense the value itself. Note that 188 even though some objects explicitly state the behavior of conditional 189 ability to change values, any read-write object may act this way. 191 Generally, an object is given read-write access in the Finisher MIB 192 specification if: 194 1. The object involves installation of a resource that some finishers 195 cannot themselves detect. Therefore, external means are needed to 196 inform the device of the installation. (Here external means include 197 using the operator console, or remote management application) and 199 2. The finisher will behave differently if the installation of the 200 resource is reported than if the installation were not reported; that 201 is, the object is not to be used as a place to put information not 202 used by the finisher, i.e., not a "sticky-note". Another way of 203 saying this is that the finisher believes that information given it 204 and acts as if the information were true. 206 3. The finisher may get hints that it may not know about the 207 existence or properties of certain resources. For example, a paper 208 tray may be removed and re-inserted. When this removal and insertion 209 happens, the finisher may either assume that a property, such as the 210 size of paper in the tray, has not changed or the finisher may change 211 the value of the associated object to "unknown", as might be done for 212 the amount of paper in the tray. As long as the finisher acts 213 according to the value in the object either strategy is acceptable. 215 4. It is an implementation-specific matter as to whether or not MIB 216 object values are persistent across power cycles or cold starts. 218 2. TERMINOLOGY 220 Where appropriate, the Printer Finishing MIB will conform to the 221 terminology, syntax, and semantics from the DMTF Large Mailing 222 Operations standard [LMO], the Internet Printing Protocol [RFC2911], 223 and/or the ISO Document Printing Application [DPA]. 225 2.1 General Terminology 227 Finisher Input: An input tray on the finisher and not otherwise 228 associated with the printer. An example of a finisher input is a 229 tray that holds finishing "inserts". 231 ^ Y 232 | 233 |<---- Reference Edge 234 | 235 | |<--- Finishing Process Axis 236 | | 237 --->| |<--- Finishing Process Offset 238 | | 239 Head +=========================+ (X2,Y4) 240 Locations # | # 241 +-----#----+ # 242 -----Y3--|-----#--O | <--+- Head # 243 ^ +-----#----+ | Mechanisms # 244 | # | | # 245 | # | | # 246 | # | | # 247 | # | | # 248 | +-----#----+ | # 249 | ---Y2--|-----#--O | <--+ # 250 | ^ +-----#----+ | # 251 | | # | | # 252 | | # | | # 253 | | # | | # 254 | | # | | # 255 | | +-----#----+ | # 256 | | -Y1--|-----#--O | <--+ # 257 | | ^ +-----#----+ bottom right # 258 | | | # | corner # X 259 --------------- +==+======================+ ----> 260 (0,0) (X1,0) 262 Figure 1 - Finishing Process Axis Parallel to Y Axis 263 ^ Y 264 | Head Locations 265 |<---------------->|---X2 266 |<---->|---X1 | 267 | | | 268 | +-|-+ +-|-+ 269 | | | | | | | (X3,Y2) 270 +======|===========|======+ 271 # | | | | | | # Finishing Process Axis 272 #----| O |-------| O |----#----- Y1 273 # +---+ +---+ # ^ 274 # ^ ^ # | 275 # | | # | 276 # +-----------+ # | 277 # | # | 278 # Head # | 279 # Mechanisms # | 280 # # | 281 # # Finishing Process Offset 282 # # | 283 # # | 284 # # | 285 # # | 286 # # | 287 # # | 288 # bottom right # | 289 # corner # v X 290 +=========================+ ------> 291 (0,0) Reference Edge 293 Figure 2 - Finishing Process Axis Parallel to X Axis 295 Finisher Output: The output of the finisher. Because processing is 296 in-line, the finisher outputs are a direct extension of the set of 297 printer outputs. 299 Media Orientation: All Finishing Processes are defined relative to a 300 portrait orientation of the medium, regardless of the orientation of 301 the printed image or the direction of feed. The 'X' and 'Y' axis, 302 therefore, will always reference the medium as shown in figures 1 303 and 2, with the 'X' axis always along the short edge of the medium. 304 All edges and corners are also defined with the medium orientation 305 as shown using the syntax top, bottom, left, and right. Thus the 306 bottom edge of the medium is at Y = 0, the left edge is at X = 0, 307 and the bottom right corner is at (X2,0) as shown in the figure 1 308 and at (X3,0) as shown in figure 2. 310 Finishing: Defined by DPA as an operation on a document following the 311 completion of the image process. Finishing processes defined within 312 this document are those applied to one or more instances of 313 rectangular paper sheet media. 315 Finishing Process: Defined by DPA as an operation applied by a 316 machine such as trimming a document, folding the sheets in a 317 document, and applying a binding to a document. 319 Finishing Specification: Defined by DPA as the specific sequence of 320 operations for a serial combination of finishing processes. The 321 exact sequential order of the processes, in many cases, is 322 critical to the obtaining the desired result. For example, a 323 folding operation followed by trimming could provide a very 324 different result than if the trimming was followed by the folding. 326 Finishing Process Parameters: This parameter set is used to create a 327 detailed definition of the finishing process. Generic Finishing 328 Process Parameters are applicable to any Finishing Specification. 330 - Head Mechanism: Defined by DPA as the physical mechanism that is 331 used to perform a finishing process. The head position may be 332 fixed or variable depending upon the capabilities of the device. 334 - Reference Edge: Defined by DPA as the edge of the document 335 relative to the axis to which the finishing process is applied. 336 The edge of the medium defined to be the Reference Edge may be 337 either the 'X' or the 'Y' axis, depending upon the finishing 338 process to be performed. 340 Note that the Reference Edge may change from one finishing process 341 to another for one of two reasons. First, a subsequent process may 342 require a different Reference Edge. Second, the actual dimensions 343 of the document may change, for example as a result of a folding or 344 a trimming operation. 346 - Jog Edge: Defined by DPA as one of the two edges that is 347 perpendicular to the Reference Edge. Specifying the Jog Edge 348 parameter indicates the edges of all sheets which correspond to 349 the Jog Edge are aligned. 351 - Finishing Process Axis: Defined by DPA as the axis which some 352 finishing processes are applied to or referenced from by the Head 353 Mechanism. Examples are the axis for a fold process or the axis 354 for a punch process. 356 - Head Locations: Defined by DPA as the position of the Heads on the 357 Finishing Process Axis. 359 - Finishing Process Offset: The offset from the Reference Edge to 360 the Finishing Process Axis at which the finishing process takes 361 place or is applied. 363 2.2 Process Specific Terminology 365 FOLDING: 367 Z Fold: A fold in which two folds are placed in the sheet in opposite 368 directions. The first fold is located at 25% of the sheet length, 369 and the second is located at 50% of the sheet length (i.e., the 370 center of the sheet). Z Folding is often used on 11x17 inch or A3 371 size sheets, when they are included in sets containing 8.5x11 inch 372 or A4 size sheets. 374 Half Fold: To fold a sheet in half so that one of the resulting 375 dimensions are exactly half the original sheet. Often used for 376 signatures or booklets. 378 Letter Fold: Folding a sheet roughly in thirds. Usually performed on 379 8.5x11 inch or A4 size sheets for insertion into an envelope. 381 Signature: The process by which images are placed on a large sheet of 382 paper in correct panel areas and in the proper orientation such that 383 when the sheet is folded it will produce a booklet with each page in 384 the proper order and orientation. 386 BINDING: 388 Adhesive Binding: A method of attaching sheets together to form a 389 book or booklet using glue or adhesive. Some adhesive binding 390 methods apply the glue to sheets individually, before merging them 391 together for form a book, but most methods involve the application 392 of adhesive to an entire book of sheets. 394 Comb Binding: A method of binding in which a series of small 395 rectangular holes is placed along the bind edge of the sheets. The 396 sheets are then held together using a tube shaped plastic binding 397 strip with comb like fingers that fit through the holes in the 398 sheets. 400 Spiral Binding: Sometimes referred to as wire binding, this binding 401 method is a mechanical bind in which the individual leaves are held 402 together by a wire or plastic spiral that is fed through small holes 403 in the paper binding edge. 405 Padding: Applying a non-penetrating adhesive to the edge of a stack 406 of sheets such that the sheets can be easily peeled off one at a 407 time. Frequently used for forms. 409 Velo Binding: A bind formed by punching holes into the edge of the 410 sheets, placing a two piece plastic strip (one side formed with 411 plastic pins that pass through the holes) along the edge and then 412 staking the two pieces together. 414 Perfect Binding: A method of binding in which all pages are cut and 415 roughed up at the back or binding edge and held together by an 416 adhesive. 418 Tape Binding: The act of placing tape over the bind edge of a set. 419 Sometimes contains adhesive to provide a functional bind to the set, 420 and sometimes done for decorative purposes on a set that has been 421 edge stapled. 423 SLITTING/CUTTING/TRIMMING: 425 Trim: To cut the edges of a sheet or set of sheets. 427 Face Trim: To cut the edges of a set of sheets on a booklet of sheets 428 that have been folded to eliminate the "creep" or edge shingling 429 that results from the folding process. 431 Gutter Trim: To cut a larger sheet into smaller sheets eliminating 432 the gutter between adjacent images. This operation requires a 433 minimum of two cuts for each gutter. 435 Tab Cutting: The act of cutting the edge of a sheet to form an index 436 tab, thereby allowing quick identification and access. The external 437 tabs are sequentially placed along the book edge for visibility and 438 ease of grasping. 440 Perforating: The act of cutting a series of very small, closely 441 spaced holes or slots into a sheet to allow for ease of separation 442 of a portion of the sheet. Sometimes also used to ease 443 bending/hinging of heavy weight papers. 445 Scoring: A means of applying small linear grooves or impressions 446 along a sheet to allow easy folding. Often used on heavy weight 447 sheets and book covers. 449 Slitting: The action of cutting apart a large sheet to form smaller 450 sheets. Usually done using a sharp circular roll system. 452 STITCHING/STAPLING: 454 Staple: The process of binding a set of sheets together using a 'U' 455 shaped piece of metal wire that is punched through the set. The ends 456 of the metal staple are then bent over, or 'clinched' to hold the 457 staple in place. Technically the term 'stapler' refers to devices 458 that use pre-cut metal staples, but the term is also commonly used 459 to refer to devices that use wire spools and then cut/form the 460 staple. (see the definition of Stitch) 462 Stitch: The process of binding a set of sheets together using a 'U' 463 shaped piece of metal wire that is punched through the set. The 464 wire used to form the staple is cut and formed into a 'U' shape in 465 the stitcher head, and the staple 'leg' length is often varied 466 depending on the number of sheets to be bound together. The ends of 467 the metal staple are bent over, or 'clinched' to hold the staple in 468 place. 470 Stitching can also refer to the process of sewing the edges of the 471 signatures of a book together. 473 Saddle Stitch: The process of stapling a set along its center line as 474 part of a booklet making process. Usually 2 or 3 staples are used. 476 Dual Stapling: The process of placing 2 staples along the bind edge 477 of a set. The staples are typically located at 25% and 75% of the 478 length of the bind edge. Although dual stapling is often performed 479 on the long edge of a set, legal documents are frequently dual 480 stapled along the top, or short edge of the set. 482 Triple Stapling: Same as above, but using 3 staples along the bind 483 edge, and usually applies to the long edge only. 485 WRAPPING: 487 Shrink Wrap: A wrap of thin plastic which when heated will shrink and 488 wrap tightly around the stack thus preparing it for shipment. 490 BANDING: 492 Band Wrap: Bundling a finished stack to prepare for shipment. Also 493 known as Strap Wrap. 495 ROTATING: 497 Sheet Rotator: A device that rotates each sheet as received from the 498 Media Path to the proper orientation for the finisher processing. 500 3. FINISHER SUBUNITS INTEGRATED INTO THE PRINTER MODEL 502 The Printer Finisher Device subunits receive media from one or more 503 Printer Media Path subunits and deliver the media to one or more 504 Printer Output subunits after the completion of the finishing 505 processes. The Printer Model, as described in the Printer MIB 506 [RFCnnnn], is modified adding the finisher subunit(s) and finisher 507 supplies between the media path and output subunits as follows: 509 Note to RFC Editor: Insert RFC number 'nnnn' when assigned. 511 +----------+ 512 +----------+ | 513 | Marker | | 514 | Supplies |-+ 515 +----------+ 516 \ 517 +-----+ \ +------+ +--------+ +------+ 518 | | \| | | | | | 519 +-----+ | +-----+ +------+ | +------+ +--------+ | +------+ | 520 |Input|-+ +------+| |Marker|-+ +------+| |Finisher|-+ |Output|-+ 521 | |===>| |+<==>| |<==>| |+==>| |===>| | 522 +-----+ +-+ +-+ +------+ +-+ +-+ +--------+ +------+ 523 \ | || | || \ 524 \ | || | || \ 525 \ | || | || +----------+ 526 +-------+ | |+--------------------| || | Finisher |-+ 527 | | | +---------------------+ || | Supplies | | 528 +-------+ | | Media Path |+ +----------+ | 529 | Media |-+ +---------------------------+ | | 530 |(opt.) | +----------+ 531 +-------+ 533 4. FINISHING SPECIFICATIONS 535 The Finisher MIB is able to provide most of the information that is 536 required to generate a Finishing Specification. This includes; 538 1. Finishing operations that can be performed on media that are 539 associated with a specific printer media path and output subunit. 541 2. Combinations of operations that cannot be performed. 543 3. The location of the operation on the medium, if applicable. 545 4. The physical characteristics of the result of the operation. 546 For example, the size and shape of a punched hole, or if a fold 547 operation creates a letter fold or a "Z" fold. 549 The Finisher MIB permits an agent to describe the order that 550 operations can be performed. 552 4.1 Multiple finDeviceTable Entries 554 Each finishing operation supported by the printer is represented by 555 one or more entries in the finDeviceTable. Each entry in this table 556 defines a "logical" finishing device, since the function of several 557 table entries may be performed by a single finisher mechanism. 558 Multiple entries may also exist in the table as a result of the 559 existence of multiple finisher mechanisms that perform the same type 560 of operation. 562 One example of possible multiple entries for a single finisher 563 device, is a hole punch operation that creates more than one hole. 564 This could be performed using a single die punch that moves to each 565 required position or a multi-die punch that simultaneously creates 566 all holes. In either case, each defined hole position may be defined 567 as a separate table entry. 569 In both cases, if the punch positions can be individually selected, 570 a table entry for each position would be necessary. 572 For the multi-die punch, each head mechanism may have a different 573 hole pattern or size. If these differences are to be properly 574 disclosed, a table entry for each head mechanism would be required. 576 4.2 Implicit Parameters 578 Finishing operations that are specified by an enum define a 579 standard operation and in many cases an implicit set of physical 580 characteristics is to be included when specifying the enum. If 581 explicit values for these characteristics are not provided in the 582 attributes table, the values defined in this section are to be 583 implied. 585 4.2.1 FinPunchPatternTC 587 enum pattern |Reference| Reference | Hole spacing 588 | Edge |Axis Offset| (see note 1) 589 -------------------+---------+-----------+--------------------------- 590 twoHoleUSTop(4) | topEdge | note 2 | 2.75 inches 591 threeHoleUS(5) | note 3 | note 2 | 4.25 inches 592 twoHoleDIN(6) | note 4 | note 5 | 80 mm 593 fourHoleDIN(7) | note 4 | note 5 | 80 mm 594 twentyTwoHoleUS(8) | note 3 | note 2 | .5 inches 595 nineteenHoleUS(9) | note 3 | note 9 | .5625 inches 596 twoHoleMetric(10) | note 6 | note 5 | 80 mm 597 swedish4Hole(11) | note 4 | note 5 | 21, 70, 21 mm 598 twoHoleUSSide(12) | note 3 | note 2 | 2.75 inches 599 fiveHoleUS(13) | note 3 | note 2 | 2, 2.25, 2.25, 2 in 600 sevenHoleUS(14) | note 3 | note 2 | 1, 1, 2.25, 2.25, 1, 1 in 601 mixed7H4S(15) | note 4 | note 5 | note 7 602 norweg6Hole(16) | note 4 | note 5 | note 8 603 metric26Hole(17) | note 6 | note 5 | 9.5 mm 604 metric30Hole(18) | note 4 | note 5 | 9.5 mm 606 Notes: 607 1. All hole to hole patterns are centered along the process edge. 608 2. Offset is 0.18 inches to 0.51 inches. 609 3. Reference edge is leftEdge(5) for letter and topEdge(3) 610 for ledger. 612 4. Reference edge is leftEdge(5) for A4 and topEdge(3) for A3. 613 5. Offset is 4.5 mm to 13 mm. 614 6. Reference edge is leftEdge(5) for B5 and topEdge(3) for B4. 615 7. 7 holes and 4 slots are punched in a H-S-H-H-S-H-S-H-H-S-H 616 pattern with 15, 25, 23, 20, 37, 37, 20, 23, 25, 15 mm spacing. 617 8. 4 holes and 2 slots are punched in a H-H-S-S-H-H pattern with 618 a 64, 18.5, 75, 18.5, 64 mm spacing. 619 9. Offset is .188 inches. 621 4.2.2 FinPunchHoleTypeTC, punchHoleSizeMaxDim, punchHoleSizeMinDim 623 enum pattern | Hole Description 624 -------------------+---------------------------------------- 625 twoHoleUSTop(4) | round(3), .2 - .32 inch diameter 626 threeHoleUS(5) | round(3), .2 - .32 inch diameter 627 twoHoleDIN(6) | round(3), 5 - 8 mm diameter 628 fourHoleDIN(7) | round(3), 5 - 8 mm diameter 629 twentyTwoHoleUS(8) | round(3), .2 - .32 inch diameter 630 nineteenHoleUS(9) | rectang(6), .313 inches X .125 inches 631 twoHoleMetric(10) | round(3), 5 - 8 mm diameter 632 swedish4Hole(11) | round(3), 5 - 8 mm diameter 633 twoHoleUSSide(12) | round(3), .2 - .32 inch diameter 634 fiveHoleUS(13) | round(3), .2 - .32 inch diameter 635 sevenHoleUS(14) | round(3), .2 - .32 inch diameter 636 mixed7H4S(15) | round(3), 5 - 8 mm diameter 637 | rectang(6), 12 mm X 6 mm 638 norweg6Hole(16) | round(3), 5 - 8 mm diameter 639 | rectang(6), 10 mm X 5.5 mm 640 metric26Hole(17) | round(3), 5 - 8 mm 641 metric30Hole(18) | round(3), 5 - 8 mm 643 Note: Hole size ranges are typical and are provided as a reference 644 only. Exact tolerances should be site defined. 646 5. THE ATTRIBUTE MECHANISM 648 Attributes provide a function similar to information objects, except 649 that attributes are identified by an enum, instead of an OID. Thus 650 new attributes may be registered without requiring a change to the 651 MIB. In addition, an implementation that does not have the 652 functionality represented by the attribute can omit the attribute 653 entirely, rather than having to return a distinguished value. The 654 agent is free to create an attribute in the Attribute Table as soon 655 as the agent is aware of the value of the attribute. 657 The agent materializes finishing subunit attributes in a four-indexed 658 finDeviceAttributeTable: 660 1. hrDeviceIndex - which device in the host 661 2. finDeviceIndex - which finisher subunit in the printer device 663 3. finDeviceAttributeTypeIndex - which attribute 665 4. finDeviceAttributeInstanceIndex - which attribute instance for 666 those attributes that can have multiple values per finishing 667 subunit. 669 5.1 Conformance of Attribute Implementation 671 An agent SHALL implement any attribute if (1) the device supports the 672 functionality represented by the attribute and (2) the information is 673 available to the agent. The agent MAY create the attribute row in 674 the finDeviceAttributeTable when the information is available or MAY 675 create the row earlier with the designated 'unknown' value 676 appropriate for that attribute. See next section. 678 If the device does not implement or does not provide access to the 679 information about an attribute, the agent SHOULD NOT create the 680 corresponding row in the finDeviceAttributeTable. 682 5.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes 684 Some attributes have a 'useful' Integer32 value, some have a 'useful' 685 OCTET STRING value, some MAY have either or both depending on 686 implementation, and some MUST have both. See the 687 finDeviceAttributeTypeTC textual convention for the specification of 688 each attribute. 690 NOTE: In some instances, objects with a MAX-ACCESS of read-write will 691 result in an SNMPv1 error or SNMPv2 exception during a write 692 operation. The administrative security policy may restrict a class 693 of users to read-only or, more importantly, the implementation may 694 implement a subset of read-write objects as read-only. This should 695 be expected to be the case for a device that can properly sense the 696 value of an object and does not want the value to be externally 697 modified. 699 In general, values for objects and attributes have been chosen so 700 that a management application will be able to determine whether a 701 'useful', 'unknown', or 'other' value is available. When a useful 702 value is not available for an object that agent SHALL return a zero- 703 length string for octet strings, the value 'unknown(2)' for enums, a 704 '0' value for an object that represents an index in another table, 705 and a value '-2' for counting integers. 707 Since each attribute is represented by a row consisting of both the 708 finDeviceAttributeValueAsInteger and finDeviceAttributeValueAsOctets 709 MANDATORY objects, SNMP requires that the agent SHALL always create 710 an attribute row with both objects specified. However, for most 711 attributes the agent SHALL return a "useful" value for one of the 712 objects and SHALL return the 'other' value for the other object. For 713 integer only attributes, the agent SHALL always return a zero-length 714 string value for the finDeviceAttributeValueAsOctets object. For 715 octet string only attributes, the agent SHALL always return a '-1' 716 value for the finDeviceAttributeValueAsInteger object. 718 5.3 Data Sub-types and Attribute Naming Conventions 720 Many attributes are sub-typed to give a more specific data type than 721 Integer32 or OCTET STRING. The data sub-type of each attribute is 722 indicated on the first line(s) of the description. Some attributes 723 have several different data sub-type representations. When an 724 attribute has both an Integer32 data sub-type and an OCTET STRING 725 data sub-type, the attribute can be represented in a single row in 726 the finDeviceAttributeTable. In this case, the data sub-type name is 727 not included as the last part of the name of the attribute. When the 728 data sub-types cannot be represented by a single row in the 729 finDeviceAttributeTable, each such representation is considered a 730 separate attribute and is assigned a separate name and enum value. 731 For these attributes, the name of the data sub-type is the last part 732 of the name of the attribute. 734 5.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 736 Most attributes shall have only one row per finishing subunit. 737 However, a few attributes can have multiple values per finishing 738 subunit, where each value is a separate row in the 739 finDeviceAttributeTable. Unless indicated with 'MULTI-ROW:' in the 740 finDeviceAttributeTypeTC description, an agent SHALL ensure that each 741 attribute occurs only once in the finDeviceAttributeTable for a 742 finishing subunit. Most of the 'MULTI-ROW' attributes do not allow 743 duplicate values, i.e., the agent SHALL ensure that each value occurs 744 only once for a finishing subunit. Only if the specification of the 745 'MULTI-ROW' attribute also says "There is no restriction on the same 746 xxx occurring in multiple rows" can the agent allow duplicate values 747 to occur for a single finishing subunit. 749 5.5 Linked MUTI-ROW Values 751 Some MULTI-ROW attributes are intended to go together. Thus a set 752 of value instances represent a single instance. For example, the 753 puncher attributes indicate the location, maximum size, minimum size 754 and shape of the various holes that the puncher can produce. So the 755 first set of values could represent one kind of hole, and the second 756 set another kind of hole, etc. 758 5.6 Index Value Attributes 760 A number of attributes are indexes in other tables. Such attribute 761 names end with the word 'Index'. If the agent has not (yet) assigned 762 an index value for a particular index attribute for a finishing 763 subunit, the agent shall either: (1) return the value 0 or (2) not 764 add this attribute to the finDeviceAttributeTable until the index 765 value is assigned. In the interests of brevity, the semantics for 0 766 is specified once here and is not repeated for each index attribute 767 specification and a DEFVAL of 0 is indicated. 769 5.7 Attribute Specifications 771 This section specifies the set of attributes that are enumerated 772 in finAttributeTypeTC. The data type tag definitions 'INTEGER:' 773 or 'OCTETS', indicate if the attribute can be represented using 774 the object finDeviceAttributeAsInteger or the object 775 finDeviceAttributeAsOctets, respectively. In some cases, a choice 776 between the two data types is possible and for a few attributes both 777 objects may be required at the same time to properly present the 778 value. 780 NOTE - The enum assignments are grouped logically with values 781 assigned in groups of 10, so that additional values may be 782 registered in the future and assigned a value that is part of 783 their logical grouping. 785 Values in the range 2**30 to 2**31-1 are reserved for private or 786 experimental usage. This range corresponds to the same range 787 reserved in IPP. Implementers are warned that use of such values 788 may conflict with other implementations. Implementers are encouraged 789 to request registration of enum values following the procedures in 790 Section 6.1. 792 The attribute types defined at the time of completion of this 793 specification are: 795 finAttributeTypeIndex Data type 796 --------------------- --------- 797 other(1), Integer32 798 AND/OR 799 OCTET STRING (SIZE(0..63)) 800 INTEGER: and/or OCTETS: An attribute that is not currently 801 approved and registered. 803 A. Generic finisher subunit attributes that apply to all finisher 804 subunit types. (3..) 806 deviceName(3), OCTET STRING (SIZE(0..63)) 807 OCTETS: The name assigned to this finisher device subunit. 809 deviceVendorName(4), OCTET STRING (SIZE(0..63)) 810 OCTETS: The name of the vendor of this finisher device 811 subunit. 813 deviceModel(5), OCTET STRING (SIZE(0..63)) 814 OCTETS: The model name of this finisher device subunit. 816 deviceVersion(6), OCTET STRING (SIZE(0..63)) 817 OCTETS: The version string for this finisher device 818 subunit. 820 deviceSerialNumber(7), OCTET STRING (SIZE(0..63)) 821 OCTETS: The serial number assigned to this finisher device 822 subunit. 824 maximumSheets(8), Integer32 (-2..32767) 825 INTEGER: Defines the maximum number of media sheets that a 826 finisher device is able to process. 828 finProcessOffsetUnits(9), PrtMediaUnitTC 829 INTEGER: An enumeration which defines the units of measure 830 for the attributes finAxisOffset, finHeadLocation, 831 punchHoleSizeLongDim, and punchHoleSizeShortDim. 833 finReferenceEdge(10), FinEdgeTC 834 INTEGER: An enumeration which defines which edge of the 835 form is the reference for this finishing process. The 836 Finishing Process Axis will be parallel to this axis. 838 finAxisOffset(11), Integer32 (-2..2147483647) 839 INTEGER: Defines the offset of the Finishing Process 840 Axis from the parallel Reference Edge. For a value of 841 finEdgeTC equal to TopEdge or RightEdge, the value 842 given is to interpreted as a negative offset from the 843 reference edge. The units of measure are defined by the 844 attribute finProcessOffsetUnits. 846 finJogEdge(12), FinEdgeTC 847 INTEGER: An enumeration which defines a second edge of the 848 document to which the media is aligned. The jog edge must 849 be perpendicular to the edge defined by finReferenceEdge. 851 finHeadLocation(13), Integer32 (-2..2147483647) 852 INTEGER: MULTI-ROW: Defines the position of the Head 853 Mechanism relative to the axis, 'X' or 'Y', that is 854 perpendicular to the Process Axis. The units of measure 855 are defined by the attribute finProcessOffsetUnits. 857 finOperationRestrictions(14), Integer32 (0..65535) 858 INTEGER: MULTI-ROW: Defines the finDeviceIndex of a 859 finishing process which cannot be combined with the 860 process defined by the finDeviceIndex for this 861 finDeviceAttributeTable instance. When this condition 862 occurs this attribute SHALL be presented in the 863 attribute tables for both finishing processes that cannot 864 be combined. 866 finNumberOfPositions(15), Integer32 (0..65535) 867 INTEGER: Defines the total number of head positions for 868 this finishing process. Each position many be realized by 869 a unique head mechanism or a single head mechanism may be 870 automatically moved to each position. 872 namedConfiguration(16), OCTET STRING (SIZE(0..63)) 873 OCTETS: Contains an administratively define name to define 874 the finishing specification configured for this device. 876 finMediaTypeRestriction(17), OCTET STRING (SIZE(0..63)) 877 OCTETS: MULTI-ROW: Defines the media type which cannot be 878 combined with the process defined by the finDeviceIndex 879 for this finDeviceAttributeTable instance. Values are the 880 same as defined for finSupplyMediaInputMediaName. 882 finPrinterInputTraySupported(18), Integer32 (0..65535) 883 INTEGER: MULTI-ROW: Defines the value of prtInputIndex 884 corresponding to the printer input tray that can be used 885 with the process defined by the finDeviceIndex for this 886 finDeviceAttributeTable instance. If this attribute is 887 not present, this process can be used with any input tray 888 in the printer. For example, this attribute can indicate 889 the current stapling capabilities for a stapler device 890 for the input trays that depend upon the size and feed 891 orientation. So if there were two letter trays, one with 892 A size and the other with B size, a two position stapler 893 might specify in one row: upper-left and upper-right for 894 the input tray with A size, but only upper-left for the 895 one with B size. 897 finPreviousFinishingOperation(19), Integer32 (0..65535) 898 INTEGER: Defines the finDeviceIndex of the previous 899 finishing process for implementations in which the 900 finishing processes are performed in a prescribed order. 901 Each finishing process in the fixed sequence is either 902 performed or not performed according to the finishing 903 instructions submitted with the job. A value of 0 904 indicates that this finishing process is the first in a 905 sequence. Finishing processes which are not part of a 906 fixed sequence SHALL NOT have this attribute. 908 finNextFinishingOperation(20), Integer32 (0..65535) 909 INTEGER: Defines the finDeviceIndex of the next finishing 910 process for implementations in which the finishing 911 processes are performed in a prescribed order. Each 912 finishing process in the fixed sequence is either 913 performed or not performed according to the finishing 914 instructions submitted with the job. A value of 0 915 indicates that this finishing process is the last in a 916 sequence. Finishing processes which are not part of a 917 fixed sequence SHALL NOT have this attribute. 919 B. Stitcher type-specific attributes (30..) 921 stitchingType(30), FinStitchingTypeTC 922 INTEGER: MULTI-ROW: Provides additional information 923 regarding the stitching operation. 925 stitchingDirection(31), FinStitchingDirTypeTC 926 INTEGER: Defines the orientation of the stitching 927 process. 929 stitchingAngle(32), FinStitchingAngleTypeTC 930 INTEGER: Defines enumerations that describe the angular 931 orientation of the stitching process relative to the 'X' 932 axis. 934 C. Folder type-specific attributes (40..) 936 foldingType(40), FinFoldingTypeTC 937 INTEGER: Provides additional information regarding the 938 folding process. 940 D. Binder type-specific attributes (50..) 942 bindingType(50), FinBindingTypeTC 943 INTEGER: Provides additional information regarding the 944 binding process. 946 E. Trimmer type-specific attributes (60..) 948 F. Die cutter type-specific attributes (70..) 950 G. Puncher type-specific attributes (80..) 952 punchHoleType(80), FinPunchHoleTypeTC 953 INTEGER: Provides information regarding the shape of the 954 punched hole. 956 punchHoleSizeLongDim(81), Integer32 (-2..2147483647) 957 INTEGER: Defines the size of the punched hole in the 958 longest dimension. This dimension is typically measured 959 parallel to either the long edge or the short edge of the 960 media and the longest dimension will always be measured 90 961 degrees from the shortest dimension. For a symmetrical 962 hole, such as a round or square hole, the shortest and 963 longest dimensions will be identical. The units of measure 964 are defined by the attribute finProcessOffsetUnits. 966 punchHoleSizeShortDim(82), Integer32 (-2..2147483647) 967 INTEGER: Defines the size of the punched hole in the 968 shortest dimension. This dimension is typically measured 969 parallel to either the long edge or the short edge of the 970 media and the shortest dimension will always be measured 971 90 degrees from the longest dimension. For a symmetrical 972 hole, such as a round or square hole, the shortest and 973 longest dimensions will be identical. The units of measure 974 are defined by the attribute finProcessOffsetUnits. 976 punchPattern(83), FinPunchPatternTC 977 INTEGER: Defines the hole pattern produced by the punch 978 process. 980 H. Perforator type-specific attributes (90..) 982 I. Slitter type-specific attributes (100..) 984 slittingType(100), FinSlittingTypeTC 985 INTEGER: Provides additional information regarding the 986 slitting process. 988 J. Separation cutter type-specific attributes (110..) 990 K. Imprinter type-specific attributes (120..) 992 L. Wrapper type-specific attributes (130..) 994 wrappingType(130), FinWrappingTypeTC 995 INTEGER: Provides additional information regarding the 996 wrapping process. 998 M. Bander type-specific attributes (140..) 1000 N. Make Envelopes type-specific attributes (150..) 1002 O. Stacker type-specific attributes (160..) 1004 stackOutputType(160) FinStackOutputTypeTC 1005 INTEGER: Defines the job-to-job orientation produced by 1006 the stacker. 1008 stackOffset(161) Integer32 (-2..2147483647) 1009 INTEGER: Defines the copy-to-copy output stack offset as 1010 a positive offset distance. The units of measure are 1011 defined by finProcessOffsetUnits. 1013 stackRotation(162) Integer32 (-2..180) 1014 INTEGER: Defines the copy-to-copy output stack rotation 1015 measured in degrees. The value is the positive 1016 copy-to-copy rotation." 1018 6. ENUMERATIONS 1020 Enumerations (enums) are sets of symbolic values defined for use with 1021 one or more objects. Commonly used enumeration sets are assigned a 1022 symbolic data type name (textual convention), rather than being 1023 specified in the SYNTAX clause of each individual object definition. 1025 Textual conventions defined in the Finisher MIB or the companion IANA 1026 Finisher MIB are extensible by RFC publication or Designated Expert 1027 Review (see 'IANA Considerations' section of this Finisher MIB and 1028 the DESCRIPTION clause in MODULE-IDENTITY of IANA Finisher MIB). All 1029 of these textual conventions are: 1031 a) used more than once in the Finisher MIB itself; or 1033 b) imported and used in any other, including vendor private, MIB 1034 modules. 1036 The Finisher MIB has also defined the following special values for 1037 use with objects of the syntax "Integer32" to define conditions that 1038 are outside of the normal numeric range: other(-1), unknown(-2), and 1039 partial(-3). The 'partial' value means that there is some supply 1040 remaining (but the amount is indeterminate) or there is some capacity 1041 remaining (but the amount is indeterminate). The Integer32 range 1042 field indicates in which objects these special values are valid. 1044 6.1 Registering Additional Enumerated Values 1046 The Finisher MIB and the companion IANA Finisher MIB each defines one 1047 category of textual convention, according to the process employed 1048 to control the addition of new enumerations: 1050 Type 1 - All of the legal values are defined in the Finisher MIB. 1051 Additional enumerated values require the publication of a new 1052 Finisher MIB. 1054 Type 2 - All of the legal values are registered in the IANA 1055 Finisher MIB. Additional enumerated values require a Designated 1056 Expert Review defined in "Guidelines for Writing an IANA 1057 Considerations Section in RFCs" [RFC2434]. The Designated Expert 1058 will be selected by the IETF Area Director(s) of the Applications 1059 Area. 1061 7. IANA PRINTER FINISHING MIB SPECIFICATION 1063 IANA-FINISHER-MIB DEFINITIONS ::= BEGIN 1065 IMPORTS 1066 MODULE-IDENTITY, 1067 mib-2 1068 FROM SNMPv2-SMI 1069 TEXTUAL-CONVENTION 1070 FROM SNMPv2-TC; 1072 ianafinisherMIB MODULE-IDENTITY 1073 LAST-UPDATED "200302100000Z" -- February 10, 2003 1074 ORGANIZATION "IANA" 1075 CONTACT-INFO "Internet Assigned Numbers Authority 1077 Postal: ICANN 1078 4676 Admiralty Way, Suite 330 1079 Marina del Rey, CA 90292 1081 Tel: +1 310 823 9358 1082 E-Mail: iana@iana.org" 1084 DESCRIPTION "This MIB module defines a set of finishing-related 1085 textual conventions for use in Finisher MIB (RFC xxxx) 1086 and other MIBs which need to specify finishing 1087 mechanism details. 1089 Any additions or changes to the contents of this MIB 1090 module require either publication of an RFC, or 1091 Designated Expert Review as defined in RFC 2434, 1092 Guidelines for Writing an IANA Considerations Section 1093 in RFCs. The Designated Expert will be selected by 1094 the IESG Area Director(s) of the Applications Area. 1096 Copyright (C) The Internet Society (2003). This 1097 version of this MIB module is part of RFC xxxx; 1098 see the RFC itself for full legal notices." 1099 -- RFC Editor assigns above RFC xxxx. 1101 REVISION "200302100000Z" -- February 10, 2003 1102 DESCRIPTION "Original version, published in coordination 1103 with Finisher MIB (RFC xxxx)." 1104 -- RFC Editor assigns above RFC xxxx. 1106 ::= { mib-2 nnn } -- nnn to be assigned by IANA 1108 -- Textual conventions for this MIB module 1110 FinDeviceTypeTC ::= TEXTUAL-CONVENTION 1111 STATUS current 1112 DESCRIPTION 1113 "The defined finishing device subunit process 1114 enumerations." 1115 SYNTAX INTEGER { 1116 other(1), 1117 unknown(2), 1118 stitcher(3), 1119 folder(4), 1120 binder(5), 1121 trimmer(6), 1122 dieCutter(7), 1123 puncher(8), 1124 perforater(9), 1125 slitter(10), 1126 separationCutter(11), 1127 imprinter(12), 1128 wrapper(13), 1129 bander(14), 1130 makeEnvelope(15), 1131 stacker(16), 1132 sheetRotator(17), 1133 inserter(18) 1134 } 1136 FinAttributeTypeTC ::= TEXTUAL-CONVENTION 1137 STATUS current 1138 DESCRIPTION 1139 "This textual convention defines the set of enums for use in 1140 the finDeviceAttributeTable. See section 5.7 for the complete 1141 specification of each attribute." 1142 SYNTAX INTEGER { 1143 other(1), 1144 deviceName(3), 1145 deviceVendorName(4), 1146 deviceModel(5), 1147 deviceVersion(6), 1148 deviceSerialNumber(7), 1149 maximumSheets(8), 1150 finProcessOffsetUnits(9), 1151 finReferenceEdge(10), 1152 finAxisOffset(11), 1153 finJogEdge(12), 1154 finHeadLocation(13), 1155 finOperationRestrictions(14), 1156 finNumberOfPositions(15), 1157 namedConfiguration(16), 1158 finMediaTypeRestriction(17), 1159 finPrinterInputTraySupported(18), 1160 finPreviousFinishingOperation(19), 1161 finNextFinishingOperation(20), 1162 stitchingType(30), 1163 stitchingDirection(31), 1164 foldingType(40), 1165 bindingType(50), 1166 punchHoleType(80), 1167 punchHoleSizeLongDim(81), 1168 punchHoleSizeShortDim(82), 1169 punchPattern(83), 1170 slittingType(100), 1171 wrappingType(130), 1172 stackOutputType(160), 1173 stackOffset(161), 1174 stackRotation(162) 1175 } 1177 FinEdgeTC ::= TEXTUAL-CONVENTION 1178 STATUS current 1179 DESCRIPTION 1180 "Specifies an edge for a Finishing Process." 1181 SYNTAX INTEGER { 1182 topEdge(3), 1183 bottomEdge(4), 1184 leftEdge(5), 1185 rightEdge(6) 1186 } 1188 FinStitchingTypeTC ::= TEXTUAL-CONVENTION 1189 STATUS current 1190 DESCRIPTION 1191 "The defined stitching type enumerations. For the edgeStitch and 1192 stapleDual enums, the finReferenceEdge attribute is recommended 1193 to define the edge to which the operation applies." 1194 SYNTAX INTEGER { 1195 other(1), -- More information in other attributes 1196 unknown(2), 1197 stapleTopLeft(4), 1198 stapleBottomLeft(5), 1199 stapleTopRight(6), 1200 stapleBottomRight(7), 1201 saddleStitch(8), 1202 edgeStitch(9), 1203 stapleDual(10) 1204 } 1206 FinStitchingDirTypeTC ::= TEXTUAL-CONVENTION 1207 STATUS current 1208 DESCRIPTION 1209 "Defines the direction, relative to the top sheet in the output 1210 subunit, that the stitching operation was performed. For a 1211 topDown(3) process, the staple will be clinched on the bottom 1212 of the stack. This parameter can be used to determine what 1213 order the pages of a booklet are to be printed such that the 1214 staple clinch will be on the inside of the resulting booklet." 1215 SYNTAX INTEGER { 1216 unknown(2), 1217 topDown(3), 1218 bottomUp(4) 1219 } 1221 FinStitchingAngleTypeTC ::= TEXTUAL-CONVENTION 1222 STATUS current 1223 DESCRIPTION 1224 "This enumeration provides a description of the angular 1225 orientation of each stitch in a single or multiple stitching 1226 operation, relative to the 'X' axis. As with all finishing 1227 operations, the 'X' axis is always relative to the portrait 1228 orientation of the document regardless of the orientation 1229 of the printed image. This enum is primarily applicable to 1230 corner stitching operations." 1231 SYNTAX INTEGER { 1232 unknown(2), 1233 horizontal(3), 1234 vertical(4), 1235 slanted(5) 1236 } 1238 FinFoldingTypeTC ::= TEXTUAL-CONVENTION 1239 STATUS current 1240 DESCRIPTION 1241 "The defined folding device process enumerations." 1242 SYNTAX INTEGER { 1243 other(1), -- More information in other attributes 1244 unknown(2), 1245 zFold(3), 1246 halfFold(4), 1247 letterFold(5) 1248 } 1250 FinBindingTypeTC ::= TEXTUAL-CONVENTION 1251 STATUS current 1252 DESCRIPTION 1253 "The defined binding type enumerations." 1254 SYNTAX INTEGER { 1255 other(1), -- More information in other attributes 1256 unknown(2), 1257 tape(4), 1258 plastic(5), 1259 velo(6), 1260 perfect(7), 1261 spiral(8), 1262 adhesive(9), 1263 comb(10), 1264 padding(11) 1265 } 1267 FinPunchHoleTypeTC ::= TEXTUAL-CONVENTION 1268 STATUS current 1269 DESCRIPTION 1270 "The defined hole type punch process enumerations." 1272 SYNTAX INTEGER { 1273 other(1), -- More information in other attributes 1274 unknown(2), 1275 round(3), 1276 oblong(4), 1277 square(5), 1278 rectangular(6), 1279 star(7) 1280 } 1282 FinPunchPatternTC ::= TEXTUAL-CONVENTION 1283 STATUS current 1284 DESCRIPTION 1285 "The defined hole pattern punch process enumerations." 1286 SYNTAX INTEGER { 1287 other(1), --Pattern to be defined in other attributes 1288 unknown(2), 1289 twoHoleUSTop(4), --Letter/legal, 8.5 inch edge 1290 threeHoleUS(5), --Letter/ledger, 11 inch edge 1291 twoHoleDIN(6), --A4/A3, 297 mm edge 1292 fourHoleDIN(7), --A4/A3, 297 mm edge 1293 twentyTwoHoleUS(8), --Letter/ledger, 11 inch edge 1294 nineteenHoleUS(9), --Letter/ledger, 11 inch edge 1295 twoHoleMetric(10), --B5/B4, 257 mm edge 1296 swedish4Hole(11), --A4/A3, 297 mm edge 1297 twoHoleUSSide(12), --Letter/ledger, 11 inch edge 1298 fiveHoleUS(13), --Letter/ledger, 11 inch edge 1299 sevenHoleUS(14), --Letter/ledger, 11 inch edge 1300 mixed7H4S(15), --A4/A3, 297 mm edge 1301 norweg6Hole(16), --A4/A3, 297 mm edge 1302 metric26Hole(17), --B5/B4, 257 mm edge 1303 metric30Hole(18) --A4/A3, 297 mm edge 1304 } 1306 FinSlittingTypeTC ::= TEXTUAL-CONVENTION 1307 STATUS current 1308 DESCRIPTION 1309 "The defined slitting type enumerations." 1310 SYNTAX INTEGER { 1311 other(1), -- More information in other attributes 1312 unknown(2), 1313 slitAndSeparate(4), 1314 slitAndMerge(5) 1315 } 1317 FinWrappingTypeTC ::= TEXTUAL-CONVENTION 1318 STATUS current 1319 DESCRIPTION 1320 "The defined wrapping device process enumerations." 1321 SYNTAX INTEGER { 1322 other(1), -- More information in other attributes 1323 unknown(2), 1324 shrinkWrap(4), 1325 paperWrap(5) 1326 } 1328 FinStackOutputTypeTC ::= TEXTUAL-CONVENTION 1329 STATUS current 1330 DESCRIPTION 1331 "The defined stack output type enumerations." 1332 SYNTAX INTEGER { 1333 other(1), -- More information in other attributes 1334 unknown(2), 1335 straight(4), -- No offset, one on top of another 1336 offset(5), 1337 crissCross(6) -- Rotated 1338 } 1339 END 1341 8. PRINTER FINISHING MIB SPECIFICATION 1343 Finisher-MIB DEFINITIONS ::= BEGIN 1345 IMPORTS 1346 MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2 FROM SNMPv2-SMI 1347 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 1348 hrDeviceIndex FROM HOST-RESOURCES-MIB 1349 PrtInputTypeTC, PrtMarkerSuppliesTypeTC FROM IANA-PRINTER-MIB 1350 printmib, PrtSubUnitStatusTC, PrtLocalizedDescriptionStringTC, 1351 PrtMarkerSuppliesSupplyUnitTC, PrtMediaUnitTC, 1352 PrtCapacityUnitTC, PrtMarkerSuppliesClassTC, 1353 PresentOnOff, prtMIBConformance FROM Printer-MIB 1354 FinDeviceTypeTC, FinAttributeTypeTC FROM IANA-FINISHER-MIB; 1356 finisherMIB MODULE-IDENTITY 1357 LAST-UPDATED "200302100000Z" 1358 ORGANIZATION "PWG IEEE/ISTO Printer Working Group" 1359 CONTACT-INFO 1361 "Harry Lewis 1362 IBM 1363 Phone (303) 924-5337 1364 Email: harryl@us.ibm.com 1366 Send comments to the printmib WG using the Finisher MIB 1367 Project (FIN) Mailing List: fin@pwg.org 1369 For further information, access the PWG web page under 'Finisher 1370 MIB': http://www.pwg.org/ 1372 Implementers of this specification are encouraged to join the 1373 fin mailing list in order to participate in discussions on any 1374 clarifications needed and registration proposals being reviewed 1375 in order to achieve consensus." 1376 DESCRIPTION 1377 "The MIB module for management of printer finisher units. 1378 The Finisher MIB is an extension of the Printer MIB. 1379 Copyright (C) The Internet Society (2003). This version of 1380 this MIB module is part of RFC xxxx; see the RFC itself for 1381 full legal notices." 1382 -- RFC Editor assigns above RFC xxxx. 1383 REVISION "200302100000Z" 1384 DESCRIPTION 1385 "The original version of this MIB." 1386 ::= { mib-2 nnn } -- nnn to be assigned by IANA 1388 -- Finisher Device Group (Mandatory) 1389 -- 1390 -- A printer may support zero or more finishing subunits. A 1391 -- finishing device subunit may be associated with one or more 1392 -- output subunits and one or more media path subunits. 1394 finDevice OBJECT IDENTIFIER ::= { printmib 30 } 1396 finDeviceTable OBJECT-TYPE 1397 SYNTAX SEQUENCE OF FinDeviceEntry 1398 MAX-ACCESS not-accessible 1399 STATUS current 1400 DESCRIPTION 1401 "This table defines the finishing device subunits, 1402 including information regarding possible configuration 1403 options and the status for each finisher device subunit." 1404 ::= { finDevice 1 } 1406 finDeviceEntry OBJECT-TYPE 1407 SYNTAX FinDeviceEntry 1408 MAX-ACCESS not-accessible 1409 STATUS current 1410 DESCRIPTION 1411 "There is an entry in the finishing device table for each 1412 possible finisher process. Each individual finisher process is 1413 implemented by a finishing device represented in this table." 1414 INDEX { hrDeviceIndex, finDeviceIndex } 1415 ::= { finDeviceTable 1 } 1417 FinDeviceEntry ::= SEQUENCE { 1418 finDeviceIndex Integer32, 1419 finDeviceType FinDeviceTypeTC, 1420 finDevicePresentOnOff PresentOnOff, 1421 finDeviceCapacityUnit PrtCapacityUnitTC, 1422 finDeviceMaxCapacity Integer32, 1423 finDeviceCurrentCapacity Integer32, 1424 finDeviceAssociatedMediaPaths OCTET STRING, 1425 finDeviceAssociatedOutputs OCTET STRING, 1426 finDeviceStatus PrtSubUnitStatusTC, 1427 finDeviceDescription PrtLocalizedDescriptionStringTC 1428 } 1430 finDeviceIndex OBJECT-TYPE 1431 SYNTAX Integer32 (1..65535) 1432 MAX-ACCESS not-accessible 1433 STATUS current 1434 DESCRIPTION 1435 "A unique value used to identify a finisher process. 1436 Although these values may change due to a major 1437 reconfiguration of the printer system (e.g. the addition 1438 of new finishing processes), the values are normally 1439 expected to remain stable across successive power cycles." 1440 ::= { finDeviceEntry 1 } 1442 finDeviceType OBJECT-TYPE 1443 SYNTAX FinDeviceTypeTC 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "Defines the type of finishing process associated with this 1448 table row entry." 1449 ::= { finDeviceEntry 2 } 1451 finDevicePresentOnOff OBJECT-TYPE 1452 SYNTAX PresentOnOff 1453 MAX-ACCESS read-write 1454 STATUS current 1455 DESCRIPTION 1456 "Indicates if this finishing device subunit is available 1457 and whether the device subunit is enabled." 1458 DEFVAL { notPresent } 1459 ::= { finDeviceEntry 3 } 1461 finDeviceCapacityUnit OBJECT-TYPE 1462 SYNTAX PrtCapacityUnitTC 1463 MAX-ACCESS read-only 1464 STATUS current 1465 DESCRIPTION 1466 "The unit of measure for specifying the capacity of this 1467 finisher device subunit." 1468 ::= { finDeviceEntry 4 } 1470 finDeviceMaxCapacity OBJECT-TYPE 1471 SYNTAX Integer32 (-2..2147483647) 1472 MAX-ACCESS read-write 1473 STATUS current 1474 DESCRIPTION 1475 "The maximum capacity of this finisher device subunit in 1476 finDeviceCapacityUnits. If the device can reliably sense 1477 this value, the value is sensed by the finisher device 1478 and is read-only: otherwise the value may be written by a 1479 management or control console application. The value (-1) 1480 means other and specifically indicates that the device 1481 places no restrictions on this parameter. The value (-2) 1482 means unknown." 1483 DEFVAL { -2 } -- unknown 1484 ::= { finDeviceEntry 5 } 1486 finDeviceCurrentCapacity OBJECT-TYPE 1487 SYNTAX Integer32 (-2..2147483647) 1488 MAX-ACCESS read-write 1489 STATUS current 1490 DESCRIPTION 1491 "The current capacity of this finisher device subunit in 1492 finDeviceCapacityUnits. If the device can reliably sense 1493 this value, the value is sensed by the finisher and is 1494 read-only: otherwise the value may be written by a 1495 management or control console application. The value (-1) 1496 means other and specifically indicates that the device 1497 places no restrictions on this parameter. The value (-2) 1498 means unknown." 1499 DEFVAL { -2 } -- unknown 1500 ::= { finDeviceEntry 6 } 1502 finDeviceAssociatedMediaPaths OBJECT-TYPE 1503 SYNTAX OCTET STRING (SIZE(1..63)) 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "Indicates the media paths which can supply media for this 1508 finisher device. The value of this object is a bit map in an 1509 octet string with each position representing the value of a 1510 prtMediaPathIndex. For a media path that can be a source 1511 for this finisher device subunit, the bit position equal 1512 to one less than the value of prtMediaPathIndex will be set. 1513 The bits are numbered starting with the most significant bit of 1514 the first byte being bit 0, the least significant bit of the 1515 first byte being bit 7, the most significant of the second byte 1516 being bit 8, and so on." 1517 ::= { finDeviceEntry 7 } 1519 finDeviceAssociatedOutputs OBJECT-TYPE 1520 SYNTAX OCTET STRING (SIZE(1..63)) 1521 MAX-ACCESS read-only 1522 STATUS current 1523 DESCRIPTION 1524 "Indicates the printer output subunits this finisher device 1525 subunit services. The value of this object is a bit map in an 1526 octet string with each position representing the value of a 1527 prtOutputIndex. For an output subunit that is serviced 1528 by this finisher device subunit, the bit position equal to 1529 to one less than the value of prtOutputIndex will be set. 1530 The bits are numbered starting with the most significant bit of 1531 the first byte being bit 0, the least significant bit of the 1532 first byte being bit 7, the most significant of the second byte 1533 being bit 8, and so on." 1534 ::= { finDeviceEntry 8 } 1536 finDeviceStatus OBJECT-TYPE 1537 SYNTAX PrtSubUnitStatusTC 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "Indicates the current status of this finisher device 1542 subunit." 1543 DEFVAL { 5 } -- unknown 1544 ::= { finDeviceEntry 9 } 1546 finDeviceDescription OBJECT-TYPE 1547 SYNTAX PrtLocalizedDescriptionStringTC 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "A free form text description of this device subunit in the 1552 localization specified by prtGeneralCurrentLocalization." 1553 ::= { finDeviceEntry 10 } 1555 -- Finisher Supply Group (Mandatory) 1556 -- 1557 -- A finisher device, but not all finisher devices, may have one or more 1558 -- supplies associated with it. For example a finisher may use both 1559 -- binding tape and stitching wire supplies. A finisher may also have 1560 -- more than one source for a given type of supply e.g. multiple supply 1561 -- sources of ink for imprinters. 1563 finSupply OBJECT IDENTIFIER ::= { printmib 31 } 1565 finSupplyTable OBJECT-TYPE 1566 SYNTAX SEQUENCE OF FinSupplyEntry 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "Each unique source of supply is an entry in the finisher 1571 supply table. Each supply entry has its own 1572 characteristics associated with it such as colorant and 1573 current supply level." 1574 ::= { finSupply 1 } 1576 finSupplyEntry OBJECT-TYPE 1577 SYNTAX FinSupplyEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "A list of finisher devices, with their associated 1582 supplies and supplies characteristics." 1583 INDEX { hrDeviceIndex, finSupplyIndex } 1584 ::= { finSupplyTable 1 } 1586 FinSupplyEntry ::= SEQUENCE { 1587 finSupplyIndex Integer32, 1588 finSupplyDeviceIndex Integer32, 1589 finSupplyClass PrtMarkerSuppliesClassTC, 1590 finSupplyType PrtMarkerSuppliesTypeTC, 1591 finSupplyDescription PrtLocalizedDescriptionStringTC, 1592 finSupplyUnit PrtMarkerSuppliesSupplyUnitTC, 1593 finSupplyMaxCapacity Integer32, 1594 finSupplyCurrentLevel Integer32, 1595 finSupplyColorName OCTET STRING 1596 } 1598 finSupplyIndex OBJECT-TYPE 1599 SYNTAX Integer32 (1..65535) 1600 MAX-ACCESS not-accessible 1601 STATUS current 1602 DESCRIPTION 1603 "A unique value used by a finisher to identify this supply 1604 container/receptacle. Although these values may change 1605 due to a major reconfiguration of the finisher (e.g. the 1606 addition of new supply sources to the finisher), values 1607 are normally expected to remain stable across successive 1608 power cycles." 1609 ::= { finSupplyEntry 1 } 1611 finSupplyDeviceIndex OBJECT-TYPE 1612 SYNTAX Integer32 (0..65535) 1613 MAX-ACCESS read-only 1614 STATUS current 1615 DESCRIPTION 1616 "The value of finDeviceIndex corresponding to the finishing 1617 device subunit with which this finisher supply is associated. 1618 The value zero indicates the associated finishing device is 1619 Unknown." 1620 ::= { finSupplyEntry 2 } 1622 finSupplyClass OBJECT-TYPE 1623 SYNTAX PrtMarkerSuppliesClassTC 1624 MAX-ACCESS read-only 1625 STATUS current 1626 DESCRIPTION 1627 "This value indicates whether this supply entity 1628 represents a supply that is consumed or a container that 1629 is filled." 1630 ::= { finSupplyEntry 3 } 1632 finSupplyType OBJECT-TYPE 1633 SYNTAX PrtMarkerSuppliesTypeTC 1634 MAX-ACCESS read-only 1635 STATUS current 1636 DESCRIPTION 1637 "The type of this supply." 1638 ::= { finSupplyEntry 4 } 1640 finSupplyDescription OBJECT-TYPE 1641 SYNTAX PrtLocalizedDescriptionStringTC 1642 MAX-ACCESS read-only 1643 STATUS current 1644 DESCRIPTION 1645 "The description of this supply/receptacle in text useful 1646 for operators and management applications and in the 1647 localization specified by prtGeneralCurrentLocalization." 1648 ::= { finSupplyEntry 5 } 1650 finSupplyUnit OBJECT-TYPE 1651 SYNTAX PrtMarkerSuppliesSupplyUnitTC 1652 MAX-ACCESS read-only 1653 STATUS current 1654 DESCRIPTION 1655 "Unit of measure of this finisher supply container or 1656 receptacle." 1657 ::= { finSupplyEntry 6 } 1659 finSupplyMaxCapacity OBJECT-TYPE 1660 SYNTAX Integer32 (-2..2147483647) 1661 MAX-ACCESS read-write 1662 STATUS current 1663 DESCRIPTION 1664 "The maximum capacity of this supply container/receptacle 1665 expressed in Supply Units. If this supply container/ 1666 receptacle can reliably sense this value, the value is 1667 sensed and is read-only; otherwise the value may be 1668 written by a control panel or management application. The 1669 value (-1) means other and places no restrictions on this 1670 parameter. The value (-2) means unknown." 1671 DEFVAL { -2 } -- unknown 1672 ::= { finSupplyEntry 7 } 1674 finSupplyCurrentLevel OBJECT-TYPE 1675 SYNTAX Integer32 (-3..2147483647) 1676 MAX-ACCESS read-write 1677 STATUS current 1678 DESCRIPTION 1679 "The current level if this supply is a container; the 1680 remaining space if this supply is a receptacle. If this 1681 supply container/receptacle can reliably sense this value, 1682 the value is sensed and is read-only; otherwise the value 1683 may be written by a control panel or management 1684 application. The value (-1) means other and places no 1685 restrictions on this parameter. The value (-2) means 1686 unknown. A value of (-3) means that the printer knows there 1687 is some supply or remaining space." 1688 DEFVAL { -2 } -- unknown 1689 ::= { finSupplyEntry 8 } 1691 -- Capacity Attribute Relationships 1692 -- 1693 -- MEDIA INPUT MEASUREMENT 1694 -- 1695 -- _______ | | 1696 -- | | | 1697 -- | | | | 1698 -- | |_ _ _ _ _ _ _ _ _ _| ________________ |direction 1699 -- | | | | v 1700 -- MaxCapacity | | | 1701 -- | | Sheets remaining | CurrentLevel 1702 -- | | | | 1703 -- v | | v 1704 -- _______ +___________________+ _______ 1706 finSupplyColorName OBJECT-TYPE 1707 SYNTAX OCTET STRING (SIZE(0..63)) 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "The name of the color associated with this supply." 1713 REFERENCE 1714 "The PWG Standardized Media Names specification [PWGMEDIA], 1715 section 4 Media Color Names, contains the recommended values 1716 for this object. Implementers may add additional string values. 1717 The naming conventions in ISO 9070 are recommended in order to 1718 avoid potential name clashes." 1719 ::= { finSupplyEntry 9 } 1721 -- Finisher Supply, Media Input Group (Conditionally Mandatory) 1722 -- 1723 -- A finisher device may have one or more associated supply media 1724 -- inputs. Each entry in this table defines an input for a 1725 -- supply media type such as inserts, covers, etc. 1726 -- 1727 -- This group is mandatory only if the printer system contains a 1728 -- finisher device that requires a media supply used exclusively by a 1729 -- finishing process. Examples are inserts or covers that are not 1730 -- supplied by an input subunit that provides media to the marker. 1732 finSupplyMediaInput OBJECT IDENTIFIER ::= { printmib 32 } 1734 finSupplyMediaInputTable OBJECT-TYPE 1735 SYNTAX SEQUENCE OF FinSupplyMediaInputEntry 1736 MAX-ACCESS not-accessible 1737 STATUS current 1738 DESCRIPTION 1739 "The input subunits associated with a finisher supply media 1740 are each represented by an entry in this table." 1741 ::= { finSupplyMediaInput 1 } 1743 finSupplyMediaInputEntry OBJECT-TYPE 1744 SYNTAX FinSupplyMediaInputEntry 1745 MAX-ACCESS not-accessible 1746 STATUS current 1747 DESCRIPTION 1748 "A list of finisher supply media input subunit features and 1749 characteristics." 1750 INDEX { hrDeviceIndex, finSupplyMediaInputIndex } 1751 ::= { finSupplyMediaInputTable 1 } 1753 FinSupplyMediaInputEntry ::= SEQUENCE { 1754 finSupplyMediaInputIndex Integer32, 1755 finSupplyMediaInputDeviceIndex Integer32, 1756 finSupplyMediaInputSupplyIndex Integer32, 1757 finSupplyMediaInputType PrtInputTypeTC, 1758 finSupplyMediaInputDimUnit PrtMediaUnitTC, 1759 finSupplyMediaInputMediaDimFeedDir Integer32, 1760 finSupplyMediaInputMediaDimXFeedDir Integer32, 1761 finSupplyMediaInputStatus PrtSubUnitStatusTC, 1762 finSupplyMediaInputMediaName OCTET STRING, 1763 finSupplyMediaInputName OCTET STRING, 1764 finSupplyMediaInputDescription PrtLocalizedDescriptionStringTC, 1765 finSupplyMediaInputSecurity PresentOnOff, 1766 finSupplyMediaInputMediaWeight Integer32, 1767 finSupplyMediaInputMediaThickness Integer32, 1768 finSupplyMediaInputMediaType OCTET STRING 1769 } 1771 finSupplyMediaInputIndex OBJECT-TYPE 1772 SYNTAX Integer32 (1..65535) 1773 MAX-ACCESS not-accessible 1774 STATUS current 1775 DESCRIPTION 1776 "A unique value used by a finisher to identify this supply 1777 media input subunit. Although these values may change 1778 due to a major reconfiguration of the finisher (e.g. the 1779 addition of new supply media input sources to the 1780 finisher), values are normally expected to remain stable 1781 across successive power cycles." 1782 ::= { finSupplyMediaInputEntry 1 } 1784 finSupplyMediaInputDeviceIndex OBJECT-TYPE 1785 SYNTAX Integer32 (0..65535) 1786 MAX-ACCESS read-only 1787 STATUS current 1788 DESCRIPTION 1789 "The value of finDeviceIndex corresponding to the finishing 1790 device subunit with which this finisher media supply is 1791 associated. The value zero indicates the associated device 1792 is unknown." 1793 ::= { finSupplyMediaInputEntry 2 } 1795 finSupplyMediaInputSupplyIndex OBJECT-TYPE 1796 SYNTAX Integer32 (0..65535) 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The value of finSupplyIndex corresponding to the finishing 1801 supply subunit with which this finisher media supply is 1802 associated. The value zero indicates the associated finishing 1803 supply is unknown or there is no applicable finisher supply 1804 table entry." 1805 ::= { finSupplyMediaInputEntry 3 } 1807 finSupplyMediaInputType OBJECT-TYPE 1808 SYNTAX PrtInputTypeTC 1809 MAX-ACCESS read-only 1810 STATUS current 1811 DESCRIPTION 1812 "The type of technology (discriminated primarily according 1813 to the feeder mechanism type) employed by the input 1814 subunit." 1815 ::= { finSupplyMediaInputEntry 4 } 1817 finSupplyMediaInputDimUnit OBJECT-TYPE 1818 SYNTAX PrtMediaUnitTC 1819 MAX-ACCESS read-only 1820 STATUS current 1821 DESCRIPTION 1822 "The unit of measure for specifying dimensional values for 1823 this input device." 1824 ::= { finSupplyMediaInputEntry 5 } 1826 finSupplyMediaInputMediaDimFeedDir OBJECT-TYPE 1827 SYNTAX Integer32 (-2..2147483647) 1828 MAX-ACCESS read-write 1829 STATUS current 1830 DESCRIPTION 1831 "This object provides the value of the dimension in the 1832 feed direction of the media that is placed or will be 1833 placed in this input device. Feed dimension measurements 1834 are taken parallel to the feed direction of the device and 1835 measured in finSupplyMediaInputDimUnits. If this input 1836 device can reliably sense this value, the value is sensed 1837 and is read-only access. Otherwise the value is read-write 1838 access and may be written by management or control panel 1839 applications. The value (-1) means other and specifically 1840 indicates that this device places no restrictions on this 1841 parameter. The value (-2) indicates unknown. " 1842 ::= { finSupplyMediaInputEntry 6 } 1844 finSupplyMediaInputMediaDimXFeedDir OBJECT-TYPE 1845 SYNTAX Integer32 (-2..2147483647) 1846 MAX-ACCESS read-write 1847 STATUS current 1848 DESCRIPTION 1849 "This object provides the value of the dimension across the 1850 feed direction of the media that is placed or will be 1851 placed in this input device. The cross feed direction is 1852 ninety degrees relative to the feed direction on this 1853 device and measured in finSupplyMediaInputDimUnits. If 1854 this input device can reliably sense this value, the value 1855 is sensed and is read-only access. Otherwise the value is 1856 read-write access and may be written by management or 1857 control panel applications. The value (-1) means other and 1858 specifically indicates that this device places no 1859 restrictions on this parameter. The value (-2) indicates 1860 unknown. " 1861 ::= { finSupplyMediaInputEntry 7 } 1863 finSupplyMediaInputStatus OBJECT-TYPE 1864 SYNTAX PrtSubUnitStatusTC 1865 MAX-ACCESS read-only 1866 STATUS current 1867 DESCRIPTION 1868 "This value indicates the current status of this input 1869 device." 1870 DEFVAL { 5 } -- unknown 1871 ::= { finSupplyMediaInputEntry 8 } 1873 finSupplyMediaInputMediaName OBJECT-TYPE 1874 SYNTAX OCTET STRING (SIZE(0..63)) 1875 MAX-ACCESS read-write 1876 STATUS current 1877 DESCRIPTION 1878 "The name of the current media contained in this input 1879 device. Examples are Engineering Manual Cover, Section A Tab 1880 Divider or any ISO standard names." 1882 ::= { finSupplyMediaInputEntry 9 } 1884 finSupplyMediaInputName OBJECT-TYPE 1885 SYNTAX OCTET STRING (SIZE(0..63)) 1886 MAX-ACCESS read-write 1887 STATUS current 1888 DESCRIPTION 1889 "The name assigned to this input subunit." 1890 ::= { finSupplyMediaInputEntry 10 } 1892 finSupplyMediaInputDescription OBJECT-TYPE 1893 SYNTAX PrtLocalizedDescriptionStringTC 1894 MAX-ACCESS read-only 1895 STATUS current 1896 DESCRIPTION 1897 "A free form text description of this input subunit in the 1898 localization specified by prtGeneralCurrentLocalization." 1899 ::= { finSupplyMediaInputEntry 11 } 1901 finSupplyMediaInputSecurity OBJECT-TYPE 1902 SYNTAX PresentOnOff 1903 MAX-ACCESS read-write 1904 STATUS current 1905 DESCRIPTION 1906 "Indicates if this subunit has some security associated 1907 with it." 1908 ::= { finSupplyMediaInputEntry 12 } 1910 finSupplyMediaInputMediaWeight OBJECT-TYPE 1911 SYNTAX Integer32 1912 MAX-ACCESS read-write 1913 STATUS current 1914 DESCRIPTION 1915 "The weight of the media associated with this Input device 1916 in grams per meter squared. The value (-1) means other 1917 and specifically indicates that the device places no 1918 restriction on this parameter. The value (-2) means 1919 unknown. This object can be used to calculate the weight 1920 of individual pages processed by the document finisher. 1921 This value, when multiplied by the number of pages in a 1922 finished set, can be used to calculate the weight of a set 1923 before it is inserted into a mailing envelope." 1924 ::= { finSupplyMediaInputEntry 13 } 1926 finSupplyMediaInputMediaThickness OBJECT-TYPE 1927 SYNTAX Integer32 (-2..2147483647) 1928 MAX-ACCESS read-write 1929 STATUS current 1930 DESCRIPTION 1931 "This object identifies the thickness of the input media 1932 processed by this document input subunit measured in 1933 micrometers. This value may be used by devices (or 1934 operators) to set up proper machine tolerances for the 1935 feeder operation. The value (-2) indicates that the media 1936 thickness is unknown or not used in the setup for this 1937 input subunit." 1938 ::= { finSupplyMediaInputEntry 14 } 1940 finSupplyMediaInputMediaType OBJECT-TYPE 1941 SYNTAX OCTET STRING (SIZE(0..63)) 1942 MAX-ACCESS read-write 1943 STATUS current 1944 DESCRIPTION 1945 "The name of the type of medium associated with this input 1946 subunit. " 1948 REFERENCE 1949 "The PWG Standardized Media Names specification [PWGMEDIA], 1950 section 3 Media Type Names, contains the recommended values 1951 for this object. Implementers may add additional string values. 1952 The naming conventions in ISO 9070 are recommended in order to 1953 avoid potential name clashes." 1954 ::= { finSupplyMediaInputEntry 15 } 1956 -- Finisher Device Attribute Group (Mandatory) 1957 -- 1958 -- A finisher device subunit may have one or more parameters that 1959 -- cannot be specified by any other objects in the MIB. The 1960 -- Device Attribute group facilitates the definition of these 1961 -- parameters. The objects which define the attributes are 1962 -- read-write, to allow both Set and Get operations. 1963 -- 1964 -- At least one table entry must exist for each finisher device defined 1965 -- by the MIB. If no other entry is possible for a finisher device, the 1966 -- deviceName(3) attribute MUST be returned. 1968 finDeviceAttribute OBJECT IDENTIFIER ::= { printmib 33 } 1970 finDeviceAttributeTable OBJECT-TYPE 1971 SYNTAX SEQUENCE OF FinDeviceAttributeEntry 1972 MAX-ACCESS not-accessible 1973 STATUS current 1974 DESCRIPTION 1975 "The attribute table defines special parameters that are 1976 applicable only to a minority of the finisher devices. 1977 An attribute table entry is used, rather than unique 1978 objects, to minimize the number of MIB objects and to 1979 allow for expansion without the addition of MIB objects. 1980 Each finisher device is represented by a separate row 1981 in the device subunit attribute table." 1982 ::= { finDeviceAttribute 1 } 1983 finDeviceAttributeEntry OBJECT-TYPE 1984 SYNTAX FinDeviceAttributeEntry 1985 MAX-ACCESS not-accessible 1986 STATUS current 1987 DESCRIPTION 1988 "Each entry defines a finisher function parameter that 1989 cannot be represented by an object in the finisher 1990 device subunit table." 1991 INDEX { hrDeviceIndex, finDeviceIndex, 1992 finDeviceAttributeTypeIndex, 1993 finDeviceAttributeInstanceIndex } 1994 ::= { finDeviceAttributeTable 1 } 1996 FinDeviceAttributeEntry ::= SEQUENCE { 1997 finDeviceAttributeTypeIndex FinAttributeTypeTC, 1998 finDeviceAttributeInstanceIndex Integer32, 1999 finDeviceAttributeValueAsInteger Integer32, 2000 finDeviceAttributeValueAsOctets OCTET STRING 2001 } 2003 finDeviceAttributeTypeIndex OBJECT-TYPE 2004 SYNTAX FinAttributeTypeTC 2005 MAX-ACCESS not-accessible 2006 STATUS current 2007 DESCRIPTION 2008 "Defines the attribute type represented by this row." 2009 ::= { finDeviceAttributeEntry 1 } 2011 finDeviceAttributeInstanceIndex OBJECT-TYPE 2012 SYNTAX Integer32 (1..65535) 2013 MAX-ACCESS not-accessible 2014 STATUS current 2015 DESCRIPTION 2016 "An index that allows the discrimination of an attribute 2017 instance when the same attribute occurs multiple times for 2018 a specific instance of a finisher function. The value of 2019 this index shall be 1 if only a single instance of the 2020 attribute occurs for the specific finisher function. 2021 Additional values shall be assigned in a contiguous manner." 2022 ::= { finDeviceAttributeEntry 2 } 2024 finDeviceAttributeValueAsInteger OBJECT-TYPE 2025 SYNTAX Integer32 (-2..2147483647) 2026 MAX-ACCESS read-write 2027 STATUS current 2028 DESCRIPTION 2029 "Defines the integer value of the attribute. The value of 2030 the attribute is represented as an integer if the 2031 finAttributeTypeTC description for the attribute has the 2032 tag 'INTEGER:'. 2034 Depending upon the attribute enum definition, this object 2035 may be either an integer, a counter, an index, or an enum. 2036 Attributes for which the concept of an integer value is 2037 not meaningful SHALL return a value of -1 for this 2038 attribute." 2039 DEFVAL { -2 } -- unknown 2040 ::= { finDeviceAttributeEntry 3 } 2042 finDeviceAttributeValueAsOctets OBJECT-TYPE 2043 SYNTAX OCTET STRING (SIZE(0..63)) 2044 MAX-ACCESS read-write 2045 STATUS current 2046 DESCRIPTION 2047 "Contains the octet string value of the attribute. The 2048 value of the attribute is represented as a string if the 2049 finAttributeTypeTC description for the attribute has the 2050 tag 'OCTETS:'. 2052 Depending upon the attribute enum definition, this object 2053 may be either a coded character set string (text) or a 2054 binary octet string. Attributes for which the concept of 2055 an octet string value is not meaningful SHALL contain a 2056 zero length string." 2057 DEFVAL { ''H } -- empty string 2058 ::= { finDeviceAttributeEntry 4 } 2060 -- Conformance Information 2062 -- compliance statements 2064 finMIBCompliance MODULE-COMPLIANCE 2065 STATUS current 2066 DESCRIPTION 2067 "The compliance statement for agents that implement the 2068 finisher MIB." 2069 MODULE -- this module 2070 MANDATORY-GROUPS { finDeviceGroup, finSupplyGroup, 2071 finDeviceAttributeGroup } 2073 OBJECT finDevicePresentOnOff 2074 MIN-ACCESS read-only 2075 DESCRIPTION 2076 "It is conformant to implement this object as read-only." 2078 OBJECT finDeviceMaxCapacity 2079 MIN-ACCESS read-only 2080 DESCRIPTION 2081 "It is conformant to implement this object as read-only." 2083 OBJECT finDeviceCurrentCapacity 2084 MIN-ACCESS read-only 2085 DESCRIPTION 2086 "It is conformant to implement this object as read-only." 2088 OBJECT finSupplyMaxCapacity 2089 MIN-ACCESS read-only 2090 DESCRIPTION 2091 "It is conformant to implement this object as read-only." 2093 OBJECT finSupplyCurrentLevel 2094 MIN-ACCESS read-only 2095 DESCRIPTION 2096 "It is conformant to implement this object as read-only." 2098 OBJECT finSupplyMediaInputMediaDimFeedDir 2099 MIN-ACCESS read-only 2100 DESCRIPTION 2101 "It is conformant to implement this object as read-only." 2103 OBJECT finSupplyMediaInputMediaDimXFeedDir 2104 MIN-ACCESS read-only 2105 DESCRIPTION 2106 "It is conformant to implement this object as read-only." 2108 OBJECT finSupplyMediaInputMediaName 2109 MIN-ACCESS read-only 2110 DESCRIPTION 2111 "It is conformant to implement this object as read-only." 2113 OBJECT finSupplyMediaInputName 2114 MIN-ACCESS read-only 2115 DESCRIPTION 2116 "It is conformant to implement this object as read-only." 2118 OBJECT finSupplyMediaInputSecurity 2119 MIN-ACCESS read-only 2120 DESCRIPTION 2121 "It is conformant to implement this object as read-only." 2123 OBJECT finSupplyMediaInputMediaWeight 2124 MIN-ACCESS read-only 2125 DESCRIPTION 2126 "It is conformant to implement this object as read-only." 2128 OBJECT finSupplyMediaInputMediaThickness 2129 MIN-ACCESS read-only 2130 DESCRIPTION 2131 "It is conformant to implement this object as read-only." 2133 OBJECT finSupplyMediaInputMediaType 2134 MIN-ACCESS read-only 2135 DESCRIPTION 2136 "It is conformant to implement this object as read-only." 2138 OBJECT finDeviceAttributeValueAsInteger 2139 MIN-ACCESS read-only 2140 DESCRIPTION 2141 "It is conformant to implement this object as read-only." 2143 OBJECT finDeviceAttributeValueAsOctets 2144 MIN-ACCESS read-only 2145 DESCRIPTION 2146 "It is conformant to implement this object as read-only." 2148 GROUP finSupplyMediaInputGroup 2149 DESCRIPTION 2150 "This group is conditionally mandatory and must be included 2151 if a finisher device requires a media supply that is used 2152 exclusively by a finishing process." 2154 ::= { prtMIBConformance 5 } 2156 finMIBGroups OBJECT IDENTIFIER ::= { prtMIBConformance 6 } 2158 finDeviceGroup OBJECT-GROUP 2159 OBJECTS { finDeviceType, finDevicePresentOnOff, 2160 finDeviceCapacityUnit, finDeviceMaxCapacity, 2161 finDeviceCurrentCapacity, finDeviceAssociatedMediaPaths, 2162 finDeviceAssociatedOutputs, finDeviceStatus, 2163 finDeviceDescription } 2164 STATUS current 2165 DESCRIPTION 2166 "The finisher device group." 2167 ::= { finMIBGroups 1 } 2169 finSupplyGroup OBJECT-GROUP 2170 OBJECTS { finSupplyDeviceIndex, finSupplyClass, finSupplyType, 2171 finSupplyDescription, finSupplyUnit, finSupplyMaxCapacity, 2172 finSupplyCurrentLevel, finSupplyColorName } 2173 STATUS current 2174 DESCRIPTION 2175 "The finisher supply group." 2176 ::= { finMIBGroups 2 } 2178 finSupplyMediaInputGroup OBJECT-GROUP 2179 OBJECTS { finSupplyMediaInputDeviceIndex, 2180 finSupplyMediaInputSupplyIndex, finSupplyMediaInputType, 2181 finSupplyMediaInputDimUnit, 2182 finSupplyMediaInputMediaDimFeedDir, 2183 finSupplyMediaInputMediaDimXFeedDir, 2184 finSupplyMediaInputStatus, finSupplyMediaInputMediaName, 2185 finSupplyMediaInputName, finSupplyMediaInputDescription, 2186 finSupplyMediaInputSecurity, 2187 finSupplyMediaInputMediaWeight, 2188 finSupplyMediaInputMediaThickness, 2189 finSupplyMediaInputMediaType } 2190 STATUS current 2191 DESCRIPTION 2192 "The finisher supply, media input group." 2193 ::= { finMIBGroups 3 } 2195 finDeviceAttributeGroup OBJECT-GROUP 2196 OBJECTS { finDeviceAttributeValueAsInteger, 2197 finDeviceAttributeValueAsOctets } 2198 STATUS current 2199 DESCRIPTION 2200 "The finisher device attribute group. This group is mandatory 2201 for a finisher device that contains an inserter subunit." 2202 ::= { finMIBGroups 4 } 2204 END 2206 9. IANA CONSIDERATIONS 2208 The initial version the IANA Finisher MIB defined in section 7 of 2209 this document is to be archived by IANA and subsequently maintained 2210 according to the Process specified in section 6.1 of this document. 2212 10. INTELLECTUAL PROPERTY 2214 The IETF takes no position regarding the validity or scope of any 2215 intellectual property or other rights that might be claimed to 2216 pertain to the implementation or use of the technology described in 2217 this document or the extent to which any license under such rights 2218 might or might not be available; neither does it represent that it 2219 has made any effort to identify any such rights. Information on the 2220 IETF's procedures with respect to rights in standards-track and 2221 standards-related documentation can be found in RFC 2028. Copies of 2222 claims of rights made available for publication and any assurances of 2223 licenses to be made available, or the result of an attempt made to 2224 obtain a general license or permission for the use of such 2225 proprietary rights by implementors or users of this specification can 2226 be obtained from the IETF Secretariat. 2228 The IETF invites any interested party to bring to its attention any 2229 copyrights, patents or patent applications, or other proprietary 2230 rights which may cover technology that may be required to practice 2231 this standard. Please address the information to the IETF Executive 2232 Director. 2234 11. INTERNATIONALIZATION CONSIDERATIONS 2235 See the Printer MIB [RFCnnnn] section 2.2.1.1, 'International 2236 Considerations'. 2237 Note to RFC Editor: Insert RFC number 'nnnn' when assigned. 2239 12. NORMATIVE REFERENCES 2241 Find IETF (Internet Engineering Task Force) RFCs at www.ietf.org. 2242 Find PWG (IEEE/ISTO Printer Working Group) at www.pwg.org. 2244 [DPA] ISO/IEC 10175 Document Printing Application (DPA). See 2245 ftp://ftp.pwg.org/pub/pwg/dpa/ 2247 [LMO] Large Mailing Operations Specification, DMTF. See 2248 http://www.dmtf.org/tech/apps.html 2250 [PWGMEDIA] IEEE-ISTO "The Printer Working Group Standard for Media 2251 Standardized Names", IEEE-ISTO 5101.1-2002. 2253 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2254 Requirement Levels", BCP 14, RFC 2119, March 1997. 2256 [RFC2434] Narten & Alvestrand, "Guidelines for Writing an IANA 2257 Considerations Section in RFCs", RFC 2434, October 1998. 2259 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2260 Rose, M., and S. Waldbusser, "Structure of Management 2261 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2263 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2264 Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", 2265 STD 58, RFC 2579, April 1999. 2267 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2268 Rose, M., and S. Waldbusser, "Conformance Statements for 2269 SMIv2", STD 58, RFC 2580, April 1999. 2271 Note to RFC Editor: Insert RFC number 'nnnn' when assigned. 2272 [RFCnnnn] Bergman, McDonald, Lewis, "The Printer MIB v2", RFC nnnn, 2273 2002. 2275 13. INFORMATIVE REFERENCES 2277 [RFC2911] Hastings et al, "Internet Printing Protocol/1.1: Model and 2278 Semantics", RFC 2911, September 2000. 2280 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2281 "Introduction and Applicability Statements for Internet- 2282 Standard Management Framework", RFC 3410, December 2002. 2284 14. SECURITY CONSIDERATIONS 2286 There are a number of management objects defined in this MIB module 2287 with a MAX-ACCESS clause of read-write and/or read-create. Such 2289 objects may be considered sensitive or vulnerable in some network 2290 environments. The support for SET operations in a non-secure 2291 environment without proper protection can have a negative effect on 2292 network operations. These are the tables and objects and their 2293 sensitivity/vulnerability: 2295 finDeviceTable: 2296 finDevicePresentOnOff -Possible severe inconvenience 2297 finDeviceMaxCapacity -Possible minor inconvenience 2298 finDeviceCurrentCapacity -Possible minor inconvenience 2299 finSupplyTable: 2300 finSupplyMaxCapacity -Possible minor inconvenience 2301 finSupplyCurrentLevel -Possible minor inconvenience 2302 finSupplyMediaInputTable 2303 finSupplyMediaInputMediaDimFeedDir -Possible severe inconvenience 2304 finSupplyMediaInputMediaDimXFeedDir -Possible severe inconvenience 2305 finSupplyMediaInputMediaName -Possible Minor inconvenience 2306 finSupplyMediaInputName -Possible Minor inconvenience 2307 finSupplyMediaInputSecurity -Possible Minor inconvenience 2308 finSupplyMediaInputMediaWeight -Possible Minor inconvenience 2309 finSupplyMediaInputMediaThickness -Possible Minor inconvenience 2310 finSupplyMediaInputMediaType -Possible Minor inconvenience 2311 finDeviceAttributeTable 2312 finDeviceAttributeValueAsInteger -Possible Minor inconvenience 2313 finDeviceAttributeValueAsOctets -Possible Minor inconvenience 2315 SNMP versions prior to SNMPv3 did not include adequate security. 2316 Even if the network itself is secure (for example by using IPSec), 2317 even then, there is no control as to who on the secure network is 2318 allowed to access and GET/SET (read/change/create/delete) the objects 2319 in this MIB module. 2321 It is RECOMMENDED that implementers consider the security features as 2322 provided by the SNMPv3 framework (see [RFC3410], section 8), 2323 including full support for the SNMPv3 cryptographic mechanisms (for 2324 authentication and privacy). 2326 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2327 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2328 enable cryptographic security. It is then a customer/operator 2329 responsibility to ensure that the SNMP entity giving access to an 2330 instance of this MIB module is properly configured to give access to 2332 the objects only to those principals (users) that have legitimate 2333 rights to indeed GET or SET (change/create/delete) them. 2335 Where the operational capability of the printing device are 2336 especially vulnerable or difficult to administer, certain objects 2337 within this MIB have been tagged as READ-ONLY, preventing 2338 modification. Further, for all READ-WRITE objects within the MIB, the 2339 working group has included specific conformance guidelines stating 2340 that vendors are free to implement certain objects as READ-ONLY. This 2341 conformance allowance should cover cases where specific vendor 2342 vulnerabilities may differ from product to product. (See conformance 2343 section with regards to MIN-ACCESS clauses). 2345 15. FULL COPYRIGHT STATEMENT 2347 Copyright (C) The Internet Society (2003). All Rights Reserved. 2349 This document and translations of it may be copied and furnished to 2350 others, and derivative works that comment on or otherwise explain it 2351 or assist in its implementation may be prepared, copied, published 2352 and distributed, in whole or in part, without restriction of any 2353 kind, provided that the above copyright notice and this paragraph are 2354 included on all such copies and derivative works. However, this 2355 document itself may not be modified in any way, such as by removing 2356 the copyright notice or references to the Internet Society or other 2357 Internet organizations, except as needed for the purpose of 2358 developing Internet standards in which case the procedures for 2359 copyrights defined in the Internet Standards process must be 2360 followed, or as required to translate it into languages other than 2361 English. 2363 The limited permissions granted above are perpetual and will not be 2364 revoked by the Internet Society or its successors or assigns. 2366 This document and the information contained herein is provided on an 2367 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2368 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2369 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2370 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2371 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2373 16. AUTHORS 2375 This document was created with significant contributions from the 2376 following individuals. 2378 Ron Bergman (Editor) 2379 Hitachi Printing Solutions America 2380 1757 Tapo Canyon Road 2381 Simi Valley, CA 93063-3394 2383 Phone: 805-578-4421 2384 Fax: 805-578-4001 2385 Email: Ron.Bergman@hitachi-ps.us 2386 Harry Lewis (chairman) 2387 IBM Corporation 2388 6300 Diagonal Hwy 2389 Boulder, CO 80301 2391 Phone: (303) 924-5337 2392 Fax: (303) 924-4662 2393 Email: harryl@us.ibm.com 2395 Ira McDonald 2396 High North Inc. 2397 P.O. Box 221 2398 Grand Marais, MI 49839 2400 Phone: (906) 494-2434 or (906) 494-2697 2401 Email: imcdonald@sharplabs.com 2403 Send comments to the Printer Working Group (PWG) using the Finisher 2404 MIB Project (FIN) Mailing List: fin@pwg.org 2406 Implementers of this specification are encouraged to join this email 2407 distribution list in order to participate in any discussions of 2408 clarification issues and review registration proposals for 2409 additional attributes and enum values. 2411 For further information, access the PWG web page under "FIN": 2412 http://www.pwg.org/ 2414 The Printer MIB Working Group would like to extend a special thank 2415 you to the following individuals that put forth a significant effort 2416 to review this document and provide numerous suggestions for 2417 improvement. 2419 David Harrington . Enterasys Networks 2420 Juergen Schoenwaelder . TU Braunschweig 2421 Bert Wijnen . Lucent Technologies and IETF Op & Mngmt, Area Director 2423 Other Participants: 2425 Chuck Adams - Tektronix 2426 Carlos Becerra - HP 2427 Andy Davidson - Tektronix 2428 Mabry Dozier - QMS 2429 Lee Farrell - Canon 2430 Jennifer Gattis - Duplo USA 2431 Paul Gloger - Xerox 2432 Richard Hart - Digital 2433 Tom Hastings - Xerox 2434 Scott Isaacson - Novell 2435 David Kellerman - Northlake Software 2436 Henrik Holst - i-data International 2437 Rick Landau - Digital 2438 Jay Martin - Underscore 2439 Gary Padlipski - Xerox 2440 Kevin Palmer - Duplo USA 2441 Bob Pentecost - HP 2442 Stuart Rowley - Kyocera 2443 Yuki Sacchi - Japan Computer Industry 2444 Philip Thambidunai - Okidata 2445 William Wagner - DPI/Osicom 2446 Chris Wellens - Interworking Labs 2447 Don Wright - Lexmark 2448 Lloyd Young - Lexmark