Network Working Group R. Herriot
Request for Comments: 3996 Global Workflow Solutions
Updates: 2911 T. Hastings
Category: Standards Track Xerox Corp.
H. Lewis
IBM Corp.
March 2005
Network Working Group R. Herriot
Request for Comments: 3996 Global Workflow Solutions
Updates: 2911 T. Hastings
Category: Standards Track Xerox Corp.
H. Lewis
IBM Corp.
March 2005
Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications
Internet打印协议（IPP）：事件通知的“ippget”传递方法
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document describes an extension to the Internet Printing Protocol1.1: Model and Semantics (RFC 2911, RFC 2910). This document specifies the 'ippget' Pull Delivery Method for use with the "Internet Printing Protocol (IPP): Event Notifications and Subscriptions" specification (RFC 3995). This IPPGET Delivery Method is REQUIRED for all clients and Printers that support RFC 3995. The Notification Recipient, acting as a client, fetches (pulls) Event Notifications by using the Get-Notifications operation defined in this document.
本文档描述了Internet打印协议1.1的扩展：模型和语义（RFC 2911，RFC 2910）。本文档指定了与“Internet打印协议（IPP）：事件通知和订阅”规范（RFC 3995）一起使用的“ippget”拉式传递方法。支持RFC 3995的所有客户端和打印机都需要此IPPGET交付方法。通知收件人充当客户端，通过使用本文档中定义的获取通知操作获取（拉取）事件通知。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Conformance Terminology . . . . . . . . . . . . . . . . 4
2.2. Other Terminology . . . . . . . . . . . . . . . . . . . 4
3. Model and Operation . . . . . . . . . . . . . . . . . . . . . 4
4. General Information . . . . . . . . . . . . . . . . . . . . . 5
5. Get-Notifications Operation . . . . . . . . . . . . . . . . . 7
5.1. Get-Notifications Request . . . . . . . . . . . . . . . 8
5.1.1. notify-subscription-ids (1setOf integer(1:MAX)) 8
5.1.2. notify-sequence-numbers (1setOf integer(1:MAX)) 9
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Conformance Terminology . . . . . . . . . . . . . . . . 4
2.2. Other Terminology . . . . . . . . . . . . . . . . . . . 4
3. Model and Operation . . . . . . . . . . . . . . . . . . . . . 4
4. General Information . . . . . . . . . . . . . . . . . . . . . 5
5. Get-Notifications Operation . . . . . . . . . . . . . . . . . 7
5.1. Get-Notifications Request . . . . . . . . . . . . . . . 8
5.1.1. notify-subscription-ids (1setOf integer(1:MAX)) 8
5.1.2. notify-sequence-numbers (1setOf integer(1:MAX)) 9
5.1.3. notify-wait (boolean) . . . . . . . . . . . . . 10
5.2. Get-Notifications Response. . . . . . . . . . . . . . . 10
5.2.1. notify-get-interval (integer(0:MAX)). . . . . . 13
5.2.2. printer-up-time (integer(1:MAX)). . . . . . . . 14
6. Additional Information about Subscription Template Attributes 17
6.1. notify-pull-method (type2 keyword). . . . . . . . . . . 17
7. Subscription Description Attributes . . . . . . . . . . . . . 18
8. Additional Printer Description Attributes . . . . . . . . . . 18
8.1. ippget-event-life (integer(15:MAX)) . . . . . . . . . . 18
9. New Values for Existing Printer Description Attributes. . . . 19
9.1. notify-pull-method-supported (1setOf type2 keyword) . . 19
9.2. operations-supported (1setOf type2 enum). . . . . . . . 19
10. New Status Codes. . . . . . . . . . . . . . . . . . . . . . . 19
10.1. successful-ok-events-complete (0x0007) . . . . . . . . 20
11. Encoding and Transport. . . . . . . . . . . . . . . . . . . . 20
12. Conformance Requirements. . . . . . . . . . . . . . . . . . . 21
12.1. Conformance for IPP Printers . . . . . . . . . . . . . 21
12.2. Conformance for IPP Clients. . . . . . . . . . . . . . 22
13. Normative References. . . . . . . . . . . . . . . . . . . . . 23
14. Informative References. . . . . . . . . . . . . . . . . . . . 23
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
15.1. Attribute Registrations. . . . . . . . . . . . . . . . 24
15.2. Delivery Method and Additional Keyword Attribute Value
registrations for Existing Attributes. . . . . . . . . 24
15.3. Additional Enum Attribute Values . . . . . . . . . . . 25
15.4. Operation Registrations. . . . . . . . . . . . . . . . 25
15.5. Status Code Registrations. . . . . . . . . . . . . . . 25
16. Internationalization Considerations . . . . . . . . . . . . . 25
17. Security Considerations . . . . . . . . . . . . . . . . . . . 26
17.1. Notification Recipient Client Access Rights. . . . . . 26
17.2. Printer Security Threats . . . . . . . . . . . . . . . 27
17.3. Notification Recipient Security Threats. . . . . . . . 27
17.4. Security Requirements for Printers . . . . . . . . . . 27
17.5. Security Requirements for clients. . . . . . . . . . . 28
18. Description of Base IPP Documents (Informative) . . . . . . . 28
19. Contributors. . . . . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 31
5.1.3. notify-wait (boolean) . . . . . . . . . . . . . 10
5.2. Get-Notifications Response. . . . . . . . . . . . . . . 10
5.2.1. notify-get-interval (integer(0:MAX)). . . . . . 13
5.2.2. printer-up-time (integer(1:MAX)). . . . . . . . 14
6. Additional Information about Subscription Template Attributes 17
6.1. notify-pull-method (type2 keyword). . . . . . . . . . . 17
7. Subscription Description Attributes . . . . . . . . . . . . . 18
8. Additional Printer Description Attributes . . . . . . . . . . 18
8.1. ippget-event-life (integer(15:MAX)) . . . . . . . . . . 18
9. New Values for Existing Printer Description Attributes. . . . 19
9.1. notify-pull-method-supported (1setOf type2 keyword) . . 19
9.2. operations-supported (1setOf type2 enum). . . . . . . . 19
10. New Status Codes. . . . . . . . . . . . . . . . . . . . . . . 19
10.1. successful-ok-events-complete (0x0007) . . . . . . . . 20
11. Encoding and Transport. . . . . . . . . . . . . . . . . . . . 20
12. Conformance Requirements. . . . . . . . . . . . . . . . . . . 21
12.1. Conformance for IPP Printers . . . . . . . . . . . . . 21
12.2. Conformance for IPP Clients. . . . . . . . . . . . . . 22
13. Normative References. . . . . . . . . . . . . . . . . . . . . 23
14. Informative References. . . . . . . . . . . . . . . . . . . . 23
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
15.1. Attribute Registrations. . . . . . . . . . . . . . . . 24
15.2. Delivery Method and Additional Keyword Attribute Value
registrations for Existing Attributes. . . . . . . . . 24
15.3. Additional Enum Attribute Values . . . . . . . . . . . 25
15.4. Operation Registrations. . . . . . . . . . . . . . . . 25
15.5. Status Code Registrations. . . . . . . . . . . . . . . 25
16. Internationalization Considerations . . . . . . . . . . . . . 25
17. Security Considerations . . . . . . . . . . . . . . . . . . . 26
17.1. Notification Recipient Client Access Rights. . . . . . 26
17.2. Printer Security Threats . . . . . . . . . . . . . . . 27
17.3. Notification Recipient Security Threats. . . . . . . . 27
17.4. Security Requirements for Printers . . . . . . . . . . 27
17.5. Security Requirements for clients. . . . . . . . . . . 28
18. Description of Base IPP Documents (Informative) . . . . . . . 28
19. Contributors. . . . . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 31
Table of Tables
表格
Table 1. Information about the Delivery Method. . . . . . . . . . 5
Table 2. Combinations of "notify-wait", "status-code", and
"notify-get-interval". . . . . . . . . . . . . . . . . . 13
Table 3. Attributes in Event Notification Content . . . . . . . . 15
Table 4. Additional Attributes in Event Notification Content for
Job Events . . . . . . . . . . . . . . . . . . . . . . . 16
Table 1. Information about the Delivery Method. . . . . . . . . . 5
Table 2. Combinations of "notify-wait", "status-code", and
"notify-get-interval". . . . . . . . . . . . . . . . . . 13
Table 3. Attributes in Event Notification Content . . . . . . . . 15
Table 4. Additional Attributes in Event Notification Content for
Job Events . . . . . . . . . . . . . . . . . . . . . . . 16
Table 5. Combinations of Events and Subscribed Events for "job-
impressions-completed" . . . . . . . . . . . . . . . . . 17
Table 6. Additional Attributes in Event Notification Content for
Printer Events . . . . . . . . . . . . . . . . . . . . . 17
Table 7. Operation-id Assignments . . . . . . . . . . . . . . . . 19
Table 8. The "event-notification-attributes-tag" Value. . . . . . 21
Table 5. Combinations of Events and Subscribed Events for "job-
impressions-completed" . . . . . . . . . . . . . . . . . 17
Table 6. Additional Attributes in Event Notification Content for
Printer Events . . . . . . . . . . . . . . . . . . . . . 17
Table 7. Operation-id Assignments . . . . . . . . . . . . . . . . 19
Table 8. The "event-notification-attributes-tag" Value. . . . . . 21
This document describes an extension to the Internet Printing Protocol/1.1: Model and Semantics [RFC 2911], [RFC 2910]. This document specifies the 'ippget' Pull Delivery Method for use with the "Internet Printing Protocol (IPP): Event Notifications and Subscriptions" specification [RFC3995]. This IPPGET Delivery Method is REQUIRED for all clients and Printers that support [RFC3995]. The Notification Recipient, acting as a client, fetches (pulls) Event Notifications by using the Get-Notifications operation defined in this document. For a description of the base IPP documents, see section 21 of this document. For a description of the IPP Event Notification Model, see [RFC3995].
本文档描述了Internet打印协议/1.1的扩展：模型和语义[RFC 2911]，[RFC 2910]。本文档指定了与“Internet打印协议（IPP）：事件通知和订阅”规范[RFC3995]一起使用的“ippget”拉式传递方法。支持[RFC3995]的所有客户端和打印机都需要此IPPGET交付方法。通知收件人充当客户端，通过使用本文档中定义的获取通知操作获取（拉取）事件通知。有关基本IPP文件的说明，请参阅本文件第21节。有关IPP事件通知模型的说明，请参阅[RFC3995]。
With this Pull Delivery Method, when an Event occurs, the Printer saves the Event Notification for a period of time called the Event Life. The Notification Recipient fetches (pulls) the Event Notifications by using the Get-Notifications operation. This operation causes the Printer to return all Event Notifications held for the specified Subscription object(s). If the Notification Recipient has selected the Event Wait Mode option to wait for additional Event Notifications, the Printer MAY continue to return Event Notifications to the Notification Recipient as asynchronous Get-Notification responses as Events occur using the transaction originated by the Notification Recipient.
使用此拉式传递方法，当事件发生时，打印机会将事件通知保存一段称为事件寿命的时间。通知收件人通过使用Get Notifications操作获取（拉取）事件通知。此操作导致打印机返回为指定订阅对象保留的所有事件通知。如果通知收件人已选择“事件等待模式”选项以等待其他事件通知，则当事件发生时，打印机可以使用通知收件人发起的事务继续将事件通知作为异步获取通知响应返回给通知收件人。
The Notification Recipient can terminate Event Wait Mode (without closing the connection) by supplying the "notify-wait" (boolean) attribute with a 'false' value in a subsequent Get-Notifications request. Similarly, the Printer can terminate Event Wait Mode (without closing the connection) by returning the "notify-get-interval" (integer) operation attribute in a Get-Notifications response that tells the Notification Recipient how long to wait before trying again.
通知收件人可以通过在后续的Get NOTITITIONS请求中为“notify Wait”（布尔）属性提供“false”值来终止事件等待模式（而不关闭连接）。类似地，打印机可以通过在get Notifications响应中返回“notify get interval”（整数）操作属性来终止事件等待模式（无需关闭连接），该属性告诉通知接收者在重试之前要等待多长时间。
This section defines the following terms that are used throughout this document:
本节定义了本文件中使用的以下术语：
Capitalized terms such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, MAY, NEED NOT, and OPTIONAL have special meaning relating to conformance as defined in [RFC2119] and [RFC2911], section 12.1. If an implementation supports the extension defined in this document, then these terms apply; otherwise, they do not. These terms define conformance to this document only; they do not affect conformance to other documents, unless it is explicitly stated otherwise.
如[RFC2119]和[RFC2911]第12.1节所定义，大写术语（如必须、不得、必需、应该、不应该、可能、不需要和可选）具有与合规性相关的特殊含义。如果实施支持本文件中定义的扩展，则这些条款适用；否则，他们不会。这些术语仅定义与本文件的一致性；除非另有明确规定，否则它们不影响与其他文件的一致性。
This document uses the same terminology as [RFC2911], including "client", "Printer", "Job", "attribute", "attribute value", "keyword", "operation", "request", "response", and "support", with the same meanings. This document also uses terminology defined in [RFC3995], such as "Subscription (object)", "Notification Recipient", "Event", "Event Notification", "Compound Event Notification", "Event Life", and "Event Notification Attribute Group", with the same meanings. In addition, this document defines the following terms for use in this document:
本文件使用与[RFC2911]相同的术语，包括“客户机”、“打印机”、“作业”、“属性”、“属性值”、“关键字”、“操作”、“请求”、“响应”和“支持”，含义相同。本文件还使用了[RFC3995]中定义的术语，如“订阅（对象）”、“通知收件人”、“事件”、“事件通知”、“复合事件通知”、“事件寿命”和“事件通知属性组”，具有相同的含义。此外，本文件定义了本文件中使用的以下术语：
Event Wait Mode: The mode requested by a Notification Recipient client in its Get-Notifications Request and granted by a Printer to keep the connection open while the Printer sends subsequent Get-Notification operation responses to the Notification Recipient in the form of Event Notifications as they occur.
事件等待模式：通知收件人客户端在其获取通知请求中请求的模式，由打印机授予该模式，以便在打印机以事件通知的形式向通知收件人发送后续获取通知操作响应时保持连接打开。
In a Subscription Creation Operation, when the "notify-pull-method" attribute is present and has the "ippget" keyword value, the client is requesting that the Printer use the "ippget" Pull Delivery Method for the Event Notifications associated with the new Subscription Object.
在订阅创建操作中，当“notify pull method”属性存在且具有“ippget”关键字值时，客户端请求打印机对与新订阅对象关联的事件通知使用“ippget”pull传递方法。
When an Event occurs, the Printer MUST generate an Event Notification and MUST assign it the Event Life. The Printer MUST hold an Event Notification for its assigned Event Life.
当事件发生时，打印机必须生成事件通知，并且必须为其分配事件生存期。打印机必须在其指定的事件生存期内保存事件通知。
When a Notification Recipient wants to receive Event Notifications for a Subscription object, it performs the Get-Notifications operation supplying the Subscription object's subscription-id, which causes the Printer to return all un-expired Event Notifications held for that Subscription object. If the Notification Recipient has selected the Event Wait Mode option to wait for additional Event Notifications, the response to the Get-Notifications request continues indefinitely as the Printer continues to send Event
当通知收件人希望接收订阅对象的事件通知时，它将执行提供订阅对象的订阅id的“获取通知”操作，这将导致打印机返回为该订阅对象保留的所有未过期事件通知。如果通知收件人已选择“事件等待模式”选项以等待其他事件通知，则在打印机继续发送事件通知时，对“获取通知”请求的响应将无限期继续
Notifications in the response as Events occur for that Subscription object.
该订阅对象发生事件时响应中的通知。
When the Notification Recipient requests Event Notifications for Per-Job Subscription Objects, the Notification Recipient typically performs the Get-Notifications operation within a second of performing the Subscription Creation operation. Because the Printer MUST save Event Notifications for at least 15 seconds (see section 8.1), the Notification Recipient is unlikely to miss any Event Notifications that occur between the Subscription Creation and the Get-Notifications operation.
当通知收件人请求每个作业订阅对象的事件通知时，通知收件人通常在执行订阅创建操作后的一秒钟内执行获取通知操作。由于打印机必须保存事件通知至少15秒（请参阅第8.1节），因此通知收件人不太可能错过订阅创建和获取通知操作之间发生的任何事件通知。
The 'ippget' Delivery Method is designed primarily for (1) a client that wants to get Events (from the job's Per-Job Subscription object) for a job that it has submitted and (2) a privileged client that wants to get all job or printer Events from a Per-Printer Subscription object.
“ippget”传递方法主要用于（1）希望从作业的每个作业订阅对象获取其已提交作业的事件的客户端，以及（2）希望从每个打印机订阅对象获取所有作业或打印机事件的特权客户端。
If a Printer supports this Delivery Method, the following are its characteristics.
如果打印机支持此传送方法，则其特征如下。
Table 1. Information about the Delivery Method
表1。关于交付方法的信息
Document Method Conformance Requirement Delivery Method Realization
文档方法一致性需求交付方法实现
1. What is the URL scheme name for the 'ippget' keyword method Push Delivery Method, or the keyword name method name for the Pull Delivery Method?
1. “ippget”关键字方法推送传递方法的URL方案名称是什么，或“Pull传递”方法的关键字名称方法名称是什么？
2. Is the Delivery Method REQUIRED, REQUIRED RECOMMENDED, or OPTIONAL for an IPP Printer to support?
2. IPP打印机支持的交付方法是必需的、推荐的还是可选的？
3. What transport and delivery protocols IPP with one new does the Printer use to deliver the operation. Event Notification Content; i.e., what is the entire network stack?
3. 打印机使用什么传输和交付协议IPP和一个新的IPP来交付操作。事件通知内容；i、 例如，整个网络堆栈是什么？
4. Can several Event Notifications be Yes. combined into a Compound Event Notification?
4. 多个事件通知是否可以是“是”。合并为复合事件通知？
5. Is the Delivery Method initiated by This Delivery Method is the Notification Recipient (pull), a pull method with or by the Printer (push)? aspects of a push method, though the Printer does not initiate the operation.
5. 此传递方法启动的传递方法是通知收件人（pull），是使用或由打印机（push）启动的传递方法？尽管打印机不启动操作，但推送方法的各个方面。
6. Is the Event Notification content Machine Consumable. Machine Consumable or Human Consumable?
6. 是事件通知内容计算机的耗材。机器消耗品还是人类消耗品？
7. What section in this document answers Section 5. the following questions? For a Machine Consumable Event Notification, what is the representation and encoding of values defined in section 9.1 of [RFC3995], and what are the conformance requirements thereof? For a Human Consumable Event Notification, what is the representation and encoding of pieces of information defined in section 9.2 of [RFC3995], and the conformance requirements thereof?
7. 本文件中的哪一节回答了第5节。以下问题？对于机器耗材事件通知，[RFC3995]第9.1节中定义的值的表示和编码是什么，其一致性要求是什么？对于人类消耗品事件通知，[RFC3995]第9.2节中定义的信息片段的表示和编码是什么，以及其一致性要求是什么？
8. What are the latency and reliability Same as IPP and the of the transport and delivery underlying HTTP protocol? transport.
8. IPP的延迟和可靠性与HTTP协议的传输和交付的延迟和可靠性相同吗？运输
9. What are the security aspects of the Same as IPP and the transport and delivery protocol; underlying HTTP e.g., how it is handled in transport and in the firewalls? same direction, so no new firewall considerations.
9. 与IPP以及运输和交付协议相同的安全方面有哪些；底层HTTP，例如，如何在传输和防火墙中处理它？方向相同，因此没有新的防火墙注意事项。
10. What are the content length None. restrictions?
10. 内容长度是多少。限制？
11. What are the additional values or None. pieces of information that a Printer sends in an Event Notification content and the conformance requirements thereof?
11. 附加值是多少，或者没有。打印机在事件通知内容中发送的信息片段及其一致性要求？
12. What are the additional Subscription None. Template and/or Subscription Description attributes and the conformance requirements thereof?
12. 什么是额外的订阅没有。模板和/或订阅描述属性及其一致性要求？
13. What are the additional Printer "ipp-event-life" Description attributes and the (integer (15: MAX)) conformance requirements thereof?
13. 附加打印机“ipp事件寿命”描述属性及其（整数（15:MAX））一致性要求是什么？
This operation is issued by a client acting in the role of a Notification Recipient requesting the Printer to return all Event Notifications held for the identified Subscription object(s).
此操作由扮演通知收件人角色的客户端发出，请求打印机返回为标识的订阅对象保留的所有事件通知。
A Printer MUST support this operation, MUST accept the request in any state (see [RFC2911] "printer-state" and "printer-state-reasons" attributes), and MUST remain in the same state with the same "printer-state-reasons" values.
打印机必须支持此操作，必须在任何状态下接受请求（请参阅[RFC2911]“打印机状态”和“打印机状态原因”属性），并且必须使用相同的“打印机状态原因”值保持相同的状态。
When a Printer performs this operation, it MUST return all and only those Event Notifications
打印机执行此操作时，必须返回所有且仅返回这些事件通知
1. whose associated Subscription Object's "notify-subscription-id" Subscription Description attribute equals one of the values of the "notify-subscription-ids" (1setOf integer(1:MAX)) operation attribute AND
1. 其关联订阅对象的“通知订阅id”订阅描述属性等于“通知订阅id”（1setOf integer（1:MAX））操作属性的值之一，并且
2. whose associated Subscription Object contains the "notify-pull-method" attribute and it has the 'ippget' keyword value, AND
2. 其关联的订阅对象包含“notify pull method”属性，并且具有“ippget”关键字值，以及
3. whose "notify-sequence-number" is equal to or greater than the corresponding value of the "notify-sequence-numbers" (1setOf integer(1:MAX)) operation attribute if supplied AND
3. 其“notify sequence number”等于或大于“notify sequence number”（1setOf integer（1:MAX））操作属性（如果提供）的相应值，并且
4. whose Event Life has not yet expired AND
4. 其事件生命期尚未到期，并且
5. where the Notification Recipient client has read-access rights to the identified Subscription Object (see Access Rights paragraph below).
5. 其中，通知收件人客户端对已标识的订阅对象具有读取访问权限（请参阅下面的访问权限段落）。
The Notification Recipient client MUST either (a) request Event Wait Mode by supplying the "notify-wait" operation attribute with a 'true' value or (b) suppress Event Wait Mode by omitting the "notify-wait" operation attribute or by supplying it with a 'false' value. To terminate Event Wait Mode subsequently, the Notification Recipient client MUST close the connection. To terminate Event Wait Mode, the Printer MUST either (a) return the "notify-get-interval" operation
通知接收方客户端必须（a）通过向“notify Wait”操作属性提供“true”值来请求事件等待模式，或（b）通过省略“notify Wait”操作属性或向其提供“false”值来抑制事件等待模式。若要随后终止事件等待模式，通知收件人客户端必须关闭连接。要终止事件等待模式，打印机必须（a）返回“notify get interval”操作
attribute in a Get-Notifications response (RECOMMENDED behavior) or (b) close the connection. The "notify-get-interval" operation attributes tell the Notification Recipient how long to wait before trying a subsequent Get-Notifications request.
属性（建议的行为）或（b）关闭连接。“notify get interval”操作属性告诉通知收件人在尝试后续的get Notifications请求之前需要等待多长时间。
Access Rights: The authenticated user (see [RFC2911], section 8.3) performing this operation MUST be (1) the owner of each Subscription Object identified by the "notify-subscription-ids" operation attribute (see section 5.1.1), (2) an operator or administrator of the Printer (see [RFC2911], sections 1 and 8.5), or (3) otherwise authorized by the Printer's administrator-configured security policy to request Event Notifications from the target Subscription Object(s). Otherwise, the IPP Printer MUST reject the operation and return: 'client-error-forbidden', 'client-error-not-authenticated', or 'client-error-not-authorized' status code, as appropriate. Furthermore, the Printer's security policy MAY limit the attributes returned by the Get-Notifications operation, in a manner similar to that of the Get-Job-Attributes operation (see [RFC2911], end of section 3.3.4.2).
访问权限：执行此操作的经过身份验证的用户（请参见[RFC2911]，第8.3节）必须是（1）由“通知订阅ID”操作属性标识的每个订阅对象的所有者（请参见第5.1.1节），（2）打印机的操作员或管理员（请参见[RFC2911]，第1节和第8.5节），或（3）打印机管理员以其他方式授权配置的安全策略从目标订阅对象请求事件通知。否则，IPP打印机必须拒绝该操作并返回“客户端错误禁止”、“客户端错误未验证”或“客户端错误未授权”状态代码（视情况而定）。此外，打印机的安全策略可能会以类似于获取作业属性操作的方式限制获取通知操作返回的属性（请参见[RFC2911]，第3.3.4.2节末尾）。
The following groups of attributes are part of the Get-Notifications Request:
以下属性组是Get Notifications请求的一部分：
Group 1: Operation Attributes
第1组：操作属性
Natural Language and Character Set: The "attributes-charset" and "attributes-natural-language" attributes, as described in [RFC2911], section 3.1.4.1.
自然语言和字符集：“属性字符集”和“属性自然语言”属性，如[RFC2911]第3.1.4.1节所述。
Target: The "printer-uri" (uri) operation attribute that is the target for this operation as described in [RFC2911], section 3.1.5.
目标：“打印机uri”（uri）操作属性，如[RFC2911]第3.1.5节所述，该属性是此操作的目标。
Requesting User Name: The "requesting-user-name" (name(MAX)) attribute SHOULD be supplied by the client as described in [RFC2911], section 8.3.
请求用户名：“请求用户名”（Name（MAX））属性应由客户机提供，如[RFC2911]第8.3节所述。
This attribute identifies one or more Subscription objects for which Events are requested. The client MUST supply this attribute with at least one value. The Printer object MUST support this attribute with multiple values.
此属性标识为其请求事件的一个或多个订阅对象。客户端必须为该属性提供至少一个值。打印机对象必须支持具有多个值的此属性。
If no Subscription Object exists with the supplied identifier, or if the identified Subscription Object does not contain the "notify-
如果不存在具有所提供标识符的订阅对象，或者如果标识的订阅对象不包含“通知”-
pull-method" attribute with the 'ippget' keyword value, the Printer MUST return the 'client-error-not-found' status code.
具有“ippget”关键字值的“pull method”属性，打印机必须返回“客户端错误未找到”状态代码。
Note: The name of both the "notify-subscription-ids" and "notify-sequence-numbers" end in 's', as they are multi-valued. However, there are other occurrences of these attribute names without the 's' that are single valued.
注意：“通知订阅ID”和“通知序列号”的名称都以“s”结尾，因为它们是多值的。但是，这些属性名称中还有其他不带单值“s”的实例。
This attribute specifies one or more of the lowest Event Notification sequence number values for the Subscription objects identified by the corresponding values of the "notify-subscription-ids" operation attribute. The Notification Recipient SHOULD supply this attribute, and the number of values SHOULD be the same as that of the "notify-subscriptions-ids" attribute. The Printer MUST support this attribute with multiple values.
此属性指定由“通知订阅ID”操作属性的相应值标识的订阅对象的一个或多个最低事件通知序列号值。通知收件人应提供此属性，并且值的数目应与“通知订阅ID”属性的数目相同。打印机必须支持具有多个值的此属性。
The Printer MUST NOT return Notification Events with lower sequence numbers for the corresponding Subscription object. Therefore, by supplying the proper values for this attribute the Notification Recipient can prevent getting the same Event Notifications from a Subscription object that were returned on a previous Get-Notifications request. The Notification Recipient SHOULD remember the highest "notify-sequence-number" value returned for each Subscription object requested and SHOULD pass that value for each requested Subscription object on the next Get-Notifications request.
打印机不得返回相应订阅对象的序列号较低的通知事件。因此，通过为该属性提供适当的值，通知收件人可以防止从订阅对象获取与在上一个Get Notifications请求中返回的相同的事件通知。通知收件人应记住为每个请求的订阅对象返回的最高“notify sequence number”值，并应在下一个Get Notifications请求中为每个请求的订阅对象传递该值。
If the Notification Recipient supplies fewer values for this attribute (including omitting this attribute) than it does for the "notify-subscription-ids" operation attribute, the Printer assumes a '1' value for each missing value. A value of '1' causes the Printer to return any un-expired Event Notification for that Subscription object, as '1' is the lowest possible sequence number. If the Notification Recipient supplies more values for this attribute than the number of values for the "notify-subscription-ids" operation attribute, the Printer ignores the extra values.
如果通知收件人为此属性提供的值（包括省略此属性）少于“通知订阅ID”操作属性提供的值，则打印机将为每个缺少的值假定一个“1”值。值“1”会导致打印机返回该订阅对象的任何未过期事件通知，因为“1”是可能的最低序列号。如果通知收件人为此属性提供的值多于“通知订阅ID”操作属性的值数，则打印机将忽略额外的值。
Note: If a Notification Recipient performs two consecutive Get-Notifications operations with the same value for "notify-sequence-number" (or omits the attribute), the time stamp value of the first Event Notification in the second Get-Notifications Response may be less than that of the time stamp of the last Event Notification in the first Get-Notification Response. This happens because the Printer sends all unexpired Event Notifications with an equal or higher sequence number according to the ordering specified in [RFC3995], and some Event Notifications from the first Get-
注意：如果通知接收者使用“notify sequence number”（通知序列号）的相同值执行两个连续的Get Notifications操作（或省略该属性），第二个Get通知响应中第一个事件通知的时间戳值可能小于第一个Get通知响应中最后一个事件通知的时间戳值。这是因为打印机根据[RFC3995]中指定的顺序发送所有序列号相等或更高的未过期事件通知，以及从第一个Get开始发送的一些事件通知-
Notifications operation may not have expired by the time the second Get-Notifications operation occurs.
在执行第二个获取通知操作时，通知操作可能尚未过期。
This value indicates whether the Notification Recipient wants Event Wait Mode. The client MAY supply this attribute. The Printer object MUST support both values of this attribute.
此值指示通知收件人是否需要事件等待模式。客户端可以提供此属性。打印机对象必须支持此属性的两个值。
If the client supplies the 'false' value or omits this attribute, the client is not requesting Event Wait Mode. If the value is 'true', the client is requesting Event Wait Mode. See the beginning of section 5.2 for the rules for Event Wait Mode.
如果客户端提供“false”值或忽略此属性，则客户端不请求事件等待模式。如果该值为“true”，则客户端正在请求事件等待模式。有关事件等待模式的规则，请参见第5.2节开头部分。
The Printer has the following options for responding to a Get-Notifications Request:
打印机具有以下选项来响应Get通知请求：
1. The Printer can reject the request and return the 'server-error-busy' status code if the Printer is too busy to accept this operation at this time. In this case, the Printer MUST return the "get-notify-interval" operation attribute to indicate when the client SHOULD try again.
1. 如果打印机此时太忙而无法接受此操作，则打印机可以拒绝请求并返回“服务器错误忙”状态代码。在这种情况下，打印机必须返回“get notify interval”操作属性，以指示客户端应在何时重试。
2. If the Notification Recipient did not request Event Wait Mode ("notify-wait-mode" = 'false' or omitted), the Printer MUST immediately return whatever Event Notifications it currently holds in the requested Subscription object(s) and MUST return the "notify-get-interval" operation attribute with the number of seconds from now, at which the Notification Recipient SHOULD repeat the Get-Notifications Request to get future Event Notifications.
2. 如果通知收件人未请求事件等待模式（“通知等待模式”=“false”或省略），则打印机必须立即返回其当前在请求的订阅对象中保存的任何事件通知，并且必须返回“notify get interval”操作属性（从现在起的秒数），通知收件人应在该时间重复Get Notifications请求以获取将来的事件通知。
3. If the Notification Recipient requested Event Wait Mode ("notify-wait-mode" = 'true'), the Printer MUST immediately return whatever Event Notifications it currently holds in the requested Subscription object(s) and MUST continue to return Event Notifications as they occur until all the requested Subscription Objects are canceled. A Subscription Object is canceled either via the Cancel-Subscription operation or by the Printer (e.g., the Subscription Object is canceled when the associated Job completes and is no longer in the Job Retention or Job History phase; see the "ippget-event-life (integer(15:MAX))" attribute discussion in section 8.1).
3. 如果通知收件人请求事件等待模式（“notify Wait Mode”=“true”），则打印机必须立即返回其当前在请求的订阅对象中保存的任何事件通知，并且必须在事件通知发生时继续返回事件通知，直到取消所有请求的订阅对象。通过取消订阅操作或打印机取消订阅对象（例如，当相关作业完成且不再处于作业保留或作业历史阶段时，取消订阅对象；请参阅第8.1节中的“ippget事件寿命（整数（15:MAX））”属性讨论）。
However, the Printer MAY decide to terminate Event Wait Mode at any time, including in the first response. In this case, the
然而，打印机可随时决定终止事件等待模式，包括在第一次响应中。在这种情况下
Printer MUST return the "notify-get-interval" operation attribute. This attribute indicates that the Printer wishes to leave Event Wait Mode and the number of seconds in the future that the Notification Recipient SHOULD try the Get-Notifications operation again. The Notification Recipient MUST accept this response and MUST disconnect. If the Notification Recipient does not disconnect, the Printer SHOULD do so.
打印机必须返回“通知获取间隔”操作属性。此属性表示打印机希望离开事件等待模式，以及通知收件人在未来应再次尝试获取通知操作的秒数。通知收件人必须接受此响应，并且必须断开连接。如果通知收件人未断开连接，则打印机应断开连接。
From the Notification Recipient's view, the response appears as an initial burst of data, which includes the Operation Attributes Group and one Event Notification Attributes Group per Event Notification that the Printer is holding. After the initial burst of data, if the Notification Recipient has selected the Event Wait Mode option to wait for additional Event Notifications, the Notification Recipient receives occasional Event Notification Attribute Groups. Proxy servers may delay some Event Notifications or cause time-outs to occur. The client MUST be prepared to perform the Get-Notifications operation again when time-outs occur.
从通知收件人的角度来看，响应显示为初始数据突发，其中包括操作属性组和打印机持有的每个事件通知的一个事件通知属性组。初始数据突发后，如果通知收件人已选择事件等待模式选项以等待其他事件通知，则通知收件人将接收偶发事件通知属性组。代理服务器可能会延迟某些事件通知或导致超时。客户端必须准备在发生超时时再次执行Get Notifications操作。
Each attribute is encoded by using the IPP rules for encoding attributes [RFC2910] and MAY be encoded in any order. Note: the Get-Jobs response in [RFC2911] acts as a model for encoding multiple groups of attributes. See section 11 for the encoding and transport rules.
通过使用IPP编码属性规则[RFC2910]对每个属性进行编码，并且可以按任何顺序进行编码。注意：[RFC2911]中的Get Jobs响应充当编码多组属性的模型。有关编码和传输规则，请参见第11节。
The following groups of attributes are part of the Get-Notifications Response:
以下属性组是Get Notifications响应的一部分：
Group 1: Operation Attributes
第1组：操作属性
Status Message: In addition to the REQUIRED status code returned in every response, the response OPTIONALLY includes a "status-message" (text(255)) and/or a "detailed-status-message" (text(MAX)) operation attribute, as described in [RFC2911], sections 13 and 3.1.6.
状态消息：除了在每个响应中返回所需的状态代码外，响应还可以包括“状态消息”（文本（255））和/或“详细状态消息”（文本（最大））操作属性，如[RFC2911]第13节和第3.1.6节所述。
The Printer can return any status codes defined in [RFC2911]. If the status code is not 'successful-xxx', the Printer MUST NOT return any Event Notification Attribute groups. The following are descriptions of the important status codes:
打印机可以返回[RFC2911]中定义的任何状态代码。如果状态代码不是“successful xxx”，打印机不得返回任何事件通知属性组。以下是重要状态代码的说明：
successful-ok: The response contains all Event Notification associated with the specified subscription-ids that had been supplied in the "notify-subscription-ids" operation attribute in the request. If the requested Subscription Objects have no associated Event Notification, the response MUST contain zero Event Notifications.
成功确定：响应包含与请求中“通知订阅ID”操作属性中提供的指定订阅ID相关联的所有事件通知。如果请求的订阅对象没有关联的事件通知，则响应必须包含零事件通知。
successful-ok-events-complete: Indicates when this return is the last return for all Subscription objects that match the request, whether or not Event Notifications are returned. This condition occurs for Event Wait Mode with Notification Recipients waiting for responses when (1) the Subscription Object is canceled with a Cancel-Subscription operation, (2) the Subscription Object is deleted, when the Per-Printer Subscription lease time expires, or (3) the 'job-completed' event occurs for a Per-Job Subscription. This condition also occurs for a Get-Notifications request that a Notification Recipient makes after the job completes, but before the Event Life expires. See section 10.1. client-error-not-found: The Printer has no Subscription Objects whose "notify-subscription-id" attribute equals any of the values of the "notify-subscription-ids" operation attribute supplied, or the identified Subscription Object does not contain the "notify-pull-method" attribute with the 'ippget' keyword value. server-error-busy: The Printer is too busy to accept this operation. The Printer SHOULD return the "notify-get-interval" operation attribute in the Operation Attributes of the response; then the Notification Recipient SHOULD wait for the number of seconds specified by the "notify-get-interval" operation attribute before performing this operation again. If the "notify-get-interval" Operation Attribute is not present, the Notification Recipient SHOULD use the normal network back-off algorithms to determine when to perform this operation again.
successful ok events complete（成功确定事件完成）：指示此返回是与请求匹配的所有订阅对象的最后一次返回的时间，以及是否返回事件通知。当（1）使用取消订阅操作取消订阅对象，（2）删除订阅对象，每打印机订阅租用时间到期，或（3）每作业订阅发生“作业完成”事件时，对于事件等待模式，通知收件人等待响应，会发生此情况。对于通知收件人在作业完成后但在事件生命周期到期之前发出的获取通知请求，也会出现这种情况。见第10.1节。找不到客户端错误：打印机没有订阅对象，其“通知订阅id”属性等于提供的“通知订阅id”操作属性的任何值，或者标识的订阅对象不包含具有“ippget”关键字值的“通知拉取方法”属性。服务器错误忙：打印机太忙，无法接受此操作。打印机应在响应的操作属性中返回“notify get interval”操作属性；然后，通知收件人应等待“notify get interval”操作属性指定的秒数，然后再次执行此操作。如果“notify get interval”操作属性不存在，则通知收件人应使用正常的网络退避算法来确定何时再次执行此操作。
Natural Language and Character Set: The "attributes-charset" and "attributes-natural-language" attributes, as described in [RFC2911], section 3.1.4.2.
自然语言和字符集：“属性字符集”和“属性自然语言”属性，如[RFC2911]第3.1.4.2节所述。
The Printer MUST use the values of "notify-charset" and "notify-natural-language", respectively, from one Subscription Object associated with the Event Notifications in this response.
打印机必须分别使用与此响应中的事件通知关联的一个订阅对象中的“notify charset”和“notify natural language”值。
Normally, there is only one matched Subscription Object, or the value of the "notify-charset" and "notify-natural-language" attributes is the same in all Subscription Objects. If not, the Printer MUST pick one Subscription Object from which to obtain the value of these attributes. The algorithm for picking the Subscription Object is implementation dependent. The choice of natural language is not critical, because 'text' and 'name' values can override the "attributes-natural-language" operation attribute. The Printer's choice of charset
通常，只有一个匹配的订阅对象，或者所有订阅对象中“notify charset”和“notify natural language”属性的值相同。否则，打印机必须选择一个订阅对象，从中获取这些属性的值。拾取订阅对象的算法取决于实现。自然语言的选择并不重要，因为“text”和“name”值可以覆盖“attributes natural language”操作属性。打印机对字符集的选择
is critical because a bad choice may leave it unable to send some 'text' and 'name' values accurately.
是至关重要的，因为错误的选择可能使其无法准确发送某些“文本”和“名称”值。
The value of this operation attribute is the number of seconds that the Notification Recipient SHOULD wait before trying the Get-Notifications operation again. The Printer MUST return this operation attribute if (1) it is too busy to return events, (2) the Notification Recipient client did not request Event Wait Mode, or (3) the Printer is terminating Event Wait Mode. The client MUST accept this attribute and SHOULD reissue the Get-Notifications operation (with or without "notify-wait" = 'true') at the indicated number of seconds in the future in order to get more Event Notifications This value is intended to help the client be a good network citizen.
此操作属性的值是通知收件人在再次尝试获取通知操作之前应等待的秒数。如果（1）打印机太忙，无法返回事件，（2）通知收件人客户端未请求事件等待模式，或（3）打印机正在终止事件等待模式，则打印机必须返回此操作属性。客户端必须接受此属性，并应在未来指定的秒数重新发出Get Notifications（获取通知）操作（带或不带“notify wait”=“true”），以便获取更多事件通知。此值旨在帮助客户端成为一个良好的网络公民。
The value of this attribute MUST be at least as large as that of the Printer's "ippget-event-life" Printer Description attribute (see section 8.1). The Printer MAY return a value that is larger than that of the "ippget-event-life" Printer Description attribute provided that the Printer increases the Event Life for this Subscription object so that Notification Recipients taking account of the larger value and polling with a longer interval will not miss events. Note: Implementing such an algorithm requires some hidden attributes in the Subscription object that are IMPLEMENTATION DEPENDENT.
此属性的值必须至少与打印机的“ippget事件寿命”打印机描述属性的值一样大（请参阅第8.1节）。打印机返回的值可能大于“ippget event life”打印机描述属性的值，前提是打印机增加此订阅对象的事件寿命，以便考虑较大值和较长时间间隔轮询的通知收件人不会错过事件。注意：实现这样一个算法需要订阅对象中一些依赖于实现的隐藏属性。
If the Printer wants to remain in Event Wait Mode, then the Printer MUST NOT return this attribute in the response.
如果打印机希望保持事件等待模式，则打印机不得在响应中返回此属性。
Here is a complete table of combinations of "notify-wait", "status-code", "notify-get-interval", and Event Notification Attributes Groups for Get-Notification initial (Wait and No Wait) Responses and subsequent Event Wait Mode Responses (which may stay in Event Wait Mode or may request the Notification Recipient to leave Event Wait Mode):
以下是“通知等待”、“状态代码”、“通知获取间隔”和事件通知属性组的完整组合表，用于获取通知初始（等待和无等待）响应和后续事件等待模式响应（可能保持在事件等待模式或可能要求通知收件人离开事件等待模式）：
Table 2. Combinations of "notify-wait", "status-code", and "notify-get-interval"
表2。“通知等待”、“状态代码”和“通知获取间隔”的组合
Client sends: Printer returns: Printer Event returns: Notification "notify-wait" "status-code" "notify-get- Attribute interval" Groups
客户端发送：打印机返回：打印机事件返回：通知“通知等待”“状态代码”“通知获取-属性间隔”组
1. 'false'* 'successful-ok' MUST return N maybe 2. 'false'* 'not-found' MUST NOT MUST NOT 3. 'false'* 'busy' MUST return N MUST NOT
1. “false”*“successful ok”必须返回N或2。”false“*”未找到“不得为3”false'*'busy'必须返回N不能
4. 'false'* 'events- MUST NOT 'job-complete' completed' 5. 'true' 'successful-ok' MUST NOT MUST 6. 'true' 'successful-ok' MUST return N maybe 7. 'true' 'not-found' MUST NOT MUST NOT 8. 'true' 'busy' MUST return N MUST NOT 9. 'true' 'events- MUST NOT 'job-complete' completed' or maybe other * 'false' or client omits the "notify-wait" attribute.
4. 'false'*'事件-不得'job complete'已完成'5'true“成功确定”不能为6true“成功确定”必须返回N或7true“未找到”不能为8true“busy”必须返回N，不能返回9true“”事件-不能为“作业完成”“已完成”或其他*“false”，或者客户端忽略了“notify wait”属性。
Explanation:
说明：
1-4: Client does not request Event Wait Mode. 5-9: Client requests Event Wait Mode. 2,7: Subscription object not found, or was canceled earlier; client should NOT try again. 3,8: Server busy, tells client to try later; client should try again in N seconds. 4: Client polled after job completed, but before Event Life expired, and got the 'job-completed' event, so the client shouldn't bother trying again; client should NOT try again later. 5: Printer returns one or more Event Notifications and is OK to stay in Event Wait Mode; the client waits for more Event Notifications to be returned. 6: Printer wants to leave Event Wait mode. Can happen on the first response (with or without Event Notifications) or happen on a subsequent response with or without Event Notifications; the client SHOULD try again in N seconds. 9: Either (1) the printer returns 'job-completed' event, or (2) the Subscription Object was canceled by either a Cancel-Job or a Per-Printer Subscription expired without being renewed. For case (1), at least one Event Notification MUST be returned; for case (2), it is unlikely that any Event Notifications are returned, and the client should NOT try again.
1-4：客户端不请求事件等待模式。5-9：客户端请求事件等待模式。2,7：未找到订阅对象，或已提前取消；客户端不应重试。3,8：服务器忙，告诉客户端稍后再试；客户端应在N秒内重试。4：客户端在作业完成后，但在事件生命期到期之前进行了轮询，并获得了“作业已完成”事件，因此客户端不必费心再次尝试；客户端不应稍后重试。5：打印机返回一个或多个事件通知，可以保持事件等待模式；客户端等待返回更多事件通知。6：打印机要退出事件等待模式。可以发生在第一个响应上（有或没有事件通知），也可以发生在后续响应上（有或没有事件通知）；客户端应在N秒内重试。9:可能是（1）打印机返回“作业已完成”事件，或者（2）订阅对象已被取消作业取消，或者每打印机订阅已过期而未续订。对于情况（1），必须至少返回一个事件通知；对于案例（2），不太可能返回任何事件通知，客户端不应重试。
The value of this attribute is the Printer's "printer-up-time" attribute at the time when the Printer sends this response. The Printer MUST return this attribute. Because each Event Notification also contains the value of this attribute when the event occurred, the value of this attribute lets a Notification Recipient know when each Event Notification occurred relative to the time of this response.
此属性的值是打印机发送此响应时打印机的“打印机启动时间”属性。打印机必须返回此属性。由于每个事件通知在事件发生时也包含此属性的值，因此此属性的值使通知收件人知道相对于此响应的时间每个事件通知发生的时间。
Group 2: Unsupported Attributes See [RFC2911], section 3.1.7, for details on returning Unsupported Attributes.
第2组：不支持的属性有关返回不支持的属性的详细信息，请参见[RFC2911]，第3.1.7节。
Group 3 through N: Event Notification Attributes The Printer responds with one Event Notification Attributes Group per matched Event Notification. The entire response is considered a single Compound Event Notification (see [RFC3995]). The matched Event Notifications are all un-expired Event Notifications associated with the matched Subscription Objects and MUST follow the "Event Notification Ordering" requirements for Event Notifications within a Compound Event Notification specified in [RFC3995] section 9. In other words, the Printer MUST order these Event Notification groups in ascending time stamp (and sequence number) order for a Subscription object. If Event Notifications for multiple Subscription objects are being returned, the Notification Events for the next Subscription object follow in ascending time stamp order, etc.
组3到N：事件通知属性打印机对每个匹配的事件通知响应一个事件通知属性组。整个响应被视为单个复合事件通知（请参见[RFC3995]）。匹配的事件通知是与匹配的订阅对象关联的所有未过期事件通知，并且必须遵循[RFC3995]第9节中规定的复合事件通知中的事件通知“事件通知顺序”要求。换句话说，打印机必须按订阅对象的时间戳（和序列号）升序排列这些事件通知组。如果返回多个订阅对象的事件通知，则下一个订阅对象的通知事件将按时间戳升序排列，以此类推。
Each Event Notification Group MUST contain all of attributes specified in section 9.1 ("Content of Machine Consumable Event Notifications") of [RFC3995], with exceptions denoted by asterisks in the tables below.
每个事件通知组必须包含[RFC3995]第9.1节（“机器耗材事件通知的内容”）中规定的所有属性，下表中用星号表示的除外。
The tables below are identical to those in section 9.1 ("Content of Machine Consumable Event Notifications") of [RFC3995], except that each cell in the "Sends" column is a "MUST".
下表与[RFC3995]第9.1节（“机器耗材事件通知的内容”）中的表相同，但“发送”列中的每个单元格都是“必须”的。
If more than one Event Notification is being returned and the status of each is not the same, then the Printer MUST return a "notify-status-code" attribute in each Event Notification Attributes group to indicate the differing status values.
如果返回多个事件通知，且每个事件通知的状态不相同，则打印机必须在每个事件通知属性组中返回“通知状态代码”属性，以指示不同的状态值。
For an Event Notification for all Events, the Printer includes the attributes shown in Table 3.
对于所有事件的事件通知，打印机包括表3所示的属性。
Table 3. Attributes in Event Notification Content
表3。事件通知内容中的属性
Source Value Sends Source Object
源值发送源对象
notify-subscription-id (integer(1:MAX)) MUST Subscription notify-printer-uri (uri) MUST Subscription notify-subscribed-event (type2 keyword) MUST Event Notification printer-up-time (integer(1:MAX)) * MUST Printer printer-current-time (dateTime) MUST ** Printer
通知订阅id（整数（1:MAX））必须订阅通知打印机uri（uri）必须订阅通知订阅事件（type2关键字）必须事件通知打印机启动时间（整数（1:MAX））*必须打印机当前时间（日期时间）必须**打印机
notify-sequence-number (integer (0:MAX)) MUST Subscription
notify-charset (charset) MUST Subscription
notify-natural-language (naturalLanguage) MUST Subscription
notify-user-data (octetString(63)) MUST *** Subscription
notify-text (text) MUST Event
Notification
attributes from the "notify-attributes" MUST **** Printer
attribute
attributes from the "notify-attributes" MUST **** Job
attribute
attributes from the "notify-attributes" MUST **** Subscription
attribute
notify-sequence-number (integer (0:MAX)) MUST Subscription
notify-charset (charset) MUST Subscription
notify-natural-language (naturalLanguage) MUST Subscription
notify-user-data (octetString(63)) MUST *** Subscription
notify-text (text) MUST Event
Notification
attributes from the "notify-attributes" MUST **** Printer
attribute
attributes from the "notify-attributes" MUST **** Job
attribute
attributes from the "notify-attributes" MUST **** Subscription
attribute
* As specified in [RFC3995] section 9, the value of the "printer-up-time" attribute sent in each Event Notification MUST be the time at which the Event occurred, not the time at which the Event Notification was sent.
* 按照[RFC3995]第9节的规定，每个事件通知中发送的“打印机启动时间”属性的值必须是事件发生的时间，而不是发送事件通知的时间。
** The Printer MUST send the "printer-current-time" attribute if and only if it supports the "printer-current-time" attribute on the Printer object.
**当且仅当打印机对象支持“打印机当前时间”属性时，打印机必须发送“打印机当前时间”属性。
*** If the associated Subscription Object does not contain a
"notify-user-data" attribute, the Printer MUST send an
octet-string of length 0.
*** If the associated Subscription Object does not contain a
"notify-user-data" attribute, the Printer MUST send an
octet-string of length 0.
**** If the "notify-attributes" attribute is present on the
Subscription Object, the Printer MUST send all attributes
specified by the "notify-attributes" attribute. Note: If the
Printer doesn't support the "notify-attributes" attribute, it
is not present on the associated Subscription Object.
**** If the "notify-attributes" attribute is present on the
Subscription Object, the Printer MUST send all attributes
specified by the "notify-attributes" attribute. Note: If the
Printer doesn't support the "notify-attributes" attribute, it
is not present on the associated Subscription Object.
For Event Notifications for Job Events, the Printer includes the additional attributes shown in Table 4.
对于作业事件的事件通知，打印机包括表4所示的附加属性。
Table 4. Additional Attributes in Event Notification Content for Job Events
表4。作业事件的事件通知内容中的其他属性
Source Value Sends Source Object
源值发送源对象
job-id (integer(1:MAX)) MUST Job job-state (type1 enum) MUST Job job-state-reasons (1setOf type2 keyword) MUST Job job-impressions-completed (integer(0:MAX)) MUST * Job
作业id（整数（1:MAX））必须作业状态（type1枚举）必须作业状态原因（1setOf type2关键字）必须作业印象完成（整数（0:MAX））必须*作业
* The Printer MUST send the "job-impressions-completed" attribute in an Event Notification only for the combinations of Events and Subscribed Events shown in Table 5.
* 打印机必须在事件通知中发送“job impressions completed”（作业印象完成）属性，该属性仅适用于表5所示的事件和订阅事件的组合。
Table 5. Combinations of Events and Subscribed Events for "job-impressions-completed"
表5。“工作印象完成”的事件和订阅事件组合
Job Event Subscribed Job Event
作业事件订阅的作业事件
'job-progress' 'job-progress' 'job-completed' 'job-completed' 'job-completed' 'job-state-changed'
“作业进度”“作业进度”“作业已完成”“作业已完成”“作业已完成”“作业状态已更改”
For Event Notification for Printer Events, the Printer includes the additional attributes shown in Table 6.
对于打印机事件的事件通知，打印机包括表6所示的附加属性。
Table 6. Additional Attributes in Event Notification Content for Printer Events
表6。打印机事件的事件通知内容中的其他属性
Source Value Sends Source Object
源值发送源对象
printer-state (type1 enum) MUST Printer printer-state-reasons (1setOf type2 keyword) MUST Printer printer-is-accepting-jobs (boolean) MUST Printer
打印机状态（type1枚举）必须打印机状态原因（1setOf type2关键字）必须打印机正在接受作业（布尔值）必须打印机
The 'ippget' Delivery Method does not define any addition Subscription Template attributes and has the conformance requirements for Subscription Template attributes defined in [RFC3995]. This section defines additional information about Subscription Template attributes defined in [RFC3995].
“ippget”传递方法未定义任何附加订阅模板属性，并且具有[RFC3995]中定义的订阅模板属性的一致性要求。本节定义了有关[RFC3995]中定义的订阅模板属性的其他信息。
This Subscription Template attribute identifies the Pull Delivery Method to be used for the Subscription Object (see [RFC3995]). To support the 'ippget' Pull Delivery Method defined in this document, the Printer MUST support this attribute with the following keyword value:
此订阅模板属性标识用于订阅对象的请求传递方法（请参见[RFC3995]）。要支持此文档中定义的“ippget”拉式传递方法，打印机必须支持具有以下关键字值的此属性：
'ippget': Indicates that the 'ippget' Pull Delivery Method is to be used for this Subscription Object.
“ippget”：表示此订阅对象将使用“ippget”拉式传递方法。
The 'ippget' Delivery Method has the conformance requirements for Subscription Description attributes defined in [RFC3995]. The 'ippget' Delivery Method does not define any addition Subscription Description attributes.
“ippget”交付方法具有[RFC3995]中定义的订阅描述属性的一致性要求。“ippget”传递方法未定义任何附加订阅描述属性。
This section defines additional Printer Description attributes for use with the 'ippget' Delivery Method.
本节定义与“ippget”传递方法一起使用的其他打印机描述属性。
This Printer Description attribute specifies the Event Life value that the Printer assigns to each Event; i.e., the number of seconds after an Event occurs during which a Printer will return that Event in an Event Notification in a Get-Notifications response. After the Event Life expires for the Event, the Printer MAY no longer return an Event Notification for that Event in a Get-Notifications response.
此打印机描述属性指定打印机分配给每个事件的事件寿命值；i、 例如，事件发生后的秒数，在此期间，打印机将在Get Notifications响应的事件通知中返回该事件。在事件的事件生存期到期后，打印机可能不再在Get Notifications响应中返回该事件的事件通知。
The Printer MUST support this attribute if it supports the 'ippget' Delivery Method. The value MUST be 15 or more (at least 15 seconds), and 60 (seconds) is the RECOMMENDED value to align with the PWG Job Monitoring MIB [RFC2707] jmGeneralJobPersistence and jmGeneralAttributePersistence objects.
如果打印机支持“ippget”传递方法，则必须支持此属性。该值必须大于等于15（至少15秒），60（秒）是与PWG作业监视MIB[RFC2707]jmGeneralJobPersistence和jmGeneralAttributePersistence对象对齐的建议值。
For example, assume the following:
例如，假设以下情况：
1. A client performs a Job Creation operation that creates a Subscription Object associated with the 'ippget' Delivery Method;
1. 客户端执行作业创建操作，创建与“ippget”传递方法关联的订阅对象；
2. An Event associated with the new Job occurs immediately after the Subscription Object is created;
2. 创建订阅对象后，立即发生与新作业关联的事件；
3. the same client or some other client performs a Get-Notifications operation so that the client is connected N seconds after the Job Creation operation.
3. 同一客户端或其他某个客户端执行获取通知操作，以便在作业创建操作后N秒连接该客户端。
Then, if N is less than the value of this attribute, the client(s) performing the Get-Notifications operations can expect not to miss any Event-Notifications, barring some unforeseen lack of memory space in the Printer. Note: The client MUST initiate the Get-Notifications at a time that is sufficiently less that N seconds to account for network latency so that it is connected to the Printer before N seconds elapses.
然后，如果N小于该属性的值，则执行Get Notifications操作的客户机可以预期不会错过任何事件通知，除非打印机中出现意外的内存空间不足。注意：客户端必须在少于N秒的时间启动Get通知，以考虑网络延迟，以便在N秒过去之前连接到打印机。
If a Printer supports the 'ippget' Delivery Method, it MUST keep 'completed', 'canceled', or 'aborted' Job objects in the Job Retention and/or Job History phases for at least as long as this attribute's value. The Printer MAY retain jobs longer that this value. See [RFC2911], section 4.3.7.1, and the discussion in [RFC3995] (regarding the 'job-completed' event). The latter explains that a Notification Recipient can query the Job after receiving a 'job-completed' Event Notification in order to find out other information about the job that is 'completed', 'aborted', or 'canceled'. However, this attribute has no effect on the Cancel-Subscription operation, which deletes the Subscription object immediately whether or not it contains the "notify-pull-method" attribute with the 'ippget' keyword value. Immediately thereafter, subsequent Get-Notifications Responses MUST NOT contain Event Notifications associated with the canceled Subscription object.
如果打印机支持“ippget”传递方法，则它必须在作业保留和/或作业历史记录阶段保留“已完成”、“已取消”或“已中止”作业对象的时间至少与此属性的值相同。打印机保留作业的时间可能超过此值。参见[RFC2911]，第4.3.7.1节和[RFC3995]中的讨论（关于“作业完成”事件）。后者解释说，通知收件人可以在收到“作业已完成”事件通知后查询作业，以查找有关“已完成”、“已中止”或“已取消”作业的其他信息。但是，此属性对取消订阅操作没有影响，取消订阅操作会立即删除订阅对象，无论其是否包含具有“ippget”关键字值的“notify pull method”属性。此后，后续的Get通知响应不得包含与已取消订阅对象关联的事件通知。
This section defines additional values for existing Printer Description attributes as defined in [RFC3995].
本节定义了[RFC3995]中定义的现有打印机描述属性的附加值。
The following keyword value for the "notify-pull-method-supported" attribute is added in order to support the new Delivery Method defined in this document:
“notify pull method supported”属性添加了以下关键字值，以支持本文档中定义的新交付方法：
'ippget': The IPP Notification Pull Delivery Method defined in this document.
“获取此IPP通知的传递方法”：在IPP中定义。
Table 7 lists the "operation-id" value defined in order to support the new Get-Notifications operation defined in this document.
表7列出了为支持本文档中定义的新Get Notifications操作而定义的“operation id”值。
Table 7. Operation-id Assignments
表7。操作id分配
Value Operation Name
值操作名
0x001C Get-Notifications
0x001C获取通知
The following status code is defined as an extension for this Delivery Method and is returned as the status code of the Get-Notifications operation in Group 1 or Group 3 to N (see section 5.2).
以下状态代码被定义为此传递方法的扩展，并作为组1或组3至N中获取通知操作的状态代码返回（请参阅第5.2节）。
The Printer MUST return the 'successful-ok-events-complete' status code to indicate when this Get-Notifications response is the last response for a Subscription object, whether or not there are Event Notifications being returned. This condition occurs for Event Wait Mode with Notification Recipients waiting for responses when (1) the Subscription Object is canceled with a Cancel-Subscription operation, (2) the Subscription object is deleted, when the Per-Printer Subscription lease time expires, or (3) the 'job-completed' event occurs for a Per-Job Subscription. This condition also occurs for a Get-Notifications request that a Notification Recipient makes after the job completes, but before the Event Life expires.
打印机必须返回“successful ok events complete”（成功确定事件完成）状态代码，以指示此Get Notifications（获取通知）响应何时是订阅对象的最后一个响应，以及是否返回了事件通知。当（1）使用取消订阅操作取消订阅对象，（2）删除订阅对象，每打印机订阅租用时间到期，或（3）每作业订阅发生“作业完成”事件时，对于事件等待模式，通知收件人等待响应，会发生此情况。对于通知收件人在作业完成后但在事件生命周期到期之前发出的获取通知请求，也会出现这种情况。
This section defines the encoding and transport considerations for this Delivery Method based on [RFC2910].
本节基于[RFC2910]定义了此交付方法的编码和传输注意事项。
The encoding of a Get-Notifications Response is modeled after the Get-Jobs Response (see [RFC2911]). In a Get-Notifications Response, each Event Notification Attributes Group MUST start with an 'event-notification-attributes-tag' (see the section "Encodings of Additional Attribute Tags" in [RFC3995]), and end with an 'end-of-attributes-tag'. In addition, for Event Wait Mode the multi-part/related is used to separate each multiple response (in time) to a single Get-Notifications Request.
Get Notifications响应的编码是在Get Jobs响应之后建模的（请参见[RFC2911]）。在Get Notifications响应中，每个事件通知属性组必须以“事件通知属性标记”（请参阅[RFC3995]中的“其他属性标记的编码”一节）开头，并以“属性结束标记”结尾。此外，对于事件等待模式，multi-part/related用于分离单个Get Notifications请求的多个响应（及时）。
The Printer returns Get-Notification Response as follows:
打印机返回Get通知响应，如下所示：
1. If the Notification Recipient client did not request Event Wait Mode ("notify-wait" = 'false' or omitted), the Printer ends the response with an 'end-of-attributes-tag' (see [RFC2911], Get-Jobs encoding), as with any operation response.
1. 如果通知收件人客户端未请求事件等待模式（“notify Wait”=“false”或省略），打印机将使用“属性结束标记”（参见[RFC2911]，获取作业编码）结束响应，与任何操作响应一样。
2. If the Notification Recipient client requests Event Wait Mode ("notify-wait" = 'true') and the Printer wishes to honor the request, the Printer MUST return the response as an application/ipp part inside a multi-part/related MIME media type. When one or more additional Events occur, the Printer returns each as an additional Event Notification Group using a separate application/ipp part under the multi-part/related type.
2. 如果通知接收者客户端请求事件等待模式（“notify Wait”=“true”），并且打印机希望执行该请求，则打印机必须将响应作为多部分/相关MIME媒体类型中的应用程序/ipp部分返回。当发生一个或多个附加事件时，打印机将使用多部分/相关类型下的单独应用程序/ipp部分，将每个事件作为附加事件通知组返回。
3. If the client requested Event Wait Mode ("notify-wait" = 'true'), but the Printer does not wish to honor the request in the initial response and wants the client explicitly polled for Event Notifications, the Printer MUST return the "notify-get-interval" operation attribute (see section 5.2.1). The Printer returns the
3. 如果客户端请求了事件等待模式（“notify Wait”=“true”），但打印机不希望在初始响应中执行该请求，并且希望显式轮询客户端以获取事件通知，则打印机必须返回“notify get interval”操作属性（参见第5.2.1节）。打印机返回打印结果
response as an application/ipp part that MAY be inside an multi-part/related type. The client MUST accept this response and reissue the Get-Notifications request in the future indicated by the value of the "notify-get-interval" attribute value.
作为应用程序/ipp部件响应，该部件可能位于多部件/相关类型内。客户端必须接受此响应，并在“notify Get interval”属性值指示的将来重新发出Get Notifications请求。
4. If the client requested Event Wait Mode ("notify-wait" = 'true'), and the Printer initially honored the request but later wishes to leave Event Wait Mode, the Printer MUST return the "notify-get-interval" operation attribute (see section 5.2.1). The Printer returns the response as an application/ipp part that MUST be inside an multi-part/related type.
4. 如果客户端请求事件等待模式（“notify Wait”=“true”），并且打印机最初接受了该请求，但后来希望离开事件等待模式，则打印机必须返回“notify get interval”操作属性（请参阅第5.2.1节）。打印机以应用程序/ipp部分的形式返回响应，该部分必须位于多部分/相关类型中。
NOTE: If a Notification Recipient fails to receive a response, it can ask the Printer for the same Event Notifications again. The Notification Recipient will receive the same Event Notifications that it should have received the first time, except for those Event Notifications that have expired in the meantime.
注意：如果通知收件人未能收到响应，它可以再次向打印机请求相同的事件通知。通知接收者将收到与其第一次应该收到的相同的事件通知，但同时过期的事件通知除外。
The Printer MAY chunk the responses, but this has no significance to the IPP semantics.
打印机可能会将响应分块，但这对IPP语义没有意义。
This notification delivery method uses the IPP transport and encoding [RFC2910] for the Get-Notifications operation with the following extension, allocated in [RFC3995]:
此通知传递方法使用IPP传输和编码[RFC2910]进行获取通知操作，扩展名如下，在[RFC3995]中分配：
Table 8. The "event-notification-attributes-tag" Value
表8。“事件通知属性标记”值
Tag Value (Hex) Meaning
标记值（十六进制）含义
0x07 "event-notification-attributes-tag"
0x07“事件通知属性标记”
This section lists the conformance requirements for clients and Printers.
本节列出了客户机和打印机的一致性要求。
It is OPTIONAL for a Printer to support IPP Notifications as defined in [RFC3995]. However, if a Printer supports IPP Notifications, the Printer MUST support the 'ippget' Delivery Method, as defined in this document, as one of its Delivery Methods. IPP Printers that conform to this specification
打印机支持[RFC3995]中定义的IPP通知是可选的。但是，如果打印机支持IPP通知，则打印机必须支持本文档中定义的“ippget”传递方法作为其传递方法之一。符合本规范的IPP打印机
1. MUST meet the conformance requirements defined in [RFC3995] for a Pull Delivery Method;
1. 必须满足[RFC3995]中规定的拉动式交付方法的一致性要求；
2. MUST support the Get-Notifications operation defined in section 5, including Event Wait Mode;
2. 必须支持第5节中定义的获取通知操作，包括事件等待模式；
3. MUST support the Subscription Template object attributes, as defined in section 6;
3. 必须支持第6节中定义的订阅模板对象属性；
4. MUST support the Subscription Description object attributes, as defined in section 7;
4. 必须支持第7节中定义的订阅描述对象属性；
5. MUST support the "ippget-event-life" Printer Description attribute defined in section 8.1, including retaining jobs in the Job Retention and/or Job History phases for at least as long as the value specified by the Printer's "ippget-event-life";
5. 必须支持第8.1节中定义的“ippget事件寿命”打印机描述属性，包括在作业保留和/或作业历史记录阶段保留作业的时间至少与打印机“ippget事件寿命”指定的值相同；
6. MUST support the additional values for IPP/1.1 Printer Description attributes defined in section 9;
6. 必须支持第9节中定义的IPP/1.1打印机描述属性的附加值；
7. MUST support the 'successful-ok-events-complete' status code, as described in section 10.1;
7. 必须支持第10.1节所述的“成功ok事件完成”状态代码；
8. MUST listen for the IPP Get-Notifications operation requests on IANA-assigned well-known port 631, unless explicitly configured by system administrators or site policies;
8. 除非系统管理员或站点策略明确配置，否则必须在IANA分配的已知端口631上侦听IPP Get Notifications操作请求；
9. SHOULD NOT listen for IPP Get-Notifications operation requests on any other port, unless explicitly configured by system administrators or site policies; and
9. 除非系统管理员或站点策略明确配置，否则不应在任何其他端口上侦听IPP Get通知操作请求；和
10. MUST meet the security conformance requirements stated in section 18.4.
10. 必须满足第18.4节规定的安全合规性要求。
It is OPTIONAL for an IPP Client to support IPP Notifications as defined in [RFC3995]. However, if a client supports IPP Notifications, the client MUST support the 'ippget' Delivery Method as defined in this document as one of its Delivery Methods. IPP Clients that conform to this specification:
IPP客户端支持[RFC3995]中定义的IPP通知是可选的。但是，如果客户端支持IPP通知，则客户端必须支持本文档中定义的“ippget”传递方法作为其传递方法之一。符合本规范的IPP客户机：
1. MUST create Subscription Objects by sending Subscription Creation operation requests containing the "notify-pull-method" attribute (as opposed to the "notify-recipient-uri" attribute) using the 'ippget' keyword value (see sections 6.1 and 15.2);
1. 必须通过使用“ippget”关键字值发送包含“notify pull method”属性（与“notify recipient uri”属性相反）的订阅创建操作请求来创建订阅对象（请参见第6.1节和第15.2节）；
2. MUST send IPP Get-Notifications operation requests (see section 5.1) via the port specified in the associated 'ipp' URL (if present) or otherwise via IANA-assigned well-known port 631;
2. 必须通过相关“IPP”URL中指定的端口（如果存在）或通过IANA分配的已知端口631发送IPP Get通知操作请求（见第5.1节）；
3. MUST convert the associated 'ipp' URLs for use in IPP Get-Notifications operation to their corresponding 'http' URL forms for use in the HTTP layer, according to the rules in section 5, "IPP URL Scheme", in [RFC2910]; and
3. 必须根据[RFC2910]第5节“ipp URL方案”中的规则，将用于ipp获取通知操作的相关“ipp”URL转换为相应的“http”URL格式，以便在http层中使用；和
4. MUST meet the security conformance requirements stated in section 18.5.
4. 必须满足第18.5节规定的安全合规性要求。
[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月。
[RFC2910] Herriot, R., Butler, S., Moore, P., Turner, R., and J. Wenn, "Internet Printing Protocol/1.1: Encoding and Transport", RFC 2910, September 2000.
[RFC2910]Herriot，R.，Butler，S.，Moore，P.，Turner，R.，和J.Wenn，“互联网打印协议/1.1：编码和传输”，RFC 29102000年9月。
[RFC2911] Hastings, T., Herriot, R., deBry, R., Isaacson, S., and P. Powell, "Internet Printing Protocol/1.1: Model and Semantics", RFC 2911, September 2000.
[RFC2911]黑斯廷斯，T.，赫里奥特，R.，德布里，R.，艾萨克森，S.，和P.鲍威尔，“互联网打印协议/1.1：模型和语义”，RFC 29112000年9月。
[RFC3995] Herriot, R. and T. Hastings, "Internet Printing Protocol (IPP): Event Notifications and Subscriptions", RFC 3995, March 2005.
[RFC3995]Herriot，R.和T.Hastings，“互联网打印协议（IPP）：事件通知和订阅”，RFC 39952005年3月。
[RFC2565] Herriot, R., Butler, S., Moore, P., and R. Turner, "Internet Printing Protocol/1.0: Encoding and Transport", RFC 2565, April 1999.
[RFC2565]Herriot，R.，Butler，S.，Moore，P.，和R.Turner，“互联网打印协议/1.0：编码和传输”，RFC 25651999年4月。
[RFC2566] deBry, R., Hastings, T., Herriot, R., Isaacson, S., and P. Powell, "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, April 1999.
[RFC2566]deBry，R.，Hastings，T.，Herriot，R.，Isaacson，S.，和P.Powell，“互联网打印协议/1.0：模型和语义”，RFC 2566，1999年4月。
[RFC2567] Wright, F., "Design Goals for an Internet Printing Protocol", RFC 2567, April 1999.
[RFC2567]Wright，F.，“互联网打印协议的设计目标”，RFC2567，1999年4月。
[RFC2568] Zilles, S., "Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol", RFC 2568, April 1999.
[RFC2568]Zilles，S.“互联网打印协议模型和协议结构的基本原理”，RFC 2568，1999年4月。
[RFC2569] Herriot, R., Hastings, T., Jacobs, N., and J. Martin, "Mapping between LPD and IPP Protocols", RFC 2569, April 1999.
[RFC2569]Herriot，R.，Hastings，T.，Jacobs，N.，和J.Martin，“LPD和IPP协议之间的映射”，RFC 2569，1999年4月。
[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月。
[RFC2707] Bergman, R., Hastings, T., Isaacson, S., and H. Lewis, "Job Monitoring MIB - V1.0", RFC 2707, November 1999.
[RFC2707]伯格曼，R.，黑斯廷斯，T.，艾萨克森，S.，和H.刘易斯，“工作监控MIB-V1.0”，RFC 2707，1999年11月。
[RFC3196] Hastings, T., Manros, C., Zehler, P., Kugler, C., and H. Holst, "Internet Printing Protocol/1.1: Implementor's Guide", RFC 3196, November 2001.
[RFC3196]黑斯廷斯，T.，曼罗斯，C.，泽勒，P.，库格勒，C.，和H.霍尔斯特，“互联网打印协议/1.1：实施者指南”，RFC 31962001年11月。
[RFC3997] Hastings, T., Ed., deBry, R., and H. Lewis, "Internet Printing Protocol (IPP): Requirements for IPP Notifications", RFC 3997, March 2005.
[RFC3997]Hastings，T.，Ed.，deBry，R.，和H.Lewis，“互联网打印协议（IPP）：IPP通知的要求”，RFC 39972005年3月。
This section contains the exact information that the IANA has added to the IPP Registries according to the procedures defined in [RFC2911], section 6. These registrations have been published in the http://www.iana.org/assignments/ipp-registrations registry.
本节包含IANA根据[RFC2911]第6节中规定的程序添加到IPP登记册的确切信息。这些注册已在http://www.iana.org/assignments/ipp-registrations 登记处。
The following table lists the attributes defined in this document. This has been registered according to the procedures in RFC 2911 [RFC2911] section 6.2.
下表列出了本文档中定义的属性。已根据RFC 2911[RFC2911]第6.2节中的程序进行了登记。
Printer Description attributes: Reference Section
------------------------------- --------- -------
ippget-event-life (integer(15:MAX)) [RFC3996] 8.1
Printer Description attributes: Reference Section
------------------------------- --------- -------
ippget-event-life (integer(15:MAX)) [RFC3996] 8.1
15.2. Delivery Method and Additional Keyword Attribute Value Registrations for Existing Attributes
15.2. 现有属性的传递方法和附加关键字属性值注册
This section lists additional keyword attribute value registrations for use with existing attributes defined in other documents. These have been registered according to the procedures in [RFC2911], section 6.1. According to [RFC3995], section 24.7.3, Pull Delivery Method registrations are the keyword attribute value registrations for the "notify-pull-method" and "notify-pull-method-supported" attributes.
本节列出了用于其他文档中定义的现有属性的其他关键字属性值注册。已根据[RFC2911]第6.1节中的程序进行了登记。根据[RFC3995]第24.7.3节，拉动交付方法注册是“通知拉动方法”和“支持的通知拉动方法”属性的关键字属性值注册。
Attribute (attribute syntax)
Values Reference Section
----------------------- --------- -------
notify-pull-method (type2 keyword) [RFC3995] 5.3.2
notify-pull-method-supported (1setOf type2 keyword)
[RFC3995] 5.3.2.1
ippget [RFC3996] 9.1
Attribute (attribute syntax)
Values Reference Section
----------------------- --------- -------
notify-pull-method (type2 keyword) [RFC3995] 5.3.2
notify-pull-method-supported (1setOf type2 keyword)
[RFC3995] 5.3.2.1
ippget [RFC3996] 9.1
The following table lists the enum attribute values defined in this document. These have been registered according to the procedures in [RFC2911], section 6.1.
下表列出了在此文档中定义的枚举属性值。已根据[RFC2911]第6.1节中的程序进行了登记。
Attribute (attribute syntax)
Value Name Reference Section
------ ----------------------------- --------- -------
operations-supported (1setOf type2 enum) [RFC2911] 4.4.15
0x001C Get-Notifications [RFC3996] 9.2
Attribute (attribute syntax)
Value Name Reference Section
------ ----------------------------- --------- -------
operations-supported (1setOf type2 enum) [RFC2911] 4.4.15
0x001C Get-Notifications [RFC3996] 9.2
The following table lists the operations defined in this document. This has been registered according to the procedures in RFC 2911 [RFC2911] section 6.4.
下表列出了本文档中定义的操作。已根据RFC 2911[RFC2911]第6.4节中的程序进行了登记。
Operations: Reference Section
----------- --------- -------
Get-Notifications [RFC3996] 5
Operations: Reference Section
----------- --------- -------
Get-Notifications [RFC3996] 5
The following table lists the status codes defined in this document. This has been registered according to the procedures in [RFC2911], section 6.6.
下表列出了本文档中定义的状态代码。已根据[RFC2911]第6.6节中的程序进行了登记。
Status codes: Reference Section
------------- --------- -------
successful-ok-events-complete (0x0007) [RFC3996] 10.1
Status codes: Reference Section
------------- --------- -------
successful-ok-events-complete (0x0007) [RFC3996] 10.1
The IPP Printer MUST localize the "notify-text" attribute as specified in section 14 of [RFC3995].
IPP打印机必须按照[RFC3995]第14节的规定本地化“通知文本”属性。
In addition, when the client receives the Get-Notifications response, it is expected to localize the attributes that have the 'keyword' attribute syntax according to the charset and natural language requested in the Get-Notifications request.
此外，当客户端接收到Get Notifications响应时，它将根据Get Notifications请求中请求的字符集和自然语言来本地化具有“关键字”属性语法的属性。
The IPP Model and Semantics document [RFC2911, section 8] discusses high-level security requirements (Client Authentication, Server Authentication and Operation Privacy). The IPP Transport and Encoding document [RFC2910, section 8] discusses the security requirements for the IPP protocol. Client Authentication is the mechanism by which the client proves its identity to the server in a secure manner. Server Authentication is the mechanism by which the server proves its identity to the client in a secure manner. Operation Privacy is defined as a mechanism for protecting operations from eavesdropping.
IPP模型和语义文档[RFC2911，第8节]讨论了高级安全要求（客户端身份验证、服务器身份验证和操作隐私）。IPP传输和编码文件[RFC2910，第8节]讨论了IPP协议的安全要求。客户端身份验证是客户端以安全的方式向服务器证明其身份的机制。服务器身份验证是服务器以安全的方式向客户端证明其身份的机制。操作隐私被定义为防止操作被窃听的机制。
The 'ippget' Delivery Method with its Get-Notifications operations leverages the security mechanism that are used in IPP/1.1 [RFC2910 and RFC2911] without adding any additional security mechanisms in order to maintain the same security support as IPP/1.1.
“ippget”交付方法及其Get通知操作利用IPP/1.1[RFC2910和RFC2911]中使用的安全机制，而无需添加任何其他安全机制，以保持与IPP/1.1相同的安全支持。
The access control model for the Get-Notifications operation defined in this document is the same as the access control model for the Get-Job-Attributes operation (see [RFC2911], section 3.2.6). The primary difference is that a Get-Notifications operation is directed at Subscription Objects rather than at Job objects, and a returned attribute group contains Event Notification attributes rather than Job object attributes.
本文档中定义的获取通知操作的访问控制模型与获取作业属性操作的访问控制模型相同（请参见[RFC2911]，第3.2.6节）。主要区别在于获取通知操作针对的是订阅对象而不是作业对象，并且返回的属性组包含事件通知属性而不是作业对象属性。
The Notification Recipient client MUST have the following access rights to the Subscription object(s) targeted by the Get-Notifications operation request:
通知收件人客户端必须对Get Notifications操作请求所针对的订阅对象具有以下访问权限：
The authenticated user (see [RFC2911], section 8.3) performing this operation MUST be (1) the owner of each Subscription Object identified by the "notify-subscription-ids" operation attribute (see section 5.1.1), (2) an operator or administrator of the Printer (see [RFC2911], sections 1 and 8.5), or (3) otherwise authorized by the Printer's administrator-configured security policy to request Event Notifications from the target Subscription Object(s). Furthermore, the Printer's security policy MAY limit
执行此操作的经过身份验证的用户（请参见[RFC2911]，第8.3节）必须是（1）由“通知订阅ID”操作属性标识的每个订阅对象的所有者（请参见第5.1.1节），（2）打印机的操作员或管理员（请参见[RFC2911]，第1节和第8.5节），或（3）打印机管理员以其他方式授权配置的安全策略从目标订阅对象请求事件通知。此外，打印机的安全策略可能会限制
the attributes returned by the Get-Notifications operation, in a manner similar to that of the Get-Job-Attributes operation (see [RFC2911], end of section 3.3.4.2).
获取通知操作返回的属性，其方式类似于获取作业属性操作（参见[RFC2911]，第3.3.4.2节末尾）。
Because the Get-Notifications operation is sent in the same direction as are Job Creation operations, usually by the same client, this Event Notification Delivery Method poses no additional authentication, authorization, privacy, firewall, or port assignment issues above those for the IPP Get-Job-Attributes and Get-Printer-Attributes operations (see [RFC2911], sections 3.2.6 and 3.2.5).
由于Get Notifications操作与Job Creation操作的发送方向相同，通常由同一客户端发送，因此此事件通知传递方法不会在IPP Get Job Attributes和Get Printer Attributes操作的基础上产生额外的身份验证、授权、隐私、防火墙或端口分配问题（参见[RFC2911]，第3.2.6节和第3.2.5节）。
Unwanted Events Notifications (spam): Unlike Push Event Notification Delivery Methods in which the IPP Printer initiates the Event Notification, with the Pull Delivery Method defined in this document, the Notification Recipient is the client that initiates the Get-Notifications operation (see section 5). Therefore, with this method there is no chance of "spam" notifications.
不需要的事件通知（垃圾邮件）：与IPP打印机启动事件通知的推送事件通知传递方法不同，使用本文档中定义的推送传递方法，通知收件人是启动获取通知操作的客户端（请参阅第5节）。因此，使用此方法不会出现“垃圾邮件”通知。
Note: When a client stays connected to a Printer by using the Event Wait Mode (see section 5.1.3) in order to receive Event Notifications as they occur, it can close down the IPP connection at any time and so can avoid future unwanted Event Notifications at any time.
注意：当客户端通过使用事件等待模式（见第5.1.3节）保持与打印机的连接，以便在事件发生时接收事件通知时，它可以随时关闭IPP连接，从而避免将来任何时候出现不必要的事件通知。
It is true that the client has control over whether to ask for Event Notifications. However, if the client subscribes to an event and does a Get-Notifications request, it gets all events for the Subscription Object in the sequence number range (see section 5.1.2), not just those it wants. If a client subscribes to a Per-Printer Subscription job event, such as 'job-completed', and someone then starts and cancels thousands of jobs, the client would have to receive these events in addition to those it is interested in. A client can protect itself better by subscribing to its own jobs by using a Per-Job Subscription, rather than create a Per-Printer subscription whose Job events apply to all jobs.
确实，客户端可以控制是否请求事件通知。但是，如果客户端订阅一个事件并执行Get NOTITITIONS请求，它将获取订阅对象在序列号范围内的所有事件（请参见第5.1.2节），而不仅仅是它想要的事件。如果客户机订阅每打印机订阅作业事件，如“作业已完成”，然后有人启动并取消数千个作业，则客户机将不得不在其感兴趣的事件之外接收这些事件。客户端可以通过使用每作业订阅来订阅自己的作业，而不是创建作业事件应用于所有作业的每打印机订阅，从而更好地保护自己。
For the Get-Notifications operation defined in this document, the same Printer conformance requirements apply for supporting and using Client Authentication, Server Authentication and Operation Privacy as stated in [RFC2910] section 8 for all IPP operations.
对于本文档中定义的获取通知操作，相同的打印机一致性要求适用于支持和使用[RFC2910]第8节中规定的所有IPP操作的客户端身份验证、服务器身份验证和操作隐私。
For the Get-Notifications operation defined in this document, the same client conformance requirements apply for supporting and using Client Authentication, Server Authentication, and Operation Privacy as stated in [RFC2910], section 8, for all IPP operations.
对于本文档中定义的获取通知操作，相同的客户端一致性要求适用于支持和使用[RFC2910]第8节中规定的所有IPP操作的客户端身份验证、服务器身份验证和操作隐私。
The base set of IPP documents includes the following:
IPP文件的基本集包括以下内容：
Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementer's Guide [RFC3196]
Mapping between LPD and IPP Protocols [RFC2569]
Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementer's Guide [RFC3196]
Mapping between LPD and IPP Protocols [RFC2569]
"Design Goals for an Internet Printing Protocol" takes a broad look at distributed printing functionality, and it enumerates real-life scenarios that help clarify the features that need to be included in a printing protocol for the Internet. It identifies requirements for three types of users: end users, operators, and administrators. It calls out a subset of end user requirements that are satisfied in IPP/1.0 [RFC2566, RFC2565]. A few OPTIONAL operator operations have been added to IPP/1.1.
“Internet打印协议的设计目标”广泛介绍了分布式打印功能，并列举了有助于澄清需要包含在Internet打印协议中的功能的实际场景。它确定了三类用户的需求：最终用户、操作员和管理员。它调用了IPP/1.0[RFC2566，RFC2565]中满足的最终用户需求子集。IPP/1.1中增加了一些可选的操作员操作。
"Rationale for the Structure and Model and Protocol for the Internet Printing Protocol" describes IPP from a high-level view, defines a roadmap for the various documents that form the suite of IPP specification documents, and gives background and rationale for the IETF working group's major decisions.
“互联网打印协议的结构、模型和协议的基本原理”从高层角度描述了IPP，定义了构成IPP规范文件套件的各种文件的路线图，并给出了IETF工作组主要决策的背景和基本原理。
"Internet Printing Protocol/1.1: Model and Semantics" describes a simplified model with abstract objects, their attributes, and their operations that are independent of encoding and transport. It introduces a Printer and a Job object. The Job object optionally supports multiple documents per Job. It also addresses security, internationalization, and directory issues.
“Internet打印协议/1.1：模型和语义”描述了一个简化模型，其中包含抽象对象、其属性以及独立于编码和传输的操作。它引入了打印机和作业对象。作业对象可以选择为每个作业支持多个文档。它还解决了安全性、国际化和目录问题。
"Internet Printing Protocol/1.1: Encoding and Transport" is a formal mapping of the abstract operations and attributes defined in the model document onto HTTP/1.1 [RFC2616]. It defines the encoding rules for a new Internet MIME media type called "application/ipp". This document also defines the rules for transporting over HTTP a message body whose Content-Type is "application/ipp". This document defines the 'ipp' scheme for identifying IPP printers and jobs.
“Internet打印协议/1.1：编码和传输”是模型文档中定义的抽象操作和属性到HTTP/1.1[RFC2616]的正式映射。它定义了名为“应用程序/ipp”的新Internet MIME媒体类型的编码规则。本文档还定义了通过HTTP传输内容类型为“application/ipp”的消息体的规则。本文件定义了识别ipp打印机和作业的“ipp”方案。
"Internet Printing Protocol/1.1: Implementer's Guide" gives insight and advice to implementers of IPP clients and IPP objects. It is intended to help them understand IPP/1.1 and some of the considerations that may assist them in the design of their client and/or IPP object implementations. For example, a typical order of processing requests is given, including error checking. Motivation for some of the specification decisions is also included.
“互联网打印协议/1.1：实施者指南”为IPP客户端和IPP对象的实施者提供了见解和建议。它旨在帮助他们理解IPP/1.1以及一些可能有助于他们设计客户端和/或IPP对象实现的注意事项。例如，给出了处理请求的典型顺序，包括错误检查。还包括一些规范决策的动机。
"Mapping between LPD and IPP Protocols" gives some advice to implementers of gateways between IPP and LPD (Line Printer Daemon) implementations.
“LPD和IPP协议之间的映射”为IPP和LPD（Line Printer Daemon）实现之间网关的实现者提供了一些建议。
Carl Kugler and Harry Lewis contributed the basic idea of in-band "smart polling" coupled with multiple responses for a single operation on the same connection, with one response for each event as it occurs. Without their continual persuasion, we would not have arrived at this Delivery Method specification and would not have been able to agree on a single REQUIRED Delivery Method for IPP.
卡尔·库格勒（Carl Kugler）和哈里·刘易斯（Harry Lewis）提出了带内“智能轮询”的基本思想，并在同一连接上为单个操作提供了多个响应，每个事件发生时都有一个响应。如果没有他们的持续劝说，我们将无法达成本交付方法规范，也无法就IPP的单一要求交付方法达成一致。
Carl Kugler IBM Corporation 6300 Diagonal Highway Boulder, CO 80301
卡尔·库格勒IBM公司科罗拉多州博尔德市6300对角线公路80301
EMail: kugler@us.ibm.com
EMail: kugler@us.ibm.com
Authors' Addresses
作者地址
Robert Herriot Global Workflow Solutions 706 Colorado Ave. Palo Alto, CA 94303
Robert Herriot全球工作流解决方案加利福尼亚州帕洛阿尔托市科罗拉多大道706号，邮编94303
Phone: 650-324-4000 EMail: bob@herriot.com
电话：650-324-4000电子邮件：bob@herriot.com
Thomas N. Hastings Xerox Corporation 710 S Aviation Blvd. ESAE 242 El Segundo CA 90245
托马斯·N·黑斯廷斯·施乐公司航空大道710号。ESAE 242加利福尼亚州塞贡多市90245
Phone: 310-333-6413 Fax: 310-333-6342 EMail: hastings@cp10.es.xerox.com
电话：310-333-6413传真：310-333-6342电子邮件：hastings@cp10.es.xerox.com
Harry Lewis IBM Corporation 6300 Diagonal Hwy Boulder, CO 80301
Harry Lewis IBM Corporation科罗拉多州博尔德市6300号对角公路80301
Phone: (303) 924-5337 EMail: harryl@us.ibm.com
电话：（303）924-5337电子邮件：harryl@us.ibm.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。