Network Working Group T. Hastings
Request for Comments: 3196 C. Manros
Obsoletes: 2639 P. Zehler
Category: Informational Xerox Corporation
C. Kugler
IBM Printing Systems Co
H. Holst
i-data Printing Systems
November 2001
Network Working Group T. Hastings
Request for Comments: 3196 C. Manros
Obsoletes: 2639 P. Zehler
Category: Informational Xerox Corporation
C. Kugler
IBM Printing Systems Co
H. Holst
i-data Printing Systems
November 2001
Internet Printing Protocol/1.1: Implementor's Guide
Internet打印协议/1.1：实施者指南
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP).
本文档是一组文档之一，这些文档共同描述了新Internet打印协议（IPP）的所有方面。
Table of Contents
目录
1 Introduction................................................... 4
1.1 Conformance language........................................ 5
1.2 Other terminology........................................... 6
1.3 Issues Raised from Interoperability Testing Events.......... 6
2 IPP Objects.................................................... 6
3 IPP Operations................................................. 7
3.1 Common Semantics............................................ 7
3.1.1 Summary of Operation Attributes............................ 8
3.1.2 Suggested Operation Processing Steps for IPP Objects....... 16
3.1.2.1 Suggested Operation Processing Steps for all Operations. 17
3.1.2.1.1 Validate version number............................... 18
3.1.2.1.2 Validate operation identifier......................... 20
3.1.2.1.3 Validate the request identifier....................... 20
3.1.2.1.4 Validate attribute group and attribute presence and
order................................................. 20
3.1.2.1.4.1 Validate the presence and order of attribute groups. 20
3.1.2.1.4.2 Ignore unknown attribute groups in the expected
position............................................ 21
1 Introduction................................................... 4
1.1 Conformance language........................................ 5
1.2 Other terminology........................................... 6
1.3 Issues Raised from Interoperability Testing Events.......... 6
2 IPP Objects.................................................... 6
3 IPP Operations................................................. 7
3.1 Common Semantics............................................ 7
3.1.1 Summary of Operation Attributes............................ 8
3.1.2 Suggested Operation Processing Steps for IPP Objects....... 16
3.1.2.1 Suggested Operation Processing Steps for all Operations. 17
3.1.2.1.1 Validate version number............................... 18
3.1.2.1.2 Validate operation identifier......................... 20
3.1.2.1.3 Validate the request identifier....................... 20
3.1.2.1.4 Validate attribute group and attribute presence and
order................................................. 20
3.1.2.1.4.1 Validate the presence and order of attribute groups. 20
3.1.2.1.4.2 Ignore unknown attribute groups in the expected
position............................................ 21
3.1.2.1.4.3 Validate the presence of a single occurrence of
required Operation attributes....................... 21
3.1.2.1.5 Validate the values of the REQUIRED Operation
attributes............................................ 29
3.1.2.1.6 Validate the values of the OPTIONAL Operation
attributes............................................ 33
3.1.2.2 Suggested Additional Processing Steps for Operations
that Create/Validate Jobs and Add Documents............. 37
3.1.2.2.1 Default "ipp-attribute-fidelity" if not supplied...... 37
3.1.2.2.2 Check that the Printer object is accepting jobs....... 38
3.1.2.2.3 Validate the values of the Job Template attributes.... 38
3.1.2.3 Algorithm for job validation............................ 39
3.1.2.3.1 Check for conflicting Job Template attributes values.. 45
3.1.2.3.2 Decide whether to REJECT the request.................. 46
3.1.2.3.3 For the Validate-Job operation, RETURN one of the
success status codes.................................. 48
3.1.2.3.4 Create the Job object with attributes to support...... 48
3.1.2.3.5 Return one of the success status codes................ 50
3.1.2.3.6 Accept appended Document Content...................... 50
3.1.2.3.7 Scheduling and Starting to Process the Job............ 50
3.1.2.3.8 Completing the Job.................................... 50
3.1.2.3.9 Destroying the Job after completion................... 51
3.1.2.3.10 Interaction with "ipp-attribute-fidelity"............. 51
3.1.2.3.11 Character set code conversion support................. 51
3.1.2.3.12 What charset to return when an unsupported charset is
requested (Issue 1.19)?....... ....................... 52
3.1.2.3.13 Natural Language Override (NLO)....................... 53
3.1.3 Status codes returned by operation......................... 55
3.1.3.1 Printer Operations...................................... 55
3.1.3.1.1 Print-Job............................................. 55
3.1.3.1.2 Print-URI............................................. 58
3.1.3.1.3 Validate-Job.......................................... 58
3.1.3.1.4 Create-Job............................................ 58
3.1.3.1.5 Get-Printer-Attributes................................ 59
3.1.3.1.6 Get-Jobs.............................................. 60
3.1.3.1.7 Pause-Printer......................................... 61
3.1.3.1.8 Resume-Printer........................................ 62
3.1.3.1.8.1 What about Printers unable to change state due to
an error condition?................................. 63
3.1.3.1.8.2 How is "printer-state" handled on Resume-Printer?... 63
3.1.3.1.9 Purge-Printer......................................... 63
3.1.3.2 Job Operations.......................................... 64
3.1.3.2.1 Send-Document......................................... 64
3.1.3.2.2 Send-URI.............................................. 65
3.1.3.2.3 Cancel-Job............................................ 65
3.1.3.2.4 Get-Job-Attributes.................................... 67
3.1.3.2.5 Hold-Job.............................................. 68
3.1.3.2.6 Release-Job........................................... 69
3.1.2.1.4.3 Validate the presence of a single occurrence of
required Operation attributes....................... 21
3.1.2.1.5 Validate the values of the REQUIRED Operation
attributes............................................ 29
3.1.2.1.6 Validate the values of the OPTIONAL Operation
attributes............................................ 33
3.1.2.2 Suggested Additional Processing Steps for Operations
that Create/Validate Jobs and Add Documents............. 37
3.1.2.2.1 Default "ipp-attribute-fidelity" if not supplied...... 37
3.1.2.2.2 Check that the Printer object is accepting jobs....... 38
3.1.2.2.3 Validate the values of the Job Template attributes.... 38
3.1.2.3 Algorithm for job validation............................ 39
3.1.2.3.1 Check for conflicting Job Template attributes values.. 45
3.1.2.3.2 Decide whether to REJECT the request.................. 46
3.1.2.3.3 For the Validate-Job operation, RETURN one of the
success status codes.................................. 48
3.1.2.3.4 Create the Job object with attributes to support...... 48
3.1.2.3.5 Return one of the success status codes................ 50
3.1.2.3.6 Accept appended Document Content...................... 50
3.1.2.3.7 Scheduling and Starting to Process the Job............ 50
3.1.2.3.8 Completing the Job.................................... 50
3.1.2.3.9 Destroying the Job after completion................... 51
3.1.2.3.10 Interaction with "ipp-attribute-fidelity"............. 51
3.1.2.3.11 Character set code conversion support................. 51
3.1.2.3.12 What charset to return when an unsupported charset is
requested (Issue 1.19)?....... ....................... 52
3.1.2.3.13 Natural Language Override (NLO)....................... 53
3.1.3 Status codes returned by operation......................... 55
3.1.3.1 Printer Operations...................................... 55
3.1.3.1.1 Print-Job............................................. 55
3.1.3.1.2 Print-URI............................................. 58
3.1.3.1.3 Validate-Job.......................................... 58
3.1.3.1.4 Create-Job............................................ 58
3.1.3.1.5 Get-Printer-Attributes................................ 59
3.1.3.1.6 Get-Jobs.............................................. 60
3.1.3.1.7 Pause-Printer......................................... 61
3.1.3.1.8 Resume-Printer........................................ 62
3.1.3.1.8.1 What about Printers unable to change state due to
an error condition?................................. 63
3.1.3.1.8.2 How is "printer-state" handled on Resume-Printer?... 63
3.1.3.1.9 Purge-Printer......................................... 63
3.1.3.2 Job Operations.......................................... 64
3.1.3.2.1 Send-Document......................................... 64
3.1.3.2.2 Send-URI.............................................. 65
3.1.3.2.3 Cancel-Job............................................ 65
3.1.3.2.4 Get-Job-Attributes.................................... 67
3.1.3.2.5 Hold-Job.............................................. 68
3.1.3.2.6 Release-Job........................................... 69
3.1.3.2.7 Restart-Job........................................... 69
3.1.3.2.7.1 Can documents be added to a restarted job?.......... 69
3.1.4 Returning unsupported attributes in Get-Xxxx responses
(Issue 1.18)............................................... 70
3.1.5 Sending empty attribute groups............................. 70
3.2 Printer Operations.......................................... 71
3.2.1 Print-Job operation........................................ 71
3.2.1.1 Flow controlling the data portion of a Print-Job
request (Issue 1.22).................................... 71
3.2.1.2 Returning job-state in Print-Job response (Issue 1.30).. 71
3.2.2 Get-Printer-Attributes operation........................... 72
3.2.3 Get-Jobs operation......................................... 72
3.2.3.1 Get-Jobs, my-jobs='true', and 'requesting-user-name'
(Issue 1.39)?.......................................... 72
3.2.3.2 Why is there a "limit" attribute in the Get-Jobs
operation?.............................................. 73
3.2.4 Create-Job operation....................................... 73
3.3 Job Operations.............................................. 74
3.3.1 Validate-Job............................................... 74
3.3.2 Restart-Job................................................ 74
4 Object Attributes.............................................. 74
4.1 Attribute Syntax's.......................................... 74
4.1.1 The 'none' value for empty sets (Issue 1.37)............... 74
4.1.2 Multi-valued attributes (Issue 1.31)....................... 75
4.1.3 Case Sensitivity in URIs (issue 1.6)....................... 75
4.1.4 Maximum length for xxxWithLanguage and xxxWithoutLanguage.. 76
4.2 Job Template Attributes..................................... 76
4.2.1 multiple-document-handling(type2 keyword).................. 76
4.2.1.1 Support of multiple document jobs....................... 76
4.3 Job Description Attributes.................................. 76
4.3.1 Getting the date and time of day........................... 76
4.4 Printer Description Attributes.............................. 77
4.4.1 queued-job-count (integer(0:MAX)).......................... 77
4.4.1.1 Why is "queued-job-count" RECOMMENDED (Issue 1.14)?..... 77
4.4.1.2 Is "queued-job-count" a good measure of how busy a
printer is (Issue 1.15)?................................ 77
4.4.2 printer-current-time (dateTime)............................ 78
4.4.3 Printer-uri................................................ 78
4.5 Empty Jobs.................................................. 79
5 Directory Considerations....................................... 79
5.1 General Directory Schema Considerations..................... 79
5.2 IPP Printer with a DNS name................................. 79
6 Security Considerations........................................ 80
6.1 Querying jobs with IPP that were submitted using other job
submission protocols (Issue 1.32)........................... 80
7 Encoding and Transport......................................... 81
7.1 General Headers............................................. 83
7.2 Request Headers............................................ 84
3.1.3.2.7 Restart-Job........................................... 69
3.1.3.2.7.1 Can documents be added to a restarted job?.......... 69
3.1.4 Returning unsupported attributes in Get-Xxxx responses
(Issue 1.18)............................................... 70
3.1.5 Sending empty attribute groups............................. 70
3.2 Printer Operations.......................................... 71
3.2.1 Print-Job operation........................................ 71
3.2.1.1 Flow controlling the data portion of a Print-Job
request (Issue 1.22).................................... 71
3.2.1.2 Returning job-state in Print-Job response (Issue 1.30).. 71
3.2.2 Get-Printer-Attributes operation........................... 72
3.2.3 Get-Jobs operation......................................... 72
3.2.3.1 Get-Jobs, my-jobs='true', and 'requesting-user-name'
(Issue 1.39)?.......................................... 72
3.2.3.2 Why is there a "limit" attribute in the Get-Jobs
operation?.............................................. 73
3.2.4 Create-Job operation....................................... 73
3.3 Job Operations.............................................. 74
3.3.1 Validate-Job............................................... 74
3.3.2 Restart-Job................................................ 74
4 Object Attributes.............................................. 74
4.1 Attribute Syntax's.......................................... 74
4.1.1 The 'none' value for empty sets (Issue 1.37)............... 74
4.1.2 Multi-valued attributes (Issue 1.31)....................... 75
4.1.3 Case Sensitivity in URIs (issue 1.6)....................... 75
4.1.4 Maximum length for xxxWithLanguage and xxxWithoutLanguage.. 76
4.2 Job Template Attributes..................................... 76
4.2.1 multiple-document-handling(type2 keyword).................. 76
4.2.1.1 Support of multiple document jobs....................... 76
4.3 Job Description Attributes.................................. 76
4.3.1 Getting the date and time of day........................... 76
4.4 Printer Description Attributes.............................. 77
4.4.1 queued-job-count (integer(0:MAX)).......................... 77
4.4.1.1 Why is "queued-job-count" RECOMMENDED (Issue 1.14)?..... 77
4.4.1.2 Is "queued-job-count" a good measure of how busy a
printer is (Issue 1.15)?................................ 77
4.4.2 printer-current-time (dateTime)............................ 78
4.4.3 Printer-uri................................................ 78
4.5 Empty Jobs.................................................. 79
5 Directory Considerations....................................... 79
5.1 General Directory Schema Considerations..................... 79
5.2 IPP Printer with a DNS name................................. 79
6 Security Considerations........................................ 80
6.1 Querying jobs with IPP that were submitted using other job
submission protocols (Issue 1.32)........................... 80
7 Encoding and Transport......................................... 81
7.1 General Headers............................................. 83
7.2 Request Headers............................................ 84
7.3 Response Headers............................................ 86
7.4 Entity Headers............................................. 87
7.5 Optional support for HTTP/1.0............................... 88
7.6 HTTP/1.1 Chunking........................................... 88
7.6.1 Disabling IPP Server Response Chunking..................... 88
7.6.2 Warning About the Support of Chunked Requests.............. 88
8 References..................................................... 89
9 Authors' Addresses............................................. 91
10 Description of the Base IPP Documents.......................... 94
11 Full Copyright Statement....................................... 96
7.3 Response Headers............................................ 86
7.4 Entity Headers............................................. 87
7.5 Optional support for HTTP/1.0............................... 88
7.6 HTTP/1.1 Chunking........................................... 88
7.6.1 Disabling IPP Server Response Chunking..................... 88
7.6.2 Warning About the Support of Chunked Requests.............. 88
8 References..................................................... 89
9 Authors' Addresses............................................. 91
10 Description of the Base IPP Documents.......................... 94
11 Full Copyright Statement....................................... 96
Tables
桌子
Table 1 - Summary of Printer operation attributes that sender MUST
supply ................................................. 8
Table 2 - Summary of Printer operation attributes that sender MAY
supply ................................................. 10
Table 3 - Summary of Job operation attributes that sender MUST
supply.................................................. 12
Table 4 - Summary of Job operation attributes that sender MAY
supply.................................................. 14
Table 5 - Printer operation response attributes................... 16
Table 6 - Examples of validating IPP version...................... 19
Table 7 - Rules for validating single values X against Z.......... 40
Table 1 - Summary of Printer operation attributes that sender MUST
supply ................................................. 8
Table 2 - Summary of Printer operation attributes that sender MAY
supply ................................................. 10
Table 3 - Summary of Job operation attributes that sender MUST
supply.................................................. 12
Table 4 - Summary of Job operation attributes that sender MAY
supply.................................................. 14
Table 5 - Printer operation response attributes................... 16
Table 6 - Examples of validating IPP version...................... 19
Table 7 - Rules for validating single values X against Z.......... 40
IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document contains information that supplements the IPP Model and Semantics [RFC2911] and the IPP Transport and Encoding [RFC2910] documents. It is intended to help implementers understand IPP/1.1, as well as IPP/1.0 [RFC2565, RFC2566], and some of the considerations that may assist them in the design of their client and/or IPP object implementation. For example, a typical order of processing requests is given, including error checking. Motivation for some of the specification decisions is also included.
IPP是一种应用程序级协议，可用于使用Internet工具和技术进行分布式打印。本文档包含补充IPP模型和语义[RFC2911]以及IPP传输和编码[RFC2910]文档的信息。它旨在帮助实施者理解IPP/1.1和IPP/1.0[RFC2565，RFC2566]，以及一些可能有助于他们设计客户端和/或IPP对象实现的注意事项。例如，给出了处理请求的典型顺序，包括错误检查。还包括一些规范决策的动机。
This document obsoletes RFC 2639 which was the Implementor's Guide for IPP/1.0. The IPP Implementor's Guide (IIG) (this document) contains information that supplements the IPP Model and Semantics [RFC2911] and the IPP Transport and Encoding [RFC2910] documents. This document is just one of a suite of documents that fully define IPP. The base set of IPP documents includes:
本文件废除了RFC 2639，它是IPP/1.0的实施者指南。IPP实施者指南（IIG）（本文件）包含补充IPP模型和语义[RFC2911]以及IPP传输和编码[RFC2910]文件的信息。本文档只是完整定义IPP的一套文档之一。IPP文件的基本集包括：
Design Goals for an Internet Printing Protocol [RFC2567] Rationale for the Structure and Model and Protocol for the Internet Printing Protocol [RFC2568]
互联网打印协议的设计目标[RFC2567]互联网打印协议的结构、模型和协议的基本原理[RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementor's Guide (this
document)
Mapping between LPD and IPP Protocols [RFC2569]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementor's Guide (this
document)
Mapping between LPD and IPP Protocols [RFC2569]
See section 10 for a description of these base IPP documents. Anyone reading these documents for the first time is strongly encouraged to read the IPP documents in the above order.
有关这些基本IPP文件的说明，请参见第10节。强烈建议首次阅读这些文件的任何人按照上述顺序阅读IPP文件。
As such the information in this document is not part of the formal specification of IPP/1.1. Instead information is presented to help implementers understand IPP/1.1, as well as IPP/1.0 [RFC2565, RFC2566], including some of the motivation for decisions taken by the committee in developing the specification. Some of the implementation considerations are intended to help implementers design their client and/or IPP object implementations. If there are any contradictions between this document and [RFC2911] or [RFC2910], those documents take precedence over this document.
因此，本文件中的信息不是IPP/1.1正式规范的一部分。相反，提供信息是为了帮助实施者理解IPP/1.1以及IPP/1.0[RFC2565，RFC2566]，包括委员会在制定规范时做出决定的一些动机。一些实现注意事项旨在帮助实现者设计其客户机和/或IPP对象实现。如果本文件与[RFC2911]或[RFC2910]之间存在任何矛盾，则这些文件优先于本文件。
Platform-specific implementation considerations will be included in this guide as they become known.
特定于平台的实施注意事项将包括在本指南中。
Note: In order to help the reader of the IIG and the IPP Model and Semantics document, the sections in this document parallel the corresponding sections in the Model document and are numbered the same for ease of cross reference. The sections that correspond to the IPP Transport and Encoding are correspondingly offset.
注：为了帮助IIG和IPP模型和语义文档的读者，本文档中的章节与模型文档中的相应章节平行，并且编号相同，以便于交叉参考。与IPP传输和编码相对应的部分相应偏移。
Usually, this document does not contain the terminology MUST, MUST NOT, MAY, NEED NOT, SHOULD, SHOULD NOT, REQUIRED, and OPTIONAL. However, when those terms do appear in this document, their intent is to repeat what the [RFC2911] and [RFC2910] documents require and allow, rather than specifying additional conformance requirements. These terms are defined in section 12 on conformance terminology in [RFC2911], most of which is taken from RFC 2119 [RFC2119].
通常，本文档不包含术语“必须”、“不得”、“可能”、“不需要”、“应该”、“不应该”、“必需”和“可选”。但是，当这些术语出现在本文件中时，它们的目的是重复[RFC2911]和[RFC2910]文件要求和允许的内容，而不是规定其他合规性要求。[RFC2911]中关于一致性术语的第12节对这些术语进行了定义，其中大部分术语取自RFC 2119[RFC2119]。
Implementers should read section 12 (APPENDIX A) in [RFC2911] in order to understand these capitalized words. The words MUST, MUST NOT, and REQUIRED indicate what implementations are required to support in a client or IPP object in order to be conformant to [RFC2911] and [RFC2910]. MAY, NEED NOT, and OPTIONAL indicate was is merely allowed as an implementer option. The verbs SHOULD and SHOULD NOT indicate suggested behavior, but which is not required or disallowed, respectively, in order to conform to the specification.
实施者应阅读[RFC2911]中的第12节（附录A），以便理解这些大写单词。词语必须、不得和必需表示为了符合[RFC2911]和[RFC2910]，需要在客户端或IPP对象中支持哪些实现。可以、不需要和可选指示仅允许作为实现者选项。动词应该和不应该表示建议的行为，但为了符合规范，这些行为分别不是必需的或不允许的。
This document uses other terms, such as "attributes", "operation", and "Printer" as defined in [RFC2911] section 12. In addition, the term "sender" refers to the client that sends a request or an IPP object that returns a response. The term "receiver" refers to the IPP object that receives a request and to a client that receives a response.
本文件使用了[RFC2911]第12节中定义的其他术语，如“属性”、“操作”和“打印机”。此外，术语“发送者”指发送请求的客户端或返回响应的IPP对象。术语“接收方”指接收请求的IPP对象和接收响应的客户端。
The IPP WG has conducted three open Interoperability Testing Events. The first one was held in September 1998, the second one was held in March 1999, and the third one was held in October 2000. See the summary reports in:
IPP工作组进行了三次开放式互操作性测试活动。第一届于1998年9月举行，第二届于1999年3月举行，第三届于2000年10月举行。请参阅中的摘要报告：
ftp://ftp.pwg.org/pub/pwg/ipp/new_TES/
ftp://ftp.pwg.org/pub/pwg/ipp/new_TES/
The issues raised from the first Interoperability Testing Event are numbered 1.n in this document and have been incorporated into "IPP/1.0 Model and Semantics" [RFC2566] and the "IPP/1.0 Encoding and Transport" [RFC2565] documents. However, some of the discussion is left here in the Implementor's Guide to help understanding.
第一次互操作性测试事件引发的问题在本文件中编号为1.n，并已纳入“IPP/1.0模型和语义”[RFC2566]和“IPP/1.0编码和传输”[RFC2565]文件中。但是，在实现者指南中留下了一些讨论，以帮助理解。
The issues raised from the second Interoperability Testing Event are numbered 2.n in this document have been incorporated into "IPP/1.1 Model and Semantics" [RFC2911] and the "IPP/1.1 Encoding and Transport" [RFC2910] documents. However, some of the discussion is left here in the Implementor's Guide to help understanding.
第二次互操作性测试事件中提出的问题编号为2。本文件中的n已纳入“IPP/1.1模型和语义”[RFC2911]和“IPP/1.1编码和传输”[RFC2910]文件中。但是，在实现者指南中留下了一些讨论，以帮助理解。
The issues raised from the third Interoperability Testing Event are numbered 3.n in this document and are described in:
第三次互操作性测试事件中提出的问题在本文件中编号为3.n，描述如下：
ftp://ftp.pwg.org/pub/pwg/ipp/Issues/Issues-raised-at-Bake-
Off3.pdf
ftp://ftp.pwg.org/pub/pwg/ipp/Issues/Issues-raised-at-Bake-
Off3.pdf
ftp://ftp.pwg.org/pub/pwg/ipp/Issues/Issues-raised-at-Bake-
Off3.doc
ftp://ftp.pwg.org/pub/pwg/ipp/Issues/Issues-raised-at-Bake-
Off3.doc
ftp://ftp.pwg.org/pub/pwg/ipp/Issues/Issues-raised-at-Bake-
Off3.txt
ftp://ftp.pwg.org/pub/pwg/ipp/Issues/Issues-raised-at-Bake-
Off3.txt
The term "client" in IPP is intended to mean any client that issues IPP operation requests and accepts IPP operation responses, whether it be a desktop or a server. In other words, the term "client" does not just mean end-user clients, such as those associated with desktops.
IPP中的术语“客户机”是指发出IPP操作请求并接受IPP操作响应的任何客户机，无论是台式机还是服务器。换句话说，术语“客户端”不仅仅指终端用户客户端，例如与台式机相关联的客户端。
The term "IPP Printer" in IPP is intended to mean an object that accepts IPP operation requests and returns IPP operation responses, whether implemented in a server or a device. An IPP Printer object MAY, if implemented in a server, turn around and forward received jobs (and other requests) to other devices and print servers/services, either using IPP or some other protocol.
IPP中的术语“IPP打印机”意指接受IPP操作请求并返回IPP操作响应的对象，无论是在服务器还是在设备中实现。如果在服务器中实现，IPP打印机对象可以使用IPP或某些其他协议，将接收到的作业（和其他请求）翻转并转发到其他设备和打印服务器/服务。
3 IPP Operations
3独立发电商运营
This section corresponds to Section 3 "IPP Operations" in the IPP/1.1 Model and Semantics document [RFC2911].
本节与IPP/1.1模型和语义文档[RFC2911]中的第3节“IPP操作”相对应。
This section discusses semantics common to all operations.
本节讨论所有操作的通用语义。
Table 1 - Summary of Printer operation attributes that sender MUST supply
表1-发送方必须提供的打印机操作属性摘要
Printer Operations
打印机操作
Requests Responses Operation PJ, PU CJ GPA GJ PP, All Attributes VJ (O) (O) (R) (R) RP, Operations (R) PP (O+)
请求响应操作PJ、PU CJ GPA GJ PP、所有属性VJ（O）（O）（R）（R）RP、操作（R）PP（O+）
Operation parameters--REQUIRED to be supplied by the sender:
操作参数——要求发送方提供：
operation-id R R R R R R
操作id R
status-code R
状态代码R
request-id R R R R R R R
请求id R
version-number R R R R R R R
版本号R
Operation attributes--REQUIRED to be supplied by the sender:
操作属性--需要由发送方提供：
attributes- R R R R R R R charset
属性-R字符集
attributes- R R R R R R R natural-language
属性-自然语言
document-uri R
文档uri R
job-id*
工作id*
job-uri*
作业uri*
Printer Operations
打印机操作
Requests Responses
请求和响应
Operation PJ, PU CJ GPA GJ PP, All Attributes VJ (O) (O) (R) (R) RP, Operations (R) PP (O+) last-document
操作PJ，PU CJ GPA GJ PP，所有属性VJ（O）（O）（R）（R）RP，操作（R）PP（O+）最后文件
printer-uri R R R R R R
打印机uri R
Operation attributes--RECOMMENDED to be supplied by the sender:
操作属性--建议由发送方提供：
job-name R R R
工作名称R
requesting-user- R R R R R R name
正在请求用户-R名称
Legend:
图例：
PJ, VJ: Print-Job, Validate-Job PU: Print-URI CJ: Create-Job GPA: Get-Printer-Attributes GJ: Get-Jobs PP, RP, PP: Pause-Printer, Resume-Printer, Purge-Printer R indicates a REQUIRED operation that MUST be supported by the IPP object (Printer or Job). For attributes, R indicates that the attribute MUST be supported by the IPP object that supports the associated operation. O indicates an OPTIONAL operation or attribute that MAY be supported by the IPP object (Printer or Job). + indicates that this is not an IPP/1.0 feature, but is only a part of IPP/1.1 and future versions of IPP.
PJ，VJ:打印作业，验证作业PU:打印URI CJ:创建作业GPA:获取打印机属性GJ:获取作业PP，RP，PP:暂停打印机，恢复打印机，清除打印机R表示IPP对象（打印机或作业）必须支持的所需操作。对于属性，R表示支持关联操作的IPP对象必须支持该属性。O表示IPP对象（打印机或作业）可能支持的可选操作或属性表示这不是IPP/1.0功能，但只是IPP/1.1和IPP未来版本的一部分。
Table 2 - Summary of Printer operation attributes that sender MAY supply
表2-发送方可能提供的打印机操作属性摘要
Printer Operations
打印机操作
Requests Respon-ses Operation Attributes PJ, PU CJ GPA GJ PP, All VJ (O) (O) (R) (R) RP, Opera (R) PP tions (O+)
请求响应操作属性PJ、PU CJ GPA GJ PP、所有VJ（O）（O）（R）（R）RP、Opera（R）PP选项（O+）
Operation attributes--OPTIONAL to be supplied by the sender:
操作属性--发送方提供的可选属性：
status-message O
状态信息O
detailed-status- O message
详细状态-O消息
document-access- O** error
文档访问-O**错误
compression R R
压缩比
document-format R R R
文件格式
document-name O O
文件名O O
document-natural- O O language
文档自然语言
ipp-attribute- R R R fidelity
ipp属性-保真度
job-impressions O O O
工作印象
job-k-octets O O O
job-k-octets-O
job-media-sheets O O O
工作媒体单
Printer Operations
打印机操作
Requests Respon-ses Operation Attributes PJ, PU CJ GPA GJ PP, All VJ (O) (O) (R) (R) RP, Opera (R) PP tions (O+)
请求响应操作属性PJ、PU CJ GPA GJ PP、所有VJ（O）（O）（R）（R）RP、Opera（R）PP选项（O+）
limit R
极限R
message
消息
my-jobs R
我的工作
requested-attributes R R
请求的属性
which-jobs R
哪一份工作是R
Legend:
图例：
PJ, VJ: Print-Job, Validate-Job PU: Print-URI CJ: Create-Job GPA: Get-Printer-Attributes GJ: Get-Jobs PP, RP, PP: Pause-Printer, Resume-Printer, Purge-Printer R indicates a REQUIRED operation that MUST be supported by the IPP object (Printer or Job). For attributes, R indicates that the attribute MUST be supported by the IPP object that supports the associated operation. O indicates an OPTIONAL operation or attribute that MAY be supported by the IPP object (Printer or Job). + indicates that this is not an IPP/1.0 feature, but is only a part of IPP/1.1 and future versions of IPP. * "job-id" is REQUIRED only if used together with "printer-uri" to identify the target job; otherwise, "job-uri" is REQUIRED. ** "document-access-error" applies to the Print-URI response only.
PJ，VJ:打印作业，验证作业PU:打印URI CJ:创建作业GPA:获取打印机属性GJ:获取作业PP，RP，PP:暂停打印机，恢复打印机，清除打印机R表示IPP对象（打印机或作业）必须支持的所需操作。对于属性，R表示支持关联操作的IPP对象必须支持该属性。O表示IPP对象（打印机或作业）可能支持的可选操作或属性表示这不是IPP/1.0功能，但只是IPP/1.1和IPP未来版本的一部分。*仅当与“打印机uri”一起用于标识目标作业时，才需要“作业id”；否则，需要“作业uri”。*“文档访问错误”仅适用于打印URI响应。
Table 3 - Summary of Job operation attributes that sender MUST supply
表3-发送方必须提供的作业操作属性摘要
Job Operations
作业操作
Requests Responses Operation SD SU CJ GJA HJ All Attributes (O) (O) (R) (R) RJ, RJ Opera-(O+) tions
请求响应操作SD SU CJ GJA HJ所有属性（O）（O）（R）（R）RJ，RJ操作-（O+）选项
Operation parameters--REQUIRED to be supplied by the sender:
操作参数——要求发送方提供：
operation-id R R R R R
操作id R
status-code R
状态代码R
request-id R R R R R R
请求id R
version-number R R R R R R
版本号R
Operation attributes--REQUIRED to be supplied by the sender:
操作属性--需要由发送方提供：
attributes-charset R R R R R R
属性字符集
attributes-natural- R R R R R R language
自然属性-R语言
document-uri R
文档uri R
job-id* R R R R R
作业id*R
job-uri* R R R R R
作业uri*R
last-document R R
最后文件
printer-uri R R R R R
打印机uri R
Operation attributes--RECOMMENDED to be supplied by the sender:
操作属性--建议由发送方提供：
job-name
职务名称
Job Operations
作业操作
Requests Responses
请求和响应
Operation SD SU CJ GJA HJ All Attributes (O) (O) (R) (R) RJ, RJ Opera-(O+) tions
操作SD SU CJ GJA HJ所有属性（O）（O）（R）（R）RJ，RJ操作-（O+）选项
requesting-user- R R R R R name
正在请求用户-R名称
Legend:
图例：
SD: Send-Document SU: Send-URI CJ: Cancel-Job GJA: Get-Job-Attributes HJ, RJ, RJ: Hold-Job, Release-Job, Restart-Job R indicates a REQUIRED operation that MUST be supported by the IPP object (Printer or Job). For attributes, R indicates that the attribute MUST be supported by the IPP object that supports the associated operation. O indicates an OPTIONAL operation or attribute that MAY be supported by the IPP object (Printer or Job). + indicates that this is not an IPP/1.0 feature, but is only a part of IPP/1.1 and future versions of IPP. * "job-id" is REQUIRED only if used together with "printer-uri" to identify the target job; otherwise, "job-uri" is REQUIRED.
SD:Send Document SU:Send URI CJ:Cancel Job GJA:Get Job Attributes HJ、RJ、RJ:Hold Job、Release Job、Restart Job R表示IPP对象（打印机或作业）必须支持的所需操作。对于属性，R表示支持关联操作的IPP对象必须支持该属性。O表示IPP对象（打印机或作业）可能支持的可选操作或属性表示这不是IPP/1.0功能，但只是IPP/1.1和IPP未来版本的一部分。*仅当与“打印机uri”一起用于标识目标作业时，才需要“作业id”；否则，需要“作业uri”。
Table 4 - Summary of Job operation attributes that sender MAY supply
表4-发送方可能提供的作业操作属性摘要
Job Operations
作业操作
Requests Responses
请求和响应
Operation SD SU CJ GJA HJ, SD All Attributes (O) (O) (R) (R) RJ, (O) Opera-RJ tions (O+)
操作SD SU CJ GJA HJ，SD所有属性（O）（O）（R）（R）RJ，（O）操作RJ（O+）
Operation attributes--OPTIONAL to be supplied by the sender:
操作属性--发送方提供的可选属性：
status-message O
状态信息O
detailed-status- O message
详细状态-O消息
document-access- O** error
文档访问-O**错误
compression R R
压缩比
document-format R R
文件格式
document-name O O
文件名O O
document-natural- O O language
文档自然语言
ipp-attribute-fidelity
属性保真度
job-impressions
工作印象
job-k-octets
job-k-octets
job-media-sheets
工作媒体单
Job Operations
作业操作
Requests Responses
请求和响应
Operation SD SU CJ GJA HJ, SD All Attributes (O) (O) (R) (R) RJ, (O) Opera-RJ tions (O+)
操作SD SU CJ GJA HJ，SD所有属性（O）（O）（R）（R）RJ，（O）操作RJ（O+）
limit
限度
message O O O
留言
job-hold-until R
工作暂停至R
my-jobs
我的工作
requested- R attributes
请求的-R属性
which-jobs
哪些工作
Legend:
图例：
SD: Send-Document SU: Send-URI CJ: Cancel-Job GJA: Get-Job-Attributes HJ, RJ, RJ: Hold-Job, Release-Job, Restart-Job R indicates a REQUIRED operation that MUST be supported by the IPP object (Printer or Job). For attributes, R indicates that the attribute MUST be supported by the IPP object that supports the associated operation. O indicates an OPTIONAL operation or attribute that MAY be supported by the IPP object (Printer or Job). + indicates that this is not an IPP/1.0 feature, but is only a part of IPP/1.1 and future versions of IPP. * "job-id" is REQUIRED only if used together with "printer-uri" to identify the target job; otherwise, "job-uri" is REQUIRED. ** "document-access-error" applies to the Send-URI operation only
SD:Send Document SU:Send URI CJ:Cancel Job GJA:Get Job Attributes HJ、RJ、RJ:Hold Job、Release Job、Restart Job R表示IPP对象（打印机或作业）必须支持的所需操作。对于属性，R表示支持关联操作的IPP对象必须支持该属性。O表示IPP对象（打印机或作业）可能支持的可选操作或属性表示这不是IPP/1.0功能，但只是IPP/1.1和IPP未来版本的一部分。*仅当与“打印机uri”一起用于标识目标作业时，才需要“作业id”；否则，需要“作业uri”。*“文档访问错误”仅适用于发送URI操作
Table 5 - Printer operation response attributes
表5-打印机操作响应属性
Printer Operations
打印机操作
Response
回答
Operation PJ (R) VJ (R) PU (O) CJ (O) GPA GJ (R) PP, Attributes SD (O) SU (O) (R) RP, PP (O+)
行动PJ（R）VJ（R）PU（O）CJ（O）GPA GJ（R）PP，属性SD（O）SU（O）（R）RP，PP（O+）
job-uri R R R
作业uri
job-id R R R
作业id R
job-state R R R
作业状态R
job-state- R+ R+ R+ reasons
作业状态-R+R+R+原因
number-of- O O O intervening-jobs
干预作业的数量-O
document- O access-error+
文档-O访问错误+
Legend:
图例：
PJ, SJ: Print-Job, Send-Document VJ: Validate-Job PU, SU: Print-URI, Send-URI CJ: Create-Job GPA: Get-Printer-Attributes GJ: Get-Jobs PP, RP, PP: Pause-Printer, Resume-Printer, Purge-Printer R indicates a REQUIRED operation that MUST be supported by the IPP object (Printer or Job). For attributes, R indicates that the attribute MUST be supported by the IPP object that supports the associated operation. O indicates an OPTIONAL operation or attribute that MAY be supported by the IPP object (Printer or Job).
PJ，SJ:打印作业，发送文档VJ:验证作业PU，SU:打印URI，发送URI CJ:创建作业GPA:获取打印机属性GJ:获取作业PP，RP，PP:暂停打印机，恢复打印机，清除打印机R表示IPP对象（打印机或作业）必须支持的所需操作。对于属性，R表示支持关联操作的IPP对象必须支持该属性。O表示IPP对象（打印机或作业）可能支持的可选操作或属性。
This section suggests the steps and error checks that an IPP object MAY perform when processing requests and returning responses. An IPP object MAY perform some or all of the error checks. However, some
本节介绍IPP对象在处理请求和返回响应时可能执行的步骤和错误检查。IPP对象可以执行部分或全部错误检查。然而，一些
implementations MAY choose to be more forgiving than the error checks shown here, in order to be able to accept requests from non-conforming clients. Not performing all of these error checks is a so-called "forgiving" implementation. On the other hand, clients that successfully submit requests to IPP objects that do perform all the error checks will be more likely to be able to interoperate with other IPP object implementations. Thus an implementer of an IPP object needs to decide whether to be a "forgiving" or a "strict" implementation. Therefore, the error status codes returned may differ between implementations. Consequentially, client SHOULD NOT expect exactly the error code processing described in this section.
实现可能会选择比此处显示的错误检查更宽容，以便能够接受来自不一致客户机的请求。不执行所有这些错误检查就是所谓的“宽恕”实现。另一方面，成功地向执行所有错误检查的IPP对象提交请求的客户端更有可能与其他IPP对象实现进行互操作。因此，IPP对象的实现者需要决定是“宽容”还是“严格”实现。因此，返回的错误状态代码可能在不同的实现中有所不同。因此，客户机不应该完全期待本节中描述的错误代码处理。
When an IPP object receives a request, the IPP object either accepts or rejects the request. In order to determine whether or not to accept or reject the request, the IPP object SHOULD execute the following steps. The order of the steps may be rearranged and/or combined, including making one or multiple passes over the request.
当IPP对象收到请求时，IPP对象接受或拒绝该请求。为了确定是否接受或拒绝请求，IPP对象应执行以下步骤。可以重新排列和/或组合步骤的顺序，包括对请求进行一次或多次传递。
A client MUST supply requests that would pass all of the error checks indicated here in order to be a conforming client. Therefore, a client SHOULD supply requests that are conforming, in order to avoid being rejected by some IPP object implementations and/or risking different semantics by different implementations of forgiving implementations. For example, a forgiving implementation that accepts multiple occurrences of the same attribute, rather than rejecting the request might use the first occurrences, while another might use the last occurrence. Thus such a non-conforming client would get different results from the two forgiving implementations.
为了成为合格的客户，客户必须提供通过此处所示所有错误检查的请求。因此，客户机应提供符合要求的请求，以避免被某些IPP对象实现拒绝和/或因原谅实现的不同实现而冒不同语义的风险。例如，接受同一属性多次出现而不是拒绝请求的宽容实现可能使用第一次出现，而另一个实现可能使用最后一次出现。因此，这样一个不一致的客户机将从两个宽容的实现中得到不同的结果。
In the following, processing continues step by step until a "RETURNS the xxx status code ..." statement is encountered. Error returns are indicated by the verb: "REJECTS". Since clients have difficulty getting the status code before sending all of the document data in a Print-Job request, clients SHOULD use the Validate-Job operation before sending large documents to be printed, in order to validate whether the IPP Printer will accept the job or not.
在下文中，处理将逐步继续，直到遇到“返回xxx状态代码…”语句。错误返回由动词“拒绝”表示。由于客户端在发送打印作业请求中的所有文档数据之前很难获取状态代码，因此客户端应在发送要打印的大型文档之前使用“验证作业”操作，以验证IPP打印机是否接受作业。
It is assumed that security authentication and authorization has already taken place at a lower layer.
假设安全认证和授权已经在较低的一层进行。
This section is intended to apply to all operations. The next section contains the additional steps for the Print-Job, Validate-Job, Print-URI, Create-Job, Send-Document, and Send-URI operations that create jobs, adds documents, and validates jobs.
本节适用于所有操作。下一节包含打印作业、验证作业、打印URI、创建作业、发送文档和发送URI操作的附加步骤，这些操作用于创建作业、添加文档和验证作业。
IIG Sect # Flow IPP error status codes
---------- ---- ----------------------
|
v err
3.1.2.1.1 <Validate version> --> server-error-version-not-
supported
ok|
v err
3.1.2.1.2 <Validate operation> --> server-error-operation-not-
supported
ok|
v err
3.1.2.1.4.1- <Validate presence> --> client-error-bad-request
3.1.2.1.4.2 <of attributes>
ok|
v err
3.1.2.1.4.3 <Validate presence> --> client-error-bad-request
<of operation attr>
ok|
v err
3.1.2.1.5 <Validate values of> --> client-error-bad-request
<operation attrs> client-error-request-value-
too-long
<(length, tag, range,>
<multi-value)>
ok|
v err
3.1.2.1.5 <Validate values> --> client-error-bad-request
<with supported values> client-error-charset-not-
supported
ok| client-error-attributes-or-
values-
| not-supported
v err
3.1.2.1.6 <Validate optionally> --> client-error-bad-request
<operation attr> client-error-natural-language-
not-supported
| client-error-request-value-
too-long
| client-error-attributes-or-
values-not-supported
IIG Sect # Flow IPP error status codes
---------- ---- ----------------------
|
v err
3.1.2.1.1 <Validate version> --> server-error-version-not-
supported
ok|
v err
3.1.2.1.2 <Validate operation> --> server-error-operation-not-
supported
ok|
v err
3.1.2.1.4.1- <Validate presence> --> client-error-bad-request
3.1.2.1.4.2 <of attributes>
ok|
v err
3.1.2.1.4.3 <Validate presence> --> client-error-bad-request
<of operation attr>
ok|
v err
3.1.2.1.5 <Validate values of> --> client-error-bad-request
<operation attrs> client-error-request-value-
too-long
<(length, tag, range,>
<multi-value)>
ok|
v err
3.1.2.1.5 <Validate values> --> client-error-bad-request
<with supported values> client-error-charset-not-
supported
ok| client-error-attributes-or-
values-
| not-supported
v err
3.1.2.1.6 <Validate optionally> --> client-error-bad-request
<operation attr> client-error-natural-language-
not-supported
| client-error-request-value-
too-long
| client-error-attributes-or-
values-not-supported
Every request and every response contains the "version-number" attribute. The value of this attribute is the major and minor version number of the syntax and semantics that the client and IPP object is using, respectively. The "version-number" attribute
每个请求和每个响应都包含“版本号”属性。该属性的值是客户端和IPP对象分别使用的语法和语义的主要版本号和次要版本号。“版本号”属性
remains in a fixed position across all future versions so that all clients and IPP object that support future versions can determine which version is being used. The IPP object checks to see if the major version number supplied in the request is supported. If not, the Printer object REJECTS the request and RETURNS the 'server-error-version-not-supported' status code in the response. The IPP object returns in the "version-number" response attribute the major and minor version for the error response. Thus the client can learn at least one major and minor version that the IPP object supports. The IPP object is encouraged to return the closest version number to the one supplied by the client.
在所有未来版本中保持固定位置，以便支持未来版本的所有客户端和IPP对象都可以确定正在使用的版本。IPP对象检查请求中提供的主版本号是否受支持。如果不支持，打印机对象将拒绝请求，并在响应中返回“服务器错误版本不支持”状态代码。IPP对象在“版本号”响应属性中返回错误响应的主要版本和次要版本。因此，客户机可以了解IPP对象支持的至少一个主要和次要版本。建议IPP对象返回与客户端提供的版本号最接近的版本号。
The checking of the minor version number is implementation dependent, however if the client-supplied minor version is explicitly supported, the IPP object MUST respond using that identical minor version number. If the major version number matches, but the minor version number does not, the Printer SHOULD accept and attempt to process the request, or MAY reject the request and return the 'server-error-version-not-supported' status code. In all cases, the Printer MUST return the nearest version number that it supports. For example, suppose that an IPP/1.2 Printer supports versions '1.1' and '1.2'. The following responses are conforming:
次要版本号的检查取决于实现，但是如果明确支持客户端提供的次要版本，则IPP对象必须使用相同的次要版本号进行响应。如果主版本号匹配，但次版本号不匹配，则打印机应接受并尝试处理该请求，或者可能拒绝该请求并返回“服务器错误版本不受支持”状态代码。在所有情况下，打印机必须返回其支持的最接近的版本号。例如，假设IPP/1.2打印机支持版本“1.1”和“1.2”。以下回答符合要求：
Table 6 - Examples of validating IPP version
表6-验证IPP版本的示例
Client supplies Printer Accept Request? Printer returns
客户供应打印机是否接受请求？打印机返回
1.0 yes (SHOULD) 1.1
1.0 是（应该）1.1
1.0 no (SHOULD NOT) 1.1
1.0 否（不应）1.1
1.1 yes (MUST) 1.1
1.1 是（必须）1.1
1.2 yes (MUST) 1.2
1.2 是（必须）1.2
1.3 yes (SHOULD) 1.2
1.3 是（应该）1.2
1.3 no (SHOULD NOT) 1.2
1.3 否（不应）1.2
It is advantageous for Printers to support both IPP/1.1 and IPP/1.0, so that they can interoperate with either client implementations. Some implementations may allow an Administrator to explicitly disable support for one or the other by setting the "ipp-versions-supported" Printer description attribute.
打印机同时支持IPP/1.1和IPP/1.0是有利的，这样它们就可以与任一客户端实现进行互操作。某些实现可能允许管理员通过设置“支持的ipp版本”打印机描述属性来明确禁用对其中一个的支持。
Likewise, it is advantageous for clients to support both versions to allow interoperability with new and legacy Printers.
同样，客户机支持这两个版本以允许与新打印机和旧打印机的互操作性也是有利的。
The Printer object checks to see if the "operation-id" attribute supplied by the client is supported as indicated in the Printer object's "operations-supported" attribute. If not, the Printer REJECTS the request and returns the 'server-error-operation-not-supported' status code in the response.
打印机对象检查客户端提供的“操作id”属性是否受支持，如打印机对象的“支持的操作”属性所示。否则，打印机将拒绝请求并在响应中返回“服务器错误操作不受支持”状态代码。
The Printer object SHOULD NOT check to see if the "request-id" attribute supplied by the client is in range: between 1 and 2**31 - 1 (inclusive), but copies all 32 bits.
打印机对象不应检查客户端提供的“请求id”属性是否在范围内：1到2**31-1（包括1），而是复制所有32位。
Note: The "version-number", "operation-id", and the "request-id" parameters are in fixed octet positions in the IPP/1.1 encoding. The "version-number" parameter will be the same fixed octet position in all versions of the protocol. These fields are validated before proceeding with the rest of the validation.
注：“版本号”、“操作id”和“请求id”参数在IPP/1.1编码中处于固定的八位字节位置。“版本号”参数在所有版本的协议中都是相同的固定八位字节位置。这些字段将在继续进行其余验证之前进行验证。
The order of the following validation steps depends on implementation.
以下验证步骤的顺序取决于实现。
Client requests and IPP object responses contain attribute groups that Section 3 requires to be present and in a specified order. An IPP object verifies that the attribute groups are present and in the correct order in requests supplied by clients (attribute groups without an * in the following tables).
客户端请求和IPP对象响应包含第3节要求以指定顺序出现的属性组。IPP对象验证属性组是否存在，以及在客户端提供的请求中的顺序是否正确（下表中没有*的属性组）。
If an IPP object receives a request with (1) required attribute groups missing, or (2) the attributes groups are out of order, or (3) the groups are repeated, the IPP object REJECTS the request and RETURNS the 'client-error-bad-request' status code. For example, it is an error for the Job Template Attributes group to occur before the Operation Attributes group, for the Operation Attributes group to be omitted, or for an attribute group to occur more than once, except in the Get-Jobs response.
如果IPP对象收到的请求（1）缺少必需的属性组，或（2）属性组出现故障，或（3）组重复，IPP对象将拒绝该请求并返回“客户端错误错误请求”状态代码。例如，作业模板属性组出现在操作属性组之前、省略操作属性组或属性组出现多次（Get Jobs响应中除外）都是错误的。
Since this kind of attribute group error is most likely to be an error detected by a client developer rather than by a customer, the IPP object NEED NOT return an indication of which attribute group was
由于这种类型的属性组错误很可能是由客户端开发人员而不是客户检测到的错误，因此IPP对象不需要返回指定了哪个属性组的指示
in error in either the Unsupported Attributes group or the Status Message. Also, the IPP object NEED NOT find all attribute group errors before returning this error.
在不支持的属性组或状态消息中出错。此外，IPP对象在返回此错误之前不需要查找所有属性组错误。
Future attribute groups may be added to the specification at the end of requests just before the Document Content and at the end of response, except for the Get-Jobs response, where it maybe there or before the first job attributes returned. If an IPP object receives an unknown attribute group in these positions, it ignores the entire group, rather than returning an error, since that group may be a new group in a later minor version of the protocol that can be ignored. (If the new attribute group cannot be ignored without confusing the client, the major version number would have been increased in the protocol document and in the request). If the unknown group occurs in a different position, the IPP object REJECTS the request and RETURNS the 'client-error-bad-request' status code.
未来的属性组可能会在文档内容之前的请求结束时和响应结束时添加到规范中，但Get Jobs响应除外，它可能在那里或在返回第一个作业属性之前。如果IPP对象在这些位置接收到未知属性组，它将忽略整个组，而不是返回错误，因为该组可能是协议较新次要版本中可以忽略的新组。（如果在不混淆客户端的情况下无法忽略新属性组，则协议文档和请求中的主版本号会增加）。如果未知组出现在不同位置，IPP对象将拒绝请求并返回“客户端错误错误请求”状态代码。
Clients also ignore unknown attribute groups returned in a response.
客户端还忽略响应中返回的未知属性组。
Note: By validating that requests are in the proper form, IPP objects force clients to use the proper form which, in turn, increases the chances that customers will be able to use such clients from multiple vendors with IPP objects from other vendors.
注意：通过验证请求的格式是否正确，IPP对象将强制客户端使用正确的格式，这反过来又增加了客户使用多个供应商的此类客户端和其他供应商的IPP对象的机会。
3.1.2.1.4.3 Validate the presence of a single occurrence of required Operation attributes
3.1.2.1.4.3 验证是否存在所需操作属性的单一匹配项
Client requests and IPP object responses contain Operation attributes that [RFC2911] Section 3 requires to be present. Attributes within a group may be in any order, except for the ordering of target, charset, and natural languages attributes. These attributes MUST be first, and MUST be supplied in the following order: charset, natural language, and then target. An IPP object verifies that the attributes that Section 4 requires to be supplied by the client have been supplied in the request (attributes without an * in the following tables). An asterisk (*) indicates groups and Operation attributes that the client may omit in a request or an IPP object may omit in a response.
客户端请求和IPP对象响应包含[RFC2911]第3节要求存在的操作属性。组中的属性可以是任何顺序，但目标、字符集和自然语言属性的顺序除外。这些属性必须是第一个，并且必须按照以下顺序提供：字符集、自然语言，然后是目标。IPP对象验证第4节要求客户端提供的属性是否已在请求中提供（下表中没有*的属性）。星号（*）表示客户端可能在请求中忽略的组和操作属性，或IPP对象可能在响应中忽略的组和操作属性。
If an IPP object receives a request with required attributes missing or repeated from a group or in the wrong position, the behavior of the IPP object is IMPLEMENTATION DEPENDENT. Some of the possible implementations are:
如果IPP对象从组或错误位置接收到缺少或重复所需属性的请求，则IPP对象的行为取决于实现。一些可能的实施方式包括：
REJECTS the request and RETURNS the 'client-error-bad-request' status code
拒绝请求并返回“客户端错误错误请求”状态代码
accepts the request and uses the first occurrence of the attribute no matter where it is
接受请求并使用属性的第一个匹配项，无论它位于何处
accepts the request and uses the last occurrence of the attribute no matter where it is
接受请求并使用属性的最后一次出现，无论它在哪里
accept the request and assume some default value for the missing attribute
接受请求并为缺少的属性假定一些默认值
Therefore, client MUST send conforming requests, if they want to receive the same behavior from all IPP object implementations. For example, it is an error for the "attributes-charset" or "attributes-natural-language" attribute to be omitted in any operation request, or for an Operation attribute to be supplied in a Job Template group or a Job Template attribute to be supplied in an Operation Attribute group in a create request. It is also an error to supply the "attributes-charset" attribute twice.
因此，如果客户端希望从所有IPP对象实现接收相同的行为，则必须发送一致性请求。例如，在任何操作请求中省略“attributes charset”或“attributes natural language”属性，或者在创建请求中在作业模板组中提供操作属性，或者在作业属性组中提供作业模板属性，都是错误的。两次提供“attributes charset”属性也是错误的。
Since these kinds of attribute errors are most likely to be detected by a client developer rather than by a customer, the IPP object NEED NOT return an indication of which attribute was in error in either the Unsupported Attributes group or the Status Message. Also, the IPP object NEED NOT find all attribute errors before returning this error.
由于这些类型的属性错误最有可能由客户端开发人员而不是客户检测到，因此IPP对象不需要返回不受支持的属性组或状态消息中哪个属性出错的指示。此外，IPP对象在返回此错误之前不需要查找所有属性错误。
The following tables list all the attributes for all the operations by attribute group in each request and each response. The order of the groups is the order that the client supplies the groups as specified in [RFC2911] Section 3. The order of the attributes within a group is arbitrary, except as noted for some of the special operation attributes (charset, natural language, and target). The tables below use the following notation:
下表按属性组列出了每个请求和每个响应中所有操作的所有属性。组的顺序是指客户按照[RFC2911]第3节的规定提供组的顺序。组中属性的顺序是任意的，但某些特殊操作属性（字符集、自然语言和目标）除外。下表使用以下符号：
R indicates a REQUIRED attribute or operation that an IPP object MUST support O indicates an OPTIONAL attribute or operation that an IPP object NEED NOT support * indicates that a client MAY omit the attribute in a request and that an IPP object MAY omit the attribute in a response. The absence of an * means that a client MUST supply the attribute in a request and an IPP object MUST supply the attribute in a response. + indicates that this is not a IPP/1.0 operation, but is only a part of IPP/1.1 and future versions of IPP.
R表示IPP对象必须支持的必需属性或操作O表示IPP对象不需要支持的可选属性或操作*表示客户端可以在请求中省略该属性，而IPP对象可以在响应中省略该属性。缺少*表示客户端必须在请求中提供属性，而IPP对象必须在响应中提供属性表示这不是IPP/1.0操作，而只是IPP/1.1和IPP未来版本的一部分。
Operation Requests
操作请求
The tables below show the attributes in their proper attribute groups for operation requests:
下表显示了操作请求的相应属性组中的属性：
Note: All operation requests contain "version-number", "operation-id", and "request-id" parameters.
注意：所有操作请求都包含“版本号”、“操作id”和“请求id”参数。
Print-Job Request (R): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) printer-uri (R) requesting-user-name (R*) job-name (R*) ipp-attribute-fidelity (R*) document-name (R*) document-format (R*) document-natural-language (O*) compression (R*) job-k-octets (O*) job-impressions (O*) job-media-sheets (O*) Group 2: Job Template Attributes (R*) <Job Template attributes> (O*) (see [RFC2911] Section 4.2) Group 3: Document Content (R) <document content>
打印作业请求（R）：第1组：操作属性（R）属性字符集（R）属性自然语言（R）打印机uri（R）请求用户名（R*）作业名称（R*）ipp属性保真度（R*）文档名称（R*）文档格式（R*）文档自然语言（O*）压缩（R*）作业k八位字节（O*）作业印象（O*）作业介质表（O*）第2组：作业模板属性（R*）<作业模板属性>（O*）（参见[RFC2911]第4.2节）第3组：文档内容（R）<文档内容>
Validate-Job Request (R): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) printer-uri (R) requesting-user-name (R*) job-name (R*) ipp-attribute-fidelity (R*) document-name (R*) document-format (R*) document-natural-language (O*) compression (R*) job-k-octets (O*) job-impressions (O*) job-media-sheets (O*) Group 2: Job Template Attributes (R*) <Job Template attributes> (O*) (see [RFC2911] Section 4.2)
验证作业请求（R）：组1：操作属性（R）属性字符集（R）属性自然语言（R）打印机uri（R）请求用户名（R*）作业名称（R*）ipp属性保真度（R*）文档名称（R*）文档格式（R*）文档自然语言（O*）压缩（R*）作业k八位字节（O*）作业印象（O*）作业介质表（O*）第2组：作业模板属性（R*）<作业模板属性>（O*）（参见[RFC2911]第4.2节）
Print-URI Request (O): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) printer-uri (R) document-uri (R) requesting-user-name (R*) job-name (R*) ipp-attribute-fidelity (R*) document-name (R*) document-format (R*) document-natural-language (O*) compression (R*) job-k-octets (O*) job-impressions (O*) job-media-sheets (O*) Group 2: Job Template Attributes (R*) <Job Template attributes> (O*) (see (see [RFC2911] Section 4.2)
打印URI请求（O）：组1：操作属性（R）属性字符集（R）属性自然语言（R）打印机URI（R）文档URI（R）请求用户名（R*）作业名称（R*）ipp属性保真度（R*）文档名称（R*）文档格式（R*）文档自然语言（O*）压缩（R*）作业k八位组（O*）作业印象（O*）作业介质表（O*）第2组：作业模板属性（R*）<作业模板属性>（O*）（参见[RFC2911]第4.2节）
Create-Job Request (O): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) printer-uri (R) requesting-user-name (R*) job-name (R*) ipp-attribute-fidelity (R*) job-k-octets (O*) job-impressions (O*) job-media-sheets (O*) Group 2: Job Template Attributes (R*) <Job Template attributes> (O*) (see (see [RFC2911] Section 4.2)
创建作业请求（O）：第1组：操作属性（R）属性字符集（R）属性自然语言（R）打印机uri（R）请求用户名（R*）作业名称（R*）ipp属性保真度（R*）作业k八位字节（O*）作业印象（O*）作业媒体表（O*）第2组：作业模板属性（R*）<作业模板属性>（O*）（请参见[RFC2911]第4.2节）
Get-Printer-Attributes Request (R): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) printer-uri (R) requesting-user-name (R*) requested-attributes (R*) document-format (R*)
获取打印机属性请求（R）：组1：操作属性（R）属性字符集（R）属性自然语言（R）打印机uri（R）请求用户名（R*）请求的属性（R*）文档格式（R*）
Get-Jobs Request (R): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R)
获取作业请求（R）：组1：操作属性（R）属性字符集（R）属性自然语言（R）
printer-uri (R) requesting-user-name (R*) limit (R*) requested-attributes (R*) which-jobs (R*) my-jobs (R*)
打印机uri（R）请求用户名（R*）限制（R*）请求属性（R*）哪些作业（R*）我的作业（R*）
Send-Document Request (O): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) (printer-uri & job-id) | job-uri (R) last-document (R) requesting-user-name (R*) document-name (R*) document-format (R*) document-natural-language (O*) compression (R*) Group 2: Document Content (R*) <document content>
发送文档请求（O）：第1组：操作属性（R）属性字符集（R）属性自然语言（R）（打印机uri和作业id）|作业uri（R）最后一个文档（R）请求用户名（R*）文档名称（R*）文档格式（R*）文档自然语言（O*）压缩（R*）第2组：文档内容（R*）<文档内容>
Send-URI Request (O): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) (printer-uri & job-id) | job-uri (R) last-document (R) document-uri (R) requesting-user-name (R*) document-name (R*) document-format (R*) document-natural-language (O*) compression (R*)
发送URI请求（O）：第1组：操作属性（R）属性字符集（R）属性自然语言（R）（打印机URI和作业id）|作业URI（R）最后一个文档（R）文档URI（R）请求用户名（R*）文档名（R*）文档格式（R*）文档自然语言（O*）压缩（R*）
Cancel-Job Request (R): Release-Job Request (O+): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) (printer-uri & job-id) | job-uri (R) requesting-user-name (R*) message (O*)
取消作业请求（R）：释放作业请求（O+）：组1：操作属性（R）属性字符集（R）属性自然语言（R）（打印机uri和作业id）|作业uri（R）请求用户名（R*）消息（O*）
Get-Job-Attributes Request (R): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) (printer-uri & job-id) | job-uri (R) requesting-user-name (R*) requested-attributes (R*)
获取作业属性请求（R）：组1：操作属性（R）属性字符集（R）属性自然语言（R）（打印机uri和作业id）|作业uri（R）请求用户名（R*）请求的属性（R*）
Pause-Printer Request (O+): Resume-Printer Request (O+): Purge-Printer Request (O+): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) printer-uri (R) requesting-user-name (R*)
暂停打印机请求（O+）：恢复打印机请求（O+）：清除打印机请求（O+）：组1:操作属性（R）属性字符集（R）属性自然语言（R）打印机uri（R）请求用户名（R*）
Hold-Job Request (O+): Restart-Job Request (O+): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) (printer-uri & job-id) | job-uri (R) requesting-user-name (R*) job-hold-until (R*) message (O*)
保留作业请求（O+）：重新启动作业请求（O+）：组1：操作属性（R）属性字符集（R）属性自然语言（R）（打印机uri和作业id）|作业uri（R）请求用户名（R*）作业保留直到（R*）消息（O*）
Operation Responses
操作响应
The tables below show the response attributes in their proper attribute groups for responses.
下表显示了响应的相应属性组中的响应属性。
Note: All operation responses contain "version-number", "status-code", and "request-id" parameters.
注意：所有操作响应都包含“版本号”、“状态代码”和“请求id”参数。
Print-Job Response (R): Create-Job Response (O): Send-Document Response (O): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) status-message (O*) detailed-status-message (O*) Group 2: Unsupported Attributes (R*) (see Note 3) n <unsupported attributes> (R*) Group 3: Job Object Attributes(R*) (see Note 2) job-uri (R) job-id (R)
打印作业响应（R）：创建作业响应（O）：发送文档响应（O）：第1组：操作属性（R）属性字符集（R）属性自然语言（R）状态消息（O*）详细状态消息（O*）第2组：不支持的属性（R*）（见注3）n<不支持的属性>（R*）第3组：作业对象属性（R*）（见注2）作业uri（R）作业id（R）
job-state (R) job-state-reasons (O* | R+) job-state-message (O*) number-of-intervening-jobs (O*)
作业状态（R）作业状态原因（O*| R+）作业状态消息（O*）干预作业数（O*）
Validate-Job Response (R):
Cancel-Job Response (R):
Hold-Job Response (O+):
Release-Job Response (O+):
Restart-Job Response (O+):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 3)
<unsupported attributes> (R*)
Validate-Job Response (R):
Cancel-Job Response (R):
Hold-Job Response (O+):
Release-Job Response (O+):
Restart-Job Response (O+):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 3)
<unsupported attributes> (R*)
Print-URI Response (O): Send-URI Response (O): Group 1: Operation Attributes (R) attributes-charset (R) attributes-natural-language (R) status-message (O*) detailed-status-message (O*) document-access-error (O*) Group 2: Unsupported Attributes (R*) (see Note 3) <unsupported attributes> (R*) Group 3: Job Object Attributes(R*) (see Note 2) job-uri (R) job-id (R) job-state (R) job-state-reasons (O* | R+) job-state-message (O*) number-of-intervening-jobs (O*)
打印URI响应（O）：发送URI响应（O）：第1组：操作属性（R）属性字符集（R）属性自然语言（R）状态消息（O*）详细状态消息（O*）文档访问错误（O*）第2组：不支持的属性（R*）（见注3）<不支持的属性>（R*）第3组：作业对象属性（R*）（见注2）作业URI（R） 作业id（R）作业状态（R）作业状态原因（O*| R+）作业状态消息（O*）干预作业数（O*）
Get-Printer-Attributes Response (R):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Group 3: Printer Object Attributes(R*) (see Note 2)
<requested attributes> (R*)
Get-Printer-Attributes Response (R):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Group 3: Printer Object Attributes(R*) (see Note 2)
<requested attributes> (R*)
Get-Jobs Response (R):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Group 3: Job Object Attributes(R*) (see Note 2, 5)
<requested attributes> (R*)
Get-Jobs Response (R):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Group 3: Job Object Attributes(R*) (see Note 2, 5)
<requested attributes> (R*)
Get-Job-Attributes Response (R):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Group 3: Job Object Attributes(R*) (see Note 2)
<requested attributes> (R*)
Get-Job-Attributes Response (R):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Group 3: Job Object Attributes(R*) (see Note 2)
<requested attributes> (R*)
Pause-Printer Response (O+):
Resume-Printer Response (O+):
Purge-Printer Response (O+):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Pause-Printer Response (O+):
Resume-Printer Response (O+):
Purge-Printer Response (O+):
Group 1: Operation Attributes (R)
attributes-charset (R)
attributes-natural-language (R)
status-message (O*)
detailed-status-message (O*)
Group 2: Unsupported Attributes (R*) (see Note 4)
<unsupported attributes> (R*)
Note 2 - the Job Object Attributes and Printer Object Attributes are returned only if the IPP object returns one of the success status codes.
注2-仅当IPP对象返回一个成功状态代码时，才会返回作业对象属性和打印机对象属性。
Note 3 - the Unsupported Attributes Group is present only if the client included some Operation and/or Job Template attributes or values that the Printer doesn't support whether a success or an error return.
注意3-仅当客户端包含打印机不支持的某些操作和/或作业模板属性或值（无论返回成功还是错误），不支持的属性组才会出现。
Note 4 - the Unsupported Attributes Group is present only if the client included some Operation attributes that the Printer doesn't support whether a success or an error return.
注意4-仅当客户端包含打印机不支持的某些操作属性时，不支持的属性组才存在，无论返回成功还是错误。
Note 5: for the Get-Jobs operation the response contains a separate Job Object Attributes group 3 to N containing requested-attributes for each job object in the response.
注意5：对于Get Jobs操作，响应包含一个单独的作业对象属性组3到N，其中包含响应中每个作业对象的请求属性。
An IPP object validates the values supplied by the client of the REQUIRED Operation attribute that the IPP object MUST support. The next section specifies the validation of the values of the OPTIONAL Operation attributes that IPP objects MAY support.
IPP对象验证客户端提供的IPP对象必须支持的必需操作属性的值。下一节指定IPP对象可能支持的可选操作属性值的验证。
The IPP object performs the following syntactic validation checks of each Operation attribute value:
IPP对象对每个操作属性值执行以下语法验证检查：
a) that the length of each Operation attribute value is correct for the attribute syntax tag supplied by the client according to [RFC2911] Section 4.1,
a) 根据[RFC2911]第4.1节，每个操作属性值的长度对于客户端提供的属性语法标记是正确的，
b) that the attribute syntax tag is correct for that Operation attribute according to [RFC2911] Section 3,
b) 根据[RFC2911]第3节，属性语法标记对于该操作属性是正确的，
c) that the value is in the range specified for that Operation attribute according to [RFC2911] Section 3,
c) 根据[RFC2911]第3节，该值在为该操作属性指定的范围内，
d) that multiple values are supplied by the client only for operation attributes that are multi-valued, i.e., that are 1setOf X according to [RFC2911] Section 3.
d) 客户仅为多值操作属性提供多个值，即根据[RFC2911]第3节为1setOf X。
If any of these checks fail, the IPP object REJECTS the request and RETURNS the 'client-error-bad-request' or the 'client-error-request-value-too-long' status code. Since such an error is most likely to be an error detected by a client developer, rather than by an end-user, the IPP object NEED NOT return an indication of which attribute had the error in either the Unsupported Attributes Group or the Status Message. The description for each of these syntactic checks is explicitly expressed in the first IF statement in the following table.
如果其中任何检查失败，IPP对象将拒绝请求并返回“客户端错误错误请求”或“客户端错误请求值过长”状态代码。由于此类错误很可能是由客户端开发人员而不是最终用户检测到的错误，因此IPP对象无需返回指示，说明在不受支持的属性组或状态消息中哪个属性存在错误。下表中的第一个IF语句明确表示了这些语法检查的描述。
In addition, the IPP object checks each Operation attribute value against some Printer object attribute or some hard-coded value if there is no "xxx-supported" Printer object attribute defined. If its value is not among those supported or is not in the range supported, then the IPP object REJECTS the request and RETURNS the error status code indicated in the table by the second IF statement. If the value of the Printer object's "xxx-supported" attribute is 'no-value' (because the system administrator hasn't configured a value), the check always fails.
此外，如果没有定义“支持xxx”的打印机对象属性，IPP对象将根据某些打印机对象属性或某些硬编码值检查每个操作属性值。如果其值不在支持的范围内或不在支持的范围内，则IPP对象将拒绝请求并返回表中第二条If语句指示的错误状态代码。如果打印机对象的“支持xxx”属性的值为“无值”（因为系统管理员尚未配置值），则检查始终失败。
-----------------------------------------------
-----------------------------------------------
attributes-charset (charset)
属性字符集（字符集）
IF NOT a single non-empty 'charset' value, REJECT/RETURN 'client-error-bad-request'.
如果不是单个非空的“字符集”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 63 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于63个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT in the Printer object's "charset-supported" attribute, REJECT/RETURN "client-error-charset-not-supported".
如果不在打印机对象的“支持的字符集”属性中，请拒绝/返回“不支持的客户端错误字符集”。
attributes-natural-language(naturalLanguage)
属性自然语言（自然语言）
IF NOT a single non-empty 'naturalLanguage' value, REJECT/RETURN 'client-error-bad-request'.
如果没有一个非空的“naturalLanguage”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 63 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于63个八位字节，则拒绝/返回“客户端错误请求值太长”。
ACCEPT the request even if not a member of the set in the Printer object's "generated-natural-language-supported" attribute. If the supplied value is not a member of the Printer object's "generated-natural-language-supported" attribute, use the Printer object's "natural-language- configured" value.
即使不是打印机对象“支持生成的自然语言”属性中的集合成员，也接受请求。如果提供的值不是打印机对象的“支持生成的自然语言”属性的成员，请使用打印机对象的“自然语言-配置”值。
requesting-user-name
请求用户名
IF NOT a single 'name' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“name”值，则拒绝/返回“client error bad request”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF the IPP object can obtain a better-authenticated name, use it instead.
如果IPP对象可以获得更好的身份验证名称，请改用它。
job-name(name)
工作名称（名称）
IF NOT a single 'name' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“name”值，则拒绝/返回“client error bad request”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT supplied by the client, the Printer object creates a name from the document-name or document-uri.
如果不是由客户机提供，打印机对象将根据文档名或文档uri创建名称。
document-name (name)
文件名（名称）
IF NOT a single 'name' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“name”值，则拒绝/返回“client error bad request”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
ipp-attribute-fidelity (boolean)
ipp属性保真度（布尔值）
IF NEITHER a single 'true' NOR a single 'false' 'boolean' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“true”或单个“false”“boolean”值，则拒绝/返回“client error bad request”。
IF the value length is NOT equal to 1 octet, REJECT/RETURN 'client-error-request-value-too-long'
如果值长度不等于1个八位字节，则拒绝/返回“客户端错误请求值太长”
IF NOT supplied by the client, the IPP object assumes the value 'false'.
如果不是由客户端提供，IPP对象将采用值“false”。
document-format (mimeMediaType)
文件格式（mimeMediaType）
IF NOT a single non-empty 'mimeMediaType' value, REJECT/RETURN 'client-error-bad-request'.
如果没有一个非空的'mimeMediaType'值，则拒绝/返回'client error bad request'。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT in the Printer object's "document-format-supported" attribute, REJECT/RETURN 'client-error-document-format-not-supported'
如果不在打印机对象的“支持的文档格式”属性中，则拒绝/返回“不支持的客户端错误文档格式”
IF NOT supplied by the client, the IPP object assumes the value of the Printer object's "document-format-default" attribute.
如果不是由客户端提供，IPP对象将采用打印机对象的“文档格式默认值”属性的值。
document-uri (uri)
文档uri（uri）
IF NOT a single non-empty 'uri' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个非空的“uri”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 1023 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于1023个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF the URI syntax is not valid, REJECT/RETURN 'client-error-bad-request'.
如果URI语法无效，请拒绝/返回“客户端错误错误请求”。
If the client-supplied URI scheme is not supported, i.e., the value is not in the Printer object's referenced-uri-scheme-supported" attribute, the Printer object MUST reject the request
如果客户端提供的URI方案不受支持，即该值不在打印机对象的“支持的引用URI方案”属性中，则打印机对象必须拒绝该请求
and return the 'client-error-uri-scheme-not-supported' status code. The Printer object MAY check to see if the document exists and is accessible. If the document is not found or is not accessible, REJECT/RETURN 'client-error-not found'.
并返回“客户端错误uri方案不受支持”状态代码。打印机对象可能会检查文档是否存在并可访问。如果未找到或无法访问文档，请拒绝/返回“未找到客户端错误”。
last-document (boolean)
最后一个文档（布尔值）
IF NEITHER a single 'true' NOR a single 'false' 'boolean' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“true”或单个“false”“boolean”值，则拒绝/返回“client error bad request”。
IF the value length is NOT equal to 1 octet, REJECT/RETURN 'client-error-request-value-too-long'
如果值长度不等于1个八位字节，则拒绝/返回“客户端错误请求值太长”
job-id (integer(1:MAX))
作业id（整数（1:最大值））
IF NOT an single 'integer' value equal to 4 octets AND in the range 1 to MAX, REJECT/RETURN 'client-error-bad-request'.
如果没有一个“整型”值等于4个八位字节且在1到最大范围内，则拒绝/返回“客户端错误错误请求”。
IF NOT a job-id of an existing Job object, REJECT/RETURN 'client-error-not-found' or 'client-error-gone' status code, if keep track of recently deleted jobs.
如果不是现有作业对象的作业id，请拒绝/返回“未找到客户端错误”或“客户端错误已消失”状态代码（如果跟踪最近删除的作业）。
requested-attributes (1setOf keyword)
请求的属性（1setOf关键字）
IF NOT one or more 'keyword' values, REJECT/RETURN 'client-error-bad-request'.
如果没有一个或多个“关键字”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
Ignore unsupported values, which are the keyword names of unsupported attributes. Don't bother to copy such requested (unsupported) attributes to the Unsupported Attribute response group since the response will not return them.
忽略不支持的值，这些值是不支持的属性的关键字名称。不要费心将这些请求的（不支持的）属性复制到不支持的属性响应组，因为响应不会返回它们。
which-jobs (type2 keyword)
哪些作业（type2关键字）
IF NOT a single 'keyword' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“关键字”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NEITHER 'completed' NOR 'not-completed', copy the attribute and the unsupported value to the Unsupported Attributes response group and REJECT/RETURN 'client-error-attributes-or-values-not-supported'.
如果“已完成”或“未完成”，请将属性和不支持的值复制到不支持的属性响应组，并拒绝/返回“客户端错误属性或不支持的值”。
Note: a Printer still supports the 'completed' value even if it keeps no completed/canceled/aborted jobs: by returning no jobs when so queried.
注意：打印机即使不保留任何已完成/取消/中止的作业，也仍然支持“已完成”值：查询时不返回任何作业。
IF NOT supplied by the client, the IPP object assumes the 'not-completed' value.
如果不是由客户端提供，IPP对象将采用“未完成”值。
my-jobs (boolean)
我的工作（布尔值）
IF NEITHER a single 'true' NOR a single 'false' 'boolean' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“true”或单个“false”“boolean”值，则拒绝/返回“client error bad request”。
IF the value length is NOT equal to 1 octet, REJECT/RETURN 'client-error-request-value-too-long'
如果值长度不等于1个八位字节，则拒绝/返回“客户端错误请求值太长”
IF NOT supplied by the client, the IPP object assumes the 'false' value.
如果不是由客户端提供，IPP对象将采用“false”值。
limit (integer(1:MAX))
限制（整数（1:最大值））
IF NOT a single 'integer' value equal to 4 octets AND in the range 1 to MAX, REJECT/RETURN 'client-error-bad-request'.
如果没有一个“整型”值等于4个八位字节且在1到最大范围内，则拒绝/返回“客户端错误错误请求”。
IF NOT supplied by the client, the IPP object returns all jobs, no matter how many.
如果不是由客户机提供，IPP对象将返回所有作业，无论有多少个作业。
-----------------------------------------------
-----------------------------------------------
OPTIONAL Operation attributes are those that an IPP object MAY support. An IPP object validates the values of the OPTIONAL attributes supplied by the client. The IPP object performs the same syntactic validation checks for each OPTIONAL attribute value as in Section 3.1.2.1.5. As in Section 3.1.2.1.5, if any fail, the IPP object REJECTS the request and RETURNS the 'client-error-bad-request' or the 'client-error-request-value-too-long' status code.
可选操作属性是IPP对象可能支持的属性。IPP对象验证客户端提供的可选属性的值。IPP对象对每个可选属性值执行与第3.1.2.1.5节相同的语法验证检查。如第3.1.2.1.5节所述，如果任何失败，IPP对象将拒绝请求并返回“客户端错误错误请求”或“客户端错误请求值过长”状态代码。
In addition, the IPP object checks each Operation attribute value against some Printer attribute or some hard-coded value if there is no "xxx-supported" Printer attribute defined. If its value is not among those supported or is not in the range supported, then the IPP object REJECTS the request and RETURNS the error status code indicated in the table. If the value of the Printer object's "xxx-supported" attribute is 'no-value' (because the system administrator hasn't configured a value), the check always fails.
此外，如果没有定义“支持xxx”的打印机属性，IPP对象将根据某些打印机属性或某些硬编码值检查每个操作属性值。如果其值不在支持的范围内或不在支持的范围内，则IPP对象将拒绝请求并返回表中指示的错误状态代码。如果打印机对象的“支持xxx”属性的值为“无值”（因为系统管理员尚未配置值），则检查始终失败。
If the IPP object doesn't recognize/support an attribute, the IPP object treats the attribute as an unknown or unsupported attribute (see the last row in the table below).
如果IPP对象无法识别/支持某个属性，则IPP对象会将该属性视为未知或不受支持的属性（请参见下表中的最后一行）。
-----------------------------------------------
-----------------------------------------------
document-natural-language (naturalLanguage)
文档自然语言（自然语言）
IF NOT a single non-empty 'naturalLanguage' value, REJECT/RETURN 'client-error-bad-request'.
如果没有一个非空的“naturalLanguage”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 63 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于63个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT a value that the Printer object supports in document formats, (no corresponding "xxx-supported" Printer attribute), REJECT/RETURN 'client-error-natural-language-not-supported'.
如果不是打印机对象在文档格式中支持的值，（没有相应的“支持xxx”打印机属性），则拒绝/返回“不支持客户端错误自然语言”。
compression (type3 keyword)
压缩（type3关键字）
IF NOT a single 'keyword' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“关键字”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT in the Printer object's "compression-supported" attribute, REJECT/RETURN 'client-error-compression-not-supported'.
如果不在打印机对象的“支持压缩”属性中，则拒绝/返回“不支持客户端错误压缩”。
Note to IPP/1.0 implementers: Support for the "compression" attribute was optional in IPP/1.0 and was changed to REQUIRED in IPP/1.1. However, an IPP/1.0 object SHOULD at least check for the "compression" attribute being present and reject the create request, if they don't support "compression". Not checking is a bug, since the data will be unintelligible.
IPP/1.0实施者注意：对“压缩”属性的支持在IPP/1.0中是可选的，在IPP/1.1中更改为必需的。但是，IPP/1.0对象至少应检查是否存在“compression”属性，如果不支持“compression”，则应拒绝创建请求。不检查是一个错误，因为数据将无法理解。
job-k-octets (integer(0:MAX))
job-k-octets（整数（0:MAX））
IF NOT a single 'integer' value equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果没有一个“整型”值等于4个八位字节，则拒绝/返回“客户端错误错误请求”。
IF NOT in the range of the Printer object's "job-k-octets-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group and REJECT/RETURN 'client-error-attributes-or-values-not-supported'.
如果不在打印机对象的“job-k-octets-supported”属性的范围内，请将该属性和不支持的值复制到不支持的属性响应组，并拒绝/返回“客户端错误属性或不支持的值”。
job-impressions (integer(0:MAX))
工作印象（整数（0:MAX））
IF NOT a single 'integer' value equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果没有一个“整型”值等于4个八位字节，则拒绝/返回“客户端错误错误请求”。
IF NOT in the range of the Printer object's "job-impressions-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group and REJECT/RETURN 'client-error-attributes-or-values-not-supported'.
如果不在打印机对象的“支持的作业印象”属性的范围内，请将该属性和不支持的值复制到不支持的属性响应组，并拒绝/返回“客户端错误属性或不支持的值”。
job-media-sheets (integer(0:MAX))
作业介质表（整数（0:MAX））
IF NOT a single 'integer' value equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果没有一个“整型”值等于4个八位字节，则拒绝/返回“客户端错误错误请求”。
IF NOT in the range of the Printer object's "job-media-sheets-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group and REJECT/RETURN 'client-error-attributes-or-values-not-supported'.
如果不在打印机对象的“支持的作业介质表”属性的范围内，请将该属性和不支持的值复制到“不支持的属性”响应组，并拒绝/返回“客户端错误属性或不支持的值”。
message (text(127))
电文（文本（127））
IF NOT a single 'text' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“文本”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 127 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于127个八位字节，则拒绝/返回“客户端错误请求值太长”。
unknown or unsupported attribute
未知或不支持的属性
IF the attribute syntax supplied by the client is supported but the length is not legal for that attribute syntax, REJECT/RETURN 'client-error-request-value-too-long'.
如果支持客户端提供的属性语法，但该属性语法的长度不合法，请拒绝/返回“客户端错误请求值过长”。
ELSE copy the attribute and value to the Unsupported Attributes response group and change the attribute value to the "out-of-band" 'unsupported' value, but otherwise ignore the attribute.
否则，将属性和值复制到不受支持的属性响应组，并将属性值更改为“带外”的“不受支持”值，否则忽略该属性。
Note: Future Operation attributes may be added to the protocol specification that may occur anywhere in the specified group. When the operation is otherwise successful, the IPP object returns the 'successful-ok-ignored-or-substituted-attributes' status code. Ignoring unsupported Operation attributes in all operations is analogous to the handling of unsupported Job Template attributes in the create and Validate-Job operations when the client supplies the "ipp-attribute-fidelity" Operation attribute with the 'false' value. This last rule is so that we can add OPTIONAL Operation attributes to future versions of IPP so that older clients can inter-work with new
注意：未来的操作属性可能会添加到协议规范中，该规范可能会出现在指定组中的任何位置。如果操作成功，IPP对象将返回“成功确定忽略或替换属性”状态代码。在所有操作中忽略不支持的操作属性类似于在客户端为“ipp属性保真度”操作属性提供“false”值时，在创建和验证作业操作中处理不支持的作业模板属性。最后一条规则是，我们可以将可选操作属性添加到IPP的未来版本中，以便旧客户端可以与新客户端交互工作
IPP objects and newer clients can inter-work with older IPP objects. (If the new attribute cannot be ignored without performing unexpectedly, the major version number would have been increased in the protocol document and in the request). This rule for Operation attributes is independent of the value of the "ipp-attribute-fidelity" attribute. For example, if an IPP object doesn't support the OPTIONAL "job-k-octets" attribute', the IPP object treats "job-k-octets" as an unknown attribute and only checks the length for the 'integer' attribute syntax supplied by the client. If it is not four octets, the IPP object REJECTS the request and RETURNS the 'client-error-bad-request' status code, else the IPP object copies the attribute to the Unsupported Attribute response group, setting the value to the "out-of-band" 'unsupported' value, but otherwise ignores the attribute.
IPP对象和较新的客户端可以与较旧的IPP对象交互工作。（如果在没有意外执行的情况下无法忽略新属性，则协议文档和请求中的主版本号会增加）。操作属性的此规则与“ipp属性保真度”属性的值无关。例如，如果IPP对象不支持可选的“job-k-octets”属性，则IPP对象将“job-k-octets”视为未知属性，并仅检查客户端提供的“integer”属性语法的长度。如果不是四个八位字节，IPP对象将拒绝请求并返回“客户端错误错误请求”状态代码，否则IPP对象将属性复制到不受支持的属性响应组，将该值设置为“带外”“不受支持”值，但会忽略该属性。
3.1.2.2 Suggested Additional Processing Steps for Operations that Create/Validate Jobs and Add Documents
3.1.2.2 为创建/验证作业和添加文档的操作建议的其他处理步骤
This section in combination with the previous section recommends the processing steps for the Print-Job, Validate-Job, Print-URI, Create-Job, Send-Document, and Send-URI operations that IPP objects SHOULD use. These are the operations that create jobs, validate a Print-Job request, and add documents to a job.
本节结合上一节介绍IPP对象应使用的打印作业、验证作业、打印URI、创建作业、发送文档和发送URI操作的处理步骤。这些操作用于创建作业、验证打印作业请求以及向作业添加文档。
IIG Sect # Flow IPP error status codes
---------- ---- ----------------------
|
v No
3.1.2.2.1 <ipp-attribute-fidelity> ------------------+
<supplied?> |
Yes| |
| ipp-attribute-fidelity = no |
|<------------------------------+
v No
3.1.2.2.2 <Printer is> --> server-error-not-accepting-jobs
<accepting jobs?>
Yes|
v err
3.1.2.3 <Validate values of> --> client-error-bad-request
<Job template attributes> client-error-request-value-too-
long
<(length, tag, range,>
<multi-value)>
ok|
v err
3.1.2.3 <Validate values with> --> client-error-bad-request
<supported values> client-error-attributes-or-
| values-not-supported
v err
3.1.2.3.1 <Any conflicting> --> client-error-conflicting-
attributes
<Job Template attr values> client-error-attributes-or-
values-not-supported
v
IIG Sect # Flow IPP error status codes
---------- ---- ----------------------
|
v No
3.1.2.2.1 <ipp-attribute-fidelity> ------------------+
<supplied?> |
Yes| |
| ipp-attribute-fidelity = no |
|<------------------------------+
v No
3.1.2.2.2 <Printer is> --> server-error-not-accepting-jobs
<accepting jobs?>
Yes|
v err
3.1.2.3 <Validate values of> --> client-error-bad-request
<Job template attributes> client-error-request-value-too-
long
<(length, tag, range,>
<multi-value)>
ok|
v err
3.1.2.3 <Validate values with> --> client-error-bad-request
<supported values> client-error-attributes-or-
| values-not-supported
v err
3.1.2.3.1 <Any conflicting> --> client-error-conflicting-
attributes
<Job Template attr values> client-error-attributes-or-
values-not-supported
v
The Printer object checks to see if the client supplied an "ipp-attribute-fidelity" Operation attribute. If the attribute is not supplied by the client, the IPP object assumes that the value is 'false'.
打印机对象检查客户端是否提供了“ipp属性保真度”操作属性。如果该属性不是由客户端提供的，IPP对象将假定该值为“false”。
If the value of the Printer objects "printer-is-accepting-jobs" is 'false', the Printer object REJECTS the request and RETURNS the 'server-error-not-accepting-jobs' status code.
如果打印机对象“打印机正在接受作业”的值为“false”，则打印机对象将拒绝请求并返回“服务器错误不接受作业”状态代码。
An IPP object validates the values of all Job Template attribute supplied by the client. The IPP object performs the analogous syntactic validation checks of each Job Template attribute value that it performs for Operation attributes (see Section 3.1.2.1.5.):
IPP对象验证客户端提供的所有作业模板属性的值。IPP对象对其为操作属性执行的每个作业模板属性值执行类似的语法验证检查（见第3.1.2.1.5节）：
a) that the length of each value is correct for the attribute syntax tag supplied by the client according to [RFC2911] Section 4.1.
a) 根据[RFC2911]第4.1节，每个值的长度对于客户端提供的属性语法标记是正确的。
b) that the attribute syntax tag is correct for that attribute according to [RFC2911] Sections 4.2 to 4.4.
b) 根据[RFC2911]第4.2至4.4节，属性语法标记对于该属性是正确的。
c) that multiple values are supplied only for multi-valued attributes, i.e., that are 1setOf X according to [RFC2911] Sections 4.2 to 4.4.
c) 仅为多值属性提供多个值，即根据[RFC2911]第4.2节至第4.4节的规定为1setOf X。
As in Section 3.1.2.1.5, if any of these syntactic checks fail, the IPP object REJECTS the request and RETURNS the 'client-error-bad-request' or 'client-error-request-value-too-long' status code as appropriate, independent of the value of the "ipp-attribute-fidelity". Since such an error is most likely to be an error detected by a client developer, rather than by an end-user, the IPP object NEED NOT return an indication of which attribute had the error in either the Unsupported Attributes Group or the Status Message. The description for each of these syntactic checks is explicitly expressed in the first IF statement in the following table.
如第3.1.2.1.5节所述，如果任何语法检查失败，IPP对象将拒绝请求并返回“客户端错误错误请求”或“客户端错误请求值过长”状态代码（视情况而定），与“IPP属性保真度”的值无关。由于此类错误很可能是由客户端开发人员而不是最终用户检测到的错误，因此IPP对象无需返回指示，说明在不受支持的属性组或状态消息中哪个属性存在错误。下表中的第一个IF语句明确表示了这些语法检查的描述。
Each Job Template attribute MUST occur no more than once. If an IPP Printer receives a create request with multiple occurrences of a Job Template attribute, it MAY:
每个作业模板属性只能出现一次。如果IPP打印机收到多次出现作业模板属性的创建请求，它可能：
1. reject the operation and return the 'client-error-bad-request' error status code
1. 拒绝操作并返回“客户端错误错误请求”错误状态代码
2. accept the operation and use the first occurrence of the attribute
2. 接受该操作并使用该属性的第一个匹配项
3. accept the operation and use the last occurrence of the attribute
3. 接受该操作并使用该属性的最后一个匹配项
depending on implementation. Therefore, clients MUST NOT supply multiple occurrences of the same Job Template attribute in the Job Attributes group in the request.
取决于实施情况。因此，客户端不能在请求的“作业属性”组中多次提供同一作业模板属性。
The process of validating a Job-Template attribute "xxx" against a Printer attribute "xxx-supported" can use the following validation algorithm (see section 3.2.1.2 in [RFC2911]).
根据打印机属性“支持xxx”验证作业模板属性“xxx”的过程可以使用以下验证算法（参见[RFC2911]中的第3.2.1.2节）。
To validate the value U of Job-Template attribute "xxx" against the value V of Printer "xxx-supported", perform the following algorithm:
要根据打印机“支持xxx”的值V验证作业模板属性“xxx”的值U，请执行以下算法：
1. If U is multi-valued, validate each value X of U by performing the algorithm in Table 7 with each value X. Each validation is separate from the standpoint of returning unsupported values. Example: If U is "finishings" that the client supplies with 'staple', 'bind' values, then X takes on the successive values: 'staple', then 'bind'
1. 如果U是多值的，则通过使用每个值X执行表7中的算法来验证U的每个值X。从返回不支持的值的角度来看，每个验证是独立的。示例：如果U是客户机提供的“装订”、“绑定”值的“finishings”，那么X将采用后续值：“装订”，然后是“绑定”
2. If V is multi-valued, validate X against each Z of V by performing the algorithm in Table 7 with each value Z. If a value Z validates, the validation for the attribute value X succeeds. If it fails, the algorithm is applied to the next value Z of V. If there are no more values Z of V, validation fails. Example" If V is "sides-supported" with values: 'one- sided', 'two-sided-long', and 'two-sided-short', then Z takes on the successive values: 'one-sided', 'two-sided-long', and 'two-sided-short'. If the client supplies "sides" with 'two-sided- long', the first comparison fails ('one-sided' is not equal to 'two-sided-long'), the second comparison succeeds ('two-sided-long' is equal to 'two-sided-long"), and the third comparison ('two-sided-short' with 'two-sided-long') is not even performed.
2. 如果V是多值的，则通过对每个值Z执行表7中的算法，针对V的每个Z验证X。如果值Z验证，则属性值X的验证成功。如果失败，该算法将应用于V的下一个值Z。如果没有更多的值Z，验证将失败。示例“如果V是“受支持的边”且值为：“单面”、“双面长”和“双面短”，则Z采用连续值：“单面”、“双面长”和“双面短”。如果客户向“边”提供“双面长”，则第一次比较失败（“单面”不等于“双面长”），第二次比较成功（“双面长”等于“双面长”），第三次比较（“双面短”与“双面长”）甚至没有执行。
3. If both U and V are single-valued, let X be U and Z be V and use the validation rules in Table 7.
3. 如果U和V都是单值的，则设X为U，Z为V，并使用表7中的验证规则。
Table 7 - Rules for validating single values X against Z
表7-验证单个值X与Z的规则
Attribute syntax attribute syntax validated if: of X of Z
属性语法如果：X/Z，则验证属性语法
integer rangeOfInteger X is within the range of Z
整数X的整数范围在Z的范围内
uri uriScheme the uri scheme in X is equal to Z
uri uri模式X中的uri模式等于Z
any boolean the value of Z is TRUE
Z值为真的任何布尔值
any any X and Z are of the same type and are equal.
任何X和Z都属于同一类型且相等。
If the value of the Printer object's "xxx-supported" attribute is 'no-value' (because the system administrator hasn't configured a value), the check always fails. If the check fails, the IPP object copies the attribute to the Unsupported Attributes response group with its unsupported value. If the attribute contains more than one value, each value is checked and each unsupported value is separately copied, while supported values are not copied. If an IPP object doesn't recognize/support a Job Template attribute, i.e., there is no corresponding Printer object "xxx-supported" attribute, the IPP object treats the attribute as an unknown or unsupported attribute (see the last row in the table below).
如果打印机对象的“支持xxx”属性的值为“无值”（因为系统管理员尚未配置值），则检查始终失败。如果检查失败，IPP对象会将该属性复制到具有其不支持的值的不支持的属性响应组。如果属性包含多个值，则会选中每个值，并分别复制每个不支持的值，而不会复制支持的值。如果IPP对象不识别/不支持作业模板属性，即没有相应的打印机对象“支持xxx”属性，则IPP对象会将该属性视为未知或不支持的属性（请参阅下表中的最后一行）。
If some Job Template attributes are supported for some document formats and not for others or the values are different for different document formats, the IPP object SHOULD take that into account in this validation using the value of the "document-format" supplied by the client (or defaulted to the value of the Printer's "document-format-default" attribute, if not supplied by the client). For example, if "number-up" is supported for the 'text/plain' document format, but not for the 'application/postscript' document format, the check SHOULD (though it NEED NOT) depend on the value of the "document-format" operation attribute. See "document-format" in [RFC2911] section 3.2.1.1 and 3.2.5.1.
如果某些文档格式支持某些作业模板属性，而其他文档格式不支持这些属性，或者不同文档格式的值不同，则IPP对象应使用客户端提供的“文档格式”值（或默认为打印机的“文档格式默认值”）在验证中考虑这些属性属性（如果不是由客户端提供）。例如，如果“text/plain”文档格式支持“number up”，但“application/postscript”文档格式不支持“number up”，则检查应（尽管不需要）取决于“document format”操作属性的值。参见[RFC2911]第3.2.1.1节和第3.2.5.1节中的“文件格式”。
Note: whether the request is accepted or rejected is determined by the value of the "ipp-attribute-fidelity" attribute in a subsequent step, so that all Job Template attribute supplied are examined and all unsupported attributes and/or values are copied to the Unsupported Attributes response group.
注意：接受还是拒绝请求取决于后续步骤中“ipp属性保真度”属性的值，以便检查提供的所有作业模板属性，并将所有不支持的属性和/或值复制到不支持的属性响应组。
-----------------------------------------------
-----------------------------------------------
job-priority (integer(1:100))
作业优先级（整数（1:100））
IF NOT a single 'integer' value with a length equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果不是长度等于4个八位字节的单个“整数值”，则拒绝/返回“客户端错误错误请求”。
IF NOT supplied by the client, use the value of the Printer object's "job-priority-default" attribute at job submission time.
如果不是由客户端提供，请在作业提交时使用打印机对象的“作业优先级默认值”属性的值。
IF NOT in the range 1 to 100, inclusive, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果不在1到100（包括1到100）的范围内，请将属性和不支持的值复制到不支持的属性响应组。
Map the value to the nearest supported value in the range 1:100 as specified by the number of discrete values indicated by the value of the Printer's "job-priority-supported" attribute. See the formula in [RFC2911] Section 4.2.1.
将该值映射到1:100范围内最接近的支持值，该值由打印机“支持的作业优先级”属性的值指示的离散值数量指定。参见[RFC2911]第4.2.1节中的公式。
job-hold-until (type3 keyword | name)
作业保留至（键入3关键字|名称）
IF NOT a single 'keyword' or 'name' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“关键字”或“名称”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT supplied by the client, use the value of the Printer object's "job-hold-until" attribute at job submission time.
如果不是由客户机提供，请在作业提交时使用打印机对象的“作业保留到”属性的值。
IF NOT in the Printer object's "job-hold-until-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果不在打印机对象的“支持前保持作业”属性中，请将该属性和不支持的值复制到“不支持的属性”响应组。
job-sheets (type3 keyword | name)
工作表（type3关键字|名称）
IF NOT a single 'keyword' or 'name' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“关键字”或“名称”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT in the Printer object's "job-sheets-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果不在打印机对象的“支持的工作表”属性中，请将该属性和不支持的值复制到“不支持的属性”响应组。
multiple-document-handling (type2 keyword)
多文档处理（type2关键字）
IF NOT a single 'keyword' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“关键字”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT in the Printer object's "multiple-document-handling-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果不在打印机对象的“支持多文档处理”属性中，请将该属性和不支持的值复制到“不支持的属性”响应组。
copies (integer(1:MAX))
副本（整数（1:最大值））
IF NOT a single 'integer' value with a length equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果不是长度等于4个八位字节的单个“整数值”，则拒绝/返回“客户端错误错误请求”。
IF NOT in range of the Printer object's "copies-supported" attribute
如果不在打印机对象的“支持的副本”属性的范围内
copy the attribute and the unsupported value to the Unsupported Attributes response group.
将属性和不支持的值复制到不支持的属性响应组。
finishings (1setOf type2 enum)
饰面（第1种类型2枚举）
IF NOT an 'enum' value(s) each with a length equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果不是长度等于4个八位字节的“枚举”值，则拒绝/返回“客户端错误错误请求”。
IF NOT in the Printer object's "finishings-supported" attribute, copy the attribute and the unsupported value(s), but not any supported values, to the Unsupported Attributes response group.
如果打印机对象的“finishings supported”属性不在其中，请将该属性和不支持的值（但不是任何支持的值）复制到不支持的属性响应组。
page-ranges (1setOf rangeOfInteger(1:MAX))
页面范围（1整合器的设置范围（1:最大））
IF NOT a 'rangeOfInteger' value(s) each with a length equal to 8 octets, REJECT/RETURN 'client-error-bad-request'.
如果不是长度等于8个八位字节的“rangeOfInteger”值，则拒绝/返回“客户端错误错误请求”。
IF first value is greater than second value in any range, the ranges are not in ascending order, or ranges overlap, REJECT/RETURN 'client-error-bad-request'.
如果任何范围内的第一个值大于第二个值，则范围不按升序排列，或范围重叠，请拒绝/返回“客户端错误错误请求”。
IF the value of the Printer object's "page-ranges-supported" attribute is 'false', copy the attribute to the Unsupported Attributes response group and set the value to the "out-of-band" 'unsupported' value.
如果打印机对象的“支持的页面范围”属性的值为“false”，请将该属性复制到“不支持的属性”响应组，并将该值设置为“带外”的“不支持的”值。
sides (type2 keyword)
侧面（type2关键字）
IF NOT a single 'keyword' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“关键字”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT in the Printer object's "sides-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果打印机对象的“支持的边”属性中没有，请将该属性和不支持的值复制到“不支持的属性”响应组。
number-up (integer(1:MAX))
向上计数（整数（1:最大值））
IF NOT a single 'integer' value with a length equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果不是长度等于4个八位字节的单个“整数值”，则拒绝/返回“客户端错误错误请求”。
IF NOT a value or in the range of one of the values of the Printer object's "number-up-supported" attribute, copy the attribute and value to the Unsupported Attribute response group.
如果不是打印机对象“number up supported”属性的值或在其中一个值的范围内，请将该属性和值复制到不受支持的属性响应组。
orientation-requested (type2 enum)
要求的方向（类型2枚举）
IF NOT a single 'enum' value with a length equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果没有一个长度等于4个八位字节的“enum”值，请拒绝/返回“client error bad request”。
IF NOT in the Printer object's "orientation-requested-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果不在打印机对象的“支持的方向请求”属性中，请将该属性和不支持的值复制到不支持的属性响应组。
media (type3 keyword | name)
媒体（类型3关键字|名称）
IF NOT a single 'keyword' or 'name' value, REJECT/RETURN 'client-error-bad-request'.
如果没有单个“关键字”或“名称”值，则拒绝/返回“客户端错误错误请求”。
IF the value length is greater than 255 octets, REJECT/RETURN 'client-error-request-value-too-long'.
如果值长度大于255个八位字节，则拒绝/返回“客户端错误请求值太长”。
IF NOT in the Printer object's "media-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果打印机对象的“支持的介质”属性中没有，请将该属性和不支持的值复制到“不支持的属性”响应组。
printer-resolution (resolution)
打印机分辨率（分辨率）
IF NOT a single 'resolution' value with a length equal to 9 octets, REJECT/RETURN 'client-error-bad-request'.
如果没有长度等于9个八位字节的单个“分辨率”值，则拒绝/返回“客户端错误错误请求”。
IF NOT in the Printer object's "printer-resolution-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果不在打印机对象的“支持的打印机分辨率”属性中，请将该属性和不支持的值复制到不支持的属性响应组。
print-quality (type2 enum)
打印质量（类型2枚举）
IF NOT a single 'enum' value with a length equal to 4 octets, REJECT/RETURN 'client-error-bad-request'.
如果没有一个长度等于4个八位字节的“enum”值，请拒绝/返回“client error bad request”。
IF NOT in the Printer object's "print-quality-supported" attribute, copy the attribute and the unsupported value to the Unsupported Attributes response group.
如果不在打印机对象的“支持的打印质量”属性中，请将该属性和不支持的值复制到“不支持的属性”响应组。
unknown or unsupported attribute (i.e., there is no corresponding Printer object "xxx-supported" attribute)
未知或不受支持的属性（即，没有相应的打印机对象“支持xxx”属性）
IF the attribute syntax supplied by the client is supported but the length is not legal for that attribute syntax,
如果支持客户端提供的属性语法，但该属性语法的长度不合法，
REJECT/RETURN 'client-error-bad-request' if the length of the attribute syntax is fixed or 'client-error-request-value-too-long' if the length of the attribute syntax is variable.
如果属性语法的长度固定，则拒绝/返回“客户端错误错误请求”；如果属性语法的长度可变，则拒绝/返回“客户端错误请求值过长”。
ELSE copy the attribute and value to the Unsupported Attributes response group and change the attribute value to the "out-of-band" 'unsupported' value. Any remaining Job Template Attributes are either unknown or unsupported Job Template attributes and are validated algorithmically according to their attribute syntax for proper length (see below).
否则，将属性和值复制到不支持的属性响应组，并将属性值更改为“带外”‘不支持’值。任何剩余的作业模板属性都是未知的或不受支持的作业模板属性，并根据其属性语法以适当的长度进行算法验证（见下文）。
-----------------------------------------------
-----------------------------------------------
If the attribute syntax is supported AND the length check fails, the IPP object REJECTS the request and RETURNS the 'client-error-bad-request' if the length of the attribute syntax is fixed or the 'client-error-request-value-too-long' status code if the length of the attribute syntax is variable. Otherwise, the IPP object copies the unsupported Job Template attribute to the Unsupported Attributes response group and changes the attribute value to the "out-of-band" 'unsupported' value. The following table shows the length checks for all attribute syntaxes. In the following table: "<=" means less than or equal, "=" means equal to:
如果支持属性语法且长度检查失败，则IPP对象将拒绝请求，并在属性语法的长度固定时返回“客户端错误错误请求”，或者在属性语法的长度可变时返回“客户端错误请求值过长”状态码。否则，IPP对象会将不受支持的作业模板属性复制到不受支持的属性响应组，并将属性值更改为“带外”的“不受支持”值。下表显示了所有属性语法的长度检查。在下表中：“<=”表示小于或等于，“=”表示等于：
Name Octet length check for read-write attributes
---------- ---------------------------------------------
Name Octet length check for read-write attributes
---------- ---------------------------------------------
'textWithLanguage <= 1023 AND 'naturalLanguage' <= 63
'textWithoutLanguage' <= 1023
'nameWithLanguage' <= 255 AND 'naturalLanguage' <= 63
'nameWithoutLanguage' <= 255
'keyword' <= 255
'enum' = 4
'uri' <= 1023
'uriScheme' <= 63
'charset' <= 63
'naturalLanguage' <= 63
'mimeMediaType' <= 255
'octetString' <= 1023
'boolean' = 1
'integer' = 4
'rangeOfInteger' = 8
'dateTime' = 11
'resolution' = 9
'1setOf X'
'textWithLanguage <= 1023 AND 'naturalLanguage' <= 63
'textWithoutLanguage' <= 1023
'nameWithLanguage' <= 255 AND 'naturalLanguage' <= 63
'nameWithoutLanguage' <= 255
'keyword' <= 255
'enum' = 4
'uri' <= 1023
'uriScheme' <= 63
'charset' <= 63
'naturalLanguage' <= 63
'mimeMediaType' <= 255
'octetString' <= 1023
'boolean' = 1
'integer' = 4
'rangeOfInteger' = 8
'dateTime' = 11
'resolution' = 9
'1setOf X'
Note: It's possible for a Printer to receive a zero length keyword in a request. Since this is a keyword, its value needs to be compared with the supported values. Assuming that the printer doesn't have any values in its corresponding "xxx-supported" attribute that are keywords of zero length, the comparison will fail. Then the request will be accepted or rejected depending on the value of "ipp-attributes-fidelity" being 'false' or 'true', respectively. No special handling is required for
注意：打印机可以在请求中接收零长度关键字。由于这是一个关键字，因此需要将其值与支持的值进行比较。假设打印机在其相应的“xxx支持”属性中没有任何长度为零的关键字值，则比较将失败。然后，根据“ipp属性保真度”的值分别为“假”或“真”，请求将被接受或拒绝。无需特殊处理
Once all the Operation and Job Template attributes have been checked individually, the Printer object SHOULD check for any conflicting values among all the supported values supplied by the client. For example, a Printer object might be able to staple and to print on transparencies, however due to physical stapling constraints, the Printer object might not be able to staple transparencies. The IPP object copies the supported attributes and their conflicting attribute values to the Unsupported Attributes response group. The Printer object only copies over those attributes that the Printer object either ignores or substitutes in order to resolve the conflict, and it returns the original values which were supplied by the client. For example suppose the client supplies "finishings" equals 'staple' and "media" equals 'transparency', but the Printer object does not support stapling transparencies. If the Printer chooses to ignore the stapling request in order to resolve the
单独检查所有操作和作业模板属性后，打印机对象应检查客户端提供的所有支持值之间是否存在任何冲突值。例如，打印机对象可能能够装订和打印透明胶片，但是由于物理装订约束，打印机对象可能无法装订透明胶片。IPP对象将支持的属性及其冲突的属性值复制到不支持的属性响应组。打印机对象仅复制打印机对象为解决冲突而忽略或替换的属性，并返回客户端提供的原始值。例如，假设客户端提供的“finishings”等于“装订”，而“media”等于“透明度”，但打印机对象不支持装订透明胶片。如果打印机选择忽略装订请求以解决问题
conflict, the Printer objects returns "finishings" equal to 'staple' in the Unsupported Attributes response group. If any attributes are multi-valued, only the conflicting values of the attributes are copied.
冲突时，打印机对象在不支持的属性响应组中返回等于“装订”的“finishings”。如果任何属性是多值的，则仅复制属性的冲突值。
Note: The decisions made to resolve the conflict (if there is a choice) is implementation dependent.
注意：解决冲突的决策（如果有选择）取决于实现。
If there were any unsupported Job Template attributes or unsupported/conflicting Job Template attribute values and the client supplied the "ipp-attribute-fidelity" attribute with the 'true' value, the Printer object REJECTS the request and return the status code:
如果存在任何不受支持的作业模板属性或不受支持/冲突的作业模板属性值，并且客户端为“ipp属性保真度”属性提供了“true”值，则打印机对象将拒绝请求并返回状态代码：
1.'client-error-conflicting-attributes' status code, if there were any conflicts between attributes supplied by the client.
1.“client-error-conflicting-attributes”状态代码，如果客户端提供的属性之间存在任何冲突。
2.'client-error-attributes-or-values-not-supported' status code, otherwise.
2.“client-error-attributes-or-values-not-supported”状态代码，否则为。
Note: Unsupported Operation attributes or values that are returned do not affect the status returned in this step. If the unsupported Operation attribute was a serious error, the above already rejected the request in a previous step. If control gets to this step with unsupported Operation attributes being returned, they are not serious errors.
注意：返回的不受支持的操作属性或值不会影响此步骤中返回的状态。如果不支持的操作属性是一个严重错误，则上述操作已在上一步中拒绝了该请求。如果控件执行此步骤时返回了不受支持的操作属性，则这些属性不是严重错误。
In general, the final results of Job processing are unknown at Job submission time. The client has to rely on notifications or polling to find out what happens at Job processing time. However, there are cases in which some Printers can determine at Job submission time that Job processing is going to fail. As an optimization, we'd like to have the Printer reject the Job in these cases.
通常，作业提交时，作业处理的最终结果是未知的。客户端必须依靠通知或轮询来了解作业处理时发生的情况。但是，在某些情况下，某些打印机可以在作业提交时确定作业处理将失败。作为一种优化，我们希望打印机在这种情况下拒绝作业。
There are three types of "processing" errors that might be detectable at Job submission time:
有三种类型的“处理”错误可能在作业提交时检测到：
1. 'client-error-document-format-not-supported' : For the Print-Job, Send-Document, Print-URI, and Send-URI operations, if all these conditions are true:
1. “不支持客户端错误文档格式”：对于打印作业，如果所有这些条件均为真，则执行发送文档、打印URI和发送URI操作：
- the Printer supports auto-sensing, - the request "document-format" operation attribute is 'application/octet-stream', - the Printer receives document data before responding, - the Printer auto-senses the document format before responding,
- 打印机支持自动感应，-请求“文档格式”操作属性为“应用程序/八位字节流”，-打印机在响应前接收文档数据，-打印机在响应前自动感应文档格式，
- the sensed document format is not supported by the Printer
- 打印机不支持检测到的文档格式
then the Printer should respond with 'client-error-document-format-not-supported' status.
然后打印机应以“客户端错误文档格式不受支持”状态响应。
2. 'client-error-compression-error': For the Print-Job, Send-Document, Print-URI, and Send-URI operations, if all these conditions are true:
2. “客户端错误压缩错误”：对于打印作业，发送文档、打印URI和发送URI操作，如果所有这些条件均为真：
- the client supplies a supported value for the "compression" operation attribute in the request - the Printer receives document data before responding, - the Printer attempts to decompress the document data before responding, - the document data cannot be decompressed using the algorithm specified by the "compression" operation attribute
- 客户端为请求中的“压缩”操作属性提供支持的值-打印机在响应之前接收文档数据-打印机在响应之前尝试解压缩文档数据-无法使用“压缩”操作属性指定的算法解压缩文档数据
then the Printer should respond with 'client-error-compression-error' status.
然后打印机应响应“客户端错误压缩错误”状态。
3. 'client-error-document-access-error': For the Print-URI, and Send-URI operations, if the Printer attempts and fails to pull the referenced document data before responding, it should respond with 'client-error-document-access-error' status.
3. “客户端错误文档访问错误”：对于“打印URI”和“发送URI”操作，如果打印机尝试在响应之前提取引用的文档数据但失败，则应以“客户端错误文档访问错误”状态进行响应。
Some Printers are not able to detect these errors until Job processing time. In that case, the errors are recorded in the corresponding job-state and job-state reason attributes. (There is no standard way for a client to determine whether a Printer can detect these errors at Job submission time.) For example, if auto-sensing happens AFTER the job is accepted (as opposed to auto-sensing at submit time before returning the response), the implementation aborts the job, puts the job in the 'aborted' state and sets the 'unsupported-document-format' value in the job's "job-state-reasons".
某些打印机在作业处理时间之前无法检测到这些错误。在这种情况下，错误将记录在相应的作业状态和作业状态原因属性中。（客户端没有标准的方法来确定打印机是否可以在作业提交时检测到这些错误。）例如，如果在接受作业后发生自动感应（而不是在返回响应之前在提交时自动感应），则实现会中止作业，将作业置于“中止”状态，并在作业的“作业状态原因”中设置“不支持的文档格式”值。
A client should always provide a valid "document-format" operation attribute whenever practical. In the absence of other information, a client itself may sniff the document data to determine document format.
只要可行，客户机应始终提供有效的“文档格式”操作属性。在没有其他信息的情况下，客户机本身可能会嗅探文档数据以确定文档格式。
Auto sensing at Job submission time may be more difficult for the Printer when combined with compression. For auto-sensed Jobs, a client may be better off deferring compression to the transfer protocol layer, e.g.; by using the HTTP Content-Encoding header.
当与压缩相结合时，在作业提交时自动感应可能对打印机更为困难。对于自动感测的作业，客户端最好将压缩延迟到传输协议层，例如。；通过使用HTTP内容编码头。
3.1.2.3.3 For the Validate-Job operation, RETURN one of the success status codes
3.1.2.3.3 对于验证作业操作，返回一个成功状态代码
If the requested operation is the Validate-Job operation, the Printer object returns:
如果请求的操作是验证作业操作，打印机对象将返回：
1. the "successful-ok" status code, if there are no unsupported or conflicting Job Template attributes or values. 2. the "successful-ok-conflicting-attributes, if there are any conflicting Job Template attribute or values. 3. the "successful-ok-ignored-or-substituted-attributes, if there are only unsupported Job Template attributes or values.
1. 如果没有不受支持或冲突的作业模板属性或值，“成功确定”状态代码。2.如果存在任何冲突的作业模板属性或值，则“成功确定”属性将发生冲突。3.如果只有不支持的作业模板属性或值，则“成功确定”属性将被忽略或替换。
Note: Unsupported Operation attributes or values that are returned do not affect the status returned in this step. If the unsupported Operation attribute was a serious error, the above already rejected the request in a previous step. If control gets to this step with unsupported Operation attributes being returned, they are not serious errors.
注意：返回的不受支持的操作属性或值不会影响此步骤中返回的状态。如果不支持的操作属性是一个严重错误，则上述操作已在上一步中拒绝了该请求。如果控件执行此步骤时返回了不受支持的操作属性，则这些属性不是严重错误。
If "ipp-attribute-fidelity" is set to 'false' (or it was not supplied by the client), the Printer object:
如果“ipp属性保真度”设置为“false”（或客户端未提供），打印机对象：
1. creates a Job object, assigns a unique value to the job's "job-uri" and "job-id" attributes, and initializes all of the job's other supported Job Description attributes. 2. removes all unsupported attributes from the Job object. 3. for each unsupported value, removes either the unsupported value or substitutes the unsupported attribute value with some supported value. If an attribute has no values after removing unsupported values from it, the attribute is removed from the Job object (so that the normal default behavior at job processing time will take place for that attribute). 4. for each conflicting value, removes either the conflicting value or substitutes the conflicting attribute value with some other supported value. If an attribute has no values after removing conflicting values from it, the attribute is removed from the Job object (so that the normal default behavior at job processing time will take place for that attribute).
1. 创建作业对象，为作业的“作业uri”和“作业id”属性指定唯一值，并初始化作业的所有其他受支持的作业描述属性。2.从作业对象中删除所有不受支持的属性。3.对于每个不受支持的值，删除不受支持的值或用某个受支持的值替换不受支持的属性值。如果从属性中删除不支持的值后该属性没有值，则该属性将从作业对象中删除（这样该属性将在作业处理时发生正常的默认行为）。4.对于每个冲突的值，删除冲突的值或用其他支持的值替换冲突的属性值。如果从属性中删除冲突值后该属性没有值，则该属性将从作业对象中删除（以便该属性在作业处理时发生正常的默认行为）。
If there were no attributes or values flagged as unsupported, or the value of 'ipp-attribute-fidelity" was 'false', the Printer object is able to accept the create request and create a new Job object. If the "ipp-attribute-fidelity" attribute is set to 'true', the Job Template attributes that populate the new Job object are necessarily all the Job Template attributes supplied in the create request. If
如果没有标记为不受支持的属性或值，或者“ipp属性保真度”的值为“false”，则打印机对象能够接受创建请求并创建新作业对象。如果“ipp属性保真度”为属性设置为“true”，填充新作业对象的作业模板属性必须是创建请求中提供的所有作业模板属性。如果
the "ipp-attribute-fidelity" attribute is set to 'false', the Job Template attributes that populate the new Job object are all the client supplied Job Template attributes that are supported or that have value substitution. Thus, some of the requested Job Template attributes will not appear in the Job object because the Printer object did not support those attributes. The attributes that populate the Job object are persistently stored with the Job object for that Job. A Get-Job-Attributes operation on that Job object will return only those attributes that are persistently stored with the Job object.
“ipp属性保真度”属性设置为“false”，填充新作业对象的作业模板属性是所有受支持或具有值替换的客户端提供的作业模板属性。因此，某些请求的作业模板属性将不会出现在作业对象中，因为打印机对象不支持这些属性。填充作业对象的属性将与该作业的作业对象一起永久存储。该作业对象上的“获取作业属性”操作将仅返回与作业对象一起持久存储的那些属性。
Note: All Job Template attributes that are persistently stored with the Job object are intended to be "override values"; that is, they that take precedence over whatever other embedded instructions might be in the document data itself. However, it is not possible for all Printer objects to realize the semantics of "override". End users may query the Printer's "pdl-override-supported" attribute to determine if the Printer either attempts or does not attempt to override document data instructions with IPP attributes.
注意：与作业对象一起持久存储的所有作业模板属性都是“覆盖值”；也就是说，它们优先于文档数据本身中的任何其他嵌入式指令。但是，并非所有打印机对象都能实现“覆盖”的语义。最终用户可以查询打印机的“支持pdl覆盖”属性，以确定打印机是否尝试使用IPP属性覆盖文档数据指令。
There are some cases, where a Printer supports a Job Template attribute and has an associated default value set for that attribute. In the case where a client does not supply the corresponding attribute, the Printer does not use its default values to populate Job attributes when creating the new Job object; only Job Template attributes actually in the create request are used to populate the Job object. The Printer's default values are only used later at Job processing time if no other IPP attribute or instruction embedded in the document data is present.
在某些情况下，打印机支持作业模板属性，并为该属性设置了关联的默认值。如果客户端不提供相应的属性，则打印机在创建新作业对象时不会使用其默认值填充作业属性；只有创建请求中实际存在的作业模板属性才用于填充作业对象。如果文档数据中不存在其他IPP属性或指令，则打印机的默认值仅在作业处理时使用。
Note: If the default values associated with Job Template attributes that the client did not supply were to be used to populate the Job object, then these values would become "override values" rather than defaults. If the Printer supports the 'attempted' value of the "pdl-override-supported" attribute, then these override values could replace values specified within the document data. This is not the intent of the default value mechanism. A default value for an attribute is used only if the create request did not specify that attribute (or it was ignored when allowed by "ipp-attribute-fidelity" being 'false') and no value was provided within the content of the document data.
注意：如果要使用与客户端未提供的作业模板属性关联的默认值来填充作业对象，则这些值将成为“覆盖值”，而不是默认值。如果打印机支持“pdl override supported”（pdl覆盖支持）属性的“尝试”值，则这些覆盖值可以替换文档数据中指定的值。这不是默认值机制的意图。仅当创建请求未指定某个属性（或当“ipp属性保真度”为“false”时被忽略）且文档数据内容中未提供任何值时，才使用该属性的默认值。
If the client does not supply a value for some Job Template attribute, and the Printer does not support that attribute, as far as IPP is concerned, the result of processing that Job (with respect to the missing attribute) is undefined.
如果客户端没有为某个作业模板属性提供值，并且打印机不支持该属性，则就IPP而言，处理该作业的结果（关于缺少的属性）是未定义的。
Once the Job object has been created, the Printer object accepts the request and returns to the client:
创建作业对象后，打印机对象接受请求并返回到客户端：
1. the 'successful-ok' status code, if there are no unsupported or conflicting Job Template attributes or values. 2. the 'successful-ok-conflicting-attributes' status code, if there are any conflicting Job Template attribute or values. 3. the 'successful-ok-ignored-or-substituted-attributes' status code, if there are only unsupported Job Template attributes or values.
1. 如果没有不受支持或冲突的作业模板属性或值，“成功确定”状态代码。2.如果存在任何冲突的作业模板属性或值，“成功确定冲突属性”状态代码。3.如果只有不受支持的作业模板属性或值，则显示“成功确定忽略或替换属性”状态代码。
Note: Unsupported Operation attributes or values that are returned do not affect the status returned in this step. If the unsupported Operation attribute was a serious error, the above already rejected the request in a previous step. If control gets to this step with unsupported Operation attributes being returned, they are not serious errors.
注意：返回的不受支持的操作属性或值不会影响此步骤中返回的状态。如果不支持的操作属性是一个严重错误，则上述操作已在上一步中拒绝了该请求。如果控件执行此步骤时返回了不受支持的操作属性，则这些属性不是严重错误。
The Printer object also returns Job status attributes that indicate the initial state of the Job ('pending', 'pending-held', 'processing', etc.), etc. See Print-Job Response, [RFC2911] section 3.2.1.2.
打印机对象还返回指示作业初始状态的作业状态属性（“挂起”、“挂起”、“处理”等）。请参阅打印作业响应[RFC2911]第3.2.1.2节。
The Printer object accepts the appended Document Content data and either starts it printing, or spools it for later processing.
Printer对象接受附加的文档内容数据并开始打印，或将其后台打印以供以后处理。
The Printer object uses its own configuration and implementation specific algorithms for scheduling the Job in the correct processing order. Once the Printer object begins processing the Job, the Printer changes the Job's state to 'processing'. If the Printer object supports PDL override (the "pdl-override-supported" attribute set to 'attempted'), the implementation does its best to see that IPP attributes take precedence over embedded instructions in the document data.
打印机对象使用其自己的配置和特定于实现的算法，以正确的处理顺序安排作业。打印机对象开始处理作业后，打印机会将作业的状态更改为“正在处理”。如果打印机对象支持PDL覆盖（“支持的PDL覆盖”属性设置为“已尝试”），则实现会尽力确保IPP属性优先于文档数据中的嵌入指令。
The Printer object continues to process the Job until it can move the Job into the 'completed' state. If an Cancel-Job operation is received, the implementation eventually moves the Job into the 'canceled' state. If the system encounters errors during processing that do not allow it to progress the Job into a completed state, the
打印机对象将继续处理作业，直到可以将作业移动到“已完成”状态。如果收到取消作业操作，则实现最终会将作业移动到“已取消”状态。如果系统在处理过程中遇到错误，使其无法将作业推进到已完成状态，则
implementation halts all processing, cleans up any resources, and moves the Job into the 'aborted' state.
实现会停止所有处理，清理所有资源，并将作业移动到“中止”状态。
Once the Job moves to the 'completed', 'aborted', or 'canceled' state, it is an implementation decision as to when to destroy the Job object and release all associated resources. Once the Job has been destroyed, the Printer would return either the "client-error-not-found" or "client-error-gone" status codes for operations directed at that Job.
一旦作业移动到“已完成”、“已中止”或“已取消”状态，则何时销毁作业对象并释放所有相关资源是一个实现决策。一旦作业被销毁，打印机将返回针对该作业的操作的“未找到客户端错误”或“客户端错误已消失”状态代码。
Note: the Printer object SHOULD NOT re-use a "job-uri" or "job-id" value for a sufficiently long time after a job has been destroyed, so that stale references kept by clients are less likely to access the wrong (newer) job.
注意：在作业被销毁后，打印机对象不应在足够长的时间内重复使用“作业uri”或“作业id”值，以便客户端保留的陈旧引用不太可能访问错误（较新）的作业。
Some Printer object implementations may support "ipp-attribute-fidelity" set to 'true' and "pdl-override-supported" set to 'attempted' and yet still not be able to realize exactly what the client specifies in the create request. This is due to legacy decisions and assumptions that have been made about the role of job instructions embedded within the document data and external job instructions that accompany the document data and how to handle conflicts between such instructions. The inability to be 100% precise about how a given implementation will behave is also compounded by the fact that the two special attributes, "ipp-attribute-fidelity" and "pdl-"override-supported", apply to the whole job rather than specific values for each attribute. For example, some implementations may be able to override almost all Job Template attributes except for "number-up". Character Sets, natural languages, and internationalization
某些打印机对象实现可能支持将“ipp属性保真度”设置为“true”和将“支持的pdl覆盖”设置为“尝试”，但仍然无法准确实现客户端在创建请求中指定的内容。这是由于对文档数据中嵌入的作业指导书的角色和随文档数据而来的外部作业指导书以及如何处理这些指导书之间的冲突做出了遗留决策和假设。由于支持两个特殊属性“ipp属性保真度”和“pdl-”覆盖，无法100%精确地描述给定实现的行为，应用于整个作业，而不是每个属性的特定值。例如，某些实现可能能够覆盖除“number up”之外的几乎所有作业模板属性。字符集、自然语言和国际化
This section discusses character set support, natural language support and internationalization.
本节讨论字符集支持、自然语言支持和国际化。
IPP clients and IPP objects are REQUIRED to support UTF-8. They MAY support additional charsets. It is RECOMMENDED that an IPP object also support US-ASCII, since many clients support US-ASCII, and indicate that UTF-8 and US-ASCII are supported by populating the Printer's "charset-supported" with 'utf-8' and 'us-ascii' values. An IPP object is required to code covert with as little loss as possible between the charsets that it supports, as indicated in the Printer's "charsets-supported" attribute.
IPP客户端和IPP对象需要支持UTF-8。它们可能支持额外的字符集。建议IPP对象也支持US-ASCII，因为许多客户端支持US-ASCII，并通过使用“UTF-8”和“US ASCII”值填充打印机的“支持的字符集”来表示支持UTF-8和US-ASCII。IPP对象需要在其支持的字符集之间进行编码转换，并尽可能少地丢失，如打印机的“支持的字符集”属性所示。
How should the server handle the situation where the "attributes-charset" of the response itself is "us-ascii", but one or more attributes in that response is in the "utf-8" format?
服务器应该如何处理响应本身的“attributes charset”是“us ascii”，但该响应中的一个或多个属性是“utf-8”格式的情况？
Example: Consider a case where a client sends a Print-Job request with "utf-8" as the value of "attributes-charset" and with the "job-name" attribute supplied. Later another client submits a Get-Job-Attribute or Get-Jobs request. This second request contains the "attributes-charset" with value "us-ascii" and "requested-attributes" attribute with exactly one value "job-name".
示例：考虑一个客户端发送一个打印作业请求，其中“UTF-8”作为“属性字符集”的值，并提供“作业名”属性。稍后，另一个客户端提交Get Job属性或Get Jobs请求。第二个请求包含值为“us ascii”的“attributes charset”和值为“job name”的“requested attributes”属性。
According to the RFC2911 document (section 3.1.4.2), the value of the "attributes-charset" for the response of the second request must be "us-ascii" since that is the charset specified in the request. The "job-name" value, however, is in "utf-8" format. Should the request be rejected even though both "utf-8" and "us-ascii" charsets are supported by the server? or should the "job-name" value be converted to "us-ascii" and return "successful-ok-conflicting-attributes" (0x0002) as the status code?
根据RFC2911文件（第3.1.4.2节），第二个请求响应的“属性字符集”值必须为“us ascii”，因为这是请求中指定的字符集。但是，“作业名称”值采用“utf-8”格式。即使服务器同时支持“utf-8”和“us ascii”字符集，请求是否应被拒绝？还是应该将“作业名称”值转换为“us ascii”并返回“成功确定冲突属性”（0x0002）作为状态代码？
Answer: An IPP object that supports both utf-8 (REQUIRED) and us-ascii, the second paragraph of section 3.1.4.2 applies so that the IPP object MUST accept the request, perform code set conversion between these two charsets with "the highest fidelity possible" and return 'successful-ok', rather than a warning 'successful-ok-conflicting-attributes, or an error. The printer will do the best it can to convert between each of the character sets that it supports -- even if that means providing a string of question marks because none of the characters are representable in US ASCII. If it can't perform such conversion, it MUST NOT advertise us-ascii as a value of its "attributes-charset-supported" and MUST reject any request that requests 'us-ascii'.
回答：支持utf-8（必需）和us ascii的IPP对象，第3.1.4.2节第二段适用，因此IPP对象必须接受请求，以“可能的最高保真度”在这两个字符集之间执行代码集转换，并返回“成功ok”，而不是警告“成功ok”，或者是一个错误。打印机将尽其所能在其支持的每个字符集之间进行转换，即使这意味着提供一个问号字符串，因为没有一个字符可以用美国ASCII表示。如果它不能执行这样的转换，它不能将us ascii作为其“支持的属性字符集”的值公布，并且必须拒绝任何请求“us ascii”的请求。
One IPP object implementation strategy is to convert all request text and name values to a Unicode internal representation. This is 16-bit and virtually universal. Then convert to the specified operation attributes-charset on output.
一种IPP对象实现策略是将所有请求文本和名称值转换为Unicode内部表示形式。这是16位的，几乎是通用的。然后在输出时转换为指定的操作属性字符集。
Also it would be smarter for a client to ask for 'utf-8', rather than 'us-ascii' and throw away characters that it doesn't understand, rather than depending on the code conversion of the IPP object.
此外，对于客户端来说，请求“utf-8”，而不是“us ascii”，并丢弃它不理解的字符，比依赖IPP对象的代码转换更为明智。
3.1.2.3.12 What charset to return when an unsupported charset is requested (Issue 1.19)?
3.1.2.3.12 请求不受支持的字符集时要返回什么字符集（问题1.19）？
Section 3.1.4.1 Request Operation attributes was clarified in November 1998 as follows:
第3.1.4.1节请求操作属性于1998年11月澄清如下：
All clients and IPP objects MUST support the 'utf-8' charset [RFC2044] and MAY support additional charsets provided that they are registered with IANA [IANA-CS]. If the Printer object does not support the client supplied charset value, the Printer object MUST reject the request, set the "attributes-charset" to 'utf-8' in the response, and return the 'client-error-charset-not-supported' status code and any 'text' or 'name' attributes using the 'utf-8' charset.
所有客户端和IPP对象必须支持“utf-8”字符集[RFC2044]，并且可以支持其他字符集，前提是它们已在IANA[IANA-CS]注册。如果打印机对象不支持客户端提供的字符集值，则打印机对象必须拒绝请求，在响应中将“attributes charset”设置为“utf-8”，并使用“utf-8”字符集返回“client error charset not supported”（客户端错误字符集不受支持）状态代码以及任何“text”（文本）或“name”（名称）属性。
Since the client and IPP object MUST support UTF-8, returning any text or name attributes in UTF-8 when the client requests a charset that is not supported should allow the client to display the text or name.
由于客户端和IPP对象必须支持UTF-8，因此当客户端请求不受支持的字符集时，返回UTF-8中的任何文本或名称属性应允许客户端显示文本或名称。
Since such an error is a client error, rather than a user error, the client should check the status code first so that it can avoid displaying any other returned 'text' and 'name' attributes that are not in the charset requested.
由于此类错误是客户端错误，而不是用户错误，因此客户端应首先检查状态代码，以避免显示不在请求的字符集中的任何其他返回的“text”和“name”属性。
Furthermore, [RFC2911] section 14.1.4.14 client-error-charset-not-supported (0x040D) was clarified in November 1998 as follows:
此外，[RFC2911]第14.1.4.14节不支持客户端错误字符集（0x040D）于1998年11月澄清如下：
For any operation, if the IPP Printer does not support the charset supplied by the client in the "attributes-charset" operation attribute, the Printer MUST reject the operation and return this status and any 'text' or 'name' attributes using the 'utf-8' charset (see Section 3.1.4.1).
对于任何操作，如果IPP打印机不支持客户端在“属性字符集”操作属性中提供的字符集，则打印机必须拒绝该操作，并使用“utf-8”字符集返回该状态以及任何“文本”或“名称”属性（见第3.1.4.1节）。
The 'text' and 'name' attributes each have two forms. One has an implicit natural language, and the other has an explicit natural language. The 'textWithoutLanguage' and 'textWithLanguage' are the two 'text' forms. The 'nameWithoutLanguage" and 'nameWithLanguage are the two 'name' forms. If a receiver (IPP object or IPP client) supports an attribute with attribute syntax 'text', it MUST support both forms in a request and a response. A sender (IPP client or IPP object) MAY send either form for any such attribute. When a sender sends a WithoutLanguage form, the implicit natural language is specified in the "attributes-natural-language" operation attribute, which all senders MUST include in every request and response.
“text”和“name”属性都有两种形式。一种是隐式自然语言，另一种是显式自然语言。“textWithoutLanguage”和“textWithLanguage”是两种“文本”形式。“nameWithoutLanguage”和“nameWithLanguage”是两种“名称”形式。如果接收者（IPP对象或IPP客户端）支持属性语法为“text”的属性，则它必须在请求和响应中同时支持这两种形式。发送者（IPP客户端或IPP对象）可以为任何此类属性发送任一表单。当发送方发送WithoutLanguage表单时，隐式自然语言在“attributes natural language”操作属性中指定，所有发送方必须在每个请求和响应中包含该属性。
When a sender sends a WithLanguage form, it MAY be different from the implicit natural language supplied by the sender or it MAY be the same. The receiver MUST treat either form equivalently.
当发送方发送WithLanguage表单时，它可能与发送方提供的隐式自然语言不同，也可能相同。接收者必须同等对待任何一种形式。
There is an implementation decision for senders, whether to always send the WithLanguage forms or use the WithoutLanguage form when the attribute's natural language is the same as the request or response.
发送者有一个实现决策，当属性的自然语言与请求或响应相同时，是始终发送WithLanguage表单还是使用WithoutLanguage表单。
The former approach makes the sender implementation simpler. The latter approach is more efficient on the wire and allows inter-working with non-conforming receivers that fail to support the WithLanguage forms. As each approach have advantages, the choice is completely up to the implementer of the sender.
前一种方法使发送方实现更简单。后一种方法在线路上更有效，并允许与不支持WithLanguage表单的不一致接收器交互工作。由于每种方法都有优点，选择完全取决于发送方的实现者。
Furthermore, when a client receives a 'text' or 'name' job attribute that it had previously supplied, that client MUST NOT expect to see the attribute in the same form, i.e., in the same WithoutLanguage or WithLanguage form as the client supplied when it created the job. The IPP object is free to transform the attribute from the WithLanguage form to the WithoutLanguage form and vice versa, as long as the natural language is preserved. However, in order to meet this latter requirement, it is usually simpler for the IPP object implementation to store the natural language explicitly with the attribute value, i.e., to store using an internal representation that resembles the WithLanguage form.
此外，当客户机收到其先前提供的“文本”或“名称”作业属性时，该客户机不得期望看到与创建作业时提供的客户机格式相同的属性，即使用相同的WithoutLanguage或WithLanguage格式。IPP对象可以自由地将属性从WithLanguage形式转换为WithoutLanguage形式，反之亦然，只要保留了自然语言。然而，为了满足后一个要求，IPP对象实现通常更容易使用属性值显式存储自然语言，即使用类似于WithLanguage形式的内部表示进行存储。
The IPP Printer MUST copy the natural language of a job, i.e., the value of the "attributes-natural-language" operation attribute supplied by the client in the create operation, to the Job object as a Job Description attribute, so that a client is able to query it. In returning a Get-Job-Attributes response, the IPP object MAY return one of three natural language values in the responses "attributes-natural-language" operation attribute: (1) that requested by the requester, (2) the natural language of the job, or (3) the configured natural language of the IPP Printer, if the requested language is not supported by the IPP Printer.
IPP打印机必须将作业的自然语言（即客户端在创建操作中提供的“attributes natural language”操作属性的值）作为作业描述属性复制到作业对象，以便客户端能够查询它。在返回Get Job Attributes响应时，IPP对象可能会返回响应“Attributes natural language”操作属性中的三个自然语言值之一：（1）请求者请求的值，（2）作业的自然语言，或（3）IPP打印机配置的自然语言，如果IPP打印机不支持请求的语言。
This "attributes-natural-language" Job Description attribute is useful for an IPP object implementation that prints start sheets in the language of the user who submitted the job. This same Job Description attribute is useful to a multi-lingual operator who has to communicate with different job submitters in different natural languages. This same Job Description attribute is expected to be used in the future to generate notification messages in the natural language of the job submitter.
此“attributes natural language”作业描述属性对于IPP对象实现非常有用，IPP对象以提交作业的用户的语言打印起始页。对于必须用不同自然语言与不同的工作提交人交流的多语言操作员来说，相同的工作描述属性非常有用。这个相同的职务描述属性预计将在将来用于以职务提交者的自然语言生成通知消息。
Early drafts of [RFC2911] contained a job-level natural language override (NLO) for the Get-Jobs response. A job-level (NLO) is an (unrequested) Job Attribute which then specified the implicit natural language for any other WithoutLanguage job attributes returned in the response for that job. Interoperability testing of early implementations showed that no one was implementing the job-level NLO in Get-Job responses. So the job-level NLO was eliminated from the Get-Jobs response. This simplification makes all requests and responses consistent in that the implicit natural language for any
[RFC2911]的早期草案包含一个用于获取作业响应的作业级自然语言覆盖（NLO）。作业级别（NLO）是一个（未请求的）作业属性，然后为响应中返回的任何其他WithoutLanguage作业属性指定隐式自然语言。对早期实现的互操作性测试表明，没有人在Get作业响应中实现作业级NLO。因此，从Get Jobs响应中消除了作业级别的NLO。这种简化使得所有的请求和响应都是一致的，因为对于任何请求，隐式的自然语言都是一致的
WithoutLanguage 'text' or 'name' form is always supplied in the request's or response's "attributes-natural-language" operation attribute.
WithoutLanguage“text”或“name”表单始终在请求或响应的“attributes natural language”操作属性中提供。
This section corresponds to [RFC2911] section 3.1.6 "Operation Response Status Codes and Status Messages". This section lists all status codes once in the first operation (Print-Job). Then it lists the status codes that are different or specialized for subsequent operations under each operation.
本节与[RFC2911]第3.1.6节“运行响应状态代码和状态消息”相对应。本节列出了第一次操作（打印作业）中的所有状态代码。然后，它列出了每个操作下后续操作的不同或专用状态代码。
The Printer object MUST return one of the following "status-code" values for the indicated reason. Whether all of the document data has been accepted or not before returning the success or error response depends on implementation. See Section 13 in [RFC2911] for a more complete description of each status code.
出于指定的原因，打印机对象必须返回以下“状态代码”值之一。返回成功或错误响应之前是否接受了所有文档数据取决于实现。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the Job object has been created and the "job-id", and "job-uri" assigned and returned in the response:
对于以下成功状态代码，已创建作业对象，并在响应中分配和返回“作业id”和“作业uri”：
successful-ok: no request attributes were substituted or ignored.
成功确定：未替换或忽略任何请求属性。
successful-ok-ignored-or-substituted-attributes: some supplied (1) attributes were ignored or (2) unsupported attribute syntaxes or values were substituted with supported values or were ignored. Unsupported attributes, attribute syntax's, or values MUST be returned in the Unsupported Attributes group of the response.
成功确定忽略或替换属性：某些提供的（1）属性被忽略或（2）不支持的属性语法或值被支持的值替换或被忽略。不支持的属性、属性语法或值必须在响应的“不支持的属性”组中返回。
successful-ok-conflicting-attributes: some supplied attribute values conflicted with the values of other supplied attributes and were either substituted or ignored. Attributes or values which conflict with other attributes and have been substituted or ignored MUST be returned in the Unsupported Attributes group of the response as supplied by the client.
成功确定冲突属性：某些提供的属性值与其他提供的属性值冲突，被替换或忽略。必须在客户端提供的响应的“不支持的属性”组中返回与其他属性冲突且已被替换或忽略的属性或值。
[RFC2911] section 3.1.6 Operation Status Codes and Messages states:
[RFC2911]第3.1.6节操作状态代码和消息说明：
If the Printer object supports the "status-message" operation attribute, it SHOULD use the REQUIRED 'utf-8' charset to return a status message for the following error status codes (see section 13 in [RFC2911]): 'client-error-bad-request', 'client-error-charset-not-supported', 'server-error-internal-error', 'server-
如果打印机对象支持“status message”操作属性，则应使用所需的“utf-8”字符集返回以下错误状态代码的状态消息（请参阅[RFC2911]中的第13节）：“客户端错误错误错误请求”、“客户端错误字符集不受支持”、“服务器错误内部错误”、“服务器错误”-
error-operation-not-supported', and 'server-error-version-not-supported'. In this case, it MUST set the value of the "attributes-charset" operation attribute to 'utf-8' in the error response.
“不支持错误操作”和“不支持服务器错误版本”。在这种情况下，它必须在错误响应中将“attributes charset”操作属性的值设置为“utf-8”。
For the following error status codes, no job is created and no "job-id" or "job-uri" is returned:
对于以下错误状态代码，不会创建作业，也不会返回“作业id”或“作业uri”：
client-error-bad-request: The request syntax does not conform to the specification.
客户端错误错误请求：请求语法不符合规范。
client-error-forbidden: The request is being refused for authorization or authentication reasons. The implementation security policy is to not reveal whether the failure is one of authentication or authorization.
禁止客户端错误：由于授权或身份验证原因，请求被拒绝。实现安全策略是不透露失败是身份验证还是授权。
client-error-not-authenticated: Either the request requires authentication information to be supplied or the authentication information is not sufficient for authorization.
未验证的客户端错误：请求要求提供验证信息，或者验证信息不足以进行授权。
client-error-not-authorized: The requester is not authorized to perform the request on the target object.
客户端错误未授权：请求者无权对目标对象执行请求。
client-error-not-possible: The request cannot be carried out because of the state of the system. See also 'server-error-not-accepting-jobs' status code, which MUST take precedence if the Printer object's "printer-accepting-jobs" attribute is 'false'.
客户端错误不可能：由于系统的状态，无法执行请求。另请参阅“服务器错误不接受作业”状态代码，如果打印机对象的“打印机接受作业”属性为“false”，则该状态代码必须优先。
client-error-timeout: not applicable.
客户端错误超时：不适用。
client-error-not-found: the target object does not exist.
找不到客户端错误：目标对象不存在。
client-error-gone: the target object no longer exists and no forwarding address is known.
客户端错误消失：目标对象不再存在，并且不知道转发地址。
client-error-request-entity-too-large: the size of the request and/or print data exceeds the capacity of the IPP Printer to process it.
客户端错误请求实体太大：请求和/或打印数据的大小超过IPP打印机处理它的容量。
client-error-request-value-too-long: the size of request variable length attribute values, such as 'text' and 'name' attribute syntax's, exceed the maximum length specified in [RFC2911] for the attribute and MUST be returned in the Unsupported Attributes Group.
客户端错误请求值太长：请求可变长度属性值（如“text”和“name”属性语法）的大小超过[RFC2911]中为属性指定的最大长度，必须在不支持的属性组中返回。
supplied is not supported. The "document-format" attribute with the unsupported value MUST be returned in the Unsupported Attributes Group. This error SHOULD take precedence over any other 'xxx-not-supported' error, except 'client-error-charset-not-supported'.
不支持提供。必须在“不支持的属性”组中返回具有不支持值的“文档格式”属性。此错误应优先于任何其他“不支持xxx”错误，但“不支持客户端错误字符集”除外。
client-error-attributes-or-values-not-supported: one or more supplied attributes, attribute syntax's, or values are not supported and the client supplied the "ipp-attributes-fidelity" operation attribute with a 'true' value. They MUST be returned in the Unsupported Attributes Group as explained below.
不支持客户端错误属性或值：不支持一个或多个提供的属性、属性语法或值，并且客户端为“ipp属性保真度”操作属性提供了“true”值。它们必须在不支持的属性组中返回，如下所述。
client-error-uri-scheme-not-supported: not applicable.
不支持客户端错误uri方案：不适用。
client-error-charset-not-supported: the charset supplied in the "attributes-charset" operation attribute is not supported. The Printer's "configured-charset" MUST be returned in the response as the value of the "attributes-charset" operation attribute and used for any 'text' and 'name' attributes returned in the error response. This error SHOULD take precedence over any other error, unless the request syntax is so bad that the client's supplied "attributes-charset" cannot be determined.
不支持客户端错误字符集：“attributes charset”操作属性中提供的字符集不受支持。打印机的“配置字符集”必须在响应中作为“属性字符集”操作属性的值返回，并用于错误响应中返回的任何“文本”和“名称”属性。此错误应优先于任何其他错误，除非请求语法太差，无法确定客户端提供的“attributes charset”。
client-error-conflicting-attributes: one or more supplied attribute values conflicted with each other and the client supplied the "ipp-attributes-fidelity" operation attribute with a 'true' value. They MUST be returned in the Unsupported Attributes Group as explained below.
客户端错误冲突属性：一个或多个提供的属性值相互冲突，并且客户端提供的“ipp属性保真度”操作属性具有“true”值。它们必须在不支持的属性组中返回，如下所述。
server-error-internal-error: an unexpected condition prevents the request from being fulfilled.
服务器错误内部错误：意外情况阻止请求得到满足。
server-error-operation-not-supported: not applicable (since Print-Job is REQUIRED).
不支持服务器错误操作：不适用（因为需要打印作业）。
server-error-service-unavailable: the service is temporarily overloaded.
服务器错误服务不可用：服务暂时超载。
server-error-version-not-supported: the version in the request is not supported. The "closest" version number supported MUST be returned in the response.
不支持服务器错误版本：不支持请求中的版本。响应中必须返回支持的“最接近”版本号。
server-error-device-error: a device error occurred while receiving or spooling the request or document data or the IPP Printer object can only accept one job at a time.
服务器错误设备错误：接收或后台处理请求或文档数据时发生设备错误，或者IPP打印机对象一次只能接受一个作业。
server-error-temporary-error: a temporary error such as a buffer full write error, a memory overflow, or a disk full condition occurred while receiving the request and/or the document data.
服务器错误临时错误：在接收请求和/或文档数据时发生临时错误，如缓冲区已满写入错误、内存溢出或磁盘已满。
server-error-not-accepting-jobs: the Printer object's "printer-is-not-accepting-jobs" attribute is 'false'.
服务器错误不接受作业：打印机对象的“打印机不接受作业”属性为“false”。
server-error-busy: the Printer is too busy processing jobs to accept another job at this time.
服务器错误忙：打印机正忙于处理作业，此时无法接受其他作业。
server-error-job-canceled: the job has been canceled by an operator or the system while the client was transmitting the document data.
服务器错误作业已取消：当客户端传输文档数据时，操作员或系统已取消作业。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to Print-URI with the following specializations and differences. See Section 14 for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码都适用于具有以下专门化和差异的打印URI。有关每个状态代码的更完整说明，请参见第14节。
client-error-uri-scheme-not-supported: the URI scheme supplied in the "document-uri" operation attribute is not supported and is returned in the Unsupported Attributes group.
不支持客户端错误uri方案：“文档uri”操作属性中提供的uri方案不受支持，并在不支持的属性组中返回。
server-error-operation-not-supported: the Print-URI operation is not supported.
不支持服务器错误操作：不支持打印URI操作。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to Validate-Job. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码均适用于验证作业。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to Create-Job with the following specializations and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码适用于创建具有以下专门化和差异的作业。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
server-error-operation-not-supported: the Create-Job operation is not supported.
不支持服务器错误操作：不支持创建作业操作。
client-error-multiple-document-jobs-not-supported: while the Create-Job and Send-Document operations are supported, this implementation doesn't support more than one document with data.
客户端错误不支持多个文档作业：虽然支持创建作业和发送文档操作，但此实现不支持多个包含数据的文档。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to the Get-Printer-Attributes operation with the following specialization's and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码适用于“获取打印机属性”操作，具有以下专门化和差异。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the requested attributes are returned in Group 3 in the response:
对于以下成功状态代码，请求的属性将在响应的组3中返回：
successful-ok: no operation attributes or values were substituted or ignored (same as Print-Job) and no requested attributes were unsupported.
成功确定：未替换或忽略任何操作属性或值（与打印作业相同），且不支持任何请求的属性。
successful-ok-ignored-or-substituted-attributes: The "requested-attributes" operation attribute MAY, but NEED NOT, be returned with the unsupported values.
成功确定忽略或替换的属性：“请求的属性”操作属性可以（但不必）返回不支持的值。
successful-ok-conflicting-attributes: same as Print-Job.
成功确定冲突属性：与打印作业相同。
For the error status codes, Group 3 is returned containing no attributes or is not returned at all:
对于错误状态代码，返回的组3不包含属性或根本不返回：
client-error-not-possible: Same as Print-Job, in addition the Printer object is not accepting any requests.
客户端错误不可能：与打印作业相同，此外打印机对象不接受任何请求。
client-error-request-entity-too-large: same as Print-job, except that no print data is involved.
客户端错误请求实体太大：与打印作业相同，只是不涉及打印数据。
client-error-attributes-or-values-not-supported: not applicable, since unsupported operation attributes and/or values MUST be ignored and an appropriate success code returned (see above).
不支持客户端错误属性或值：不适用，因为必须忽略不支持的操作属性和/或值，并返回相应的成功代码（见上文）。
client-error-conflicting-attributes: same as Print-Job, except that "ipp-attribute-fidelity" is not involved.
客户端错误冲突属性：与打印作业相同，只是不涉及“ipp属性保真度”。
server-error-operation-not-supported: not applicable (since Get-Printer-Attributes is REQUIRED).
不支持服务器错误操作：不适用（因为需要获取打印机属性）。
server-error-device-error: same as Print-Job, except that no document data is involved.
服务器错误设备错误：与打印作业相同，只是不涉及文档数据。
server-error-temporary-error: same as Print-Job, except that no document data is involved.
服务器错误临时错误：与打印作业相同，只是不涉及文档数据。
server-error-not-accepting-jobs: not applicable.
不接受作业时发生服务器错误：不适用。
server-error-busy: same as Print-Job, except the IPP object is too busy to accept even query requests.
服务器错误忙：与打印作业相同，只是IPP对象太忙，甚至无法接受查询请求。
server-error-job-canceled: not applicable.
服务器错误作业已取消：不适用。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to the Get-Jobs operation with the following specialization's and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码均适用于Get作业操作，具有以下特殊性和差异。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the requested attributes are returned in Group 3 in the response:
对于以下成功状态代码，请求的属性将在响应的组3中返回：
successful-ok: same as Get-Printer-Attributes (see section 3.1.3.1.5).
成功确定：与获取打印机属性相同（参见第3.1.3.1.5节）。
successful-ok-ignored-or-substituted-attributes: same as Get-Printer-Attributes (see section 3.1.3.1.5).
成功确定忽略或替换属性：与获取打印机属性相同（参见第3.1.3.1.5节）。
successful-ok-conflicting-attributes: same as Get-Printer-Attributes (see section 3.1.3.1.5).
成功确定冲突属性：与获取打印机属性相同（参见第3.1.3.1.5节）。
For any error status codes, Group 3 is returned containing no attributes or is not returned at all. The following brief error status code descriptions contain unique information for use with Get-Jobs operation. See section 14 for the other error status codes that apply uniformly to all operations:
对于任何错误状态代码，返回的组3不包含任何属性或根本不返回。以下简短的错误状态代码描述包含用于获取作业操作的唯一信息。有关统一适用于所有操作的其他错误状态代码，请参见第14节：
client-error-not-possible: Same as Print-Job, in addition the Printer object is not accepting any requests.
客户端错误不可能：与打印作业相同，此外打印机对象不接受任何请求。
client-error-request-entity-too-large: same as Print-job, except that no print data is involved.
客户端错误请求实体太大：与打印作业相同，只是不涉及打印数据。
client-error-document-format-not-supported: not applicable.
不支持客户端错误文档格式：不适用。
client-error-attributes-or-values-not-supported: not applicable, since unsupported operation attributes and/or values MUST be ignored and an appropriate success code returned (see above).
不支持客户端错误属性或值：不适用，因为必须忽略不支持的操作属性和/或值，并返回相应的成功代码（见上文）。
client-error-conflicting-attributes: same as Print-Job, except that "ipp-attribute-fidelity" is not involved.
客户端错误冲突属性：与打印作业相同，只是不涉及“ipp属性保真度”。
server-error-operation-not-supported: not applicable (since Get-Jobs is REQUIRED).
不支持服务器错误操作：不适用（因为需要获取作业）。
server-error-device-error: same as Print-Job, except that no document data is involved.
服务器错误设备错误：与打印作业相同，只是不涉及文档数据。
server-error-temporary-error: same as Print-Job, except that no document data is involved.
服务器错误临时错误：与打印作业相同，只是不涉及文档数据。
server-error-not-accepting-jobs: not applicable.
不接受作业时发生服务器错误：不适用。
server-error-job-canceled: not applicable.
服务器错误作业已取消：不适用。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to Pause-Printer with the following specializations and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码适用于具有以下专门化和差异的暂停打印机。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the Printer object is being stopped from scheduling jobs on all its devices.
对于以下成功状态代码，正在停止打印机对象在其所有设备上调度作业。
successful-ok: no request attributes were substituted or ignored (same as Print-Job).
成功确定：未替换或忽略任何请求属性（与打印作业相同）。
successful-ok-ignored-or-substituted-attributes: same as Print-Job.
成功确定忽略或替换属性：与打印作业相同。
successful-ok-conflicting-attributes: same as Print-Job.
成功确定冲突属性：与打印作业相同。
For any of the error status codes, the Printer object has not been stopped from scheduling jobs on all its devices.
对于任何错误状态代码，尚未停止打印机对象在其所有设备上调度作业。
client-error-not-possible: not applicable.
客户端错误不可能：不适用。
client-error-not-found: the target Printer object does not exist.
找不到客户端错误：目标打印机对象不存在。
client-error-gone: the target Printer object no longer exists and no forwarding address is known.
客户端错误消失：目标打印机对象不再存在，并且不知道转发地址。
client-error-request-entity-too-large: same as Print-Job, except no document data is involved.
客户端错误请求实体太大：与打印作业相同，只是不涉及文档数据。
client-error-document-format-not-supported: not applicable.
不支持客户端错误文档格式：不适用。
client-error-conflicting-attributes: same as Print-Job, except that the Printer's "printer-is-accepting-jobs" attribute is not involved.
客户端错误冲突属性：与打印作业相同，只是不涉及打印机的“打印机正在接受作业”属性。
server-error-operation-not-supported: the Pause-Printer operation is not supported.
不支持服务器错误操作：不支持暂停打印机操作。
server-error-device-error: not applicable.
服务器错误设备错误：不适用。
server-error-temporary-error: same as Print-Job, except no document data is involved.
服务器错误临时错误：与打印作业相同，只是不涉及文档数据。
server-error-not-accepting-jobs: not applicable.
不接受作业时发生服务器错误：不适用。
server-error-job-canceled: not applicable.
服务器错误作业已取消：不适用。
All of the Print-Job status code descriptions in Section 3.1.3.1.1 Print-Job Response with the specialization's described for Pause-Printer are applicable to Resume-Printer. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中的所有打印作业状态代码描述，以及针对暂停打印机所述的专门化，均适用于恢复打印机。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the Printer object resumes scheduling jobs on all its devices.
对于以下成功状态代码，打印机对象在其所有设备上恢复调度作业。
successful-ok: no request attributes were substituted or ignored (same as Print-Job).
成功确定：未替换或忽略任何请求属性（与打印作业相同）。
successful-ok-ignored-or-substituted-attributes: same as Print-Job.
成功确定忽略或替换属性：与打印作业相同。
successful-ok-conflicting-attributes: same as Print-Job.
成功确定冲突属性：与打印作业相同。
For any of the error status codes, the Printer object does not resume scheduling jobs.
对于任何错误状态代码，打印机对象都不会恢复计划作业。
server-error-operation-not-supported: the Resume-Printer operation is not supported.
不支持服务器错误操作：不支持恢复打印机操作。
3.1.3.1.8.1 What about Printers unable to change state due to an error condition?
3.1.3.1.8.1 由于出现错误而无法更改状态的打印机如何处理？
If, in case, the IPP printer is unable to change its state due to some problem with the actual printer device (say, it is shut down or there is a media-jam as indicated in [RFC2911]), what should be the result of the "Resume-Printer" operation? Should it still change the 'printer-state-reasons' and return success or should it fail ?
在这种情况下，如果IPP打印机由于实际打印机设备出现问题而无法更改其状态（例如，如[RFC2911]中所述，打印机关闭或出现卡纸），则“恢复打印机”操作的结果应该是什么？它应该仍然更改“打印机状态原因”并返回成功还是失败？
The Resume-Printer operation must clear the 'paused' or 'moving-to-paused' 'printer-state-message'. The operation must return a 'successful-ok' status code.
恢复打印机操作必须清除“暂停”或“移动到暂停”打印机状态消息。操作必须返回“成功确定”状态代码。
If the Resume-Printer operation succeeds, what should be the value of "printer-state" and who should take care of the "printer-state" attribute value later on ?
如果恢复打印机操作成功，“打印机状态”的值应该是多少？以后谁来处理“打印机状态”属性值？
The Resume-Printer operation may change the "printer-state-reasons" value.
恢复打印机操作可能会更改“打印机状态原因”值。
The "printer-state" will change to one of three states:
“打印机状态”将更改为以下三种状态之一：
1. 'idle' - no additional jobs and no error conditions present
1. “空闲”-不存在其他作业和错误条件
2. 'processing' - job available and no error conditions present
2. “处理”-作业可用且不存在错误条件
3. current state (i.e. no change) an error condition is present (e.g. media jam)
3. 当前状态（即无变化）存在错误情况（例如介质堵塞）
In the third case the "printer-state-reason" will be cleared by automata when it detects the error condition no longer exists. The "printer-state" will move to 'idle' or 'processing' when conditions permit. (i.e. no more error conditions)
在第三种情况下，当自动机检测到错误条件不再存在时，“打印机状态原因”将被清除。条件允许时，“打印机状态”将移至“空闲”或“处理”。（即不再出现错误情况）
All of the Print-Job status code descriptions in Section 3.1.3.1.1 Print-Job Response with the specialization's described for Pause-Printer are applicable to Purge-Printer. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中的所有打印作业状态代码说明，以及暂停打印机的专用说明，均适用于清除打印机。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the Printer object purges all it's jobs.
对于以下成功状态代码，打印机对象将清除其所有作业。
successful-ok: no request attributes were substituted or ignored (same as Print-Job).
成功确定：未替换或忽略任何请求属性（与打印作业相同）。
successful-ok-ignored-or-substituted-attributes: same as Print-Job.
成功确定忽略或替换属性：与打印作业相同。
successful-ok-conflicting-attributes: same as Print-Job.
成功确定冲突属性：与打印作业相同。
For any of the error status codes, the Printer object does not purge any jobs.
对于任何错误状态代码，打印机对象都不会清除任何作业。
server-error-operation-not-supported: the Purge-Printer operation is not supported.
不支持服务器错误操作：不支持清除打印机操作。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to the Get-Printer-Attributes operation with the following specialization's and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码适用于“获取打印机属性”操作，具有以下专门化和差异。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the document has been added to the specified Job object and the job's "number-of-documents" attribute has been incremented:
对于以下成功状态代码，文档已添加到指定的作业对象，并且作业的“文档数”属性已递增：
successful-ok: no request attributes were substituted or ignored (same as Print-Job).
成功确定：未替换或忽略任何请求属性（与打印作业相同）。
successful-ok-ignored-or-substituted-attributes: same as Print-Job.
成功确定忽略或替换属性：与打印作业相同。
successful-ok-conflicting-attributes: same as Print-Job.
成功确定冲突属性：与打印作业相同。
For the error status codes, no document has been added to the Job object and the job's "number-of-documents" attribute has not been incremented:
对于错误状态代码，未向作业对象添加任何文档，且作业的“文档数”属性未增加：
client-error-not-possible: Same as Print-Job, except that the Printer's "printer-is-accepting-jobs" attribute is not involved, so that the client is able to finish submitting a job that was created with a Create-Job operation after this attribute has been set to 'true'. Another condition is that the state of the job precludes Send-Document, i.e., the job has
客户端错误不可能：与打印作业相同，只是不涉及打印机的“打印机正在接受作业”属性，因此在将该属性设置为“true”后，客户端可以完成提交通过创建作业操作创建的作业。另一个条件是作业的状态不允许发送文档，即作业具有
already been closed out by the client. However, if the IPP Printer closed out the job due to timeout, the 'client-error-timeout' error status SHOULD be returned instead.
已被客户关闭。但是，如果IPP打印机由于超时而关闭了作业，则应返回“客户端错误超时”错误状态。
client-error-timeout: This request was sent after the Printer closed the job, because it has not received a Send-Document or Send-URI operation within the Printer's "multiple-operation-time-out" period .
客户端错误超时：此请求是在打印机关闭作业后发送的，因为它在打印机的“多次操作超时”期间未收到发送文档或发送URI操作。
client-error-request-entity-too-large: same as Print-Job.
客户端错误请求实体太大：与打印作业相同。
client-error-conflicting-attributes: same as Print-Job, except that "ipp-attributes-fidelity" operation attribute is not involved..
客户端错误冲突属性：与打印作业相同，只是不涉及“ipp属性保真度”操作属性。。
server-error-operation-not-supported: the Send-Document request is not supported.
不支持服务器错误操作：不支持发送文档请求。
server-error-not-accepting-jobs: not applicable.
不接受作业时发生服务器错误：不适用。
server-error-job-canceled: the job has been canceled by an operator or the system while the client was transmitting the data.
服务器错误作业已取消：在客户端传输数据时，操作员或系统已取消作业。
All of the Print-Job status code descriptions in Section 3.1.3.1.1 Print-Job Response with the specialization's described for Send-Document are applicable to Send-URI. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中的所有打印作业状态代码描述以及针对发送文档所描述的专门化都适用于发送URI。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
client-error-uri-scheme-not-supported: the URI scheme supplied in the "document-uri" operation attribute is not supported and the "document-uri" attribute MUST be returned in the Unsupported Attributes group.
不支持客户端错误uri方案：不支持“文档uri”操作属性中提供的uri方案，必须在不支持的属性组中返回“文档uri”属性。
server-error-operation-not-supported: the Send-URI operation is not supported.
不支持服务器错误操作：不支持发送URI操作。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to Cancel-Job with the following specializations and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码适用于具有以下专门化和差异的取消作业。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the Job object is being canceled or has been canceled:
对于以下成功状态代码，作业对象正在被取消或已被取消：
successful-ok: no request attributes were substituted or ignored (same as Print-Job).
成功确定：未替换或忽略任何请求属性（与打印作业相同）。
successful-ok-ignored-or-substituted-attributes: same as Print-Job.
成功确定忽略或替换属性：与打印作业相同。
successful-ok-conflicting-attributes: same as Print-Job.
成功确定冲突属性：与打印作业相同。
For any of the error status codes, the Job object has not been canceled or was previously canceled.
对于任何错误状态代码，作业对象尚未取消或以前已取消。
client-error-not-possible: The request cannot be carried out because of the state of the Job object ('completed', 'canceled', or 'aborted') or the state of the system.
客户端错误不可能：由于作业对象的状态（“已完成”、“已取消”或“已中止”）或系统的状态，无法执行请求。
client-error-not-found: the target Printer and/or Job object does not exist.
找不到客户端错误：目标打印机和/或作业对象不存在。
client-error-gone: the target Printer and/or Job object no longer exists and no forwarding address is known.
客户端错误消失：目标打印机和/或作业对象不再存在，并且不知道转发地址。
client-error-request-entity-too-large: same as Print-Job, except no document data is involved.
客户端错误请求实体太大：与打印作业相同，只是不涉及文档数据。
client-error-document-format-not-supported: not applicable.
不支持客户端错误文档格式：不适用。
client-error-attributes-or-values-not-supported: not applicable, since unsupported operation attributes and values MUST be ignored.
不支持客户端错误属性或值：不适用，因为必须忽略不支持的操作属性和值。
client-error-conflicting-attributes: same as Print-Job, except that the Printer's "printer-is-accepting-jobs" attribute is not involved.
客户端错误冲突属性：与打印作业相同，只是不涉及打印机的“打印机正在接受作业”属性。
server-error-operation-not-supported: not applicable (Cancel-Job is REQUIRED).
不支持服务器错误操作：不适用（需要取消作业）。
server-error-device-error: same as Print-Job, except no document data is involved.
服务器错误设备错误：与打印作业相同，只是不涉及文档数据。
server-error-temporary-error: same as Print-Job, except no document data is involved.
服务器错误临时错误：与打印作业相同，只是不涉及文档数据。
server-error-not-accepting-jobs: not applicable.
不接受作业时发生服务器错误：不适用。
server-error-job-canceled: not applicable.
服务器错误作业已取消：不适用。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to Get-Job-Attributes with the following specializations and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码适用于获取具有以下专门化和差异的作业属性。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the requested attributes are returned in Group 3 in the response:
对于以下成功状态代码，请求的属性将在响应的组3中返回：
successful-ok: same as Get-Printer-Attributes (see section 3.1.3.1.5).
成功确定：与获取打印机属性相同（参见第3.1.3.1.5节）。
successful-ok-ignored-or-substituted-attributes: same as Get-Printer-Attributes (see section 3.1.3.1.5).
成功确定忽略或替换属性：与获取打印机属性相同（参见第3.1.3.1.5节）。
successful-ok-conflicting-attributes: same as Get-Printer-Attributes (see section 3.1.3.1.5).
成功确定冲突属性：与获取打印机属性相同（参见第3.1.3.1.5节）。
For the error status codes, Group 3 is returned containing no attributes or is not returned at all.
对于错误状态代码，返回的组3不包含属性或根本不返回。
client-error-not-possible: Same as Print-Job, in addition the Printer object is not accepting any requests.
客户端错误不可能：与打印作业相同，此外打印机对象不接受任何请求。
client-error-document-format-not-supported: not applicable.
不支持客户端错误文档格式：不适用。
client-error-attributes-or-values-not-supported: not applicable.
不支持客户端错误属性或值：不适用。
client-error-uri-scheme-not-supported: not applicable.
不支持客户端错误uri方案：不适用。
client-error-attributes-or-values-not-supported: not applicable, since unsupported operation attributes and/or values MUST be ignored and an appropriate success code returned (see above).
不支持客户端错误属性或值：不适用，因为必须忽略不支持的操作属性和/或值，并返回相应的成功代码（见上文）。
client-error-conflicting-attributes: not applicable
客户端错误冲突属性：不适用
server-error-operation-not-supported: not applicable (since Get-Job-Attributes is REQUIRED).
不支持服务器错误操作：不适用（因为需要获取作业属性）。
server-error-device-error: same as Print-Job, except no document data is involved.
服务器错误设备错误：与打印作业相同，只是不涉及文档数据。
server-error-temporary-error: sane as Print-Job, except no document data is involved..
服务器错误临时错误：与打印作业相同，但不涉及任何文档数据。。
server-error-not-accepting-jobs: not applicable.
不接受作业时发生服务器错误：不适用。
server-error-job-canceled: not applicable.
服务器错误作业已取消：不适用。
All of the Print-Job status codes described in Section 3.1.3.1.1 Print-Job Response are applicable to Hold-Job with the following specializations and differences. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中描述的所有打印作业状态代码均适用于具有以下专门化和差异的保留作业。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
For the following success status codes, the Job object is being held or has been held:
对于以下成功状态代码，作业对象正在保留或已保留：
successful-ok: no request attributes were substituted or ignored (same as Print-Job).
成功确定：未替换或忽略任何请求属性（与打印作业相同）。
successful-ok-ignored-or-substituted-attributes: same as Print-Job.
成功确定忽略或替换属性：与打印作业相同。
successful-ok-conflicting-attributes: same as Print-Job.
成功确定冲突属性：与打印作业相同。
For any of the error status codes, the Job object has not been held or was previously held.
对于任何错误状态代码，作业对象尚未保留或以前已保留。
client-error-not-possible: The request cannot be carried out because of the state of the Job object ('completed', 'canceled', or 'aborted') or the state of the system.
客户端错误不可能：由于作业对象的状态（“已完成”、“已取消”或“已中止”）或系统的状态，无法执行请求。
client-error-not-found: the target Printer and/or Job object does not exist.
找不到客户端错误：目标打印机和/或作业对象不存在。
client-error-gone: the target Printer and/or Job object no longer exists and no forwarding address is known.
客户端错误消失：目标打印机和/或作业对象不再存在，并且不知道转发地址。
client-error-request-entity-too-large: same as Print-Job, except no document data is involved.
客户端错误请求实体太大：与打印作业相同，只是不涉及文档数据。
client-error-document-format-not-supported: not applicable.
不支持客户端错误文档格式：不适用。
client-error-conflicting-attributes: same as Print-Job, except that the Printer's "printer-is-accepting-jobs" attribute is not involved.
客户端错误冲突属性：与打印作业相同，只是不涉及打印机的“打印机正在接受作业”属性。
server-error-operation-not-supported: the Hold-Job operation is not supported.
不支持服务器错误操作：不支持保留作业操作。
server-error-device-error: not applicable.
服务器错误设备错误：不适用。
server-error-temporary-error: same as Print-Job, except no document data is involved.
服务器错误临时错误：与打印作业相同，只是不涉及文档数据。
server-error-not-accepting-jobs: not applicable.
不接受作业时发生服务器错误：不适用。
server-error-job-canceled: not applicable.
服务器错误作业已取消：不适用。
All of the Print-Job status code descriptions in Section 3.1.3.1.1 Print-Job Response with the specialization's described for Hold-Job are applicable to Release-Job. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中的所有打印作业状态代码描述，以及针对保留作业所描述的专业化，均适用于发布作业。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
server-error-operation-not-supported: the Release-Job operation is not supported.
不支持服务器错误操作：不支持发布作业操作。
All of the Print-Job status code descriptions in Section 3.1.3.1.1 Print-Job Response with the specialization's described for Hold-Job are applicable to Restart-Job. See Section 13 in [RFC2911] for a more complete description of each status code.
第3.1.3.1.1节“打印作业响应”中的所有打印作业状态代码描述，以及针对保留作业所述的专门化，均适用于重新启动作业。有关每个状态代码的更完整说明，请参见[RFC2911]中的第13节。
server-error-operation-not-supported: the Restart-Job operation is not supported.
不支持服务器错误操作：不支持重新启动作业操作。
Assume I give a Create-Job request along with a set of 5 documents. All the documents get printed and the job state is moved to completed. I issue a Restart-Job request on the job. Now the issue is that, if I try to add new documents to the restarted job, will the IPP Server permit me to do so or return "client-error-not-possible " and again print those 5 jobs?
假设我给出了一个createjob请求以及一组5个文档。将打印所有文档，并将作业状态移到“已完成”。我对作业发出重新启动作业请求。现在的问题是，如果我尝试向重新启动的作业添加新文档，IPP服务器是否允许我这样做，或者返回“客户端错误不可能”，然后再次打印这5个作业？
A job can not move to the 'completed' state until all the documents have been processed. The 'last-document' flag indicates when the last document for a job is being sent from the client. This is the semantic equivalent of closing a job. No documents may be added once a job is closed. Section 3.3.7 of the IPP/1.1 model states "The job is moved to the 'pending' job state and restarts the beginning on the same IPP Printer object with the same attribute values." 'number-of-documents' is a job attribute.
在处理完所有文档之前，作业无法移动到“已完成”状态。“last document”标志指示作业的最后一个文档何时从客户端发送。这在语义上等同于关闭作业。作业关闭后，不能添加任何文档。IPP/1.1模型第3.3.7节规定：“作业被移动到“挂起”作业状态，并在具有相同属性值的同一IPP打印机对象上重新开始。”“文档数”是作业属性。
3.1.4 Returning unsupported attributes in Get-Xxxx responses (Issue 1.18)
3.1.4 在Get Xxxx响应中返回不支持的属性（问题1.18）
In the Get-Printer-Attributes, Get-Jobs, or Get-Job-Attributes responses, the client cannot depend on getting unsupported attributes returned in the Unsupported Attributes group that the client requested, but are not supported by the IPP object. However, such unsupported requested attributes will not be returned in the Job Attributes or Printer Attributes group (since they are unsupported). Furthermore, the IPP object is REQUIRED to return the 'successful-ok-ignored-or-substituted-attributes' status code, so that the client knows that not all that was requested has been returned.
在Get Printer Attributes、Get Jobs或Get Job Attributes响应中，客户端无法依赖于获取客户端请求的不支持属性组中返回的不支持属性，但IPP对象不支持这些属性。但是，这些不受支持的请求属性将不会在“作业属性”或“打印机属性”组中返回（因为它们不受支持）。此外，IPP对象需要返回“successful ok ignored or substituted attributes”（成功确定忽略或替换的属性）状态代码，以便客户端知道并非所有请求都已返回。
The [RFC2911] and [RFC2910] specifications RECOMMEND that a sender not send an empty attribute group in a request or a response. However, they REQUIRE a receiver to accept an empty attribute group as equivalent to the omission of that group. So a client SHOULD omit the Job Template Attributes group entirely in a create operation that is not supplying any Job Template attributes. Similarly, an IPP object SHOULD omit an empty Unsupported Attributes group if there are no unsupported attributes to be returned in a response.
[RFC2911]和[RFC2910]规范建议发送方不要在请求或响应中发送空属性组。但是，它们要求接收者接受一个空属性组，作为该组的省略。因此，在不提供任何作业模板属性的创建操作中，客户端应该完全忽略作业模板属性组。类似地，如果响应中没有要返回的不受支持的属性，则IPP对象应该省略空的不受支持的属性组。
The [RFC2910] specification REQUIRES a receiver to be able to receive either an empty attribute group or an omitted attribute group and treat them equivalently. The term "receiver" means an IPP object for a request and a client for a response. The term "sender' means a client for a request and an IPP object for a response.
[RFC2910]规范要求接收方能够接收空属性组或省略的属性组，并对其进行等效处理。术语“接收者”指用于请求的IPP对象和用于响应的客户端。术语“发送方”是指请求的客户端和响应的IPP对象。
There is an exception to the rule for Get-Jobs when there are no attributes to be returned. [RFC2910] contains the following paragraph:
当没有要返回的属性时，Get Jobs规则有一个例外。[RFC2910]包含以下段落：
The syntax allows an xxx-attributes-tag to be present when the xxx-attribute-sequence that follows is empty. The syntax is defined this way to allow for the response of Get-Jobs where no attributes are returned for some job-objects. Although it is RECOMMENDED that the sender not send an xxx-attributes-tag if there are no attributes (except in the Get-Jobs response just mentioned), the receiver MUST be able to decode such syntax.
当下面的xxx属性序列为空时，该语法允许出现xxx属性标记。语法是这样定义的，以允许在某些作业对象没有返回属性的情况下响应Get作业。尽管建议发送方在没有属性的情况下（除了刚才提到的Get Jobs响应之外）不要发送xxx attributes标记，但接收方必须能够解码这种语法。
3.2.1.1 Flow controlling the data portion of a Print-Job request (Issue 1.22)
3.2.1.1 控制打印作业请求数据部分的流（问题1.22）
A paused printer, or one that is stopped due to paper out or jam or spool space full or buffer space full, may flow control the data of a Print-Job operation (at the TCP/IP layer), so that the client is not able to send all the document data. Consequently, the Printer will not return a response until the condition is changed.
暂停的打印机，或因出纸、卡纸、线轴空间满或缓冲区空间满而停止的打印机，可能会控制打印作业操作的数据流（在TCP/IP层），因此客户端无法发送所有文档数据。因此，在条件改变之前，打印机不会返回响应。
The Printer should not return a Print-Job response with an error code in any of these conditions, since either the printer will be resumed and/or the condition will be freed either by human intervention or as jobs print.
打印机在任何情况下都不应返回带有错误代码的打印作业响应，因为打印机将通过人工干预或打印作业恢复和/或释放状态。
In writing test scripts to test IPP Printers, the script must also be written not to expect a response, if the printer has been paused, until the printer is resumed, in order to work with all possible implementations.
在编写测试脚本以测试IPP打印机时，如果打印机已暂停，则还必须编写脚本，以防出现响应，直到打印机恢复，以便使用所有可能的实现。
An IPP client submits a small job via Print-Job. By the time the IPP printer/print server is putting together a response to the operation, the job has finished printing and been removed as an object from the print system. What should the job-state be in the response?
IPP客户端通过打印作业提交小作业。当IPP打印机/打印服务器对操作做出响应时，作业已完成打印，并已作为对象从打印系统中删除。响应中的作业状态应该是什么？
The Model suggests that the Printer return a response before it even accepts the document content. The Job Object Attributes are returned only if the IPP object returns one of the success status codes. Then the job-state would always be "pending" or "pending-held".
该模型建议打印机在接受文档内容之前返回响应。仅当IPP对象返回一个成功状态代码时，才会返回作业对象属性。然后作业状态将始终为“挂起”或“挂起挂起”。
This issue comes up for the implementation of an IPP Printer object as a server that forwards jobs to devices that do not provide job status back to the server. If the server is reasonably certain that the job completed successfully, then it should return the job-state as 'completed'. Also the server can keep the job in its "job history" long after the job is no longer in the device. Then a user could query the server and see that the job was in the 'completed' state and completed as specified by the jobs "time-at-completed" time, which would be the same as the server submitted the job to the device.
将IPP Printer对象实现为服务器时会出现此问题，该服务器将作业转发给不向服务器提供作业状态的设备。如果服务器合理地确定作业已成功完成，则应将作业状态返回为“已完成”。此外，服务器可以在作业不再位于设备中很久之后将作业保留在其“作业历史记录”中。然后，用户可以查询服务器，查看作业是否处于“完成”状态，并按照作业“完成时的时间”时间的指定完成，这与服务器将作业提交到设备的时间相同。
An alternative is for the server to respond to the client before or while sending the job to the device, instead of waiting until the server has finished sending the job to the device. In this case, the server can return the job's state as 'pending' with the 'job-outgoing' value in the job's "job-state-reasons" attribute.
另一种方法是，服务器在将作业发送到设备之前或发送时响应客户端，而不是等到服务器完成将作业发送到设备之后。在这种情况下，服务器可以使用作业的“作业状态原因”属性中的“作业传出”值将作业状态返回为“挂起”。
If the server doesn't know for sure whether the job completed successfully (or at all), it could return the (out-of-band) 'unknown' value.
如果服务器不确定作业是否成功完成（或根本不知道），它可能会返回（带外）“未知”值。
On the other hand, if the server is able to query the device and/or setup some sort of event notification that the device initiates when the job makes state transitions, then the server can return the current job state in the Print-Job response and in subsequent queries because the server knows what the job state is in the device (or can query the device).
另一方面，如果服务器能够查询设备和/或设置设备在作业进行状态转换时启动的某种事件通知，则服务器可以在打印作业响应和后续查询中返回当前作业状态，因为服务器知道设备中的作业状态（或者可以查询设备）。
All of these alternatives depend on implementation of the server and the device.
所有这些替代方案都取决于服务器和设备的实现。
If a Printer supports the "printer-make-and-model" attribute and returns the .INF file model name of the printer in that attribute, the Microsoft client will automatically install the correct driver (if available).
如果打印机支持“打印机品牌和型号”属性并在该属性中返回打印机的.INF文件型号名称，则Microsoft客户端将自动安装正确的驱动程序（如果可用）。
Clients which poll periodically for printer status or queued-job-count should use the "requested-attributes" operation attribute to limit the scope of the query in order to save Printer and network resources.
定期轮询打印机状态或排队作业计数的客户端应使用“请求的属性”操作属性来限制查询范围，以节省打印机和网络资源。
3.2.3.1 Get-Jobs, my-jobs='true', and 'requesting-user-name' (Issue 1.39)?
3.2.3.1 获取作业、my Jobs='true'和'请求用户名'（问题1.39）？
In [RFC2911] section 3.2.6.1 'Get-Jobs Request', if the attribute 'my-jobs' is present and set to TRUE, MUST the 'requesting-user-name' attribute be there too, and if it's not present what should the IPP printer do?
在[RFC2911]第3.2.6.1节“获取作业请求”中，如果属性“我的作业”存在并设置为TRUE，“请求用户名”属性也必须存在，如果不存在，IPP打印机应该做什么？
[RFC2911] Section 8.3 describes the various cases of "requesting-user-name" being present or not for any operation. If the client does not supply a value for "requesting-user-name", the printer MUST assume that the client is supplying some anonymous name, such as "anonymous".
[RFC2911]第8.3节描述了任何操作中存在或不存在“请求用户名”的各种情况。如果客户端未提供“请求用户名”的值，则打印机必须假定客户端提供了某种匿名名称，如“匿名”。
When using the Get-Jobs operation a client implementer might choose to limit the number of jobs that the client shows on the first screenful. For example, if its UI can only display 50 jobs, it can defend itself against a printer that would otherwise return 500 jobs, perhaps taking a long time on a slow dial-up line. The client can then go and ask for a larger number of jobs in the background, while showing the user the first 50 jobs. Since the job history is returned in reverse order, namely the most recently completed jobs are returned first, the user is most likely interested in the first jobs that are returned. Limiting the number of jobs may be especially useful for a client that is requesting 'completed' jobs from a printer that keeps a long job history. Clients that don't mind sometimes getting very large responses, can omit the "limit" attribute in their Get-Jobs requests.
当使用GetJobs操作时，客户端实现者可能会选择限制客户端在第一个屏幕上显示的作业数。例如，如果它的用户界面只能显示50个作业，那么它可以保护自己不受一台打印机的影响，否则打印机将返回500个作业，这可能需要很长时间才能使用慢速拨号线路。然后，客户端可以在后台请求更多的作业，同时向用户显示前50个作业。由于作业历史以相反的顺序返回，即首先返回最近完成的作业，因此用户很可能对返回的第一个作业感兴趣。限制作业数量对于从保存长作业历史记录的打印机请求“已完成”作业的客户端可能特别有用。有时不介意获得非常大响应的客户机可以在其Get Jobs请求中忽略“limit”属性。
A Printer may respond to a Create-Job operation with "job-state" 'pending' or 'pending-held' and " job-state-reason" 'job-data-insufficient' to indicate that operation has been accepted by the Printer, but the Printer is expecting additional document data before it can move the job into the 'processing' state. Alternatively, it may respond with "job-state" 'processing' and "job-state-reason" 'job-incoming' to indicate that the Create-Job operation has been accepted by the Printer, but the Printer is expecting additional Send-Document and/or Send-URI operations and/or is accessing/accepting document data. The second alternative is for non-spooling Printers that don't implement the 'pending' state.
打印机可能会以“作业状态”“挂起”“挂起”和“作业状态原因”“作业数据不足”来响应创建作业操作，以指示打印机已接受该操作，但打印机在将作业移动到“处理”状态之前需要额外的文档数据。或者，它可以响应“作业状态”‘处理’和“作业状态原因”‘作业传入’，以指示打印机已接受创建作业操作，但打印机需要额外的发送文档和/或发送URI操作和/或正在访问/接受文档数据。第二种选择适用于不实现“挂起”状态的非后台打印打印机。
Should the server wait for the "last-document" operation attribute set to 'true' before starting to "process" the job?
在开始“处理”作业之前，服务器是否应该等待“last document”操作属性设置为“true”？
It depends on implementation. Some servers spool the entire job, including all document data, before starting to process, so such an implementation would wait for the "last-document" before starting to process the job. If the time-out occurs without the "last-document", then the server takes one of the indicated actions in section 3.3.1 in the [RFC2911] document. Other servers will start to process document data as soon as they have some. These are the so-called "non-spooling" printers. Currently, there isn't a way for a client to determine whether the Printer will spool all the data or will start to process (and print) as soon as it has some data.
这取决于执行情况。有些服务器在开始处理之前会对整个作业（包括所有文档数据）进行假脱机处理，因此这样的实现将在开始处理作业之前等待“最后一个文档”。如果在没有“最后一份文件”的情况下发生超时，则服务器将采取[RFC2911]文件第3.3.1节中规定的措施之一。其他服务器一旦有了文档数据，就会开始处理文档数据。这些是所谓的“非假脱机”打印机。目前，客户机无法确定打印机是将假脱机所有数据，还是在有数据后立即开始处理（和打印）。
The Validate-Job operation has been designed so that its implementation may be a part of the Print-Job operation. Therefore, requiring Validate-Job is not a burden on implementers. Also it is useful for client's to be able to count on its presence in all conformance implementations, so that the client can determine before sending a long document, whether the job will be accepted by the IPP Printer or not.
验证作业操作的设计使其实现可能是打印作业操作的一部分。因此，要求验证作业不是实现者的负担。此外，客户能够在所有一致性实现中依赖其存在也是很有用的，这样客户可以在发送长文档之前确定作业是否会被IPP打印机接受。
The Restart-Job operation allows the reprocessing of a completed job. Some jobs store the document data on the printer. Jobs created using the Print-Job operation are an example. It is required that the printer retains the job data after the job has moved to a 'completed state' in order for the Restart-Job operation to succeed.
重新启动作业操作允许重新处理已完成的作业。某些作业将文档数据存储在打印机上。例如，使用打印作业操作创建的作业。要求打印机在作业移动到“完成状态”后保留作业数据，以便重新启动作业操作成功。
Some jobs contain only a reference to the job data. A job created using the Print-URI is an example of such a job. When the Restart-Job operation is issued the job is reprocessed. The job data MUST be retrieved again to print the job.
某些作业仅包含对作业数据的引用。使用打印URI创建的作业就是此类作业的一个示例。发出重新启动作业操作后，将重新处理作业。必须再次检索作业数据才能打印作业。
It is possible that a job fails while attempting to access the print data. When such a job is the target of a Restart-Job the Printer SHALL attempt to retrieve the job data again.
在尝试访问打印数据时，作业可能会失败。当此类作业是重新启动作业的目标时，打印机应再次尝试检索作业数据。
4 Object Attributes
4对象属性
[RFC2911] states that the 'none' value should be used as the value of a 1setOf when the set is empty. In most cases, sets that are potentially empty contain keywords so the keyword 'none' is used, but for the 3 finishings attributes, the values are enums and thus the empty set is represented by the enum 3. Currently there are no other attributes with 1setOf values, which can be empty and can contain values that are not keywords. This exception requires special code and is a potential place for bugs. It would have been better if we had chosen an out-of-band value, either "no-value" or some new value, such as 'none'. Since we didn't, implementations have to deal with the different representations of 'none', depending on the attribute syntax.
[RFC2911]指出，当集合为空时，“无”值应用作1setOf的值。在大多数情况下，可能为空的集合包含关键字，因此使用关键字“none”，但对于3个finishings属性，值是枚举，因此空集合由枚举3表示。目前没有其他具有1setOf值的属性，这些属性可以为空，并且可以包含非关键字的值。此异常需要特殊的代码，并且可能存在bug。如果我们选择带外值，或者选择“无值”，或者选择一些新值，例如“无”，则会更好。由于我们没有这样做，实现必须根据属性语法处理“none”的不同表示。
What is the attribute syntax for a multi-valued attribute? Since some attributes support values in more than one data type, such as "media", "job-hold-until", and "job-sheets", IPP semantics associate the attribute syntax with each value, not with the attribute as a whole. The protocol associates the attribute syntax tag with each value. Don't be fooled, just because the attribute syntax tag comes before the attribute keyword. All attribute values after the first have a zero length attribute keyword as the indication of a subsequent value of the same attribute.
多值属性的属性语法是什么？由于某些属性支持多个数据类型中的值，例如“媒体”、“作业保留到”和“作业表”，因此IPP语义将属性语法与每个值关联，而不是与整个属性关联。协议将属性语法标记与每个值相关联。不要因为attributesyntax标记在attribute关键字之前就被愚弄了。第一个之后的所有属性值都有一个长度为零的属性关键字，作为同一属性的后续值的指示。
IPP client and server implementations must be aware of the diverse uppercase/lowercase nature of URIs. RFC 2396 defines URL schemes and Host names as case insensitive but reminds us that the rest of the URL may well demonstrate case sensitivity. When creating URL's for fields where the choice is completely arbitrary, it is probably best to select lower case. However, this cannot be guaranteed and implementations MUST NOT rely on any fields being case-sensitive or case-insensitive in the URL beyond the URL scheme and host name fields.
IPP客户端和服务器实现必须了解URI的不同大小写性质。RFC2396将URL方案和主机名定义为不区分大小写，但提醒我们URL的其余部分可能具有区分大小写的能力。当为完全任意选择的字段创建URL时，最好选择小写。但是，这是无法保证的，除了URL方案和主机名字段外，实现不得依赖URL中任何区分大小写或不区分大小写的字段。
The reason that the IPP specification does not make any restrictions on URIs, is so that implementations of IPP may use off-the-shelf components that conform to the standards that define URIs, such as RFC 2396 and the HTTP/1.1 specifications [RFC2616]. See these specifications for rules of matching, comparison, and case-sensitivity.
IPP规范对URI没有任何限制的原因是，IPP的实现可以使用符合定义URI的标准的现成组件，如RFC 2396和HTTP/1.1规范[RFC2616]。有关匹配、比较和区分大小写的规则，请参见这些规范。
It is also recommended that System Administrators and implementations avoid creating URLs for different printers that differ only in their case. For example, don't have Printer1 and printer1 as two different IPP Printers.
还建议系统管理员和实现避免为不同的打印机创建URL，这些打印机仅在其情况下有所不同。例如，不要将Printer1和Printer1作为两个不同的IPP打印机。
Example of equivalent URI's
等效URI的示例
http://abc.com:80/~smith/home.html
http://abc.com:80/~smith/home.html
http://ABC.com/%7Esmith/home.html
http://ABC.com/%7Esmith/home.html
http:/ABC.com:/%7esmith/home.html
http:/ABC.com:/%7esmith/home.html
Example of equivalent URI's using the IPP scheme
使用IPP方案的等效URI示例
ipp://abc.com:631/~smith/home.html
ipp://abc.com:631/~smith/home.html
ipp://ABC.com/%7Esmith/home.html
ipp://ABC.com/%7Esmith/home.html
http:/ABC.com:631/%7esmith/home.html
http:/ABC.com:631/%7esmith/home.html
The HTTP/1.1 specification [RFC2616] contains more details on comparing URLs.
HTTP/1.1规范[RFC2616]包含有关比较URL的更多详细信息。
The 'textWithLanguage' and 'nameWithLanguage' are compound syntaxes that have two components. The first component is the 'language' component that can contain up to 63 octets. The second component is the 'text' or 'name' component. The maximum length of these are 1023 octets and 255 octets respectively. The definition of attributes with either syntax may further restrict the length (e.g., printer-name (name(127))).
“textWithLanguage”和“nameWithLanguage”是具有两个组件的复合语法。第一个组件是“语言”组件，最多可包含63个八位字节。第二个组件是“文本”或“名称”组件。它们的最大长度分别为1023个八位字节和255个八位字节。使用任一语法定义属性可能会进一步限制长度（例如，打印机名称（名称（127）））。
The length of the 'language' component has no effect on the allowable length of 'text' in 'textWithLanguage' or the length of 'name' in 'nameWithLanguage'
“语言”组件的长度对“textWithLanguage”中允许的“文本”长度或“nameWithLanguage”中允许的“名称”长度没有影响
IPP/1.0 is silent on which of the four effects an implementation would perform if it supports Create-Job, but does not support "multiple-document-handling" or multiple documents per job. IPP/1.1 was changed so that a Printer could support Create-Job without having to support multiple document jobs. The "multiple-document-jobs-supported" (boolean) Printer description attribute was added to IPP/1.1 along with the 'server-error-multiple-document-jobs-not-supported' status code for a Printer to indicate whether or not it supports multiple document jobs, when it supports the Create-Job operation. Also IPP/1.1 was clarified that the Printer MUST support the "multiple-document-handling" (type2 keyword) Job Template attribute with at least one value if the Printer supports multiple documents per job.
如果IPP/1.0支持创建作业，但不支持“多文档处理”或每个作业有多个文档，那么它对实现将执行的四种效果中的哪一种没有说明。IPP/1.1已更改，因此打印机可以支持创建作业，而无需支持多个文档作业。IPP/1.1中添加了“支持多个文档作业”（布尔值）打印机描述属性以及打印机的“服务器错误不支持多个文档作业”状态代码，以指示打印机在支持创建作业操作时是否支持多个文档作业。此外，IPP/1.1还阐明，如果打印机支持每个作业多个文档，则打印机必须至少支持一个值的“多文档处理”（type2关键字）作业模板属性。
The "date-time-at-creation", "date-time-at-processing", and "date-time-at-completed" attributes are returned as dateTime syntax. These attributes are OPTIONAL for a Printer to support. However, there are
“创建时的日期时间”、“处理时的日期时间”和“完成时的日期时间”属性作为日期时间语法返回。这些属性是打印机支持的可选属性。然而，有
various ways for a Printer to get the date and time of day. Some suggestions:
打印机获取日期和时间的各种方法。一些建议：
1. A Printer can get time from an NTP timeserver if there's one reachable on the network . See RFC 1305. Also DHCP option 32 in RFC 2132 returns the IP address of the NTP server.
1. 如果网络上有可以访问的NTP时间服务器，则打印机可以从NTP时间服务器获取时间。见RFC 1305。RFC 2132中的DHCP选项32还返回NTP服务器的IP地址。
2. Get the date and time at startup from a human operator
2. 从人工操作员处获取启动日期和时间
3. Have an operator set the date and time using a web administrative interface
3. 让操作员使用web管理界面设置日期和时间
4. Get the date and time from incoming HTTP requests, though the problems of spoofing need to be considered. Perhaps comparing several HTTP requests could reduce the chances of spoofing.
4. 从传入的HTTP请求中获取日期和时间，但需要考虑欺骗问题。也许比较几个HTTP请求可以减少欺骗的机会。
5. Internal date time clock battery driven.
5. 内部日期时间时钟由电池驱动。
6. Query "http://tycho.usno.navy.mil/cgi-bin/timer.pl"
6. 查询“http://tycho.usno.navy.mil/cgi-bin/timer.pl"
The reason that "queued-job-count" is RECOMMENDED, is that some clients look at that attribute alone when summarizing the status of a list of printers, instead of doing a Get-Jobs to determine the number of jobs in the queue. Implementations that fail to support the "queued-job-count" will cause that client to display 0 jobs when there are actually queued jobs.
建议使用“排队作业计数”的原因是，某些客户端在汇总打印机列表的状态时仅查看该属性，而不是执行Get Jobs来确定队列中的作业数。不支持“排队作业计数”的实现将导致该客户端在实际存在排队作业时显示0个作业。
We would have made it a REQUIRED Printer attribute, but some implementations had already been completed before the issue was raised, so making it a SHOULD was a compromise.
我们本来会将其作为必需的打印机属性，但在提出问题之前，一些实现已经完成，因此将其作为一个应该是一种折衷。
4.4.1.2 Is "queued-job-count" a good measure of how busy a printer is (Issue 1.15)?
4.4.1.2 “排队作业计数”是衡量打印机繁忙程度的一个好方法吗（问题1.15）？
The "queued-job-count" is not a good measure of how busy the printer is when there are held jobs. A future registration could be to add a "held-job-count" (or an "active-job-count") Printer Description attribute if experience shows that such an attribute (combination) is needed to quickly indicate how busy a printer really is.
“排队作业计数”不能很好地衡量有保留作业时打印机的繁忙程度。如果经验表明需要添加“保持作业计数”（或“活动作业计数”）打印机描述属性（组合）以快速指示打印机的实际繁忙程度，则将来的注册可能是添加“保持作业计数”（或“活动作业计数”）打印机描述属性。
A Printer implementation MAY support this attribute by obtaining the date and time by any number of implementation-dependent means at startup or subsequently. Examples include:
打印机实现可通过在启动时或之后通过任何数量的依赖于实现的方式获取日期和时间来支持此属性。例子包括：
1. an internal date time clock,
1. 内部日期时钟，
2. from the operator at startup using the console,
2. 操作员在启动时使用控制台，
3. from an operator using an administrative web page,
3. 来自使用管理网页的操作员，
4. from HTTP headers supplied in client requests,
4. 从客户端请求中提供的HTTP头，
5. use HTTP to query "http://tycho.usno.navy.mil/cgi-bin/timer.pl"
5. 使用HTTP查询“http://tycho.usno.navy.mil/cgi-bin/timer.pl"
6. from the network, using NTP [RFC1305] or DHCP option 32 [RFC2132] that returns the IP address of the NTP server.
6. 使用NTP[RFC1305]或DHCP选项32[RFC2132]从网络返回NTP服务器的IP地址。
If an implementation supports this attribute by obtaining the current time from the network (at startup or later), but the time is not available, then the implementation MUST return the value of this attribute using the out-of-band 'no-value' meaning not configured. See the beginning of section 4.1.
如果实现通过从网络获取当前时间（启动时或以后）来支持此属性，但时间不可用，则实现必须使用带外“无值”返回此属性的值，表示未配置。见第4.1节开头部分。
Since the new "date-and-time-at-xxx" Job Description attributes refer to the "printer-current-time", they will be covered also.
由于新的“xxx日期和时间”职务描述属性指的是“打印机当前时间”，因此也将涵盖这些属性。
Must the operational attribute for printer-uri match one of the values in "printer-uri-supported"?
打印机uri的操作属性必须与“支持的打印机uri”中的一个值匹配吗？
A forgiving printer implementation would not reject the operation. But the implementation has its rights to reject a printer or job operation if the operational attribute printer-uri is not a value of the printer-uri-supported. The printer might not be improperly configured. The request obviously reached the printer. The printer could treat the printer-uri as the logical equivalent of a value in the printer-uri-supported. It would be implementation dependent for which value, and associated security policy, would apply. This does also apply to a job object specified with a printer-uri and job-id, or with a job-uri. See section 4.1.3 for how to compare URI's.
宽容的打印机实现不会拒绝该操作。但是，如果操作属性printer uri不是受支持的打印机uri的值，则实现有权拒绝打印机或作业操作。打印机可能未正确配置。显然，这一请求已到达打印机。打印机可以将打印机uri视为支持的打印机uri中的值的逻辑等价物。它将取决于应用哪个值和相关的安全策略的实现。这也适用于使用打印机uri和作业id或作业uri指定的作业对象。有关如何比较URI的信息，请参见第4.1.3节。
The IPP object model does not prohibit a job that contains no documents. Such a job may be created in a number of ways including a 'create-job' followed by an 'add-document' that contains no data and has the 'last-document' flag set.
IPP对象模型不禁止不包含文档的作业。可以通过多种方式创建这样的作业，包括“创建作业”，后跟不包含数据且设置了“最后一个文档”标志的“添加文档”。
An empty job is processed just as any other job. The operation that "closes" an empty job is not rejected because the job is empty. If no other conditions exist, other than the job is empty, the response to the operation will indicate success. After the job is scheduled and processed, the job state SHALL be 'completed'.
空作业的处理方式与任何其他作业相同。“关闭”空作业的操作不会因为作业为空而被拒绝。如果除作业为空外，不存在其他条件，则对操作的响应将指示成功。计划和处理作业后，作业状态应为“已完成”。
There will be some variation in the value(s) of the "job-state-reasons" attribute. It is required that if no conditions, other than the job being empty, exist the "job-state-reasons" SHALL include the
“作业状态原因”属性的值会有一些变化。如果不存在除工作为空以外的任何条件，“工作状态原因”应包括
'completed-successfully'. If other conditions existed, the 'completed-with-warnings' or 'completed-with-errors' values may be used.
“已成功完成”。如果存在其他条件，则可以使用“已完成但有警告”或“已完成但有错误”值。
5 Directory Considerations
5目录注意事项
The [RFC2911] document lists RECOMMENDED and OPTIONAL Printer object attributes for directory schemas. See [RFC2911] APPENDIX E: Generic Directory Schema.
[RFC2911]文档列出了目录架构的推荐和可选打印机对象属性。参见[RFC2911]附录E：通用目录模式。
The SLP printer template is defined in the "Definition of the Printer Abstract Service Type v2.0" document [svrloc-printer]. The LDAP printer template is defined in the "Internet Printing Protocol (IPP): LDAP Schema for Printer Services" document [ldap-printer]. Both documents systematically add "printer-" to any attribute that doesn't already start with "printer-" in order to keep the printer directory attributes distinct from other directory attributes. Also, instead of using "printer-uri-supported", "uri-authentication-supported", and "uri-security-supported", they use a "printer-xri-supported" attribute with special syntax to contain all of the same information in a single attribute.
SLP打印机模板在“打印机抽象服务类型v2.0的定义”文档[svrloc打印机]中定义。LDAP打印机模板在“Internet打印协议（IPP）：打印机服务LDAP架构”文档[LDAP打印机]中定义。这两个文档都系统地将“打印机-”添加到任何尚未以“打印机-”开头的属性中，以使打印机目录属性与其他目录属性不同。此外，它们不使用“支持的打印机uri”、“支持的uri身份验证”和“支持的uri安全性”，而是使用具有特殊语法的“支持的打印机xri”属性在单个属性中包含所有相同的信息。
If the IPP printer has a DNS name should there be at least two values for the printer-uri-supported attribute. One URL with the fully qualified DNS name the other with the IP address in the URL?
如果IPP打印机具有DNS名称，则支持的打印机uri属性应至少有两个值。一个URL具有完全限定的DNS名称，另一个URL中具有IP地址？
The printer may contain one or the other or both. It's up to the administrator to configure this attribute.
打印机可以包含一个或另一个，也可以同时包含两个。由管理员配置此属性。
6 Security Considerations
6安全考虑
The security considerations given in [RFC2911] Section 8 "Security Considerations" all apply to this document. In addition, the following sub-sections describes security consideration that have arisen as a result of implementation testing.
[RFC2911]第8节“安全注意事项”中给出的安全注意事项均适用于本文件。此外，以下小节描述了由于实现测试而产生的安全考虑。
6.1 Querying jobs with IPP that were submitted using other job submission protocols (Issue 1.32)
6.1 使用IPP查询使用其他作业提交协议提交的作业（问题1.32）
The following clarification was added to [RFC2911] section 8.5:
[RFC2911]第8.5节增加了以下澄清：
8.5 Queries on jobs submitted using non-IPP protocols If the device that an IPP Printer is representing is able to accept jobs using other job submission protocols in addition to IPP, it is RECOMMEND that such an implementation at least allow such "foreign" jobs to be queried using Get-Jobs returning "job-id" and "job-uri" as 'unknown'. Such an implementation NEED NOT support all of the same IPP job attributes as for IPP jobs. The IPP object returns the 'unknown' out-of-band value for any requested attribute of a foreign job that is supported for IPP jobs, but not for foreign jobs.
8.5 对使用非IPP协议提交的作业的查询如果IPP打印机所代表的设备能够接受除IPP之外使用其他作业提交协议的作业，则建议这样的实现至少允许使用返回“作业id”和“作业uri”为“未知”的Get作业来查询此类“外来”作业。这种实现不需要支持与IPP作业相同的所有IPP作业属性。IPP对象返回IPP作业支持但不支持外部作业的外部作业的任何请求属性的“未知”带外值。
It is further RECOMMENDED, that the IPP Printer generate "job-id" and "job-uri" values for such "foreign jobs", if possible, so that they may be targets of other IPP operations, such as Get-Job-Attributes and Cancel-Job. Such an implementation also needs to deal with the problem of authentication of such foreign jobs. One approach would be to treat all such foreign jobs as belonging to users other than the user of the IPP client. Another approach would be for the foreign job to belong to 'anonymous'. Only if the IPP client has been authenticated as an operator or administrator of the IPP Printer object, could the foreign jobs be queried by an IPP request. Alternatively, if the security policy were to allow users to query other users' jobs, then the foreign jobs would also be visible to an end-user IPP client using Get-Jobs and Get-Job- Attributes.
进一步建议，如果可能，IPP打印机为此类“外部作业”生成“作业id”和“作业uri”值，以便它们可能成为其他IPP操作的目标，例如获取作业属性和取消作业。这种实施还需要处理此类外国工作的认证问题。一种方法是将所有此类外来作业视为属于IPP客户端用户以外的用户。另一种方法是让外国工作属于“匿名”。只有当IPP客户端已作为IPP打印机对象的操作员或管理员进行身份验证时，IPP请求才能查询外部作业。或者，如果安全策略允许用户查询其他用户的作业，则最终用户IPP客户端也可以使用Get jobs和Get Job-Attributes查看外部作业。
Thus IPP MAY be implemented as a "universal" protocol that provides access to jobs submitted with any job submission protocol. As IPP becomes widely implemented, providing a more universal access makes sense.
因此，IPP可以实现为“通用”协议，提供对使用任何作业提交协议提交的作业的访问。随着IPP的广泛实施，提供更普遍的接入是有意义的。
7 Encoding and Transport
7编码和传输
This section discusses various aspects of IPP/1.1 Encoding and Transport [RFC2910].
本节讨论IPP/1.1编码和传输[RFC2910]的各个方面。
A server is not required to send a response until after it has received the client's entire request. Hence, a client must not expect a response until after it has sent the entire request. However, we recommend that the server return a response as soon as possible if an error is detected while the client is still sending the data, rather than waiting until all of the data is received. Therefore, we also recommend that a client listen for an error response that an IPP server MAY send before it receives all the data. In this case a client, if chunking the data, can send a premature zero-length chunk to end the request before sending all the data (and so the client can keep the connection open for other requests, rather than closing it). If the request is blocked for some reason, a client MAY determine the reason by opening another connection to query the server using Get-Printer-Attributes.
服务器在收到客户端的整个请求之前，不需要发送响应。因此，客户端必须在发送整个请求之后才能期望响应。但是，如果在客户端仍在发送数据时检测到错误，我们建议服务器尽快返回响应，而不是等到收到所有数据。因此，我们还建议客户端在接收所有数据之前侦听IPP服务器可能发送的错误响应。在这种情况下，如果客户机对数据进行分块，则可以在发送所有数据之前发送一个过早的零长度分块来结束请求（因此客户机可以为其他请求保持连接打开，而不是关闭连接）。如果请求因某种原因被阻止，客户端可以通过打开另一个连接来确定原因，以使用“获取打印机属性”查询服务器。
IPP, by design, uses TCP's built-in flow control mechanisms [RFC 793] to throttle clients when Printers are busy. Therefore, it is perfectly normal for an IPP client transmitting a Job to be blocked for a really long time. Accordingly, socket timeouts must be avoided. Some socket implementations have a timeout option, which specifies how long a write operation on a socket can be blocked before it times out and the blocking ends. A client should set this option for infinite timeout when transmitting Job submissions.
IPP在设计上使用TCP的内置流量控制机制[RFC 793]在打印机忙时限制客户端。因此，IPP客户端传输作业被阻塞很长时间是完全正常的。因此，必须避免插座超时。一些套接字实现具有超时选项，该选项指定套接字上的写入操作在超时和阻塞结束之前可以被阻塞多长时间。客户端在传输作业提交时应将此选项设置为无限超时。
Some IPP client applications might be able to perform other useful work while a Job transmission is blocked. For example, the client may have other jobs that it could transmit to other Printers simultaneously. A client may have a GUI, which must remain responsive to the user while the Job transmission is blocked. These clients should be designed to spawn a thread to handle the Job transmission at its own pace, leaving the main application free to do other work. Alternatively, single-threaded applications could use non-blocking I/O.
当作业传输被阻止时，某些IPP客户端应用程序可能能够执行其他有用的工作。例如，客户端可能有其他作业，可以同时传输到其他打印机。客户端可能有GUI，在作业传输被阻止时，GUI必须对用户保持响应。这些客户机应该设计为产生一个线程，以自己的速度处理作业传输，让主应用程序自由地执行其他工作。或者，单线程应用程序可以使用非阻塞I/O。
Some Printer conditions, such as jam or lack of paper, could cause a client to be blocked indefinitely. Clients may open additional connections to the Printer to Get-Printer-Attributes, determine the state of the device, alert a user if the printer is stopped, and let a user decide whether to abort the job transmission or not.
某些打印机状况（如卡纸或缺纸）可能会导致客户端无限期被阻塞。客户端可以打开与打印机的附加连接，以获取打印机属性、确定设备状态、在打印机停止时向用户发出警报，并让用户决定是否中止作业传输。
In the following sections, there are tables of all HTTP headers, which describe their use in an IPP client or server. The following is an explanation of each column in these tables.
在以下部分中，有所有HTTP头的表，这些表描述了它们在IPP客户端或服务器中的使用。以下是这些表中每列的说明。
- the "header" column contains the name of a header - the "request/client" column indicates whether a client sends the header. - the "request/ server" column indicates whether a server supports the header when received. - the "response/ server" column indicates whether a server sends the header. - the "response /client" column indicates whether a client supports the header when received. - the "values and conditions" column specifies the allowed header values and the conditions for the header to be present in a request/response.
- “标头”列包含标头的名称-“请求/客户端”列指示客户端是否发送标头。-“请求/服务器”列指示服务器在接收时是否支持标头。-“响应/服务器”列指示服务器是否发送标头。-“响应/客户端”列指示客户端在接收时是否支持标头。-“值和条件”列指定请求/响应中允许的标头值和标头存在的条件。
The table for "request headers" does not have columns for responses, and the table for "response headers" does not have columns for requests.
“请求标头”表中没有响应列，“响应标头”表中没有请求列。
The following is an explanation of the values in the "request/client" and "response/ server" columns.
以下是对“请求/客户端”和“响应/服务器”列中的值的说明。
- must: the client or server MUST send the header, - must-if: the client or server MUST send the header when the condition described in the "values and conditions" column is met, - may: the client or server MAY send the header - not: the client or server SHOULD NOT send the header. It is not relevant to an IPP implementation.
- 必须：客户端或服务器必须发送标头，-必须如果：当满足“值和条件”列中描述的条件时，客户端或服务器必须发送标头，-可能：客户端或服务器可以发送标头-不：客户端或服务器不应发送标头。它与IPP实施无关。
The following is an explanation of the values in the "response/client" and "request/ server" columns.
以下是对“响应/客户端”和“请求/服务器”列中的值的说明。
- must: the client or server MUST support the header, - may: the client or server MAY support the header - not: the client or server SHOULD NOT support the header. It is not relevant to an IPP implementation.
- 必须：客户端或服务器必须支持标头，-may:客户端或服务器可能支持标头-not:客户端或服务器不应支持标头。它与IPP实施无关。
The following is a table for the general headers.
下表列出了常规标题。
General- Request Response Values and Conditions Header
常规-请求-响应值和条件标头
Client Server Server Client
客户端服务器客户端
Cache- not must not "no-cache" only Control must
缓存-不能“没有缓存”只能控制
Connection must- must must- must "close" only. Both if if client and server SHOULD keep a connection for the duration of a sequence of operations. The client and server MUST include this header for the last operation in such a sequence.
连接必须-必须-只能“关闭”。在一系列操作期间，客户端和服务器都应保持连接。客户机和服务器必须在这样的序列中的最后一个操作中包含此标头。
Date may may must may per RFC 1123 [RFC1123] from RFC 2616 [RFC2616]
根据RFC 1123[RFC1123]从RFC 2616[RFC2616]开始的日期可能必须为5月
Pragma must not must not "no-cache" only
Pragma不能仅为“无缓存”
Transfer- must- must must- must "chunked" only. Header Encoding if if MUST be present if Content-Length is absent.
仅传输-必须-必须-必须“分块”。如果缺少内容长度，则必须存在标题编码。
Upgrade not not not not
不升级
Via not not not not
Via not
The following is a table for the request headers.
下表列出了请求头。
Request- Client Server Request Values and Conditions Header
请求-客户端服务器请求值和条件标头
Accept may must "application/ipp" only. This value is the default if the client omits it
仅接受“申请/ipp”。如果客户端忽略此值，则此值为默认值
Accept- not not Charset information is within the Charset application/ipp entity
接受-非字符集信息在字符集应用程序/ipp实体中
Accept- may must empty and per RFC 2616 [RFC2616] Encoding and IANA registry for content-codings
接受-可能必须为空，并且按照RFC 2616[RFC2616]编码和IANA注册表进行内容编码
Accept- not not language information is within the Language application/ipp entity
接受-非语言信息在语言应用程序/ipp实体中
Authorization must- must per RFC 2616. A client MUST send if this header when it receives a 401 "Unauthorized" response and does not receive a "Proxy-Authenticate" header.
授权必须-必须符合RFC 2616。当客户端收到401“未经授权”响应且未收到“代理身份验证”标头时，必须发送此标头。
From not not per RFC 2616. Because RFC recommends sending this header only with the user's approval, it is not very useful
不符合RFC 2616的要求。因为RFC建议仅在用户批准的情况下发送此标题，所以它不是很有用
Host must must per RFC 2616
主机必须符合RFC 2616的要求
If-Match not not
如果不匹配
If-Modified- not not Since
如果已修改-未自
If-None-Match not not
如果没有匹配，则不匹配
If-Range not not
如果范围不是
If- not not Unmodified-Since
如果-不是未修改的，因为
Request- Client Server Request Values and Conditions Header
请求-客户端服务器请求值和条件标头
Max-Forwards not not
马克斯没有
Proxy- must- not per RFC 2616. A client MUST send Authorizati if this header when it receives a on 401 "Unauthorized" response and a "Proxy-Authenticate" header.
代理-必须-不符合RFC 2616。当客户端收到on 401“Unauthorized”响应和“Proxy Authenticate”报头时，必须发送Authorizati if此报头。
Range not not
范围不
Referrer not not
推荐人不是
User-Agent not not
用户代理不是
The following is a table for the request headers.
下表列出了请求头。
Response- Server Client Response Values and Conditions Header
响应-服务器客户端响应值和条件标头
Accept-Ranges not not
不接受范围
Age not not
年龄不是
Location must- may per RFC 2616. When URI needs if redirection.
位置必须-可根据RFC 2616。当URI需要if重定向时。
Proxy- must per RFC 2616 Authenticat e not
代理-必须根据RFC 2616进行身份验证
Public may may per RFC 2616
公众可根据RFC 2616进行
Retry-After may may per RFC 2616
根据RFC 2616，5月后重试
Server not not
服务器不是
Vary not not
不改变
Warning may may per RFC 2616
根据RFC 2616，可能会出现警告
WWW- must- must per RFC 2616. When a server needs Authenticate if to authenticate a client.
WWW-must-must符合RFC 2616。当服务器需要验证时，如果要验证客户端。
The following is a table for the entity headers.
下表列出了实体标题。
Entity-Header Request Response Values and Conditions
实体头请求响应值和条件
Client Server Server Client
客户端服务器客户端
Allow not not not not
不允许
Content-Base not not not not
内容库不是
Content- may must must must per RFC 2616 and Encoding IANA registry for content codings.
内容-可能必须按照RFC 2616和编码IANA注册中心进行内容编码。
Content- not not not not Application/ipp Language handles language
内容-非应用程序/ipp语言处理语言
Content- must- must must- must the length of the Length if if message-body per RFC 2616. Header MUST be present if Transfer-Encoding is absent..
Content-must-must-must是根据RFC 2616的长度if-if消息体的长度。如果缺少传输编码，则必须存在标头。。
Content- not not not not Location
内容-非位置
Content-MD5 may may may may per RFC 2616
Content-MD5可能符合RFC 2616
Content-Range not not not not
内容范围不
Content-Type must must must must "application/ipp" only
内容类型只能是“应用程序/ipp”
ETag not not not not
埃塔格不是
Expires not not not not
过期不
Last-Modified not not not not
上次修改的不是
IPP implementations consist of an HTTP layer and an IPP layer. In the following discussion, the term "client" refers to the HTTP client layer and the term "server" refers to the HTTP server layer. The Encoding and Transport document [RFC2910] requires that HTTP 1.1 MUST be supported by all clients and all servers. However, a client and/or a server implementation may choose to also support HTTP 1.0.
IPP实现由HTTP层和IPP层组成。在下面的讨论中，术语“客户端”指HTTP客户端层，术语“服务器”指HTTP服务器层。编码和传输文档[RFC2910]要求所有客户端和服务器都必须支持HTTP 1.1。但是，客户机和/或服务器实现也可以选择支持HTTP 1.0。
This option means that a server may choose to communicate with a (non-conforming) client that only supports HTTP 1.0. In such cases the server should not use any HTTP 1.1 specific parameters or features and should respond using HTTP version number 1.0.
此选项意味着服务器可以选择与仅支持HTTP 1.0的（不一致的）客户端通信。在这种情况下，服务器不应使用任何HTTP 1.1特定的参数或功能，而应使用HTTP版本号1.0进行响应。
This option also means that a client may choose to communicate with a (non-conforming) server that only supports HTTP 1.0. In such cases, if the server responds with an HTTP 'unsupported version number' to an HTTP 1.1 request, the client should retry using HTTP version number 1.0.
此选项还意味着客户端可以选择与仅支持HTTP 1.0的（不一致的）服务器通信。在这种情况下，如果服务器以HTTP“不支持的版本号”响应HTTP 1.1请求，则客户端应使用HTTP版本号1.0重试。
Clients MUST anticipate that the HTTP/1.1 server may chunk responses and MUST accept them in responses. However, a (non-conforming) HTTP client that is unable to accept chunked responses may attempt to request an HTTP 1.1 server not to use chunking in its response to an operation by using the following HTTP header:
客户端必须预期HTTP/1.1服务器可能会对响应进行分块，并且必须在响应中接受它们。但是，无法接受分块响应的（非一致性）HTTP客户端可能会尝试使用以下HTTP标头请求HTTP 1.1服务器在其对操作的响应中不使用分块：
TE: identity
TE：身份
This mechanism should not be used by a server to disable a client from chunking a request, since chunking of document data is an important feature for clients to send long documents.
服务器不应使用此机制来禁止客户端对请求进行分块，因为文档数据分块是客户端发送长文档的一个重要功能。
This section describes some problems with the use of chunked requests and HTTP/1.1 servers.
本节描述了使用分块请求和HTTP/1.1服务器时的一些问题。
The HTTP/1.1 standard [RFC2616] requires that conforming servers support chunked requests for any method. However, in spite of this requirement, some HTTP/1.1 implementations support chunked responses in the GET method, but do not support chunked POST method requests. Some HTTP/1.1 implementations that support CGI scripts [CGI] and/or servlets [Servlet] require that the client supply a Content-Length. These implementations might reject a chunked POST method and return a
HTTP/1.1标准[RFC2616]要求一致性服务器支持任何方法的分块请求。然而，尽管有这一要求，一些HTTP/1.1实现支持GET方法中的分块响应，但不支持分块POST方法请求。一些支持CGI脚本[CGI]和/或Servlet[Servlet]的HTTP/1.1实现要求客户端提供内容长度。这些实现可能会拒绝分块POST方法并返回
411 status code (Length Required), might attempt to buffer the request and run out of room returning a 413 status code (Request Entity Too Large), or might successfully accept the chunked request.
411状态代码（需要长度），可能尝试缓冲请求并返回413状态代码（请求实体太大），或者可能成功接受分块请求。
Because of this lack of conformance of HTTP servers to the HTTP/1.1 standard, the IPP standard [RFC2910] REQUIRES that a conforming IPP Printer object implementation support chunked requests and that conforming clients accept chunked responses. Therefore, IPP object implementers are warned to seek HTTP server implementations that support chunked POST requests in order to conform to the IPP standard and/or use implementation techniques that support chunked POST requests.
由于HTTP服务器与HTTP/1.1标准不一致，IPP标准[RFC2910]要求一致的IPP打印机对象实现支持分块请求，并且一致的客户端接受分块响应。因此，IPP对象实现者被警告寻求支持分块POST请求的HTTP服务器实现，以符合IPP标准和/或使用支持分块POST请求的实现技术。
8 References
8参考文献
[CGI] CGI/1.1 (http://www.w3.org/CGI/).
[CGI]CGI/1.1(http://www.w3.org/CGI/).
[IANA-CS] IANA Registry of Coded Character Sets:
http://www.iana.org/assignments/character-sets
[IANA-CS] IANA Registry of Coded Character Sets:
http://www.iana.org/assignments/character-sets
[ldap-printer] Fleming, P., Jones, K., Lewis, H. and I. McDonald, "Internet Printing Protocol (IPP): LDAP Schema for Printer Services", Work in Progress.
[ldap打印机]Fleming，P.，Jones，K.，Lewis，H.和I.McDonald，“互联网打印协议（IPP）：打印机服务的ldap模式”，正在进行中。
[RFC793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981.
[RFC793]Postel，J.，“传输控制协议”，标准7，RFC 793，1981年9月。
[RFC1123] Braden, R., "Requirements for Internet Hosts - Application and Support", RFC 1123, October, 1989.
[RFC1123]Braden，R.，“互联网主机的要求-应用和支持”，RFC1123，1989年10月。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[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月。
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RFC2396]Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。
[RFC2565] DeBry, R., Hastings, T., Herriot, R., Isaacson, S. and P. Powell, "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, April 1999.
[RFC2565]DeBry，R.，Hastings，T.，Herriot，R.，Isaacson，S.和P.Powell，“互联网打印协议/1.0：模型和语义”，RFC 2566，1999年4月。
[RFC2566] Herriot, R., Butler, S., Moore, P. and R. Turner, "Internet Printing Protocol/1.0: Encoding and Transport", RFC 2565, April 1999.
[RFC2566]Herriot，R.，Butler，S.，Moore，P.和R.Turner，“互联网打印协议/1.0：编码和传输”，RFC 25651999年4月。
[RFC2567] Wright, D., "Design Goals for an Internet Printing Protocol", RFC 2567, April 1999.
[RFC2567]Wright，D.，“互联网打印协议的设计目标”，RFC2567，1999年4月。
[RFC2568] Zilles, S., "Rationale for the Structure and 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月。
[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. and R. Turner, "Internet Printing Protocol/1.0: Encoding and Transport", RFC 2910, September, 2000.
[RFC2910]Herriot，R.，Butler，S.，Moore，P.和R.Turner，“互联网打印协议/1.0：编码和传输”，RFC 29102000年9月。
[RFC2911] DeBry, R., Hastings, T., Herriot, R., Isaacson, S. and P. Powell, "Internet Printing Protocol/1.0: Model and Semantics", RFC 2911, September, 2000.
[RFC2911]DeBry，R.，Hastings，T.，Herriot，R.，Isaacson，S.和P.Powell，“互联网打印协议/1.0：模型和语义”，RFC 29112000年9月。
[Servlet] Servlet Specification Version 2.1 (http://java.sun.com/products/servlet/2.1/ index.html).
[Servlet]Servlet规范版本2.1(http://java.sun.com/products/servlet/2.1/ index.html）。
[svrloc-printer] St. Pierre, P., Isaacson, S., McDonald, I., "Definition of the Printer Abstract Service Type v2.0", http://www.isi.edu/in-notes/iana/assignments/svrloc-templates/printer.2.0.en (IANA Registered, May 27, 2000).
[svrloc打印机]圣皮埃尔，P.，艾萨克森，S.，麦当劳，I.，“打印机抽象服务类型v2.0的定义”，http://www.isi.edu/in-notes/iana/assignments/svrloc-templates/printer.2.0.en （IANA注册，2000年5月27日）。
[SSL] Netscape, The SSL Protocol, Version 3, (Text version 3.02), November 1996.
[SSL]Netscape，SSL协议，版本3，（文本版本3.02），1996年11月。
Thomas N. Hastings Xerox Corporation 701 Aviation Blvd. El Segundo, CA 90245
托马斯·黑斯廷斯施乐公司航空大道701号。加利福尼亚州塞贡多市，邮编90245
EMail: hastings@cp10.es.xerox.com
EMail: hastings@cp10.es.xerox.com
Carl-Uno Manros Independent Consultant 1601 N. Sepulveda Blvd. #505 Manhattan Beach, CA 90266
卡尔·乌诺·曼罗斯独立顾问，西普韦达大道北1601号#加利福尼亚州曼哈顿海滩505号，邮编90266
Email: carl@manros.com
Email: carl@manros.com
Carl Kugler Mail Stop 003G IBM Printing Systems Co 6300 Diagonal Hwy Boulder CO 80301
卡尔·库格勒邮政站003G IBM印刷系统公司6300斜交公路博尔德公司80301
EMail: Kugler@us.ibm.com
EMail: Kugler@us.ibm.com
Henrik Holst i-data Printing Systems Vadstrupvej 35-43 2880 Bagsvaerd, Denmark
丹麦巴格斯瓦尔德Henrik Holst i-data打印系统Vadstrupvej 35-43 2880
EMail: hh@I-data.com
EMail: hh@I-data.com
Peter Zehler Xerox Corporation 800 Philips Road Webster, NY 14580
彼得·泽勒·施乐公司，纽约州韦伯斯特飞利浦路800号，邮编14580
EMail: PZehler@crt.xerox.com
EMail: PZehler@crt.xerox.com
IPP Web Page: http://www.pwg.org/ipp/
IPP Mailing List: ipp@pwg.org
IPP Web Page: http://www.pwg.org/ipp/
IPP Mailing List: ipp@pwg.org
To subscribe to the ipp mailing list, send the following email:
要订阅ipp邮件列表，请发送以下电子邮件：
1) send it to majordomo@pwg.org 2) leave the subject line blank 3) put the following two lines in the message body: subscribe ipp end
1) 寄到majordomo@pwg.org2）主题行留空3）在消息正文中插入以下两行：subscribe ipp end
Implementers of this specification document are encouraged to join the IPP Mailing List in order to participate in any discussions of clarification issues and review of registration proposals for additional attributes and values. In order to reduce spam the mailing list rejects mail from non-subscribers, so you must subscribe to the mailing list in order to send a question or comment to the mailing list.
鼓励本规范文件的实施者加入IPP邮件列表，以便参与澄清问题的任何讨论，并审查其他属性和值的注册提案。为了减少垃圾邮件，邮件列表拒绝来自非订阅者的邮件，因此您必须订阅邮件列表才能向邮件列表发送问题或评论。
Other Participants:
其他与会者：
Chuck Adams - Tektronix Shivaun Albright - HP
Chuck Adams-泰克Shivaun Albright-惠普
Stefan Andersson - Axis Jeff Barnett - IBM
Stefan Andersson-安讯士Jeff Barnett-IBM
Ron Bergman - Hitachi Koki Dennis Carney - IBM Imaging Systems
Ron Bergman-日立Koki Dennis Carney-IBM成像系统
Keith Carter - IBM Angelo Caruso - Xerox
Keith Carter-IBM Angelo Caruso-施乐
Rajesh Chawla - TR Computing Nancy Chen - Okidata Solutions
Rajesh Chawla-TR计算Nancy Chen-Okidata解决方案
Josh Cohen - Microsoft Jeff Copeland - QMS
Josh Cohen-微软Jeff Copeland-QMS
Andy Davidson - Tektronix Roger deBry - IBM
安迪·戴维森-泰克公司罗杰·德布雷-IBM
Maulik Desai - Auco Mabry Dozier - QMS
Maulik Desai-Auco Mabry Dozier-QMS
Lee Farrell - Canon Information Satoshi Fujitami - Ricoh Systems
Lee Farrell-佳能信息Satoshi Fujitami-理光系统
Steve Gebert - IBM Sue Gleeson - Digital
Steve Gebert-IBM Sue Gleeson-数字
Charles Gordon - Osicom Brian Grimshaw - Apple
查尔斯·戈登-奥西科姆·布莱恩·格里姆肖-苹果
Jerry Hadsell - IBM Richard Hart - Digital
Jerry Hadsell-IBM Richard Hart-数字
Tom Hastings - Xerox Henrik Holst - I-data
汤姆黑斯廷斯-施乐亨里克霍尔斯特-I-data
Stephen Holmstead Zhi-Hong Huang - Zenographics
黄志宏-天顶学
Scott Isaacson - Novell Babek Jahromi - Microsoft
Scott Isaacson-Novell Babek Jahromi-微软
Swen Johnson - Xerox David Kellerman - Northlake Software
Swen Johnson-施乐公司David Kellerman-Northlake软件
Robert Kline - TrueSpectra Charles Kong - Panasonic
罗伯特·克莱恩-孔泉-松下
Carl Kugler - IBM Dave Kuntz - Hewlett-Packard
卡尔·库格勒-IBM戴夫·昆茨-惠普
Takami Kurono - Brother Rick Landau - Digital
Takami Kurono-兄弟Rick Landau-数字
Scott Lawrence - Agranot Systems Greg LeClair - Epson
斯科特·劳伦斯-阿格拉诺系统公司格雷格·莱克莱尔-爱普生
Dwight Lewis - Lexmark Harry Lewis - IBM
德怀特·刘易斯-莱克斯马克·哈里·刘易斯-IBM
Tony Liao - Vivid Image Roy Lomicka - Digital
Tony Liao-生动形象Roy Lomicka-数字
Pete Loya - HP Ray Lutz - Cognisys
皮特·洛亚-惠普雷·卢茨-科尼赛
Mike MacKay - Novell, Inc. David Manchala - Xerox
迈克·麦凯-诺维尔公司大卫·曼查拉-施乐
Carl-Uno Manros - Xerox Jay Martin - Underscore
卡尔·乌诺·曼罗斯-施乐杰伊·马丁-下划线
Stan McConnell - Xerox Larry Masinter - Xerox
斯坦·麦康奈尔-施乐公司拉里·马斯特-施乐公司
Sandra Matts - Hewlett Packard Peter Michalek - Shinesoft
桑德拉·马特斯-惠普公司彼得·米切莱克-希内斯福特
Ira McDonald - High North Inc. Mike Moldovan - G3 Nova
爱尔兰共和军麦克唐纳-高北公司迈克摩尔多瓦-G3诺瓦
Tetsuya Morita - Ricoh Yuichi Niwa - Ricoh
森田铁也-理光日日一-理光
Pat Nogay - IBM Ron Norton - Printronics
Pat Nogay-IBM Ron Norton-Printronics
Hugo Parra, Novell Bob Pentecost - Hewlett-Packard
雨果·帕拉，中篇小说鲍勃·彭特科斯-惠普
Patrick Powell - Astart Jeff Rackowitz - Intermec Technologies
Patrick Powell-Astart Jeff Rackowitz-Intermec Technologies
Eric Random - Peerless Rob Rhoads - Intel
Eric Random-无与伦比的Rob Rhoads-英特尔
Xavier Riley - Xerox Gary Roberts - Ricoh
泽维尔·莱利-施乐加里·罗伯茨-理光
David Roach - Unisys Stuart Rowley - Kyocera
David Roach-Unisys Stuart Rowley-京瓷
Yuji Sasaki - Japan Computer Richard Schneider - Epson Industry
佐佐木裕二-日本计算机理查德·施耐德-爱普生工业
Kris Schoff - HP Katsuaki Sekiguchi - Canon
克里斯·肖夫-惠普胜垣关口-佳能
Bob Setterbo - Adobe Gail Songer - Peerless
鲍勃·塞特博-奥多比·盖尔·松格-无与伦比
Hideki Tanaka - Canon Devon Taylor - Novell, Inc.
田中英机-佳能德文泰勒-诺维尔公司。
Mike Timperman - Lexmark Atsushi Uchino - Epson
Mike Timperman-Lexmark Atsushi Uchino-Epson
Shigeru Ueda - Canon Bob Von Andel - Allegro Software
上田茂-佳能Bob Von Andel-快板软件
William Wagner - NetSilicon/DPI Jim Walker - DAZEL
William Wagner - NetSilicon/DPI Jim Walker - DAZEL
Chris Wellens - Interworking Labs Trevor Wells - Hewlett Packard
Chris Wellens-互通实验室Trevor Wells-惠普
Craig Whittle - Sharp Labs Rob Whittle - Novell, Inc.
Craig Whittle-Sharp实验室Rob Whittle-Novell公司。
Jasper Wong - Xionics Don Wright - Lexmark
Jasper Wong-Don Wright-利盟
Michael Wu - Heidelberg Digital Rick Yardumian - Xerox
迈克尔·吴-海德堡数码里克·亚杜米安-施乐
Michael Yeung - Toshiba Lloyd Young - Lexmark
迈克尔·杨-东芝劳埃德·杨-利盟
Atsushi Yuki - Kyocera Peter Zehler - Xerox
Atsushi Yuki-京瓷彼得·泽勒-施乐
William Zhang- Canon Information Frank Zhao - Panasonic Systems
William Zhang-佳能信息Frank Zhao-松下系统
Steve Zilles - Adobe Rob Zirnstein - Canon Information Systems
Steve Zilles-Adobe Rob Zirnstein-佳能信息系统
In addition to this document, the base set of IPP documents includes:
除本文件外，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]
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]
Mapping between LPD and IPP Protocols [RFC2569]
The "Design Goals for an Internet Printing Protocol" document takes a broad look at distributed printing functionality, and it enumerates real-life scenarios that help to clarify the features that need to be
“Internet打印协议的设计目标”文档广泛介绍了分布式打印功能，并列举了有助于澄清需要改进的功能的实际场景
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 [RFC2566, RFC2565]. A few OPTIONAL operator operations have been added to IPP/1.1 [RFC2911, RFC2910].
包含在Internet的打印协议中。它确定了三类用户的需求：最终用户、操作员和管理员。它调用了IPP/1.0[RFC2566，RFC2565]中满足的最终用户需求子集。IPP/1.1[RFC2911、RFC2910]中增加了一些可选的操作员操作。
The "Rationale for the Structure and Model and Protocol for the Internet Printing Protocol" document describes IPP from a high level view, defines a roadmap for the various documents that form the suite of IPP specification documents, and gives background and rationale for the IETF IPP working group's major decisions.
“互联网打印协议的结构、模型和协议的基本原理”文件从高层次上描述了IPP，定义了构成IPP规范文件套件的各种文件的路线图，并为IETF IPP工作组的主要决策提供了背景和基本原理。
The "Internet Printing Protocol/1.1: Model and Semantics" document describes a simplified model with abstract objects, their attributes, and their operations. The model introduces a Printer and a Job. The Job supports multiple documents per Job. The model document also addresses how security, internationalization, and directory issues are addressed.
“Internet打印协议/1.1：模型和语义”文档描述了一个简化模型，其中包含抽象对象、它们的属性及其操作。该模型引入了打印机和作业。每个作业支持多个文档。模型文档还讨论了如何解决安全性、国际化和目录问题。
The "Internet Printing Protocol/1.1: Encoding and Transport" document is a formal mapping of the abstract operations and attributes defined in the model document onto HTTP/1.1 [RFC2616]. It also defines the encoding rules for a new Internet MIME media type called "application/ipp". This document also defines the rules for transporting a message body over HTTP whose Content-Type is "application/ipp". This document defines the 'ipp' scheme for identifying IPP printers and jobs.
“Internet打印协议/1.1：编码和传输”文档是模型文档中定义的抽象操作和属性到HTTP/1.1[RFC2616]的正式映射。它还定义了称为“应用程序/ipp”的新Internet MIME媒体类型的编码规则。本文档还定义了通过HTTP传输内容类型为“application/ipp”的消息体的规则。本文件定义了识别ipp打印机和作业的“ipp”方案。
The "Mapping between LPD and IPP Protocols" document gives some advice to implementers of gateways between IPP and LPD (Line Printer Daemon) implementations.
“LPD和IPP协议之间的映射”文档为IPP和LPD（Line Printer Daemon）实现之间网关的实现者提供了一些建议。
11 Full Copyright Statement
11完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。