rfc2707.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

         operator to be able to make gross estimates.

      Capacity Planner:

         Provide the ability to determine printer utilization as a
         function of time.

         Provide the ability to determine how long jobs wait before
         starting to print.

      Accountant:

         Provide information to allow the creation of a record of
         resources consumed and printer usage data for charging users or
         groups for resources consumed.

         Provide information to allow the prediction of consumable usage
         and resource need.

   The MIB supports printers that can contain more than one job at a
   time, but still be usable for low end printers that only contain a
   single job at a time.  In particular, the MIB supports the needs of
   Windows and other PC environments for managing low-end direct-connect
   (serial or parallel) and networked devices without unnecessary
   overhead or complexity, while also providing for higher end systems
   and devices.

1.2 Types of Job Monitoring Applications

   The Job Monitoring MIB is designed for the following types of
   monitoring applications:

        1. Monitor a single job starting when the job is submitted and
           ending a defined period after the job completes.  The Job
           Submission ID table provides the map to find the specific job
           to be monitored.

        2. Monitor all 'active' jobs in a queue, which this
           specification generalizes to a "job set".  End users may use
           such a program when selecting a least busy printer, so the
           MIB is designed for such a program to start up quickly and
           find the information needed quickly without having to read



Bergman, et al.              Informational                      [Page 6]

RFC 2707               Job Monitoring MIB - V1.0           November 1999


           all (completed) jobs in order to find the active jobs.
           System operators may also use such a program, in which case
           it would be running for a long period of time and may also be
           interested in the jobs that have completed.  Finally such a
           program may be used to provide an enhanced console and
           logging capability.

        3. Collect resource usage for accounting or system utilization
           purposes that copy the completed job statistics to an
           accounting system. It is recognized that depending on
           accounting programs to copy MIB data during the job-retention
           period is somewhat unreliable, since the accounting program
           may not be running (or may have crashed).  Such a program is
           also expected to keep a shadow copy of the entire Job
           Attribute table including completed, canceled, and aborted
           jobs which the program updates on each polling cycle.  Such a
           program polls at the rate of the persistence of the Attribute
           table.  The design is not optimized to help such an
           application determine which jobs are completed, canceled, or
           aborted.  Instead, the application SHOULD query each job that
           the application's shadow copy shows was not complete,
           canceled, or aborted at the previous poll cycle to see if it
           is now complete or canceled, plus any new jobs that have been
           submitted.

   The MIB provides a set of objects that represent a compatible subset
   of job and document attributes of the ISO DPA standard [iso-dpa] and
   the Internet Printing Protocol (IPP) [ipp-model], so that coherence
   is maintained between these two protocols and the information
   presented to end users and system operators by monitoring
   applications.  However, the job monitoring MIB is intended to be used
   with printers that implement other job submitting and management
   protocols, such as IEEE 1284.1 (TIPSI) [tipsi], as well as with ones
   that do implement ISO DPA.  Thus the job monitoring MIB does not
   require implementation of either the ISO DPA or IPP protocols.

   The MIB is designed so that an additional MIB(s) can be specified in
   the future for monitoring multi-function (scan, FAX, copy) jobs as an
   augmentation to this MIB.

2  Terminology and Job Model

   This section defines the terms that are used in this specification
   and the general model for jobs in alphabetical order.







Bergman, et al.              Informational                      [Page 7]

RFC 2707               Job Monitoring MIB - V1.0           November 1999


      NOTE - Existing systems use conflicting terms, so these terms are
      drawn from the ISO 10175 Document Printing Application (DPA)
      standard [iso-dpa].  For example, PostScript systems use the term
      session for what is called a job in this specification and the
      term job to mean what is called a document in this specification.

   Accounting Application:  The SNMP management application that copies
   job information to some more permanent medium so that another
   application can perform accounting on the data for Accountants, Asset
   Managers, and Capacity Planners use.

   Agent:  The network entity that accepts SNMP requests from a monitor
   or accounting application and provides access to the instrumentation
   for managing jobs modeled by the management objects defined in the
   Job Monitoring MIB module for a server or a device.

   Attribute:  A name, value-pair that specifies a job or document
   instruction, a status, or a condition of a job or a document that has
   been submitted to a server or device.  A particular attribute NEED
   NOT be present in each job instance.  In other words, attributes are
   present in a job instance only when there is a need to express the
   value, either because (1) the client supplied a value in the job
   submission protocol, (2) the document data contained an embedded
   attribute, or (3) the server or device supplied a default value.  An
   agent MAY represent an attribute as an entry (row) in the Attribute
   table in this MIB in which entries are present only when necessary.
   Attributes are identified in this MIB by an enum.

   Client:  The network entity that end users use to submit jobs to
   spoolers, servers, or printers and other devices, depending on the
   configuration, using any job submission protocol over a serial or
   parallel port to a directly-connected device or over the network to a
   networked-connected device.

   Device:  A hardware entity that (1) interfaces to humans, such as a
   device that produces marks on paper or scans marks on paper to
   produce an electronic representation, (2) accesses digital media,
   such as CD-ROMs, or (3) interfaces electronically to another device,
   such as sends FAX data to another FAX device.

   Document:  A sub-section within a job that contains print data and
   document instructions that apply to just the document.

   Document Instruction:  An instruction specifying how to process the
   document.  Document instructions MAY be passed in the job submission
   protocol separate from the actual document data, or MAY be embedded
   in the document data or a combination, depending on the job
   submission protocol and implementation.



