Network Working Group C. Kugler
Request for Comments: 3998 H. Lewis
Category: Standards Track IBM Corporation
T. Hastings, Ed.
Xerox Corporation
March 2005
Network Working Group C. Kugler
Request for Comments: 3998 H. Lewis
Category: Standards Track IBM Corporation
T. Hastings, Ed.
Xerox Corporation
March 2005
Internet Printing Protocol (IPP): Job and Printer Administrative Operations
Internet打印协议（IPP）：作业和打印机管理操作
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document specifies the following 16 additional OPTIONAL system administration operations for use with the Internet Printing Protocol/1.1 (IPP), plus a few associated attributes, values, and status codes, and using the IPP Printer object to manage printer fan-out and fan-in.
本文档指定了以下16个附加可选系统管理操作，用于Internet打印协议/1.1（IPP），以及一些相关属性、值和状态代码，并使用IPP打印机对象管理打印机扇出和扇入。
Printer operations: Job operations: Enable-Printer and Disable-Printer Reprocess-Job Pause-Printer-After-Current-Job Cancel-Current-Job Hold-New-Jobs and Release-Held-New-Jobs Suspend-Current-Job Deactivate-Printer and Activate-Printer Resume-Job Restart-Printer Promote-Job Shutdown-Printer and Startup-Printer Schedule-Job-After
打印机操作：作业操作：启用和禁用打印机重新处理作业当前作业后暂停打印机取消当前作业保留新作业并释放保留的新作业暂停当前作业停用打印机并激活打印机恢复作业重新启动打印机提升作业关闭打印机并启动打印机计划作业之后
Table of Contents
目录
1. Introduction.................................................. 4
2. Terminology................................................... 4
2.1. Conformance Terminology................................. 4
2.2. Other Terminology....................................... 5
3. Definition of the Printer Operations.......................... 6
3.1. The Disable and Enable Printer Operations............... 7
3.1.1. Disable-Printer Operation....................... 7
3.1.2. Enable-Printer Operation........................ 8
3.2. The Pause and Resume Printer Operations................. 8
3.2.1. Pause-Printer-After-Current-Job Operation....... 9
3.3. Hold and Release New Jobs Operations.................... 11
3.3.1. Hold-New-Jobs Operation......................... 11
3.3.2. Release-Held-New-Jobs Operation................. 12
3.4. Deactivate and Activate Printer Operations.............. 12
3.4.1. Deactivate-Printer Operation.................... 13
3.4.2. Activate-Printer Operation...................... 13
3.5. Restart-Printer, Shutdown-Printer,
and Startup-Printer Operations.......................... 14
3.5.1. Restart-Printer Operation....................... 14
3.5.2. Shutdown-Printer Operation...................... 14
3.5.3. Startup-Printer Operation....................... 15
4. Definition of the Job Operations.............................. 16
4.1. Reprocess-Job Operation................................. 17
4.2. Cancel-Current-Job Operation............................ 17
4.3. Suspend and Resume Job Operations....................... 18
4.3.1. Suspend-Current-Job Operation................... 19
4.3.2. Resume-Job Operation............................ 20
4.4. Job Scheduling Operations............................... 20
4.4.1. Promote-Job Operation........................... 20
4.4.2. Schedule-Job-After Operation.................... 21
5. Additional Status Codes....................................... 23
5.1. 'server-error-printer-is-deactivated' (0x050A).......... 23
6. Use of Operation Attributes
That Are Messages from the Operator........................... 23
7. New Printer Description Attributes............................ 26
7.1. subordinate-printers-supported (1setOf uri)............. 26
7.2. parent-printers-supported (1setOf uri).................. 26
8. Additional Values for
the "printer-state-reasons" Printer Description Attribute..... 26
8.1. 'hold-new-jobs' Value................................... 27
8.2. 'deactivated' Value..................................... 27
9. Additional Values for
the "job-state-reasons" Job Description attribute............. 27
9.1. 'job-suspended' Value................................... 27
10. Use of the Printer Object to Represent
IPP Printer Fan-Out and IPP Printer Fan-In.................... 27
1. Introduction.................................................. 4
2. Terminology................................................... 4
2.1. Conformance Terminology................................. 4
2.2. Other Terminology....................................... 5
3. Definition of the Printer Operations.......................... 6
3.1. The Disable and Enable Printer Operations............... 7
3.1.1. Disable-Printer Operation....................... 7
3.1.2. Enable-Printer Operation........................ 8
3.2. The Pause and Resume Printer Operations................. 8
3.2.1. Pause-Printer-After-Current-Job Operation....... 9
3.3. Hold and Release New Jobs Operations.................... 11
3.3.1. Hold-New-Jobs Operation......................... 11
3.3.2. Release-Held-New-Jobs Operation................. 12
3.4. Deactivate and Activate Printer Operations.............. 12
3.4.1. Deactivate-Printer Operation.................... 13
3.4.2. Activate-Printer Operation...................... 13
3.5. Restart-Printer, Shutdown-Printer,
and Startup-Printer Operations.......................... 14
3.5.1. Restart-Printer Operation....................... 14
3.5.2. Shutdown-Printer Operation...................... 14
3.5.3. Startup-Printer Operation....................... 15
4. Definition of the Job Operations.............................. 16
4.1. Reprocess-Job Operation................................. 17
4.2. Cancel-Current-Job Operation............................ 17
4.3. Suspend and Resume Job Operations....................... 18
4.3.1. Suspend-Current-Job Operation................... 19
4.3.2. Resume-Job Operation............................ 20
4.4. Job Scheduling Operations............................... 20
4.4.1. Promote-Job Operation........................... 20
4.4.2. Schedule-Job-After Operation.................... 21
5. Additional Status Codes....................................... 23
5.1. 'server-error-printer-is-deactivated' (0x050A).......... 23
6. Use of Operation Attributes
That Are Messages from the Operator........................... 23
7. New Printer Description Attributes............................ 26
7.1. subordinate-printers-supported (1setOf uri)............. 26
7.2. parent-printers-supported (1setOf uri).................. 26
8. Additional Values for
the "printer-state-reasons" Printer Description Attribute..... 26
8.1. 'hold-new-jobs' Value................................... 27
8.2. 'deactivated' Value..................................... 27
9. Additional Values for
the "job-state-reasons" Job Description attribute............. 27
9.1. 'job-suspended' Value................................... 27
10. Use of the Printer Object to Represent
IPP Printer Fan-Out and IPP Printer Fan-In.................... 27
10.1. IPP Printer Fan-Out..................................... 28
10.2. IPP Printer Fan-In...................................... 28
10.3. Printer Object Attributes Used
to Represent Printer Fan-Out and Printer Fan-In......... 29
10.4. Subordinate Printer URI................................. 29
10.5. Printer Object Attributes Used
to Represent Output Device Fan-Out...................... 30
10.6. Figures to Show All Possible Configurations............. 30
10.7. Forwarding Requests..................................... 33
10.7.1. Forwarding Requests
that Affect Printer Objects..................... 33
10.7.2. Forwarding Requests that Affect Jobs............ 35
10.8. Additional Attributes to Help with Fan-Out.............. 37
10.8.1. output-device-assigned (name(127))
Job Description Attribute - from [RFC2911]...... 37
10.8.2. original-requesting-user-name (name(MAX))
Operation and Job Description Attribute......... 37
10.8.3. requesting-user-name (name(MAX))
Operation Attribute - Additional Semantics...... 38
10.8.4. job-originating-user-name (name(MAX))
Job Description Attribute -
Additional Semantics............................ 38
11. Conformance Requirements...................................... 38
12. Normative References.......................................... 39
13. Informative References........................................ 40
14. IANA Considerations........................................... 40
14.1. Attribute Registrations................................. 41
14.2. Attribute Value Registrations........................... 41
14.3. Additional Enum Attribute Value Registrations........... 41
14.4. Operation Registrations................................. 42
14.5. Status Code Registrations............................... 43
15. Internationalization Considerations........................... 43
16. Security Considerations....................................... 43
17. Summary of Base IPP Documents................................. 44
Authors' Addresses................................................ 45
Full Copyright Statement.......................................... 46
10.1. IPP Printer Fan-Out..................................... 28
10.2. IPP Printer Fan-In...................................... 28
10.3. Printer Object Attributes Used
to Represent Printer Fan-Out and Printer Fan-In......... 29
10.4. Subordinate Printer URI................................. 29
10.5. Printer Object Attributes Used
to Represent Output Device Fan-Out...................... 30
10.6. Figures to Show All Possible Configurations............. 30
10.7. Forwarding Requests..................................... 33
10.7.1. Forwarding Requests
that Affect Printer Objects..................... 33
10.7.2. Forwarding Requests that Affect Jobs............ 35
10.8. Additional Attributes to Help with Fan-Out.............. 37
10.8.1. output-device-assigned (name(127))
Job Description Attribute - from [RFC2911]...... 37
10.8.2. original-requesting-user-name (name(MAX))
Operation and Job Description Attribute......... 37
10.8.3. requesting-user-name (name(MAX))
Operation Attribute - Additional Semantics...... 38
10.8.4. job-originating-user-name (name(MAX))
Job Description Attribute -
Additional Semantics............................ 38
11. Conformance Requirements...................................... 38
12. Normative References.......................................... 39
13. Informative References........................................ 40
14. IANA Considerations........................................... 40
14.1. Attribute Registrations................................. 41
14.2. Attribute Value Registrations........................... 41
14.3. Additional Enum Attribute Value Registrations........... 41
14.4. Operation Registrations................................. 42
14.5. Status Code Registrations............................... 43
15. Internationalization Considerations........................... 43
16. Security Considerations....................................... 43
17. Summary of Base IPP Documents................................. 44
Authors' Addresses................................................ 45
Full Copyright Statement.......................................... 46
List of Tables
表格一览表
Table 1. Printer Operation Operation-Id Assignments.............. 6
Table 2. Pause and Resume Printer Operations..................... 9
Table 3. State Transition Table for
Pause-Printer-After-Current-Job Operation............... 10
Table 4. Job Operation Operation-Id Assignments.................. 16
Table 5. Operation Attribute Support for Printer Operations...... 24
Table 6. Operation Attribute Support for Job Operations.......... 25
Table 7. Forwarding Operations that Affect Printer Objects....... 34
Table 8. Forwarding Operations that Affect Jobs Objects.......... 36
Table 1. Printer Operation Operation-Id Assignments.............. 6
Table 2. Pause and Resume Printer Operations..................... 9
Table 3. State Transition Table for
Pause-Printer-After-Current-Job Operation............... 10
Table 4. Job Operation Operation-Id Assignments.................. 16
Table 5. Operation Attribute Support for Printer Operations...... 24
Table 6. Operation Attribute Support for Job Operations.......... 25
Table 7. Forwarding Operations that Affect Printer Objects....... 34
Table 8. Forwarding Operations that Affect Jobs Objects.......... 36
Table 9. Conformance Requirement Dependencies for Operations..... 38
Table 10. Conformance Requirement Dependencies
for "printer-state-reasons" Values...................... 39
Table 11. Conformance Requirement Dependencies
for "job-state-reasons" Values.......................... 39
Table 9. Conformance Requirement Dependencies for Operations..... 38
Table 10. Conformance Requirement Dependencies
for "printer-state-reasons" Values...................... 39
Table 11. Conformance Requirement Dependencies
for "job-state-reasons" Values.......................... 39
List of Figures
数字一览表
Figure 1. Embedded Printer Object................................ 31
Figure 2. Hosted Printer Object.................................. 31
Figure 3. Output Device Fan-Out.................................. 31
Figure 4. Chained IPP Printer Objects............................ 32
Figure 5. IPP Printer Object Fan-Out............................. 32
Figure 6. IPP Printer Object Fan-In.............................. 33
Figure 1. Embedded Printer Object................................ 31
Figure 2. Hosted Printer Object.................................. 31
Figure 3. Output Device Fan-Out.................................. 31
Figure 4. Chained IPP Printer Objects............................ 32
Figure 5. IPP Printer Object Fan-Out............................. 32
Figure 6. IPP Printer Object Fan-In.............................. 33
The Internet Printing Protocol (IPP) is an application level protocol that can be used for distributed printing using Internet tools and technologies. IPP version 1.1 ([RFC2911, RFC2910]) focuses on end-user functionality, with a few administrative operations included. This document defines additional OPTIONAL end user, operator, and administrator operations used to control Jobs and Printers. In addition, this document extends the semantic model of the Printer object by allowing them to be configured into trees and/or inverted trees that represent Printer object Fan-Out and Printer object Fan-In, respectively. The special case of a tree with only a single Subordinate node represents Chained Printers. This document is a registration proposal for an extension to IPP/1.0 and IPP/1.1 following the registration procedures in those documents.
Internet打印协议（IPP）是一种应用程序级协议，可用于使用Internet工具和技术进行分布式打印。IPP版本1.1（[RFC2911，RFC2910]）侧重于最终用户功能，包括一些管理操作。本文档定义了用于控制作业和打印机的其他可选最终用户、操作员和管理员操作。此外，本文档还扩展了打印机对象的语义模型，允许将它们配置为分别表示打印机对象扇出和打印机对象扇入的树和/或倒树。只有一个从属节点的树的特例表示链式打印机。本文件是按照IPP/1.0和IPP/1.1文件中的注册程序对其进行扩展的注册提案。
The requirements and use cases for this document are defined in [RFC3239].
[RFC3239]中定义了本文件的要求和用例。
This section defines the terminology used throughout this document.
本节定义了本文件中使用的术语。
Capitalized terms such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, MAY, NEED NOT, and OPTIONAL have special meaning relating to conformance as defined in RFC 2119 [RFC2119] and [RFC2911], section 12.1. If an implementation supports the extension defined in this document, then these terms apply; otherwise, they do not. These terms define conformance to this document only; they do not affect conformance to other documents, unless explicitly stated otherwise.
如RFC 2119[RFC2119]和[RFC2911]第12.1节所定义，大写术语（如必须、不得、必需、应该、不应该、可能、不需要和可选）具有与合规性相关的特殊含义。如果实施支持本文件中定义的扩展，则这些条款适用；否则，他们不会。这些术语仅定义与本文件的一致性；除非另有明确说明，否则它们不影响与其他文件的一致性。
This document uses terms such as "client", "Printer", "Job", "attributes", "keywords", "operation", and "support". These terms have special meaning and are defined in the model terminology ([RFC2911], section 12.2).
本文档使用诸如“客户机”、“打印机”、“作业”、“属性”、“关键字”、“操作”和“支持”等术语。这些术语具有特殊含义，并在模型术语（[RFC2911]，第12.2节）中定义。
In addition, the following capitalized terms are defined:
此外，定义了以下大写术语：
IPP Printer object (or Printer for short) - A software abstraction defined by [RFC2911].
IPP打印机对象（简称打印机）-由[RFC2911]定义的软件抽象。
Printer Operation - An operation whose target is an IPP Printer object and whose effect is on the Printer object.
打印机操作-目标为IPP打印机对象且其效果影响打印机对象的操作。
Output Device - The physical imaging mechanism that an IPP Printer controls. Note: although this term is capitalized in this specification (but not in [RFC2911]), there is no formal object called an Output Device defined in this document (or in [RFC2911]).
输出设备—IPP打印机控制的物理成像机制。注：尽管本规范（但[RFC2911]中未定义）中该术语大写，但本文件（或[RFC2911]中）中未定义称为输出设备的正式对象。
Output Device Fan-Out - A configuration in which an IPP Printer controls more than one Output Device.
输出设备扇出-IPP打印机控制多个输出设备的配置。
Printer Fan-Out - A configuration in which an IPP Printer object controls more than one Subordinate IPP Printer object.
打印机扇出-IPP打印机对象控制多个从属IPP打印机对象的配置。
Printer Fan-In - A configuration in which an IPP Printer object is controlled by more than one IPP Printer object.
打印机扇入—IPP打印机对象由多个IPP打印机对象控制的配置。
Subordinate Printer - An IPP Printer object that is controlled by another IPP Printer object. Such a Subordinate Printer MAY have zero or more Subordinate Printers.
从属打印机-由另一个IPP打印机对象控制的IPP打印机对象。这样的从属打印机可以有零台或多台从属打印机。
Leaf Printer - An IPP Printer object that has no Subordinate Printers.
叶子打印机-没有从属打印机的IPP打印机对象。
Non-Leaf Printer - An IPP Printer object that has one or more Subordinate Printers. A Non-Leaf Printer is also called a Parent Printer.
无叶打印机-具有一个或多个从属打印机的IPP打印机对象。无叶打印机也称为父打印机。
Chained Printer - a Non-Leaf Printer that has exactly one Subordinate Printer.
链式打印机-仅具有一个附属打印机的非页式打印机。
Job Creation operations - IPP operations that create a Job object: Print-Job, Print-URI, and Create-Job.
作业创建操作-创建作业对象的IPP操作：打印作业、打印URI和创建作业。
All Printer Operations are directed at Printer objects. A client MUST always supply the "printer-uri" operation attribute in order to identify the correct target of the operation. These descriptions assume all of the common semantics of the IPP/1.1 Model and Semantics document ([RFC2911], section 3.1).
所有打印机操作都指向打印机对象。客户端必须始终提供“打印机uri”操作属性，以便标识正确的操作目标。这些描述假设IPP/1.1模型和语义文档（[RFC2911]，第3.1节）的所有通用语义。
The Printer Operations defined in this document are summarized in Table 1.
表1总结了本文档中定义的打印机操作。
Table 1. Printer Operation Operation-Id Assignments
表1。打印机操作Id分配
Operation Name Operation-Id Brief Description
--------------------------------------------------------------------
Enable-Printer 0x22 Allows the target Printer to accept
Job Creation operations.
Operation Name Operation-Id Brief Description
--------------------------------------------------------------------
Enable-Printer 0x22 Allows the target Printer to accept
Job Creation operations.
Disable-Printer 0x23 Prevents the target Printer from accepting Job Creation operations.
禁用打印机0x23可防止目标打印机接受作业创建操作。
Pause-Printer- 0x24 Pauses the Printer after the current After-Current- job has been sent to the Output Job Device.
暂停打印机-0x24在当前作业发送到输出作业设备后暂停打印机。
Hold-New-Jobs 0x25 Finishes processing all currently pending jobs. Any new jobs are placed in the 'pending-held' state.
保留新作业0x25完成处理所有当前挂起的作业。任何新作业都将处于“挂起挂起”状态。
Release-Held- 0x26 Releases all jobs to the 'pending' New-Jobs state that had been held by the effect of a previous Hold-New-Jobs operation and condition the Printer so that it no longer holds new jobs.
Release Hold（释放保留）-0x26将所有作业释放到“挂起”新作业状态，该状态由先前的“保留新作业”操作保持，并调整打印机，使其不再保留新作业。
Deactivate- 0x27 Puts the Printer into a read-only Printer deactivated state.
停用-0x27将打印机置于只读打印机停用状态。
Activate- 0x28 Restores the Printer to normal Printer activity.
激活-0x28将打印机恢复为正常打印机活动。
Restart-Printer 0x29 Restarts the target Printer and re-initializes the software.
重新启动打印机0x29重新启动目标打印机并重新初始化软件。
Shutdown- 0x2A Shuts down the target Printer so that Printer it cannot be restarted or queried.
关机-0x2A关闭目标打印机，使其无法重新启动或查询。
Startup-Printer 0x2B Starts up the instance of the Printer object.
启动打印机0x2B启动打印机对象的实例。
All of the operations in this document are OPTIONAL for an IPP object to support. Unless the specification of an OPTIONAL operation requires support of another OPTIONAL operation, conforming implementations may support any combination of these operations. Many of the operations come in pairs, so both are REQUIRED if either one is implemented.
本文档中的所有操作都是IPP对象支持的可选操作。除非可选操作的规范要求支持另一个可选操作，否则一致性实现可以支持这些操作的任何组合。许多操作是成对的，因此如果实现了其中一个操作，则两个操作都是必需的。
This section defines the OPTIONAL Disable-Printer and Enable-Printer operations that stop and start the IPP Printer object from accepting new IPP jobs. If either of these operations are supported, both MUST be supported.
本节定义了可选的“禁用打印机”和“启用打印机”操作，用于停止和启动IPP打印机对象接受新IPP作业。如果支持这两种操作中的任何一种，则必须同时支持这两种操作。
These operations allow the operator to control whether the Printer will accept new Job Creation (Print-Job, Print-URI, and Create-Job) operations. These operations have no other effect on the Printer, so the Printer continues to accept all other operations and continues to schedule and process jobs normally. In other words, these operations control the "input of new jobs" to the IPP Printer, and the Pause and Resume operations (see section 3.2) independently control the "output of new jobs" from the IPP Printer to the Output Device.
这些操作允许操作员控制打印机是否接受新作业创建（打印作业、打印URI和创建作业）操作。这些操作对打印机没有其他影响，因此打印机将继续接受所有其他操作，并继续正常安排和处理作业。换句话说，这些操作控制IPP打印机的“新作业输入”，暂停和恢复操作（见第3.2节）独立控制从IPP打印机到输出设备的“新作业输出”。
This OPTIONAL operation allows a client to stop the Printer object from accepting new jobs; i.e., it causes the Printer to reject subsequent Job Creation operations and return the 'server-error-not-accepting-jobs' status code. The Printer still accepts all other operations, including Validate-Job, Send-Document, and Send-URI operations. Thus a Disable-Printer operation allows a client to continue submitting multiple documents of a multiple document job if the Create-Job operation had already been accepted. All previously created or submitted Jobs and all Jobs currently processing continue unaffected.
此可选操作允许客户端停止打印机对象接受新作业；i、 例如，它会导致打印机拒绝后续的作业创建操作，并返回“服务器错误不接受作业”状态代码。打印机仍然接受所有其他操作，包括验证作业、发送文档和发送URI操作。因此，如果已接受创建作业操作，则禁用打印机操作允许客户端继续提交多文档作业的多个文档。以前创建或提交的所有作业以及当前正在处理的所有作业继续不受影响。
The IPP Printer MUST accept the request in any state. The Printer sets the value of its "printer-is-accepting-jobs" READ-ONLY Printer Description attribute to 'false' (see [RFC2911], section 4.4.20), no matter what the previous value was. This operation has no immediate or direct effect on the Printer's "printer-state" and "printer-state-reasons" attributes.
IPP打印机必须在任何状态下接受请求。打印机将其“打印机正在接受作业”只读打印机描述属性的值设置为“false”（请参阅[RFC2911]，第4.4.20节），无论之前的值是什么。此操作不会立即或直接影响打印机的“打印机状态”和“打印机状态原因”属性。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911] sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参见[RFC2911]第8.3节）必须是打印机对象的操作员或管理员（请参见[RFC2911]第1节和第8.5节）。
The Disable-Printer Request and Disable-Printer Response have the same attribute groups and attributes as do the Pause-Printer 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).
禁用打印机请求和禁用打印机响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This OPTIONAL operation allows a client to start the Printer object accepting jobs; i.e., it causes the Printer to accept subsequent Job Creation operations. The Printer still accepts all other operations. All previously submitted and currently processing Jobs continue unaffected.
此可选操作允许客户端启动打印机对象接受作业；i、 例如，它使打印机接受后续的作业创建操作。打印机仍接受所有其他操作。所有以前提交和当前正在处理的作业继续不受影响。
The IPP Printer MUST accept the request in any state. The Printer sets the value of its "printer-is-accepting-jobs" READ-ONLY Printer Description attribute to 'true' (see [RFC2911], section 4.4.20), no matter what the previous value was. This operation has no immediate or direct effect on the Printer's "printer-state" and "printer-state-reasons" attributes.
IPP打印机必须在任何状态下接受请求。打印机将其“打印机正在接受作业”只读打印机描述属性的值设置为“真”（请参阅[RFC2911]，第4.4.20节），无论之前的值是什么。此操作不会立即或直接影响打印机的“打印机状态”和“打印机状态原因”属性。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911] sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参见[RFC2911]第8.3节）必须是打印机对象的操作员或管理员（请参见[RFC2911]第1节和第8.5节）。
The Enable-Printer Request and Enable-Printer Response have the same attribute groups and attributes as does 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).
启用打印机请求和启用打印机响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.8.1和3.2.8.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This section leaves the OPTIONAL IPP/1.1 Pause-Printer (see [RFC2911], sections 3.2.7) ambiguous as to whether it stops the Printer immediately or after the current job. It also defines the OPTIONAL Pause-Printer-After-Current-Job operation as following the current job. These operations affect the scheduling of IPP jobs. If either of these Pause Printer operations are supported, then the Resume-Printer operation MUST be supported.
本节对可选IPP/1.1暂停打印机（参见[RFC2911]，第3.2.7节）是否立即停止打印机或在当前作业后停止打印机不明确。它还将当前作业操作之后的可选暂停打印机定义为当前作业之后的暂停打印机。这些操作会影响IPP作业的调度。如果支持这些暂停打印机操作之一，则必须支持恢复打印机操作。
These operations allow the operator to control whether the Printer will send new IPP jobs to the associated Output Device(s) that the IPP Printer object represents. These operations have no other effect on the Printer, so the Printer continues to accept all operations.
这些操作允许操作员控制打印机是否将新的IPP作业发送到IPP打印机对象表示的关联输出设备。这些操作对打印机没有其他影响，因此打印机将继续接受所有操作。
In other words, these operations control the "output of new jobs" to the Output Device(s), and the Disable and Enable Printer Operations (see section 3.1) independently control the "input of new jobs" to the IPP Printer.
换句话说，这些操作控制输出设备的“新作业输出”，禁用和启用打印机操作（见第3.1节）独立控制IPP打印机的“新作业输入”。
Table 2. Pause and Resume Printer Operations
表2。暂停并恢复打印机操作
Pause and Resume Printers Description
--------------------------------------------------------------------
IPP/1.1 Pause Printer Stops the IPP Printer from sending
new IPP Jobs to the Output Device(s)
either immediately or after the
current job completes, depending on
implementation, as defined in
[RFC2911].
Pause and Resume Printers Description
--------------------------------------------------------------------
IPP/1.1 Pause Printer Stops the IPP Printer from sending
new IPP Jobs to the Output Device(s)
either immediately or after the
current job completes, depending on
implementation, as defined in
[RFC2911].
Pause-Printer-After- Stops the IPP Printer from sending Current-Job new IPP Jobs to the Output Device(s) after the current jobs finish.
暂停打印机后-停止IPP打印机在当前作业完成后将新IPP作业发送到输出设备。
Resume-Printer Starts the IPP Printer sending IPP Jobs to the Output Device again.
Resume Printer启动IPP打印机，将IPP作业再次发送到输出设备。
This OPTIONAL operation allows a client to stop the Printer object from sending IPP jobs to any of its Output Devices or Subordinate Printers. If the IPP Printer is in the middle of sending an IPP job to an Output Device or Subordinate Printer, the IPP Printer MUST complete sending that Job. However, after receiving this operation, the IPP Printer MUST NOT send any additional IPP jobs to any of its Output Devices or Subordinate Printers. In addition, after having received this operation, the IPP Printer MUST NOT start processing any more jobs, so additional jobs MUST NOT enter the 'processing' state.
此可选操作允许客户端停止打印机对象向其任何输出设备或从属打印机发送IPP作业。如果IPP打印机正处于将IPP作业发送到输出设备或下属打印机的中间，则IPP打印机必须完成发送该作业。但是，收到此操作后，IPP打印机不得向其任何输出设备或从属打印机发送任何附加IPP作业。此外，收到此操作后，IPP打印机不得开始处理任何其他作业，因此其他作业不得进入“处理”状态。
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 Printer is busy processing any jobs), the IPP Printer object transitions immediately to the 'stopped' state by setting its "printer-state" attribute to 'stopped', removing the 'moving-to-paused' value, if present, from its "printer-state-reasons" attribute, and adding the 'paused' value to its "printer-state-reasons" attribute.
如果IPP打印机未向输出设备或从属打印机发送IPP作业（无论输出设备或从属打印机是否正在忙于处理任何作业），IPP打印机对象将其“打印机状态”属性设置为“停止”，删除“移动到暂停”值，立即转换为“停止”状态，如果存在，从其“打印机状态原因”属性，并将“暂停”值添加到其“打印机状态原因”属性。
If the implementation will take appreciable time to complete sending an IPP job that it has started sending to an Output Device or Subordinate Printer, the IPP Printer adds the 'moving-to-paused'
如果实现需要相当长的时间才能完成向输出设备或从属打印机发送已开始发送的IPP作业，则IPP打印机会添加“移动到暂停”
value to the Printer object's "printer-state-reasons" attribute (see section [RFC2911], 4.4.12). When the IPP Printer has completed sending IPP jobs that it was in the process of sending, the Printer object transitions to the 'stopped' state by setting its "printer-state" attribute to 'stopped', removing the 'moving-to-paused' value, if present, from its "printer-state-reasons" attribute, and adding the 'paused' value to its "printer-state-reasons" attribute.
打印机对象的“打印机状态原因”属性的值（请参阅[RFC2911]，4.4.12节）。当IPP打印机完成发送其正在发送的IPP作业时，打印机对象将通过将其“打印机状态”属性设置为“已停止”，从其“打印机状态原因”属性中删除“移动到暂停”值（如果存在），并将“暂停”值添加到“已停止”状态“打印机状态原因”属性。
This operation MUST NOT affect the acceptance of Job Creation requests (see Disable-Printer Operation, section 3.1.1).
此操作不得影响作业创建请求的接受（请参阅“禁用打印机操作”，第3.1.1节）。
For any jobs that are 'pending' or 'pending-held', the 'printer-stopped' values of the jobs' "job-state-reasons" attribute also apply. However, the IPP Printer NEED NOT update those jobs' "job-state-reasons" attributes and only have to return the 'printer-stopped' value when those jobs are queried by using the Get-Job-Attributes or Get-Jobs operations (so-called "lazy evaluation").
对于任何“挂起”或“挂起”的作业，作业的“作业状态原因”属性的“打印机已停止”值也适用。但是，IPP打印机不需要更新这些作业的“作业状态原因”属性，只需在使用“获取作业属性”或“获取作业”操作查询这些作业时返回“打印机停止”值（所谓的“延迟评估”）。
The IPP Printer MUST accept the request in any state and transition the Printer to the indicated new "printer-state", and it MUST add the indicated value to "printer-state-reasons" attribute before returning as follows:
IPP打印机必须在任何状态下接受请求，并将打印机转换到指定的新“打印机状态”，并且必须在返回前将指定值添加到“打印机状态原因”属性中，如下所示：
Table 3. State Transition Table for Pause-Printer-After-Current-Job Operation
表3。当前作业操作后暂停打印机的状态转换表
Current New "printer IPP Printer's response status
"printer- "printer- -state- code and action (REQUIRED/
state" state" reasons" OPTIONAL state transition for
a Printer to support):
--------------------------------------------------------------------
'idle' 'stopped' 'paused' REQUIRED: 'successful-ok'
Current New "printer IPP Printer's response status
"printer- "printer- -state- code and action (REQUIRED/
state" state" reasons" OPTIONAL state transition for
a Printer to support):
--------------------------------------------------------------------
'idle' 'stopped' 'paused' REQUIRED: 'successful-ok'
'processing' 'processing' 'moving- OPTIONAL: 'successful-ok'; to- Later, when the IPP Printer paused' has finished sending IPP jobs to an Output Device, the "printer-state" becomes 'stopped', and the 'paused' value replaces the 'moving-to-paused' value in the "printer-state-reasons" attribute
“正在处理”“正在处理”“正在移动-可选：“成功确定”；到-稍后，当IPP打印机暂停”完成向输出设备发送IPP作业时，“打印机状态”变为“停止”，并且“暂停”值替换“打印机状态原因”属性中的“移动到暂停”值
'processing' 'stopped' 'paused' REQUIRED: 'successful-ok'; the IPP Printer wasn't in the middle of sending an IPP job to an Output Device
'处理''已停止''暂停''必需：'成功确定'；IPP打印机并没有将IPP作业发送到输出设备。
'stopped' 'stopped' 'paused' REQUIRED: 'successful-ok'
“已停止”“已停止”“已暂停”必需：“成功确定”
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Pause-Printer-After-Current-Job Request and Pause-Printer-After-Current-Job Response have the same attribute groups and attributes as does the Pause-Printer 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).
当前作业请求后暂停打印机和当前作业响应后暂停打印机具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This section defines operations to condition the Printer to hold any new jobs and to release them.
本节定义了调整打印机以保留任何新作业并释放这些作业的操作。
This OPTIONAL operation allows a client to condition the Printer to complete the current 'pending' and 'processing' IPP Jobs but not to start processing any subsequently created IPP Jobs. If the IPP Printer is in the middle of sending an IPP job to an Output Device or Subordinate Printer, the IPP Printer MUST complete sending that Job. Furthermore, the IPP Printer MUST send all of the current 'pending' IPP Jobs to the Output Device(s) or Subordinate IPP Printer object(s). Any subsequently received Job Creation operations will cause the IPP Printer to put the Job into the 'pending-held' state, with the 'job-held-on-create' value being added to the job's "job-state-reasons" attribute. Thus all newly accepted jobs will be automatically held by the Printer.
此可选操作允许客户端调节打印机以完成当前“挂起”和“处理”IPP作业，但不开始处理任何随后创建的IPP作业。如果IPP打印机正处于将IPP作业发送到输出设备或下属打印机的中间，则IPP打印机必须完成发送该作业。此外，IPP打印机必须将所有当前“挂起”IPP作业发送到输出设备或从属IPP打印机对象。随后收到的任何作业创建操作都会导致IPP打印机将作业置于“挂起保留”状态，并将“创建时保留作业”值添加到作业的“作业状态原因”属性中。因此，打印机将自动保留所有新接受的作业。
When the Printer completes all the 'pending' and 'processing' jobs, it enters the 'idle' state as usual. An operator monitoring Printer state changes will know when the Printer has completed all current jobs because the Printer enters the 'idle' state.
当打印机完成所有“挂起”和“处理”作业时，它会像往常一样进入“空闲”状态。监控打印机状态更改的操作员将知道打印机何时已完成所有当前作业，因为打印机进入“空闲”状态。
This operation MUST NOT affect the acceptance of Job Creation requests (see Disable-Printer Operation, section 3.1.1), except to put the Jobs into the 'pending-held' state, instead of the 'pending' or 'processing' state.
此操作不得影响作业创建请求的接受（请参阅禁用打印机操作，第3.1.1节），除非将作业置于“挂起-保留”状态，而不是“挂起”或“处理”状态。
The IPP Printer MUST accept the request in any state, MUST NOT transition the Printer to any other "printer-state", and MUST add the 'hold-new-jobs' value to the Printer's "printer-state-reasons" attribute (whether the value was present or not).
IPP打印机必须在任何状态下接受请求，不得将打印机转换为任何其他“打印机状态”，并且必须将“保留新作业”值添加到打印机的“打印机状态原因”属性中（无论该值是否存在）。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Hold-New-Jobs Request and Hold-New-Jobs Response have the same attribute groups and attributes as does the Pause-Printer 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).
保持新作业请求和保持新作业响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This OPTIONAL operation allows a client to undo the effect of a previous Hold-New-Jobs operation. In particular, the Printer releases all the jobs that it held as a consequence of a Hold-New-Jobs operations; i.e., while the 'hold-new-jobs' value was present in the Printer's "printer-state-reasons" attribute. In addition, the Printer MUST accept this request in any state, MUST NOT transition the Printer to any other "printer-state", and MUST remove the 'hold-new-jobs' value from its "printer-state-reasons" attribute (whether the value was present or not) so that the Printer no longer holds newly created jobs.
此可选操作允许客户端撤消以前的保留新作业操作的效果。特别是，打印机释放由于保持新作业操作而保持的所有作业；i、 例如，“保留新作业”值出现在打印机的“打印机状态原因”属性中。此外，打印机必须在任何状态下接受此请求，不得将打印机转换为任何其他“打印机状态”，并且必须从其“打印机状态原因”属性中删除“保留新作业”值（无论该值是否存在），以便打印机不再保留新创建的作业。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Release-Held-New-Jobs Request and Release-Held-New-Jobs Response have the same attribute groups and attributes as the Pause-Printer 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).
释放保留的新作业请求和释放保留的新作业响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This section defines the OPTIONAL Deactivate-Printer and Activate-Printer operations that stop and start the IPP Printer object from accepting all requests except queries and performing work. If either of these operations are supported, both MUST be supported.
本节定义了可选的“停用打印机”和“激活打印机”操作，用于停止和启动IPP打印机对象以接受除查询和执行工作之外的所有请求。如果支持这两种操作中的任何一种，则必须同时支持这两种操作。
These operations allow the operator to put the Printer into a dormant read-only condition and to take it out of this condition.
这些操作允许操作员将打印机置于休眠只读状态，并使其脱离此状态。
This OPTIONAL operation allows a client to stop the Printer object from sending IPP jobs to any of its Output Devices or Subordinate Printers (Pause-Printer-After-Current-Job) and to stop the Printer object from accepting any requests but query requests. The Printer performs a Disable-Printer and a Pause-Printer-After-Current-Job operation immediately. If these two operations cannot be completed immediately, it includes use of all of the "printer-state-reasons". In addition, the Printer MUST immediately reject all requests, except for Activate-Printer, queries (Get-Printer-Attributes, Get-Job-Attributes, Get-Jobs, etc.), Send-Document, and Send-URI (so that partial job submission can be completed, see section 3.1.1). The Printer MUST then return the 'server-error-service-unavailable' status code.
此可选操作允许客户端停止打印机对象向其任何输出设备或从属打印机发送IPP作业（在当前作业后暂停打印机），并停止打印机对象接受除查询请求以外的任何请求。打印机在当前作业操作后立即执行禁用打印机和暂停打印机。如果无法立即完成这两个操作，则包括使用所有“打印机状态原因”。此外，打印机必须立即拒绝所有请求，除了激活打印机、查询（获取打印机属性、获取作业属性、获取作业等）、发送文档和发送URI（以便完成部分作业提交，请参见第3.1.1节）。然后打印机必须返回“服务器错误服务不可用”状态代码。
The IPP Printer MUST accept the request in any state. Immediately, the Printer MUST set the 'deactivated' value in its "printer-state-reasons" attribute. Note: neither the Disable-Printer nor the Pause-Printer-After-Current-Job set the 'deactivated' value.
IPP打印机必须在任何状态下接受请求。打印机必须立即在其“打印机状态原因”属性中设置“停用”值。注意：当前作业后禁用打印机和暂停打印机均未设置“停用”值。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Deactivate-Printer Request and Deactivate-Printer Response have the same attribute groups and attributes as does the Pause-Printer 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).
停用打印机请求和停用打印机响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This OPTIONAL operation allows a client to undo the effects of the Deactivate-Printer; i.e., it allows the Printer object to start sending IPP jobs to any of its Output Devices or Subordinate Printers (Pause-Printer-After-Current-Job) and starts the Printer object from accepting any requests. The Printer performs an Enable-Printer and a Resume-Printer operation immediately. In addition, the Printer MUST immediately start accepting all requests.
此可选操作允许客户端撤消停用打印机的效果；i、 例如，它允许打印机对象开始向其任何输出设备或从属打印机发送IPP作业（在当前作业后暂停打印机），并启动打印机对象接受任何请求。打印机会立即执行启用打印机和恢复打印机操作。此外，必须立即启动打印机接受所有请求。
The IPP Printer MUST accept the request in any state. The Printer MUST immediately remove the 'deactivated' value from its "printer-state-reasons" attribute (whether it is present or not).
IPP打印机必须在任何状态下接受请求。打印机必须立即从其“打印机状态原因”属性（无论是否存在）中删除“已停用”值。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Activate-Printer Request and Activate-Printer Response have the same attribute groups and attributes as the Pause-Printer 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).
激活打印机请求和激活打印机响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This section defines the OPTIONAL Restart-Printer, Shutdown-Printer, and Startup-Printer operations that initialize, shutdown, and start up the Printer object, respectively. Each of these operations is OPTIONAL, and any combination MAY be supported.
本节定义了分别初始化、关闭和启动打印机对象的可选重新启动打印机、关闭打印机和启动打印机操作。每个操作都是可选的，可以支持任何组合。
This OPTIONAL operation allows a client to restart a Printer object whose operation is in need of initialization because of incorrect or erratic behavior; i.e., perform the effect of a software re-boot. The implementation MUST attempt to save any information about Jobs and the Printer object before re-initializing. However, this operation MAY have drastic consequences on the running system, so the client SHOULD first try the Deactivate-Printer operation to minimize the effect on the current state of the system. The effects of previous Disable-Printer, Pause Printer, and Deactivate-Printer operations are lost.
此可选操作允许客户端重新启动打印机对象，该打印机对象的操作因行为不正确或不稳定而需要初始化；i、 例如，执行软件重新引导的效果。在重新初始化之前，实现必须尝试保存有关作业和打印机对象的任何信息。但是，此操作可能会对正在运行的系统产生严重影响，因此客户端应首先尝试停用打印机操作，以将对系统当前状态的影响降至最低。以前的禁用打印机、暂停打印机和停用打印机操作的效果将丢失。
The IPP Printer MUST accept the request in any state. The Printer object MUST initialize its Printer's "printer-state" to 'idle', remove the state reasons from its "printer-state-reasons" attribute, and change its "printer-is-accepting-jobs" attribute to 'true'.
IPP打印机必须在任何状态下接受请求。打印机对象必须将其打印机的“打印机状态”初始化为“空闲”，从其“打印机状态原因”属性中删除状态原因，并将其“打印机正在接受作业”属性更改为“true”。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Restart-Printer Request and Restart-Printer Response have the same attribute groups and attributes as does 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).
重启打印机请求和重启打印机响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.8.1和3.2.8.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This OPTIONAL operation allows a client to shutdown a Printer; i.e., to stop processing jobs without losing any jobs and to make the Printer object unavailable for any operations using the IPP protocol. There is no way to bring the instance of the Printer object back to being used, except for the Startup-Printer (see section 3.5.3), which starts up a new instance of the Printer object for hosted
此可选操作允许客户端关闭打印机；i、 例如，停止处理作业而不丢失任何作业，并使打印机对象不可用于使用IPP协议的任何操作。除了启动打印机（请参阅第3.5.3节）之外，无法使打印机对象的实例恢复使用，该启动打印机对象的新实例用于托管
implementations. The purpose of Shutdown-Printer is to shutdown the Printer for an extended period, not to reset the device(s) or modify a Printer attribute. See Restart-Printer (section 3.5.1) and Startup-Printer (section 3.5.3) for the way to initialize the software. See the Disable-Printer operation (section 3.1) for a way for the client to stop the Printer from accepting Job Creation requests without stopping processing or shutting down.
实现。关闭打印机的目的是长时间关闭打印机，而不是重置设备或修改打印机属性。有关初始化软件的方法，请参阅重新启动打印机（第3.5.1节）和启动打印机（第3.5.3节）。有关客户端在不停止处理或关闭的情况下停止打印机接受作业创建请求的方法，请参阅“禁用打印机操作”（第3.1节）。
The Printer MUST add the 'shutdown' value (see [RFC2911], section 4.4.11) immediately to its "printer-state-reasons" Printer Description attribute. It then performs a Deactivate-Printer operation (see section 3.4.1), which in turn performs Disable-Printer and Pause-Printer-After-Current-Job operations).
打印机必须立即将“关机”值（参见[RFC2911]，第4.4.11节）添加到其“打印机状态原因”打印机描述属性中。然后执行停用打印机操作（参见第3.4.1节），该操作依次执行禁用打印机和在当前作业操作后暂停打印机）。
Note: To shutdown the Printer after all the currently submitted jobs have completed, the operator issues a Disable-Printer operation (see section 3.1.1) and then waits until all the jobs have completed. The Printer goes into the 'idle' state before issuing the Shutdown-Printer operation.
注意：要在当前提交的所有作业完成后关闭打印机，操作员会发出“禁用打印机”操作（参见第3.1.1节），然后等待所有作业完成。在发出关闭打印机操作之前，打印机将进入“空闲”状态。
The Printer object MUST accept this operation in any state and transition the Printer object through the "printer-states" and "printer-state-reasons" defined for the Pause-Printer-After-Current-Job operation until the activity is completed and the Printer object disappears.
打印机对象必须在任何状态下接受此操作，并在当前作业操作后通过为暂停打印机定义的“打印机状态”和“打印机状态原因”转换打印机对象，直到活动完成且打印机对象消失。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Shutdown-Printer Request and Shutdown-Printer Response have the same attribute groups and attributes as does the Pause-Printer 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).
关机打印机请求和关机打印机响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
This OPTIONAL operation allows a client to start up an instance of a Printer object, provided that there isn't one already initiated. The purpose of Startup-Printer is to allow a hosted implementation of the IPP Printer object (i.e., a Server that implements an IPP Printer on behalf of a networked or local Output Device) to be started after the host is available (by means outside this document). See section 3.5.1 for the way to initialize the software or reset the Output Device(s) when the IPP Printer object has already been initiated.
此可选操作允许客户端启动打印机对象的实例，前提是尚未启动打印机对象。启动打印机的目的是允许在主机可用后（通过本文档之外的方式）启动IPP打印机对象的托管实现（即，代表网络或本地输出设备实现IPP打印机的服务器）。有关在IPP打印机对象已启动时初始化软件或重置输出设备的方法，请参见第3.5.1节。
The host MUST accept this operation only when the Printer object has not been initiated. If the Printer object already exists, the host must return the 'client-error-not-possible' status code.
只有在打印机对象尚未启动时，主机才能接受此操作。如果打印机对象已存在，主机必须返回“客户端错误不可能”状态代码。
The result of this operation MUST be with the Printer object's "printer-state" set to 'idle', the state reasons removed from its "printer-state-reasons" attribute, and its "printer-is-accepting-jobs" attribute set to 'false'. Then the operator can reconfigure the Printer before performing an Enable-Printer operation. However, when a Printer is first powered up, it is RECOMMENDED that its "printer-is-accepting-jobs" attribute be set to 'true' in order to achieve easy "out of the box" operation.
此操作的结果必须是打印机对象的“打印机状态”设置为“空闲”，状态原因从其“打印机状态原因”属性中删除，并且其“打印机正在接受作业”属性设置为“false”。然后，操作员可以在执行启用打印机操作之前重新配置打印机。但是，当打印机首次通电时，建议将其“打印机正在接受作业”属性设置为“true”，以实现简单的“开箱即用”操作。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Shutdown-Printer Request and Shutdown-Printer Response have the same attribute groups and attributes as does the Pause-Printer 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).
关机打印机请求和关机打印机响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]第3.2.7.1和3.2.7.2节），包括新的“来自操作员的打印机消息”操作属性（参见第6节）。
All Job operations are directed at Job objects. A client MUST always supply some means to identify the Job object in order to select the correct target of the operation. That job identification MAY either be a single Job URI or a combination of a Printer URI and a Job ID. The IPP object implementation MUST support both forms of identification for every job.
所有作业操作都指向作业对象。客户机必须始终提供一些方法来标识作业对象，以便选择正确的操作目标。该作业标识可以是单个作业URI，也可以是打印机URI和作业ID的组合。IPP对象实现必须支持每个作业的两种标识形式。
The Job Operations defined in this document are summarized in Table 4.
表4总结了本文件中定义的作业操作。
Table 4. Job Operation Operation-Id Assignments
表4。作业操作Id分配
Operation Name Operation-Id Brief description
--------------------------------------------------------------------
Reprocess-Job 0x2C Creates a copy of a completed target
job with a new Job ID and processes it.
Operation Name Operation-Id Brief description
--------------------------------------------------------------------
Reprocess-Job 0x2C Creates a copy of a completed target
job with a new Job ID and processes it.
Cancel-Current- 0x2D Cancels the current job on the target Job Printer or the specified job if it is the current job.
取消当前作业-0x2D取消目标作业打印机上的当前作业或指定作业（如果是当前作业）。
Suspend- 0x2E Suspends the current processing job on Current-Job the target Printer or the specified job if it is the current job, allowing other jobs to be processed instead.
挂起-0x2E挂起目标打印机当前作业上的当前处理作业或指定作业（如果是当前作业），允许处理其他作业。
Resume-Job 0x2F Resumes the suspended target job.
恢复作业0x2F恢复挂起的目标作业。
Promote-Job 0x30 Promotes the pending target job to be next after the current job(s) complete.
升级作业0x30将挂起的目标作业升级为当前作业完成后的下一个作业。
Schedule-Job- 0x31 Schedules the target job immediately After after the specified job, all other scheduling factors being equal.
计划作业-0x31在指定作业之后立即计划目标作业，所有其他计划因子相等。
This OPTIONAL operation is a create job operation that allows a client to re-process a copy of a job that had been retained in the queue after processing was completed, canceled, or aborted (see [RFC2911], section 4.3.7.2). This operation is the same as the Restart-Job operation (see [RFC2911], section 3.3.7), except that the Printer creates a new job that is a copy of the target job and the target job is unchanged. New values are assigned to the "job-uri" and "job-id" attributes. The new job's Job Description attributes that track job progress, such as "job-impressions-completed", "job-media-sheets-completed", and "job-k-octets-processed", are initialized to 0, as with any create job operation. The target job moves to the Job History after a suitable period, independent of whether one or more Reprocess-Job operations have been performed upon it.
此可选操作是一种创建作业操作，允许客户端重新处理在处理完成、取消或中止后保留在队列中的作业副本（请参阅[RFC2911]，第4.3.7.2节）。此操作与重新启动作业操作相同（请参阅[RFC2911]，第3.3.7节），只是打印机创建了一个新作业，该作业是目标作业的副本，并且目标作业没有更改。将新值分配给“作业uri”和“作业id”属性。与任何创建作业操作一样，跟踪作业进度的新作业的作业描述属性（如“已完成作业印象”、“已完成作业媒体表”和“已处理作业k-octets”）初始化为0。目标作业在适当的时间段后移动到作业历史记录，与是否对其执行了一个或多个重新处理作业操作无关。
If the Set-Job-Attributes operation is supported, then the "job-hold-until" operation attribute MUST be supported with at least the 'indefinite' value, so that a client can modify the new job before it is scheduled for processing by using the Set-Job-Attributes operation. After modifying the job, the client can release the job for processing by using the Release-Job operation specifying the newly assigned "job-uri" or "job-id" for the new job.
如果支持设置作业属性操作，则“作业保留到”操作属性必须至少支持“不确定”值，以便客户端可以在计划使用设置作业属性操作进行处理之前修改新作业。修改作业后，客户端可以通过使用release job操作来释放作业以进行处理，该操作为新作业指定新分配的“作业uri”或“作业id”。
This OPTIONAL operation allows a client to cancel the current job on the target Printer or the specified job if it is the current job on the Printer. See [RFC2911], section 3.3.3, for the semantics of canceling a job. Since a Job might already be marking by the time a Cancel-Current-Job is received, some media sheet pages might print before the job is actually terminated.
此可选操作允许客户端取消目标打印机上的当前作业，或者取消指定的作业（如果该作业是打印机上的当前作业）。有关取消作业的语义，请参见[RFC2911]，第3.3.3节。由于在收到“取消当前作业”时，作业可能已经在标记，因此某些介质页可能会在作业实际终止之前打印。
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 current job in the 'processing' or 'processing-stopped' state; otherwise, it MUST reject the request and return the 'client-error-not-possible' status code. If more than one job is in the 'processing' or 'processing-stopped' state, the one that is marking is canceled, and the others are unaffected.
如果客户端未提供“作业id”操作属性，则如果当前作业处于“正在处理”或“正在停止处理”状态，打印机必须接受请求并取消当前作业；否则，它必须拒绝请求并返回“客户端错误不可能”状态代码。如果多个作业处于“正在处理”或“正在处理已停止”状态，则正在标记的作业将被取消，其他作业不受影响。
Warning: On a shared printer, there is a race condition. Between the time when a user issues this operation and the time of 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' state), the Printer MUST reject this operation and return the 'client-error-not-possible' status code. Otherwise, the Printer cancels the specified job.
警告：在共享打印机上，存在争用条件。在用户发出此操作和接受此操作之间，当前作业可能会更改为其他作业。如果用户或操作员已通过取消新作业的身份验证，则会取消错误的作业。为了防止此竞争取消错误的作业，客户端可能会提供“作业id”操作属性，该属性将根据当前作业的作业id进行检查。如果“作业id”属性标识的作业不是打印机上的当前作业（即，未处于“处理”或“处理已停止”状态），打印机必须拒绝此操作并返回“客户端错误不可能”状态代码。否则，打印机将取消指定的作业。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must either be the job owner (as determined in the Job Creation operation) or an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参见[RFC2911]，第8.3节）必须是作业所有者（在作业创建操作中确定）或打印机对象的操作员或管理员（请参见[RFC2911]，第1节和第8.5节）。
The Cancel-Current-Job Request and Cancel-Current-Job Response have the same attribute groups and attributes as does the Resume-Printer operation (see [RFC2911], section 3.2.8), including the new "job-message-from-operator" operation attribute (see section 6), with the addition of the following Group 1 Operation attribute in the request:
取消当前作业请求和取消当前作业响应具有与恢复打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.8节），包括新的“来自操作员的作业消息”操作属性（参见第6节），并在请求中添加了以下第1组操作属性：
"job-id" (integer(1:MAX)): The client OPTIONALLY supplies this Operation attribute to verify that the identified job is still the current job on the target Printer object. The IPP object MUST support this operation attribute if it supports this operation.
“作业id”（整数（1:MAX））：客户端可选地提供此操作属性，以验证标识的作业仍然是目标打印机对象上的当前作业。如果IPP对象支持此操作，则它必须支持此操作属性。
This section defines the Suspend-Current-Job and Resume-Job operations. These operations allow an operator or user to suspend a job while it is processing, allowing other jobs to be processed, and to resume the suspended job at a later point without losing any of the output.
本节定义暂停当前作业和恢复作业操作。这些操作允许操作员或用户在处理作业时挂起作业，允许处理其他作业，并在稍后恢复挂起的作业，而不会丢失任何输出。
If either of these operations is supported, both MUST be supported.
如果支持这两种操作中的任何一种，则必须同时支持这两种操作。
The Hold-Job and Release-Job operations ([RFC2911], section 3.3.5) are for holding and releasing held jobs, not suspending and resuming suspended jobs.
保留作业和释放作业操作（[RFC2911]，第3.3.5节）用于保留和释放保留作业，而不是暂停和恢复暂停作业。
This OPTIONAL operation allows a client to stop the current job on the target Printer or the specified job if it is the current job on the Printer, to allow other jobs to be processed instead. The Printer moves the current job or the target job to the 'processing-stopped' state and sets the 'job-suspended' value (see section 9.1) in the job's "job-state-reasons" attribute and processes other jobs.
此可选操作允许客户端停止目标打印机上的当前作业或指定作业（如果该作业是打印机上的当前作业），以允许处理其他作业。打印机将当前作业或目标作业移动到“处理停止”状态，并在作业的“作业状态原因”属性中设置“作业暂停”值（见第9.1节），并处理其他作业。
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 a current job in the 'processing' or 'processing-stopped' state. Otherwise, it MUST reject the request and return the 'client-error-not-possible' status code. If more than one job is in the 'processing' or 'processing-stopped' state, all of them are suspended.
如果客户端未提供“作业id”操作属性，则如果当前作业处于“正在处理”或“正在停止处理”状态，打印机必须接受请求并挂起当前作业。否则，它必须拒绝请求并返回“客户端错误不可能”状态代码。如果多个作业处于“正在处理”或“已停止处理”状态，则所有作业都将挂起。
Warning: On a shared printer, there is a race condition. Between the time when a user issues this operation and the time of its acceptance, the current job might change to a different job. If the user or operator is authenticated to suspend the new job, the wrong job is suspended. To prevent this race from pausing 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' state), 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.
警告：在共享打印机上，存在争用条件。在用户发出此操作和接受此操作之间，当前作业可能会更改为其他作业。如果用户或操作员通过了暂停新作业的身份验证，则会暂停错误的作业。为了防止此竞争暂停错误的作业，客户端可能会提供“作业id”操作属性，该属性会根据当前作业的作业id进行检查。如果“作业id”属性标识的作业不是打印机上的当前作业（即，未处于“处理”或“处理已停止”状态），打印机必须拒绝此操作并返回“客户端错误不可能”状态代码。否则，打印机将挂起指定的作业并处理其他作业。
The Printer MUST reject a Suspend-Current-Job request (and return the 'client-error-not-possible') for a job that has been suspended, i.e., for a job in the 'processing-stopped' state, with the 'job-suspended' value in its "job-state-reasons" attribute.
对于已挂起的作业，打印机必须拒绝挂起当前作业请求（并返回“客户端错误不可能”），即对于处于“处理已停止”状态的作业，其“作业状态原因”属性中的“作业挂起”值。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be either the job owner (as determined in the Job Creation operation) or an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参见[RFC2911]，第8.3节）必须是作业所有者（在作业创建操作中确定）或打印机对象的操作员或管理员（请参见[RFC2911]，第1节和第8.5节）。
The Suspend-Current-Job Request and Suspend-Current-Job Response have the same attribute groups and attributes as does the Pause-Printer operation (see [RFC2911], section 3.2.8 ), including the new "job-message-from-operator" operation attribute (see section 6), with the addition of the following Group 1 Operation attribute in the request:
暂停当前作业请求和暂停当前作业响应具有与暂停打印机操作相同的属性组和属性（参见[RFC2911]，第3.2.8节），包括新的“来自操作员的作业消息”操作属性（参见第6节），并在请求中添加了以下第1组操作属性：
"job-id" (integer(1:MAX)): The client OPTIONALLY supplies this Operation attribute to verify that the identified job is still the current job on the target Printer object. The IPP object MUST support this operation attribute if it supports this operation.
“作业id”（整数（1:MAX））：客户端可选地提供此操作属性，以验证标识的作业仍然是目标打印机对象上的当前作业。如果IPP对象支持此操作，则它必须支持此操作属性。
This OPTIONAL operation allows a client to resume the target job at the point where it was suspended. The Printer moves the target job to the 'pending' state and removes the 'job-suspended' value from the job's "job-state-reasons" attribute.
此可选操作允许客户端在目标作业挂起的位置恢复该作业。打印机将目标作业移动到“挂起”状态，并从作业的“作业状态原因”属性中删除“作业挂起”值。
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 Printer MUST reject the request and return the 'client-error-not-possible' status code, since the job was not suspended.
如果目标作业未处于“处理已停止”状态，且作业的“作业状态原因”属性中有“作业已暂停”值，则打印机必须拒绝请求并返回“客户端错误不可能”状态代码，因为作业未暂停。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be either the job owner (as determined in the Job Creation operation) or an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参见[RFC2911]，第8.3节）必须是作业所有者（在作业创建操作中确定）或打印机对象的操作员或管理员（请参见[RFC2911]，第1节和第8.5节）。
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).
恢复作业请求和恢复作业响应具有与发布作业操作相同的属性组和属性（参见[RFC2911]，第3.3.6节），包括新的“来自操作员的作业消息”操作属性（参见第6节）。
This section defines jobs that allow an operator to control the scheduling of jobs.
本节定义允许操作员控制作业调度的作业。
This OPTIONAL operation allows a client to make the pending target job be processed next after the current job completes. This operation is especially useful in a production printing environment where the operator is involved in job scheduling.
此可选操作允许客户端在当前作业完成后下一步处理挂起的目标作业。在操作员参与作业调度的生产打印环境中，此操作特别有用。
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 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-not-possible' status code.
如果目标作业处于“挂起”状态，此操作不会更改作业的状态，但会导致在当前作业完成后处理作业。如果目标作业未处于“挂起”状态，打印机必须拒绝请求并返回“客户端错误不可能”状态代码。
If the Printer implements the "job-priority" Job Template attribute (see [RFC2911], section 4.2.1), the Printer sets the job's "job-priority" to the highest value supported (so that the job will print before any of the other pending jobs). The Printer returns the target job immediately after the current job(s) in a Get-Jobs response (see [RFC2911], section 3.2.6) for the 'not-completed' jobs.
如果打印机实现“作业优先级”作业模板属性（请参阅[RFC2911]，第4.2.1节），则打印机会将作业的“作业优先级”设置为支持的最高值（以便作业将在任何其他挂起作业之前打印）。对于“未完成”作业，打印机会在“获取作业”响应（请参见[RFC2911]，第3.2.6节）中的当前作业之后立即返回目标作业。
When the current job is completed, canceled, suspended (see section 4.3.1), or aborted, the target of this operation is processed next.
当当前作业完成、取消、暂停（见第4.3.1节）或中止时，下一步处理此操作的目标。
If a client issues this request (again) before the target of the operation of the original request started processing, the target of this new request is processed first.
如果客户机在原始请求的操作目标开始处理之前发出此请求（再次），则首先处理此新请求的目标。
IPP is specified not to require queues for job scheduling, as there are other implementation techniques for scheduling multiple jobs, such as re-evaluating a criteria function for each job on a scheduling cycle. However, if an implementation does implement queues for jobs, then the Promote-Job operation puts the specified job at the front of the queue. A subsequent Promote-Job operation prior to the processing of the first job puts that specified job at the front of the queue, so that it is "in front" of the previously promoted job.
IPP被指定为不需要队列来进行作业调度，因为还有其他用于调度多个作业的实现技术，例如重新评估调度周期中每个作业的标准函数。但是，如果实现确实实现了作业队列，则升级作业操作会将指定的作业放在队列的前面。在处理第一个作业之前的后续提升作业操作会将指定作业放在队列的前面，以便它位于先前提升作业的“前面”。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Promote-Job Request and Promote-Job Response have the same attribute groups and attributes as does the Cancel-Job operation (see [RFC2911], section 3.3.3), including the new "job-message-from-operator" operation attribute (see section 6).
提升作业请求和提升作业响应具有与取消作业操作相同的属性组和属性（参见[RFC2911]，第3.3.3节），包括新的“来自操作员的作业消息”操作属性（参见第6节）。
This OPTIONAL operation allows a client to request that the Printer schedule the target job so that it will be processed immediately after the specified predecessor job, all other scheduling factors being equal. This operation is specially useful in a production printing environment where the operator is involved in job scheduling.
此可选操作允许客户端请求打印机计划目标作业，以便在所有其他计划因素相同的情况下，在指定的前置作业之后立即处理目标作业。在操作员参与作业调度的生产打印环境中，此操作特别有用。
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 preceding job completes. The preceding job can be in the target 'pending', 'processing', or 'processing-stopped' state. If the target job is not in the 'pending' state, or if the predecessor job is not in the 'pending', 'processing', or 'processing-stopped' state, the Printer MUST reject the request, and it returns the 'client-error-not-possible' status code, as the job cannot have its position changed.
如果目标作业处于“挂起”状态，此操作不会更改作业的状态，但会导致在前一个作业完成后处理该作业。前面的作业可以处于目标“挂起”、“处理”或“处理已停止”状态。如果目标作业未处于“挂起”状态，或者前置作业未处于“挂起”、“处理”或“处理已停止”状态，则打印机必须拒绝请求，并返回“客户端错误不可能”状态代码，因为作业的位置无法更改。
If the Printer implements the "job-priority" Job Template attribute (see [RFC2911], section 4.2.1), the Printer sets the job's "job-priority" to that of the predecessor job (so that the job will print after the predecessor job). The Printer returns the target job immediately after the predecessor in a Get-Jobs response (see [RFC2911], section 3.2.6) for the 'not-completed' jobs.
如果打印机实现了“作业优先级”作业模板属性（请参见[RFC2911]，第4.2.1节），则打印机将作业的“作业优先级”设置为前置作业的“作业优先级”（以便作业将在前置作业之后打印）。对于“未完成”作业，打印机会在“获取作业”响应（请参见[RFC2911]，第3.2.6节）中，在前一个作业之后立即返回目标作业。
When the predecessor job completes processing or is canceled or aborted while processing, the target of this operation is processed next.
当前置作业完成处理或在处理过程中被取消或中止时，下一步将处理此操作的目标。
If the client does not supply a predecessor job, this operation has the same semantics as Promote-Job (see section 4.4).
如果客户端不提供前置作业，则此操作的语义与升级作业相同（请参阅第4.4节）。
IPP is specified not to require queues for job scheduling, as there are other implementation techniques for scheduling multiple jobs, such as re-evaluating a criteria function for each job on a scheduling cycle. However, if an implementation does implement queues for jobs, then the Schedule-Job-After operation puts the specified job immediately after the specified job in the queue. A subsequent Schedule-Job-After operation specifying the same job will cause its target job to be placed after that job, even though it is between the first target job and the specified job. For example, suppose the job queue consisted of jobs A, B, C, D, and E, in that order. A Schedule-Job-After with job E as the target and B as the specified job would result in the following queue: A, B, E, C, D. A subsequent Schedule-Job-After with Job D as the target and B as the specified job would result in the following queue: A, B, D, E, C.
IPP被指定为不需要队列来进行作业调度，因为还有其他用于调度多个作业的实现技术，例如重新评估调度周期中每个作业的标准函数。但是，如果某个实现确实实现了作业队列，则“调度作业后”操作会将指定作业放在队列中指定作业的后面。指定相同作业的操作后的后续计划作业将导致其目标作业放置在该作业之后，即使该作业位于第一个目标作业和指定作业之间。例如，假设作业队列按顺序由作业A、B、C、D和E组成。以作业E为目标，B为指定作业的调度作业之后将产生以下队列：A、B、E、C、D。以作业D为目标，B为指定作业的后续调度作业之后将产生以下队列：A、B、D、E、C。
In other words, the link between the two jobs in a Schedule-Job-After 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.
换言之，不保留运行后调度作业中两个作业之间的链接；i、 例如，由于此操作，两个作业上都没有指向另一个作业的属性。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).
访问权限：执行此操作的经过身份验证的用户（请参阅[RFC2911]，第8.3节）必须是打印机对象的操作员或管理员（请参阅[RFC2911]，第1节和第8.5节）。
The Schedule-Job-After Request have the same attribute groups and attributes as does the Cancel-Job operation (see [RFC2911], section 3.3.3), plus the new "job-message-from-operator" operation attribute (see section 6). In addition, the following operation attribute is defined:
请求后调度作业具有与取消作业操作相同的属性组和属性（参见[RFC2911]，第3.3.3节），以及新的“来自操作员的作业消息”操作属性（参见第6节）。此外，还定义了以下操作属性：
"predecessor-job-id": The client OPTIONALLY supplies this attribute. The Printer MUST support it, if it supports this operation. This attribute specifies the job after which the target job is to be processed. If the client omits this attribute, the Printer MUST process the target job next, i.e., after the current job, if there is one.
“前置作业id”：客户端可以选择提供此属性。如果打印机支持此操作，则必须支持它。此属性指定处理目标作业之后的作业。如果客户端忽略此属性，打印机必须下一步处理目标作业，即在当前作业（如果有）之后。
The Schedule-Job-After Response has the same attribute groups, attributes, and status codes as does the Cancel-Job operation (see [RFC2911], section 3.3.3). The following status codes have particular meaning for this operation:
响应后的计划作业具有与取消作业操作相同的属性组、属性和状态代码（请参见[RFC2911]，第3.3.3节）。以下状态代码对此操作具有特殊意义：
'client-error-not-possible' - The target job was not in the 'pending' state, or the predecessor job was not in the 'pending', 'processing', or 'processing-stopped' state.
“客户端错误不可能”-目标作业未处于“挂起”状态，或者前置作业未处于“挂起”、“处理”或“处理已停止”状态。
'client-error-not-found' - Either the target job or the predecessor job was not found.
“未找到客户端错误”-未找到目标作业或前置作业。
This section defines new status codes used by the operations defined in this document.
本节定义了本文档中定义的操作所使用的新状态代码。
The Printer has been deactivated by the Deactivate-Printer operation and is only accepting the Activate-Printer (see section 3.5.1), Get-Job-Attributes, Get-Jobs, Get-Printer-Attributes, and any other Get-Xxxx operations. An operator can perform the Activate-Printer operation to allow the Printer to accept other operations.
打印机已被停用打印机操作停用，仅接受激活打印机（见第3.5.1节）、获取作业属性、获取作业、获取打印机属性和任何其他获取Xxxx操作。操作员可以执行“激活打印机”操作，以允许打印机接受其他操作。
This section summarizes the usage of the "printer-message-from-operator" and "job-message-from-operator" operation attributes [RFC3380] that set the corresponding Printer and Job Description attributes (see [RFC2911] for the definition of these). These operation attributes are defined for most of the Printer and Job operations that operators are likely to perform, respectively, so that operators can indicate the reasons for their actions.
本节总结了“来自操作员的打印机消息”和“来自操作员的作业消息”操作属性[RFC3380]的用法，它们设置了相应的打印机和作业描述属性（有关这些属性的定义，请参见[RFC2911]）。这些操作属性分别为操作员可能执行的大多数打印机和作业操作定义，以便操作员可以指出其操作的原因。
Table 5 shows the operation attributes defined for use with the Printer Operations.
表5显示了为与打印机操作一起使用而定义的操作属性。
Table 5. Operation Attribute Support for Printer Operations
表5。打印机操作的操作属性支持
Operation Attribute A B
---------------------------------------------
attributes-charset REQ REQ
attributes-natural-language REQ REQ
printer-uri REQ REQ
requesting-user-name REQ REQ
printer-message-from-operator Note OPT
Operation Attribute A B
---------------------------------------------
attributes-charset REQ REQ
attributes-natural-language REQ REQ
printer-uri REQ REQ
requesting-user-name REQ REQ
printer-message-from-operator Note OPT
Legend: A: Get-Printer-Attributes, Set-Printer-Attributes B: All other Printer administrative operations, including, but not limited to, Pause-Printer, Pause-Printer-After-Current-Job, Resume-Printer, Hold-New-Jobs, Release-Held-New-Jobs, Purge-Jobs, Enable-Print, Disable-Printer, Restart-Printer, Shutdown-Printer, and Startup-Printer. REQ: REQUIRED for a Printer to support. OPT: OPTIONAL for a Printer to support; the Printer ignores the attribute if it is not supported. Note: According to [RFC3380], the Client MUST NOT supply the "printer-message-from-operator" operation attribute in a Get-Printer-Attributes or Set-Printer-Attributes operation; the Printer MUST ignore this operation attribute in these two operations. Instead, when it is used by an operator, the client MUST supply the "printer-message-from-operator" as (one of the) explicit attributes being set on the Printer object with the Set-Printer-Attributes operation.
图例：A：获取打印机属性，设置打印机属性B：所有其他打印机管理操作，包括但不限于暂停打印机、当前作业后暂停打印机、恢复打印机、保留新作业、释放保留的新作业、清除作业、启用打印、禁用打印机、重新启动打印机、关闭打印机和启动打印机。REQ：打印机需要支持。OPT：打印机支持的可选选项；如果不支持该属性，打印机将忽略该属性。注意：根据[RFC3380]，在获取打印机属性或设置打印机属性操作中，客户端不得提供“来自操作员的打印机消息”操作属性；在这两个操作中，打印机必须忽略此操作属性。相反，当操作员使用“打印机消息”时，客户端必须提供“来自操作员的打印机消息”，作为通过“设置打印机属性”操作在打印机对象上设置的（其中一个）显式属性。
Table 6 shows the operation attributes defined for use with the Job operations.
表6显示了定义用于作业操作的操作属性。
Table 6. Operation Attribute Support for Job Operations
表6。作业操作的操作属性支持
Operation Attribute A B C F
---------------------------------------------------------
attributes-charset REQ REQ REQ REQ
attributes-natural-language REQ REQ REQ REQ
printer-uri REQ REQ REQ REQ
job-uri REQ REQ REQ
job-id REQ REQ REQ REQ
requesting-user-name REQ REQ REQ REQ
job-message-from-operator OPT OPT OPT Note
message** OPT OPT OPT n/a
job-hold-until n/a n/a OPT* n/a
Operation Attribute A B C F
---------------------------------------------------------
attributes-charset REQ REQ REQ REQ
attributes-natural-language REQ REQ REQ REQ
printer-uri REQ REQ REQ REQ
job-uri REQ REQ REQ
job-id REQ REQ REQ REQ
requesting-user-name REQ REQ REQ REQ
job-message-from-operator OPT OPT OPT Note
message** OPT OPT OPT n/a
job-hold-until n/a n/a OPT* n/a
Legend: A: Cancel-Job, Resume-Job, Restart-Job, Promote-Job, Schedule-Job-After B: Cancel-Current-Job, Suspend-Current-Job C: Hold-Job, Release-Job, Reprocess-Job F: Get-Job-Attributes, Set-Job-Attributes
图例：A:取消作业、恢复作业、重新启动作业、提升作业、在B:取消当前作业、暂停当前作业C:保留作业、释放作业、重新处理作业F:获取作业属性、设置作业属性
REQ; REQUIRED for a Printer to support. OPT: OPTIONAL for a Printer to support; the Printer ignores the attribute if it is supplied, but not supported. n/a: not applicable for use with the operation; the Printer ignores the attribute. Note: According to [RFC3380], the Client MUST NOT supply the "job-message-from-operator" operation attribute in a Get-Job-Attributes or Set-Job-Attributes operation; the Printer MUST ignore this operation attribute in these two operations. Instead, when used by an operator, the client MUST supply the "job-message-from-operator" as (one of the) explicit attributes being set on the Job object with the Set-Job-Attributes operation. *: The Printer MUST support the "job-hold-until" operation attribute if it supports the "job-hold-until" Job Template attribute. For the Reprocess-Job operation, the client can hold the job and then modify the job before releasing it to be processed. **: In [RFC2911], the "message" operation attribute is defined to contain a message to the operator, but [RFC2911] does not define a Job Description attribute to store the message.
请求；打印机需要支持。OPT：打印机支持的可选选项；如果该属性已提供但不受支持，则打印机将忽略该属性。不适用：不适用于与操作一起使用；打印机将忽略该属性。注意：根据[RFC3380]，在获取作业属性或设置作业属性操作中，客户端不得提供“来自操作员的作业消息”操作属性；在这两个操作中，打印机必须忽略此操作属性。相反，当由操作员使用时，客户机必须提供“来自操作员的作业消息”，作为使用“设置作业属性”操作在作业对象上设置的（其中一个）显式属性。*：如果打印机支持“作业保留到”作业模板属性，则必须支持“作业保留到”操作属性。对于重新处理作业操作，客户端可以保留作业，然后在释放作业以进行处理之前修改作业。**：在[RFC2911]中，“消息”操作属性定义为包含发送给操作员的消息，但[RFC2911]未定义用于存储消息的职务描述属性。
The following new Printer Description attributes are needed to support the new operations defined in this document and the concepts of Printer Fan-Out (see section 10).
需要以下新的打印机描述属性来支持本文档中定义的新操作和打印机扇出的概念（参见第10节）。
This Printer attribute is REQUIRED if an implementation supports Subordinate Printers (see section 10) and contains the URIs of the immediate Subordinate Printer object(s) associated with this Printer object. Each Non-Leaf Printer object MUST support this Printer Description attribute. A Leaf Printer object either does not support the "subordinate-printers-supported" attribute or does so with the 'no-value' out-of-band value (see [RFC2911], section 4.1), depending on the implementation.
如果实现支持从属打印机（请参见第10节），并且包含与此打印机对象关联的直接从属打印机对象的URI，则需要此打印机属性。每个非叶子打印机对象都必须支持此打印机描述属性。叶子打印机对象不支持“支持的从属打印机”属性，或者支持带外值“无值”（参见[RFC2911]，第4.1节），具体取决于实现。
The precise format of the Subordinate Printer URIs is implementation dependent (see section 10.4).
从属打印机URI的精确格式取决于实现（见第10.4节）。
If the Printer object does not have an associated Output Device, the Printer MAY automatically copy the value of the Subordinate Printer object's "printer-name" attribute to the Job object's "output-device-assigned" attribute (see [RFC2911], section 4.3.13). The "output-device-assigned" Job attribute identifies the Output Device to which the Printer object has assigned a job; for example, when a single Printer object is supporting Device Fan-Out or Printer Fan-Out.
如果打印机对象没有关联的输出设备，打印机可以自动将从属打印机对象的“打印机名称”属性的值复制到作业对象的“已分配的输出设备”属性（请参见[RFC2911]，第4.3.13节）。“输出设备分配”作业属性标识打印机对象已分配作业的输出设备；例如，当单个打印机对象支持设备扇出或打印机扇出时。
This Printer attribute is REQUIRED if an implementation supports Subordinate Printers (see section 10) and contains the URI of the Non-Leaf printer object(s) for which this Printer object is the immediate Subordinate; i.e., this Printer's immediate "parent" or "parents". Each Subordinate Printer object MUST support this Printer Description attribute. A Printer that has no parents either does not support the "parent-printers-supported" attribute or does so with the 'no-value' out-of-band value (see [RFC2911], section 4.1), depending on the implementation.
如果实现支持从属打印机（参见第10节），并且包含此打印机对象为直接从属的非叶打印机对象的URI，则需要此打印机属性；i、 例如，此打印机的直接“父级”或“父级”。每个从属打印机对象都必须支持此打印机描述属性。没有父级的打印机不支持“支持的父级打印机”属性，或者使用“无值”带外值（参见[RFC2911]，第4.1节），具体取决于实现。
8. Additional Values for the "printer-state-reasons" Printer Description Attribute
8. “打印机状态原因”打印机描述属性的附加值
This section defines additional values for the "printer-state-reasons" Printer Description attribute.
本节定义“打印机状态原因”打印机描述属性的附加值。
'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 taking an appreciable time to stop. Later, when all output has stopped, the "printer-state" becomes 'stopped', and the 'paused' value replaces the 'moving-to-paused' value in the "printer-state-reasons" attribute. This value MUST be supported if the Hold-New-Jobs operation is supported and the implementation takes significant time to pause a device in certain circumstances.
“保留新作业”：操作员已发出“保留新作业”操作（见第3.3.1节）或其他方式，但输出设备需要相当长的时间才能停止。稍后，当所有输出都停止时，“打印机状态”变为“停止”，并且“暂停”值替换“打印机状态原因”属性中的“移动到暂停”值。如果支持Hold New Jobs（保留新作业）操作，并且在某些情况下实施需要花费大量时间来暂停设备，则必须支持此值。
'deactivated': A client has issued a Deactivate-Printer operation for the Printer object (see section 3.4.1), and the Printer is in the process of becoming deactivated or has become deactivated. The Printer MUST reject all requests except for Activate-Printer, queries (Get-Printer-Attributes, Get-Job-Attributes, Get-Jobs, etc.), Send-Document, and Send-URI (so that partial job submission can be completed; see section 3.1.1), and then return the 'server-error-service-unavailable' status code.
“已停用”：客户端已对打印机对象发出停用打印机操作（请参阅第3.4.1节），打印机正在停用或已停用。打印机必须拒绝除激活打印机、查询（获取打印机属性、获取作业属性、获取作业等）、发送文档和发送URI（以便可以完成部分作业提交；请参阅第3.1.1节）之外的所有请求，然后返回“服务器错误服务不可用”状态代码。
9. Additional Values for the "job-state-reasons" Job Description Attribute
9. “职务状态原因”职务说明属性的其他值
This section defines additional values for the "job-state-reasons" Job Description attribute.
本节定义了“职务状态原因”职务描述属性的附加值。
'job-suspended': While job processing has been suspended by the Suspend-Current-Job operation, other jobs can be processed on the Printer. The Job can be resumed with the Resume-Job operation, which removes this value.
“暂停作业”：暂停当前作业操作暂停作业处理时，可以在打印机上处理其他作业。可以使用“恢复作业”操作恢复作业，该操作会删除此值。
10. Use of the Printer Object to Represent IPP Printer Fan-Out and IPP Printer Fan-In
10. 使用Printer对象表示IPP打印机扇出和IPP打印机扇入
This section defines how the Printer object MAY be used to represent IPP Printer Fan-Out and IPP Printer Fan-In. In Fan-Out, an IPP Printer is used to represent other IPP Printer objects. In Fan-In, several IPP Printer objects are used to represent another IPP Printer object.
本节定义如何使用打印机对象表示IPP打印机扇出和IPP打印机扇入。在扇出模式中，IPP打印机用于表示其他IPP打印机对象。在“扇入”中，几个IPP打印机对象用于表示另一个IPP打印机对象。
The IPP/1.1 Model and Semantics introduces the semantic concept of an IPP Printer object that represents more than one Output Device (see [RFC2911], section 2.1). This concept is called "Output Device Fan-Out". However, with Fan-Out there was no way to represent the individual states of the Output Devices or to perform operations on a specific Output Device. This document generalizes the semantics of the Printer object to represent Subordinate Fan-Out Output Devices such as IPP Printer objects. This concept is called "Printer object Fan-Out". A Printer object that has a Subordinate Printer object is called a Non-Leaf Printer object. Thus, a Non-Leaf Printer object supports one or more Subordinate Printer objects in order to represent Printer object Fan-Out. A Printer object that does not have any Subordinate Printer objects is called a Leaf Printer object.
IPP/1.1模型和语义介绍了表示多个输出设备的IPP打印机对象的语义概念（请参见[RFC2911]，第2.1节）。这个概念被称为“输出设备扇出”。但是，使用扇出，无法表示输出设备的各个状态或在特定输出设备上执行操作。本文档概括了打印机对象的语义，以表示从属扇出输出设备，如IPP打印机对象。此概念称为“打印机对象扇出”。具有从属打印机对象的打印机对象称为非叶打印机对象。因此，非叶子打印机对象支持一个或多个从属打印机对象，以表示打印机对象扇出。没有任何从属打印机对象的打印机对象称为叶打印机对象。
Each Non-Leaf Printer object submits jobs to its immediate Subordinate Printers and otherwise controls the Subordinate Printers by 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.
每个非叶子打印机对象向其直接下属打印机提交作业，并使用IPP或其他协议控制下属打印机。挂起的作业是保留在非活页打印机中，直到从属打印机可以接受它们，还是保留在从属打印机中，取决于实施和/或配置策略。此外，从属打印机对象又可以具有从属打印机对象。因此，打印机对象可以是无叶打印机和从属打印机。
A Subordinate Printer object MUST be a conforming Printer object, so it MUST support all of the REQUIRED [RFC2911] operations and 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.
从属打印机对象必须是一致的打印机对象，因此它必须支持所有必需的[RFC2911]操作和属性。但是，通过访问控制，可以对从属打印机进行配置，以便不允许最终用户客户端执行任何操作（或仅获取打印机属性），同时允许一个或多个非叶子打印机对象执行任何操作。
The IPP/1.1 Model and Semantics did not preclude the semantic concept of multiple IPP Printer objects that represent a single Output Device (see [RFC2911], section 2.1). However, there was no way for the client to determine whether there was a Fan-In configuration; nor was there a way to perform operations on the Subordinate device. This specification generalizes the semantics of the Printer object to allow several Non-Leaf IPP Printer objects to represent a single Subordinate Printer object. Thus a Non-Leaf Printer object MAY share a Subordinate Printer object with one or more other Non-Leaf Printer objects in order to represent IPP Printer Fan-In.
IPP/1.1模型和语义并未排除表示单个输出设备的多个IPP打印机对象的语义概念（参见[RFC2911]，第2.1节）。但是，客户端无法确定是否存在扇入配置；也没有办法在从属设备上执行操作。本规范概括了打印机对象的语义，允许多个非叶子IPP打印机对象表示单个从属打印机对象。因此，非叶式打印机对象可以与一个或多个其他非叶式打印机对象共享从属打印机对象，以表示IPP打印机扇入。
As with Fan-Out (see section 10.1), when a Printer object is a Non-Leaf Printer, it MUST NOT have an associated Output Device. As with
与扇出一样（参见第10.1节），当打印机对象是非叶式打印机时，它不得具有关联的输出设备。如同
Fan-Out, a Leaf Printer object has one or more associated Output Devices. As with Fan-Out, the Non-Leaf Printer objects submit jobs to their Subordinate Printer objects and otherwise control the Subordinate Printer. As with Fan-Out, whether pending jobs are kept in the Non-Leaf Printers until the Subordinate Printer can accept them or are kept in the Subordinate Printer depends on the implementation and/or configuration policy.
扇出，叶打印机对象具有一个或多个关联的输出设备。与扇出一样，非叶打印机对象将作业提交给其从属打印机对象，并以其他方式控制从属打印机。与扇出一样，挂起的作业是保留在非活页打印机中，直到从属打印机可以接受它们，还是保留在从属打印机中，取决于实现和/或配置策略。
10.3. Printer Object Attributes Used to Represent Printer Fan-Out and Printer Fan-In
10.3. 用于表示打印机扇出和打印机扇入的打印机对象属性
The following Printer Description attributes are defined to represent the relationship between Printer object(s) and their Subordinate Printer object(s):
定义以下打印机描述属性以表示打印机对象与其从属打印机对象之间的关系：
1. "subordinate-printers-supported" (1setOf uri) - Contains the URI of the immediate Subordinate Printer object(s).
1. “支持的下级打印机”（1setOf uri）-包含直接下级打印机对象的uri。
2. "parent-printers-supported (1setOf uri) - Contains the URI of the Non-Leaf printer object(s) for which this Printer object is the immediate Subordinate; i.e., this Printer's immediate "parent" or "parents".
2. 支持的父打印机（1setOf uri）-包含此打印机对象是其直接下级的非叶打印机对象的uri；即此打印机的直接“父”或“父”。
Each Subordinate Printer object has a URI used as the target of each operation on the Subordinate Printer. The means to configure URIs for Subordinate Printer objects is implementation-dependent, as are all URIs. However, there are two distinct approaches:
每个从属打印机对象都有一个URI，用作从属打印机上每个操作的目标。为从属打印机对象配置URI的方法与所有URI一样，取决于实现。但是，有两种不同的方法：
a. When the implementation seeks to make sure that no operation on a Subordinate Printer object "sneaks by" the parent Printer object (or that no Subordinate Printer is fronting for a device that is not networked), the host part of the URI specifies the host of the parent Printer. Then the parent Printer object can easily reflect the state of the Subordinate Printer objects in the parent's Printer object state and state reasons as the operation passes "through" the parent Printer object.
a. 当实现试图确保没有对下级打印机对象的操作“偷袭”父打印机对象（或者没有下级打印机针对未联网的设备进行前置）时，URI的主机部分指定父打印机的主机。然后，当操作“通过”父打印机对象时，父打印机对象可以很容易地在父打印机对象状态和状态原因中反映从属打印机对象的状态。
b. When the Subordinate Printer is networked and the implementation allows operations to go directly to the Subordinate Printer (with proper access control) without knowledge of the parent Printer object, the host part of the URI is different from the host part of the parent Printer object. In this a case, the parent Printer object MAY keep its "printer-state" and "printer-state-reasons" up to date, either by polling the Subordinate Printer object or by subscribing to events with the Subordinate Printer object (see [RFC3995] for
b. 当从属打印机联网且实现允许操作直接转到从属打印机（具有适当的访问控制）而不知道父打印机对象时，URI的主机部分与父打印机对象的主机部分不同。在这种情况下，父打印机对象可以通过轮询下级打印机对象或通过订阅下级打印机对象的事件（有关详细信息，请参阅[RFC3995]），使其“打印机状态”和“打印机状态原因”保持最新
means to subscribe to event notification when the Subordinate Printer object supports IPP notification). Alternatively, the parent Printer MAY wait until its "printer-state" and "printer-state-reasons" attributes are queried and then query all its Subordinate Printers in order to return the correct values.
表示在从属打印机对象支持IPP通知时订阅事件通知）。或者，父打印机可以等待其“打印机状态”和“打印机状态原因”属性被查询，然后查询其所有下级打印机，以返回正确的值。
Only Leaf IPP Printer objects are allowed to have one or more associated Output Devices. Each Leaf Printer object MAY support the "output-devices-supported" (1setOf name(127)) to indicate the user-friendly name(s) of the Output Device(s) that the Leaf Printer object represents. It is RECOMMENDED that each Leaf Printer object have only one associated Output Device, so that the individual Output Devices can be represented completely and controlled completely by clients. In other words, the Leaf Printer's "output-devices-supported" attribute SHOULD have only one value.
仅允许叶IPP打印机对象具有一个或多个关联的输出设备。每个叶式打印机对象可支持“支持的输出设备”（1setOf name（127））以指示叶式打印机对象表示的输出设备的用户友好名称。建议每个叶子打印机对象仅具有一个关联的输出设备，以便各个输出设备可以完全由客户端表示和控制。换句话说，叶式打印机的“支持的输出设备”属性应该只有一个值。
Non-Leaf Printer MUST NOT have associated Output Devices. However, a Non-Leaf Printer SHOULD support an "output-devices-supported" (1setOf name(127)) Printer Description attribute that contains all the values of its immediate Subordinate Printers. As these Subordinate Printers MAY be Leaf or Non-Leaf, the same rules apply to them. Thus any Non-Leaf Printer SHOULD have an "output-devices-supported" (1setOf name(127)) attribute that contains all the values of the Output Devices associated with Leaf Printers of its complete sub-tree.
非活页打印机不得具有关联的输出设备。但是，非叶式打印机应支持“支持的输出设备”（1setOf name（127））打印机描述属性，该属性包含其直接下级打印机的所有值。由于这些从属打印机可能是叶式打印机或非叶式打印机，因此相同的规则适用于它们。因此，任何非叶式打印机都应该具有“output devices supported”（1setOf name（127））属性，该属性包含与其完整子树的叶式打印机关联的输出设备的所有值。
When a configuration of Printers and Output Devices is added, moved, or changed, there can be moments when the tree structure is not consistent; i.e., times when a Non-Leaf Printer's "subordinate-printers-supported" does not agree with the Subordinate Printer's "parent-printers-supported". Therefore, the operator SHOULD first Deactivate all Printers being configured in this way, update all pointer attributes, and then reactivate them. A useful client tool would validate a tree structure before Activating the Printers involved.
当添加、移动或更改打印机和输出设备的配置时，可能会出现树结构不一致的情况；i、 例如，非活页打印机的“支持的从属打印机”与从属打印机的“支持的父打印机”不一致的次数。因此，操作员应首先停用以这种方式配置的所有打印机，更新所有指针属性，然后重新激活它们。一个有用的客户端工具将在激活相关打印机之前验证树结构。
Figures 1, 2, and 3 are taken from [RFC2911] to show the configurations possible with IPP/1.0 and IPP/1.1 where all Printer objects are Leaf Printer objects. The remaining figures show additional configurations using Non-Leaf and Leaf Printer objects.
图1、图2和图3取自[RFC2911]，显示了IPP/1.0和IPP/1.1的可能配置，其中所有打印机对象都是叶子打印机对象。其余的图显示了使用非叶子和叶子打印机对象的其他配置。
Legend:
图例：
----> indicates a network protocol with the direction of its requests
----> indicates a network protocol with the direction of its requests
##### indicates a Printer object that is either embedded in an Output Device, or hosted in a server. The Printer object might or might not be capable of queuing/spooling.
#####指示嵌入在输出设备中或托管在服务器中的打印机对象。打印机对象可能无法排队/后台打印。
any indicates any network protocol or direct connect, including IPP.
any表示任何网络协议或直接连接，包括IPP。
Output Device
+---------------+
| ########### |
O +--------+ | # (Leaf) # |
/|\ | client |------------IPP-----------------># Printer # |
/ \ +--------+ | # Object # |
| ########### |
+---------------+
Output Device
+---------------+
| ########### |
O +--------+ | # (Leaf) # |
/|\ | client |------------IPP-----------------># Printer # |
/ \ +--------+ | # Object # |
| ########### |
+---------------+
Figure 1. Embedded Printer Object
图1。嵌入式打印机对象
########### Output Device
O +--------+ # (Leaf) # +---------------+
/|\ | client |---IPP----># Printer #---any->| |
/ \ +--------+ # object # | |
########### +---------------+
########### Output Device
O +--------+ # (Leaf) # +---------------+
/|\ | client |---IPP----># Printer #---any->| |
/ \ +--------+ # object # | |
########### +---------------+
Figure 2. Hosted Printer Object
图2。托管打印机对象
+---------------+
| |
+->| Output Device |
########### any/ | |
O +--------+ # (Leaf) # / +---------------+
/|\ | client |---IPP----># Printer #--*
/ \ +--------+ # Object # \ +---------------+
########### any\ | |
+->| Output Device |
| |
+---------------+
+---------------+
| |
+->| Output Device |
########### any/ | |
O +--------+ # (Leaf) # / +---------------+
/|\ | client |---IPP----># Printer #--*
/ \ +--------+ # Object # \ +---------------+
########### any\ | |
+->| Output Device |
| |
+---------------+
Figure 3. Output Device Fan-Out
图3。输出设备扇出
########### ###########
O +--------+ # Non-Leaf# # subord. #
/|\ | client |---IPP----># Printer #---IPP----># Printer #
/ \ +--------+ # object # # object #
########### ###########
########### ###########
O +--------+ # Non-Leaf# # subord. #
/|\ | client |---IPP----># Printer #---IPP----># Printer #
/ \ +--------+ # object # # object #
########### ###########
The Subordinate Printer can be a Non-Leaf Printer, as in Figures 4 through 6, or can be a Leaf Printer, as in Figures 1 through 3.
从属打印机可以是非叶式打印机，如图4至图6所示，也可以是叶式打印机，如图1至图3所示。
Figure 4. Chained IPP Printer Objects
图4。链接的IPP打印机对象
+------IPP--------------------->###########
/ +---># subord. #
/ / # Printer #
/ ########### IPP # object #
O +--------+ # Non-Leaf# / ###########
/|\ | client |---IPP----># Printer #--*
/ \ +--------+ # object # \
\ ########### IPP ###########
\ \ # subord. #
\ +---># Printer #
+------IPP---------------------># object #
###########
+------IPP--------------------->###########
/ +---># subord. #
/ / # Printer #
/ ########### IPP # object #
O +--------+ # Non-Leaf# / ###########
/|\ | client |---IPP----># Printer #--*
/ \ +--------+ # object # \
\ ########### IPP ###########
\ \ # subord. #
\ +---># Printer #
+------IPP---------------------># object #
###########
The Subordinate Printer can be a Non-Leaf Printer, as in Figures 4 through 6, or can be a Leaf Printer, as in Figures 1 through 3.
从属打印机可以是非叶式打印机，如图4至图6所示，也可以是叶式打印机，如图1至图3所示。
Figure 5. IPP Printer Object Fan-Out
图5。IPP打印机对象扇出
###########
# Non-Leaf#
+---># Printer #-+
/ # object # \
IPP ########### \ ###########
O +--------+ / +-IPP-># subord. #
/|\ | client |--+-----------IPP---------------># Printer #
/ \ +--------+ \ +-IPP-># object #
IPP ########### / ###########
\ # Non-Leaf# /
+---># Printer #-+
# object #
###########
###########
# Non-Leaf#
+---># Printer #-+
/ # object # \
IPP ########### \ ###########
O +--------+ / +-IPP-># subord. #
/|\ | client |--+-----------IPP---------------># Printer #
/ \ +--------+ \ +-IPP-># object #
IPP ########### / ###########
\ # Non-Leaf# /
+---># Printer #-+
# object #
###########
The Subordinate Printer can be a Non-Leaf Printer, as in Figures 4 through 6, or can be a Leaf Printer, as in Figures 1 through 3.
从属打印机可以是非叶式打印机，如图4至图6所示，也可以是叶式打印机，如图1至图3所示。
Figure 6. IPP Printer Object Fan-In
图6。IPP打印机对象扇入
This section describes the forwarding of Job and Printer requests to Subordinate Printer objects.
本节介绍将作业和打印机请求转发到下级打印机对象。
In Printer Fan-Out, Printer Fan-In, and Chained Printers, the Non-Leaf IPP Printer object MUST NOT forward the operations that affect Printer objects to its Subordinate Printer objects. If a client seeks to explicitly target a Subordinate Printer, the client MUST specify the URI of the Subordinate Printer. The client can determine the URI of any Subordinate Printers by querying the Printer's "subordinate-printers-supported (1setOf uri) attribute (see section 7.1).
在打印机扇出、打印机扇入和链式打印机中，非叶式IPP打印机对象不得将影响打印机对象的操作转发给其下级打印机对象。如果客户端试图显式地以从属打印机为目标，则客户端必须指定从属打印机的URI。客户端可以通过查询打印机的“支持的从属打印机（1setOf URI）”属性来确定任何从属打印机的URI（参见第7.1节）。
Table 7 lists the operations that affect Printer objects and the forwarding behavior that a Non-Leaf Printer MUST exhibit to its immediate Subordinate Printers. Operations that affect jobs have a different forwarding rule (see section 10.7.2 and Table 8):
表7列出了影响打印机对象的操作以及非叶式打印机必须向其直接下级打印机显示的转发行为。影响作业的操作具有不同的转发规则（见第10.7.2节和表8）：
Table 7. Forwarding Operations that Affect Printer Objects
表7。转发影响打印机对象的操作
Printer Operation Non-Leaf Printer Action
---------------------------------------------------------------
Printer Operations:
Printer Operation Non-Leaf Printer Action
---------------------------------------------------------------
Printer Operations:
Enable-Printer MUST NOT forward to any of its Subordinate Printers Disable-Printer MUST NOT forward to any of its Subordinate Printers Hold-New-Jobs MUST NOT forward to any of its Subordinate Printers Release-Held-New- MUST NOT forward to any of its Subordinate Jobs Printers Deactivate-Printer MUST NOT forward to any of its Subordinate Printers Activate-Printer MUST NOT forward to any of its Subordinate Printers Restart-Printer MUST NOT forward to any of its Subordinate Printers Shutdown-Printer MUST NOT forward to any of its Subordinate Printers Startup-Printer MUST NOT forward to any of its Subordinate Printers
启用打印机不得转发至其任何下级打印机禁用打印机不得转发至其任何下级打印机保留新作业不得转发至其任何下级打印机发布保留新-不得转发至其任何下级作业打印机停用打印机不得转发至其任何下级打印机激活打印机不得转发到其任何下级打印机重新启动打印机不得转发到其任何下级打印机关机打印机不得转发到其任何下级打印机启动打印机不得转发到其任何下级打印机
IPP/1.1 Printer See [RFC2911] Operations:
IPP/1.1打印机参见[RFC2911]操作：
Get-Printer- MUST NOT forward to any of its Subordinate Attributes Printers Pause-Printer MUST NOT forward to any of its Subordinate Printers Resume-Printer MUST NOT forward to any of its Subordinate Printers
获取打印机-不得转发到其任何从属属性打印机暂停打印机不得转发到其任何从属打印机恢复打印机不得转发到其任何从属打印机
Set Operations: See [RFC3380]
设置操作：请参见[RFC3380]
Set-Printer- MUST NOT forward to any of its Subordinate Attributes Printers
设置打印机-不得转发到其任何从属属性打印机
Unlike Printer Operations that only affect Printer objects (see section 10.7.1), a Non-Leaf Printer object MUST forward operations that directly affect jobs to the appropriate Job object(s) in one or more of its immediate Subordinate Printer objects. Forwarding is REQUIRED since the purpose of this Job operation is to affect the indicated job, which may have been forwarded itself. This forwarding MAY be immediate or queued, depending on the operation and the implementation. For example, a Non-Leaf Printer object MAY queue/spool jobs, feeding a job at a time to its Subordinate Printer(s), or MAY forward jobs immediately to one of its Subordinate Printers. In either case, the Non-Leaf Printer object forwards Job Creation operations to one of its Subordinate Printers. Only the time of forwarding of the Job Creation operations depends on whether the policy is to queue/spool jobs in the Non-Leaf Printer or the Subordinate Printer.
与仅影响打印机对象的打印机操作不同（参见第10.7.1节），非叶式打印机对象必须将直接影响作业的操作转发到其一个或多个直接下级打印机对象中的相应作业对象。需要转发，因为此作业操作的目的是影响所指示的作业，该作业可能已自行转发。根据操作和实现，此转发可以是即时的，也可以是排队的。例如，非活页打印机对象可以对作业进行排队/假脱机，一次将作业提供给其下属打印机，或者可以将作业立即转发给其下属打印机之一。在任何一种情况下，非叶子打印机对象都会将作业创建操作转发给其下属打印机之一。只有转发作业创建操作的时间取决于策略是对非活页打印机还是从属打印机中的作业进行排队/假脱机。
When a Non-Leaf Printer object creates a Job object in its Subordinate Printer, whether that Non-Leaf Printer object keeps a fully formed Job object or just keeps a mapping from the "job-ids" that it assigned to those assigned by its Subordinate Printer object is IMPLEMENTATION-DEPENDENT. In either case, the Non-Leaf Printer MUST be able to accept and carry out future Job operations that specify the "job-id" that the Non-Leaf Printer assigned and returned to the job submitting client.
当非叶式打印机对象在其从属打印机中创建作业对象时，该非叶式打印机对象是保留完整格式的作业对象，还是仅保留从其分配给其从属打印机对象的“作业ID”的映射取决于实现。在任何一种情况下，无叶打印机都必须能够接受并执行将来的作业操作，这些作业操作指定了无叶打印机分配并返回给作业提交客户端的“作业id”。
Table 8 lists the operations that directly affect jobs and the forwarding behavior that a Non-Leaf Printer MUST exhibit to its Subordinate Printers.
表8列出了直接影响作业的操作以及非叶式打印机必须向其下属打印机显示的转发行为。
Table 8. Forwarding Operations that Affect Jobs Objects
表8。影响作业对象的转发操作
Operation Non-Leaf Printer action
---------------------------------------------------------------
Job operations:
Operation Non-Leaf Printer action
---------------------------------------------------------------
Job operations:
Reprocess-Job MUST forward to the appropriate Job in one of its Subordinate Printers Cancel-Current- MUST NOT forward Job Resume-Job MUST forward to the appropriate Job in one of its Subordinate Printers Promote-Job MUST forward to the appropriate Job in one of its Subordinate Printers
重新处理作业必须转发到其下属打印机之一中的相应作业取消当前-不得转发作业恢复作业必须转发到其下属打印机之一中的相应作业升级作业必须转发到其下属打印机之一中的相应作业
IPP/1.1 Printer operations:
IPP/1.1打印机操作：
Print-Job MUST forward immediately or queue to the appropriate Subordinate Printer Print-URI MUST forward immediately or queue to the appropriate Subordinate Printer Validate-Job MUST forward to the appropriate Subordinate Printer Create-Job MUST forward immediately or queue to the appropriate Subordinate Printer Get-Jobs MUST forward to all its Subordinate Printers Purge-Jobs MUST forward to all its Subordinate Printers
打印作业必须立即转发或队列到相应的下级打印机打印URI必须立即转发或队列到相应的下级打印机验证作业必须转发到相应的下级打印机创建作业必须立即转发或队列到相应的下级打印机获取作业必须转发到其所有下级打印机清除作业必须转发到其所有下级打印机
IPP/1.1 Job operations:
IPP/1.1作业操作：
Send-Document MUST forward immediately or queue to the appropriate Job in one of its Subordinate Printers Send-URI MUST forward immediately or queue to the appropriate Job in one of its Subordinate Printers Cancel-Job MUST forward to the appropriate Job in one of its Subordinate Printers Get-Job- MUST forward to the appropriate Job in one of Attributes its Subordinate Printers if the Non-Leaf Printer doesn't know the complete status of the Job object Hold-Job MUST forward to the appropriate Job in one of its Subordinate Printers Release-Job MUST forward to the appropriate Job in one of its Subordinate Printers
发送文档必须立即转发或排队到其下属打印机之一中的相应作业发送URI必须立即转发或排队到其下属打印机之一中的相应作业取消作业必须转发到其下属打印机之一中的相应作业获取作业-必须转发到其下属打印机之一中的相应作业属性其从属打印机如果非叶子打印机不知道作业对象的完整状态，则保持作业必须转发到其一个从属打印机中的相应作业发布作业必须转发到其一个从属打印机中的相应作业
Restart-Job MUST forward to the appropriate Job in one of its Subordinate Printers
重新启动作业必须转发到其下属打印机之一中的相应作业
IPP Set operations: See [RFC3380]
IPP装置操作：见[RFC3380]
Set-Job- MUST forward to the appropriate Job in one of Attributes its Subordinate Printers
设置作业-必须转发到其下属打印机属性之一中的相应作业
When a Printer receives a request that REQUIRES forwarding, it does so on a "best efforts basis" and returns a response to its client without waiting for responses from any of its Subordinate Printers. Such forwarded requests could fail.
当打印机收到需要转发的请求时，它会在“尽最大努力”的基础上进行转发，并向其客户端返回响应，而无需等待其任何下级打印机的响应。这样的转发请求可能会失败。
The following operation and Job Description attributes are defined to help represent Job relationships for Fan-Out and forwarding of jobs.
定义以下操作和作业描述属性有助于表示作业扇出和转发的作业关系。
10.8.1. output-device-assigned (name(127)) Job Description Attribute - from [RFC2911]
10.8.1. 分配的输出设备（名称（127））作业描述属性-来自[RFC2911]
[RFC2911] defines "output-device-assigned" as follows: "This attribute identifies the Output Device to which the Printer object has assigned 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 "Device Fan-Out" see [RFC2911] section 2.1)." See also section 10.1 in this specification.
[RFC2911]将“已分配的输出设备”定义为：“此属性标识打印机对象已分配此作业的输出设备。如果输出设备实现嵌入式打印机对象，则打印机对象无需设置此属性。如果打印服务器实现打印机对象，则该值可能为空（零长度字符串）或在打印机对象将输出设备分配给作业之前不返回。当单个打印机对象支持多个设备时，此属性特别有用（所谓的“设备扇出”请参见[RFC2911]第2.1节）。“另请参见本规范第10.1节。
10.8.2. original-requesting-user-name (name(MAX)) Operation and Job Description Attribute
10.8.2. 原始请求用户名（名称（最大））操作和职务描述属性
The operation attribute containing the user name of the original user; i.e., corresponding to the "requesting-user-name" operation attribute (see [RFC2911], section 3.2.1.1) that the original client supplied to the first Printer object. The Printer copies the "original-requesting-user-name" operation attribute to the corresponding Job Description attribute.
包含原始用户用户名的操作属性；i、 e.，对应于原始客户端提供给第一个打印机对象的“请求用户名”操作属性（参见[RFC2911]，第3.2.1.1节）。打印机将“原始请求用户名”操作属性复制到相应的职务描述属性。
10.8.3. requesting-user-name (name(MAX)) Operation Attribute - Additional Semantics
10.8.3. 请求用户名（name（MAX））操作属性-附加语义
The IPP/1.1 "requesting-user-name" operation attribute (see [RFC2911] section 3.2.1.1) is updated by each client to be itself on each hop; i.e., the "requesting-user-name" represents the client forwarding the request, not the original client.
IPP/1.1“请求用户名”操作属性（参见[RFC2911]第3.2.1.1节）由每个客户端更新，使其在每个跃点上都是自己的；i、 例如，“请求用户名”表示转发请求的客户端，而不是原始客户端。
10.8.4. job-originating-user-name (name(MAX)) Job Description Attribute - Additional Semantics
10.8.4. 作业原始用户名（name（MAX））作业描述属性-附加语义
The "job-originating-user-name" Job Description attribute (see [RFC2911], section 4.3.6) remains as the authenticated original user, not the parent Printer's authenticated host, and is forwarded by each client without changing the value.
“作业发起用户名”作业描述属性（参见[RFC2911]，第4.3.6节）保留为经过身份验证的原始用户，而不是父打印机的身份验证主机，并由每个客户端转发，而不更改值。
The Job and Printer Administrative operations defined in this document are OPTIONAL operations. However, some operations MUST be implemented if others are implemented, as shown in Table 9.
本文档中定义的作业和打印机管理操作是可选操作。但是，如果实现了其他操作，则必须实现一些操作，如表9所示。
Table 9. Conformance Requirement Dependencies for Operations
表9。操作的一致性需求依赖关系
Operations REQUIRED If any of these operations are
supported:
--------------------------------------------------------------------
Enable-Printer Disable-Printer
Disable-Printer Enable-Printer
Pause-Printer Resume-Printer
Resume-Printer Pause-Printer,
Pause-Printer-After-Current-Job
Hold-New-Jobs Release-Held-New-Jobs
Release-Held-New-Jobs Hold-New-Jobs
Activate-Printer, Deactivate-Printer
Disable-Printer,
Pause-Printer-After-Current-Job
Deactivate-Printer, Activate-Printer
Enable-Printer,
Resume-Printer
Restart-Printer none
Shutdown-Printer none
Startup-Printer none
Reprocess-Job none
Cancel-Current-Job none
Resume-Job Suspend-Current-Job
Suspend-Current-Job Resume-Job
Operations REQUIRED If any of these operations are
supported:
--------------------------------------------------------------------
Enable-Printer Disable-Printer
Disable-Printer Enable-Printer
Pause-Printer Resume-Printer
Resume-Printer Pause-Printer,
Pause-Printer-After-Current-Job
Hold-New-Jobs Release-Held-New-Jobs
Release-Held-New-Jobs Hold-New-Jobs
Activate-Printer, Deactivate-Printer
Disable-Printer,
Pause-Printer-After-Current-Job
Deactivate-Printer, Activate-Printer
Enable-Printer,
Resume-Printer
Restart-Printer none
Shutdown-Printer none
Startup-Printer none
Reprocess-Job none
Cancel-Current-Job none
Resume-Job Suspend-Current-Job
Suspend-Current-Job Resume-Job
Promote-Job none Schedule-Job-After Promote-Job
提升作业无在提升作业后安排作业
Tables 10 and 11 list the "printer-state-reasons" and "job-state-reasons" values that are REQUIRED if the indicated operations are supported.
表10和表11列出了支持所示操作时所需的“打印机状态原因”和“作业状态原因”值。
Table 10. Conformance Requirement Dependencies for "printer-state-reasons" Values
表10。“打印机状态原因”值的一致性要求依赖项
"printer-state- Conformance If any of the following Printer
reasons" values: Requirement Operations are supported:
--------------------------------------------------------------------
'paused' REQUIRED Pause-Printer,
Pause-Printer-After-Current-Job,
or Deactivate-Printer
'hold-new-jobs' REQUIRED Hold-New-Jobs
'moving-to-paused' OPTIONAL Pause-Printer,
Pause-Printer-After-Current-Job,
Deactivate-Printer
'deactivated' REQUIRED Deactivate-Printer
"printer-state- Conformance If any of the following Printer
reasons" values: Requirement Operations are supported:
--------------------------------------------------------------------
'paused' REQUIRED Pause-Printer,
Pause-Printer-After-Current-Job,
or Deactivate-Printer
'hold-new-jobs' REQUIRED Hold-New-Jobs
'moving-to-paused' OPTIONAL Pause-Printer,
Pause-Printer-After-Current-Job,
Deactivate-Printer
'deactivated' REQUIRED Deactivate-Printer
Table 11. Conformance Requirement Dependencies for "job-state-reasons" Values
表11。“作业状态原因”值的一致性需求依赖关系
"job-state-reasons" Conformance If any of the following Job values: Requirement operations are supported:
如果支持以下任何作业值：需求操作，则符合“作业状态原因”：
'job-suspended' REQUIRED Suspend-Current-Job 'printer-stopped' REQUIRED Always REQUIRED
“作业已挂起”必需挂起当前作业“打印机已停止”必需始终必需
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC 2246, January 1999.
[RFC2246]Dierks，T.和C.Allen，“TLS协议版本1.0”，RFC2246，1999年1月。
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2616]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2616，1999年6月。
[RFC2910] Herriot, R., Butler, S., Moore, P., Turner, R., and J. Wenn, "Internet Printing Protocol/1.1: Encoding and Transport", RFC 2910, September 2000.
[RFC2910]Herriot，R.，Butler，S.，Moore，P.，Turner，R.，和J.Wenn，“互联网打印协议/1.1：编码和传输”，RFC 29102000年9月。
[RFC2911] Hastings, T., Herriot, R., deBry, R., Isaacson, S., and P. Powell, "Internet Printing Protocol/1.1: Model and Semantics", RFC 2911, September 2000.
[RFC2911]黑斯廷斯，T.，赫里奥特，R.，德布里，R.，艾萨克森，S.，和P.鲍威尔，“互联网打印协议/1.1：模型和语义”，RFC 29112000年9月。
[RFC3380] Hastings, T., Herriot, R., Kugler, C., and H. Lewis, "Internet Printing Protocol (IPP): Job and Printer Set Operations", RFC 3380, September 2002.
[RFC3380]黑斯廷斯，T.，赫里奥特，R.，库格勒，C.，和H.刘易斯，“互联网打印协议（IPP）：作业和打印机集操作”，RFC3380，2002年9月。
[RFC2567] Wright, F., "Design Goals for an Internet Printing Protocol", RFC 2567, April 1999.
[RFC2567]Wright，F.，“互联网打印协议的设计目标”，RFC2567，1999年4月。
[RFC2568] Zilles, S., "Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol", RFC 2568, April 1999.
[RFC2568]Zilles，S.“互联网打印协议模型和协议结构的基本原理”，RFC 2568，1999年4月。
[RFC2569] Herriot, R., Hastings, T., Jacobs, N., and J. Martin, "Mapping between LPD and IPP Protocols", RFC 2569, April 1999.
[RFC2569]Herriot，R.，Hastings，T.，Jacobs，N.，和J.Martin，“LPD和IPP协议之间的映射”，RFC 2569，1999年4月。
[RFC3196] Hastings, T., Manros, C., Zehler, P., Kugler, C., and H. Holst, "Internet Printing Protocol/1.1: Implementor's Guide", RFC 3196, November 2001.
[RFC3196]黑斯廷斯，T.，曼罗斯，C.，泽勒，P.，库格勒，C.，和H.霍尔斯特，“互联网打印协议/1.1：实施者指南”，RFC 31962001年11月。
[RFC3239] Kugler, C., Lewis, H., and T. Hastings, "Internet Printing Protocol (IPP): Requirements for Job, Printer, and Device Administrative Operations", RFC 3239, February 2002.
[RFC3239]Kugler，C.，Lewis，H.，和T.Hastings，“互联网打印协议（IPP）：作业、打印机和设备管理操作的要求”，RFC 3239，2002年2月。
[RFC3995] Herriot, R. and T. Hastings, "Internet Printing Protocol (IPP): Event Notifications and Subscriptions", RFC 3995, February 2005.
[RFC3995]Herriot，R.和T.Hastings，“互联网打印协议（IPP）：事件通知和订阅”，RFC 39952005年2月。
This section contains the registration information that IANA added to the IPP Registry according to the procedures defined in [RFC2911], section 6, to cover the definitions in this document. The resulting registrations have been published as additions to the http://www.iana.org/assignments/ipp-registrations file.
本节包含IANA根据[RFC2911]第6节中定义的程序添加到IPP注册中心的注册信息，以涵盖本文件中的定义。由此产生的注册已作为对http://www.iana.org/assignments/ipp-registrations 文件
The following table lists all the attributes defined in this document. These have been registered according to the procedures in [RFC2911], section 6.2.
下表列出了本文档中定义的所有属性。已根据[RFC2911]第6.2节中的程序对其进行了登记。
Name Reference Section
-------------------------------------- --------- -------
Job Description attributes:
original-requesting-user-name (name(MAX)) [RFC3998] 10.8.2
Name Reference Section
-------------------------------------- --------- -------
Job Description attributes:
original-requesting-user-name (name(MAX)) [RFC3998] 10.8.2
Printer Description attributes: subordinate-printers-supported (1setOf uri) [RFC3998] 7.1 parent-printers-supported (1setOf uri) [RFC3998] 7.2
打印机描述属性：支持的从属打印机（1setOf uri）[RFC3998]7.1支持的父打印机（1setOf uri）[RFC3998]7.2
Operation attributes: original-requesting-user-name (name(MAX)) [RFC3998] 10.8.2
操作属性：原始请求用户名（名称（最大））[RFC3998]10.8.2
This section lists the additional values defined in this document for existing attributes.
本节列出了本文档中为现有属性定义的附加值。
Attribute
Value Reference Section
--------------------- --------- -------
job-state-reasons (1setOf type2 keyword)
job-suspended [RFC3998] 9.1
Attribute
Value Reference Section
--------------------- --------- -------
job-state-reasons (1setOf type2 keyword)
job-suspended [RFC3998] 9.1
printer-state-reasons (1setOf type2 keyword) hold-new-jobs [RFC3998] 8.1 deactivated [RFC3998] 8.2
打印机状态原因（1setOf type2关键字）保留新作业[RFC3998]8.1已停用[RFC3998]8.2
The following table lists all the new enum attribute values defined in this document. These have been registered according to the procedures in [RFC2911], section 6.1.
下表列出了此文档中定义的所有新枚举属性值。已根据[RFC2911]第6.1节中的程序进行了登记。
Attribute (attribute syntax)
Value Name Reference Section
------- -------------------- --------- -------
operations-supported (1setOf type2 enum) [RFC2911] 4.4.1
0x0022 Enable-Printer [RFC3998] 3
0x0023 Disable-Printer [RFC3998] 3
0x0024 Pause-Printer-After-Current-Job [RFC3998] 3
0x0025 Hold-New-Jobs [RFC3998] 3
0x0026 Release-Held-New-Jobs [RFC3998] 3
0x0027 Deactivate-Printer [RFC3998] 3
0x0028 Activate-Printer [RFC3998] 3
0x0029 Restart-Printer [RFC3998] 3
0x002A Shutdown-Printer [RFC3998] 3
0x002B Startup-Printer [RFC3998] 3
0x002C Reprocess-Job [RFC3998] 4
0x002D Cancel-Current-Job [RFC3998] 4
0x002E Suspend-Current-Job [RFC3998] 4
0x002F Resume-Job [RFC3998] 4
0x0030 Promote-Job [RFC3998] 4
0x0031 Schedule-Job-After [RFC3998] 4
Attribute (attribute syntax)
Value Name Reference Section
------- -------------------- --------- -------
operations-supported (1setOf type2 enum) [RFC2911] 4.4.1
0x0022 Enable-Printer [RFC3998] 3
0x0023 Disable-Printer [RFC3998] 3
0x0024 Pause-Printer-After-Current-Job [RFC3998] 3
0x0025 Hold-New-Jobs [RFC3998] 3
0x0026 Release-Held-New-Jobs [RFC3998] 3
0x0027 Deactivate-Printer [RFC3998] 3
0x0028 Activate-Printer [RFC3998] 3
0x0029 Restart-Printer [RFC3998] 3
0x002A Shutdown-Printer [RFC3998] 3
0x002B Startup-Printer [RFC3998] 3
0x002C Reprocess-Job [RFC3998] 4
0x002D Cancel-Current-Job [RFC3998] 4
0x002E Suspend-Current-Job [RFC3998] 4
0x002F Resume-Job [RFC3998] 4
0x0030 Promote-Job [RFC3998] 4
0x0031 Schedule-Job-After [RFC3998] 4
The following table lists all the operations defined in this document. These have been registered according to the procedures in [RFC2911], section 6.4.
下表列出了本文档中定义的所有操作。已根据[RFC2911]第6.4节中的程序进行了登记。
Name Reference Section
----------------------------- --------- -------
Activate-Printer [RFC3998] 3.4.2
Cancel-Current-Job [RFC3998] 4.2
Deactivate-Printer [RFC3998] 3.4.1
Disable-Printer [RFC3998] 3.1.1
Enable-Printer [RFC3998] 3.1.2
Hold-New-Jobs [RFC3998] 3.3.1
Pause-Printer-After-Current-Job [RFC3998] 3.2.1
Promote-Job [RFC3998] 4.4.1
Release-Held-New-Jobs [RFC3998] 3.3.2
Reprocess-Job [RFC3998] 4.1
Restart-Printer [RFC3998] 3.5.1
Resume-Job [RFC3998] 4.3.2
Schedule-Job-After [RFC3998] 4.4.2
Shutdown-Printer [RFC3998] 3.5.2
Startup-Printer [RFC3998] 3.5.3
Suspend-Current-Job [RFC3998] 4.3.1
Name Reference Section
----------------------------- --------- -------
Activate-Printer [RFC3998] 3.4.2
Cancel-Current-Job [RFC3998] 4.2
Deactivate-Printer [RFC3998] 3.4.1
Disable-Printer [RFC3998] 3.1.1
Enable-Printer [RFC3998] 3.1.2
Hold-New-Jobs [RFC3998] 3.3.1
Pause-Printer-After-Current-Job [RFC3998] 3.2.1
Promote-Job [RFC3998] 4.4.1
Release-Held-New-Jobs [RFC3998] 3.3.2
Reprocess-Job [RFC3998] 4.1
Restart-Printer [RFC3998] 3.5.1
Resume-Job [RFC3998] 4.3.2
Schedule-Job-After [RFC3998] 4.4.2
Shutdown-Printer [RFC3998] 3.5.2
Startup-Printer [RFC3998] 3.5.3
Suspend-Current-Job [RFC3998] 4.3.1
The following table lists the status code defined in this document. This has been registered according to the procedures in [RFC2911], section 6.6.
下表列出了本文档中定义的状态代码。已根据[RFC2911]第6.6节中的程序进行了登记。
Value Name Reference Section
------ ------------------------ --------- -------
0x0000:0x00FF - "successful"
none at this time
Value Name Reference Section
------ ------------------------ --------- -------
0x0000:0x00FF - "successful"
none at this time
0x0100:0x01FF - "informational" none at this time
0x0100:0x01FF-“信息性”此时无
0x0300:0x03FF - "redirection" See RFC 2911 Errata none at this time
0x0300:0x03FF-“重定向”见RFC 2911勘误表此时无
0x0400:0x04FF - "client-error" none at this time
0x0400:0x04FF-“客户端错误”此时无
0x0500:0x05FF - "server-error" 0x050A server-error-printer-is-deactivated [RFC3998] 5.1
0x0500:0x05FF-“服务器错误”0x050A服务器错误打印机已停用[RFC3998]5.1
This document has the same localization considerations as [RFC2911].
本文件具有与[RFC2911]相同的本地化注意事项。
The IPP Model and Semantics document [RFC2911] discusses high level security requirements (Client Authentication, Server Authentication, and Operation Privacy). Client Authentication is the mechanism by which the client proves its identity to the server in a secure manner. Server Authentication is the mechanism by which the server proves its identity to the client in a secure manner. Operation Privacy is defined as a mechanism for protecting operations from eavesdropping.
IPP模型和语义文档[RFC2911]讨论了高级安全要求（客户端身份验证、服务器身份验证和操作隐私）。客户端身份验证是客户端以安全的方式向服务器证明其身份的机制。服务器身份验证是服务器以安全的方式向客户端证明其身份的机制。操作隐私被定义为防止操作被窃听的机制。
Printer operations defined in this specification (see section 3), as well as Pause-Printer, Resume-Printer, and Purge-Job (defined in [RFC2911]) are intended for use by an operator and/or administrator. Job operations defined in this specification (see section 4) and Cancel-Job, Hold-Job, and Release-Job (defined in [RFC2911]) are intended for use by the job owner, operator, or administrator of the Printer object. These operator and administrator operations affect service for all users.
本规范（见第3节）中定义的打印机操作以及暂停打印机、恢复打印机和清除作业（在[RFC2911]中定义）供操作员和/或管理员使用。本规范（见第4节）中定义的作业操作以及取消作业、保留作业和释放作业（在[RFC2911]中定义）旨在供打印机对象的作业所有者、操作员或管理员使用。这些操作员和管理员操作会影响所有用户的服务。
Inappropriate use of an administrative operation by an unauthenticated end user can affect the quality of service for all users. Therefore, IPP Printer implementations MUST support both successful certificate-based TLS [RFC2246] client authentication and successful operator/administrator authorization (see [RFC2911], sections 5.2.7 and 8, and [RFC2910]) to perform the administrative operations defined in this document. [RFC2910] requires the IPP Printer to support the minimum cipher suite specified for TLS/1.0. The means for authorizing an operator or administrator of the Printer object are outside the scope of this specification, RFC 2910, and RFC 2911.
未经验证的最终用户不当使用管理操作可能会影响所有用户的服务质量。因此，IPP打印机实施必须支持成功的基于证书的TLS[RFC2246]客户端身份验证和成功的操作员/管理员授权（参见[RFC2911]，第5.2.7和8节，以及[RFC2910]），以执行本文档中定义的管理操作。[RFC2910]要求IPP打印机支持为TLS/1.0指定的最小密码套件。授权打印机对象的操作员或管理员的方法不在本规范RFC 2910和RFC 2911的范围内。
The use of TLS and Client Authentication solves the Denial of Service, Man in the Middle, and Masquerading security threats.
The use of TLS and Client Authentication solves the Denial of Service, Man in the Middle, and Masquerading security threats.translate error, please retry
The base set of IPP documents includes the following:
IPP文件的基本集包括以下内容：
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 [RFC3196]
Mapping between LPD and IPP Protocols [RFC2569]
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 [RFC3196]
Mapping between LPD and IPP Protocols [RFC2569]
"Design Goals for an Internet Printing Protocol" takes a broad look at distributed printing functionality, and it enumerates real-life scenarios that help clarify the features that have 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.
“Internet打印协议的设计目标”广泛介绍了分布式打印功能，并列举了有助于澄清Internet打印协议中必须包含的功能的实际场景。它确定了三类用户的需求：最终用户、操作员和管理员。它列出了IPP/1.0中满足的最终用户需求的子集。IPP/1.1中增加了一些可选的操作员操作。
"Rationale for the Structure and Model and Protocol for the Internet Printing Protocol" 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.
“互联网打印协议的结构、模型和协议的基本原理”从高层角度描述了IPP，定义了构成IPP规范文件套件的各种文件的路线图，并给出了IETF工作组主要决策的背景和基本原理。
"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 and a Job object. The Job object optionally supports multiple documents per Job. It also addresses security, internationalization, and directory issues.
“Internet打印协议/1.1：模型和语义”描述了一个简化模型，其中包含抽象对象、其属性以及独立于编码和传输的操作。它引入了打印机和作业对象。作业对象可以选择为每个作业支持多个文档。它还解决了安全性、国际化和目录问题。
"Internet Printing Protocol/1.1: Encoding and Transport" 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.
“Internet打印协议/1.1：编码和传输”是模型文档中定义的抽象操作和属性到HTTP/1.1[RFC2616]的正式映射。它定义了名为“应用程序/ipp”的新Internet MIME媒体类型的编码规则。本文档还定义了通过HTTP传输内容类型为“application/ipp”的消息体的规则。本文件定义了用于识别IPP打印机和作业的“ippget”方案。
"Internet Printing Protocol/1.1: Implementer's Guide" 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.
“互联网打印协议/1.1：实施者指南”为IPP客户端和IPP对象的实施者提供了见解和建议。它旨在帮助他们理解IPP/1.1以及一些可能有助于他们设计客户端和/或IPP对象实现的注意事项。例如，给出了处理请求的典型顺序，包括错误检查。还包括一些规范决策的动机。
"Mapping between LPD and IPP Protocols" gives some advice to implementers of gateways between IPP and LPD (Line Printer Daemon) implementations.
“LPD和IPP协议之间的映射”为IPP和LPD（Line Printer Daemon）实现之间网关的实现者提供了一些建议。
Authors' Addresses
作者地址
Carl Kugler IBM Corporation, 003G 6300 Diagonal Hwy Boulder, CO 80301
卡尔·库格勒IBM公司，美国科罗拉多州博尔德市对角大道003G 6300号，邮编80301
Phone: (303) 924-5060 EMail: kugler@us.ibm.com
电话：（303）924-5060电子邮件：kugler@us.ibm.com
Tom Hastings, editor Xerox Corporation 701 S Aviation Blvd. ESAE 242 El Segundo, CA 90245
汤姆·黑斯廷斯，编辑，施乐公司航空大道701号。加利福尼亚州塞贡多市ESAE 242号，邮编90245
Phone: 310-333-6413 Fax: 310-333-6342 EMail: hastings@cp10.es.xerox.com
电话：310-333-6413传真：310-333-6342电子邮件：hastings@cp10.es.xerox.com
Harry Lewis IBM Corporation 6300 Diagonal Hwy Boulder, CO 80301
Harry Lewis IBM Corporation科罗拉多州博尔德市6300号对角公路80301
Phone: (303) 924-5337 EMail: harryl@us.ibm.com
电话：（303）924-5337电子邮件：harryl@us.ibm.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。