10. References 10.1. Normative References [ASCII] ANSI, "Coded Character Set - 7-bit American Standard Code for Information Interchange", ANSI X3.4-1986. [CHARSET] IANA Character Set Registry: http://www.iana.org/assignments/character-sets [CHARMIB] IANA Character Set MIB: http://www.iana.org/assignments/ianacharset-mib [ISO10175] ISO, "Document Printing Application (DPA)", ISO 10175, 1996. [ISO10646] ISO, "Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane", ISO 10646-1, September 2000. ISO, "Universal Multiple-Octet Coded Character Set (UCS) - Part 2: Supplemental Planes", ISO 10646-2, January 2001. [PWGMEDIA] IEEE-ISTO PWG "The Printer Working Group Standard for Media Standardized Names", IEEE-ISTO PWG 5101.1-2002. [RFC1213] McCloghrie, K. and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 3629, November 2003.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC 2790, March 2000. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3806] Bergman, R., Lewis, H., and I. McDonald, "Printer Finishing MIB", RFC 3806, June 2004. 10.2. Informative References [APPLEMAC] Apple staff, "Inside MacIntosh: Networking", 1994. [RFC854] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, May 1983. [RFC959] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9, RFC 959, October 1985. [RFC1179] McLaughlin, L., "Line printer daemon protocol", RFC 1179, August 1990. [RFC1350] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, July 1992. [RFC1945] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext Transfer Protocol - HTTP/1.0", RFC 1945, May 1996. [RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC 2246, 1999.
[RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1", RFC 2616, June 1999. [RFC2821] Klensin, J., Ed., "Simple Mail Transfer Protocol", RFC 2821, April 2001. [RFC2822] Resnick, P., Ed., "Internet Message Format", RFC 2822, April 2001. [RFC2910] Herriot, R., Ed., Butler, S., Moore, P., Turner, R., and J. Wenn, "Internet Printing Protocol/1.1: Encoding and Transport", RFC 2910, September 2000. [RFC2911] Hastings, T., Ed., Herriot, R., deBry, R., Isaacson, S., and P. Powell, "Internet Printing Protocol/1.1: Model and Semantics", RFC 2911, September 2000. [RFC2978] Freed, N. and J. Postel, "IANA Charset Registration Procedures", BCP 19, RFC 2978, October 2000. [RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced by an On-line Database", RFC 3232, January 2002. [RFC3285] Gahrns, M. and T. Hain, "Using Microsoft Word to create Internet Drafts and RFCs", RFC 3285, May 2002. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002.
Appendix A - Glossary of Terms Addressability - On the marker, the number of distinct marking units (pels) per unit of addressability unit that can be set; for example, 300 dots per inch is expressed as 300 per 1000 Thousandths Of Inches and 4 dots per millimeter is 4 per 1000 Micrometers. Addressability is not resolution because marks that are one addressability position apart may not be independently resolvable by the eye due to factors such as gain in the area of marks so they overlap or nearly touch. Alert - A reportable event for which there is an entry in the alert table. Bin - An output sub-unit which may or may not be removable. Binary Change Event - An event which comes in pairs; the leading edge event and the trailing edge event. The leading edge event enters a state from which there is only one exit. A binary change event may be critical or non-critical. See unary change event. Bursting - The process by which continuous media is separated into individual sheets, typically by bursting along pre-formed perforations. Channel - A term used to describe a single source of data which is presented to a printer. The model that we use in describing a printer allows for an arbitrary number of channels. Multiple channels can exist on the same physical port. This is commonly done over Ethernet ports where EtherTalk, TCP/IP, and SPX/IPX protocols can be supplying different data streams simultaneously to a single printer on the same physical port. Collation - In multiple copy output, placing the pages from separate copies into separate ordered sets, ready for binding. Control Language - A data syntax or language for controlling the printer through the print data channel. Critical Alert - An alert triggered by an event which leads to a state in which printing is no longer possible; the printer is stopped. Decollating - The process by which the individual parts within a multi-part form are separated and sorted into separate stacks for each part. Description - Information about the configuration and capabilities of the printer and its various sub-units.
DPA - ISO 10175 Document Printing Application standard. A standard for a client server protocol for a print system, including (1) submitting print jobs to and (2) managing print jobs in a spooler. Event - A state change in the printer. Group - A collection of objects that represent a type of sub-unit of the printer. Host Resources MIB - See [RFC2790]. IANA - Internet Assigned Numbers Authority. See [RFC3232]. Idempotent - Idempotence is the property of an operation that results in the same state no matter how many times it is executed (at least once). This is a property that is shared by true databases in which operations on data items only change the state of the data item and do not have other side effects. Because the SNMP data model is that of operations on a database, SNMP MIB objects should be assumed to be idempotent. If a MIB object is defined in a non-idempotent way, the this data model can break in subtle ways when faced with packet loss, multiple managers, and other common conditions. In order to fulfill the common need for actions to result from SNMP Set operations, SNMP MIB objects can be modeled such that the change in state from one state to another has the side effect of causing an action. It is important to note that with this model, an SNMP operation that sets a value equal to its current value will cause no action. This retains the idempotence of a single command, while allowing actions to be initiated by SNMP SET requests. Input - A tray or bin from which instances of the media are obtained and fed into the Media Path. Interpreter - The embodiment of an algorithm that processes a data stream consisting of a Page Description Language (PDL) and/or a Control Language. Localization - The specification of human language, country, and character set needed to present information to people in their native languages. Management Application (a.k.a. Manager) - A program which queries and controls one or more managed nodes. Management Station - A physical computer on which one or more management applications can run.
Media Path - The mechanisms that transport instances of the media from an input, through the marker, possibly through media buffers and duplex pathways, out to the output with optional finishing applied. The inputs and outputs are not part of the Media Path. Non-critical Alert - An alert triggered by a reportable event which does not lead to a state in which printing is no longer possible; such an alert may lead to a state from which printing may no longer be possible in the future, such as the low toner state or the alert may be pure informational, such as a configuration change at the printer. Output - A bin or stacker which accepts instances of media that have been processed by a printer. Page Description Language (PDL) - A data syntax or language for the electronic representation of a document as a sequence of page images. Printer - A physical device that takes media from an input source, produces marks on that media according to some page description or page control language and puts the result in some output destination, possibly with finishing applied. Printing - The entire process of producing a printed document from generation of the file to be printed, choosing printing properties, selection of a printer, routing, queuing, resource management, scheduling, and finally printing including notifying the user. Reportable event - An event that is deemed of interest to a management station watching the printer. Status - Information regarding the current operating state of the printer and its various sub-units. This is an abstraction of the exact physical condition of the printer. Sub-mechanism - A distinguishable part of a sub-unit. Sub-unit - A part of the printer which may be a physical part, such as one of the input sources or a logical part such as an interpreter. Tray - An input sub-unit which is typically removable. Unary Change Event - An event that indicates a change of state of the printer, but to a state which is (often) just as valid as the state that was left, and from which no return is necessary. See binary change event.
Visible state - The portion of the state of the printer that can be examined by a management application. Warning - A non-critical alert. See non-critical alert. Appendix B - Media Size Names The PWG Standardized Media Names specification [PWGMEDIA], section 5 Self Describing Names, contains the currently recommended media size names. This appendix lists the standardized media size names from ISO/IEC 10175 Document Printing Application (DPA), [ISO10175] as presented in RFC 1759. Management applications are encouraged to use the names from the PWG standard. However, many legacy systems exist that use the DPA names and they are presented here for the convenience of developers. A printer implementing the Printer MIB has no knowledge of these names, however; all media sizes in the MIB are given in terms of media dimensions as the values of prtInputMediaDimFeedDirChosen and prtInputMediaDimXFeedDirChosen. String name Description other unknown na-letter or letter North American letter size: 8.5 by 11 inches na-legal or legal North American legal size: 8.5 by 14 inches na-10x13-envelope North American 10x13 envelope size: 10 by 13 inches na-9x12-envelope North American 9x12 envelope size: 9 by 12 inches na-number-10-envelope North American number 10 business envelope size: 4.125 by 9.5 inches na-7x9-envelope North American 7x9 size: 7 by 9 inches na-9x11-envelope North American 9x11 size: 9 by 11 inches na-10x14-envelope North American 10x14 envelope size: 10 by 14 inches na-number-9-envelope North American number 9 business envelope size: 3.875 by 8.875 inches na-6x9-envelope North American 6x9 envelope size: 6 by 9 inches na-10x15-envelope North American 10x15 envelope size: 10 by 15 inches a engineering A size 8.5 inches by 11 inches b engineering B size 11 inches by 17 inches c engineering C size 17 inches by 22 inches d engineering D size 22 inches by 34 inches
e engineering E size 34 inches by 44 inches iso-a0 ISO A0 size: 841 mm by 1189 mm iso-a1 ISO A1 size: 594 mm by 841 mm iso-a2 ISO A2 size: 420 mm by 594 mm iso-a3 ISO A3 size: 297 mm by 420 mm iso-a4 ISO A4 size: 210 mm by 297 mm iso-a5 ISO A5 size: 148 mm by 210 mm iso-a6 ISO A6 size: 105 mm by 148 mm iso-a7 ISO A7 size: 74 mm by 105 mm iso-a8 ISO A8 size: 52 mm by 74 mm iso-a9 ISO A9 size: 37 mm by 52 mm iso-a10 ISO A10 size: 26 mm by 37 mm iso-b0 ISO B0 size: 1000 mm by 1414 mm iso-b1 ISO B1 size: 707 mm by 1000 mm iso-b2 ISO B2 size: 500 mm by 707 mm iso-b3 ISO B3 size: 353 mm by 500 mm iso-b4 ISO B4 size: 250 mm by 353 mm iso-b5 ISO B5 size: 176 mm by 250 mm iso-b6 ISO B6 size: 125 mm by 176 mm iso-b7 ISO B7 size: 88 mm by 125 mm iso-b8 ISO B8 size: 62 mm by 88 mm iso-b9 ISO B9 size: 44 mm by 62 mm iso-b10 ISO B10 size: 31 mm by 44 mm iso-c0 ISO C0 size: 917 mm by 1297 mm iso-c1 ISO C1 size: 648 mm by 917 mm iso-c2 ISO C2 size: 458 mm by 648 mm iso-c3 ISO C3 size: 324 mm by 458 mm iso-c4 ISO C4 size: 229 mm by 324 mm iso-c5 ISO C5 size: 162 mm by 229 mm iso-c6 ISO C6 size: 114 mm by 162 mm iso-c7 ISO C7 size: 81 mm by 114 mm iso-c8 ISO C8 size: 57 mm by 81 mm iso-designated ISO Designated Long size: 110 mm by 220 mm jis-b0 JIS B0 size 1030 mm by 1456 mm jis-b1 JIS B1 size 728 mm by 1030 mm jis-b2 JIS B2 size 515 mm by 728 mm jis-b3 JIS B3 size 364 mm by 515 mm jis-b4 JIS B4 size 257 mm by 364 mm jis-b5 JIS B5 size 182 mm by 257 mm jis-b6 JIS B6 size 128 mm by 182 mm jis-b7 JIS B7 size 91 mm by 128 mm jis-b8 JIS B8 size 64 mm by 91 mm jis-b9 JIS B9 size 45 mm by 64 mm jis-b10 JIS B10 size 32 mm by 45 mm
Appendix C - Media Names For the convenience of management application developers, this appendix lists the standardized media names from ISO/IEC 10175 Document Printing Application (DPA), [ISO10175]. Management applications that present a dialogue for choosing media may wish to use these names as an alternative to separately specifying, size, color, and/or type. New names may also be created using this format and the names defined in the PWG Standardized Media Names specification [PWGMEDIA]. Using standard media names will mean that a single management application dealing with printers from different vendors and under different system mangers will tend to use the same names for the same media. If selection of media by name is used, the attributes (size, type or color) implied by the name must be explicitly mapped to the appropriate object (prtInputMediaDimFeedDirDeclared, prtInputMediaDimXFeedDirDeclared, prtInputMediaType and prtInputMediaColor) in the MIB. The object prtInputMediaName is intended for display to an operator and is purely descriptive. The value in prtInputMediaName is not interpreted by the printer so using a standard name for this value will not change any of the other media attributes nor will it cause an alert if the media in the input sub- unit does not match the name. Simple Name Descriptor Text other unknown iso-a4-white Specifies the ISO A4 white medium with size: 210 mm by 297 mm as defined in ISO 216 iso-a4-coloured Specifies the ISO A4 colored medium with size: 210 mm by 297 mm as defined in ISO 216 iso-a4-transparent Specifies the ISO A4 transparent medium with size: 210 mm by 297 mm as defined in ISO 216 iso-a3-white Specifies the ISO A3 white medium with size: 297 mm by 420 mm as defined in ISO 216 iso-a3-coloured Specifies the ISO A3 colored medium with size: 297 mm by 420 mm as defined in ISO 216 iso-a5-white Specifies the ISO A5 white medium with size: 148 mm by 210 mm as defined in ISO 216 iso-a5-coloured Specifies the ISO A5 colored medium with size: 148 mm by 210 mm as defined in ISO 216 iso-b4-white Specifies the ISO B4 white medium with size: 250 mm by 353 mm as defined in ISO 216 iso-b4-coloured Specifies the ISO B4 colored medium with size: 250 mm by 353 mm as defined in ISO 216
iso-b5-white Specifies the ISO B5 white medium with size: 176 mm by 250 mm as defined in ISO 216 iso-b5-coloured Specifies the ISO B5 colored medium with size: 176 mm by 250 mm as defined in ISO 216 jis-b4-white Specifies the JIS B4 white medium with size: 257 mm by 364 mm as defined in JIS P0138 jis-b4-coloured Specifies the JIS B4 colored medium with size: 257 mm by 364 mm as defined in JIS P0138 jis-b5-white Specifies the JIS B5 white medium with size: 182 mm by 257 mm as defined in JIS P0138 jis-b5-coloured Specifies the JIS B5 colored medium with size: 182 mm by 257 mm as defined in JIS P0138 The following standard values are defined for North American media: na-letter-white Specifies the North American letter white medium with size: 8.5 inches by 11 inches na-letter-coloured Specifies the North American letter colored medium with size: 8.5 inches by 11 inches na-letter-transparent Specifies the North American letter transparent medium with size: 8.5 inches by 11 inches na-legal-white Specifies the North American legal white medium with size: 8.5 inches by 14 inches na-legal-coloured Specifies the North American legal colored medium with size: 8.5 inches by 14 inches The following standard values are defined for envelopes: iso-b5-envelope Specifies the ISO B5 envelope medium with size: 176 mm by 250 mm as defined in ISO 216 and ISO 269 iso-b4-envelope Specifies the ISO B4 envelope medium with size: 250 mm by 353 mm as defined in ISO 216 iso-c4-envelope Specifies the ISO C4 envelope medium with size: 229 mm by 324 mm as defined in ISO 216 and ISO 269 iso-c5-envelope Specifies the ISO C5 envelope medium with size: 162 mm by 229 mm as defined in ISO 269 iso-designated-long-envelope Specifies the ISO Designated Long envelope medium with size: 110 mm by 220 mm as defined in ISO 269
na-10x13-envelope Specifies the North American 10x13 envelope medium with size: 10 inches by 13 inches na-9x12-envelope Specifies the North American 9x12 envelope medium with size: 9 inches by 12 inches na-number-10-envelope Specifies the North American number 10 business envelope medium with size: 4.125 inches by 9.5 inches na-7x9-envelope Specifies the North American 7x9 inch envelope na-9x11-envelope Specifies the North American 9x11 inch envelope na-10x14-envelope Specifies the North American 10x14 inch envelope na-number-9-envelope Specifies the North American number 9 business envelope 3.875 by 8.875 inches na-6x9-envelope Specifies the North American 6x9 inch envelope na-10x15-envelope Specifies the North American 10x15 inch envelope The following standard values are defined for the less commonly used media (white-only): iso-a0-white Specifies the ISO A0 white medium with size: 841 mm by 1189 mm as defined in ISO 216 iso-a1-white Specifies the ISO A1 white medium with size: 594 mm by 841 mm as defined in ISO 216 iso-a2-white Specifies the ISO A2 white medium with size: 420 mm by 594 mm as defined in ISO 216 iso-a6-white Specifies the ISO A6 white medium with size: 105 mm by 148 mm as defined in ISO 216 iso-a7-white Specifies the ISO A7 white medium with size: 74 mm by 105 mm as defined in ISO 216 iso-a8-white Specifies the ISO A8 white medium with size: 52 mm by 74 mm as defined in ISO 216 iso-a9-white Specifies the ISO A9 white medium with size: 39 mm by 52 mm as defined in ISO 216 iso-a10-white Specifies the ISO A10 white medium with size: 26 mm by 37 mm as defined in ISO 216
iso-b0-white Specifies the ISO B0 white medium with size: 1000 mm by 1414 mm as defined in ISO 216 iso-b1-white Specifies the ISO B1 white medium with size: 707 mm by 1000 mm as defined in ISO 216 iso-b2-white Specifies the ISO B2 white medium with size: 500 mm by 707 mm as defined in ISO 216 iso-b3-white Specifies the ISO B3 white medium with size: 353 mm by 500 mm as defined in ISO 216 iso-b6-white Specifies the ISO B6 white medium with size: 125 mm by 176 mm i as defined in ISO 216 iso-b7-white Specifies the ISO B7 white medium with size: 88 mm by 125 mm as defined in ISO 216 iso-b8-white Specifies the ISO B8 white medium with size: 62 mm by 88 mm as defined in ISO 216 iso-b9-white Specifies the ISO B9 white medium with size: 44 mm by 62 mm as defined in ISO 216 iso-b10-white Specifies the ISO B10 white medium with size: 31 mm by 44 mm as defined in ISO 216 jis-b0-white Specifies the JIS B0 white medium with size: 1030 mm by 1456 mm jis-b1-white Specifies the JIS B1 white medium with size: 728 mm by 1030 mm jis-b2-white Specifies the JIS B2 white medium with size: 515 mm by 728 mm jis-b3-white Specifies the JIS B3 white medium with size: 364 mm by 515 mm jis-b6-white Specifies the JIS B6 white medium with size: 257 mm by 364 mm jis-b7-white Specifies the JIS B7 white medium with size: 182 mm by 257 mm jis-b8-white Specifies the JIS B8 white medium with size: 128 mm by 182 mm jis-b9-white Specifies the JIS B9 white medium with size: 91 mm by 128 mm jis-b10-white Specifies the JIS B10 white medium with size: 64 mm by 91 mm
The following standard values are defined for engineering media: a Specifies the engineering A size medium with size: 8.5 inches by 11 inches b Specifies the engineering B size medium with size: 11 inches by 17 inches c Specifies the engineering C size medium with size: 17 inches by 22 inches d Specifies the engineering D size medium with size: 22 inches by 34 inches e Specifies the engineering E size medium with size: 34 inches by 44 inches Appendix D - Roles of Users Background The need for "Role Models" stemmed in large part from the need to understand the importance of any given proposed object for the MIB. Many times the real world need for a proposed object would be debated within the group; the debate would typically result in the need to describe the potential usage of the object in terms of a "live" person performing some type of printing-related task. Determining the value of a proposed object through identification of the associated human users was found to be so common that a more formalized model was required for consistent analysis. The model describing categories of human-oriented tasks is called "Role Models" in this document. In developing the Role Models it was necessary to identify the common, primary tasks that humans typically face when interacting with a printer and its related printing system(s). It was expected that certain kinds of tasks would serve to identify the various Role Models. In presenting the set of Role Models, the set of "Common Print System Tasks" are first presented, followed by the set of Role Model definitions. Finally, a simple matrix is presented in which Role Models and Tasks are cross-compared. Common Print System Tasks Upon researching the many tasks encountered by humans in dealing with printers and printing systems, the following were found to be pervasive within any operating environment: Printer job state - Determine the status of a job without a printer.
Printer capabilities - Determine the current capabilities of a printer, for example, the available media sizes, two-sided printing, a particular type of interpreter, etc. Printer job submission - Submit a print job to a printer. Printer job removal - Remove a job from a printer. Notification of events - Receive notification of the existence of a defined printer event. An event can be of many types, including warnings, errors, job stage completion (e.g., "job done"), etc. Printer configuration - Query the current configuration of a printer. Printer consumables - Determine the current state of any and all consumables within a printer. Print job identification - Determine the identification of a job within a printer. Internal printer status - Determine the current status of the printer. Printer identification - Determine the identity of a printer. Printer location - Determine the physical location of a printer. Local system configuration - Determine various aspects of the current configuration of the local system involved with the operation of a printer. These "tasks" cover a large spectrum of requirements surrounding the operation of a printer in a network environment. This list serves as the basis for defining the various Role Models described below. Proposed Role Models Following is the list of "Role Models" used to evaluate the requirements for any given Printer MIB object. Note that the keyword enclosed in parentheses represents an abbreviation for the particular Role Model in the matrix described later in this document. User (USER) - A person or application that submits print jobs to the printer; typically viewed as the "end user" within the overall printing environment.
Operator (OP) - A person responsible for maintaining a printer on a day-to-day basis, including such tasks as filling empty media trays, emptying full output trays, replacing toner cartridges, clearing simple paper jams, etc. Technician (TECH) - A person responsible for repairing a malfunctioning printer, performing routine preventive maintenance, and other tasks that typically require advanced training on the printer internals. An example of a "technician" would be a manufacturer's Field Service representative, or other person formally trained by the manufacturer or similar representative. System Manager (MGR) - A person responsible for configuration and troubleshooting of components involved in the overall printing environment, including printers, print queues and network connectivity issues. This person is typically responsible for ensuring the overall operational integrity of the print system components, and is typically viewed as the central point of coordination among all other Role Models. Help Desk (HELP) - A person responsible for supporting Users in their printing needs, including training Users and troubleshooting Users' printing problems. Asset Manager (AM) - A person responsible for managing an organization's printing system assets (primarily printers). Such a person needs to be able to identify and track the location of printing assets on an ongoing basis. Capacity Planner (CP) - A person responsible for tracking the usage of printing resources on an ongoing basis for the purpose of planning printer acquisitions and/or placement of printers based on usage trends. Installer (INST) - A person or application responsible for installing or configuring printing system components on a local system. Accountant (ACCT) - A person responsible for tracking the usage of printing resources on an ongoing basis for the purpose of charging Users for resources used. Matrix of Common Print System Tasks and Role Models To better understand the relationship between the set of defined "Common Print System Tasks" and the various "Role Models," the following matrix is provided.
It is important to recognize that many of the tasks will appear to be applicable to many of the Role Models. However, when considering the actual context of a task, it is very important to realize that often the actual context of a task is such that the Role Model can change. For example, it is obvious that a "System Manager" must be able to submit print jobs to a printer; however, when submitting a print job, a person identified as a "System Manager" is actually operating in the context of a "User" in this case; hence, the requirement to submit a print job is not listed as a requirement for a System Manager. Conversely, while a "User" must be able to remove a job previously submitted to a printer, an "Operator" is often expected to be able to remove any print job from any printer; hence, print job removal is a (subtly different) requirement for both the "User" and "Operator" Role Models. Role Models ----------- Requirement Area USER OP TECH MGR HELP AM CP INST ACCT Print job status xx xx xx xx xx Printer capabilities xx xx xx Print job submission xx Print job removal xx xx Notification of events xx xx Printer configuration xx xx Printer consumables xx xx xx Print job identification xx xx xx xx xx Internal printer status xx xx xx Printer identification xx xx xx xx xx xx xx Printer location xx Local system configuration xx xx Appendix E - Overall Printer Status Table The Status Table establishes a convention for the top 25 printer errors. The table defines a suggested relationship between various printer states and the variables Printer hrDeviceStatus, hrPrinterStatus, hrPrinterDetectedErrorState, prtAlertGroup, prtAlertCode and various sub-unit status variables (prtInputStatus, prtOutputStatus, prtMarkerStatus, prtMediaPathStatus and prtChannelStatus). This table is the recommended implementation of these variables. It is provided to guide implementors of this MIB and users of the MIB by providing a sample set of states and the variable values that are expected to be produced as result of that state. This information supplements that provided in Section
18.104.22.168 "Overall Printer Status". This is not an exhaustive list rather it is a guideline. The definition of PrtSubUnitStatusTC specifies that SubUnitStatus is an integer that is the sum of 5 distinct values/states: Availability, Critical, Non-Critical, On-line and Transitioning. Thus when a non- critical alert or alerts are present the values for Availability, On-Line and Transitioning will be summed with the Non- Critical Alerts (8) value. The table was generated in landscape format and is located at ftp://ftp.pwg.org/pub/pwg/pmp/contributions/Top25Errors.pdf. Appendix F - Participants The Printer MIB Working Group would like to extend a special thank you to the following individuals that put forth a significant effort to review this document and provide numerous suggestions for improvement. David Harrington - Enterasys Networks Juergen Schoenwaelder - TU Braunschweig Bert Wijnen - Lucent Technologies and IETF Op & Mngmt, Area Director This version of the Printer MIB would not be possible without the previous work that resulted in RFC 1759. The authors of the Printer MIB version 2 would like to acknowledge the following individuals for their efforts in developing the base for this document. A special recognition is also extended to Steve Waldbusser, who provided significant technical guidance in the development of the architecture of the Printer MIB. Joel Gyllenskog - Microworks Tom Hastings - Xerox Jay Martin - Underscore, Inc. Ron Smith - Texas Instruments Steve Waldbusser - Lucent Technologies Don Wright - Lexmark Steve Zilles - Adobe The following people attended at least one meeting of the Printer MIB Working Group for version 2; many attended most meetings. Ron Bergman - Hitachi Printing Solutions Luis Cubero - Hewlett-Packard Jay Cummings - Novell Andy Davidson - Tektronix Lee Farrell - Canon
Tom Hastings - Xerox Scott Isaacson - Novell Binnur Al-Kazily - Hewlett-Packard Rick Landau - Digital Equipment Corporation David Kellerman - Northlake Software Harry Lewis - IBM Pete Loya - Hewlett-Packard Jay Martin - Underscore, Inc. Bob Pentecost - Hewlett-Packard Dave Roach - Unisys Stuart Rowley - Kyocera Bob Setterbo - Adobe Mike Timperman - Lexmark Randy Turner - 2Wire, Inc. Bill Wagner - NETsilicon, Inc. Chris Wellens - Interworking Labs Craig Whittle - Sharp Labs Don Wright - Lexmark Lloyd Young - Lexmark Atsushi Yuki - Kyocera Steve Zilles - Adobe
Significant Contributors Ray Casterline Lighthouse Solutions, LLC Phone: (716) 218-9910 EMail: RayCasterline@lhsolutions.com Gary Gocek Phone: (585) 223-3826 EMail: email@example.com Thomas N. Hastings Xerox Corporation Phone: (310) 333-6413 EMail: firstname.lastname@example.org Scott Isaacson Novell Phone: (801) 861-7366 EMail: email@example.com Binnur Al-Kazily Hewlett-Packard, Inc. Phone: (208) 396-6372 EMail: firstname.lastname@example.org David Kellerman Northlake Software Phone: (503) 228-3383 EMail: email@example.com Matt King Lexmark International Phone: (859) 232-6907 EMail: firstname.lastname@example.org Jay Martin Underscore, Inc. Phone: (603) 889-7000 EMail: email@example.com
Mike McKay Novell, Inc. Bob Pentecost Hewlett-Packard Phone: (208) 396-3312 EMail: firstname.lastname@example.org Stuart Rowley Kyocera Phone: (510) 299-7206 EMail: email@example.com Gail Songer Peerless Systems Networking Phone: (650) 569-4414 EMail: firstname.lastname@example.org Randy Turner 2Wire, Inc. Phone (408) 895-1216 EMail: email@example.com William Wagner NETsilicon, Inc. Phone: (781) 398-4588 EMail: WWagner@NetSilicon.com Chris Wellens Interworking Labs Phone: (408) 685-3190 EMail: firstname.lastname@example.org F.D. Wright Lexmark International Phone: (859) 232-4808 EMail: email@example.com
Lloyd Young Lexmark International Phone: (859) 232-5150 EMail: firstname.lastname@example.org Stephen N. Zilles Adobe Systems, Inc. Phone: (415) 962-4766 EMail: email@example.com Authors' Addresses Ron Bergman (Chairman) Hitachi Printing Solutions America 2635 Park Center Drive Simi Valley, CA 93065-6209 Phone: (805) 578-4421 EMail: Ron.Bergman@hitachi-ps.us Harry Lewis IBM 6300 Diagonal Hwy. Boulder, CO 80301 Phone (303) 924-5337 EMail: firstname.lastname@example.org Ira McDonald High North Inc P.O. Box 221 Grand Marais, MI 49839 Phone: (906) 494-2434 or (906) 494-2697 EMail: email@example.com
Full Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- firstname.lastname@example.org. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.