draft-ietf-ipp-ops-set2-02.txt   draft-ietf-ipp-ops-set2-03.txt 
Internet Printing Protocol WG Carl Kugler Internet Printing Protocol WG Carl Kugler
INTERNET-DRAFT H. Lewis INTERNET-DRAFT H. Lewis
<draft-ietf-ipp-ops-set2-02.txt> IBM Corporation <draft-ietf-ipp-ops-set2-03.txt> IBM Corporation
T. Hastings (editor) Updates: RFC 2911 T. Hastings (editor)
Classification: Proposed Standard Xerox Corporation [Target Category: standards track Xerox Corporation
August 15, 2000 Expires: January 17, 2002 July 17, 2001
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
Job and Printer Administrative Operations Job and Printer Administrative Operations
Copyright (C) The Internet Society (2001). All Rights Reserved.
Copyright (C) The Internet Society (2000). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with
provisions of Section 10 of [rfc2026]. Internet-Drafts are working all provisions of Section 10 of [rfc2026]. Internet-Drafts are
documents of the Internet Engineering Task Force (IETF), its areas, and working documents of the Internet Engineering Task Force (IETF), its
its working groups. Note that other groups may also distribute working areas, and its working groups. Note that other groups may also
documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference
or to cite them other than as "work in progress". material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed as The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document is a submission to the Internet Printing Protocol Working This document specifies the following 16 additional OPTIONAL
Group of the Internet Engineering Task Force (IETF). After approval, it operations for use with the Internet Printing Protocol/1.0 (IPP)
is intended to be on the IETF standards track. Comments should be [RFC2565, RFC2566] and IPP/1.1 [RFC2910, RFC2911]:
submitted to the ipp@pwg.org mailing list.
This document specifies the following 16 additional OPTIONAL operations
for use with the Internet Printing Protocol/1.0 (IPP) [RFC2565, RFC2566]
and IPP/1.1 [ipp-mod, ipp-pro]:
Printer operations: Job operations: Printer operations: Job operations:
Enable-Printer and Disable-Printer Reprocess-Job Enable-Printer and Disable-Printer Reprocess-Job
Pause-Printer-After-Current-Job Cancel-Current-Job Pause-Printer-After-Current-Job Cancel-Current-Job
Hold-New-Jobs and Release-Held-New-Jobs Suspend-Current-Job and Hold-New-Jobs and Release-Held-New- Suspend-Current-Job and
Resume-Job Jobs Resume-Job
Deactivate-Printer and Activate-Printer Promote-Job Deactivate-Printer and Activate- Promote-Job
Printer
Restart-Printer Schedule-Job-After Restart-Printer Schedule-Job-After
Shutdown-Printer and Startup-Printer Shutdown-Printer and Startup-Printer
New Job Description attributes: "original-requesting-user-name" New Job Description attributes: "original-requesting-user-name"
New Printer Description attributes: "subordinate-printers-supported" and New Printer Description attributes: "subordinate-printers-supported"
"parent-printers-supported". and "parent-printers-supported".
New "printer-state-reasons" values: 'hold-new-jobs' and 'deactivated'.
New "printer-state-reasons" values: 'hold-new-jobs' and
'deactivated'.
New "job-state-reasons" attribute values: 'job-suspended'. New "job-state-reasons" attribute values: 'job-suspended'.
New event keyword: 'forwarded-operation-failed'. New Job event keyword: 'job-forwarded-operation-failed'.
New status code: 'server-error-printer-is-deactivated'. New status code: 'server-error-printer-is-deactivated'.
Expires: February 15, 2001
The scope of IPP, is characterized in RFC2526 "Design Goals for an
Internet Printing Protocol". It is not the intent of this document to
revise or clarify this scope or conjecture as to the degree of industry
adoption or trends related to IPP within printing systems. It is the
intent of this document to extend the original set of operations - in a
similar fashion to the Set1 extensions which referred to IPP/1.0 and
were later incorporated into IPP/1.1.
The full set of IPP documents includes:
Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [IPP-MOD]
Internet Printing Protocol/1.1: Encoding and Transport [IPP-PRO]
Internet Printing Protocol/1.1: Implementer's Guide [IPP-IIG]
Mapping between LPD and IPP Protocols [RFC2569]
Internet Printing Protocol (IPP): IPP Event Notification
Specification [ipp-ntfy]
The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet. It identifies
requirements for three types of users: end users, operators, and
administrators. It calls out a subset of end user requirements that are
satisfied in IPP/1.0. A few OPTIONAL operator operations have been
added to IPP/1.1.
The "Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol" document describes IPP from a high level view,
defines a roadmap for the various documents that form the suite of IPP
specification documents, and gives background and rationale for the IETF
working group's major decisions.
The "Internet Printing Protocol/1.1: Model and Semantics", describes a
simplified model with abstract objects, their attributes, and their
operations that are independent of encoding and transport. It introduces
a Printer object and a Job object. The Job object optionally supports
multiple documents per Job. It also addresses security,
internationalization, and directory issues.
The "Internet Printing Protocol/1.1: Encoding and Transport" document is
a formal mapping of the abstract operations and attributes defined in
the model document onto HTTP/1.1 [RFC2616]. It defines the encoding
rules for a new Internet MIME media type called "application/ipp". This
document also defines the rules for transporting over HTTP a message
body whose Content-Type is "application/ipp". This document defines a
new scheme named 'ipp' for identifying IPP printers and jobs.
The "Internet Printing Protocol/1.1: Implementer's Guide" document gives
insight and advice to implementers of IPP clients and IPP objects. It
is intended to help them understand IPP/1.1 and some of the
considerations that may assist them in the design of their client and/or
IPP object implementations. For example, a typical order of processing
Expires: February 15, 2001
requests is given, including error checking. Motivation for some of the
specification decisions is also included.
The "Mapping between LPD and IPP Protocols" document gives some advice
to implementers of gateways between IPP and LPD (Line Printer Daemon)
implementations.
The "Internet Printing Protocol (IPP): IPP Event Notification
Specification" document defines the semantics for Subscription Creation
Operations and the requirements for other Delivery Method documents to
define a Delivery Method to carry an Event Notifications to a
Notification Recipient.
Expires: February 15, 2001
Table of Contents Table of Contents
1 Introduction........................................................6 1 Introduction.....................................................6
2 Terminology.........................................................6 2 Terminology......................................................6
2.1 Conformance Terminology.........................................6 2.1 Conformance Terminology........................................6
2.2 Other terminology...............................................6 2.2 Other terminology..............................................6
3 Definition of the Printer Operations................................7 3 Definition of the Printer Operations.............................7
3.1 The Disable and Enable Printer Operations.......................8 3.1 The Disable and Enable Printer Operations.....................10
3.1.1 Disable-Printer Operation 9 3.1.1 Disable-Printer Operation...................................10
3.1.2 Enable-Printer Operation 9 3.1.2 Enable-Printer Operation....................................11
3.2 The Pause and Resume Printer Operations........................10 3.2 The Pause and Resume Printer Operations.......................11
3.2.1 Pause-Printer-After-Current-Job operation 11 3.2.1 Pause-Printer-After-Current-Job operation...................12
3.3 Hold and Release New Jobs operations...........................12 3.3 Hold and Release New Jobs operations..........................14
3.3.1 Hold-New-Jobs operation 12 3.3.1 Hold-New-Jobs operation.....................................15
3.3.2 Release-Held-New-Jobs operation 13 3.3.2 Release-Held-New-Jobs operation.............................15
3.4 Deactivate and Activate Printer Operations.....................13 3.4 Deactivate and Activate Printer Operations....................16
3.4.1 Deactivate-Printer operation 14 3.4.1 Deactivate-Printer operation................................16
3.4.2 Activate-Printer operation 14 3.4.2 Activate-Printer operation..................................17
3.5 Restart-Printer, Shutdown-Printer, and Startup-Printer operations 3.5 Restart-Printer, Shutdown-Printer, and Startup-Printer operations
15 17
3.5.1 Restart-Printer operation 15 3.5.1 Restart-Printer operation...................................18
3.5.2 Shutdown-Printer Operation 16 3.5.2 Shutdown-Printer Operation..................................18
3.5.3 Startup-Printer operation 16 3.5.3 Startup-Printer operation...................................19
4 Definition of the Job Operations...................................17
4.1 Reprocess-Job Operation........................................18
4.2 Cancel-Current-Job Operation...................................18
4.3 Suspend and Resume Job operations..............................19
4.3.1 Suspend-Current-Job operation 19
4.3.2 Resume-Job operation 20
4.4 Job Scheduling Operations......................................21
4.4.1 Promote-Job operation 21
4.4.2 Schedule-Job-After operation 22
5 Additional status codes............................................23 4 Definition of the Job Operations................................20
5.1 'server-error-printer-is-deactivated' (0x050A).................23 4.1 Reprocess-Job Operation.......................................21
4.2 Cancel-Current-Job Operation..................................22
4.3 Suspend and Resume Job operations.............................23
4.3.1 Suspend-Current-Job operation...............................23
4.3.2 Resume-Job operation........................................24
4.4 Job Scheduling Operations.....................................25
4.4.1 Promote-Job operation.......................................25
4.4.2 Schedule-Job-After operation................................26
6 Use of Operation Attributes that are Messages from the Operator....23 5 Additional status codes.........................................27
5.1 'server-error-printer-is-deactivated' (0x050A)................28
7 New Printer Description Attributes.................................25 6 Use of Operation Attributes that are Messages from the Operator.28
7.1 subordinate-printers-supported (1setOf uri)....................25
7.2 parent-printers-supported (1setOf uri).........................26
8 Additional Values for "printer-state-reasons"......................26 7 New Printer Description Attributes..............................31
8.1 'hold-new-jobs'................................................26 7.1 subordinate-printers-supported (1setOf uri)...................31
8.2 'deactivated'..................................................26 7.2 parent-printers-supported (1setOf uri)........................31
9 Additional Values for "job-state-reasons"..........................26 8 Additional Values for the "printer-state-reasons" Printer
9.1 'job-suspended'................................................27 Description attribute.............................................32
8.1 'hold-new-jobs' value.........................................32
8.2 'deactivated' value...........................................32
10 Additional events.................................................27 9 Additional Values for the "job-state-reasons" Job Description
attribute.........................................................32
9.1 'job-suspended' value.........................................33
Expires: February 15, 2001 10 Additional events..............................................33
11 Use of the Printer object to represent IPP Printer Fan-Out and IPP 11 Use of the Printer object to represent IPP Printer Fan-Out and IPP
Printer Fan-In........................................................27 Printer Fan-In....................................................33
11.1IPP Printer Fan-Out............................................27 11.1 IPP Printer Fan-Out..........................................33
11.2IPP Printer Fan-In.............................................28 11.2 IPP Printer Fan-In...........................................34
11.3Printer object attributes used to represent Printer Fan-Out and 11.3Printer object attributes used to represent Printer Fan-Out and
Printer Fan-In......................................................28 Printer Fan-In....................................................34
11.4Subordinate Printer URI........................................28 11.4 Subordinate Printer URI......................................35
11.5Printer object attributes used to represent Output Device Fan-Out 11.5 Printer object attributes used to represent Output Device Fan-
29 Out 35
11.6Figures to show all possible configurations....................30 11.6 Figures to show all possible configurations..................37
11.7Forwarding requests............................................32 11.7 Forwarding requests..........................................40
11.7.1 Forwarding requests that affect Printer objects 32 11.7.1 Forwarding requests that affect Printer objects............40
11.7.2 Forwarding requests that affect Jobs 33 11.7.2 Forwarding requests that affect Jobs.......................42
11.8 Additional attributes to help with fan-out...................44
11.8.1 output-device-assigned (name(127)) Job Description attribute -
from [RFC2911].........................................45
11.8.2 original-requesting-user-name (name(MAX)) operation attribute
.......................................................45
12 Conformance Requirements..........................................35 12 Conformance Requirements.......................................45
13 IANA Considerations...............................................36 13 IANA Considerations............................................47
13.1 This section contains the registration information for IANA to
add to the various IPP Registries according to the procedures defined
in RFC 2911 [RFC2911] section 6 to cover the definitions in this
document. Attribute Registrations................................47
13.2 Attribute Value Registrations................................48
13.2.1 Additional Keyword Attribute Value Registrations for the "job-
state-reasons" attribute...............................48
13.2.2 Additional Keyword Attribute Value Registrations for the
"printer-state-reasons" attribute......................49
13.3 Additional Enum Attribute Value Registrations for the
"operations-supported" Printer Attribute..........................49
13.4 Additional keyword Attribute Value Registrations for the
"notify-events" Subscription Template Attribute...................50
13.5 Operation Registrations......................................50
13.6 Status code Registrations....................................51
14 Internationalization Considerations...............................36 14 Internationalization Considerations............................51
15 Security Considerations........................................51
15 Security Considerations...........................................36 16 Author's Addresses.............................................51
16 Author's Addresses................................................37 17 References.....................................................52
17 References........................................................37 18 Summary of Base IPP Documents..................................53
18 Appendix A: Full Copyright Statement..............................38 19 Appendix A: Full Copyright Statement...........................55
List of Tables List of Tables
Table 1 - Printer Operation Operation-Id assignments..................8
Table 2 - Pause and Resume Printer and Device Operations.............10 Table 1 - Printer Operation Operation-Id assignments...............9
Table 3 - Job operation Operation-Id assignments.....................17 Table 2 - Pause and Resume Printer Operations.....................12
Table 4 - Operation attribute support for Printer Operations.........24 Table 3 - State Transition Table for Pause-Printer-After-Current-Job
Table 5 - Operation attribute support for Job operations.............24 operation .....................................................14
Table 6 - Forwarding operations that affect Printer objects..........32 Table 4 - Job operation Operation-Id assignments..................21
Table 7 - Forwarding operations that affect Jobs objects.............33 Table 5 - Operation attribute support for Printer Operations......29
Table 8 - Conformance Requirement Dependencies for Operations........35 Table 6 - Operation attribute support for Job operations..........30
Table 9 - Conformance Requirement Dependencies for "printer-state- Table 7 - Forwarding operations that affect Printer objects.......41
reasons" Values..................................................36 Table 8 - Forwarding operations that affect Jobs objects..........43
Table 10 - Conformance Requirement Dependencies for "job-state-reasons" Table 9 - Conformance Requirement Dependencies for Operations.....46
Values...........................................................36 Table 10- Conformance Requirement Dependencies for "printer-state-
reasons" Values ...............................................47
Table 11- Conformance Requirement Dependencies for "job-state-
reasons" Values ...............................................47
List of Figures List of Figures
Figure 1 - Embedded Printer object...................................30
Figure 2 - Hosted Printer object.....................................30
Figure 3 - Output Device Fan-Out.....................................30
Figure 4 - Chained IPP Printer Objects...............................31
Figure 5 - IPP Printer Object Fan-Out................................31
Figure 6 - IPP Printer Object Fan-In.................................31
Expires: February 15, 2001 Figure 1 - Embedded Printer object................................38
Figure 2 - Hosted Printer object..................................38
Figure 3 - Output Device Fan-Out..................................38
Figure 4 - Chained IPP Printer Objects............................39
Figure 5 - IPP Printer Object Fan-Out.............................39
Figure 6 - IPP Printer Object Fan-In..............................40
1 Introduction 1 Introduction
The Internet Printing Protocol (IPP) is an application level protocol The Internet Printing Protocol (IPP) is an application level protocol
that can be used for distributed printing using Internet tools and that can be used for distributed printing using Internet tools and
technologies. IPP version 1.1 ([ipp-mod, ipp-pro]) focuses on end user technologies. IPP version 1.1 ([RFC2911, RFC2910]) focuses on end
functionality with a few administrative operations included. This user functionality with a few administrative operations included.
document defines additional OPTIONAL end user, operator, and This document defines additional OPTIONAL end user, operator, and
administrator operations used to control Jobs and Printers. In administrator operations used to control Jobs and Printers. In
addition, this document extends the semantic model of the Printer object addition, this document extends the semantic model of the Printer
by allowing them to be configured into trees and/or inverted trees that object by allowing them to be configured into trees and/or inverted
represent Printer object Fan-Out and Printer object Fan-In, trees that represent Printer object Fan-Out and Printer object Fan-
respectively. The special case of a tree with only a single Subordinate In, respectively. The special case of a tree with only a single
node represents Chained Printers. This document is a registration Subordinate node represents Chained Printers. This document is a
proposal for an extension to IPP/1.0 and IPP/1.1 following the registration proposal for an extension to IPP/1.0 and IPP/1.1
registration procedures in those documents. following the registration procedures in those documents.
The requirements and use cases for this document are defined in [ipp- The requirements and use cases for this document are defined in [ipp-
ops-admin-req]. That document also includes requirements and use cases ops-admin-req].
for operations on the Device object which is the subject of a third
document [ipp-device-ops]. That [ipp-device-ops] document is not needed
in order to implement the operations defined in this document.
2 Terminology 2 Terminology
This section defines terminology used throughout this document. This section defines terminology used throughout this document.
2.1 Conformance Terminology 2.1 Conformance Terminology
Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD
MAY, NEED NOT, and OPTIONAL, have special meaning relating to NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to
conformance as specified in RFC 2119 [RFC2119] and [ipp-mod] section conformance as defined in RFC 2119 [RFC2119] and [RFC2911] section
12.1. These terms refer to conformance to this document or a particular 12.1. If an implementation supports the extension defined in this
operation, if this document or operation is implemented. document, then these terms apply; otherwise, they do not. These
terms define conformance to this document only; they do not affect
The following specialization of these terms apply to this document: conformance to other documents, unless explicitly stated otherwise.
REQUIRED: if an implementation supports an operation described in
this document, it MUST support a REQUIRED feature described with
that operation.
OPTIONAL: if an implementation supports an operation described in
this document, it MAY support an OPTIONAL feature described with
that operation.
2.2 Other terminology 2.2 Other terminology
This document uses terms such as "attributes", "keywords", and This document uses terms such as "client", "Printer", "Job",
"support". These terms have special meaning and are defined in the "attributes", "keywords", and "support". These terms have special
model terminology [ipp-mod] section 12.2. meaning and are defined in the model terminology [RFC2911] section
12.2.
Expires: February 15, 2001
In addition, the following capitalized terms are defined: In addition, the following capitalized terms are defined:
IPP Printer object (or Printer for short) - a software abstraction IPP Printer object (or Printer for short) - a software abstraction
defined by [ipp-mod]. defined by [RFC2911].
Printer Operation - an operation whose target is an IPP Printer Printer Operation - an operation whose target is an IPP Printer
object and whose effect is on the Printer object. object and whose effect is on the Printer object.
Output Device - the physical imaging mechanism that an IPP Printer Output Device - the physical imaging mechanism that an IPP Printer
controls. Note: while this term is capitalized in this controls. Note: while this term is capitalized in this
specification (but not in [ipp-mod]), there is no formal object specification (but not in [RFC2911]), there is no formal object
called an Output Device defined in this document (or [ipp-mod]). called an Output Device defined in this document (or [RFC2911]).
Output Device Fan-Out - a configuration in which an IPP Printer Output Device Fan-Out - a configuration in which an IPP Printer
controls more that one output-device. controls more that one output-device.
Printer Fan-Out - a configuration in which an IPP Printer object Printer Fan-Out - a configuration in which an IPP Printer object
controls more than one Subordinate IPP Printer object. controls more than one Subordinate IPP Printer object.
Printer Fan-In - a configuration in which an IPP Printer object is Printer Fan-In - a configuration in which an IPP Printer object is
controlled by more than one IPP Printer object. controlled by more than one IPP Printer object.
Subordinate Printer - an IPP Printer object that is controlled by Subordinate Printer - an IPP Printer object that is controlled by
another IPP Printer object. Such a Subordinate Printer MAY have another IPP Printer object. Such a Subordinate Printer MAY have
one or more Subordinate Printers. one or more Subordinate Printers.
Leaf Printer - a Subordinate Printer that has no Subordinate Leaf Printer - a Subordinate Printer that has no Subordinate
Printers. Printers.
Non-Leaf Printer - an IPP Printer object that has one or more Non-Leaf Printer - an IPP Printer object that has one or more
Subordinate Printers. Subordinate Printers.
Chained Printer - a Non-Leaf Printer that has exactly one Subordinate Chained Printer - a Non-Leaf Printer that has exactly one Subordinate
Printer. Printer.
Job Creation operations - IPP operations that create a Job object: Job Creation operations - IPP operations that create a Job object:
Print-Job, Print-URI, and Create-Job. Print-Job, Print-URI, and Create-Job.
3 Definition of the Printer Operations 3 Definition of the Printer Operations
All Printer Operations are directed at Printer objects. A client MUST All Printer Operations are directed at Printer objects. A client
always supply the "printer-uri" operation attribute in order to identify MUST always supply the "printer-uri" operation attribute in order to
the correct target of the operation. These descriptions assume all of identify the correct target of the operation. These descriptions
the common semantics of IPP/1.1 Model and Semantics document [ipp-mod] assume all of the common semantics of IPP/1.1 Model and Semantics
section 3.1. document [RFC2911] section 3.1.
Expires: February 15, 2001
The Printer Operations defined in this document are summarized in Table The Printer Operations defined in this document are summarized in
1: Table 1:
Table 1 - Printer Operation Operation-Id assignments Table 1 - Printer Operation Operation-Id assignments
Operation Name Operati Brief description Operation Name Operation- Brief description
on-Id Id
Enable-Printer 0x22 Allows the target Printer to accept Job
Creation operations Enable-Printer 0x22 Allows the target Printer to accept
Job Creation operations
Disable-Printer 0x23 Prevents the target Printer from Disable-Printer 0x23 Prevents the target Printer from
accepting Job Creation operations accepting Job Creation operations
Pause-Printer- 0x24 Pause the Printer after the current job
After-Current- has been sent to the Output Device. Pause-Printer- Pause the Printer after the current
Job After-Current- job has been sent to the Output
Job 0x24 Device.
Hold-New-Jobs 0x25 Finishes processing all currently Hold-New-Jobs 0x25 Finishes processing all currently
pending jobs. Any new jobs are placed pending jobs. Any new jobs are
in the 'pending-held' state. placed in the 'pending-held' state.
Release-Held- 0x26 Release all jobs to the 'pending' state
New-Jobs that had been held by the effect of a Release-Held- 0x26 Release all jobs to the 'pending'
previous Hold-New-Jobs operation and New-Jobs state that had been held by the
condition the Printer to no longer hold effect of a previous Hold-New-Jobs
new jobs. operation and condition the Printer
to no longer hold new jobs.
Deactivate- 0x27 Puts the Printer into a read-only Deactivate- 0x27 Puts the Printer into a read-only
Printer deactivated state. Printer deactivated state.
Activate- 0x28 Restores the Printer to normal activity
Printer Activate- 0x28 Restores the Printer to normal
Printer activity
Restart-Printer 0x29 Restarts the target Printer and re- Restart-Printer 0x29 Restarts the target Printer and re-
initializes the software initializes the software
Shutdown- 0x2A Shuts down the target Printer so that Shutdown- 0x2A Shuts down the target Printer so that
Printer it cannot be restarted or queried Printer it cannot be restarted or queried
Startup-Printer 0x2B Starts up the instance of the Printer Startup-Printer 0x2B Starts up the instance of the Printer
object object
All of the operations in this document are OPTIONAL for an IPP object to All of the operations in this document are OPTIONAL for an IPP object
support. Unless the specification of an OPTIONAL operation requires to support. Unless the specification of an OPTIONAL operation
support of another OPTIONAL operation, conforming implementations may requires support of another OPTIONAL operation, conforming
support any combination of these operations. Many of the operations implementations may support any combination of these operations.
come in pairs and so both are REQUIRED if either one is implemented.
Many of the operations come in pairs and so both are REQUIRED if
either one is implemented.
3.1 The Disable and Enable Printer Operations 3.1 The Disable and Enable Printer Operations
This section defines the OPTIONAL Disable-Printer and Enable-Printer This section defines the OPTIONAL Disable-Printer and Enable-Printer
operations that stop and start the IPP Printer object from accepting new operations that stop and start the IPP Printer object from accepting
IPP jobs. If either of these operations are supported, both MUST be new IPP jobs. If either of these operations are supported, both MUST
supported. be supported.
These operations allow the operator to control whether or not the These operations allow the operator to control whether or not the
Printer will accept new Job Creation (Print-Job, Print-URI, and Create- Printer will accept new Job Creation (Print-Job, Print-URI, and
Job) operations. These operations have no other effect on the Printer, Create-Job) operations. These operations have no other effect on the
so that the Printer continues to accept all other operations and Printer, so that the Printer continues to accept all other operations
continues to schedule and process jobs normally. In other words, these and continues to schedule and process jobs normally. In other words,
operation control the "input of new jobs" to the IPP Printer while the these operation control the "input of new jobs" to the IPP Printer
while the Pause and Resume operations (see section 3.2) independently
Expires: February 15, 2001 control the "output of new jobs" from the IPP Printer to the Output
Device.
Pause and Resume operations (see section 3.2) independently control the
"output of new jobs" from the IPP Printer to the Output Device.
The Disable-Printer and Enable-Printer operations MUST NOT affect the
submission of jobs using other job submission protocols to the
associated Output Device; the Disable and Enable Device Operations (see
[ipp-device-ops]) are intended to stop the acceptance of all jobs by the
associated Output Device(s).
3.1.1 Disable-Printer Operation 3.1.1 Disable-Printer Operation
This OPTIONAL operation allows a client to stop the Printer object from This OPTIONAL operation allows a client to stop the Printer object
accepting new jobs, i.e., cause the Printer to reject subsequent Job from accepting new jobs, i.e., cause the Printer to reject subsequent
Creation operations and return the 'server-error-not-accepting-jobs' Job Creation operations and return the 'server-error-not-accepting-
status code. The Printer still accepts all other operations, including jobs' status code. The Printer still accepts all other operations,
Validate-Job, Send-Document and Send-URI operations. Thus a Disable- including Validate-Job, Send-Document and Send-URI operations. Thus
Printer operation allows a client to continue submitting multiple a Disable-Printer operation allows a client to continue submitting
documents of a multiple document job if the Create-Job operation had multiple documents of a multiple document job if the Create-Job
already been accepted. All previously created or submitted Jobs and operation had already been accepted. All previously created or
currently processing Jobs continue unaffected. submitted Jobs and currently processing Jobs continue unaffected.
The IPP Printer MUST accept the request in any state. The Printer sets The IPP Printer MUST accept the request in any state. The Printer
the value of its "printer-is-accepting-jobs" READ-ONLY Printer sets the value of its "printer-is-accepting-jobs" READ-ONLY Printer
Description attribute to 'false' (see [ipp-mod] section 4.4.20), no Description attribute to 'false' (see [RFC2911] section 4.4.20), no
matter what the previous value was. This operation has no immediate or matter what the previous value was. This operation has no immediate
direct effect on the Printer's "printer-state" and "printer-state- or direct effect on the Printer's "printer-state" and "printer-state-
reasons" attributes. reasons" attributes.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Disable-Printer Request and Disable-Printer Response have the same The Disable-Printer Request and Disable-Printer Response have the
attribute groups and attributes as the Pause-Printer operation (see same attribute groups and attributes as the Pause-Printer operation
[ipp-mod] sections 3.2.7.1 and 3.2.7.2), including the new "printer- (see [RFC2911] sections 3.2.7.1 and 3.2.7.2), including the new
message-from-operator" operation attribute (see section 6). "printer-message-from-operator" operation attribute (see section 6).
3.1.2 Enable-Printer Operation 3.1.2 Enable-Printer Operation
This OPTIONAL operation allows a client to start the Printer object This OPTIONAL operation allows a client to start the Printer object
accepting jobs, i.e., cause the Printer to accept subsequent Job accepting jobs, i.e., cause the Printer to accept subsequent Job
Creation operations. The Printer still accepts all other operations. Creation operations. The Printer still accepts all other operations.
All previously submitted Jobs and currently processing Jobs continue All previously submitted Jobs and currently processing Jobs continue
unaffected. unaffected.
The IPP Printer MUST accept the request in any state. The Printer sets The IPP Printer MUST accept the request in any state. The Printer
the value of its "printer-is-accepting-jobs" READ-ONLY Printer sets the value of its "printer-is-accepting-jobs" READ-ONLY Printer
Description attribute to 'true' (see [ipp-mod] section 4.4.20), no Description attribute to 'true' (see [RFC2911] section 4.4.20), no
matter what the previous value was. This operation has no immediate or matter what the previous value was. This operation has no immediate
direction effect on the Printer's "printer-state" and "printer-state- or direction effect on the Printer's "printer-state" and "printer-
reasons" attributes. state-reasons" attributes.
Expires: February 15, 2001
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Enable-Printer Request and Enable-Printer Response have the same The Enable-Printer Request and Enable-Printer Response have the same
attribute groups and attributes as the Pause-Printer operation (see attribute groups and attributes as the Pause-Printer operation (see
[ipp-mod] sections 3.2.8.1 and 3.2.8.2), including the new "printer- [RFC2911] sections 3.2.8.1 and 3.2.8.2), including the new "printer-
message-from-operator" operation attribute (see section 6). message-from-operator" operation attribute (see section 6).
3.2 The Pause and Resume Printer Operations 3.2 The Pause and Resume Printer Operations
This section leaves the OPTIONAL IPP/1.1 Pause-Printer (see [ipp-mod] This section leaves the OPTIONAL IPP/1.1 Pause-Printer (see [RFC2911]
sections 3.2.7) to be ambiguous as to whether or not it stops the sections 3.2.7) to be ambiguous as to whether or not it stops the
Printer immediately or after the current job and defines the OPTIONAL Printer immediately or after the current job and defines the OPTIONAL
Pause-Printer-After-All-Current-Jobs operation to be after the current Pause-Printer-After-Current-Job operation to be after the current
job. These operations affect the scheduling of IPP jobs. If either of job. These operations affect the scheduling of IPP jobs. If either
these Pause Printer operations are supported, then the Resume-Printer of these Pause Printer operations are supported, then the Resume-
operation MUST be supported. Printer operation MUST be supported.
These operations allow the operator to control whether or not the These operations allow the operator to control whether or not the
Printer will send new IPP jobs to the associated Output Device(s) that Printer will send new IPP jobs to the associated Output Device(s)
the IPP Printer object represents. These operations have no other that the IPP Printer object represents. These operations have no
effect on the Printer, so that the Printer continues to accept all other effect on the Printer, so that the Printer continues to accept
operations. In other words, these operation control the "output of new all operations. In other words, these operation control the "output
jobs" to the Output Device(s) while the Disable and Enable Printer of new jobs" to the Output Device(s) while the Disable and Enable
Operations (see section 3.1) independently control the "input of new Printer Operations (see section 3.1) independently control the "input
jobs" to the IPP Printer. of new jobs" to the IPP Printer.
The Pause and Resume Printer Operations MUST NOT affect jobs that were
submitted using other job submission protocols to the associated Output
Device; the Pause and Resume Device Operations (see [ipp-device-ops])
are intended to stop the acceptance of all jobs by the associated Output
Device(s).
This document and [ipp-device-ops] define distinct operations in order
to disambiguate the Pause-Printer operation as shown in Table 2. The
Printer Operations affect only Jobs submitted using IPP, while the
Device Operations affect all jobs no matter what job submission protocol
was used to submit them to the Output Device.
Table 2 - Pause and Resume Printer and Device Operations Table 2 - Pause and Resume Printer Operations
Pause and Resume Printer Description Pause and Resume Printers Description
and Device Operations
IPP/1.1 Pause Printer Stops the IPP Printer from sending IPP/1.1 Pause Printer Stops the IPP Printer from sending
new IPP Jobs to the Output Device(s) new IPP Jobs to the Output Device(s)
either immediately or after the either immediately or after the
current job completes, depending on current job completes, depending on
implementation, as defined in [ipp- implementation, as defined in
mod]. [RFC2911].
Pause-Printer-After- Stops the IPP Printer from sending Pause-Printer-After- Stops the IPP Printer from sending
Current-Job new IPP Jobs to the Output Device(s) Current-Job new IPP Jobs to the Output Device(s)
Expires: February 15, 2001
Pause and Resume Printer Description
and Device Operations
after the current jobs finish after the current jobs finish
Resume-Printer Starts the IPP Printer sending IPP Resume-Printer Starts the IPP Printer sending IPP
Jobs to the Output Device again. Jobs to the Output Device again.
3.2.1 Pause-Printer-After-Current-Job operation 3.2.1 Pause-Printer-After-Current-Job operation
This OPTIONAL operation allows a client to stop the Printer object from This OPTIONAL operation allows a client to stop the Printer object
starting to send IPP jobs to any of its Output Devices or Subordinate from starting to send IPP jobs to any of its Output Devices or
Printers. If the IPP Printer is in the middle of sending an IPP job to Subordinate Printers. If the IPP Printer is in the middle of sending
an Output Device or Subordinate Printer, the IPP Printer MUST complete an IPP job to an Output Device or Subordinate Printer, the IPP
sending that Job. However, after receiving this operation, the IPP Printer MUST complete sending that Job. However, after receiving
Printer MUST NOT start to send any additional IPP jobs to any of its this operation, the IPP Printer MUST NOT start to send any additional
Output Devices or Subordinate Printers. In addition, after having IPP jobs to any of its Output Devices or Subordinate Printers. In
received this operation, the IPP Printer MUST NOT start processing any addition, after having received this operation, the IPP Printer MUST
more jobs, so additional jobs MUST NOT enter the 'processing' state. NOT start processing any more jobs, so additional jobs MUST NOT enter
the 'processing' state.
If the IPP Printer is not sending an IPP Job to the Output Device or If the IPP Printer is not sending an IPP Job to the Output Device or
Subordinate Printer (whether or not the Output Device or Subordinate Subordinate Printer (whether or not the Output Device or Subordinate
Printer is busy processing any jobs), the IPP Printer object transitions Printer is busy processing any jobs), the IPP Printer object
immediately to the 'stopped' state by setting its "printer-state" transitions immediately to the 'stopped' state by setting its
attribute to 'stopped', removing the 'moving-to-paused' value, if "printer-state" attribute to 'stopped', removing the 'moving-to-
present, from its "printer-state-reasons" attribute, and adding the paused' value, if present, from its "printer-state-reasons"
'paused' value to its "printer-state-reasons" attribute. attribute, and adding the 'paused' value to its "printer-state-
reasons" attribute.
If the implementation will take appreciable time to complete sending an If the implementation will take appreciable time to complete sending
IPP job that it has started sending to an Output Device or Subordinate an IPP job that it has started sending to an Output Device or
Printer, the IPP Printer adds the 'moving-to-paused' value to the Subordinate Printer, the IPP Printer adds the 'moving-to-paused'
Printer object's "printer-state-reasons" attribute (see section [ipp- value to the Printer object's "printer-state-reasons" attribute (see
mod] 4.4.12). When the IPP Printer has completed sending IPP jobs that section [RFC2911] 4.4.12). When the IPP Printer has completed
it was in the process of sending, the Printer object transitions to the sending IPP jobs that it was in the process of sending, the Printer
'stopped' state by setting its "printer-state" attribute to 'stopped', object transitions to the 'stopped' state by setting its "printer-
removing the 'moving-to-paused' value, if present, from its "printer- state" attribute to 'stopped', removing the 'moving-to-paused' value,
state-reasons" attribute, and adding the 'paused' value to its "printer- if present, from its "printer-state-reasons" attribute, and adding
state-reasons" attribute. the 'paused' value to its "printer-state-reasons" attribute.
This operation MUST NOT affect the acceptance of Job Creation requests This operation MUST NOT affect the acceptance of Job Creation
(see Disable-Printer section 3.1.1). requests (see Disable-Printer section 3.1.1).
For any jobs that are 'pending' or 'pending-held', the 'printer-stopped' For any jobs that are 'pending' or 'pending-held', the 'printer-
value of the jobs' "job-state-reasons" attribute also applies. However, stopped' value of the jobs' "job-state-reasons" attribute also
the IPP Printer NEED NOT update those jobs' "job-state-reasons" applies. However, the IPP Printer NEED NOT update those jobs' "job-
attributes and only need return the 'printer-stopped' value when those state-reasons" attributes and only need return the 'printer-stopped'
jobs are queried using the Get-Job-Attributes or Get-Jobs operations value when those jobs are queried using the Get-Job-Attributes or
(so-called "lazy evaluation"). Get-Jobs operations (so-called "lazy evaluation").
The IPP Printer MUST accept the request in any state and transition the The IPP Printer MUST accept the request in any state and transition
Printer to the indicated new "printer-state" and MUST add the indicated the Printer to the indicated new "printer-state" and MUST add the
value to "printer-state-reasons" attribute before returning as follows: indicated value to "printer-state-reasons" attribute before returning
as follows:
Table 3 - State Transition Table for Pause-Printer-After-Current-Job
operation
Expires: February 15, 2001
Current New "printer IPP Printer's response status Current New "printer IPP Printer's response status
"printer- "printer- -state- code and action: "printer- "printer- -state- code and action:
state" state" reasons" state" state" reasons"
REQUIRED/OPTIONAL state REQUIRED/OPTIONAL state
transition for a Printer to transition for a Printer to
support support
'idle' 'stopped' 'paused' REQUIRED: 'successful-ok' 'idle' 'stopped' 'paused' REQUIRED: 'successful-ok'
'processing' 'processing' 'moving- OPTIONAL: 'successful-ok'; 'processing' 'processing' 'moving- OPTIONAL: 'successful-ok';
to- Later, when the IPP Printer has to- Later, when the IPP Printer
paused' finished sending IPP jobs to an paused' has finished sending IPP jobs
Output Device, the "printer- to an Output Device, the
state" becomes 'stopped', and "printer-state" becomes
the 'paused' value replaces the 'stopped', and the 'paused'
'moving-to-paused' value in the value replaces the 'moving-to-
"printer-state-reasons" paused' value in the "printer-
attribute state-reasons" attribute
'processing' 'stopped' 'paused' REQUIRED: 'successful-ok'; the 'processing' 'stopped' 'paused' REQUIRED: 'successful-ok';
IPP Printer wasn't in the middle the IPP Printer wasn't in the
of sending an IPP job to an middle of sending an IPP job
Output Device to an Output Device
'stopped' 'stopped' 'paused' REQUIRED: 'successful-ok' 'stopped' 'stopped' 'paused' REQUIRED: 'successful-ok'
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Pause-Printer-After-Current-Job Request and Pause-Printer-After- The Pause-Printer-After-Current-Job Request and Pause-Printer-After-
Current-Job Response have the same attribute groups and attributes as Current-Job Response have the same attribute groups and attributes as
the Pause-Printer operation (see [ipp-mod] sections 3.2.7.1 and the Pause-Printer operation (see [RFC2911] sections 3.2.7.1 and
3.2.7.2), including the new "printer-message-from-operator" operation 3.2.7.2), including the new "printer-message-from-operator" operation
attribute (see section 6). attribute (see section 6).
3.3 Hold and Release New Jobs operations 3.3 Hold and Release New Jobs operations
This section defines operations to condition the Printer to hold any new This section defines operations to condition the Printer to hold any
jobs and to release them. new jobs and to release them.
3.3.1 Hold-New-Jobs operation 3.3.1 Hold-New-Jobs operation
This OPTIONAL operation allows a client to condition the Printer to This OPTIONAL operation allows a client to condition the Printer to
complete the current 'pending' and 'processing' IPP Jobs but not start complete the current 'pending' and 'processing' IPP Jobs but not
processing any subsequently created IPP Jobs. If the IPP Printer is in start processing any subsequently created IPP Jobs. If the IPP
the middle of sending an IPP job to an Output Device or Subordinate Printer is in the middle of sending an IPP job to an Output Device or
Printer, the IPP Printer MUST complete sending that Job. Furthermore, Subordinate Printer, the IPP Printer MUST complete sending that Job.
the IPP Printer MUST send all of the current 'pending' IPP Jobs to the Furthermore, the IPP Printer MUST send all of the current 'pending'
Output Device(s) or Subordinate IPP Printer object(s). Any subsequently IPP Jobs to the Output Device(s) or Subordinate IPP Printer
received Job Creation operations will cause the IPP Printer to put the object(s). Any subsequently received Job Creation operations will
Job into the 'pending-held' state with the 'job-held-on-create' value cause the IPP Printer to put the Job into the 'pending-held' state
being added to the job's "job-state-reasons" attribute. Thus all newly with the 'job-held-on-create' value being added to the job's "job-
accepted jobs will be automatically held by the Printer. state-reasons" attribute. Thus all newly accepted jobs will be
automatically held by the Printer.
Expires: February 15, 2001
When the Printer completes all of the 'pending' and 'processing' jobs, When the Printer completes all of the 'pending' and 'processing'
it enters the 'idle' state as usual. An operator that is monitoring jobs, it enters the 'idle' state as usual. An operator that is
Printer state changes will know when the Printer has completed all monitoring Printer state changes will know when the Printer has
current jobs because the Printer enters the 'idle' state. completed all current jobs because the Printer enters the 'idle'
state.
This operation MUST NOT affect the acceptance of Job Creation requests This operation MUST NOT affect the acceptance of Job Creation
(see Disable-Printer section 3.1.1), except to put the Jobs into the requests (see Disable-Printer section 3.1.1), except to put the Jobs
'pending-held' state, instead of the 'pending' or 'processing' state. into the 'pending-held' state, instead of the 'pending' or
'processing' state.
The IPP Printer MUST accept the request in any state, MUST NOT The IPP Printer MUST accept the request in any state, MUST NOT
transition the Printer to any other "printer-state", and MUST add the transition the Printer to any other "printer-state", and MUST add the
'hold-new-jobs' value to the Printer's "printer-state-reasons" attribute 'hold-new-jobs' value to the Printer's "printer-state-reasons"
(whether the value was present or not). attribute (whether the value was present or not).
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Hold-New-Jobs Request and Hold-New-Jobs Response have the same The Hold-New-Jobs Request and Hold-New-Jobs Response have the same
attribute groups and attributes as the Pause-Printer operation (see attribute groups and attributes as the Pause-Printer operation (see
[ipp-mod] sections 3.2.7.1 and 3.2.7.2), including the new "printer- [RFC2911] sections 3.2.7.1 and 3.2.7.2), including the new "printer-
message-from-operator" operation attribute (see section 6). message-from-operator" operation attribute (see section 6).
3.3.2 Release-Held-New-Jobs operation 3.3.2 Release-Held-New-Jobs operation
This OPTIONAL operation allows a client to undo the effect of a previous This OPTIONAL operation allows a client to undo the effect of a
Hold-New-Jobs operation. In particular, the Printer releases all of the previous Hold-New-Jobs operation. In particular, the Printer
jobs that it had held as a consequence of a Hold-New-Jobs operations, releases all of the jobs that it had held as a consequence of a Hold-
i.e., while the 'hold-new-jobs' value was present in the Printer's New-Jobs operations, i.e., while the 'hold-new-jobs' value was
"printer-state-reasons" attribute. In addition, the Printer MUST accept present in the Printer's "printer-state-reasons" attribute. In
this request in any state, MUST NOT transition the Printer to any other addition, the Printer MUST accept this request in any state, MUST NOT
"printer-state", and MUST remove the 'hold-new-jobs' value from its transition the Printer to any other "printer-state", and MUST remove
"printer-state-reasons" attribute (whether the value was present or not) the 'hold-new-jobs' value from its "printer-state-reasons" attribute
so that the Printer no longer holds newly created jobs. (whether the value was present or not) so that the Printer no longer
holds newly created jobs.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Release-Held-New-Jobs Request and Release-Held-New-Jobs Response The Release-Held-New-Jobs Request and Release-Held-New-Jobs Response
have the same attribute groups and attributes as the Pause-Printer have the same attribute groups and attributes as the Pause-Printer
operation (see [ipp-mod] sections 3.2.7.1 and 3.2.7.2), including the operation (see [RFC2911] sections 3.2.7.1 and 3.2.7.2), including the
new "printer-message-from-operator" operation attribute (see section 6). new "printer-message-from-operator" operation attribute (see section
6).
3.4 Deactivate and Activate Printer Operations 3.4 Deactivate and Activate Printer Operations
This section defines the OPTIONAL Deactivate-Printer and Activate- This section defines the OPTIONAL Deactivate-Printer and Activate-
Printer operations that stop and start the IPP Printer object from Printer operations that stop and start the IPP Printer object from
accepting all requests except queries and performing work. If either of accepting all requests except queries and performing work. If either
these operations are supported, both MUST be supported. of these operations are supported, both MUST be supported.
Expires: February 15, 2001
These operations allow the operator to put the Printer into a dormant These operations allow the operator to put the Printer into a dormant
read-only condition and to take it out of such a condition. These read-only condition and to take it out of such a condition. These
operations are a combination of the Deactivate and Pause operations, operations are a combination of the Deactivate and Pause operations,
plus preventing the acceptance of any other requests, except queries. plus preventing the acceptance of any other requests, except queries.
The Deactivate and Activate Printer Operations MUST NOT affect the
submission of jobs using other job submission protocols to the
associated Output Device; the Deactivate and Activate Device Operations
(see [ipp-device-ops]) are intended to stop the associated Output
Device(s) from performing work and accepting operations, except query
operations.
3.4.1 Deactivate-Printer operation 3.4.1 Deactivate-Printer operation
This OPTIONAL operation allows a client to stop the Printer object from This OPTIONAL operation allows a client to stop the Printer object
starting to send IPP jobs to any of its Output Devices or Subordinate from starting to send IPP jobs to any of its Output Devices or
Printers (Pause-Printer-After-Current-Job) and stop the Printer object Subordinate Printers (Pause-Printer-After-Current-Job) and stop the
from accepting any, but query requests. The Printer performs a Disable- Printer object from accepting any, but query requests. The Printer
Printer and a Pause-Printer-After-Current-Job operation immediately, performs a Disable-Printer and a Pause-Printer-After-Current-Job
including use of all of the "printer-state-reasons" if these two operation immediately, including use of all of the "printer-state-
operations cannot be completed immediately. In addition, the Printer reasons" if these two operations cannot be completed immediately. In
MUST immediately reject all requests, except Activate-Printer, queries addition, the Printer MUST immediately reject all requests, except
(Get-Printer-Attributes, Get-Job-Attributes, Get-Jobs, etc.), Send- Activate-Printer, queries (Get-Printer-Attributes, Get-Job-
Document, and Send-URI (so that partial job submission can be completed Attributes, Get-Jobs, etc.), Send-Document, and Send-URI (so that
- see section 3.1.1) and return the 'server-error-service-unavailable' partial job submission can be completed - see section 3.1.1) and
status code. return the 'server-error-service-unavailable' status code.
The IPP Printer MUST accept the request in any state. Immediately, the The IPP Printer MUST accept the request in any state. Immediately,
Printer MUST set the 'deactivated' value in its "printer-state-reasons" the Printer MUST set the 'deactivated' value in its "printer-state-
attribute. Note: neither the Disable-Printer nor the Pause-Printer- reasons" attribute. Note: neither the Disable-Printer nor the Pause-
After-Current-Job set the 'deactivated' value. Printer-After-Current-Job set the 'deactivated' value.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Deactivate-Printer Request and Deactivate-Printer Response have the The Deactivate-Printer Request and Deactivate-Printer Response have
same attribute groups and attributes as the Pause-Printer operation (see the same attribute groups and attributes as the Pause-Printer
[ipp-mod] sections 3.2.7.1 and 3.2.7.2), including the new "printer- operation (see [RFC2911] sections 3.2.7.1 and 3.2.7.2), including the
message-from-operator" operation attribute (see section 6). new "printer-message-from-operator" operation attribute (see section
6).
3.4.2 Activate-Printer operation 3.4.2 Activate-Printer operation
This OPTIONAL operation allows a client to undo the effects of the This OPTIONAL operation allows a client to undo the effects of the
Deactivate-Printer, i.e., allow the Printer object to start sending IPP Deactivate-Printer, i.e., allow the Printer object to start sending
jobs to any of its Output Devices or Subordinate Printers (Pause- IPP jobs to any of its Output Devices or Subordinate Printers (Pause-
Printer-After-Current-Job) and start the Printer object from accepting Printer-After-Current-Job) and start the Printer object from
any requests. The Printer performs an Enable-Printer and a Resume- accepting any requests. The Printer performs an Enable-Printer and a
Printer operation immediately. In addition, the Printer MUST Resume-Printer operation immediately. In addition, the Printer MUST
immediately start accepting all requests. immediately start accepting all requests.
Expires: February 15, 2001 The IPP Printer MUST accept the request in any state. Immediately,
the Printer MUST immediately remove the 'deactivated' value from its
The IPP Printer MUST accept the request in any state. Immediately, the
Printer MUST immediately remove the 'deactivated' value from its
"printer-state-reasons" attribute (whether present or not). "printer-state-reasons" attribute (whether present or not).
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Activate-Printer Request and Activate-Printer Response have the same The Activate-Printer Request and Activate-Printer Response have the
attribute groups and attributes as the Pause-Printer operation (see same attribute groups and attributes as the Pause-Printer operation
[ipp-mod] sections 3.2.7.1 and 3.2.7.2), including the new "printer- (see [RFC2911] sections 3.2.7.1 and 3.2.7.2), including the new
message-from-operator" operation attribute (see section 6). "printer-message-from-operator" operation attribute (see section 6).
3.5 Restart-Printer, Shutdown-Printer, and Startup-Printer operations 3.5 Restart-Printer, Shutdown-Printer, and Startup-Printer operations
This section defines the OPTIONAL Restart-Printer, Shutdown-Printer, and This section defines the OPTIONAL Restart-Printer, Shutdown-Printer,
Startup-Printer operations that initialize, shutdown, and startup the and Startup-Printer operations that initialize, shutdown, and startup
Printer object, respectively. Each of these operations is OPTIONAL and the Printer object, respectively. Each of these operations is
any combination MAY be supported. OPTIONAL and any combination MAY be supported.
The Restart-Printer, Shutdown-Printer, and Startup-Printer operations
MUST NOT affect the submission of jobs using other job submission
protocols to the associated Output Device; the Reset-Device and Power-
Off-Device Operations (see [ipp-device-ops]) are intended to initialize
or power off the associated Output Device(s).
3.5.1 Restart-Printer operation 3.5.1 Restart-Printer operation
This OPTIONAL operation allows a client to restart a Printer object This OPTIONAL operation allows a client to restart a Printer object
whose operation is in need of initialization because of incorrect or whose operation is in need of initialization because of incorrect or
erratic behavior, i.e., perform the effect of a software re-boot. The erratic behavior, i.e., perform the effect of a software re-boot.
implementation MUST attempt to save any information about Jobs and the The implementation MUST attempt to save any information about Jobs
Printer object before re-initializing. However, this operation MAY have and the Printer object before re-initializing. However, this
drastic consequences on the running system, so the operator should first operation MAY have drastic consequences on the running system, so the
try the Deactivate-Printer to minimize the effect on the current state client SHOULD first try the Deactivate-Printer operation to minimize
of the system. The effects of previous Disable-Printer, Pause Printer, the effect on the current state of the system. The effects of
and Deactivate-Printer operations are lost. previous Disable-Printer, Pause Printer, and Deactivate-Printer
operations are lost.
The IPP Printer MUST accept the request in any state. The Printer The IPP Printer MUST accept the request in any state. The Printer
object MUST initialize its Printer's "printer-state" to 'idle', remove object MUST initialize its Printer's "printer-state" to 'idle',
the state reasons from its "printer-state-reasons" attribute, and its remove the state reasons from its "printer-state-reasons" attribute,
"printer-is-accepting-jobs" attribute to 'true'. and its "printer-is-accepting-jobs" attribute to 'true'.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Restart-Printer Request and Restart-Printer Response have the same
attribute groups and attributes as the Pause-Printer operation (see
[ipp-mod] sections 3.2.8.1 and 3.2.8.2), including the new "printer-
message-from-operator" operation attribute (see section 6).
Expires: February 15, 2001 The Restart-Printer Request and Restart-Printer Response have the
same attribute groups and attributes as the Pause-Printer operation
(see [RFC2911] sections 3.2.8.1 and 3.2.8.2), including the new
"printer-message-from-operator" operation attribute (see section 6).
3.5.2 Shutdown-Printer Operation 3.5.2 Shutdown-Printer Operation
This OPTIONAL operation allows a client to shutdown a Printer, i.e., This OPTIONAL operation allows a client to shutdown a Printer, i.e.,
stop processing jobs and make the Printer object no longer available for stop processing jobs without losing any jobs and make the Printer
any operations using the IPP protocol without losing any jobs. There is object no longer available for any operations using the IPP protocol.
no way to bring the instance of the Printer object back to being used, There is no way to bring the instance of the Printer object back to
except for the Startup-Printer (see section 3.5.3) which starts up a new being used, except for the Startup-Printer (see section 3.5.3) which
instance of the Printer object for hosted implementations. The purpose starts up a new instance of the Printer object for hosted
of Shutdown-Printer is to shutdown the Printer for an extended period, implementations. The purpose of Shutdown-Printer is to shutdown the
not to reset the device(s) or modify a Printer attribute. See Restart- Printer for an extended period, not to reset the device(s) or modify
Printer (section 3.5.1), Startup-Printer (section ), and Reset-Device a Printer attribute. See Restart-Printer (section 3.5.1) and
[ipp-device-ops] for the way to initialize the software or reset the Startup-Printer (section 3.5.3) for the way to initialize the
Output Device(s). See the Disable-Printer operation (section 3.1) for a software. See the Disable-Printer operation (section 3.1) for a way
way for the client to stop the Printer from accepting Job Creation for the client to stop the Printer from accepting Job Creation
requests without stopping processing or shutting down. requests without stopping processing or shutting down.
The Printer MUST add the 'shutdown' value (see [ipp-mod] section 4.4.11) The Printer MUST add the 'shutdown' value (see [RFC2911] section
immediately to its "printer-state-reasons" Printer Description attribute 4.4.11) immediately to its "printer-state-reasons" Printer
and performs a Deactivate-Printer operation (see section 3.4.1) which Description attribute and performs a Deactivate-Printer operation
performs a Disable-Printer and Pause-Printer-After-Current-Job (see section 3.4.1) which performs a Disable-Printer and Pause-
operation). Printer-After-Current-Job operation).
Note: In order to shutdown the Printer after all the currently Note: In order to shutdown the Printer after all the currently
submitted jobs have completed, the operator issues a Disable-Printer submitted jobs have completed, the operator issues a Disable-Printer
operation (see section 3.1.1) and then waits until all the jobs have operation (see section 3.1.1) and then waits until all the jobs have
completed and the Printer goes into the 'idle' state before issuing the completed and the Printer goes into the 'idle' state before issuing
Shutdown-Printer operation. the Shutdown-Printer operation.
The Printer object MUST accept this operation in any state and The Printer object MUST accept this operation in any state and
transition the Printer object through the "printer-states" and "printer- transition the Printer object through the "printer-states" and
state-reasons" defined for the Pause-Printer-After-Current-Job operation "printer-state-reasons" defined for the Pause-Printer-After-Current-
until the activity is completed and the Printer object disappears. Job operation until the activity is completed and the Printer object
disappears.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Shutdown-Printer Request and Shutdown-Printer Response have the same The Shutdown-Printer Request and Shutdown-Printer Response have the
attribute groups and attributes as the Pause-Printer operation (see same attribute groups and attributes as the Pause-Printer operation
[ipp-mod] sections 3.2.7.1 and 3.2.7.2), including the new "printer- (see [RFC2911] sections 3.2.7.1 and 3.2.7.2), including the new
message-from-operator" operation attribute (see section 6). "printer-message-from-operator" operation attribute (see section 6).
3.5.3 Startup-Printer operation 3.5.3 Startup-Printer operation
This OPTIONAL operation allows a client to startup an instance of a This OPTIONAL operation allows a client to startup an instance of a
Printer object, provided that there isn't one already instantiated. The Printer object, provided that there isn't one already instantiated.
purpose of Startup-Printer is to allow a hosted implementation of the The purpose of Startup-Printer is to allow a hosted implementation of
IPP Printer object (i.e., a Server that implements an IPP Printer on the IPP Printer object (i.e., a Server that implements an IPP Printer
behalf of a networked or local Output Device) to be started after the on behalf of a networked or local Output Device) to be started after
host is available (by means outside this document). See Restart-Printer the host is available (by means outside this document). See Restart-
(section 3.5.1) and Reset-Device [ipp-device-ops] for the way to Printer (section 3.5.1) for the way to initialize the software or
initialize the software or reset the Output Device(s) when the IPP reset the Output Device(s) when the IPP Printer object has already
Printer object has already been instantiated. been instantiated.
Expires: February 15, 2001
The host MUST accept this operation only when the Printer object has not The host MUST accept this operation only when the Printer object has
been instantiated. If the Printer object already exists, the host must not been instantiated. If the Printer object already exists, the
return the 'client-error-not-possible' status code. host must return the 'client-error-not-possible' status code.
The result of this operation MUST be with the Printer object's "printer- The result of this operation MUST be with the Printer object's
state" set to 'idle', the state reasons removed from its "printer-state- "printer-state" set to 'idle', the state reasons removed from its
reasons" attribute, and its "printer-is-accepting-jobs" attribute set to "printer-state-reasons" attribute, and its "printer-is-accepting-
'false'. Then the operator can reconfigure the Printer before jobs" attribute set to 'false'. Then the operator can reconfigure
performing an Enable-Printer operation. However, when a Printer is the Printer before performing an Enable-Printer operation. However,
first powered up, it is RECOMMENDED that its "printer-is-accepting-jobs" when a Printer is first powered up, it is RECOMMENDED that its
attribute be set to 'true' in order to achieve easy "out of the box" "printer-is-accepting-jobs" attribute be set to 'true' in order to
operation. achieve easy "out of the box" operation.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Shutdown-Printer Request and Shutdown-Printer Response have the same The Shutdown-Printer Request and Shutdown-Printer Response have the
attribute groups and attributes as the Pause-Printer operation (see same attribute groups and attributes as the Pause-Printer operation
[ipp-mod] sections 3.2.7.1 and 3.2.7.2), including the new "printer- (see [RFC2911] sections 3.2.7.1 and 3.2.7.2), including the new
message-from-operator" operation attribute (see section 6). "printer-message-from-operator" operation attribute (see section 6).
4 Definition of the Job Operations 4 Definition of the Job Operations
All Job operations are directed at Job objects. A client MUST always All Job operations are directed at Job objects. A client MUST always
supply some means of identifying the Job object in order to identify the supply some means of identifying the Job object in order to identify
correct target of the operation. That job identification MAY either be the correct target of the operation. That job identification MAY
a single Job URI or a combination of a Printer URI with a Job ID. The either be a single Job URI or a combination of a Printer URI with a
IPP object implementation MUST support both forms of identification for Job ID. The IPP object implementation MUST support both forms of
every job. identification for every job.
The Job Operations defined in this document are summarized in Table 3: The Job Operations defined in this document are summarized in Table
4:
Table 3 - Job operation Operation-Id assignments Table 4 - Job operation Operation-Id assignments
Operation Name Operation- Brief description
Id
Operation Name Operati Brief description
on-Id
Reprocess-Job 0x2C Creates a copy of a completed target Reprocess-Job 0x2C Creates a copy of a completed target
job with a new Job ID and processes it job with a new Job ID and processes it
Cancel-Current- 0x2D Cancels the current job on the target Cancel-Current- 0x2D Cancels the current job on the target
Job Printer or the specified job if it is Job Printer or the specified job if it is
the current job the current job
Suspend- 0x2E Suspends the current processing job on Suspend- 0x2E Suspends the current processing job on
Current-Job the target Printer or the specified job Current-Job the target Printer or the specified
if it is the current job, allowing job if it is the current job, allowing
other jobs to be processed instead other jobs to be processed instead
Resume-Job 0x2F Resume the suspended target job Resume-Job 0x2F Resume the suspended target job
Promote-Job 0x30 Promote the pending target job to be Promote-Job 0x30 Promote the pending target job to be
next after the current job(s) complete next after the current job(s) complete
Schedule-Job- 0x31 Schedule the target job immediately Schedule-Job- 0x31 Schedule the target job immediately
After after the specified job, all other After after the specified job, all other
scheduling factors being equal. scheduling factors being equal.
Expires: February 15, 2001
4.1 Reprocess-Job Operation 4.1 Reprocess-Job Operation
This OPTIONAL operation is a create job operation that allows a client This OPTIONAL operation is a create job operation that allows a
to re-process a copy of a job that had been retained in the queue after client to re-process a copy of a job that had been retained in the
processing completed, was canceled, or was aborted (see [ipp-mod] queue after processing completed, was canceled, or was aborted (see
section 4.3.7.2). This operation is the same as the Restart-Job [RFC2911] section 4.3.7.2). This operation is the same as the
operation (see [ipp-mod] section 3.3.7), except that the Printer creates Restart-Job operation (see [RFC2911] section 3.3.7), except that the
a new job that is a copy of the target job and the target job is Printer creates a new job that is a copy of the target job and the
unchanged. The new job is assigned new values to the "job-uri" and target job is unchanged. The new job is assigned new values to the
"job-id" attributes and the new job's Job Description attributes that "job-uri" and "job-id" attributes and the new job's Job Description
accumulate job progress, such as "job-impressions-completed", "job- attributes that accumulate job progress, such as "job-impressions-
media-sheets-completed", and "job-k-octets-processed", are initialized completed", "job-media-sheets-completed", and "job-k-octets-
to 0 as with any create job operation. The target job moves to the Job processed", are initialized to 0 as with any create job operation.
History after a suitable period, independent of whether one or more The target job moves to the Job History after a suitable period,
Reprocess-Job operations have been performed on it. independent of whether one or more Reprocess-Job operations have been
performed on it.
If the Set-Job-Attributes operation is supported, then the "job-hold- If the Set-Job-Attributes operation is supported, then the "job-hold-
until" operation attribute MUST be supported with at least the until" operation attribute MUST be supported with at least the
'indefinite' value, so that a client can modify the new job before it is 'indefinite' value, so that a client can modify the new job before it
scheduled for processing using the Set-Job-Attributes operation. After is scheduled for processing using the Set-Job-Attributes operation.
modifying the job, the client can release the job for processing, by After modifying the job, the client can release the job for
using the Release-Job operation specifying the newly assigned "job-uri" processing, by using the Release-Job operation specifying the newly
or "job-id" for the new job. assigned "job-uri" or "job-id" for the new job.
4.2 Cancel-Current-Job Operation 4.2 Cancel-Current-Job Operation
This OPTIONAL operation allows a client to cancel the current job on the This OPTIONAL operation allows a client to cancel the current job on
target Printer or the specified job if it is the current job on the the target Printer or the specified job if it is the current job on
Printer. See [ipp-mod] section 3.3.3 for the semantics of canceling a the Printer. See [RFC2911] section 3.3.3 for the semantics of
job. Since a Job might already be marking by the time a Cancel-Current- canceling a job. Since a Job might already be marking by the time a
Job is received, some media sheet pages might be printed before the job Cancel-Current-Job is received, some media sheet pages might be
is actually terminated. printed before the job is actually terminated.
If the client does not supply a "job-id" operation attribute, the If the client does not supply a "job-id" operation attribute, the
Printer MUST accept the request and cancel the current job if there is a Printer MUST accept the request and cancel the current job if there
current job in the 'processing' or 'processing-stopped' state; is a current job in the 'processing' or 'processing-stopped' state;
otherwise, it MUST reject the request and return the 'client-error-not- otherwise, it MUST reject the request and return the 'client-error-
possible' status code. If more than one job is in the 'processing' or not-possible' status code. If more than one job is in the
'processing-stopped' states, the one that is marking is canceled and the 'processing' or 'processing-stopped' states, the one that is marking
others are unaffected. is canceled and the others are unaffected.
Warning: On a shared printer, there is a race condition. Between the
time that a user issues this operation and its acceptance, the current
job might change to a different job. If the user or operator is
authenticated to cancel the new job, the wrong job is canceled. To
prevent this race from canceling the wrong job, the client MAY supply
the "job-id" operation attribute which is checked against the current
job's job-id. If the job identified by the "job-id" attribute is not
the current job on the Printer, i.e., is not in the 'processing' or
'processing-stopped' states, the Printer MUST reject this operation and
Expires: February 15, 2001
return the 'client-error-not-possible' status code. Otherwise, the Warning: On a shared printer, there is a race condition. Between
Printer cancels the specified job. the time that a user issues this operation and its acceptance, the
current job might change to a different job. If the user or operator
is authenticated to cancel the new job, the wrong job is canceled.
To prevent this race from canceling the wrong job, the client MAY
supply the "job-id" operation attribute which is checked against the
current job's job-id. If the job identified by the "job-id"
attribute is not the current job on the Printer, i.e., is not in the
'processing' or 'processing-stopped' states, the Printer MUST reject
this operation and return the 'client-error-not-possible' status
code. Otherwise, the Printer cancels the specified job.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must either be the job owner (as determined in performing this operation must either be the job owner (as determined
the Job Creation operation) or an operator or administrator of the in the Job Creation operation) or an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Cancel-Current-Job Request and Cancel-Current-Job Response have the The Cancel-Current-Job Request and Cancel-Current-Job Response have
same attribute groups and attributes as the Resume-Printer operation the same attribute groups and attributes as the Resume-Printer
(see [ipp-mod] section 3.2.8), including the new "job-message-from- operation (see [RFC2911] section 3.2.8), including the new "job-
operator" operation attribute (see section 6), with the addition of the message-from-operator" operation attribute (see section 6), with the
following Group 1 Operation attributes in the request: addition of the following Group 1 Operation attributes in the
request:
"job-id" (integer(1:MAX)): "job-id" (integer(1:MAX)):
The client OPTIONALLY supplies this Operation attribute in order to The client OPTIONALLY supplies this Operation attribute in order to
verify that the identified job is still the current job on the verify that the identified job is still the current job on the
target Printer object. The IPP object MUST supports this operation target Printer object. The IPP object MUST supports this operation
attribute, if it supports this operation. attribute, if it supports this operation.
4.3 Suspend and Resume Job operations 4.3 Suspend and Resume Job operations
This section defines the Suspend-Current-Job and Resume-Job operations. This section defines the Suspend-Current-Job and Resume-Job
These operations allow an operator or user to suspend a job while it is operations. These operations allow an operator or user to suspend a
processing and allow other jobs to be processed and the resume the job while it is processing and allow other jobs to be processed and
suspended job at a later point in time without losing any of the output. the resume the suspended job at a later point in time without losing
any of the output.
If either of these operations is supported, they both MUST be supported. If either of these operations is supported, they both MUST be
supported.
The Hold-Job and Release-Job operations ([ipp-mod] section 3.3.5) are The Hold-Job and Release-Job operations ([RFC2911] section 3.3.5) are
for holding and releasing held jobs, not suspending and resuming for holding and releasing held jobs, not suspending and resuming
suspended jobs. suspended jobs.
4.3.1 Suspend-Current-Job operation 4.3.1 Suspend-Current-Job operation
This OPTIONAL operation allows a client to stop the current job on the This OPTIONAL operation allows a client to stop the current job on
target Printer or the specified job if it is the current job on the the target Printer or the specified job if it is the current job on
Printer, and allow other jobs to be processed instead. The Printer the Printer, and allow other jobs to be processed instead. The
moves the current job or the target job to the 'processing-stopped' Printer moves the current job or the target job to the 'processing-
state and sets the 'job-suspended' value (see section 9.1) in the job's stopped' state and sets the 'job-suspended' value (see section 9.1)
"job-state-reasons" attribute and processes other jobs. in the job's "job-state-reasons" attribute and processes other jobs.
If the client does not supply a "job-id" operation attribute, the If the client does not supply a "job-id" operation attribute, the
Printer MUST accept the request and suspend the current job if there is Printer MUST accept the request and suspend the current job if there
a current job in the 'processing' or 'processing-stopped' state; is a current job in the 'processing' or 'processing-stopped' state;
otherwise, it MUST reject the request and return the 'client-error-not- otherwise, it MUST reject the request and return the 'client-error-
possible' status code. If more than one job is in the 'processing' or not-possible' status code. If more than one job is in the
'processing-stopped' states, all of them are suspended. 'processing' or 'processing-stopped' states, all of them are
suspended.
Warning: On a shared printer, there is a race condition. Between the
time that a user issues this operation and its acceptance, the current
job might change to a different job. If the user or operator is
Expires: February 15, 2001
authenticated to suspend the new job, the wrong job is suspended. To Warning: On a shared printer, there is a race condition. Between
prevent this race from pausing the wrong job, the client MAY supply the the time that a user issues this operation and its acceptance, the
"job-id" operation attribute which is checked against the current job's current job might change to a different job. If the user or operator
job-id. If the job identified by the "job-id" attribute is not the is authenticated to suspend the new job, the wrong job is suspended.
current job on the Printer, i.e., is not in the 'processing' or To prevent this race from pausing the wrong job, the client MAY
'processing-stopped' states, the Printer MUST reject this operation and supply the "job-id" operation attribute which is checked against the
return the 'client-error-not-possible' status code. Otherwise, the current job's job-id. If the job identified by the "job-id"
Printer suspends the specified job and processed other jobs. attribute is not the current job on the Printer, i.e., is not in the
'processing' or 'processing-stopped' states, the Printer MUST reject
this operation and return the 'client-error-not-possible' status
code. Otherwise, the Printer suspends the specified job and
processed other jobs.
The Printer MUST reject a Resume-Job request (and return the 'client- The Printer MUST reject a Resume-Job request (and return the 'client-
error-not-possible') for a job that has been suspended , i.e., for a job error-not-possible') for a job that has been suspended , i.e., for a
in the 'processing-stopped' state, with the 'job-suspended' value in its job in the 'processing-stopped' state, with the 'job-suspended' value
"job-state-reasons" attribute. in its "job-state-reasons" attribute.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must either be the job owner (as determined in performing this operation must either be the job owner (as determined
the Job Creation operation) or an operator or administrator of the in the Job Creation operation) or an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Suspend-Current-Job Request and Suspend-Current-Job Response have The Suspend-Current-Job Request and Suspend-Current-Job Response have
the same attribute groups and attributes as the Pause-Printer operation the same attribute groups and attributes as the Pause-Printer
(see [ipp-mod] section 3.2.8 ), including the new "job-message-from- operation (see [RFC2911] section 3.2.8 ), including the new "job-
operator" operation attribute (see section 6), with the addition of the message-from-operator" operation attribute (see section 6), with the
following Group 1 Operation attributes in the request: addition of the following Group 1 Operation attributes in the
request:
"job-id" (integer(1:MAX)): "job-id" (integer(1:MAX)):
The client OPTIONALLY supplies this Operation attribute in
The client OPTIONALLY supplies this Operation attribute in order to order to verify that the identified job is still the current
verify that the identified job is still the current job on the job on the target Printer object. The IPP object MUST supports
target Printer object. The IPP object MUST supports this operation this operation attribute, if it supports this operation.
attribute, if it supports this operation.
4.3.2 Resume-Job operation 4.3.2 Resume-Job operation
This OPTIONAL operation allows a client to resume the target job at the This OPTIONAL operation allows a client to resume the target job at
point where it was suspended. The Printer moves the target job to the the point where it was suspended. The Printer moves the target job
'pending' state and removes the 'job-suspended' value from the job's to the 'pending' state and removes the 'job-suspended' value from the
"job-state-reasons" attribute. job's "job-state-reasons" attribute.
If the target job is not in the 'processing-stopped' state with the If the target job is not in the 'processing-stopped' state with the
'job-suspended' value in the job's "job-state-reasons" attribute, the 'job-suspended' value in the job's "job-state-reasons" attribute, the
Printer MUST reject the request and return the 'client-error-not- Printer MUST reject the request and return the 'client-error-not-
possible' status code, since the job was not suspended. possible' status code, since the job was not suspended.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must either be the job owner (as determined in performing this operation must either be the job owner (as determined
the Job Creation operation) or an operator or administrator of the in the Job Creation operation) or an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Resume-Job Request and Resume-Job Response have the same attribute
groups and attributes as the Release-Job operation (see [ipp-mod]
section 3.3.6), including the new "job-message-from-operator" operation
attribute (see section 6).
Expires: February 15, 2001 The Resume-Job Request and Resume-Job Response have the same
attribute groups and attributes as the Release-Job operation (see
[RFC2911] section 3.3.6), including the new "job-message-from-
operator" operation attribute (see section 6).
4.4 Job Scheduling Operations 4.4 Job Scheduling Operations
This section defines jobs that allow an operator to control the This section defines jobs that allow an operator to control the
scheduling of jobs. scheduling of jobs.
4.4.1 Promote-Job operation 4.4.1 Promote-Job operation
This OPTIONAL operation allows a client to make the pending target job This OPTIONAL operation allows a client to make the pending target
be processed next after the current job completes. This operation is job be processed next after the current job completes. This
specially useful in a production printing environment where the operator operation is specially useful in a production printing environment
is involved in job scheduling. where the operator is involved in job scheduling.
If the target job is in the 'pending' state, this operation does not If the target job is in the 'pending' state, this operation does not
change the job's state, but causes the job to be processed after the change the job's state, but causes the job to be processed after the
current job(s) complete. If the target job is not in the 'pending' current job(s) complete. If the target job is not in the 'pending'
state, the Printer MUST reject the request and return the 'client-error- state, the Printer MUST reject the request and return the 'client-
not-possible' status code. error-not-possible' status code.
If the Printer implements the "job-priority" Job Template attribute (see If the Printer implements the "job-priority" Job Template attribute
[ipp-mod] section 4.2.1), the Printer sets the job's "job-priority" to (see [RFC2911] section 4.2.1), the Printer sets the job's "job-
the highest value supported (so that the job will print before any of priority" to the highest value supported (so that the job will print
the other pending jobs). The Printer returns the target job immediately before any of the other pending jobs). The Printer returns the
after the current job(s) in a Get-Jobs response (see [ipp-mod] section target job immediately after the current job(s) in a Get-Jobs
3.2.6) for the 'not-completed' jobs. response (see [RFC2911] section 3.2.6) for the 'not-completed' jobs.
When the current job completes, is canceled, suspended (see section When the current job completes, is canceled, suspended (see section
4.3.1), or aborted, the target of this operation is processed next. 4.3.1), or aborted, the target of this operation is processed next.
If a client issues this request (again) before the target of the If a client issues this request (again) before the target of the
operation of the original request started processing, the target of this operation of the original request started processing, the target of
new request is processed before the previous job that was to be this new request is processed before the previous job that was to be
processed next. processed next.
IPP is specified not to require queues for job scheduling, since there IPP is specified not to require queues for job scheduling, since
are other implementation techniques for scheduling multiple jobs, such there are other implementation techniques for scheduling multiple
as re-evaluating a criteria function for each job on a scheduling cycle. jobs, such as re-evaluating a criteria function for each job on a
However, if an implementation does implement queues for jobs, then the scheduling cycle. However, if an implementation does implement
Promote-Job puts the specified job at the front of the queue. A queues for jobs, then the Promote-Job puts the specified job at the
subsequent Promote-Job before the first job starts processing puts that front of the queue. A subsequent Promote-Job before the first job
specified job at the front of the queue, so that it is "in front" of the starts processing puts that specified job at the front of the queue,
previously promoted job. so that it is "in front" of the previously promoted job.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be an operator or administrator of the performing this operation must be an operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Promote-Job Request and Promote-Job Response have the same attribute
groups and attributes as the Cancel-Job operation (see [ipp-mod] section
3.3.3), including the new "job-message-from-operator" operation
attribute (see section 6).
Expires: February 15, 2001 The Promote-Job Request and Promote-Job Response have the same
attribute groups and attributes as the Cancel-Job operation (see
[RFC2911] section 3.3.3), including the new "job-message-from-
operator" operation attribute (see section 6).
4.4.2 Schedule-Job-After operation 4.4.2 Schedule-Job-After operation
This OPTIONAL operation allows a client to request the Printer to This OPTIONAL operation allows a client to request the Printer to
schedule the target job so that it will be processed immediately after schedule the target job so that it will be processed immediately
the specified predecessor job, all other scheduling factors being equal. after the specified predecessor job, all other scheduling factors
This operation is specially useful in a production printing environment being equal. This operation is specially useful in a production
where the operator is involved in job scheduling. printing environment where the operator is involved in job
scheduling.
If the target job is in the 'pending' state, this operation does not If the target job is in the 'pending' state, this operation does not
change the job's state, but causes the job to be processed after the change the job's state, but causes the job to be processed after the
predecessor job completes. The predecessor job can be in the 'pending', predecessor job completes. The predecessor job can be in the
'processing', or 'processing-stopped' states. If the target job is not 'pending', 'processing', or 'processing-stopped' states. If the
in the 'pending' state or the predecessor job is not in the 'pending', target job is not in the 'pending' state or the predecessor job is
'processing', or 'processing-stopped' states, the Printer MUST reject not in the 'pending', 'processing', or 'processing-stopped' states,
the request and returns the 'client-error-not-possible' status code, the Printer MUST reject the request and returns the 'client-error-
since the job cannot have its position changed. not-possible' status code, since the job cannot have its position
changed.
If the Printer implements the "job-priority" Job Template attribute (see If the Printer implements the "job-priority" Job Template attribute
[ipp-mod] section 4.2.1), the Printer sets the job's "job-priority" to (see [RFC2911] section 4.2.1), the Printer sets the job's "job-
that of the predecessor job (so that the job will print after the priority" to that of the predecessor job (so that the job will print
predecessor job). The Printer returns the target job immediately after after the predecessor job). The Printer returns the target job
the predecessor in a Get-Jobs response (see [ipp-mod] section 3.2.6) for immediately after the predecessor in a Get-Jobs response (see
the 'not-completed' jobs. [RFC2911] section 3.2.6) for the 'not-completed' jobs.
When the predecessor job completes processing or is canceled or aborted When the predecessor job completes processing or is canceled or
while processing, the target of this operation is processed next. aborted while processing, the target of this operation is processed
next.
If the client does not supply a predecessor job, this operation has the If the client does not supply a predecessor job, this operation has
same semantics as Promote-Job (see section 4.4). the same semantics as Promote-Job (see section 4.4).
IPP is specified not to require queues for job scheduling, since there IPP is specified not to require queues for job scheduling, since
are other implementation techniques for scheduling multiple jobs, such there are other implementation techniques for scheduling multiple
as re-evaluating a criteria function for each job on a scheduling cycle. jobs, such as re-evaluating a criteria function for each job on a
However, if an implementation does implement queues for jobs, then the scheduling cycle. However, if an implementation does implement
Schedule-Job-After operation puts the specified job immediately after queues for jobs, then the Schedule-Job-After operation puts the
the specified job in the queue. A subsequent Schedule-Job-After specified job immediately after the specified job in the queue. A
operation specifying the same job will cause its target job to be placed subsequent Schedule-Job-After operation specifying the same job will
after that job, even though it is between the first target job and the cause its target job to be placed after that job, even though it is
specified job. For example, suppose the job queue consisted of jobs: A, between the first target job and the specified job. For example,
B, C, D, and E, in that order. A Schedule-Job-After with job E as the suppose the job queue consisted of jobs: A, B, C, D, and E, in that
target and B as the specified job would result in the following queue: order. A Schedule-Job-After with job E as the target and B as the
A, B, E, C, D. A subsequent Schedule-Job-After with Job D as the target specified job would result in the following queue: A, B, E, C, D. A
and B as the specified job would result in the following queue: A, B, subsequent Schedule-Job-After with Job D as the target and B as the
D, E, C. In other words, the link between the two jobs in a Schedule- specified job would result in the following queue: A, B, D, E, C.
Job-After operation is not retained, i.e., there is no attribute on In other words, the link between the two jobs in a Schedule-Job-After
either job that points to the other job as a result of this operation. operation is not retained, i.e., there is no attribute on either job
that points to the other job as a result of this operation.
Access Rights: The authenticated user (see [ipp-mod] section 8.3) Access Rights: The authenticated user (see [RFC2911] section 8.3)
performing this operation must be operator or administrator of the performing this operation must be operator or administrator of the
Printer object (see [ipp-mod] Sections 1 and 8.5). Printer object (see [RFC2911] Sections 1 and 8.5).
The Schedule-Job-After Request have the same attribute groups and The Schedule-Job-After Request have the same attribute groups and
attributes as the Cancel-Job operation (see [ipp-mod] section 3.3.3), attributes as the Cancel-Job operation (see [RFC2911] section 3.3.3),
plus the new "job-message-from-operator" operation attribute (see plus the new "job-message-from-operator" operation attribute (see
Expires: February 15, 2001
section 6). In addition, the following operation attributes are section 6). In addition, the following operation attributes are
defined: defined:
"predecessor-job-id": "predecessor-job-id":
The client OPTIONALLY supplies this attribute. The Printer MUST The client OPTIONALLY supplies this attribute. The Printer
support it, if it supports this operation. This attribute MUST support it, if it supports this operation. This attribute
specifies the job after which the target job is to be processed. specifies the job after which the target job is to be
If the client omits this attribute, the Printer MUST process the processed. If the client omits this attribute, the Printer
target job next, i.e., after the current job, if any. MUST process the target job next, i.e., after the current job,
if any.
The Schedule-Job-After Response has the same attribute groups, The Schedule-Job-After Response has the same attribute groups,
attributes, and status codes as the Cancel-Job operation (see [ipp-mod] attributes, and status codes as the Cancel-Job operation (see
section 3.3.3). The following status codes have particular meaning for [RFC2911] section 3.3.3). The following status codes have particular
this operation: meaning for this operation:
'client-error-not-possible' - the target job was not in the 'pending' 'client-error-not-possible' - the target job was not in the
state or the predecessor job was no in the 'pending', 'processing', 'pending' state or the predecessor job was no in the 'pending',
or 'processing-stopped' states. 'processing', or 'processing-stopped' states.
'client-error-not-found' - either the target job or the predecessor 'client-error-not-found' - either the target job or the
job was not found. predecessor job was not found.
5 Additional status codes 5 Additional status codes
This section defines new status codes used by the operations defined in This section defines new status codes used by the operations defined
this document. in this document.
5.1 'server-error-printer-is-deactivated' (0x050A) 5.1 'server-error-printer-is-deactivated' (0x050A)
The Printer has been deactivated using the Deactivate-Printer operation The Printer has been deactivated using the Deactivate-Printer
and is only accepting the Activate-Printer (see section 3.5.1), Get-Job- operation and is only accepting the Activate-Printer (see section
Attributes, Get-Jobs, Get-Printer-Attributes, and any other Get-Xxxx 3.5.1), Get-Job-Attributes, Get-Jobs, Get-Printer-Attributes, and any
operations. An operator can perform the Activate-Printer operation to other Get-Xxxx operations. An operator can perform the Activate-
allow the Printer to accept other operations. Printer operation to allow the Printer to accept other operations.
6 Use of Operation Attributes that are Messages from the Operator 6 Use of Operation Attributes that are Messages from the Operator
This section summarizes the usage of the "printer-message-from-operator" This section summarizes the usage of the "printer-message-from-
and "job-message-from-operator" operation attributes that set the operator" and "job-message-from-operator" operation attributes that
corresponding Printer and Job Description attributes (see [ipp-set-ops] set the corresponding Printer and Job Description attributes (see
for the definition of these operation attributes). These operation [ipp-set-ops] for the definition of these operation attributes).
attributes are defined for most of the Device and Job operations that These operation attributes are defined for most of the Printer and
operators are likely to perform, respectively, so that operators can Job operations that operators are likely to perform, respectively, so
indicate the reasons for their actions. that operators can indicate the reasons for their actions.
Table 4 shows the operation attributes that are defined for use with the
Printer Operations.
Legend:
REQ - REQUIRED for a Printer to support
OPT - OPTIONAL for a Printer to support; the Printer ignores the
attribute if not supported
Expires: February 15, 2001 Table 5 shows the operation attributes that are defined for use with
<blank> - not defined for use with the operation; the Printer the Printer Operations.
ignores the attribute
Table 4 - Operation attribute support for Printer Operations Table 5 - Operation attribute support for Printer Operations
Operation Pause- Hold-New- Pur Get- Enabl Rest Shut Operation Attribute A B C D E F G
Attribute Printer, Jobs, ge- Printe e- art- down
Pause- Release- Job r- Print Prin -
Printer- Held-New- s Attrib , ter Prin
After- Jobs utes, Disab ter,
Current- Set- le- Star
Job, Printe Print tup-
Resume- r- er Prin
Printer Attrib ter
utes
attributes- REQ REQ REQ REQ REQ REQ REQ attributes-charset REQ REQ REQ REQ REQ REQ REQ
charset
attributes- REQ REQ REQ REQ REQ REQ REQ attributes-natural-language REQ REQ REQ REQ REQ REQ REQ
natural-
language
printer-uri REQ REQ REQ REQ REQ REQ REQ printer-uri REQ REQ REQ REQ REQ REQ REQ
requesting- REQ REQ REQ REQ REQ REQ REQ requesting-user-name REQ REQ REQ REQ REQ REQ REQ
user-name
printer- OPT OPT OPT OPT OPT OPT printer-message-from- OPT OPT OPT OPT OPT OPT
message-
from-
operator operator
Table 5 shows the operation attributes that are defined for use with the
Job operations.
Legend: Legend:
A: Pause-Printer, Pause-Printer-After-Current-Job, Resume-Printer
B: Hold-New-Jobs, Release-Held-New-Jobs
C: Purge-Jobs
D: Get-Printer-Attributes, Set-Printer-Attributes
E: Enable-Print, Disable-Printer
F: Restart-Printer
G: Shutdown-Printer, Startup-Printer
REQ - REQUIRED for a Printer to support REQ - REQUIRED for a Printer to support
O - OPTIONAL for a Printer to support; the Printer ignores the OPT - OPTIONAL for a Printer to support; the Printer ignores the
attribute if supplied, but not supported attribute if not supported
<blank> - not defined for use with the operation; the Printer <blank> - not defined for use with the operation; the Printer
ignores the attribute ignores the attribute
Table 6 shows the operation attributes that are defined for use with
the Job operations.
Table 5 - Operation attribute support for Job operations Table 6 - Operation attribute support for Job operations
Operation Can Canc Hol Sus Res Get- Rest Repr Pro Sch Operation A B C D E F G H I J
Attribute cel el- d- pen ume Job- art- oces mot edu Attribute
- Curr Job d- - Attrib Job s- e- le-
Job ent- , Cur Job utes, Job Job Job
Job Rel ren Set- -
eas t- Job- Aft
e- Job Attrib er
Job utes
attributes- REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ attributes- REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ
charset charset
attributes- REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ attributes- REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ
natural-language natural-
language
printer-uri REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ printer-uri REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ
Expires: February 15, 2001
Operation Can Canc Hol Sus Res Get- Rest Repr Pro Sch
Attribute cel el- d- pen ume Job- art- oces mot edu
- Curr Job d- - Attrib Job s- e- le-
Job ent- , Cur Job utes, Job Job Job
Job Rel ren Set- -
eas t- Job- Aft
e- Job Attrib er
Job utes
job-uri REQ REQ REQ REQ REQ REQ REQ REQ job-uri REQ REQ REQ REQ REQ REQ REQ REQ
job-id REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ job-id REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ
requesting-user- REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ requesting- REQ REQ REQ REQ REQ REQ REQ REQ REQ REQ
name user-name
job-message- OPT OPT OPT OPT OPT OPT OPT OPT OPT job-message- OPT OPT OPT OPT OPT OPT OPT OPT OPT
from-operator from-operator
message [to- OPT OPT OPT OPT OPT OPT OPT OPT message [to- OPT OPT OPT OPT OPT OPT OPT OPT
operator] operator]
job-hold-until OPT OPT* job-hold-until OPT OPT
* * * **
Legend:
A: Cancel-Job
B: Cancel-Current-Job
C: Hold-Job, Release-Job
D: Suspend-Current-Job
E: Resume-Job
F: Get-Job-Attributes, Set-Job-Attributes
G: Restart-Job
H: Reprocess-Job
I: Promote-Job
J: Schedule-Job-After
REQ - REQUIRED for a Printer to support
O - OPTIONAL for a Printer to support; the Printer ignores the
attribute if supplied, but not supported
<blank> - not defined for use with the operation; the Printer ignores
the attribute
* The Printer MUST support the "job-hold-until" operation attribute * The Printer MUST support the "job-hold-until" operation attribute
if it supports the "job-hold-until" Job Template attribute. if it supports the "job-hold-until" Job Template attribute.
** The Printer MUST support the "job-hold-until" operation attribute if ** The Printer MUST support the "job-hold-until" operation attribute
it supports the Set-Job-Attributes operation, so that the client can if it supports the Set-Job-Attributes operation, so that the
hold the job with the Reprocess-Job operation and the modify the job client can hold the job with the Reprocess-Job operation and the
before releasing it to be processed. modify the job before releasing it to be processed.
7 New Printer Description Attributes 7 New Printer Description Attributes
The following new Printer Description attributes are needed to support The following new Printer Description attributes are needed to
the new operations defined in this document and the concepts of Printer support the new operations defined in this document and the concepts
Fan-Out (see section 11). of Printer Fan-Out (see section 11).
7.1 subordinate-printers-supported (1setOf uri) 7.1 subordinate-printers-supported (1setOf uri)
This Printer attribute is REQUIRED if an implementation supports This Printer attribute is REQUIRED if an implementation supports
Subordinate Printers (see section 11) and contains the URIs of the Subordinate Printers (see section 11) and contains the URIs of the
immediate Subordinate Printer object(s) associated with this Printer immediate Subordinate Printer object(s) associated with this Printer
object. Each Non-Leaf Printer object MUST support this Printer object. Each Non-Leaf Printer object MUST support this Printer
Description attribute. A Leaf Printer object either does not support Description attribute. A Leaf Printer object either does not support
the "subordinate-printers-supported" attribute or does so with the 'no- the "subordinate-printers-supported" attribute or does so with the
value' out-of-band value (see [ipp-mod] section 4.1), depending on 'no-value' out-of-band value (see [RFC2911] section 4.1), depending
implementation. on implementation.
The precise format of the Subordinate Printer URIs is implementation The precise format of the Subordinate Printer URIs is implementation
dependent (see section 11.4). dependent (see section 11.4).
If the Printer object does not have an associated Output Device, the If the Printer object does not have an associated Output Device, the
Printer MAY automatically copy the value of the Subordinate Printer Printer MAY automatically copy the value of the Subordinate Printer
object's "printer-name" MAY be used to populate the Job object's object's "printer-name" attribute to the Job object's "output-
device-assigned" attribute (see [RFC2911] section 4.3.13). The
Expires: February 15, 2001 "output-device-assigned" Job attribute identifies the Output Device
to which the Printer object has assigned a job, for example, when a
"output-device-assigned" attribute (see [ipp-mod] section 4.3.13). The single Printer object is supporting Device Fan-Out or Printer Fan-
"output-device-assigned" Job attribute identifies the Output Device to Out.
which the Printer object has assigned a job, for example, when a single
Printer object is supporting Device Fan-Out or Printer Fan-Out.
7.2 parent-printers-supported (1setOf uri) 7.2 parent-printers-supported (1setOf uri)
This Printer attribute is REQUIRED if an implementation supports This Printer attribute is REQUIRED if an implementation supports
Subordinate Printers (see section 11) and contains the URI of the Non- Subordinate Printers (see section 11) and contains the URI of the
Leaf printer object(s) for which this Printer object is the immediate Non-Leaf printer object(s) for which this Printer object is the
Subordinate, i.e., this Printer's immediate "parent" or "parents". Each immediate Subordinate, i.e., this Printer's immediate "parent" or
Subordinate Printer object MUST support this Printer Description "parents". Each Subordinate Printer object MUST support this Printer
attribute. A Printer that has no parents, either does not support the Description attribute. A Printer that has no parents, either does
"parent-printers-supported" attribute or does so with the 'no-value' not support the "parent-printers-supported" attribute or does so with
out-of-band value (see [ipp-mod] section 4.1), depending on the 'no-value' out-of-band value (see [RFC2911] section 4.1),
implementation. depending on implementation.
8 Additional Values for "printer-state-reasons" 8 Additional Values for the "printer-state-reasons" Printer Description
attribute
This section defines additional values for the "printer-state-reasons" This section defines additional values for the "printer-state-
Printer Description attribute. reasons" Printer Description attribute.
8.1 'hold-new-jobs' 8.1 'hold-new-jobs' value
'hold-new-jobs': The operator has issued the Hold-New-Jobs operation 'hold-new-jobs': The operator has issued the Hold-New-Jobs operation
(see section 3.3.1) or other means, but the output-device(s) are (see section 3.3.1) or other means, but the output-device(s) are
taking an appreciable time to stop. Later, when all output has taking an appreciable time to stop. Later, when all output has
stopped, the "printer-state" becomes 'stopped', and the 'paused' stopped, the "printer-state" becomes 'stopped', and the 'paused'
value replaces the 'moving-to-paused' value in the "printer-state- value replaces the 'moving-to-paused' value in the "printer-state-
reasons" attribute. This value MUST be supported, if the Hold-New- reasons" attribute. This value MUST be supported, if the Hold-
Jobs operation is supported and the implementation takes New-Jobs operation is supported and the implementation takes
significant time to pause a device in certain circumstances. significant time to pause a device in certain circumstances.
8.2 'deactivated' 8.2 'deactivated' value
'deactivated': A client has issued a Deactivate-Printer operation 'deactivated': A client has issued a Deactivate-Printer operation
for the Printer object (see section 3.4.1) and the Printer is in for the Printer object (see section 3.4.1) and the Printer is in
the process of becoming deactivated or has become deactivated. The the process of becoming deactivated or has become deactivated. The
Printer MUST reject all requests except Activate-Printer, queries Printer MUST reject all requests except Activate-Printer, queries
(Get-Printer-Attributes, Get-Job-Attributes, Get-Jobs, etc.), Send- (Get-Printer-Attributes, Get-Job-Attributes, Get-Jobs, etc.),
Document, and Send-URI (so that partial job submission can be Send-Document, and Send-URI (so that partial job submission can be
completed - see section 3.1.1) and return the 'server-error- completed - see section 3.1.1) and return the 'server-error-
service-unavailable' status code. service-unavailable' status code.
9 Additional Values for "job-state-reasons" 9 Additional Values for the "job-state-reasons" Job Description
attribute
This section defines additional values for the "job-state-reasons" Job
Description attribute.
Expires: February 15, 2001 This section defines additional values for the "job-state-reasons"
Job Description attribute.
9.1 'job-suspended' 9.1 'job-suspended' value
'job-suspended': The job has been suspended while processing using 'job-suspended': The job has been suspended while processing
the Suspend-Current-Job operation and other jobs can be processed using the Suspend-Current-Job operation and other jobs can be
on the Printer. The Job can be resumed using the Resume-Job processed on the Printer. The Job can be resumed using the
operation which removes this value. Resume-Job operation which removes this value.
10 Additional events 10 Additional events
The following Printer events are defined for use with [ipp-ntfy]: The following Job events are defined for use with [ipp-ntfy]:
'forwarded-operation-failed' - an operation that a Printer forwarded 'job-forwarded-operation-failed' - an operation that a Printer
to a Subordinate Printer (see section 11.7) failed. forwarded to a Subordinate Printer (see section 11.7) failed.
11 Use of the Printer object to represent IPP Printer Fan-Out and IPP 11 Use of the Printer object to represent IPP Printer Fan-Out and IPP
Printer Fan-In Printer Fan-In
This section defines how the Printer object MAY be used to represent IPP This section defines how the Printer object MAY be used to represent
Printer Fan-Out and IPP Printer Fan-In. Fan-Out is where an IPP Printer IPP Printer Fan-Out and IPP Printer Fan-In. Fan-Out is where an IPP
is used to represent other IPP Printer objects. Fan-In is where several Printer is used to represent other IPP Printer objects. Fan-In is
IPP Printer objects are used to represent another IPP Printer object. where several IPP Printer objects are used to represent another IPP
Printer object.
11.1 IPP Printer Fan-Out 11.1 IPP Printer Fan-Out
The IPP/1.1 Model and Semantics introduces the semantic concept of an The IPP/1.1 Model and Semantics introduces the semantic concept of an
IPP Printer object that represents more than one Output Device (see IPP Printer object that represents more than one Output Device (see
[ipp-mod] section 2.1). This concept is called "Output Device Fan-Out". [RFC2911] section 2.1). This concept is called "Output Device Fan-
However, there was no way to represent the individual states of the Out". However, there was no way to represent the individual states
Output Devices or to perform operations on a specific Output Device when of the Output Devices or to perform operations on a specific Output
there was Fan-Out. This document generalizes the semantics of the Device when there was Fan-Out. This document generalizes the
Printer object to represent such Subordinate Fan-Out Output Devices as semantics of the Printer object to represent such Subordinate Fan-Out
IPP Printer objects. This concept is called "Printer object Fan-Out". Output Devices as IPP Printer objects. This concept is called
A Printer object that has a Subordinate Printer object is called a Non- "Printer object Fan-Out". A Printer object that has a Subordinate
Leaf Printer object. Thus a Non-Leaf Printer object supports one or Printer object is called a Non-Leaf Printer object. Thus a Non-Leaf
more Subordinate Printer objects in order to represent Printer object Printer object supports one or more Subordinate Printer objects in
Fan-Out. A Printer object that does not have any Subordinate Printer order to represent Printer object Fan-Out. A Printer object that does
objects is called a Leaf Printer object. not have any Subordinate Printer objects is called a Leaf Printer
object.
Each Non-Leaf Printer object submits jobs to its immediate Subordinate
Printers and otherwise controls the Subordinate Printers using IPP or
other protocols. Whether pending jobs are kept in the Non-Leaf Printer
until a Subordinate Printer can accept them or are kept in the
Subordinate Printers depends on implementation and/or configuration
policy. Furthermore, a Subordinate Printer object MAY, in turn, have
Subordinate Printer objects. Thus a Printer object can be both a Non-
Leaf Printer and a Subordinate Printer.
A Subordinate Printer object MUST be a conforming Printer object, so it
MUST support all of the REQUIRED [ipp-mod] operations and attributes.
However, with access control, the Subordinate Printer MAY be configured
Expires: February 15, 2001 Each Non-Leaf Printer object submits jobs to its immediate
Subordinate Printers and otherwise controls the Subordinate Printers
using IPP or other protocols. Whether pending jobs are kept in the
Non-Leaf Printer until a Subordinate Printer can accept them or are
kept in the Subordinate Printers depends on implementation and/or
configuration policy. Furthermore, a Subordinate Printer object MAY,
in turn, have Subordinate Printer objects. Thus a Printer object can
be both a Non-Leaf Printer and a Subordinate Printer.
so that end-user clients are not permitted to perform any operations (or A Subordinate Printer object MUST be a conforming Printer object, so
just Get-Printer-Attributes) while one or more Non-Leaf Printer it MUST support all of the REQUIRED [RFC2911] operations and
object(s) are permitted to perform any operation. attributes. However, with access control, the Subordinate Printer
MAY be configured so that end-user clients are not permitted to
perform any operations (or just Get-Printer-Attributes) while one or
more Non-Leaf Printer object(s) are permitted to perform any
operation.
11.2 IPP Printer Fan-In 11.2 IPP Printer Fan-In
The IPP/1.1 Model and Semantics did not preclude the semantic concept of The IPP/1.1 Model and Semantics did not preclude the semantic concept
multiple IPP Printer objects that represent a single Output Device (see of multiple IPP Printer objects that represent a single Output Device
[ipp-mod] section 2.1). However, there was no way for the client to (see [RFC2911] section 2.1). However, there was no way for the
determine that there was a Fan-In configuration, nor was there a way to client to determine that there was a Fan-In configuration, nor was
perform operations on the Subordinate device. This specification there a way to perform operations on the Subordinate device. This
generalizes the semantics of the Printer object to allow several Non- specification generalizes the semantics of the Printer object to
Leaf IPP Printer objects to represent a single Subordinate Printer allow several Non-Leaf IPP Printer objects to represent a single
object. Thus a Non-Leaf Printer object MAY share a Subordinate Printer Subordinate Printer object. Thus a Non-Leaf Printer object MAY share
object with one or more other Non-Leaf Printer objects in order to a Subordinate Printer object with one or more other Non-Leaf Printer
represent IPP Printer Fan-In. objects in order to represent IPP Printer Fan-In.
As with Fan-Out (see section 11.1), when a Printer object is a Non-Leaf As with Fan-Out (see section 11.1), when a Printer object is a Non-
Printer, it MUST NOT have an associated Output Device. As with Fan-Out, Leaf Printer, it MUST NOT have an associated Output Device. As with
a Leaf Printer object has one or more associated Output Devices. As Fan-Out, a Leaf Printer object has one or more associated Output
with Fan-Out, the Non-Leaf Printer objects submit jobs to their Devices. As with Fan-Out, the Non-Leaf Printer objects submit jobs
Subordinate Printer objects and otherwise control the Subordinate to their Subordinate Printer objects and otherwise control the
Printer. As with Fan-Out, whether pending jobs are kept in the Non-Leaf Subordinate Printer. As with Fan-Out, whether pending jobs are kept
Printers until the Subordinate Printer can accept them or are kept in in the Non-Leaf Printers until the Subordinate Printer can accept
the Subordinate Printer depends on implementation and/or configuration them or are kept in the Subordinate Printer depends on implementation
policy. and/or configuration policy.
11.3 Printer object attributes used to represent Printer Fan-Out and 11.3 Printer object attributes used to represent Printer Fan-Out and
Printer Fan-In Printer Fan-In
The following Printer Description attributes are defined to represent The following Printer Description attributes are defined to represent
the relationship between Printer object(s) and their Subordinate Printer the relationship between Printer object(s) and their Subordinate
object(s): Printer object(s):
1."subordinate-printers-supported" (1setOf uri) - contains the URI of 1."subordinate-printers-supported" (1setOf uri) - contains the URI
the immediate Subordinate Printer object(s). of the immediate Subordinate Printer object(s).
2."parent-printers-supported (1setOf uri) - contains the URI of the 2."parent-printers-supported (1setOf uri) - contains the URI of
Non-Leaf printer object(s) for which this Printer object is the the Non-Leaf printer object(s) for which this Printer object is
immediate Subordinate, i.e., this Printer's immediate "parent" or the immediate Subordinate, i.e., this Printer's immediate
"parents". "parent" or "parents".
11.4 Subordinate Printer URI 11.4 Subordinate Printer URI
Each Subordinate Printer object has a URI which is used as the target of Each Subordinate Printer object has a URI which is used as the target
each operation on the Subordinate Printer. The means for configuring of each operation on the Subordinate Printer. The means for
URIs for Subordinate Printer objects is implementation-dependent as are configuring URIs for Subordinate Printer objects is implementation-
all URIs. However, there are two distinct approaches: dependent as are all URIs. However, there are two distinct
approaches:
a. When the implementation wants to make sure that no operation on a. When the implementation wants to make sure that no operation on
a Subordinate Printer object as a target "sneaks by" the parent a Subordinate Printer object as a target "sneaks by" the parent
Expires: February 15, 2001
Printer object (or the Subordinate Printer is fronting for a device Printer object (or the Subordinate Printer is fronting for a device
that is not networked), the host part of the URI specifies the host that is not networked), the host part of the URI specifies the host
of the parent Printer. Then the parent Printer object can easily of the parent Printer. Then the parent Printer object can easily
reflect the state of the Subordinate Printer objects in the reflect the state of the Subordinate Printer objects in the
parent's Printer object state and state reasons as the operation parent's Printer object state and state reasons as the operation
passes "through" the parent Printer object. passes "through" the parent Printer object.
b. When the Subordinate Printer is networked and the implementation b. When the Subordinate Printer is networked and the implementation
allows operations to go directly to the Subordinate Printer (with allows operations to go directly to the Subordinate Printer (with
proper access control) without knowledge of the parent Printer proper access control) without knowledge of the parent Printer
object, the host part of the URI is different than the host part of object, the host part of the URI is different than the host part of
the parent Printer object. In such a case, the parent Printer the parent Printer object. In such a case, the parent Printer
object MUST keep its "printer-state" and "printer-state-reasons" up object MUST keep its "printer-state" and "printer-state-reasons" up
to date, either by polling the Subordinate Printer object or by to date, either by polling the Subordinate Printer object or by
subscribing to events with the Subordinate Printer object (see subscribing to events with the Subordinate Printer object (see
[ipp-not-spec] for means to subscribe to event notification when [ipp-not-spec] for means to subscribe to event notification when
the Subordinate Printer object supports IPP notification). the Subordinate Printer object supports IPP notification).
11.5 Printer object attributes used to represent Output Device Fan-Out 11.5 Printer object attributes used to represent Output Device Fan-Out
Only Leaf IPP Printer objects are allowed to have one or more associated Only Leaf IPP Printer objects are allowed to have one or more
Output Devices. Each Leaf Printer object MAY support the "output- associated Output Devices. Each Leaf Printer object MAY support the
devices-supported" (1setOf name(127)) to indicate the user-friendly "output-devices-supported" (1setOf name(127)) to indicate the user-
name(s) of the Output Device(s) that the Leaf Printer object represents. friendly name(s) of the Output Device(s) that the Leaf Printer object
It is RECOMMENDED that each Leaf Printer object have only one associated represents. It is RECOMMENDED that each Leaf Printer object have
Output Device, so that the individual Output Devices can be represented only one associated Output Device, so that the individual Output
completely and controlled completely by clients. In other words, the Devices can be represented completely and controlled completely by
Leaf Printer's "output-devices-supported" attribute SHOULD have only one clients. In other words, the Leaf Printer's "output-devices-
value. supported" attribute SHOULD have only one value.
Non-Leaf Printer MUST NOT have associated Output Devices. However, a Non-Leaf Printer MUST NOT have associated Output Devices. However, a
Non-Leaf Printer SHOULD support an "output-devices-supported" (1setOf Non-Leaf Printer SHOULD support an "output-devices-supported" (1setOf
name(127)) Printer Description attribute that contains all the values of name(127)) Printer Description attribute that contains all the values
its immediate Subordinate Printers. Since such Subordinate Printers MAY of its immediate Subordinate Printers. Since such Subordinate
be Leaf or Non-Leaf, the same rules apply to them, etc. Thus any Non- Printers MAY be Leaf or Non-Leaf, the same rules apply to them, etc.
Leaf Printer SHOULD have an "output-devices-supported" (1setOf Thus any Non-Leaf Printer SHOULD have an "output-devices-supported"
name(127)) attribute that contains all the values of the Output Devices (1setOf name(127)) attribute that contains all the values of the
associated with Leaf Printers of its complete sub-tree. Output Devices associated with Leaf Printers of its complete sub-
tree.
When adding, removing, or changing a configuration of Printers and When adding, removing, or changing a configuration of Printers and
Output Devices, there can be moments in time when the tree structure is Output Devices, there can be moments in time when the tree structure
not consistent. In other words, times when a Non-Leaf Printer's is not consistent. In other words, times when a Non-Leaf Printer's
"subordinate-printers-supported" does not agree with the Subordinate "subordinate-printers-supported" does not agree with the Subordinate
Printer's "parent-printers-supported". Therefore, the operator SHOULD Printer's "parent-printers-supported". Therefore, the operator
first Deactivate all Printers that are being configured in this way, SHOULD first Deactivate all Printers that are being configured in
update all pointer attributes, and then reactivate. A useful client this way, update all pointer attributes, and then reactivate. A
tool would validate a tree structure before Activating the Printers useful client tool would validate a tree structure before Activating
involved. the Printers involved.
Expires: February 15, 2001
11.6 Figures to show all possible configurations 11.6 Figures to show all possible configurations
Figure 1, Figure 2, and Figure 3 are taken from [ipp-mod] to show the Figure 1, Figure 2, and Figure 3 are taken from [RFC2911] to show the
configurations possible with IPP/1.0 and IPP/1.1 where all Printer configurations possible with IPP/1.0 and IPP/1.1 where all Printer
objects are Leaf Printer objects. The remaining figures show additional objects are Leaf Printer objects. The remaining figures show
configurations that this document defines using Non-Leaf and Leaf additional configurations that this document defines using Non-Leaf
Printer objects. Legend for all figures: and Leaf Printer objects. Legend for all figures:
----> indicates a network protocol with the direction of its requests ----> indicates a network protocol with the direction of its requests
##### indicates a Printer object which is either: ##### indicates a Printer object which is either:
- embedded in an Output Device or - embedded in an Output Device or
- hosted in a server. The Printer object - hosted in a server. The Printer object
might or might not be capable of queuing/spooling. might or might not be capable of queuing/spooling.
any indicates any network protocol or direct any indicates any network protocol or direct
connect, including IPP connect, including IPP
skipping to change at page 31, line 4 skipping to change at page 39, line 4
########### any/ | | ########### any/ | |
O +--------+ # (Leaf) # / +---------------+ O +--------+ # (Leaf) # / +---------------+
/|\ | client |---IPP----># Printer #--* /|\ | client |---IPP----># Printer #--*
/ \ +--------+ # Object # \ +---------------+ / \ +--------+ # Object # \ +---------------+
########### any\ | | ########### any\ | |
+->| Output Device | +->| Output Device |
| | | |
+---------------+ +---------------+
Figure 3 - Output Device Fan-Out Figure 3 - Output Device Fan-Out
Expires: February 15, 2001
########### ########### ########### ###########
O +--------+ # Non-Leaf# # subord. # O +--------+ # Non-Leaf# # subord. #
/|\ | client |---IPP----># Printer #---IPP----># Printer # /|\ | client |---IPP----># Printer #---IPP----># Printer #
/ \ +--------+ # object # # object # / \ +--------+ # object # # object #
########### ########### ########### ###########
The Subordinate Printer can be a Non-Leaf Printer as in Figure 4 to The Subordinate Printer can be a Non-Leaf Printer as in Figure 4 to
Figure 6, or can be a Leaf Printer as in Figure 1 to Figure 3. Figure 6, or can be a Leaf Printer as in Figure 1 to Figure 3.
Figure 4 - Chained IPP Printer Objects Figure 4 - Chained IPP Printer Objects
skipping to change at page 31, line 50 skipping to change at page 40, line 4
IPP ########### \ ########### IPP ########### \ ###########
O +--------+ / +-IPP-># subord. # O +--------+ / +-IPP-># subord. #
/|\ | client |--+-----------IPP---------------># Printer # /|\ | client |--+-----------IPP---------------># Printer #
/ \ +--------+ \ +-IPP-># object # / \ +--------+ \ +-IPP-># object #
IPP ########### / ########### IPP ########### / ###########
\ # Non-Leaf# / \ # Non-Leaf# /
+---># Printer #-+ +---># Printer #-+
# object # # object #
########### ###########
(Non-Leaf) (Non-Leaf)
The Subordinate Printer can be a Non-Leaf Printer as in Figure 4, Figure The Subordinate Printer can be a Non-Leaf Printer as in Figure 4,
5, or Figure 6, or can be a Leaf Printer as in Figure 1, Figure 2, or Figure 5, or Figure 6, or can be a Leaf Printer as in Figure 1,
Figure 3. Figure 2, or Figure 3.
Figure 6 - IPP Printer Object Fan-In Figure 6 - IPP Printer Object Fan-In
Expires: February 15, 2001
11.7 Forwarding requests 11.7 Forwarding requests
This section describes the forwarding of Job and Printer requests to This section describes the forwarding of Job and Printer requests to
Subordinate Printer objects. Subordinate Printer objects.
11.7.1 Forwarding requests that affect Printer objects 11.7.1 Forwarding requests that affect Printer objects
In Printer Fan-Out, Printer Fan-In, and Chained Printers, the Non-Leaf In Printer Fan-Out, Printer Fan-In, and Chained Printers, the Non-
IPP Printer object MUST NOT forward the operations that affect Printer Leaf IPP Printer object MUST NOT forward the operations that affect
objects to its Subordinate Printer objects. If a client wants to Printer objects to its Subordinate Printer objects. If a client
explicitly target a Subordinate Printer, the client MUST specify the URI wants to explicitly target a Subordinate Printer, the client MUST
of the Subordinate Printer. The client can determine the URI of any specify the URI of the Subordinate Printer. The client can
Subordinate Printers by querying the Printer's "subordinate-printers- determine the URI of any Subordinate Printers by querying the
supported (1setOf uri) attribute (see section 7.1). Printer's "subordinate-printers-supported (1setOf uri) attribute (see
section 7.1).
Table 6 lists the operations that affect Printer objects and the Table 7 lists the operations that affect Printer objects and the
forwarding behavior that a Non-Leaf Printer MUST exhibit to its forwarding behavior that a Non-Leaf Printer MUST exhibit to its
immediate Subordinate Printers. Operations that affect jobs have a immediate Subordinate Printers. Operations that affect jobs have a
different forwarding rule (see section 11.7.2 and Table 7): different forwarding rule (see section 11.7.2 and Table 8):
Table 6 - Forwarding operations that affect Printer objects Table 7 - Forwarding operations that affect Printer objects
Printer Operation Non-Leaf Printer action Printer Operation Non-Leaf Printer action
Printer Operations: Printer Operations:
Enable-Printer MUST NOT forward to any of its Subordinate Enable-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Disable-Printer MUST NOT forward to any of its Subordinate Disable-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Hold-New-Jobs MUST NOT forward to any of its Subordinate Hold-New-Jobs MUST NOT forward to any of its Subordinate
Printers Printers
Release-Held-New- MUST NOT forward to any of its Subordinate Release-Held-New- MUST NOT forward to any of its Subordinate
Jobs Printers Jobs Printers
Deactivate-Printer MUST NOT forward to any of its Subordinate Deactivate-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Activate-Printer MUST NOT forward to any of its Subordinate Activate-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Restart-Printer MUST NOT forward to any of its Subordinate Restart-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Shutdown-Printer MUST NOT forward to any of its Subordinate Shutdown-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Startup-Printer MUST NOT forward to any of its Subordinate Startup-Printer MUST NOT forward to any of its Subordinate
Printers Printers
IPP/1.1 Printer See [ipp-mod]
IPP/1.1 Printer See [RFC2911]
Operations: Operations:
Get-Printer- MUST NOT forward to any of its Subordinate Get-Printer- MUST NOT forward to any of its Subordinate
Attributes Printers Attributes Printers
Pause-Printer MUST NOT forward to any of its Subordinate Pause-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Resume-Printer MUST NOT forward to any of its Subordinate Resume-Printer MUST NOT forward to any of its Subordinate
Printers Printers
Set operations: See [ipp-set-ops]
Set-Printer- MUST NOT forward to any of its Subordinate
Expires: February 15, 2001
Printer Operation Non-Leaf Printer action Printer Operation Non-Leaf Printer action
Set operations: See [ipp-set-ops]
Set-Printer- MUST NOT forward to any of its Subordinate
Attributes Printers Attributes Printers
11.7.2 Forwarding requests that affect Jobs 11.7.2 Forwarding requests that affect Jobs
Unlike Printer Operations that only affect Printer objects (see section Unlike Printer Operations that only affect Printer objects (see
11.7.1), a Non-Leaf Printer object MUST forward operations that directly section 11.7.1), a Non-Leaf Printer object MUST forward operations
affect jobs to the appropriate Job object(s) in one or more of its that directly affect jobs to the appropriate Job object(s) in one or
immediate Subordinate Printer objects. Forwarding is REQUIRED since the more of its immediate Subordinate Printer objects. Forwarding is
purpose of such a Job operation is to affect the indicated job which REQUIRED since the purpose of such a Job operation is to affect the
itself may have been forwarded. Such forwarding MAY be immediate or indicated job which itself may have been forwarded. Such forwarding
queued, depending on the operation and the implementation. For example, MAY be immediate or queued, depending on the operation and the
a Non-Leaf Printer object MAY queue/spool jobs, feeding a job at a time implementation. For example, a Non-Leaf Printer object MAY
to its Subordinate Printer(s), or MAY forward jobs immediately to one of queue/spool jobs, feeding a job at a time to its Subordinate
its Subordinate Printers. In either case, the Non-Leaf Printer object Printer(s), or MAY forward jobs immediately to one of its Subordinate
is forwarding Job Creation operations to one of its Subordinate Printers. In either case, the Non-Leaf Printer object is forwarding
Printers. Only the time of forwarding of the Job Creation operations Job Creation operations to one of its Subordinate Printers. Only the
depends on whether the policy is to queue/spool jobs in the Non-Leaf time of forwarding of the Job Creation operations depends on whether
Printer or the Subordinate Printer. the policy is to queue/spool jobs in the Non-Leaf Printer or the
Subordinate Printer.
When a Non-Leaf Printer object creates a Job object in its Subordinate When a Non-Leaf Printer object creates a Job object in its
Printer, whether that Non-Leaf Printer object keeps a fully formed Job Subordinate Printer, whether that Non-Leaf Printer object keeps a
object or just keeps a mapping from the "job-ids" that it assigned to fully formed Job object or just keeps a mapping from the "job-ids"
those assigned by its Subordinate Printer object is IMPLEMENTATION- that it assigned to those assigned by its Subordinate Printer object
DEPENDENT. In either case, the Non-Leaf Printer MUST be able to accept is IMPLEMENTATION-DEPENDENT. In either case, the Non-Leaf Printer
and carry out future Job operations that specify the "job-id" that the MUST be able to accept and carry out future Job operations that
Non-Leaf Printer assigned and returned to the job submitting client. specify the "job-id" that the Non-Leaf Printer assigned and returned
to the job submitting client.
Table 7 lists the operations that directly affect jobs and the Table 8 lists the operations that directly affect jobs and the
forwarding behavior that a Non-Leaf Printer MUST exhibit to its forwarding behavior that a Non-Leaf Printer MUST exhibit to its
Subordinate Printers: Subordinate Printers:
Table 7 - Forwarding operations that affect Jobs objects Table 8 - Forwarding operations that affect Jobs objects
Job operation Non-Leaf Printer action Job operation Non-Leaf Printer action
Job operations: Job operations:
Reprocess-Job MUST forward to the appropriate Job in one of Reprocess-Job MUST forward to the appropriate Job in one of
its Subordinate Printers its Subordinate Printers
Cancel- MUST NOT forward
Current-Job Cancel-Current-
Job MUST NOT forward
Resume-Job MUST forward to the appropriate Job in one of Resume-Job MUST forward to the appropriate Job in one of
its Subordinate Printers its Subordinate Printers
Promote-Job MUST forward to the appropriate Job in one of Promote-Job MUST forward to the appropriate Job in one of
its Subordinate Printers its Subordinate Printers
IPP/1.1 Printer IPP/1.1 Printer
Operations: Operations:
Print-Job MUST forward immediately or queue to the Print-Job MUST forward immediately or queue to the
appropriate Subordinate Printer appropriate Subordinate Printer
Print-URI MUST forward immediately or queue to the Print-URI MUST forward immediately or queue to the
appropriate Subordinate Printer appropriate Subordinate Printer
Expires: February 15, 2001
Job operation Non-Leaf Printer action
Validate-Job MUST forward to the appropriate Subordinate Validate-Job MUST forward to the appropriate Subordinate
Printer Printer
Create-Job MUST forward immediately or queue to the Create-Job MUST forward immediately or queue to the
appropriate Subordinate Printer appropriate Subordinate Printer
Get-Jobs MUST forward to all its Subordinate Printers Get-Jobs MUST forward to all its Subordinate Printers
Purge-Jobs MUST forward to all its Subordinate Printers Purge-Jobs MUST forward to all its Subordinate Printers
IPP/1.1 Job IPP/1.1 Job
operations: operations:
Send-Document MUST forward immediately or queue to the Send-Document MUST forward immediately or queue to the
appropriate Job in one of its Subordinate appropriate Job in one of its Subordinate
Printers Printers
Send-URI MUST forward immediately or queue to the Send-URI MUST forward immediately or queue to the
appropriate Job in one of its Subordinate appropriate Job in one of its Subordinate
Printers Printers
Job operation Non-Leaf Printer action
appropriate Job in one of its Subordinate
Printers
Cancel-Job MUST forward to the appropriate Job in one of Cancel-Job MUST forward to the appropriate Job in one of
its Subordinate Printers its Subordinate Printers
Get-Job- MUST forward to the appropriate Job in one of Get-Job- MUST forward to the appropriate Job in one of
Attributes its Subordinate Printers, if the Non-Leaf Attributes its Subordinate Printers, if the Non-Leaf
Printer doesn't know the complete status of the Printer doesn't know the complete status of the
Job object Job object
Hold-Job MUST forward to the appropriate Job in one of Hold-Job MUST forward to the appropriate Job in one of
its Subordinate Printers its Subordinate Printers
Release-Job MUST forward to the appropriate Job in one of Release-Job MUST forward to the appropriate Job in one of
its Subordinate Printers its Subordinate Printers
Restart-Job MUST forward to the appropriate Job in one of Restart-Job MUST forward to the appropriate Job in one of
its Subordinate Printers its Subordinate Printers
IPP Set operations: See [ipp-set-ops] IPP Set operations: See [ipp-set-ops]
Set-Job- MUST forward to the appropriate Job in one of Set-Job- MUST forward to the appropriate Job in one of
Attributes its Subordinate Printers Attributes its Subordinate Printers
When a Printer receives a request that REQUIRES forwarding, it does so When a Printer receives a request that REQUIRES forwarding, it does
on a "best efforts basis", and returns a response to its client without so on a "best efforts basis", and returns a response to its client
waiting for responses from any of its Subordinate Printers. Such without waiting for responses from any of its Subordinate Printers.
forwarded requests could fail. In order for a client to become aware of Such forwarded requests could fail. In order for a client to become
such a condition, a new 'forwarded-operation-failed' event is defined, aware of such a condition, a new 'job-forwarded-operation-failed' Job
which a client can subscribe to (see section 10 and [ipp-ntfy]). event is defined, which a client can subscribe to (see section 10 and
[ipp-ntfy]).
The following Job Description attributes are defined to help represent 11.8 Additional attributes to help with fan-out
Job relationships for Fan-Out and forwarding of jobs:
1."output-device-assigned" (name(127)) - from [ipp-mod]: This attribute The following Job Description attributes are defined to help
identifies the Output Device to which the Printer object has assigned represent Job relationships for Fan-Out and forwarding of jobs:
this job. If an Output Device implements an embedded Printer object,
the Printer object NEED NOT set this attribute. If a print server
implements a Printer object, the value MAY be empty (zero-length
string) or not returned until the Printer object assigns an Output
Device to the job. This attribute is particularly useful when a
single Printer object supports multiple devices (so called "Fan-
Out").
2."original-requesting-user-name" (name(MAX)) - operation attribute 11.8.1 output-device-assigned (name(127)) Job Description attribute -
containing the user name of the original user, i.e., corresponds to from [RFC2911]
Expires: February 15, 2001 This attribute identifies the Output Device to which the Printer
the "requesting-user-name" operation attribute that the original object has assigned this job. If an Output Device implements an
client supplied to the first Printer object. The IPP/1.1 embedded Printer object, the Printer object NEED NOT set this
"requesting-user-name" operation attribute (see [ipp-mod]) is updated attribute. If a print server implements a Printer object, the value
by each client to be itself on each hop, i.e., the "requesting-user- MAY be empty (zero-length string) or not returned until the Printer
name" is the client forwarding the request, not the original client. object assigns an Output Device to the job. This attribute is
The "job-originating-user-name" Job Description attribute remains as particularly useful when a single Printer object supports multiple
the authenticated original user, not the parent Printer's devices (so called "Device Fan-Out").
authenticated host, and is forwarded by each client without changing
the value. 11.8.2 original-requesting-user-name (name(MAX)) operation attribute
The operation attribute containing the user name of the original
user, i.e., corresponds to the "requesting-user-name" operation
attribute that the original client supplied to the first Printer
object. The IPP/1.1 "requesting-user-name" operation attribute (see
[RFC2911]) is updated by each client to be itself on each hop, i.e.,
the "requesting-user-name" is the client forwarding the request, not
the original client. The "job-originating-user-name" Job Description
attribute remains as the authenticated original user, not the parent
Printer's authenticated host, and is forwarded by each client without
changing the value.
12 Conformance Requirements 12 Conformance Requirements
The Job and Printer Administrative operations defined in this document The Job and Printer Administrative operations defined in this
are OPTIONAL operations. However, some operations MUST be implemented document are OPTIONAL operations. However, some operations MUST be
if others are implemented as shown in Table 8. implemented if others are implemented as shown in Table 9.
Table 8 - Conformance Requirement Dependencies for Operations Table 9 - Conformance Requirement Dependencies for Operations
Operations REQUIRED If any of these operations are supported: Operations REQUIRED If any of these operations are supported:
Enable-Printer Disable-Printer Enable-Printer Disable-Printer
Disable-Printer Enable-Printer Disable-Printer Enable-Printer
Pause-Printer Resume-Printer Pause-Printer Resume-Printer
Resume-Printer Pause-Printer, Pause-Printer-After-Current-Job Resume-Printer Pause-Printer, Pause-Printer-After-Current-
Job
Hold-New-Jobs Release-Held-New-Jobs Hold-New-Jobs Release-Held-New-Jobs
Release-Held-New-Jobs Hold-New-Jobs Release-Held-New-Jobs Hold-New-Jobs
Activate-Printer, Deactivate-Printer Activate-Printer, Deactivate-Printer
Disable-Printer, Disable-Printer,
Pause-Printer-After- Pause-Printer-After-
Current-Job Current-Job
skipping to change at page 35, line 64 skipping to change at page 47, line 4
Cancel-Current-Job none Cancel-Current-Job none
Resume-Job Suspend-Current-Job Resume-Job Suspend-Current-Job
Suspend-Current-Job Resume-Job Suspend-Current-Job Resume-Job
Promote-Job none Promote-Job none
Schedule-Job-After Promote-Job Schedule-Job-After Promote-Job
Table 10 and Table 11 list the "printer-state-reasons" and "job-
state-reasons" values that are REQUIRED if the indicated operations
are supported.
Table 9 and Table 10 list the "printer-state-reasons" and "job-state- Table 10- Conformance Requirement Dependencies for "printer-state-
reasons" values that are REQUIRED if the indicated operations are
supported.
Expires: February 15, 2001
Table 9 - Conformance Requirement Dependencies for "printer-state-
reasons" Values reasons" Values
"printer-state- Conforman If any of the following Printer "printer-state- Conformance If any of the following Printer
reasons" values: ce Operations are supported: reasons" values: Requirement Operations are supported:
Requireme
nt
'paused' REQUIRED Pause-Printer, Pause-Printer-After- 'paused' REQUIRED Pause-Printer, Pause-Printer-
Current-Job, or Deactivate-Printer After-Current-Job, or
Deactivate-Printer
'hold-new-jobs' REQUIRED Hold-New-Jobs 'hold-new-jobs' REQUIRED Hold-New-Jobs
'moving-to-paused' OPTIONAL Pause-Printer, Pause-Printer-After- 'moving-to-paused' OPTIONAL Pause-Printer, Pause-Printer-
Current-Job, Deactivate-Printer After-Current-Job, Deactivate-
Printer
'deactivated' REQUIRED Deactivate-Printer 'deactivated' REQUIRED Deactivate-Printer
Table 10 - Conformance Requirement Dependencies for "job-state-reasons" Table 11- Conformance Requirement Dependencies for "job-state-
Values reasons" Values
"job-state-reasons" Conforman If any of the following Job operations "job-state-reasons" Conformance If any of the following Job
values: ce are supported: values: Requirement operations are supported:
Requireme
nt
'job-suspended' REQUIRED Suspend-Current-Job 'job-suspended' REQUIRED Suspend-Current-Job
'printer-stopped' REQUIRED always REQUIRED 'printer-stopped' REQUIRED always REQUIRED
13 IANA Considerations 13 IANA Considerations
The operations and attributes in this registration proposal will be 13.1 This section contains the registration information for IANA to add
published by IANA according to the procedures in RFC 2566 [rfc2566] to the various IPP Registries according to the procedures defined in
section 6.4 for operations with the following URL: RFC 2911 [RFC2911] section 6 to cover the definitions in this
document. Attribute Registrations
ftp.isi.edu/iana/assignments/ipp/operations/ipp-admin-ops.txt The following table lists all the attributes defined in this
document. These are to be registered according to the procedures in
RFC 2911 [RFC2911] section 6.2.
Job Description attributes: Ref. Section:
output-device-assigned (name(127)) RFC NNNN 11.8.1
Printer Description attributes: Ref. Section:
subordinate-printers-supported (1setOf uri) RFC NNNN 7.1
parent-printers-supported (1setOf uri) RFC NNNN 7.2
Operation attributes: Ref. Section:
original-requesting-user-name (name(MAX)) RFC NNNN 11.8.2
The resulting attribute registrations will be published in the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attributes/
area.
13.2 Attribute Value Registrations
This section lists the additional values that are defined in this
document for existing attributes.
13.2.1 Additional Keyword Attribute Value Registrations for the "job-
state-reasons" attribute
The following table the new keyword attribute value defined in this
document as an additional type2 keyword value for use with the "job-
state-reasons" Job Description attribute. This is to be registered
according to the procedures in RFC 2911 [RFC2911] section 6.1.
type2 keyword Attribute Values: Ref. Section:
job-suspended RFC NNNN 9.1
The resulting enum attribute value registration will be published in
the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute-
values/job-state-reasons/
area.
13.2.2 Additional Keyword Attribute Value Registrations for the
"printer-state-reasons" attribute
The following table all the new keyword attribute values defined in
this document as additional type2 keyword values for use with the
"printer-state-reasons" Printer Description attribute. These are to
be registered according to the procedures in RFC 2911 [RFC2911]
section 6.1.
type2 keyword Attribute Values: Ref. Section:
hold-new-jobs RFC NNNN 8.1
deactivated RFC NNNN 8.2
The resulting enum attribute value registrations will be published in
the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute-
values/printer-state-reasons/
area.
13.3 Additional Enum Attribute Value Registrations for the "operations-
supported" Printer Attribute
The following table lists all the new enum attribute values defined
in this document as additional type2 enum values for use with the
"operations-supported" Printer Description attribute. These are to
be registered according to the procedures in RFC 2911 [RFC2911]
section 6.1.
type2 enum Attribute Values: Value Ref. Section:
Enable-Printer 0x22 RFC NNNN 3
Disable-Printer 0x23 RFC NNNN 3
Pause-Printer-After-Current-Job 0x24 RFC NNNN 3
Hold-New-Jobs 0x25 RFC NNNN 3
Release-Held-New-Jobs 0x26 RFC NNNN 3
Deactivate-Printer 0x27 RFC NNNN 3
Activate-Printer 0x28 RFC NNNN 3
Restart-Printer 0x29 RFC NNNN 3
Shutdown-Printer 0x2A RFC NNNN 3
Startup-Printer 0x2B RFC NNNN 3
The resulting enum attribute value registrations will be published in
the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute-
values/operations-supported/
area.
13.4 Additional keyword Attribute Value Registrations for the "notify-
events" Subscription Template Attribute
The following table lists the event keyword defined in this document
as an additional type2 keyword value for use with the "notify-events"
Subscription Template attribute, i.e., the "notify-events", "notify-
events-default", and "notify-events-supported" attributes. This is
to be registered according to the procedures in RFC 2911 [RFC2911]
section 6.1 and [ipp-ntfy] section 13.6.
type2 keyword Attribute Value: Ref. Section:
job-forwarded-operation-failed RFC NNNN 10
The resulting status code registration will be published in the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute-
values/notify-events/
area.
13.5 Operation Registrations
The following table lists all of the operations defined in this
document. These are to be registered according to the procedures in
RFC 2911 [RFC2911] section 6.4.
Operations: Ref. Section:
Enable-Printer Operation RFC NNNN 3.1.2
Disable-Printer Operation RFC NNNN 3.1.1
Pause-Printer-After-Current-Job Operation RFC NNNN 3.2.1
Hold-New-Jobs Operation RFC NNNN 3.3.1
Release-Held-New-Jobs Operation RFC NNNN 3.3.2
Deactivate-Printer Operation RFC NNNN 3.4.1
Activate-Printer Operation RFC NNNN 3.4.2
Restart-Printer Operation RFC NNNN 3.5.1
Shutdown-Printer Operation RFC NNNN 3.5.2
Startup-Printer Operation RFC NNNN 3.5.3
The resulting enum attribute value registrations will be published in
the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute-
values/operations/
area.
13.6 Status code Registrations
The following table lists the status code defined in this document.
This is to be registered according to the procedures in RFC 2911
[RFC2911] section 6.6.
Status codes: Ref. Section:
server-error-printer-is-deactivated RFC NNNN 5.1
The resulting status code registration will be published in the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/status-codes/
area.
14 Internationalization Considerations 14 Internationalization Considerations
This document has the same localization considerations as the [ipp-mod]. This document has the same localization considerations as the
[RFC2911].
15 Security Considerations 15 Security Considerations
The IPP Model and Semantics document [ipp-mod] discusses high level The IPP Model and Semantics document [RFC2911] discusses high level
security requirements (Client Authentication, Server Authentication and security requirements (Client Authentication, Server Authentication
Operation Privacy). Client Authentication is the mechanism by which the and Operation Privacy). Client Authentication is the mechanism by
client proves its identity to the server in a secure manner. Server which the client proves its identity to the server in a secure
Authentication is the mechanism by which the server proves its identity manner. Server Authentication is the mechanism by which the server
to the client in a secure manner. Operation Privacy is defined as a proves its identity to the client in a secure manner. Operation
mechanism for protecting operations from eavesdropping. Privacy is defined as a mechanism for protecting operations from
eavesdropping.
Expires: February 15, 2001
16 Author's Addresses 16 Author's Addresses
Carl Kugler Carl Kugler
IBM IBM
Boulder CO Boulder CO
Phone: (303) 924-5060 Phone: (303) 924-5060
FAX: FAX:
e-mail: kugler@us.ibm.com e-mail: kugler@us.ibm.com
skipping to change at page 37, line 34 skipping to change at page 52, line 21
e-mail: hastings@cp10.es.xerox.com e-mail: hastings@cp10.es.xerox.com
Harry Lewis Harry Lewis
IBM IBM
Boulder CO Boulder CO
Phone: (303) 924-5337 Phone: (303) 924-5337
FAX: FAX:
e-mail: harryl@us.ibm.com e-mail: harryl@us.ibm.com
IPP Web Page: http://www.pwg.org/ipp/
IPP Mailing List: ipp@pwg.org
To subscribe to the ipp mailing list, send the following email:
1) send it to majordomo@pwg.org
2) leave the subject line blank
3) put the following two lines in the message body:
subscribe ipp
end
Implementers of this specification document are encouraged to join
the IPP Mailing List in order to participate in any discussions of
clarification issues and review of registration proposals for
additional attributes and values. In order to reduce spam the
mailing list rejects mail from non-subscribers, so you must subscribe
to the mailing list in order to send a question or comment to the
mailing list.
17 References 17 References
[ipp-iig] [ipp-iig]
Hastings, T., Manros, C., "Internet Printing Protocol/1.1: draft- Hastings, T., Manros, C., "Internet Printing Protocol/1.1: draft-
ietf-ipp-implementers-guide-v11-01.txt, work in progress, May 9, ietf-ipp-implementers-guide-v11-03.txt, work in progress, July 17,
2000. 2001.
[ipp-mod]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf-
ipp-model-v11-07.txt>, May 22, 2000.
[ipp-ntfy] [ipp-ntfy]
Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M., Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M.,
Bergman, R., "Internet Printing Protocol/1.1: IPP Event Bergman, R., "Internet Printing Protocol/1.1: IPP Event
Notification Specification", <draft-ietf-ipp-not-spec-04.txt>, July Notification Specification", <draft-ietf-ipp-not-spec-07.txt>, July
13, 2000. 17, 2001.
[ipp-ops-admin-req] [ipp-ops-admin-req]
Hastings, T., "Internet Printing Protocol (IPP): Requirements for Hastings, T., "Internet Printing Protocol (IPP): Requirements for
Job, Printer, and Device Administrative Operations", <draft-ietf- Job, Printer, and Device Administrative Operations", <draft-ietf-
ipp-ops-admin-req-00.txt>, work in progress, July 19, 2000. ipp-ops-admin-req-01.txt>, work in progress, July 17, 2001.
Expires: February 15, 2001
[ipp-pro]
Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11-
06.txt, May 30, 2000.
[RFC2566] [RFC2566]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566,
April 1999. April 1999.
[RFC2910]
Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
Protocol/1.1: Encoding and Transport", RFC 2910, September 2000.
[RFC2911]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", RFC 2911,
September 2000.
Change History of this document is available at: Change History of this document is available at:
ftp://ftp.pwg.org/pub/pwg/ipp/new_OPS/ipp-ops-set2-change- ftp://ftp.pwg.org/pub/pwg/ipp/new_OPS/ipp-ops-set2-change-
history.txt history.txt
18 Appendix A: Full Copyright Statement 18 Summary of Base IPP Documents
Copyright (C) The Internet Society (1998,1999). All Rights Reserved The base set of IPP documents includes:
Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig]
Mapping between LPD and IPP Protocols [RFC2569]
Internet Printing Protocol (IPP): IPP Event Notifications and
Subscriptions [ipp-ntfy]
The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet. It identifies
requirements for three types of users: end users, operators, and
administrators. It calls out a subset of end user requirements that
are satisfied in IPP/1.0. A few OPTIONAL operator operations have
been added to IPP/1.1.
The "Rationale for the Structure and Model and Protocol for the
Internet Printing Protocol" document describes IPP from a high level
view, defines a roadmap for the various documents that form the suite
of IPP specification documents, and gives background and rationale
for the IETF working group's major decisions.
The "Internet Printing Protocol/1.1: Model and Semantics" document
describes a simplified model with abstract objects, their attributes,
and their operations that are independent of encoding and transport.
It introduces a Printer and a Job object. The Job object optionally
supports multiple documents per Job. It also addresses security,
internationalization, and directory issues.
The "Internet Printing Protocol/1.1: Encoding and Transport" document
is a formal mapping of the abstract operations and attributes defined
in the model document onto HTTP/1.1 [RFC2616]. It defines the
encoding rules for a new Internet MIME media type called
"application/ipp". This document also defines the rules for
transporting over HTTP a message body whose Content-Type is
"application/ipp". This document defines the 'ippget' scheme for
identifying IPP printers and jobs.
The "Internet Printing Protocol/1.1: Implementer's Guide" document
gives insight and advice to implementers of IPP clients and IPP
objects. It is intended to help them understand IPP/1.1 and some of
the considerations that may assist them in the design of their client
and/or IPP object implementations. For example, a typical order of
processing requests is given, including error checking. Motivation
for some of the specification decisions is also included.
The "Mapping between LPD and IPP Protocols" document gives some
advice to implementers of gateways between IPP and LPD (Line Printer
Daemon) implementations.
The "IPP Event Notifications and Subscriptions" document defines an
extension to IPP/1.0 [RFC2566, RFC2565] and IPP/1.1 [RFC2911,
RFC2910]. This extension allows a client to subscribe to printing
related Events and defines the semantics for delivering asynchronous
Event Notifications to the specified Notification Recipient via a
specified Delivery Method (i.e., protocols) defined in (separate)
Delivery Method documents.
19 Appendix A: Full Copyright Statement
Copyright (C) The Internet Society (1998,1999,2000,2001). All Rights
Reserved
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it
assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are included kind, provided that the above copyright notice and this paragraph are
on all such copies and derivative works. However, this document itself included on all such copies and derivative works. However, this
may not be modified in any way, such as by removing the copyright notice document itself may not be modified in any way, such as by removing
or references to the Internet Society or other Internet organizations, the copyright notice or references to the Internet Society or other
except as needed for the purpose of developing Internet standards in Internet organizations, except as needed for the purpose of
which case the procedures for copyrights defined in the Internet developing Internet standards in which case the procedures for
Standards process must be followed, or as required to translate it into copyrights defined in the Internet Standards process must be
languages other than English. followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Expires: February 15, 2001 Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

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