Bergman, et al.              Informational                      [Page 8]

RFC 2707               Job Monitoring MIB - V1.0           November 1999


   End User:  A user that uses a client to submit a print job.  See
   "user".

   Impression:  For a print job, an impression is the passage of the
   entire side of a sheet by the marker, whether or not any marks are
   made and independent of the number of passes that the side makes past
   the marker.  Thus a four pass color process counts as a single
   impression, as does highlight color.  Impression counters count all
   kinds:  monochrome, highlight color, and full process color, while
   full color counters only count full color impressions, and high light
   color counters only count high light color impressions.

   One-sided processing involves one impression per sheet.  Two-sided
   processing involves two impressions per sheet.  If a two-sided
   document has an odd number of pages, the last sheet still counts as
   two impressions, if that sheet makes two passes through the marker or
   the marker marks on both sides of a sheet in a single pass.  Two-up
   printing is the placement of two logical pages on one side of a sheet
   and so is still a single impression.  See "page" and "sheet".

   NOTE - Since impressions include blank sides, it is suggested that
   accounting application implementers consider charging for sheets,
   rather than impressions, possibly using the value of the sides
   attribute to select different charges for one-sided versus two-sided
   printing, since some users may think that impressions don't include
   blank sides.

   Internal Collation: The production of the sheets for each document
   copy performed within the printing device by making multiple passes
   over either the source or an intermediate representation of the
   document.

   Job:  A unit of work whose results are expected together without
   interjection of unrelated results.  A job contains one or more
   documents.

   Job Accounting:  The activity of a management application of
   accessing the MIB and recording what happens to the job during and
   after the processing of the job.

   Job Instruction:  An instruction specifying how, when, or where the
   job is to be processed.  Job instructions MAY be passed in the job
   submission protocol or MAY be embedded in the document data or a
   combination depending on the job submission protocol and
   implementation.






Bergman, et al.              Informational                      [Page 9]

RFC 2707               Job Monitoring MIB - V1.0           November 1999


   Job Monitoring (using SNMP):  The activity of a management
   application of accessing the MIB and (1) identifying jobs in the job
   tables being processed by the server, printer or other devices, and
   (2) displaying information to the user about the processing of the
   job.

   Job Monitoring Application:  The SNMP management application that End
   Users, and System Operators use to monitor jobs using SNMP.  A
   monitor MAY be either a separate application or MAY be part of the
   client that also submits jobs.  See "monitor".

   Job Set:  A group of jobs that are queued and scheduled together
   according to a specified scheduling algorithm for a specified device
   or set of devices.  For implementations that embed the SNMP agent in
   the device, the MIB job set normally represents all the jobs known to
   the device, so that the implementation only implements a single job
   set.  If the SNMP agent is implemented in a server that controls one
   or more devices, each MIB job set represents a job queue for (1) a
   specific device or (2) set of devices, if the server uses a single
   queue to load balance between several devices.  Each job set is
   disjoint; no job SHALL be represented in more than one MIB job set.

   Monitor:  Short for Job Monitoring Application.

   Page:  A page is a logical division of the original source document.
   Number up is the imposition of more than one page on a single side of
   a sheet.  See "impression" and "sheet" and "two-up".

   Proxy:  An agent that acts as a concentrator for one or more other
   agents by accepting SNMP operations on the behalf of one or more
   other agents, forwarding them on to those other agents, gathering
   responses from those other agents and returning them to the original
   requesting monitor.

   Queuing:  The act of a device or server of ordering (queuing) the
   jobs for the purposes of scheduling the jobs to be processed.

   Printer:  A device that puts marks on media.

   Server:  A network entity that accepts jobs from clients and in turn
   submits the jobs to printers and other devices that may be directly
   connected to the server via a serial or parallel port or may be on
   the network.  A server MAY be a printer supervisor control program,
   or a print spooler.

   Sheet:  A sheet is a single instance of a medium, whether printing on
   one or both sides of the medium.  See "impression" and "page".




Bergman, et al.              Informational                     [Page 10]

RFC 2707               Job Monitoring MIB - V1.0           November 1999


   SNMP Information Object:  A name, value-pair that specifies an
   action, a status, or a condition in an SNMP MIB.  Objects are
   identified in SNMP by an OBJECT IDENTIFIER.

   Spooler:  A server that accepts jobs, spools the data, and decides
   when and on which printer to print the job.  A spooler is a client to
   a printer or a printer supervisor, depending on implementation.

   Spooling:  The act of a device or server of (1) accepting jobs and
   (2) writing the job's attributes and document data on to secondary
   storage.

   Stacked:  When a media sheet is placed in an output bin of a device.

   Supervisor:  A server that contains a control program that controls a
   printer or other device.  A supervisor is a client to the printer or
   other device.