1 IANA-PRINTER-MIB DEFINITIONS ::= BEGIN
\r
2 -- http://www.iana.org/assignments/ianaprinter-mib
\r
7 FROM SNMPv2-SMI -- [RFC2578]
\r
9 FROM SNMPv2-TC; -- [RFC2579]
\r
11 ianaPrinterMIB MODULE-IDENTITY
\r
12 LAST-UPDATED "200509140000Z" -- September 14, 2005
\r
15 CONTACT-INFO "Internet Assigned Numbers Authority
\r
17 4676 Admiralty Way, Suite 330
\r
18 Marina del Rey, CA 90292
\r
20 Tel: +1 310 823 9358
\r
21 E-Mail: iana&iana.org"
\r
23 DESCRIPTION "This MIB module defines a set of printing-related
\r
24 TEXTUAL-CONVENTIONs for use in Printer MIB (RFC 3805),
\r
25 Finisher MIB (RFC 3806), and other MIBs which need to
\r
26 specify printing mechanism details.
\r
28 Any additions or changes to the contents of this MIB
\r
29 module require either publication of an RFC, or
\r
30 Designated Expert Review as defined in RFC 2434,
\r
31 Guidelines for Writing an IANA Considerations Section
\r
32 in RFCs. The Designated Expert will be selected by
\r
33 the IESG Area Director(s) of the Applications Area.
\r
35 Copyright (C) The Internet Society (2004). The
\r
36 initial version of this MIB module was published
\r
37 in RFC 3805. For full legal notices see the RFC
\r
39 http://www.ietf.org/copyrights/ianamib.html"
\r
41 REVISION "200509140000Z" -- September 14, 2005
\r
42 DESCRIPTION "Updates to include missing 'unknown' values
\r
43 for PrtCoverStatusTC, PrtChannelTypeTC,
\r
44 PrtAlertGroupTC and removal of comment for
\r
45 for PrtAlertGroupTC."
\r
47 REVISION "200406020000Z" -- June 2, 2004
\r
48 DESCRIPTION "Original version, published in coordination
\r
49 with Printer MIB (RFC 3805)."
\r
53 -- Generic TEXTUAL-CONVENTIONs
\r
56 PrtCoverStatusTC ::= TEXTUAL-CONVENTION
\r
57 -- This TC was extracted from prtCoverStatus in RFC 1759.
\r
60 "Values for encoding the state of a particular cover or
\r
61 access panel on the printer case or enclosure."
\r
73 -- General Group TEXTUAL-CONVENTIONs
\r
76 PrtGeneralResetTC ::= TEXTUAL-CONVENTION
\r
77 -- This TC was extracted from prtGeneralReset in RFC 1759.
\r
80 "Values for reading and writing the prtGeneralReset object.
\r
82 If a device does not have NVRAM, the device shall none the
\r
83 less respond to a SET with the value resetToNVRAM(5) with a
\r
84 sort of warm reset that resets the device to implementation-
\r
85 defined state that is preferably under control of the system
\r
86 administrator by some means outside the scope of the Printer
\r
91 powerCycleReset(4), -- Cold Start
\r
92 resetToNVRAM(5), -- Warm Start
\r
93 resetToFactoryDefaults(6) -- Reset contents of
\r
98 -- Channel Group TEXTUAL-CONVENTIONs
\r
101 PrtChannelTypeTC ::= TEXTUAL-CONVENTION
\r
102 -- This TC was extracted from prtChannelType in RFC 1759.
\r
105 "This enumeration indicates the type of channel that is
\r
115 -- AppleTalk Printer
\r
116 -- Access Protocol (PAP)
\r
118 -- prtChannelInformation entry:
\r
124 -- Status: Optional
\r
125 -- Multiplicity: Single
\r
126 -- Description: The name of the printer
\r
127 -- within the AppleTalk naming scope
\r
129 -- prtChannelInformation entry:
\r
131 -- Printer queue name
\r
134 -- Status: Mandatory
\r
135 -- Multiplicity: Single
\r
136 -- Description: queue name as
\r
137 -- defined in [RFC1179].
\r
138 chNetwareRPrinter(9),
\r
140 -- For each entry of this type, the
\r
141 -- prtChannelInformation must have a pair of
\r
142 -- keywords. For Netware 3.x channels this must
\r
143 -- be a (PServer, Printer) pair. For Netware
\r
144 -- 4.x channels and for IntranetWare channels
\r
145 -- this must be a (NDSTree, NDSPrinter) pair.
\r
147 -- prtChannelInformation entries:
\r
149 -- Print Server Name
\r
150 -- Keyword: PServer
\r
152 -- Status: Mandatory
\r
153 -- Multiplicity: Single
\r
154 -- Description: The Pserver's SAP name
\r
157 -- Keyword: Printer
\r
159 -- Status: Mandatory
\r
160 -- Multiplicity: Single
\r
161 -- Description: The printer number
\r
164 -- Keyword: NDSTree
\r
166 -- Multiplicity: Single
\r
167 -- Description: The tree's SAP name
\r
170 -- NDS Printer object
\r
171 -- Keyword: NDSPrinter
\r
172 -- Syntax: Text (Unicode)
\r
173 -- Status: Mandatory
\r
174 -- Multiplicity: Single
\r
175 -- Description: The fully qualified
\r
176 -- name of the Printer
\r
178 -- In the Netware 3.x environment, the
\r
179 -- client checks the Bindery object
\r
180 -- representing the named PServer. The
\r
181 -- client then checks for queues which
\r
182 -- are associated with the numbered
\r
183 -- printer. In the 4.x and IntraNetware
\r
184 -- environment, the client looks up the
\r
185 -- queues which are associated with the
\r
186 -- NDS Printer Object in the named Tree.
\r
187 -- Depending on client access rights to
\r
188 -- those queues, the client submits jobs
\r
189 -- to the appropriate queue.
\r
190 chNetwarePServer(10),
\r
192 -- For each entry of this type, the
\r
193 -- prtChannelInformation must have a pair
\r
194 -- of keywords. For Netware 3.x channels
\r
195 -- this must be a (Server, PServer) pair.
\r
196 -- For Netware 4.x and IntranetWare
\r
197 -- channels, this must be a
\r
198 -- (NDSTree, NDSPServer) pair.
\r
200 -- prtChannelInformation entries:
\r
205 -- Status: Mandatory
\r
206 -- Multiplicity: Single
\r
207 -- Description: The SAP name of the
\r
208 -- server for which the PServer is defined.
\r
211 -- Keyword: PServer
\r
213 -- Status: Mandatory
\r
214 -- Multiplicity: Single
\r
215 -- Description: The bindery name of
\r
220 -- Keyword: NDSTree
\r
222 -- Status: Mandatory
\r
223 -- Multiplicity: Single
\r
224 -- Description: The NDS Tree name
\r
227 -- Keyword: NDSPServer
\r
228 -- Syntax: Text (Unicode)
\r
229 -- Status: Mandatory
\r
230 -- Multiplicity: Single
\r
231 -- Description: The fully qualified
\r
232 -- name of the PServer object in the tree.
\r
234 -- In the 3.x environment, the client
\r
235 -- checks the bindery object
\r
236 -- representing the named PServer on the
\r
237 -- named Server. In the 4.x and
\r
238 -- IntranetWare environment,
\r
239 -- the client checks the NDS object
\r
240 -- representing the named PServer in the
\r
241 -- named Tree. In either case, the
\r
242 -- client then checks for all queues
\r
243 -- associated with the Pserver object.
\r
244 -- Depending on client access rights
\r
245 -- to those queues, the client submits
\r
246 -- jobs to the appropriate queue.
\r
249 -- (see chPortTCP - 37; chBidirPortTCP - 38)
\r
251 -- A bi-directional, LPD-like, protocol using
\r
252 -- 9101 for control and 9100 for data.
\r
253 -- Adobe Systems, Inc.
\r
254 chFTP(13), -- [RFC959]
\r
255 chTFTP(14), -- [RFC1350]
\r
257 chIBM3270(16), -- IBM Coax
\r
258 chIBM5250(17), -- IBM Twinax
\r
262 -- TCP port 35, for reserved TCP port list see
\r
263 -- [RFC3232]. This RFC should also be
\r
264 -- referenced for other channel
\r
265 -- enumerations utilizing TCP port
\r
267 -- numbers 0 through 1024.
\r
268 chCPAP(21), -- TCP port 170
\r
269 -- Digital Equipment Corp.
\r
270 chDCERemoteProcCall(22), -- OSF
\r
272 chONCRemoteProcCall(23), -- SUN Microsystems
\r
274 chOLE(24), -- Microsoft
\r
277 chPCPrint(26), -- Banyan
\r
278 chServerMessageBlock(27),
\r
279 -- File/Print sharing protocol used by
\r
280 -- various network operating systems
\r
281 -- from IBM 3Com, Microsoft and others
\r
283 -- prtChannelInformation entry:
\r
288 -- Status: Optional
\r
289 -- Multiplicity: Single
\r
290 -- Description: The service name of
\r
292 chDPMF(28), -- IBM Infoprint
\r
293 chDLLAPI(29), -- Microsoft
\r
295 chVxDAPI(30), -- Microsoft
\r
297 chSystemObjectManager(31), -- IBM
\r
299 -- Digital Equipment Corp.
\r
301 -- prtChannelInformation entries:
\r
306 -- Status: Conditionally
\r
308 -- (see note below)
\r
309 -- Multiplicity: Single
\r
310 -- Description: LAT port name
\r
313 -- Keyword: Service
\r
316 -- Status: Conditionally
\r
318 -- Multiplicity: Single
\r
319 -- Description: LAT service name
\r
321 -- The LAT channel may be
\r
322 -- identified by either a port or
\r
323 -- service, so either a
\r
324 -- Port or Service entry must be
\r
325 -- specified, but not both.
\r
327 chUSB(34), -- Not in RFC 1759
\r
328 -- Universal Serial Bus
\r
329 chIRDA(35), -- Not in RFC 1759
\r
330 -- Infrared Data Assoc. Prot.
\r
331 chPrintXChange(36), -- Not in RFC 1759
\r
332 -- PrintXChange Protocol
\r
333 chPortTCP(37), -- Not in RFC 1759
\r
334 -- A unidirectional "raw" TCP
\r
335 -- channel that uses an administratively
\r
336 -- assigned TCP port address.
\r
338 -- prtChannelInformation entry:
\r
342 -- Syntax: decimal number
\r
343 -- Status: Mandatory
\r
344 -- Multiplicity: Single
\r
345 -- Description: TCP port number
\r
346 chBidirPortTCP(38), -- Not in RFC 1759
\r
347 -- A bi-directional version of chPortTCP
\r
349 -- prtChannelInformation entries:
\r
351 chUNPP(39), -- Not in RFC 1759
\r
352 -- Universal Network Printing
\r
353 -- Protocol(UNPP). A bi-directional,
\r
354 -- multiport network printing
\r
355 -- application protocol available on
\r
356 -- multiple transport protocols.
\r
357 -- Underscore, Inc.
\r
358 -- Contact: info&underscore.com
\r
359 chAppleTalkADSP(40), -- Not in RFC 1759
\r
360 -- AppleTalk Data Stream Protocol.
\r
361 -- ADSP is part of the AppleTalk
\r
362 -- suite of protocols.
\r
363 -- It is a symmetric, connection-
\r
365 -- oriented protocol that makes
\r
366 -- possible the establishment
\r
367 -- and maintenance of full-duplex
\r
368 -- streams of data bytes between
\r
369 -- two sockets in an AppleTalk
\r
372 chPortSPX(41), -- Not in RFC 1759
\r
373 -- Sequenced Packet Exchange (SPX)
\r
375 -- Novell, Inc. Similar to TCP, a
\r
376 -- bi-directional data pipe using
\r
377 -- Novell SPX as a transport.
\r
379 -- prtChannelInformation entries:
\r
383 -- Syntax: HexString
\r
384 -- Status: Mandatory
\r
385 -- Multiplicity: Single
\r
386 -- Description: The network number
\r
390 -- Syntax: HexString
\r
391 -- Status: Mandatory
\r
392 -- Multiplicity: Single
\r
393 -- Description: The node number
\r
397 -- Syntax: HexString
\r
398 -- Status: Mandatory
\r
399 -- Multiplicity: Single
\r
400 -- Description: The SPX socket number
\r
402 -- There must be exactly one "Net" and
\r
403 -- one "Node" and one "Socket" entry. A
\r
404 -- HexString is a binary value
\r
405 -- represented as a string of
\r
406 -- ASCII characters using hexadecimal
\r
408 chPortHTTP(42), -- Not in RFC 1759
\r
409 -- Hypertext Transfer Protocol. See [RFC1945]
\r
411 chNDPS(43), -- Not in RFC 1759
\r
415 -- prtChannelInformation entry:
\r
417 -- Printer Agent Name
\r
420 -- Status: Mandatory
\r
421 -- Multiplicity: Single
\r
422 -- Description: The NDPS Printer
\r
424 chIPP(44), -- Not in RFC 1759
\r
425 -- Internet Printing Protocol (IPP),
\r
426 -- (IPP/1.1 - see [RFC2910] and [RFC2911])
\r
427 -- also applies to all future versions of IPP.
\r
431 -- Syntax: URI (Unicode UTF-8 per
\r
433 -- Status: Mandatory
\r
434 -- Multiplicity: Single
\r
435 -- Default: not applicable
\r
436 -- Description: URI of this IPP Printer
\r
437 -- within Internet naming scope. Unicode
\r
438 -- UTF-8 [RFC3629] string with
\r
439 -- hexadecimal escapes for any non-ASCII
\r
440 -- characters (per [RFC2396]).
\r
441 -- Conformance: An IPP Printer shall list all
\r
442 -- IPP URI it supports (one per IPP Channel
\r
443 -- entry). If a URI contains the 'http:'
\r
444 -- scheme it must have an explicit port.
\r
445 -- See: [RFC3629], [RFC2396], [RFC2910],
\r
448 -- IPP Printer Client Authentication
\r
451 -- Status: Optional
\r
452 -- Multiplicity: Single
\r
454 -- Description: A client authentication
\r
455 -- mechanism supported for this IPP Printer
\r
458 -- no client authentication mechanism
\r
459 -- 'requesting-user-name'
\r
460 -- authenticated user in 'requesting-
\r
464 -- authenticated user via HTTP Basic
\r
467 -- authenticated user via HTTP Digest
\r
470 -- authenticated user via certificate
\r
472 -- Conformance: An IPP Printer should list
\r
473 -- all IPP client authentication mechanisms
\r
474 -- it supports (one per IPP Channel entry).
\r
475 -- See: [RFC2911] and [RFC2910].
\r
477 -- IPP Printer Security
\r
478 -- Keyword: Security
\r
480 -- Status: Optional
\r
481 -- Multiplicity: Single
\r
483 -- Description: A security mechanism
\r
484 -- supported for this IPP Printer URI:
\r
486 -- no security mechanism
\r
488 -- SSL3 secure communications channel
\r
491 -- TLS secure communications channel
\r
493 -- Conformance: An IPP Printer should list
\r
494 -- all IPP security mechanisms it supports
\r
495 -- (one per IPP Channel entry).
\r
496 -- See: [RFC2246], [RFC2911].
\r
498 -- IPP Printer Protocol Version
\r
499 -- Keyword: Version
\r
501 -- Status: Optional
\r
502 -- Multiplicity: Multiple
\r
504 -- Description: All of the IPP protocol
\r
505 -- versions (major.minor) supported for
\r
506 -- this IPP Printer URI:
\r
508 -- IPP/1.0 conforming Printer
\r
510 -- IPP/1.1 conforming Printer
\r
512 -- Conformance: An IPP Printer should list
\r
513 -- all IPP versions it supports (all listed
\r
514 -- in each IPP Channel entry). An IPP
\r
515 -- Client should select the highest
\r
516 -- numbered version the IPP Client supports
\r
517 -- for use in all IPP Requests (for optimum
\r
521 -- Print Job submission via Simple Mail
\r
522 -- Transfer Protocol (SMTP) - see [RFC2821]
\r
524 -- prtChannelInformation entry:
\r
528 -- Status: Mandatory
\r
529 -- Multiplicity: Single
\r
530 -- Default: not applicable
\r
531 -- Description: The SMTP URL of the printer.
\r
535 -- Interpreter Group TEXTUAL-CONVENTIONs
\r
538 PrtInterpreterLangFamilyTC ::= TEXTUAL-CONVENTION
\r
539 -- This TC was extracted from prtInterpreterLangFamily in RFC 1759.
\r
542 "This enumeration indicates the type of interpreter that is
\r
546 unknown(2), -- Not in RFC 1759
\r
547 langPCL(3), -- PCL. Starting with PCL version 5,
\r
548 -- HP-GL/2 is included as part of the
\r
550 -- PCL and HP-GL/2 are registered
\r
551 -- trademarks of Hewlett-Packard
\r
553 langHPGL(4), -- Hewlett-Packard Graphics Language.
\r
554 -- HP-GL is a registered trademark of
\r
555 -- Hewlett-Packard Company.
\r
556 langPJL(5), -- Peripheral Job Language. Appears in
\r
557 -- the data stream between data intended
\r
558 -- for a page description language.
\r
559 -- Hewlett-Packard Co.
\r
561 langPS(6), -- PostScript (tm) Language
\r
562 -- Postscript - a trademark of Adobe
\r
563 -- Systems Incorporated which may be
\r
564 -- registered in certain jurisdictions
\r
565 langIPDS(7), -- Intelligent Printer Data Stream
\r
566 -- Bi-directional print data stream for
\r
567 -- documents consisting of data objects
\r
568 -- (text, image, graphics, bar codes),
\r
569 -- resources (fonts, overlays) and page,
\r
570 -- form and finishing instructions.
\r
571 -- Facilitates system level device
\r
572 -- control, document tracking and error
\r
573 -- recovery throughout the print
\r
575 -- IBM Corporation.
\r
576 langPPDS(8), -- IBM Personal Printer Data Stream.
\r
577 -- Originally called IBM ASCII, the name
\r
578 -- was changed to PPDS when the Laser
\r
579 -- Printer was introduced in 1989.
\r
580 -- Lexmark International, Inc.
\r
581 langEscapeP(9), -- Epson Corp.
\r
583 langDDIF(11), -- Digital Document Interchange Format
\r
584 -- Digital Equipment Corp., Maynard MA
\r
585 langInterpress(12),
\r
587 langISO6429(13), -- ISO 6429. Control functions for
\r
588 -- Coded Character Sets (has ASCII
\r
589 -- control characters, plus additional
\r
591 -- character imaging devices.)
\r
592 langLineData(14), -- line-data: Lines of data as
\r
593 -- separate ASCII or EBCDIC records
\r
594 -- and containing no control functions
\r
595 -- (no CR, LF, HT, FF, etc.)
\r
596 -- For use with traditional line
\r
597 -- printers. May use CR and/or LF to
\r
598 -- delimit lines, instead of records.
\r
599 -- See ISO 10175 Document Printing
\r
600 -- Application (DPA) [ISO10175].
\r
601 langMODCA(15), -- Mixed Object Document Content
\r
603 -- Definitions that allow the
\r
604 -- composition, interchange, and
\r
605 -- presentation of final form
\r
606 -- documents as a collection of data
\r
607 -- objects (text, image, graphics, bar
\r
608 -- codes), resources (fonts, overlays)
\r
610 -- and page, form and finishing
\r
612 -- IBM Corporation.
\r
613 langREGIS(16), -- Remote Graphics Instruction Set,
\r
614 -- Digital Equipment Corp., Maynard MA
\r
615 langSCS(17), -- SNA Character String
\r
616 -- Bi-directional print data stream for
\r
617 -- SNA LU-1 mode of communication.
\r
619 langSPDL(18), -- ISO 10180 Standard Page Description
\r
622 langTEK4014(19), -- Tektronix Corp.
\r
624 langIGP(21), -- Printronix Corp.
\r
625 langCodeV(22), -- Magnum Code-V, Image and printer
\r
626 -- control language used to control
\r
627 -- impact/dot-matrix printers.
\r
628 -- QMS, Inc., Mobile AL
\r
629 langDSCDSE(23), -- DSC-DSE: Data Stream Compatible and
\r
630 -- Emulation Bi-directional print data
\r
631 -- stream for non-SNA (DSC) and SNA LU-3
\r
632 -- 3270 controller (DSE) communications
\r
634 langWPS(24), -- Windows Printing System, Resource
\r
635 -- based command/data stream used by
\r
636 -- Microsoft At Work Peripherals.
\r
637 -- Developed by the Microsoft
\r
639 langLN03(25), -- Early DEC-PPL3, Digital Equipment
\r
642 langQUIC(27), -- QUIC (Quality Information Code), Page
\r
643 -- Description Language for laser
\r
644 -- printers. Included graphics, printer
\r
645 -- control capability and emulation of
\r
646 -- other well-known printer.
\r
648 langCPAP(28), -- Common Printer Access Protocol
\r
649 -- Digital Equipment Corp.
\r
650 langDecPPL(29), -- Digital ANSI-Compliant Printing
\r
653 -- Digital Equipment Corp.
\r
654 langSimpleText(30),
\r
655 -- simple-text: character coded data,
\r
656 -- including NUL, CR , LF, HT, and FF
\r
657 -- control characters. See ISO 10175
\r
659 -- Document Printing Application (DPA)
\r
661 langNPAP(31), -- Network Printer Alliance Protocol
\r
662 -- (NPAP). This protocol has been
\r
663 -- superseded by the IEEE 1284.1 TIPSI
\r
664 -- Std (ref. LangTIPSI(49)).
\r
665 langDOC(32), -- Document Option Commands, Appears in
\r
666 -- the data stream between data
\r
667 -- intended for a page description.
\r
669 langimPress(33), -- imPRESS, Page description language
\r
670 -- originally developed for the
\r
671 -- ImageServer product line. A binary
\r
672 -- language providing representations
\r
673 -- of text, simple graphics, and some
\r
674 -- large forms (simple
\r
675 -- bit-map and CCITT group 3/4
\r
677 -- language was intended to be sent over
\r
678 -- an 8-bit channel and supported early
\r
679 -- document preparation languages (e.g.,
\r
683 -- 24 wire dot matrix printer for
\r
684 -- USA, Europe, and Asia except
\r
686 -- More widely used in Germany, and
\r
687 -- some Asian countries than in US.
\r
689 langNPDL(35), -- Page printer for Japanese market.
\r
691 langNEC201PL(36), -- Serial printer language used in
\r
692 -- the Japanese market.
\r
695 -- Automatic PDL sensing. Automatic
\r
696 -- sensing of the interpreter
\r
697 -- language family by the printer
\r
698 -- examining the document content.
\r
699 -- Which actual interpreter language
\r
700 -- families are sensed depends on
\r
701 -- the printer implementation.
\r
702 langPages(38), -- Page printer Advanced Graphic
\r
705 langLIPS(39), -- LBP Image Processing System
\r
706 langTIFF(40), -- Tagged Image File Format (Aldus)
\r
708 langDiagnostic(41),
\r
709 -- A hex dump of the input to the
\r
712 -- The PostScript Language used for
\r
713 -- control (with any PDLs)
\r
714 -- Adobe Systems Incorporated
\r
715 langCaPSL(43), -- Canon Print Systems Language
\r
716 langEXCL(44), -- Extended Command Language
\r
717 -- Talaris Systems Inc.
\r
718 langLCDS(45), -- Line Conditioned Data Stream
\r
719 -- Xerox Corporation
\r
720 langXES(46), -- Xerox Escape Sequences
\r
721 -- Xerox Corporation
\r
722 langPCLXL(47), -- Not in RFC 1759
\r
723 -- Printer Control Language. Extended
\r
724 -- language features for printing, and
\r
725 -- printer control.
\r
726 -- Hewlett-Packard Co.
\r
727 langART(48), -- Not in RFC 1759
\r
728 -- Advanced Rendering Tools (ART).
\r
729 -- Page Description language
\r
730 -- originally developed for the Laser
\r
732 -- Technical reference manual: "ART IV
\r
733 -- Reference Manual", No F33M.
\r
734 -- Fuji Xerox Co., Ltd.
\r
735 langTIPSI(49), -- Not in RFC 1759
\r
736 -- Transport Independent Printer
\r
737 -- System Interface (ref. IEEE Std.
\r
739 langPrescribe(50), -- Not in RFC 1759
\r
740 -- Page description and printer
\r
741 -- control language. It can be
\r
742 -- described with ordinary ASCII
\r
743 -- Technical reference manual:
\r
744 -- "PRESCRIBE II Programming Manual"
\r
745 langLinePrinter(51), -- Not in RFC 1759
\r
746 -- A simple-text character stream which
\r
747 -- supports the control codes LF, VT,
\r
748 -- FF, and plus Centronics or
\r
749 -- Dataproducts Vertical Format Unit
\r
750 -- (VFU) language is commonly used on
\r
751 -- many older model line and matrix
\r
753 langIDP(52), -- Not in RFC 1759
\r
754 -- Imaging Device Protocol
\r
757 langXJCL(53), -- Not in RFC 1759
\r
758 -- Xerox Job Control Language (JCL).
\r
759 -- A Job Control language originally
\r
760 -- developed for the LaserPress printers
\r
761 -- and is capable of switching PDLs.
\r
762 -- Technical reference manual:
\r
763 -- "ART IV Reference Manual", No F33M.
\r
764 -- Fuji Xerox Co., Ltd.
\r
765 langPDF(54), -- Not in RFC 1759
\r
766 -- Adobe Portable Document Format
\r
767 -- Adobe Systems, Inc.
\r
768 langRPDL(55), -- Not in RFC 1759
\r
769 -- Ricoh Page Description Language for
\r
771 -- Technical manual "RPDL command
\r
772 -- reference" No.307029
\r
774 langIntermecIPL(56), -- Not in RFC 1759
\r
775 -- Intermec Printer Language for label
\r
777 -- Technical Manual: "IPL Programmers
\r
778 -- Reference Manual"
\r
779 -- Intermec Corporation
\r
780 langUBIFingerprint(57), -- Not in RFC 1759
\r
781 -- An intelligent basic-like programming
\r
782 -- language for label printers.
\r
783 -- Reference Manual: "UBI Fingerprint
\r
784 -- 7.1", No. 1-960434-00
\r
785 -- United Barcode Industries
\r
786 langUBIDirectProtocol(58), -- Not in RFC 1759
\r
787 -- An intelligent control language for
\r
789 -- Programmers guide: " UBI Direct
\r
790 -- Protocol", No. 1-960419-00
\r
791 -- United Barcode Industries
\r
792 langFujitsu(59), -- Not in RFC 1759
\r
793 -- Fujitsu Printer Language
\r
794 -- Reference Manual:
\r
795 -- "FM Printer Sequence" No. 80HP-0770
\r
797 langCGM(60), -- Not in RFC 1759
\r
798 -- Computer Graphics Metafile
\r
799 -- MIME type 'image/cgm'
\r
800 langJPEG(61), -- Not in RFC 1759
\r
801 -- Joint Photographic Experts Group
\r
802 -- MIME type 'image/jpeg'
\r
803 langCALS1(62), -- Not in RFC 1759
\r
804 -- US DOD CALS1 (see MIL-STD-1840)
\r
806 -- MIME type 'application/cals-1840'
\r
807 langCALS2(63), -- Not in RFC 1759
\r
808 -- US DOD CALS2 (see MIL-STD-1840)
\r
809 -- MIME type 'application/cals-1840'
\r
810 langNIRS(64), -- Not in RFC 1759
\r
811 -- US DOD NIRS (see MIL-STD-1840)
\r
812 -- MIME type 'application/cals-1840'
\r
813 langC4(65) -- Not in RFC 1759
\r
814 -- US DOD C4 (see MIL-STD-1840)
\r
815 -- MIME type 'application/cals-1840'
\r
819 -- Input/Output Group TEXTUAL-CONVENTIONs
\r
822 PrtInputTypeTC ::= TEXTUAL-CONVENTION
\r
823 -- This TC was extracted from prtInputType in RFC 1759.
\r
826 "The type of technology (discriminated primarily according to
\r
827 feeder mechanism type) employed by a specific component or
\r
832 sheetFeedAutoRemovableTray(3),
\r
833 sheetFeedAutoNonRemovableTray(4),
\r
834 sheetFeedManual(5),
\r
836 continuousFanFold(7)
\r
839 PrtOutputTypeTC ::= TEXTUAL-CONVENTION
\r
840 -- This TC was extracted from prtOutputType in RFC 1759.
\r
843 "The Type of technology supported by this output subunit."
\r
849 continuousRollDevice(5),
\r
851 continuousFanFold(7)
\r
855 -- Marker Group TEXTUAL-CONVENTIONs
\r
858 PrtMarkerMarkTechTC ::= TEXTUAL-CONVENTION
\r
859 -- This TC was extracted from prtMarkerMarkTech in RFC 1759.
\r
862 "The type of marking technology used for this marking
\r
867 electrophotographicLED(3),
\r
868 electrophotographicLaser(4),
\r
869 electrophotographicOther(5),
\r
870 impactMovingHeadDotMatrix9pin(6),
\r
871 impactMovingHeadDotMatrix24pin(7),
\r
872 impactMovingHeadDotMatrixOther(8),
\r
873 impactMovingHeadFullyFormed(9),
\r
880 thermalTransfer(16),
\r
881 thermalSensitive(17),
\r
882 thermalDiffusion(18),
\r
884 electroerosion(20),
\r
886 photographicMicrofiche(22),
\r
887 photographicImagesetter(23),
\r
888 photographicOther(24),
\r
894 PrtMarkerSuppliesTypeTC ::= TEXTUAL-CONVENTION
\r
895 -- This TC was extracted from prtMarkerSuppliesType in RFC 1759.
\r
898 "The type of this supply."
\r
903 -- Values for Printer MIB
\r
910 opc(9), -- photo conductor
\r
916 fuser(15), -- Not in RFC 1759
\r
917 coronaWire(16), -- Not in RFC 1759
\r
918 fuserOilWick(17), -- Not in RFC 1759
\r
919 cleanerUnit(18), -- Not in RFC 1759
\r
920 fuserCleaningPad(19), -- Not in RFC 1759
\r
921 transferUnit(20), -- Not in RFC 1759
\r
922 tonerCartridge(21), -- Not in RFC 1759
\r
923 fuserOiler(22), -- Not in RFC 1759
\r
924 -- End of values for Printer MIB
\r
925 -- Values for Finisher MIB
\r
926 water(23), -- Not in RFC 1759
\r
927 wasteWater(24), -- Not in RFC 1759
\r
928 glueWaterAdditive(25),-- Not in RFC 1759
\r
929 wastePaper(26), -- Not in RFC 1759
\r
930 bindingSupply(27), -- Not in RFC 1759
\r
931 bandingSupply(28), -- Not in RFC 1759
\r
932 stitchingWire(29), -- Not in RFC 1759
\r
933 shrinkWrap(30), -- Not in RFC 1759
\r
934 paperWrap(31), -- Not in RFC 1759
\r
935 staples(32), -- Not in RFC 1759
\r
936 inserts(33), -- Not in RFC 1759
\r
937 covers(34) -- Not in RFC 1759
\r
938 -- End of values for Finisher MIB
\r
942 -- Media Path TEXTUAL-CONVENTIONs
\r
945 PrtMediaPathTypeTC ::= TEXTUAL-CONVENTION
\r
946 -- This TC was extracted from prtMediaPathType in RFC 1759.
\r
949 "The type of the media path for this media path."
\r
954 longEdgeBindingDuplex(3),
\r
955 shortEdgeBindingDuplex(4),
\r
960 -- Console Group TEXTUAL-CONVENTIONs
\r
963 PrtConsoleColorTC ::= TEXTUAL-CONVENTION
\r
964 -- This TC was extracted from prtConsoleColor in RFC 1759.
\r
967 "The color of this light."
\r
978 orange(10) -- Not in RFC 1759
\r
981 PrtConsoleDisableTC ::= TEXTUAL-CONVENTION
\r
982 -- This TC was extracted from prtConsoleDisable in RFC 1759.
\r
985 "This value indicates whether or not input is accepted from
\r
986 the operator console. A value of 'enabled' indicates that
\r
987 input is accepted from the console, and a value of 'disabled'
\r
988 indicates that input is not accepted from the console. "
\r
995 -- Alert Group TEXTUAL-CONVENTIONs
\r
998 PrtAlertTrainingLevelTC ::= TEXTUAL-CONVENTION
\r
999 -- This TC was extracted from prtAlertTrainingLevel in RFC 1759.
\r
1003 "The level of training required to handle this alert, if
\r
1004 human intervention is required. The noInterventionRequired
\r
1005 value should be used if the event does not require any human
\r
1006 intervention. The training level is an enumeration that is
\r
1007 determined and assigned by the printer manufacturer based on
\r
1008 the information or training required to handle this alert.
\r
1009 The printer will break alerts into these different training
\r
1010 levels. It is the responsibility of a management application
\r
1011 in the system to determine how a particular alert is handled
\r
1012 and how and to whom that alert is routed. The following are
\r
1013 the four training levels of alerts:
\r
1015 Field Service - Alerts that typically require advanced
\r
1016 training and technical knowledge of the printer and its
\r
1017 subunits. An example of a technical person would be a
\r
1018 manufacturer's Field Service representative, or other
\r
1019 person formally trained by the manufacturer or similar
\r
1021 Trained - Alerts that require an intermediate or moderate
\r
1022 knowledge of the printer and its subunits. A typical
\r
1023 example of such an alert is replacing a toner cartridge.
\r
1024 Untrained - Alerts that can be fixed without prior
\r
1025 training either because the action to correct the alert
\r
1026 is obvious or the printer can help the untrained person
\r
1027 fix the problem. A typical example of such an alert is
\r
1028 reloading paper trays or emptying output bins on a low
\r
1030 Management - Alerts that have to do with overall operation
\r
1031 of and configuration of the printer. Examples of such
\r
1032 management events are configuration change of subunits."
\r
1040 noInterventionRequired(7) -- Not in RFC 1759
\r
1043 PrtAlertGroupTC ::= TEXTUAL-CONVENTION
\r
1044 -- Values in the range 1 to 29 must not be IANA-assigned without
\r
1045 -- re-publishing Printer MIB.
\r
1046 -- Values of 30 and greater are for use in MIBs that augment
\r
1047 -- the Printer MIB, such as the Finisher MIB.
\r
1048 -- This TC extracted from prtAlertGroup in RFC 1759.
\r
1052 "The type of subunit within the printer model that this alert
\r
1053 is related. Input, output, and markers are examples of
\r
1054 printer model groups, i.e., examples of types of subunits.
\r
1055 Wherever possible, the enumerations match the sub-identifier
\r
1056 that identifies the relevant table in the Printer MIB.
\r
1058 NOTE: Alert type codes have been added for the Host Resources
\r
1059 MIB storage table and device table. These additional types
\r
1060 are for situations in which the printer's storage and device
\r
1061 objects must generate alerts (and possibly traps for critical
\r
1066 -- Values for Host Resources MIB
\r
1067 hostResourcesMIBStorageTable(3),
\r
1068 hostResourcesMIBDeviceTable(4),
\r
1069 -- Values for Printer MIB
\r
1070 generalPrinter(5),
\r
1076 markerSupplies(11),
\r
1077 markerColorant(12),
\r
1081 consoleDisplayBuffer(16),
\r
1082 consoleLights(17),
\r
1083 alert(18), -- Not in RFC 1759
\r
1084 -- Values (5) to (29) reserved for Printer MIB
\r
1085 -- Values for Finisher MIB
\r
1086 finDevice(30), -- Not in RFC 1759
\r
1087 finSupply(31), -- Not in RFC 1759
\r
1088 finSupplyMediaInput(32), -- Not in RFC 1759
\r
1089 finAttribute(33) -- Not in RFC 1759
\r
1090 -- Values (30) to (39) reserved for Finisher MIB
\r
1093 PrtAlertCodeTC ::= TEXTUAL-CONVENTION
\r
1094 -- This TC was extracted from prtAlertCode in RFC 1759.
\r
1097 "The code that describes the type of alert for this entry in
\r
1099 the table. Binary change event alerts describe states of the
\r
1100 subunit while unary change event alerts describe a single
\r
1101 event. The same alert code can be used for a binary change
\r
1102 event or a unary change event, depending on implementation.
\r
1103 Also, the same alert code can be used to indicate a critical
\r
1104 or non-critical (warning) alert, depending on implementation.
\r
1105 The value of prtAlertSeverityLevel specifies binary vs. unary
\r
1106 and critical vs. non-critical for each event for the
\r
1109 While there are some specific codes for many subunits, the
\r
1110 generic codes should be used for most subunit alerts. The
\r
1111 network management station can then query the subunit
\r
1112 specified by prtAlertGroup to determine further subunit
\r
1113 status and other subunit information.
\r
1115 An agent shall not add two entries to the alert table for the
\r
1116 same event, one containing a generic event code and the other
\r
1117 containing a specific event code; the agent shall add only
\r
1118 one entry in the alert table for each event; either generic
\r
1119 (preferred) or specific, not both.
\r
1121 Implementation of the unary change event
\r
1122 alertRemovalOfBinaryChangeEntry(1801) is optional. When
\r
1123 implemented, this alert code shall indicate to network
\r
1124 management stations that the trailing edge of a binary change
\r
1125 event has occurred and the corresponding alert entry has been
\r
1126 removed from the alert table. As with all events, the
\r
1127 alertRemovalOfBinaryChangeEntry(1801) alert shall be placed
\r
1128 at the end of the alert table. Such an alert table entry
\r
1129 shall specify the following information:
\r
1131 prtAlertSeverityLevel warningUnaryChangeEvent(4)
\r
1132 prtAlertTrainingLevel noInterventionRequired(7)
\r
1133 prtAlertGroup alert(18)
\r
1134 prtAlertGroupIndex the index of the row in the
\r
1135 alert table of the binary
\r
1136 change event that this event
\r
1138 prtAlertLocation unknown (-2)
\r
1139 prtAlertCode alertRemovalOfBinaryChangeEntry(1801)
\r
1140 prtAlertDescription <description or null string>
\r
1141 prtAlertTime the value of sysUpTime at
\r
1142 the time of the removal of the
\r
1143 binary change event from the
\r
1146 Optionally, the agent may generate a trap coincident with
\r
1148 removing the binary change event and placing the unary change
\r
1149 event alertRemovalOfBinaryChangeEntry(1801) in the alert
\r
1150 table. For such a trap, the prtAlertIndex sent with the above
\r
1151 trap parameters shall be the index of the
\r
1152 alertRemovalOfBinaryChangeEvent row that was added to the
\r
1153 prtAlertTable; not the index of the row that was removed from
\r
1154 the prtAlertTable."
\r
1157 -- an event that is not represented
\r
1158 -- by one of the alert codes
\r
1159 -- specified below.
\r
1161 -- The following generic codes are common to
\r
1162 -- multiple groups. The NMS may examine the
\r
1163 -- prtAlertGroup object to determine what group
\r
1164 -- to query for further information.
\r
1168 interlockClosed(6),
\r
1169 configurationChange(7),
\r
1171 subunitMissing(9), -- Not in RFC 1759
\r
1172 -- The subunit tray, bin, etc.
\r
1173 -- has been removed.
\r
1174 subunitLifeAlmostOver(10), -- Not in RFC 1759
\r
1175 subunitLifeOver(11), -- Not in RFC 1759
\r
1176 subunitAlmostEmpty(12), -- Not in RFC 1759
\r
1177 subunitEmpty(13), -- Not in RFC 1759
\r
1178 subunitAlmostFull(14), -- Not in RFC 1759
\r
1179 subunitFull(15), -- Not in RFC 1759
\r
1180 subunitNearLimit(16), -- Not in RFC 1759
\r
1181 subunitAtLimit(17), -- Not in RFC 1759
\r
1182 subunitOpened(18), -- Not in RFC 1759
\r
1183 subunitClosed(19), -- Not in RFC 1759
\r
1184 subunitTurnedOn(20), -- Not in RFC 1759
\r
1185 subunitTurnedOff(21), -- Not in RFC 1759
\r
1186 subunitOffline(22), -- Not in RFC 1759
\r
1187 subunitPowerSaver(23), -- Not in RFC 1759
\r
1188 subunitWarmingUp(24), -- Not in RFC 1759
\r
1189 subunitAdded(25), -- Not in RFC 1759
\r
1190 subunitRemoved(26), -- Not in RFC 1759
\r
1191 subunitResourceAdded(27), -- Not in RFC 1759
\r
1192 subunitResourceRemoved(28), -- Not in RFC 1759
\r
1193 subunitRecoverableFailure(29),
\r
1194 -- Not in RFC 1759
\r
1195 subunitUnrecoverableFailure(30),
\r
1197 -- Not in RFC 1759
\r
1198 subunitRecoverableStorageError(31),
\r
1199 -- Not in RFC 1759
\r
1200 subunitUnrecoverableStorageError(32),
\r
1201 -- Not in RFC 1759
\r
1202 subunitMotorFailure(33), -- Not in RFC 1759
\r
1203 subunitMemoryExhausted(34), -- Not in RFC 1759
\r
1204 subunitUnderTemperature(35), -- Not in RFC 1759
\r
1205 subunitOverTemperature(36), -- Not in RFC 1759
\r
1206 subunitTimingFailure(37), -- Not in RFC 1759
\r
1207 subunitThermistorFailure(38), -- Not in RFC 1759
\r
1209 -- General Printer group
\r
1210 doorOpen(501), -- DEPRECATED
\r
1211 -- Use coverOpened(3)
\r
1212 doorClosed(502), -- DEPRECATED
\r
1213 -- Use coverClosed(4)
\r
1216 printerNMSReset(505), -- Not in RFC 1759
\r
1217 -- The printer has been reset by some
\r
1218 -- network management station(NMS)
\r
1219 -- writing into 'prtGeneralReset'.
\r
1220 printerManualReset(506), -- Not in RFC 1759
\r
1221 -- The printer has been reset manually.
\r
1222 printerReadyToPrint(507), -- Not in RFC 1759
\r
1223 -- The printer is ready to print. (i.e.,
\r
1224 -- not warming up, not in power save
\r
1225 -- state, not adjusting print quality,
\r
1229 inputMediaTrayMissing(801),
\r
1230 inputMediaSizeChange(802),
\r
1231 inputMediaWeightChange(803),
\r
1232 inputMediaTypeChange(804),
\r
1233 inputMediaColorChange(805),
\r
1234 inputMediaFormPartsChange(806),
\r
1235 inputMediaSupplyLow(807),
\r
1236 inputMediaSupplyEmpty(808),
\r
1237 inputMediaChangeRequest(809), -- Not in RFC 1759
\r
1238 -- An interpreter has detected that a
\r
1239 -- different medium is need in this input
\r
1240 -- tray subunit. The prtAlertDescription may
\r
1241 -- be used to convey a human readable
\r
1242 -- description of the medium required to
\r
1243 -- satisfy the request.
\r
1244 inputManualInputRequest(810), -- Not in RFC 1759
\r
1246 -- An interpreter has detected that manual
\r
1247 -- input is required in this subunit. The
\r
1248 -- prtAlertDescription may be used to convey
\r
1249 -- a human readable description of the medium
\r
1250 -- required to satisfy the request.
\r
1251 inputTrayPositionFailure(811), -- Not in RFC 1759
\r
1252 -- The input tray failed to position correctly.
\r
1253 inputTrayElevationFailure(812),
\r
1254 -- Not in RFC 1759
\r
1255 inputCannotFeedSizeSelected(813),
\r
1256 -- Not in RFC 1759
\r
1258 outputMediaTrayMissing(901),
\r
1259 outputMediaTrayAlmostFull(902),
\r
1260 outputMediaTrayFull(903),
\r
1261 outputMailboxSelectFailure(904),
\r
1262 -- Not in RFC 1759
\r
1264 markerFuserUnderTemperature(1001),
\r
1265 markerFuserOverTemperature(1002),
\r
1266 markerFuserTimingFailure(1003),
\r
1267 -- Not in RFC 1759
\r
1268 markerFuserThermistorFailure(1004),
\r
1269 -- Not in RFC 1759
\r
1270 markerAdjustingPrintQuality(1005),
\r
1271 -- Not in RFC 1759
\r
1272 -- Marker Supplies group
\r
1273 markerTonerEmpty(1101),
\r
1274 markerInkEmpty(1102),
\r
1275 markerPrintRibbonEmpty(1103),
\r
1276 markerTonerAlmostEmpty(1104),
\r
1277 markerInkAlmostEmpty(1105),
\r
1278 markerPrintRibbonAlmostEmpty(1106),
\r
1279 markerWasteTonerReceptacleAlmostFull(1107),
\r
1280 markerWasteInkReceptacleAlmostFull(1108),
\r
1281 markerWasteTonerReceptacleFull(1109),
\r
1282 markerWasteInkReceptacleFull(1110),
\r
1283 markerOpcLifeAlmostOver(1111),
\r
1284 markerOpcLifeOver(1112),
\r
1285 markerDeveloperAlmostEmpty(1113),
\r
1286 markerDeveloperEmpty(1114),
\r
1287 markerTonerCartridgeMissing(1115),
\r
1288 -- Not in RFC 1759
\r
1289 -- Media Path Device Group
\r
1290 mediaPathMediaTrayMissing(1301),
\r
1291 mediaPathMediaTrayAlmostFull(1302),
\r
1292 mediaPathMediaTrayFull(1303),
\r
1293 mediaPathCannotDuplexMediaSelected(1304),
\r
1295 -- Not in RFC 1759
\r
1296 -- Interpreter Group
\r
1297 interpreterMemoryIncrease(1501),
\r
1298 interpreterMemoryDecrease(1502),
\r
1299 interpreterCartridgeAdded(1503),
\r
1300 interpreterCartridgeDeleted(1504),
\r
1301 interpreterResourceAdded(1505),
\r
1302 interpreterResourceDeleted(1506),
\r
1303 interpreterResourceUnavailable(1507),
\r
1304 interpreterComplexPageEncountered(1509),
\r
1305 -- Not in RFC 1759
\r
1306 -- The interpreter has encountered a page
\r
1307 -- that is too complex for the resources that
\r
1310 alertRemovalOfBinaryChangeEntry(1801)
\r
1311 -- Not in RFC 1759
\r
1312 -- A binary change event entry has been
\r
1313 -- removed from the alert table. This unary
\r
1314 -- change alert table entry is added to the
\r
1315 -- end of the alert table.
\r