RFC 2569         Mapping between LPD and IPP Protocols        April 1999


   A mapper SHOULD use the job attribute number-of-intervening-jobs
   rather than the job's position in a list of jobs to determine 'rank'
   because a Printer may omit jobs that it wants to keep secret. If a
   printer doesn't support the job attribute number-of-intervening-jobs,
   a mapper MAY use the job's position.

   Note: a Printer may set the value of job-originating-user-name to the
   authenticated user or to the value of "requesting-user-name",
   depending on the implementation and configuration. For a gateway, the
   authenticated user is the user-id of the gateway, but the
   "requesting-user-name" may contain the name of the user who is the
   gateway's client.

   In order to obtain the information specified above, The LPD-to-IPP
   mapper SHALL use the Get-Printer-Attributes operation to get
   printer-status and SHOULD use the Get-Jobs operation to get
   information about all of the jobs. If the LPD command contains job-
   numbers or user-names, the mapper MAY handle the filtering of the
   response. If the LPD command contains job-numbers but no user-names,
   the mapper MAY use Get-Job-Attributes on each converted job-number
   rather than Get-Jobs. If the LPD command contains a single user-name
   but no job-numbers, the mapper MAY use Get-Jobs with the my-jobs
   option if the server supports this option and if the server allows
   the client to be a proxy for the LPD user.

   NOTE: This specification does not define how the mapper maps the LPD
   Printer-name operand to the IPP "printer-uri" operation attribute.

3.4 Send queue state (long)

   Command syntax:

   send-queue-long = %x04 printer-name *(SP(user-name / job-number)) LF

   The mapper's response to this command includes information about the
   printer and its jobs. RFC 1179 specifies neither the information nor
   the format of its response. This document requires the mapper to
   follow existing practice as specified in this document.

   The mapper SHALL produce a response in the following format which
   consists of a printer-status line optionally followed a list of jobs,
   where each job consists of a blank line, a description line, and one
   line for each file. The description line contains the user-name,
   rank, job-number and host. This format is defined by examples below.
   Appendix B contain the ABNF syntax.







 
RFC 2569         Mapping between LPD and IPP Protocols        April 1999


   For an printer with no jobs the response is:

      no entries

   For a printer with jobs, an example of the response is:

      killtree is ready and printing

      fred: active                        [job 123 tiger]
              2 copies of stuff           602 bytes

      smith: 1st                          [job 124 snail]
              2 copies of resume          7088 bytes
              2 copies of foo             10200 bytes

      fred: 2nd                           [job 125 tiger]
              more                        99 bytes

      The column numbers of above headings and job entries are:

      |       |                           |
      01      09                          41

   Although the format of the long form is different from the format of
   the short form, their fields are identical except for a) the copies
   and host fields which are only in the long form, and b) the "size"
   field contains the single copy size of each file.  Thus the sum of
   the file sizes in the "size" field times the value of the "copies"
   field produces the value for the "Total Size" field in the short
   form. For fields other than the host and copies fields, see the
   preceding section.  For the host field see the table below.

      LPD field IPP attribute        special conversion details