draft-ietf-ipp-lpd-ipp-map-01.txt   draft-ietf-ipp-lpd-ipp-map-02.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
INTERNET-DRAFT INTERNET-DRAFT
Robert Herriot (editor) Robert Herriot (editor)
Sun Microsystems, Inc. Sun Microsystems, Inc.
Tom Hastings Tom Hastings
Xerox Corporation Xerox Corporation
Norm Jacobs Norm Jacobs
Sun Microsystems, Inc. Sun Microsystems, Inc.
Jay Martin Jay Martin
Underscore, Inc. Underscore, Inc.
July 30, 1997 November 20, 1997
Mapping between LPD and IPP Protocols Mapping between LPD and IPP Protocols
<draft-ietf-ipp-lpd-ipp-map-01.txt> draft-ietf-ipp-lpd-ipp-map-02.txt
Expires Jan 30, 1998 Copyright c The Internet Society (date). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
skipping to change at page 1, line 41 skipping to change at page 1, line 41
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Abstract Abstract
This Internet-Draft specifies the mapping between (1) the commands This Internet-Draft specifies the mapping between (1) the commands
and operands of the "Line Printer Daemon (LPD) Protocol" specified and operands of the ''Line Printer Daemon (LPD) Protocol'' specified
in RFC 1179 and (2) the operations and parameters of the Internet in RFC 1179 and (2) the operations and parameters of the Internet
Printing Protocol (IPP). One of the purposes of this document is Printing Protocol (IPP). One of the purposes of this document is
to compare the functionality of the two protocols. Another purpose to compare the functionality of the two protocols. Another purpose
is to facilitate implementation of gateways between LPD and IPP. is to facilitate implementation of gateways between LPD and IPP.
This document is an informational document that is not on the
standards track. It is intended to help implementors of gateways
between IPP and LPD. It also provides an example, which gives
additional insight into IPP.
WARNING: RFC 1179 was not on standards track. While RFC 1179 was WARNING: RFC 1179 was not on standards track. While RFC 1179 was
intended to record existing practice, it fell short in some areas. intended to record existing practice, it fell short in some areas.
However, this specification maps between (1) the actual current However, this specification maps between (1) the actual current
practice of RFC 1179 and (2) IPP. This document does not attempt practice of RFC 1179 and (2) IPP. This document does not attempt
to map the numerous divergent extensions to the LPD protocol that to map the numerous divergent extensions to the LPD protocol that
have been made by many implementers. have been made by many implementers.
Jacobs, Martin Expires May 20, 1998
Jacobs, Martin Expires January 30, 1998
TABLE OF CONTENTS TABLE OF CONTENTS
1. Introduction........................................................3 1. Introduction........................................................3
2. Terminology.........................................................3 2. Terminology.........................................................3
3. Mapping from LPD Commands to IPP Operations.........................4 3. Mapping from LPD Commands to IPP Operations.........................4
3.1 Print any waiting jobs ...........................................4 3.1 Print any waiting jobs ...........................................4
3.2 Receive a printer job ............................................4 3.2 Receive a printer job ............................................4
3.2.1 Abort job ....................................................5 3.2.1 Abort job ....................................................5
3.2.2 Receive control file .........................................6 3.2.2 Receive control file .........................................5
3.2.3 Receive data file ............................................6 3.2.3 Receive data file ............................................5
3.3 Send queue state (short) .........................................6 3.3 Send queue state (short) .........................................6
3.4 Send queue state (long) ..........................................8 3.4 Send queue state (long) ..........................................7
3.5 Remove jobs ......................................................9 3.5 Remove jobs ......................................................8
4. Mapping of LPD Control File Lines to IPP Parameters................10 4. Mapping of LPD Control File Lines to IPP Parameters.................9
4.1 Required Job Functions ..........................................10 4.1 Required Job Functions ...........................................9
4.2 Optional Job Functions ..........................................11 4.2 Optional Job Functions ..........................................10
4.3 Required Document Functions .....................................12 4.3 Required Document Functions .....................................10
4.4 Recommended Document Functions ..................................13 4.4 Recommended Document Functions ..................................11
5. Mapping from IPP operations to LPD commands........................13 5. Mapping from IPP operations to LPD commands........................11
5.1 Get-Operations ..................................................13 5.1 Print-Job .......................................................11
5.2 Print-Job .......................................................13 5.2 Print-URI .......................................................12
5.3 Print-URI .......................................................14 5.3 Validate-Job ....................................................12
5.4 Validate-Job ....................................................15 5.4 Create-Job ......................................................12
5.5 Create-Job ......................................................15 5.5 Send-Document ...................................................13
5.6 Send-Document ...................................................15 5.6 Send-URI ........................................................13
5.7 Send-URI ........................................................15 5.7 Cancel-Job ......................................................13
5.8 Cancel-Job ......................................................15 5.8 Get-Attributes ..................................................13
5.9 Get-Attributes ..................................................16 5.9 Get-Jobs ........................................................14
5.10 Get-Jobs .......................................................17 6. Mapping of IPP Parameters to LPD Control File Lines................14
6. Mapping of IPP Parameters to LPD Control File Lines................17 6.1 Required Job Functions ..........................................14
6.1 Required Job Functions ..........................................17 6.2 Optional Job Functions ..........................................15
6.2 Optional Job Functions ..........................................18 6.3 Required Document Functions .....................................15
6.3 Required Document Functions .....................................18 7. Copyright Notice...................................................16
7. References.........................................................19 8. References.........................................................16
8. Author's Addresses.................................................19 9. Author's Addresses.................................................17
9. Appendix A: ABNF Syntax for response of Send-queue-state (short)...20 10. Appendix A: ABNF Syntax for response of Send-queue-state (short)..17
10. Appendix B: ABNF Syntax for response of Send-queue-state (long)...20 11. Appendix B: ABNF Syntax for response of Send-queue-state (long)...17
11. Appendix C: Unsupported LPD functions.............................21 12. Appendix C: Unsupported LPD functions.............................18
Jacobs, Martin Expires January 30, 1998 Jacobs, Martin Expires May 20, 1998
Mapping between the LPD and IPP Protocols Mapping between the LPD and IPP Protocols
1. Introduction 1. Introduction
The reader of this specification is expected to be familiar with the IPP The reader of this specification is expected to be familiar with the IPP
Model and Semantics specification [1], the IPP Protocol specification Model and Semantics specification [ipp-mod], the IPP Protocol
[2], and the Line Printer Daemon (LPD) protocol specification [3] as specification [ipp-pro], and the Line Printer Daemon (LPD) protocol
described in RFC 1179. specification [rfc1179] as described in RFC 1179.
RFC 1179 was written in 1990 in an attempt to document existing LPD RFC 1179 was written in 1990 in an attempt to document existing LPD
protocol implementations. Since then, a number of undocumented protocol implementations. Since then, a number of undocumented
extensions have been made by vendors to support functionality specific extensions have been made by vendors to support functionality specific
to their printing solutions. All of these extensions consist of to their printing solutions. All of these extensions consist of
additional control file commands. This document does not address any of additional control file commands. This document does not address any of
these vendor extensions. Rather it addresses existing practice within these vendor extensions. Rather it addresses existing practice within
the context of the features described by RFC 1179. Deviations of the context of the features described by RFC 1179. Deviations of
existing practice from RFC 1179 are so indicated. existing practice from RFC 1179 are so indicated.
Other LPD control file commands in RFC 1179 are obsolete. They are Other LPD control file commands in RFC 1179 are obsolete. They are
intended to work on "text" only formats and are inappropriate for many intended to work on "text" only formats and are inappropriate for many
contemporary document formats that completely specify each page. This contemporary document formats that completely specify each page. This
document does not address the support of these obsolete features. document does not address the support of these obsolete features.
In the area of document formats, also known as page description In the area of document formats, also known as page description
languages (PDL), RFC 1179 defines a fixed set with no capability for languages (PDL), RFC 1179 defines a fixed set with no capability for
extension. Consequently, some new PDL's are not supported, and some of extension. Consequently, some new PDL's are not supported, and some of
those that are supported are sufficiently unimportant now that they have those that are supported are sufficiently unimportant now that they have
not been registered for use with the Printer MIB[4] and IPP[1] [2], not been registered for use with the Printer MIB[rfc1759] and IPP[ipp-
though they could be registered if desired. See the Printer MIB mod] [ipp-pro], though they could be registered if desired. See the
specification [4] and/or the IPP Model specification [1] for Printer MIB specification [rfc1759] and/or the IPP Model specification
instructions for registration of document-formats with IANA. IANA lists [ipp-mod] for instructions for registration of document-formats with
the registered document-formats as "printer languages". IANA. IANA lists the registered document-formats as "printer
languages".
This document addresses the protocol mapping for both directions: This document addresses the protocol mapping for both directions:
mapping of the LPD protocol to the IPP protocol and mapping of the IPP mapping of the LPD protocol to the IPP protocol and mapping of the IPP
protocol to the LPD protocol. The former is called the "LPD-to-IPP protocol to the LPD protocol. The former is called the "LPD-to-IPP
mapper" and the latter is called the "IPP-to-LPD mapper". mapper" and the latter is called the "IPP-to-LPD mapper".
This document is an informational document that is not on the standards
track. It is intended to help implementors of gateways between IPP and
LPD. It also provides an example, which gives additional insight into
IPP.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [6]. document are to be interpreted as described in RFC 2119 [abnf].
RFC 1179 uses the word "command" in two contexts: for over-the-wire RFC 1179 uses the word "command" in two contexts: for over-the-wire
operations and for command file functions. This document SHALL use the operations and for command file functions. This document SHALL use the
Jacobs, Martin Expires May 20, 1998
word "command" for the former and the phrase "functions" for the latter. word "command" for the former and the phrase "functions" for the latter.
The syntax of the LPD commands is given using ABNF [6]. The syntax of the LPD commands is given using ABNF [abnf].
The following tokens are used in order to make the syntax more readable: The following tokens are used in order to make the syntax more readable:
LF stands for %x0A (linefeed) LF stands for %x0A (linefeed)
Jacobs, Martin Expires January 30, 1998
SP stands for %x20. (space) SP stands for %x20. (space)
DIGIT stands for %x30-39 ("0" to "9") DIGIT stands for %x30-39 ("0" to "9")
3. Mapping from LPD Commands to IPP Operations 3. Mapping from LPD Commands to IPP Operations
This section describes the mapping from LPD commands to IPP operations. This section describes the mapping from LPD commands to IPP operations.
Each of the following sub-sections appear as sub-sections of section 5 Each of the following sub-sections appear as sub-sections of section 5
of RFC 1179. of RFC 1179.
The following table summarizes the IPP operation that the mapper uses The following table summarizes the IPP operation that the mapper uses
when it receives an LPD command. Each section below gives more detail. when it receives an LPD command. Each section below gives more detail.
LPD command IPP operation LPD command IPP operation
print-any-waiting-jobs ignore print-any-waiting-jobs ignore
receive-a-printer-job Print-Job or Create-Job/Send-Document receive-a-printer-job Print-Job or Create-Job/Send-Document
send queue state Get-Attributes (printer) and Get-Jobs send queue state (short Get-Attributes (printer) and Get-Jobs
(short or long) or long)
remove-jobs Cancel-Job remove-jobs Cancel-Job
3.1 Print any waiting jobs 3.1 Print any waiting jobs
Command syntax: Command syntax:
print-waiting-jobs = %x01 printer-name LF print-waiting-jobs = %x01 printer-name LF
This command causes the LPD daemon check its queue and print any waiting This command causes the LPD daemon check its queue and print any waiting
jobs. An IPP printer handles waiting jobs without such a nudge. jobs. An IPP printer handles waiting jobs without such a nudge.
skipping to change at page 4, line 51 skipping to change at page 5, line 4
receive-job = %x02 printer-name LF receive-job = %x02 printer-name LF
The control file and data files mentioned in the following paragraphs The control file and data files mentioned in the following paragraphs
are received via LPD sub-commands that follow this command. Their are received via LPD sub-commands that follow this command. Their
mapping to IPP commands and attributes is described later in this mapping to IPP commands and attributes is described later in this
section. section.
The mapper maps the 'Receive a printer job' command to either: The mapper maps the 'Receive a printer job' command to either:
. the Print-Job operation which includes a single data file or . the Print-Job operation which includes a single data file or
Jacobs, Martin Expires May 20, 1998
. the Create-Job operation followed by one Send-Document . the Create-Job operation followed by one Send-Document
operation for each data file. operation for each data file.
If the IPP printer supports both Create-Job and Send-Document, and if a If the IPP printer supports both Create-Job and Send-Document, and if a
job consists of: job consists of:
Jacobs, Martin Expires January 30, 1998 . a single data file, the mapper SHOULD use the Print-Job
. a single data file, the mapper SHOULD use the PrintJob
operation, but MAY use the Create-Job and Send-Document operation, but MAY use the Create-Job and Send-Document
operations. operations.
. more than one data file, the mapper SHALL use Create Job . more than one data file, the mapper SHALL use Create-Job
followed by one Send-Document for each received LPD data file. followed by one Send-Document for each received LPD data file.
If the IPP printer does not support both Create-Job and Send-Document, If the IPP printer does not support both Create-Job and Send-Document,
and if a job consists of: and if a job consists of:
. a single data file, the mapper SHALL use the PrintJob . a single data file, the mapper SHALL use the PrintJob
operation. operation.
. more than one data file, the mapper SHALL submit each received . more than one data file, the mapper SHALL submit each received
LPD data file as a separate Print-Job operation (thereby LPD data file as a separate Print-Job operation (thereby
converting a single LPD job into multiple IPP jobs). converting a single LPD job into multiple IPP jobs).
skipping to change at page 5, line 33 skipping to change at page 5, line 39
whether the LPD control file, which supplies attributes for Create-Job, whether the LPD control file, which supplies attributes for Create-Job,
arrives before or after all LPD data files. arrives before or after all LPD data files.
NOTE: This specification does not specify how the mapper maps: the LPD NOTE: This specification does not specify how the mapper maps: the LPD
Printer-name operand to the IPP "printer-uri" parameter. Printer-name operand to the IPP "printer-uri" parameter.
The following 3 sub-sections gives further details about the mapping The following 3 sub-sections gives further details about the mapping
from LPD receive-a-printer-job sub-commands. Each of the following from LPD receive-a-printer-job sub-commands. Each of the following
sub-sections appear as sub-sections of section 6 of RFC 1179. sub-sections appear as sub-sections of section 6 of RFC 1179.
ISSUE: the mapper needs to maintain information such as the mapping of
each job-number to its corresponding job-URI. It would be nice for IPP
to support an "scratch-pad" attribute for the mapper to encode such
information. Then it wouldn't have to maintain this information
separately.
3.2.1 Abort job 3.2.1 Abort job
Sub-command syntax: Sub-command syntax:
abort-job = %x1 LF abort-job = %x1 LF
This sub-command of receive-a-printer-job is intended to abort any job This sub-command of receive-a-printer-job is intended to abort any job
transfer in process. transfer in process.
If the mapper receives this sub-command, it SHALL cancel the job that it If the mapper receives this sub-command, it SHALL cancel the job that it
is in the process of transmitting. is in the process of transmitting.
If the mapper is in the process of sending a Print-Job or Create-Job If the mapper is in the process of sending a Print-Job or Create-Job
operation, it terminates the job either by closing the connection, or operation, it terminates the job either by closing the connection, or
performing the Cancel-Job operation with the job-uri that it received performing the Cancel-Job operation with the job-uri that it received
from the Print-Job or Create-Job operation. from the Print-Job or Create-Job operation.
NOTE: This sub-command is implied if at any time the connection between NOTE: This sub-command is implied if at any time the connection between
the LPD client and server is terminated before an entire print job has the LPD client and server is terminated before an entire print job has
been transferred via an LPD Receive-a-printer-job request. been transferred via an LPD Receive-a-printer-job request.
Jacobs, Martin Expires January 30, 1998 Jacobs, Martin Expires May 20, 1998
3.2.2 Receive control file 3.2.2 Receive control file
Sub-command syntax: Sub-command syntax:
receive-control-file = %x2 number-of-bytes SP name-of-control-file LF receive-control-file = %x2 number-of-bytes SP name-of-control-file LF
number-of-bytes = 1*DIGIT number-of-bytes = 1*DIGIT
name-of-control-file = "cfA" job-number client-host-name name-of-control-file = "cfA" job-number client-host-name
; e.g. "cfA123woden" ; e.g. "cfA123woden"
job-number = 3DIGIT job-number = 3DIGIT
skipping to change at page 6, line 31 skipping to change at page 6, line 31
or Create-Job operation. or Create-Job operation.
3.2.3 Receive data file 3.2.3 Receive data file
Sub-command syntax: %x3 number-of-bytes-in-data-file Name-of-data-file Sub-command syntax: %x3 number-of-bytes-in-data-file Name-of-data-file
receive-data-file = %x03 number-of-bytes SP name-of-data-file LF receive-data-file = %x03 number-of-bytes SP name-of-data-file LF
number-of-bytes = 1*DIGIT number-of-bytes = 1*DIGIT
name-of-data-file = "df" letter job-number client-host-name name-of-data-file = "df" letter job-number client-host-name
; e.g. "dfA123woden for the first file ; e.g. "dfA123woden for the first file
letter = %x41-5A / %x61-7A ; "A" to "Z", "a" to "z" letter = %x41-5A / %x61-7A ; "A" " to Z", "a" to "z"
; first file is "A", ; first file is "A",
; second "B", and 52nd file is "z" ; second "B", and 52nd file is "z"
job-number = 3DIGIT job-number = 3DIGIT
client-host-name = <a host name> client-host-name = <a host name>
This sub-command is roughly equivalent to the IPP Send-Document This sub-command is roughly equivalent to the IPP Send-Document
operation. operation.
The mapper SHALL use the contents of the received LPD data file as the The mapper SHALL use the contents of the received LPD data file as the
data to transmit with the IPP Print-Job or Send-Document operation. data to transmit with the IPP Print-Job or Send-Document operation.
skipping to change at page 7, line 4 skipping to change at page 7, line 4
3.3 Send queue state (short) 3.3 Send queue state (short)
Command syntax: Command syntax:
send-queue-short = %x03 printer-name *(SP(user-name / job-number)) LF send-queue-short = %x03 printer-name *(SP(user-name / job-number)) LF
The mapper's response to this command includes information about the The mapper's response to this command includes information about the
printer and its jobs. RFC 1179 specifies neither the information nor the printer and its jobs. RFC 1179 specifies neither the information nor the
format of its response. This document requires the mapper to follow format of its response. This document requires the mapper to follow
existing practice as specified in this document. existing practice as specified in this document.
Jacobs, Martin Expires January 30, 1998 Jacobs, Martin Expires May 20, 1998
The mapper SHALL produce a response in the following format which The mapper SHALL produce a response in the following format which
consists of a printer-status line optionally followed by a heading line, consists of a printer-status line optionally followed by a heading line,
and a list of jobs. This format is defined by examples below. Appendix A and a list of jobs. This format is defined by examples below. Appendix A
contains the ABNF syntax. contains the ABNF syntax.
For an printer with no jobs, the response starts in column 1 and is: For an printer with no jobs, the response starts in column 1 and is:
no entries no entries
skipping to change at page 7, line 44 skipping to change at page 7, line 44
LPD field IPP attribute special conversion details LPD field IPP attribute special conversion details
printer- printer-state and For a printer-state of idle or printer- printer-state and For a printer-state of idle or
status printer-state-reasons processing, the mapper SHALL use status printer-state-reasons processing, the mapper SHALL use
the formats above. For stopped, the formats above. For stopped,
the mapper SHALL use printer- the mapper SHALL use printer-
state-reasons to produce an state-reasons to produce an
unspecified format for the error. unspecified format for the error.
rank number-of- the mapper SHALL the format above rank number-of- the mapper SHALL the format above
intervening-jobs intervening-jobs
owner job-originating-user unspecified conversion; job- owner job-originating-user- unspecified conversion; job-
originating-user may be the name originating-user-namemay be the
mapper's user-name mapper's user-name
job job-uri unspecified conversion job job-id the mapper shall use the job-id
files document-name the mapper shall create a comma files document-name the mapper shall create a comma
separated list of the document- separated list of the document-
names and then truncate this list names and then truncate this list
to the first 24 characters to the first 24 characters
total- job-k-octets the mapper shall multiple the total- job-k- the mapper shall multiple the
size value of job-k-octets by 1024. size octets*copies*1024 value of job-k-octets by 1024 and
by the value of the "copies"
attribute.
A mapper SHOULD use the job attribute number-of-intervening-jobs rather 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 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 Jacobs, Martin Expires May 20, 1998
Jacobs, Martin Expires January 30, 1998
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 support the job attribute number-of-intervening-jobs, a mapper MAY use
the job's position. the job's position.
ISSUE: is job-k-octets the sum of the bytes of each document times the ISSUE: the value of job-originating-user-name is still somewhat murky in
number of copies? If so, "total-size" is 1024 times job-k-octets. The IPP especially where the IPP client is a proxy for some user coming from
model document needs clarification. elsewhere.In order to obtain the information specified above, The LPD-
to-IPP mapper SHALL use the Get-Attributes operation of the printer to
In order to obtain the information specified above, The LPD-to-IPP get printer-status and SHOULD use the Get-Jobs operation to get
mapper SHALL use the Get-Attributes operation of the printer to get information about all of the jobs. If the LPD command contains job-
printer-status and SHOULD use the Get-Jobs operation to get information numbers or user-names, the mapper MAY handle the filtering of the
about all of the jobs. If the LPD command contains job-numbers or user- response. If the LPD command contains job-numbers but no user-names, the
names, the mapper handles the filtering of the response because Get-Jobs mapper MAY use Get-Attributes on each converted job-number rather than
has no way to limit jobs to those of a particular user. If the LPD Get-Jobs. If the LPD command contains a single user-name but no job-
command contains job-numbers but no user-names, the mapper MAY use Get- numbers, the mapper MAY use Get-Attributes with the my-jobs option if
Attributes on each converted job-number rather than Get-Jobs. 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 NOTE: This specification does not define how the mapper maps the LPD
Printer-name operand to the IPP "printer-uri" parameter. Printer-name operand to the IPP "printer-uri" parameter.
3.4 Send queue state (long) 3.4 Send queue state (long)
Command syntax: Command syntax:
send-queue-long = %x04 printer-name *(SP(user-name / job-number)) LF send-queue-long = %x04 printer-name *(SP(user-name / job-number)) LF
skipping to change at page 8, line 56 skipping to change at page 9, line 4
no entries no entries
For a printer with jobs, an example of the response is: For a printer with jobs, an example of the response is:
killtree is ready and printing killtree is ready and printing
fred: active [job 123 tiger] fred: active [job 123 tiger]
2 copies of stuff 602 bytes 2 copies of stuff 602 bytes
smith: 1st [job 124 snail] smith: 1st [job 124 snail]
Jacobs, Martin Expires May 20, 1998
2 copies of resume 7088 bytes 2 copies of resume 7088 bytes
2 copies of foo 10200 bytes 2 copies of foo 10200 bytes
fred: 2nd [job 125 tiger] fred: 2nd [job 125 tiger]
Jacobs, Martin Expires January 30, 1998
more 99 bytes more 99 bytes
The column numbers of above headings and job entries are: The column numbers of above headings and job entries are:
| | | | | |
01 09 41 01 09 41
Although the format of the long form is different from the format of the Although the format of the long form is different from the format of the
short form, their fields are identical except for the copies and host short form, their fields are identical except for a) the copies and host
fields which are only in the long form. For fields other than the host fields which are only in the long form, and b) the "size" field
and copies fields, see the preceding section. For the host field see the contains the single copy size of each file. Thus the sum of the file
table below. 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 LPD field IPP attribute special conversion details
host job-originating-host unspecified conversion; job- host unspecified conversion; job-
originating-host may be the originating-host may be the
mapper's host mapper's host
copies copies the mapper shall assume the copies copies the mapper shall assume the
value of copies precedes the value of copies precedes the
string "copies of "; otherwise, string "copies of "; otherwise,
the value of copies is 1. the value of copies is 1.
NOTE: This specification does not define how the mapper maps the LPD NOTE: This specification does not define how the mapper maps the LPD
Printer-name operand to the IPP printer-uri parameter. Printer-name operand to the IPP printer-uri parameter.
skipping to change at page 9, line 47 skipping to change at page 9, line 54
The agent operand is the user-name of the user initiating the remove- The agent operand is the user-name of the user initiating the remove-
jobs command. The special user-name 'root' indicates a privileged user jobs command. The special user-name 'root' indicates a privileged user
who can remove jobs whose user-name differs from the agent.. who can remove jobs whose user-name differs from the agent..
The mapper SHALL issue one Cancel-Job operation for each job referenced The mapper SHALL issue one Cancel-Job operation for each job referenced
by the remove-jobs command. Each job-number in the remove-jobs command by the remove-jobs command. Each job-number in the remove-jobs command
references a single job. Each user-name in the remove-jobs command references a single job. Each user-name in the remove-jobs command
implicitly references all jobs owned by the specified user. The active implicitly references all jobs owned by the specified user. The active
job is implicitly referenced when the remove-jobs command contains job is implicitly referenced when the remove-jobs command contains
neither job-numbers nor user-names. The mapper MAY use Get-Job to neither job-numbers nor user-names. The mapper MAY use Get-Jobs to
determine the job-uri of implicitly referenced jobs. determine the job-uri of implicitly referenced jobs.
Jacobs, Martin Expires May 20, 1998
The mapper SHALL not use the agent name of `root' when end-users cancel The mapper SHALL not use the agent name of `root' when end-users cancel
their own jobs. Violation of this rule creates a potential security their own jobs. Violation of this rule creates a potential security
violation, and it may cause the printer to issue a notification that violation, and it may cause the printer to issue a notification that
misleads a user into thinking that some other person canceled the job. misleads a user into thinking that some other person canceled the job.
If the agent of a remove-jobs command for a job J is the same as the If the agent of a remove-jobs command for a job J is the same as the
user name specified with the `P' function in the control file for job J, user name specified with the `P' function in the control file for job J,
Jacobs, Martin Expires January 30, 1998
then the mapper SHALL ensure that the caller of the Cancel-Job command then the mapper SHALL ensure that the caller of the Cancel-Job command
for job J is the same as job-originating-user for job J. for job J is the same as job-originating-user for job J.
Note: This requirement means that a mapper must be consistent in who the Note: This requirement means that a mapper must be consistent in who the
receiver perceives as the caller of IPP operations. The mapper either receiver perceives as the caller of IPP operations. The mapper either
acts as itself or acts on behalf of another user. The latter is acts as itself or acts on behalf of another user. The latter is
preferable if it is possible. This consistency is necessary between preferable if it is possible. This consistency is necessary between
Print-Job/Create-Job and Cancel-Job in order for Cancel-Job to work, but Print-Job/Create-Job and Cancel-Job in order for Cancel-Job to work, but
it is also desirable for other operations. For example, Get-Jobs may it is also desirable for other operations. For example, Get-Jobs may
give more information about job submitted by the caller of this give more information about job submitted by the caller of this
skipping to change at page 10, line 50 skipping to change at page 11, line 5
. required with a job, . required with a job,
. optional with a job . optional with a job
. required with each document. . required with each document.
In the tables below, each LPD value is given a name, such as `h'. If an In the tables below, each LPD value is given a name, such as `h'. If an
IPP value uses the LPD value, then the IPP value column contains the LPD IPP value uses the LPD value, then the IPP value column contains the LPD
name, such as `h' to denote this. Otherwise, the IPP value column name, such as `h' to denote this. Otherwise, the IPP value column
specifies the literal value. specifies the literal value.
Jacobs, Martin Expires May 20, 1998
4.1 Required Job Functions 4.1 Required Job Functions
The following LPD functions MUST be in a received LPD job. The mapper The following LPD functions MUST be in a received LPD job. The mapper
SHALL receive each of the following LPD functions and SHALL include the SHALL receive each of the following LPD functions and SHALL include the
information as a parameter with each IPP job. The functions SHOULD be in information as a parameter with each IPP job. The functions SHOULD be in
the order `H', `P' and they SHOULD be the first two functions in the the order `H', `P' and they SHOULD be the first two functions in the
control file, but they MAY be anywhere in the control file and in any control file, but they MAY be anywhere in the control file and in any
order. order.
Jacobs, Martin Expires January 30, 1998
LPD function IPP LPD function IPP
name value description name value name value description name value
H h Originating Host h (in security layer) H h Originating Host h (in security layer)
P u User identification u (in security layer) P u User identification u (in security layer
and operation
attribute)
none best-effort `true' none best-effort `true'
A mapper MAY sends its own host rather than the client's host, and a A mapper MAY sends its own host rather than the client's host, and a
mapper MAY send its own user-name as user identification rather than the mapper MAY send its own user-name as user identification rather than the
client user. But in any case, the values sent SHALL be compatible with client user. But in any case, the values sent SHALL be compatible with
the Cancel-Job operation. The IPP operation MAY have no way to specify the Cancel-Job operation. The IPP operation MAY have no way to specify
an originating host-name. an originating host-name.
ISSUE: what do we do about job-orginating-host? ISSUE: what do we do about job-orginating-host?
skipping to change at page 11, line 45 skipping to change at page 11, line 57
table. table.
LPD function IPP LPD function IPP
name value description name value name value description name value
J j Job name for job-name j J j Job name for job-name j
banner page banner page
L l Print banner page job-sheets `standard' if `L' is L l Print banner page job-sheets `standard' if `L' is
present present
`none' if `L' is present `none' if `L' is present
M m Mail When Printed notification- `job-completion' M m Mail When Printed IPP has no notification
events 'mailto://'m`@'h mechanism. To support
notification- this LPD feature, the
method Jacobs, Martin Expires May 20, 1998
Note: `m' is the user name and not an email address. The mapper can gateway must poll
fabricate an email address with the source host. This email address .
mail fail when the `h' is some intermediary host that doesn't know about
user `m'. But there is no better solution.
Jacobs, Martin Expires January 30, 1998
4.3 Required Document Functions 4.3 Required Document Functions
The mapper SHALL receive one set of the required document functions with The mapper SHALL receive one set of the required document functions with
each copy of a document, and SHALL include the converted information as each copy of a document, and SHALL include the converted information as
parameters with each IPP document parameters with each IPP document
If the control file contains required and recommended document If the control file contains required and recommended document
functions, the required functions SHOULD precede the recommended ones functions, the required functions SHOULD precede the recommended ones
and if the job contains multiple documents, all the functions for each and if the job contains multiple documents, all the functions for each
document are grouped together as shown in the example of section 6.3 document are grouped together as shown in the example of section 6.3
"Required Document Functions". However, the document functions MAY be in "Required Document Functions". However, the document functions MAY be in
any order. any order.
LPD function IPP LPD function IPP
name valu description name value name valu description name value
e e
f fff Print formatted document-format 37 (langAutomatic) f fff Print formatted document-format 'application/octet-
file file stream'
l fff Print file leaving document-format 37 (langAutomatic) l fff Print file leaving document-format 'application/octet-
control characters control characters stream'
o fff Print Postscript document-format 6 (langPS). o fff Print Postscript document-format 'application/PostScri
output file output file pt'
copies see note copies see note
Note: In practice, the `f' LPD function is often overloaded. It is often Note: In practice, the `f' LPD function is often overloaded. It is often
used with any format of document data including PostScript and PCL data. used with any format of document data including PostScript and PCL data.
Note: In practice, the `l' LPD function is often used as a rough Note: In practice, the `l' LPD function is often used as a rough
equivalent to the `f' function. equivalent to the `f' function.
Note: When RFC 1179 was written, no implementation supported the `o' Note: When RFC 1179 was written, no implementation supported the `o'
function; instead `f' was used for PostScript. Windows NT now sends `o' function; instead `f' was used for PostScript. Windows NT now sends `o'
function for a PostScript file. function for a PostScript file.
skipping to change at page 12, line 55 skipping to change at page 13, line 5
reject the job because the document contains a format that the mapper reject the job because the document contains a format that the mapper
does not support. does not support.
The mapper determines the number of copies by counting the number of The mapper determines the number of copies by counting the number of
occurrences of each `fff' file with one of the lower-case functions occurrences of each `fff' file with one of the lower-case functions
above. For example, if `f dfA123woden' occurs 4 times, then copies has a above. For example, if `f dfA123woden' occurs 4 times, then copies has a
value of 4. Although the LPD protocol allows the value of copies to be value of 4. Although the LPD protocol allows the value of copies to be
different for each document, the commands and the receiving print different for each document, the commands and the receiving print
systems don't support this. systems don't support this.
ISSUE: should we register DVI, ditroff and troff. At least DVI and one Jacobs, Martin Expires May 20, 1998
of the troff is still in use.
Jacobs, Martin Expires January 30, 1998
4.4 Recommended Document Functions 4.4 Recommended Document Functions
The mapper SHOULD receive one set of the recommended document functions The mapper SHOULD receive one set of the recommended document functions
with each document, and SHOULD include the converted information as with each document, and SHOULD include the converted information as
parameters with each IPP document. The functions SHOULD be received in parameters with each IPP document. The functions SHOULD be received in
the order `U' and `N', but they MAY arrive in any order. the order `U' and `N', but they MAY arrive in any order.
LPD function IPP LPD function IPP
name value description name value name value description name value
skipping to change at page 13, line 29 skipping to change at page 13, line 29
Note: the value `fff' of the `U' function is the name of the data file Note: the value `fff' of the `U' function is the name of the data file
as transferred, e.g. "dfA123woden". as transferred, e.g. "dfA123woden".
5. Mapping from IPP operations to LPD commands 5. Mapping from IPP operations to LPD commands
If the IPP-to-LPD mapper receives an IPP operation, the following table If the IPP-to-LPD mapper receives an IPP operation, the following table
summarizes the LPD command that it uses. Each section below gives the summarizes the LPD command that it uses. Each section below gives the
detail. Each of the following sub-sections appear as sub-sections of detail. Each of the following sub-sections appear as sub-sections of
section 3 in the document "Internet Printing Protocol/1.0: Model and section 3 in the document "Internet Printing Protocol/1.0: Model and
Semantics" [1]. Semantics" [ipp-mod].
IPP operation LPD command IPP operation LPD command
Get-Operations implemented by the mapper
Print-Job or Print-URI or receive-a-printer-job Print-Job or Print-URI or receive-a-printer-job
Create-Job/Send-Document/Send-URI and then print-any-waiting-jobs Create-Job/Send-Document/Send-URI and then print-any-waiting-jobs
Validate-Job implemented by the mapper Validate-Job implemented by the mapper
Cancel-Job remove-jobs Cancel-Job remove-jobs
Get-Attributes (printer or job) send queue state (short or long) Get-Attributes (printer or job) send queue state (short or long)
or Get-Jobs or Get-Jobs
5.1 Get-Operations 5.1 Print-Job
The mapper SHALL return a list of the operations that it supports. It
SHALL support at least those operations that are mandatory according to
the IPP model document [1].
5.2 Print-Job
The mapper SHALL send the following commands in the order listed below: The mapper SHALL send the following commands in the order listed below:
. receive-a-printer-job command . receive-a-printer-job command
. both receive-control-file sub-command and receive-data-file . both receive-control-file sub-command and receive-data-file
sub-command sub-command
(unspecified order, see Note below) (unspecified order, see Note below)
. print-any-waiting-jobs command, . print-any-waiting-jobs command,
except that if the mapper is sending a sequence of receive-a- except that if the mapper is sending a sequence of receive-a-
Jacobs, Martin Expires January 30, 1998
printer-job commands, it MAY omit sending print-any-waiting- printer-job commands, it MAY omit sending print-any-waiting-
jobs after any receive-a printer-job command that is neither jobs after any receive-a printer-job command that is neither
the first nor last command in this sequence the first nor last command in this sequence
Note: it is recommended that the order of the receive-control-file sub- Note: it is recommended that the order of the receive-control-file sub-
command and the receive-data-file sub-command be configurable because command and the receive-data-file sub-command be configurable because
either order fails for some print systems. Some print systems assume either order fails for some print systems. Some print systems assume
that the control file follows all data files and start printing that the control file follows all data files and start printing
Jacobs, Martin Expires May 20, 1998
immediately on receipt of the control file. When such a print system immediately on receipt of the control file. When such a print system
tries to print a data file that has not arrived, it produces an error. tries to print a data file that has not arrived, it produces an error.
Other print systems assume that the control file arrives before the data Other print systems assume that the control file arrives before the data
files and start printing when the first data file arrives. Such a system files and start printing when the first data file arrives. Such a system
ignores the control information, such as banner page or copies. ignores the control information, such as banner page or copies.
NOTE: This specification does not define the mapping between the IPP NOTE: This specification does not define the mapping between the IPP
printer-uri and the LPD printer-name. printer-uri and the LPD printer-name.
The mapper SHALL send the IPP parameters and attributes received from The mapper SHALL send the IPP parameters and attributes received from
the operation to the LPD printer by using the LPD receive-control-file the operation to the LPD printer by using the LPD receive-control-file
sub-command. The mapper SHALL create the job-number for use in the sub-command. The mapper SHALL create the LPD job-number for use in the
control file name, but the receiving printer MAY, in some circumstances, control file name, but the receiving printer MAY, in some circumstances,
assign a different job-number to the job. The mapper SHALL create the assign a different job-number to the job. The mapper SHALL create the
job-uri returned in the Print-Job response. IPP job-id and IPP job-uri returned in the Print-Job response.
NOTE: This specification does not specify how the mapper determines the NOTE: This specification does not specify how the mapper determines the
job-number or the job-uri of a job that it creates nor does it specify LPD job-number, the IPP job-id or the IPP job-uri of a job that it
the relation ship between the job-uri and the job-number, both of which creates nor does it specify the relation ship between the IPP job-uri,
the mapper creates. IPP the job-id and the LPD job-number, both of which the mapper creates.
However, it is likely that the mapper will use the same integer value
for both theLPD job-number and the IPP job-id, and that the IPP Job-uri
is the printer's URI with the job-id concatenated on the end.
The mapper SHALL send data received in the IPP operation to the LPD The mapper SHALL send data received in the IPP operation to the LPD
printer by using the LPD receive-data-file sub-command. The mapper SHALL printer by using the LPD receive-data-file sub-command. The mapper SHALL
specify the exact number of bytes being transmitted in the number-of- specify the exact number of bytes being transmitted in the number-of-
bytes field of the receive-data-file sub-command. It SHALL NOT use a bytes field of the receive-data-file sub-command. It SHALL NOT use a
value of 0 in this field. value of 0 in this field.
If the mapper, while it is transmitting a receive-a-printer-job command If the mapper, while it is transmitting a receive-a-printer-job command
or sub-command, either detects that its IPP connection has closed or or sub-command, either detects that its IPP connection has closed or
receives a Cancel-Job operation, the mapper SHALL terminate the LPD job receives a Cancel-Job operation, the mapper SHALL terminate the LPD job
either with the abort sub-command or the remove-jobs command. either with the abort sub-command or the remove-jobs command.
ISSUE: error code conversion. ISSUE: error code conversion.
5.3 Print-URI 5.2 Print-URI
The mapper SHALL handle this operation in the same way as a Print-Job The mapper SHALL handle this operation in the same way as a Print-Job
operation except that it SHALL obtain data referenced by the "document- operation except that it SHALL obtain data referenced by the "document-
uri" parameter and SHALL then treat that data as if it had been received uri" parameter and SHALL then treat that data as if it had been received
via a Print-Job operation. via a Print-Job operation.
Jacobs, Martin Expires January 30, 1998 5.3 Validate-Job
5.4 Validate-Job
The mapper SHALL perform this operation directly. Because LPD supports The mapper SHALL perform this operation directly. Because LPD supports
very few attributes, this operation doesn't have much to check. very few attributes, this operation doesn't have much to check.
5.5 Create-Job Jacobs, Martin Expires May 20, 1998
5.4 Create-Job
The mapper SHALL handle this operation like Print-Job, except The mapper SHALL handle this operation like Print-Job, except
. the mapper SHALL send the control file after it has received . the mapper SHALL send the control file after it has received
the last Send-Document or Send-URI operation because the the last Send-Document or Send-URI operation because the
control file contains all the document-name and document- control file contains all the document-name and document-
format values specified in the Send-Document and Send-URI format values specified in the Send-Document and Send-URI
operations. operations.
. the mapper SHALL perform one receive-data-file sub-command for . the mapper SHALL perform one receive-data-file sub-command for
each Send-Document or Send-URI operation received and in the each Send-Document or Send-URI operation received and in the
same order received. same order received.
. the mapper SHALL send the control file either before all data . the mapper SHALL send the control file either before all data
files or after all data files. files or after all data files.
(See the note in the section on Print-Job about the dilemma of (See the note in the section on Print-Job about the dilemma of
sending the control file either before or after the data sending the control file either before or after the data
files. files.
5.6 Send-Document 5.5 Send-Document
The mapper performs a receive-data-file sub-command on the received The mapper performs a receive-data-file sub-command on the received
data. See the preceding section 5.5 "Create-Job" for the details. data. See the preceding section 5.4 "Create-Job" for the details.
5.7 Send-URI 5.6 Send-URI
The mapper SHALL obtain the data referenced by the "document-uri" The mapper SHALL obtain the data referenced by the "document-uri"
parameter, and SHALL then treat that data as if it had been received via parameter, and SHALL then treat that data as if it had been received via
a Send-Document operation. See the preceding section 5.6 "Send-Document" a Send-Document operation. See the preceding section 5.5 "Send-Document"
for the details. for the details.
5.8 Cancel-Job 5.7 Cancel-Job
The mapper SHALL perform a remove-jobs command with the following The mapper SHALL perform a remove-jobs command with the following
parameters: parameters:
. the printer is the one containing the job specified by the IPP . the printer is the one to which the job was submitted, that is
job-uri, the IPP printer-uri is mapped to an LPD printer-name by the
same mechanism as for all commands. ,
. the agent is the authenticated user-name of the IPP client, . the agent is the authenticated user-name of the IPP client,
. the job-number is the one corresponding to the IPP job-uri . the job-number is the job-id returned by the Print-Job
parameter. command, that is, the LPD job-number has the same value as the
IPP job-id for likely implementations. .
NOTE: This specification does not specify how the mapper maps the IPP
"job-uri" to the LPD printer-name or LPD job-number.
Jacobs, Martin Expires January 30, 1998
ISSUE: the model needs to offer a solution for mapping jobs to printers
either with a new job attribute "printer-uri" or with all operation
targets being a printer-uri.
5.9 Get-Attributes 5.8 Get-Attributes
LPD severely limits the set of attributes that the mapper is able to LPD severely limits the set of attributes that the mapper is able to
return in its response for this operation. return in its response for this operation.
When the mapper receives a Get-Attributes operation for a printer When the mapper receives a Get-Attributes operation for a printer
object, it SHALL support, at most, the following printer attributes: object, it SHALL support, at most, the following printer attributes:
Jacobs, Martin Expires May 20, 1998
. printer-state . printer-state
. printer-state-reasons . printer-state-reasons
When the mapper receives a Get-Attributes operation for a job object, it When the mapper receives a Get-Attributes operation for a job object, it
SHALL support, at most, the following job attributes: SHALL support, at most, the following job attributes:
. number-of-intervening-jobs . number-of-intervening-jobs
. job-originating-user . job-originating-user-name
. job-uri . job-id
. job-originating-host
. document-name . document-name
. job-k-octets . job-k-octets
. copies . copies
The mapper uses either the long or short form of the "send queue state" The mapper uses either the long or short form of the "send queue state"
command. If it receives a request for the "job-originating-host" or command. If it receives a request for the "job-k-octets" or "copies"
"copies" and supports those attribute it SHALL use the long form; and supports the attribute it SHALL use the long form; otherwise, it
otherwise, it SHALL use the short form. SHALL use the short form.
Note: the value of job-k-octets is the value in the short form, but it Note: the value of job-k-octets is the value in the short form divided
can be computed from the copies and file size fields in the long form. by the number of "copies" which is on the long form only. Its value can
also be determined by adding the "size" field values for each document
in the job in the long form.
The mapper SHALL assume that the LPD response that it receives has the The mapper SHALL assume that the LPD response that it receives has the
format and information specified in section 3.3 "Send queue state format and information specified in section 3.3 "Send queue state
(short)" and section 3.4 "Send queue state (long)". The mapper SHALL (short)" and section 3.4 "Send queue state (long)". The mapper SHALL
determine the value of each requested attribute by using the inverse of determine the value of each requested attribute by using the inverse of
the mapping specified in the two aforementioned sections. the mapping specified in the two aforementioned sections.
Note: when the mapper receives the Get-Attributes operation for a Note: when the mapper receives the Get-Attributes operation for a
printer, it can determine the response from the printer-status line printer, it can determine the response from the printer-status line
without examining the rest of the LPD response. When the mapper receives without examining the rest of the LPD response. When the mapper receives
the Get-Attributes operation for a job and uses the LPD short form, it the Get-Attributes operation for a job and uses the LPD short form, it
can determine the response from the single line that pertains to the job can determine the response from the single line that pertains to the job
specified by the Get-Attributes operation. specified by the Get-Attributes operation.
NOTE: For Get-Attributes of a job, this specification does not specify NOTE: for Get-Attributes of a job, the mapper can use its correspondence
how the mapper maps the IPP "job-uri" to the LPD printer-name or LPD between the IPP job-id, job-uri and the LPD job-number.
job-number.
Jacobs, Martin Expires January 30, 1998
5.10 Get-Jobs 5.9 Get-Jobs
The mapper SHALL perform this operation in the same way as Get- The mapper SHALL perform this operation in the same way as Get-
Attributes of a printer except that the mapper converts the job-lines, Attributes of a printer except that the mapper converts the job-lines,
and the IPP response contains one job object for each job in the LPD and the IPP response contains one job object for each job in the LPD
response.. response..
6. Mapping of IPP Parameters to LPD Control File Lines 6. Mapping of IPP Parameters to LPD Control File Lines
This section describes the mapping from IPP operation input parameters This section describes the mapping from IPP operation input parameters
to LPD control file lines (called `functions'). The mapper receives the to LPD control file lines (called `functions'). The mapper receives the
Jacobs, Martin Expires May 20, 1998
IPP operation input parameters via the IPP operation. Each of the IPP IPP operation input parameters via the IPP operation. Each of the IPP
operation input parameters appear as sub-sections of section 3 and 4.2 operation input parameters appear as sub-sections of section 3 and 4.2
in the IPP model document [1]. in the IPP model document [ipp-mod].
In the context of LPD control file lines, the text operands have a In the context of LPD control file lines, the text operands have a
maximum length of 31 or 99 while IPP input parameters have a maximum of maximum length of 31 or 99 while IPP input parameters have a maximum of
255 characters. Therefore, there may be some data loss if the IPP 255 characters. Therefore, there may be some data loss if the IPP
parameters exceed the maximum length of the LPD equivalent operands. parameters exceed the maximum length of the LPD equivalent operands.
The mapper converts each supported IPP parameter to its corresponding The mapper converts each supported IPP parameter to its corresponding
LPD function as defined by tables in the subsections that follow. These LPD function as defined by tables in the subsections that follow. These
subsections group functions according to whether they are: subsections group functions according to whether they are:
skipping to change at page 17, line 49 skipping to change at page 17, line 37
6.1 Required Job Functions 6.1 Required Job Functions
The mapper SHALL include the following LPD functions with each job, and The mapper SHALL include the following LPD functions with each job, and
they SHALL have the specified value. They SHALL be the first functions they SHALL have the specified value. They SHALL be the first functions
in the control file and they SHALL be in the order "H" and then "P". in the control file and they SHALL be in the order "H" and then "P".
IPP LPD function IPP LPD function
name value name value description name value name value description
(in security layer) h H gateway host Originating Host (perhaps in security h H gateway host Originating Host
layer)
(in security layer) u P u User identification (in security layer) u P u User identification
A mapper SHALL sends its own host rather than the client's host, because A mapper SHALL sends its own host rather than the client's host, because
some LPD systems require that it be the same as the host from which the some LPD systems require that it be the same as the host from which the
remove-jobs command comes. A mapper MAY send its own user name as user remove-jobs command comes. A mapper MAY send its own user name as user
identification rather than the client user. But in any case, the values identification rather than the client user. But in any case, the values
sent SHALL be compatible with the LPD remove-jobs operation. sent SHALL be compatible with the LPD remove-jobs operation.
Jacobs, Martin Expires January 30, 1998
6.2 Optional Job Functions 6.2 Optional Job Functions
The mapper MAY include the following LPD functions with each job. They The mapper MAY include the following LPD functions with each job. They
SHALL have the specified value if they are sent. These functions, if SHALL have the specified value if they are sent. These functions, if
present, SHALL follow the require job functions, and they SHALL precede present, SHALL follow the require job functions, and they SHALL precede
the required document functions. the required document functions.
IPP attribute LPD function IPP attribute LPD function
Jacobs, Martin Expires May 20, 1998
name value nam value description name value nam value description
e e
job-name j J j Job name for banner job-name j J j Job name for banner
page page
job-sheets `standard' L u Print banner page job-sheets `standard' L u Print banner page
job-sheets `none' omit `L' function job-sheets `none' omit `L' function
notification- `job-completion' user Mail When Printed Note: `L' has special meaning when it is omitted. If `J' is omitted,
user`@' M events `mailto://' some undefined behavior occurs with respect to the banner page.
notification- host
method
Note: `L' has special meaning when it is omitted. If `M' is omitted,
there is no notification. If `J' is omitted, some undefined behavior
occurs with respect to the banner page.
Note: the `user' for the `M' function comes from a substring of the
notification-method's value.
6.3 Required Document Functions 6.3 Required Document Functions
The mapper SHALL include one set of the following LPD functions with The mapper SHALL include one set of the following LPD functions with
each document, and they SHALL have the specified values. For each each document, and they SHALL have the specified values. For each
document, the order of the functions SHALL be `f', `U' and then `N', document, the order of the functions SHALL be `f', `U' and then `N',
where `f' is replicated once for each copy. where `f' is replicated once for each copy.
IPP attribute LPD function IPP attribute LPD function
name value name value description name value name value description
document- `37' (langAutomatic) f fff Print formatted file document- 'application/octet- f fff Print formatted file
format or `6' (langPS). format stream' or
'application/PostScrip
t'
copies c replicate `f' `c' copies c replicate `f' `c'
times times
none U fff Unlink data file none U fff Unlink data file
document- n N n Name of source file document- n N n Name of source file
name name
Note: the value `fff' of the `f' and `U' functions is the name of the Note: the value `fff' of the `f' and `U' functions is the name of the
data file as transferred, e.g. "dfA123woden". data file as transferred, e.g. "dfA123woden".
Note: the mapper SHALL not send the `o' function Note: the mapper SHALL not send the `o' function
ISSUE: should we register DVI, troff or ditroff? ISSUE: should we register DVI, troff or ditroff?
Jacobs, Martin Expires January 30, 1998
If the mapper receives no "best-effort" or it has a value of false, then If the mapper receives no "best-effort" or it has a value of false, then
the mapper SHALL reject the job if it specifies attributes or attribute the mapper SHALL reject the job if it specifies attributes or attribute
values that are not among those supported in the above tables. values that are not among those supported in the above tables.
Below is an example of the minimal control file for a job with three Below is an example of the minimal control file for a job with three
copies of two files `foo' and `bar': copies of two files `foo' and `bar':
H tiger H tiger
P jones P jones
f dfA123woden f dfA123woden
f dfA123woden f dfA123woden
f dfA123woden f dfA123woden
U dfA123woden U dfA123woden
N foo N foo
f dfB123woden f dfB123woden
Jacobs, Martin Expires May 20, 1998
f dfB123woden f dfB123woden
f dfB123woden f dfB123woden
U dfB123woden U dfB123woden
N bar N bar
7. References 7. Copyright Notice
[1] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, "Internet This document and translations of it may be copied and furnished to
Printing Protocol/1.0: Model and Semantics", <draft-ietf-ipp-model- others, and derivative works that comment on or otherwise explain it or
02.txt>, July 1997. assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
[2] R. Herriot, S. Butler, P. Moore, R. Turner, "Internet Printing The limited permissions granted above are perpetual and will not be
Protocol/1.0: Protocol specification", <draft-ietf-ipp-protocol-00.txt>, revoked by the Internet Society or its successors or assigns.
July 1997.
[3] L. McLaughlin, "Line Printer Daemon Protocol", RFC 1179, August This document and the information contained herein is provided on an "AS
1990. IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS 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.
[4] Smith, R., Wright, F., Hastings, T., Zilles, S., and Gyllenskog, J., 8. References
"Printer MIB", RFC 1759, March 1995.
[5] S. Bradner, "Key words for use in RFCs to Indicate Requirement [ipp-mod] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
Levels", RFC 2119 , March 1997 "Internet Printing Protocol/1.0: Model and Semantics", <draft-
ietf-ipp-model-07.txt>, November 1997.
[6] D. Crocker et al., "Augmented BNF for Syntax Specifications: ABNF", [ipp-pro] R. Herriot, S. Butler, P. Moore, R. Turner, "Internet
draft-ietf-drums-abnf-03.txt. Printing Protocol/1.0: Protocol specification", <draft-ietf-ipp-
protocol-03.txt>, November 1997.
8. Author's Addresses [rfc1179] L. McLaughlin, "Line Printer Daemon Protocol", RFC 1179,
August 1990.
[rfc1759] Smith, R., Wright, F., Hastings, T., Zilles, S., and
Gyllenskog, J., "Printer MIB", RFC 1759, March 1995.
[rfc2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119 , March 1997
[abnf] D. Crocker et al., "Augmented BNF for Syntax Specifications:
ABNF", draft-ietf-drums-abnf-05.txt.
Jacobs, Martin Expires May 20, 1998
9. Author's Addresses
Robert Herriot (editor) Norm Jacobs Robert Herriot (editor) Norm Jacobs
Sun Microsystems Inc. Sun Microsystems Inc. Sun Microsystems Inc. Sun Microsystems Inc.
901 San Antonio.Road., MPK-17 1430 Owl Ridge Rd. 901 San Antonio.Road., MPK-17 1430 Owl Ridge Rd.
Mountain View, CA 94043 Colorado Springs, CO 80919 Mountain View, CA 94043 Colorado Springs, CO 80919
Phone: 650-786-8995 Phone: 719-532-9927 Phone: 650-786-8995 Phone: 719-532-9927
Fax: 650-786-7077 Fax: 719-535-0956 Fax: 650-786-7077 Fax: 719-535-0956
Email: robert.herriot@eng.sun.com Email: Email: robert.herriot@eng.sun.com Email:
Norm.Jacobs@Central.sun.com Norm.Jacobs@Central.sun.com
Jacobs, Martin Expires January 30, 1998
Thomas N. Hastings Jay Martin Thomas N. Hastings Jay Martin
Xerox Corporation Underscore, Inc. Xerox Corporation Underscore, Inc.
701 S. Aviation Blvd., ESAE-231 41-C Sagamore Park Road 701 S. Aviation Blvd., ESAE-231 41-C Sagamore Park Road
El Segundo, CA 90245 Hudson, NH 03051-4915 El Segundo, CA 90245 Hudson, NH 03051-4915
Phone: 310-333-6413 Phone: 603-889-7000 Phone: 310-333-6413 Phone: 603-889-7000
Fax: 310-333-5514 Fax: 603-889-2699 Fax: 310-333-5514 Fax: 603-889-2699
EMail: hastings@cp10.es.xerox.com Email: jkm@underscore.com EMail: hastings@cp10.es.xerox.com Email: jkm@underscore.com
9. Appendix A: ABNF Syntax for response of Send-queue-state (short) 10. Appendix A: ABNF Syntax for response of Send-queue-state (short)
The syntax in ABNF for the response to the LPD command `send-queue-state The syntax in ABNF for the response to the LPD command `send-queue-state
(long)' is: (long)' is:
status-response = empty-queue / nonempty-queue status-response = empty-queue / nonempty-queue
empty-queue = "no-entries" LF empty-queue = "no-entries" LF
nonempty-queue = printer-status LF heading LF *(job LF) nonempty-queue = printer-status LF heading LF *(job LF)
printer-status = OK-status / error-status printer-status = OK-status / error-status
OK-status = printer-name SP "ready and printing" LF OK-status = printer-name SP "ready and printing" LF
error-status = < implementation dependent status information > error-status = < implementation dependent status information >
heading = "Rank" 3SP Owner 6SP "Job" 13SP "Files" heading = "Rank" 3SP "Owner" 6SP "Job" 13SP "Files"
23SP "Total Size" LF 23SP "Total Size" LF
; the column headings and their values below begin ; the column headings and their values below begin
at the columns at the columns
; 1, 8, 19, 35 and 63 ; 1, 8, 19, 35 and 63
job = rank *SP owner *SP job *SP files *SP total-size "bytes" job = rank *SP owner *SP job *SP files *SP total-size "bytes"
; jobs are in order of oldest to newest ; jobs are in order of oldest to newest
rank = "active" / "1st" / "2nd" / "3rd" / integer "th" rank = "active" / "1st" / "2nd" / "3rd" / integer "th"
; job that is printing is "active" ; job that is printing is "active"
; other values show position in the queue ; other values show position in the queue
owner = <user name of person who submitted the job> owner = <user name of person who submitted the job>
job = 1*3DIGIT ; job-number job = 1*3DIGIT ; job-number
files = <file name> *( "," <file name>) ; truncated to 24 characters files = <file name> *( "," <file name>) ; truncated to 24 characters
total-size = 1*DIGIT ; combined size in bytes of all documents total-size = 1*DIGIT ; combined size in bytes of all documents
10. Appendix B: ABNF Syntax for response of Send-queue-state (long) 11. Appendix B: ABNF Syntax for response of Send-queue-state (long)
The syntax in ABNF for the response to the LPD command `send-queue-state The syntax in ABNF for the response to the LPD command `send-queue-state
(long)' is: (long)' is:
Jacobs, Martin Expires May 20, 1998
status-response = empty-queue / nonempty-queue status-response = empty-queue / nonempty-queue
empty-queue = "no-entries" LF empty-queue = "no-entries" LF
nonempty-queue = printer-status LF *job nonempty-queue = printer-status LF *job
printer-status = OK-status / error-status printer-status = OK-status / error-status
OK-status = printer-name SP "ready and printing" LF OK-status = printer-name SP "ready and printing" LF
error-status = < implementation dependent status information > error-status = < implementation dependent status information >
job = LF line-1 LF line-2 LF job = LF line-1 LF line-2 LF
line-1 = owner ":" SP rank 1*SP "[job" job SP host "]" line-1 = owner ":" SP rank 1*SP "[job" job SP host "]"
line-2 = file-name 1*SP document-size "bytes" line-2 = file-name 1*SP document-size "bytes"
; jobs are in order of oldest to newest ; jobs are in order of oldest to newest
rank = "active" / "1st" / "2nd" / "3rd" / integer "th" rank = "active" / "1st" / "2nd" / "3rd" / integer "th"
Jacobs, Martin Expires January 30, 1998
; job that is printing is "active" ; job that is printing is "active"
; other values show position in the queue ; other values show position in the queue
owner = <user name of person who submitted the job> owner = <user name of person who submitted the job>
job = 1*3DIGIT job = 1*3DIGIT
file-name = [ 1*DIGIT "copies of" SP ] <file name> file-name = [ 1*DIGIT "copies of" SP ] <file name>
; truncated to 24 characters ; truncated to 24 characters
document-size = 1*DIGIT ;size of single copy of the document. document-size = 1*DIGIT ;size of single copy of the document.
11. Appendix C: Unsupported LPD functions 12. Appendix C: Unsupported LPD functions
The follow LPD functions have no IPP equivalent. The LPD-to-IPP mapper The follow LPD functions have no IPP equivalent. The LPD-to-IPP mapper
ignores them and the IPP-to-LPD mapper does not send them. ignores them and the IPP-to-LPD mapper does not send them.
LPD command LPD command
name description name description
C Class for banner page C Class for banner page
I Indent Printing I Indent Printing
H Host of client
M Mail when printed
S Symbolic link data S Symbolic link data
T Title for pr T Title for pr
W Width of output W Width of output
1 troff R font 1 troff R font
2 troff I font 2 troff I font
3 troff B font 3 troff B font
4 troff S font 4 troff S font
The follow LPD functions specify document-formats which have no IPP The follow LPD functions specify document-formats which have no IPP
equivalent, unless someone registers them. The LPD-to-IPP mapper rejects equivalent, unless someone registers them. The LPD-to-IPP mapper rejects
skipping to change at page 21, line 46 skipping to change at page 22, line 4
LPD command LPD command
name description name description
c Plot CIF file c Plot CIF file
d Print DVI file d Print DVI file
g Plot file g Plot file
k reserved for Kerberized clients and servers k reserved for Kerberized clients and servers
n Print ditroff output file n Print ditroff output file
p Print file with 'pr' format p Print file with 'pr' format
r File to print with FORTRAN carriage control r File to print with FORTRAN carriage control
Jacobs, Martin Expires May 20, 1998
t Print troff output file t Print troff output file
v Print raster file v Print raster file
z reserved for future use with the Palladium z reserved for future use with the Palladium
print system print system
ISSUE: we may move some of these to the supported list. ISSUE: we may move some of these to the supported list.
Jacobs, Martin Expires January 30, 1998 Jacobs, Martin Expires May 20, 1998
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/