draft-ietf-ipp-notify-get-06.txt   draft-ietf-ipp-notify-get-07.txt 
Internet Printing Protocol WG Robert Herriot (editor) Internet Printing Protocol WG R. Herriot
INTERNET-DRAFT Thomas N. Hastings INTERNET-DRAFT consultant
<draft-ietf-ipp-notify-get-06.txt> Xerox Corp. <draft-ietf-ipp-notify-get-07.txt> T. Hastings
Updates: RFC 2911 Carl Kugler Updates: RFC 2911 Xerox Corp.
[Target category: standards track] Harry Lewis [Target category: standards track] June 27, 2002
IBM, Corp. Expires: December 27, 2002
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
The 'ippget' Delivery Method for Event Notifications The 'ippget' Delivery Method for Event Notifications
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Status of this Memo: Status of this Memo:
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of [rfc2026]. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress". material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed as The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document describes an extension to the Internet Printing This document describes an extension to the Internet Printing
Protocol/1.0 (IPP) [RFC2566, RFC2565] and IPP/1.1 [RFC2911, RFC2910]. Protocol/1.1: Model and Semantics (RFC 2911, RFC 2910). This
This document specifies the 'ippget' Delivery Method for use with the document specifies the 'ippget' Delivery Method for use with the
"IPP Event Notifications and Subscriptions" specification [ipp-ntfy]. "Internet Printing Protocol (IPP): Event Notifications and
When IPP Notification [ipp-ntfy] is supported, the Delivery Method Subscriptions" specification. When IPP Notification [ipp-ntfy] is
defined in this document is one of the RECOMMENDED Delivery Methods supported, the Delivery Method defined in this document is the
for Printers to support. REQUIRED Delivery Method for clients and Printers to support. They
MAY support additional Delivery Methods.
The 'ippget' Delivery Method is a 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)
Event Notifications using the Get-Notifications operation. If the
Notification Recipient has selected the Event Wait Mode option to
wait for additional Event Notifications, the Printer continues to
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
The 'ippget' Delivery Method is a 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) Event Notifications using the Get-Notifications operation.
If the Notification Recipient has selected the Event Wait Mode option
to wait for additional Event Notifications, the Printer continues to
return Event Notifications to the Notification Recipient as Get- return Event Notifications to the Notification Recipient as Get-
Notification responses as Events occur using the connection Notification responses as Events occur using the connection
originated by the Notification Recipient. originated by the Notification Recipient.
Either the Notification Recipient or the Printer can terminate Event Either the Notification Recipient or the Printer can terminate Event
Wait Mode without closing the connection. Wait Mode without closing the connection.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Table of Contents Table of Contents
1 Introduction.....................................................5 1 Introduction.....................................................5
2 Terminology......................................................6 2 Terminology......................................................6
3 Model and Operation..............................................7 3 Model and Operation..............................................7
4 General Information..............................................8 4 General Information..............................................8
skipping to change at page 3, line 30 skipping to change at page 3, line 28
5.1.2 notify-sequence-numbers (1setOf integer(1:MAX)).............11 5.1.2 notify-sequence-numbers (1setOf integer(1:MAX)).............11
5.1.3 notify-wait (boolean).......................................12 5.1.3 notify-wait (boolean).......................................12
5.2 Get-Notifications Response....................................13 5.2 Get-Notifications Response....................................13
5.2.1 notify-get-interval (integer(0:MAX))........................16 5.2.1 notify-get-interval (integer(0:MAX))........................16
5.2.2 printer-up-time (integer(1:MAX))............................18 5.2.2 printer-up-time (integer(1:MAX))............................18
5.2.3 redirect-uri (uri)..........................................18 5.2.3 redirect-uri (uri)..........................................18
6 Additional Information about Subscription Template Attributes...22 6 Additional Information about Subscription Template Attributes...22
6.1 notify-pull-method (type2 keyword)............................22 6.1 notify-pull-method (type2 keyword)............................22
7 Subscription Description Attributes.............................23 7 Subscription Description Attributes.............................22
8 Additional Printer Description Attributes.......................23 8 Additional Printer Description Attributes.......................23
8.1 ippget-event-life (integer(15:MAX))...........................23 8.1 ippget-event-life (integer(15:MAX))...........................23
9 New Values for Existing Printer Description Attributes..........24 9 New Values for Existing Printer Description Attributes..........24
9.1 notify-pull-method-supported (1setOf type2 keyword)...........24 9.1 notify-pull-method-supported (1setOf type2 keyword)...........24
9.2 operations-supported (1setOf type2 enum)......................24 9.2 operations-supported (1setOf type2 enum)......................24
10 New Status Codes...............................................25 10 New Status Codes...............................................24
10.1 successful-ok-events-complete (0x0007).......................25 10.1 successful-ok-events-complete (0x0007).......................25
10.2 redirection-other-site (0x0300)..............................25 10.2 redirection-other-site (0x0300)..............................25
11 Encoding and Transport.........................................25 11 Encoding and Transport.........................................25
12 Conformance Requirements.......................................27 12 Conformance Requirements.......................................27
12.1 Conformance for IPP Printers.................................27 12.1 Conformance for IPP Printers.................................27
12.2 Conformance for IPP Clients..................................28 12.2 Conformance for IPP Clients..................................28
13 IANA Considerations............................................28 13 Normative References...........................................28
13.1 Additional attribute value registrations for existing attributes
29
INTERNET-DRAFT IPP: The 'ippget' Delivery Method 14 Informative References.........................................29
13.1.1 Additional values for the "notify-pull-method-supported" 15 Security Considerations........................................30
Printer attribute......................................29 15.1 Notification Recipient client access rights..................30
13.1.2 Additional values for the "operations-supported" Printer 15.2 Printer security threats.....................................31
attribute..............................................29 15.3 Notification Recipient security threats......................31
13.2 Operation Registrations......................................30 15.4 Security requirements for Printers...........................31
13.3 Attribute Registrations......................................30 15.5 Security requirements for clients............................32
13.4 Status code Registrations....................................30
14 Internationalization Considerations............................31 16 Internationalization Considerations............................32
15 Security Considerations........................................31 17 IANA Considerations............................................32
17.1 Additional attribute value registrations for existing attributes
32
17.1.1 Additional values for the "notify-pull-method-supported"
Printer attribute......................................32
17.1.2 Additional values for the "operations-supported" Printer
attribute..............................................33
17.2 Operation Registrations......................................33
17.3 Attribute Registrations......................................33
17.4 Status code Registrations....................................34
16 References.....................................................31 18 Contributors...................................................34
17 Authors' Addresses.............................................33 19 Authors' Addresses.............................................35
18 Description of Base IPP documents..............................34 20 Description of Base IPP documents..............................35
19 Full Copyright Statement.......................................35 21 Full Copyright Statement.......................................37
Table of Tables Table of Tables
Table 1 - Information about the Delivery Method....................8 Table 1 - Information about the Delivery Method....................8
Table 2 - Combinations of "notify-wait", "status-code", and "notify- Table 2 - Combinations of "notify-wait", "status-code", and "notify-
get-interval" .................................................17 get-interval" .................................................17
Table 3 - Attributes in Event Notification Content................20 Table 3 - Attributes in Event Notification Content................20
Table 4 - Additional Attributes in Event Notification Content for Job Table 4 - Additional Attributes in Event Notification Content for Job
Events ........................................................21 Events ........................................................21
Table 5 - Combinations of Events and Subscribed Events for "job- Table 5 - Combinations of Events and Subscribed Events for "job-
impressions-completed" ........................................22 impressions-completed" ........................................21
Table 6 - Additional Attributes in Event Notification Content for Table 6 - Additional Attributes in Event Notification Content for
Printer Events ................................................22 Printer Events ................................................22
Table 7 - Operation-id assignments................................25 Table 7 - Operation-id assignments................................24
Table 8 - The "event-notification-attributes-tag" value...........27 Table 8 - The "event-notification-attributes-tag" value...........27
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
1 Introduction 1 Introduction
The "IPP Event Notifications and Subscriptions" document [ipp-ntfy] The "IPP Event Notifications and Subscriptions" document [ipp-ntfy]
defines an OPTIONAL extension to Internet Printing Protocol/1.0 (IPP) defines an OPTIONAL extension to Internet Printing Protocol/1.1:
[RFC2566, RFC2565] and IPP/1.1 [RFC2911, RFC2910]. For a description Model and Semantics [RFC2911, RFC2910]. For a description of the
of the base IPP documents, see section 18. The [ipp-ntfy] extension base IPP documents, see section 20. The [ipp-ntfy] extension defines
defines operations that a client can perform in order to create operations that a client can perform in order to create Subscription
Subscription Objects in a Printer and carry out other operations on Objects in a Printer and carry out other operations on them. A
them. A Subscription Object represents a Subscription abstraction. Subscription Object represents a Subscription abstraction. A client
A client associates Subscription Objects with a particular Job by associates Subscription Objects with a particular Job by performing
performing the Create-Job-Subscriptions operation or by submitting a the Create-Job-Subscriptions operation or by submitting a Job with
Job with subscription information. A client associates Subscription subscription information. A client associates Subscription Objects
Objects with the Printer by performing a Create-Printer-Subscriptions with the Printer by performing a Create-Printer-Subscriptions
operation. Four other operations are defined for Subscription operation. Four other operations are defined for Subscription
Objects: Get-Subscriptions-Attributes, Get-Subscriptions, Renew- Objects: Get-Subscriptions-Attributes, Get-Subscriptions, Renew-
Subscription, and Cancel-Subscription. The Subscription Object Subscription, and Cancel-Subscription. The Subscription Object
specifies that when one of the specified Events occurs, the Printer specifies that when one of the specified Events occurs, the Printer
sends an asynchronous Event Notification to the specified sends an asynchronous Event Notification to the specified
Notification Recipient via the specified Delivery Method (i.e., Notification Recipient via the specified Delivery Method (i.e.,
protocol). protocol).
The "IPP Event Notifications and Subscriptions" document [ipp-ntfy] The "IPP Event Notifications and Subscriptions" document [ipp-ntfy]
specifies that each Delivery Method is defined in another document. specifies that each Delivery Method is defined in another document.
This document is one such document, and it specifies the 'ippget' This document is one such document, and it specifies the 'ippget'
delivery method. When IPP Notification [ipp-ntfy] is supported, the delivery method. If a client or Printer supports IPP Notification
Delivery Method defined in this document is one of the RECOMMENDED [ipp-ntfy], the client or Printer MUST support the 'ippget' Delivery
Delivery Methods for Printers to support. Method defined in this document. Such a client or Printer MAY
support additional Delivery Methods.
The 'ippget' Delivery Method is a Pull Delivery Method. When an The 'ippget' Delivery Method is a Pull Delivery Method. When an
Event occurs, the Printer saves the Event Notification for a period Event occurs, the Printer saves the Event Notification for a period
of time called the Event Life. The Notification Recipient fetches of time called the Event Life. The Notification Recipient fetches
(pulls) the Event Notifications using the Get-Notifications (pulls) the Event Notifications using the Get-Notifications
operation. This operation causes the Printer to return all Event operation. This operation causes the Printer to return all Event
Notifications held for the specified Subscription object(s). If the Notifications held for the specified Subscription object(s). If the
Notification Recipient has selected the Event Wait Mode option to Notification Recipient has selected the Event Wait Mode option to
wait for additional Event Notifications, the Printer continues to wait for additional Event Notifications, the Printer continues to
return Event Notifications to the Notification Recipient as Get- return Event Notifications to the Notification Recipient as Get-
skipping to change at page 6, line 5 skipping to change at page 6, line 5
The Notification Recipient can terminate Event Wait Mode (without The Notification Recipient can terminate Event Wait Mode (without
closing the connection) by supplying the "notify-wait" (boolean) closing the connection) by supplying the "notify-wait" (boolean)
attribute with a 'false' value in a subsequent Get-Notifications attribute with a 'false' value in a subsequent Get-Notifications
request. Similarly, the Printer can terminate Event Wait Mode request. Similarly, the Printer can terminate Event Wait Mode
(without closing the connection) by returning the "notify-get- (without closing the connection) by returning the "notify-get-
interval" (integer) operation attribute in a Get-Notifications interval" (integer) operation attribute in a Get-Notifications
response which tells the Notification Recipient how long to wait response which tells the Notification Recipient how long to wait
before trying again. before trying again.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
2 Terminology 2 Terminology
This section defines the following terms that are used throughout This section defines the following terms that are used throughout
this document: this document:
This document uses the same terminology as [RFC2911], such as This document uses the same terminology as [RFC2911], such as
"client", "Printer", "Job", "attribute", "attribute value", "client", "Printer", "Job", "attribute", "attribute value",
"keyword", "operation", "request", "response", and "support". "keyword", "operation", "request", "response", and "support".
Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD
skipping to change at page 7, line 5 skipping to change at page 6, line 52
terms are reproduced here: terms are reproduced here:
Event - some occurrence (either expected or unexpected) within the Event - some occurrence (either expected or unexpected) within the
printing system of a change of state, condition, or printing system of a change of state, condition, or
configuration of a Job or Printer object. An Event occurs only configuration of a Job or Printer object. An Event occurs only
at one instant in time and does not span the time the physical at one instant in time and does not span the time the physical
Event takes place. For example, jam-occurred and jam-cleared Event takes place. For example, jam-occurred and jam-cleared
are two distinct, instantaneous Events, even though the jam may are two distinct, instantaneous Events, even though the jam may
last for a while. last for a while.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Event Notification - the information about an Event that the Printer Event Notification - the information about an Event that the Printer
sends when an Event occurs. sends when an Event occurs.
3 Model and Operation 3 Model and Operation
In a Subscription Creation Operation, when the "notify-pull-method" In a Subscription Creation Operation, when the "notify-pull-method"
attribute is present and has the 'ippget' keyword value, the client attribute is present and has the 'ippget' keyword value, the client
is requesting that the Printer use the 'ippget' Pull Delivery Method is requesting that the Printer use the 'ippget' Pull Delivery Method
for the Event Notifications associated with the new Subscription for the Event Notifications associated with the new Subscription
Object. Object.
skipping to change at page 7, line 46 skipping to change at page 7, line 41
performing the Subscription Creation operation. Because the Printer performing the Subscription Creation operation. Because the Printer
MUST save Event Notifications for at least 15 seconds (see section MUST save Event Notifications for at least 15 seconds (see section
8.1), the Notification Recipient is unlikely to miss any Event 8.1), the Notification Recipient is unlikely to miss any Event
Notifications that occur between the Subscription Creation and the Notifications that occur between the Subscription Creation and the
Get-Notifications operation. Get-Notifications operation.
The 'ippget' Delivery Method is designed primarily for (1) a client The 'ippget' Delivery Method is designed primarily for (1) a client
that wants to get Events (from the job's per-Job Subscription object) that wants to get Events (from the job's per-Job Subscription object)
for a job that it has submitted and (2) for a privileged client that for a job that it has submitted and (2) for a privileged client that
wants to get all job or printer Events from a per-Printer wants to get all job or printer Events from a per-Printer
Subscription object. If several groups of users expect to receive Subscription object.
jobs from other users (FAX paradigm) and each group has a different
designated person, say, a secretary, to receive job completion
Events, the Printer should be configured to support multiple URLs,
one for each group. Then the designated (privileged) person can run
an application that gets the events for jobs submitted to that URL
from the per-Printer Subscription object that the application
creates.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
4 General Information 4 General Information
If a Printer supports this Delivery Method, the following are its If a Printer supports this Delivery Method, the following are its
characteristics. characteristics.
Table 1 - Information about the Delivery Method Table 1 - Information about the Delivery Method
Document Method Conformance Requirement Delivery Method Document Method Conformance Requirement Delivery Method
Realization Realization
1. What is the URL scheme name for the 1. What is the URL scheme name for the
Push Delivery Method or the keyword Push Delivery Method or the keyword name
method name for the Pull Delivery method name for the Pull Delivery
Method? ippget Method? 'ippget' keyword method
2. Is the Delivery Method REQUIRED, 2. Is the Delivery Method REQUIRED, REQUIRED
RECOMMENDED or OPTIONAL for an IPP RECOMMENDED or OPTIONAL for an IPP
Printer to support? RECOMMENDED Printer to support?
3. What transport and delivery protocols IPP with one new 3. What transport and delivery protocols IPP with one new
does the Printer use to deliver the operation. does the Printer use to deliver the operation.
Event Notification Content, i.e., what Event Notification Content, i.e., what
is the entire network stack? is the entire network stack?
4. Can several Event Notifications be Yes. 4. Can several Event Notifications be
combined into a Compound Event combined into a Compound Event
Notification? Notification? Yes.
5. Is the Delivery Method initiated by This Delivery Method is 5. Is the Delivery Method initiated by This Delivery Method is
the Notification Recipient (pull), or a pull method with the Notification Recipient (pull), or a pull method with
by the Printer (push)? aspects of a push by the Printer (push)? aspects of a push
method, though the method, though the
Printer does not Printer does not
initiate the connection. initiate the connection.
6. Is the Event Notification content Machine Consumable 6. Is the Event Notification content Machine Consumable
Machine Consumable or Human Machine Consumable or Human
Consumable? Consumable?
7. What section in this document answers Section 5 7. What section in this document answers Section 5
the following question? For a Machine the following question? For a Machine
Consumable Event Notification, what is Consumable Event Notification, what is
the representation and encoding of the representation and encoding of
values defined in section 9.1 of [ipp- values defined in section 9.1 of [ipp-
ntfy] and the conformance requirements ntfy] and the conformance requirements
thereof? For a Human Consumable Event
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
ntfy] and the conformance requirements
thereof? For a Human Consumable Event thereof? For a Human Consumable Event
Notification, what is the Notification, what is the
representation and encoding of pieces representation and encoding of pieces
of information defined in section 9.2 of information defined in section 9.2
of [ipp-ntfy] and the conformance of [ipp-ntfy] and the conformance
requirements thereof? requirements thereof?
8. What are the latency and reliability Same as IPP and the 8. What are the latency and reliability Same as IPP and the
of the transport and delivery underlying HTTP of the transport and delivery underlying HTTP
protocol? transport protocol? transport
9. What are the security aspects of the Same as IPP and the 9. What are the security aspects of the
transport and delivery protocol, e.g., underlying HTTP transport and delivery protocol, e.g., underlying HTTP
how it is handled in firewalls? transport and in the how it is handled in firewalls? transportPandnintthe
same direction, so no same direction, so no
new firewall new firewall
considerations. considerations.
10.What are the content length None 10.What are the content length None
restrictions? restrictions?
11.What are the additional values or None 11.What are the additional values or
pieces of information that a Printer pieces of information that a Printer
sends in an Event Notification content sends in an Event Notification content
and the conformance requirements and the conformance requirements
thereof? thereof? None
12.What are the additional Subscription None 12.What are the additional Subscription None
Template and/or Subscription Template and/or Subscription
Description attributes and the Description attributes and the
conformance requirements thereof? conformance requirements thereof?
13.What are the additional Printer "ipp-event-life" 13.What are the additional Printer "ipp-event-life"
Description attributes and the (integer (15: MAX)) Description attributes and the (integer (15: MAX))
conformance requirements thereof? conformance requirements thereof?
5 Get-Notifications operation 5 Get-Notifications operation
This operation is issued by a client acting in the role of a This operation is issued by a client acting in the role of a
Notification Recipient requesting the Printer to return all Event Notification Recipient requesting the Printer to return all Event
Notifications held for the identified Subscription object(s). Notifications held for the identified Subscription object(s).
A Printer MUST support this operation. A Printer MUST support this operation.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
When a Printer performs this operation, it MUST return all and only When a Printer performs this operation, it MUST return all and only
those Event Notifications: those Event Notifications:
1. Whose associated Subscription Object's "notify-subscription-id" 1. Whose associated Subscription Object's "notify-subscription-id"
Subscription Description attribute equals one of the values of Subscription Description attribute equals one of the values of
the "notify-subscription-ids" (1setOf integer(1:MAX)) operation the "notify-subscription-ids" (1setOf integer(1:MAX)) operation
attribute AND attribute AND
2. Whose associated Subscription Object's contains the "notify- 2. Whose associated Subscription Object's contains the "notify-
pull-method" attribute and it has the 'ippget' keyword value AND pull-method" attribute and it has the 'ippget' keyword value AND
3. Whose "notify-sequence-number" is equal to or greater than the 3. Whose "notify-sequence-number" is equal to or greater than the
corresponding value of the "notify-sequence-numbers (1setOf corresponding value of the "notify-sequence-numbers (1setOf
integer(1:MAX)) operation attribute, if supplied AND integer(1:MAX)) operation attribute, if supplied AND
4. Whose Event Life has not yet expired AND 4. Whose Event Life has not yet expired AND
5. Where the Notification Recipient is the owner of or has read- 5. Where the Notification Recipient client has read-access rights
access rights to the identified Subscription Object. to the identified Subscription Object (see Access Rights
paragraph below).
The Notification Recipient client can request Event Wait Mode by The Notification Recipient client can request Event Wait Mode by
supplying the "notify-wait" operation attribute with a 'true' value. supplying the "notify-wait" operation attribute with a 'true' value.
The Notification Recipient client can terminate Event Wait Mode The Notification Recipient client can terminate Event Wait Mode
(without closing the connection) by supplying the "notify-wait" (without closing the connection) by supplying the "notify-wait"
attribute with a 'false' value in a subsequent Get-Notifications attribute with a 'false' value in a subsequent Get-Notifications
request. Similarly, the Printer can terminate Event Wait Mode request. Similarly, the Printer can terminate Event Wait Mode
(without closing the connection) by returning the "notify-get- (without closing the connection) by returning the "notify-get-
interval" operation attribute in a Get-Notifications response which interval" operation attribute in a Get-Notifications response which
tells the Notification Recipient how long to wait before trying tells the Notification Recipient how long to wait before trying
again. again.
The Printer MUST accept the request in any state (see [RFC2911] The Printer MUST accept the request in any state (see [RFC2911]
"printer-state" and "printer-state-reasons" attributes) and MUST "printer-state" and "printer-state-reasons" attributes) and MUST
remain in the same state with the same "printer-state-reasons" remain in the same state with the same "printer-state-reasons"
values. values.
Access Rights: If the policy of the Printer is to allow all users to Access Rights: The authenticated user (see [RFC2911] section 8.3)
access all Event Notifications, then the Printer MUST accept this performing this operation MUST be (1) the owner of each Subscription
operation from any user. Otherwise, the authenticated user (see Object identified by the "notify-subscription-ids" operation
[RFC2911] section 8.3) performing this operation MUST be the owner of attribute (see section 5.1.1), (2) an operator or administrator of
each Subscription Object identified by the "notify-subscription-ids" the Printer (see [RFC2911] Sections 1 and 8.5), or (3) be otherwise
operation attribute (as returned during a Subscription Creation authorized by the Printer's administrator-configured security policy
Operation) or an operator or administrator of the Printer (see to request Event Notifications from the target Subscription
[RFC2911] Sections 1 and 8.5). Otherwise, the IPP object MUST reject Object(s). Otherwise, the IPP Printer MUST reject the operation and
the operation and return: 'client-error-forbidden', 'client-error- return: 'client-error-forbidden', 'client-error-not-authenticated',
not-authenticated', or 'client-error-not-authorized' status code as or 'client-error-not-authorized' status code as appropriate.
appropriate. Furthermore, the Printer's security policy MAY limit the attributes
returned by the Get-Notifications operation, in a manner similar to
INTERNET-DRAFT IPP: The 'ippget' Delivery Method the Get-Job-Attributes operation (see [RFC2911] end of section
3.3.4.2).
5.1 Get-Notifications Request 5.1 Get-Notifications Request
The following groups of attributes are part of the Get-Notifications The following groups of attributes are part of the Get-Notifications
Request: Request:
Group 1: Operation Attributes Group 1: Operation Attributes
Natural Language and Character Set: Natural Language and Character Set:
The "attributes-charset" and "attributes-natural-language" The "attributes-charset" and "attributes-natural-language"
skipping to change at page 12, line 4 skipping to change at page 12, line 7
valued. valued.
5.1.2 notify-sequence-numbers (1setOf integer(1:MAX)) 5.1.2 notify-sequence-numbers (1setOf integer(1:MAX))
This attribute specifies one or more lowest Event Notification This attribute specifies one or more lowest Event Notification
sequence number values for the Subscription objects identified sequence number values for the Subscription objects identified
by the corresponding values of the "notify-subscription-ids" by the corresponding values of the "notify-subscription-ids"
operation attribute. The Notification Recipient SHOULD supply operation attribute. The Notification Recipient SHOULD supply
this attribute and the number of values SHOULD be the same as this attribute and the number of values SHOULD be the same as
the number of values of the "notify-subscriptions-ids" the number of values of the "notify-subscriptions-ids"
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
attribute. The Printer MUST support this attribute with attribute. The Printer MUST support this attribute with
multiple values. multiple values.
The Printer MUST NOT return Notification Events with lower The Printer MUST NOT return Notification Events with lower
sequence numbers for the corresponding Subscription object. sequence numbers for the corresponding Subscription object.
Therefore, by supplying the proper values for this attribute Therefore, by supplying the proper values for this attribute
the Notification Recipient can prevent getting the same Event the Notification Recipient can prevent getting the same Event
Notifications from a Subscription object that were returned on Notifications from a Subscription object that were returned on
a previous Get-Notifications request. The Notification a previous Get-Notifications request. The Notification
Recipient SHOULD remember the highest "notify-sequence-number" Recipient SHOULD remember the highest "notify-sequence-number"
skipping to change at page 13, line 4 skipping to change at page 13, line 8
5.1.3 notify-wait (boolean) 5.1.3 notify-wait (boolean)
This value indicates whether or not the Notification Recipient This value indicates whether or not the Notification Recipient
wants Event Wait Mode. The client MAY supply this attribute. wants Event Wait Mode. The client MAY supply this attribute.
The Printer object MUST support both values of this attribute. The Printer object MUST support both values of this attribute.
If the client supplies the 'false' value or omits this If the client supplies the 'false' value or omits this
attribute, the client is not requesting Event Wait Mode. If attribute, the client is not requesting Event Wait Mode. If
the value is 'true', the client is requesting Event Wait Mode. the value is 'true', the client is requesting Event Wait Mode.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
See the beginning of section 5.2 for the rules for Event Wait See the beginning of section 5.2 for the rules for Event Wait
Mode. Mode.
5.2 Get-Notifications Response 5.2 Get-Notifications Response
The Printer has the following options for responding to a Get- The Printer has the following options for responding to a Get-
Notifications Request: Notifications Request:
1. The Printer can reject the request and return the 'server-error- 1. The Printer can reject the request and return the 'server-error-
busy' status code, if the Printer is too busy to accept this busy' status code, if the Printer is too busy to accept this
skipping to change at page 14, line 4 skipping to change at page 14, line 8
attribute. This attribute indicates that the Printer wishes to attribute. This attribute indicates that the Printer wishes to
leave Event Wait Mode and the number of seconds in the future leave Event Wait Mode and the number of seconds in the future
that the Notification Recipient SHOULD try the Get-Notifications that the Notification Recipient SHOULD try the Get-Notifications
operation again. The Notification Recipient MUST accept this operation again. The Notification Recipient MUST accept this
response and MUST disconnect. If the Notification Recipient response and MUST disconnect. If the Notification Recipient
does not disconnect, the Printer SHOULD do so. does not disconnect, the Printer SHOULD do so.
From the Notification Recipient's view, the response appears as an From the Notification Recipient's view, the response appears as an
initial burst of data, which includes the Operation Attributes Group initial burst of data, which includes the Operation Attributes Group
and one Event Notification Attributes Group per Event Notification and one Event Notification Attributes Group per Event Notification
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
that the Printer is holding. After the initial burst of data, if the that the Printer is holding. After the initial burst of data, if the
Notification Recipient has selected the Event Wait Mode option to Notification Recipient has selected the Event Wait Mode option to
wait for additional Event Notifications, the Notification Recipient wait for additional Event Notifications, the Notification Recipient
receives occasional Event Notification Attribute Groups. Proxy receives occasional Event Notification Attribute Groups. Proxy
servers may delay some Event Notifications or cause time-outs to servers may delay some Event Notifications or cause time-outs to
occur. The client MUST be prepared to perform the Get-Notifications occur. The client MUST be prepared to perform the Get-Notifications
operation again when time-outs occur. operation again when time-outs occur.
Each attribute is encoded using the IPP rules for encoding attributes Each attribute is encoded using the IPP rules for encoding attributes
[RFC2910] and MAY be encoded in any order. Note: the Get-Jobs [RFC2910] and MAY be encoded in any order. Note: the Get-Jobs
skipping to change at page 15, line 4 skipping to change at page 15, line 5
is the last return for all Subscription objects that is the last return for all Subscription objects that
match the request, whether or not there are Event match the request, whether or not there are Event
Notifications being returned. This condition occurs for Notifications being returned. This condition occurs for
Event Wait Mode with Notification Recipients waiting for Event Wait Mode with Notification Recipients waiting for
responses when the Subscription Object is: (1) canceled responses when the Subscription Object is: (1) canceled
with a Cancel-Subscription operation, (2) deleted when with a Cancel-Subscription operation, (2) deleted when
the Per-Printer Subscription lease time expires, or (3) the Per-Printer Subscription lease time expires, or (3)
when the 'job-completed' event occurs for a Per-Job when the 'job-completed' event occurs for a Per-Job
Subscription. This condition also occurs for a Get- Subscription. This condition also occurs for a Get-
Notifications request that a Notification Recipient makes Notifications request that a Notification Recipient makes
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
after the job completes, but before the Event Life after the job completes, but before the Event Life
expires. See section 10.1. expires. See section 10.1.
client-error-not-found: The Printer has no Subscription client-error-not-found: The Printer has no Subscription
Object's whose "notify-subscription-id" attribute equals Object's whose "notify-subscription-id" attribute equals
any of the values of the "notify-subscription-ids" any of the values of the "notify-subscription-ids"
operation attribute supplied or the identified operation attribute supplied or the identified
Subscription Object does not contain the "notify-pull- Subscription Object does not contain the "notify-pull-
method" attribute with the 'ippget' keyword value. method" attribute with the 'ippget' keyword value.
server-error-busy: The Printer is too busy to accept this server-error-busy: The Printer is too busy to accept this
operation. The Printer SHOULD return the "notify-get- operation. The Printer SHOULD return the "notify-get-
skipping to change at page 15, line 42 skipping to change at page 15, line 40
The "attributes-charset" and "attributes-natural-language" The "attributes-charset" and "attributes-natural-language"
attributes as described in [RFC2911] section 3.1.4.2. attributes as described in [RFC2911] section 3.1.4.2.
The Printer MUST use the values of "notify-charset" and The Printer MUST use the values of "notify-charset" and
"notify-natural-language", respectively, from one Subscription "notify-natural-language", respectively, from one Subscription
Object associated with the Event Notifications in this Object associated with the Event Notifications in this
response. response.
Normally, there is only one matched Subscription Object, or the Normally, there is only one matched Subscription Object, or the
value of the "notify-charset" and "notify-natural-language" value of the "notify-charset" and "notify-natural-language"
attributes is the same in all Subscription Objects. If not, the attributes is the same in all Subscription Objects. If not,
Printer MUST pick one Subscription Object from which to obtain the Printer MUST pick one Subscription Object from which to
the value of these attributes. The algorithm for picking the obtain the value of these attributes. The algorithm for
Subscription Object is implementation dependent. The choice of picking the Subscription Object is implementation dependent.
natural language is not critical because 'text' and 'name' The choice of natural language is not critical because 'text'
values can override the "attributes-natural-language" operation and 'name' values can override the "attributes-natural-
attribute. The Printer's choice of charset is critical because language" operation attribute. The Printer's choice of charset
a bad choice may leave it unable to send some 'text' and 'name' is critical because a bad choice may leave it unable to send
values accurately. some 'text' and 'name' values accurately.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
5.2.1 notify-get-interval (integer(0:MAX)) 5.2.1 notify-get-interval (integer(0:MAX))
The value of this operation attribute is the number of seconds The value of this operation attribute is the number of seconds
that the Notification Recipient SHOULD wait before trying the that the Notification Recipient SHOULD wait before trying the
Get-Notifications operation again. The Printer MUST return Get-Notifications operation again. The Printer MUST return
this operation attribute if: (1) it is too busy to return this operation attribute if: (1) it is too busy to return
events, (2) the Notification Recipient client did not request events, (2) the Notification Recipient client did not request
Event Wait Mode, or (3) the Printer is terminating Event Wait Event Wait Mode, or (3) the Printer is terminating Event Wait
Mode. The client MUST accept this attribute and SHOULD re- Mode. The client MUST accept this attribute and SHOULD re-
skipping to change at page 17, line 5 skipping to change at page 17, line 5
If the Printer wants to remain in Event Wait Mode, then the If the Printer wants to remain in Event Wait Mode, then the
Printer MUST NOT return this attribute in the response. Printer MUST NOT return this attribute in the response.
Here is a complete table of combinations of "notify-wait", Here is a complete table of combinations of "notify-wait",
"status-code", "notify-get-interval", and Event Notification "status-code", "notify-get-interval", and Event Notification
Attributes Groups for Get-Notification initial (Wait and No Attributes Groups for Get-Notification initial (Wait and No
Wait) Responses and subsequent Event Wait Mode Responses (which Wait) Responses and subsequent Event Wait Mode Responses (which
may be staying in Event Wait Mode or may be requesting the may be staying in Event Wait Mode or may be requesting the
Notification Recipient to leave Event Wait Mode): Notification Recipient to leave Event Wait Mode):
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Table 2 - Combinations of "notify-wait", "status-code", and "notify- Table 2 - Combinations of "notify-wait", "status-code", and "notify-
get-interval" get-interval"
client sends: Printer returns: Printer Event client sends: Printer returns: Printer Event
returns: Notification returns: Notification
"notify-wait" "status-code" "notify-get- Attribute "notify-wait" "status-code" "notify-get- Attribute
interval" Groups interval" Groups
1. 'false'* 'successful-ok' MUST return N maybe 1. 'false'* 'successful-ok' MUST return N maybe
2. 'false'* 'not-found' MUST NOT MUST NOT 2. 'false'* 'not-found' MUST NOT MUST NOT
3. 'false'* 'busy' MUST return N MUST NOT 3. 'false'* 'busy' MUST return N MUST NOT
4. 'false'* 'events- 'job- 4. 'false'* 'events- MUST NOT 'job-
complete' MUST NOT completed' complete' completed'
5. 'true' 'successful-ok' MUST NOT MUST 5. 'true' 'successful-ok' MUST NOT MUST
6. 'true' 'successful-ok' MUST return N maybe 6. 'true' 'successful-ok' MUST return N maybe
7. 'true' 'not-found' MUST NOT MUST NOT 7. 'true' 'not-found' MUST NOT MUST NOT
8. 'true' 'busy' MUST return N MUST NOT 8. 'true' 'busy' MUST return N MUST NOT
9. 'true' 'events- MUST NOT 'job- 9. 'true' 'events- MUST NOT 'job-
skipping to change at page 18, line 5 skipping to change at page 18, line 5
3,8: server busy, tells client to try later; client should try 3,8: server busy, tells client to try later; client should try
again in N seconds. again in N seconds.
4: client polled after job completed, but before Event Life 4: client polled after job completed, but before Event Life
expired, and got the 'job-completed' event, so the client expired, and got the 'job-completed' event, so the client
shouldn't bother trying again; client should NOT try again shouldn't bother trying again; client should NOT try again
later. later.
5: Printer returns one or more Event Notifications and is OK 5: Printer returns one or more Event Notifications and is OK
to stay in Event Wait Mode; the client waits for more Event to stay in Event Wait Mode; the client waits for more Event
Notifications to be returned. Notifications to be returned.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
6: Printer wants to leave Event Wait mode. Can happen on the 6: Printer wants to leave Event Wait mode. Can happen on the
first response (with or without Event Notifications) or happen first response (with or without Event Notifications) or happen
on a subsequent response with or without Event Notifications; on a subsequent response with or without Event Notifications;
the client SHOULD try again in N seconds. the client SHOULD try again in N seconds.
9: Printer either (1) returns 'job-completed' event or (2) the 9: Printer either (1) returns 'job-completed' event or (2) the
Subscription Object was canceled by either a Cancel-Job or a Subscription Object was canceled by either a Cancel-Job or a
Per-Printer Subscription expired without being renewed. For Per-Printer Subscription expired without being renewed. For
case (1), at least one Event Notification MUST be returned, case (1), at least one Event Notification MUST be returned,
while for case (2), it is unlikely that any Event Notifications while for case (2), it is unlikely that any Event Notifications
are returned; the client should NOT try again. are returned; the client should NOT try again.
skipping to change at page 19, line 4 skipping to change at page 18, line 48
Unsupported Attributes. Unsupported Attributes.
Group 3 through N: Event Notification Attributes Group 3 through N: Event Notification Attributes
The Printer responds with one Event Notification Attributes The Printer responds with one Event Notification Attributes
Group per matched Event Notification. The entire response is Group per matched Event Notification. The entire response is
considered a single Compound Event Notification (see [ipp- considered a single Compound Event Notification (see [ipp-
ntfy]). The matched Event Notifications are all un-expired ntfy]). The matched Event Notifications are all un-expired
Event Notification associated with the matched Subscription Event Notification associated with the matched Subscription
Objects and MUST follow the "Event Notification Ordering" Objects and MUST follow the "Event Notification Ordering"
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
requirements for Event Notifications within a Compound Event requirements for Event Notifications within a Compound Event
Notification specified in [ipp-ntfy] section 9. In other Notification specified in [ipp-ntfy] section 9. In other
words, the Printer MUST order these Event Notification groups words, the Printer MUST order these Event Notification groups
in ascending time stamp (and sequence number) order for a in ascending time stamp (and sequence number) order for a
Subscription object. If Event Notifications for multiple Subscription object. If Event Notifications for multiple
Subscription objects are being returned, the Notification Subscription objects are being returned, the Notification
Events for the next Subscription object follow in ascending Events for the next Subscription object follow in ascending
time stamp order, etc. time stamp order, etc.
Each Event Notification Group MUST contain all of attributes Each Event Notification Group MUST contain all of attributes
skipping to change at page 20, line 5 skipping to change at page 20, line 5
ntfy] except that each cell in the "Sends" column is a "MUST". ntfy] except that each cell in the "Sends" column is a "MUST".
If more than one Event Notification is being returned and the If more than one Event Notification is being returned and the
status of each is not the same, then the Printer MUST return a status of each is not the same, then the Printer MUST return a
"notify-status-code" attribute in each Event Notification "notify-status-code" attribute in each Event Notification
Attributes group to indicate the differing status values. Attributes group to indicate the differing status values.
For an Event Notification for all Events, the Printer includes For an Event Notification for all Events, the Printer includes
the attributes shown in Table 3. the attributes shown in Table 3.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Table 3 - Attributes in Event Notification Content Table 3 - Attributes in Event Notification Content
Source Value Sends Source Source Value Sends Source
Object Object
notify-subscription-id (integer(1:MAX)) MUST Subscription notify-subscription-id (integer(1:MAX)) MUST Subscription
notify-printer-uri (uri) MUST Subscription notify-printer-uri (uri) MUST Subscription
notify-subscribed-event (type2 keyword) MUST Event notify-subscribed-event (type2 keyword) MUST Event
skipping to change at page 21, line 5 skipping to change at page 21, line 5
* As specified in [ipp-ntfy] section 9, the value of the * As specified in [ipp-ntfy] section 9, the value of the
"printer-up-time" attribute sent in each Event Notification "printer-up-time" attribute sent in each Event Notification
MUST be the time at which the Event occurred, not the time at MUST be the time at which the Event occurred, not the time at
which the Event Notification was sent. which the Event Notification was sent.
** The Printer MUST send the "printer-current-time" attribute ** The Printer MUST send the "printer-current-time" attribute
if and only if it supports the "printer-current-time" attribute if and only if it supports the "printer-current-time" attribute
on the Printer object. on the Printer object.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
*** If the associated Subscription Object does not contain a *** If the associated Subscription Object does not contain a
"notify-user-data" attribute, the Printer MUST send an octet- "notify-user-data" attribute, the Printer MUST send an octet-
string of length 0. string of length 0.
**** If the "notify-attributes" attribute is present on the **** If the "notify-attributes" attribute is present on the
Subscription Object, the Printer MUST send all attributes Subscription Object, the Printer MUST send all attributes
specified by the "notify-attributes" attribute. Note: if the specified by the "notify-attributes" attribute. Note: if the
Printer doesn't support the "notify-attributes" attribute, it Printer doesn't support the "notify-attributes" attribute, it
is not present on the associated Subscription Object. is not present on the associated Subscription Object.
skipping to change at page 22, line 5 skipping to change at page 21, line 36
job-state (type1 enum) MUST Job job-state (type1 enum) MUST Job
job-state-reasons (1setOf type2 keyword) MUST Job job-state-reasons (1setOf type2 keyword) MUST Job
job-impressions-completed (integer(0:MAX)) MUST * Job job-impressions-completed (integer(0:MAX)) MUST * Job
* The Printer MUST send the "job-impressions-completed" * The Printer MUST send the "job-impressions-completed"
attribute in an Event Notification only for the combinations of attribute in an Event Notification only for the combinations of
Events and Subscribed Events shown in Table 5. Events and Subscribed Events shown in Table 5.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Table 5 - Combinations of Events and Subscribed Events for "job- Table 5 - Combinations of Events and Subscribed Events for "job-
impressions-completed" impressions-completed"
Job Event Subscribed Job Event Job Event Subscribed Job Event
'job-progress' 'job-progress' 'job-progress' 'job-progress'
'job-completed' 'job-completed' 'job-completed' 'job-completed'
'job-completed' 'job-state-changed' 'job-completed' 'job-state-changed'
skipping to change at page 23, line 4 skipping to change at page 22, line 33
the same conformance requirements for Subscription Template the same conformance requirements for Subscription Template
attributes as defined in [ipp-ntfy]. This section defines additional attributes as defined in [ipp-ntfy]. This section defines additional
information about Subscription Template attributes defined in [ipp- information about Subscription Template attributes defined in [ipp-
ntfy]. ntfy].
6.1 notify-pull-method (type2 keyword) 6.1 notify-pull-method (type2 keyword)
This Subscription Template attribute identifies the Pull Delivery This Subscription Template attribute identifies the Pull Delivery
Method to be used for the Subscription Object (see [ipp-ntfy]). In Method to be used for the Subscription Object (see [ipp-ntfy]). In
order to support the 'ippget' Pull Delivery Method defined in this order to support the 'ippget' Pull Delivery Method defined in this
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
document, the Printer MUST support this attribute with the following document, the Printer MUST support this attribute with the following
keyword value: keyword value:
'ippget': indicates that the IPPGET Pull Delivery Method is to be 'ippget': indicates that the IPPGET Pull Delivery Method is to be
used for this Subscription Object. used for this Subscription Object.
7 Subscription Description Attributes 7 Subscription Description Attributes
The 'ippget' Delivery Method has the same conformance requirements The 'ippget' Delivery Method has the same conformance requirements
for Subscription Description attributes as defined in [ipp-ntfy]. for Subscription Description attributes as defined in [ipp-ntfy].
skipping to change at page 24, line 5 skipping to change at page 23, line 38
Subscription Object associated with the 'ippget' Delivery Subscription Object associated with the 'ippget' Delivery
Method, AND Method, AND
2.an Event associated with the new Job occurs immediately after 2.an Event associated with the new Job occurs immediately after
the Subscription Object is created, AND the Subscription Object is created, AND
3.the same client or some other client performs a Get- 3.the same client or some other client performs a Get-
Notifications operation such that the client is connected N Notifications operation such that the client is connected N
seconds after the Job Creation operation. seconds after the Job Creation operation.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Then, if N is less than the value of this attribute, the client(s) Then, if N is less than the value of this attribute, the client(s)
performing the Get-Notifications operations can expect not to miss performing the Get-Notifications operations can expect not to miss
any Event-Notifications, barring some unforeseen lack of memory space any Event-Notifications, barring some unforeseen lack of memory space
in the Printer. Note: The client MUST initiate the Get- in the Printer. Note: The client MUST initiate the Get-
Notifications a time that is sufficiently less that N seconds to Notifications a time that is sufficiently less that N seconds to
account for network latency so that it is connected to the Printer account for network latency so that it is connected to the Printer
before N seconds elapses. before N seconds elapses.
If a Printer supports the 'ippget' Delivery Method, it MUST keep If a Printer supports the 'ippget' Delivery Method, it MUST keep
'completed', 'canceled', or 'aborted' Job objects in the Job 'completed', 'canceled', or 'aborted' Job objects in the Job
skipping to change at page 25, line 5 skipping to change at page 24, line 32
defined in this document: defined in this document:
'ippget' - The IPP Notification Pull Delivery Method defined in 'ippget' - The IPP Notification Pull Delivery Method defined in
this document. this document.
9.2 operations-supported (1setOf type2 enum) 9.2 operations-supported (1setOf type2 enum)
Table 7 lists the "operation-id" value defined in order to support Table 7 lists the "operation-id" value defined in order to support
the new Get-Notifications operation defined in this document. the new Get-Notifications operation defined in this document.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Table 7 - Operation-id assignments Table 7 - Operation-id assignments
Value Operation Name Value Operation Name
0x001C Get-Notifications 0x001C Get-Notifications
10 New Status Codes 10 New Status Codes
The following status codes are defined as extensions for this The following status codes are defined as extensions for this
Delivery Method and are returned as the status code of the Get- Delivery Method and are returned as the status code of the Get-
skipping to change at page 25, line 37 skipping to change at page 25, line 23
operation, (2) deleted when the Per-Printer Subscription lease time operation, (2) deleted when the Per-Printer Subscription lease time
expires, or (3) when the 'job-completed' event occurs for a Per-Job expires, or (3) when the 'job-completed' event occurs for a Per-Job
Subscription. This condition also occurs for a Get-Notifications Subscription. This condition also occurs for a Get-Notifications
request that a Notification Recipient makes after the job completes, request that a Notification Recipient makes after the job completes,
but before the Event Life expires. but before the Event Life expires.
10.2 redirection-other-site (0x0300) 10.2 redirection-other-site (0x0300)
This status code means that the Printer doesn't perform that Get- This status code means that the Printer doesn't perform that Get-
Notifications operation and that the "redirect-uri" operation Notifications operation and that the "redirect-uri" operation
attribute in the response contains the uri that the Notification attribute (see section 5.2.3) in the response contains the uri that
Recipient MUST use for performing the Get-Notifications operation. the Notification Recipient MUST use for performing the Get-
If the client issues subsequent Get-Notifications operations, it MUST Notifications operation. If the client issues subsequent Get-
use the value of the "redirect-uri" operation attribute returned by Notifications operations, it MUST use the value of the "redirect-uri"
the Printer as the target of the operation. operation attribute returned by the Printer as the target of the
operation.
11 Encoding and Transport 11 Encoding and Transport
This section defines the encoding and transport considerations for This section defines the encoding and transport considerations for
this Delivery Method based on [RFC2910]. this Delivery Method based on [RFC2910].
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
The encoding of a Get-Notifications Response is modeled the Get-Jobs The encoding of a Get-Notifications Response is modeled the Get-Jobs
Response (see [RFC2911]). In a Get-Notifications Response, each Response (see [RFC2911]). In a Get-Notifications Response, each
Event Notification Attributes Group MUST start with an 'event- Event Notification Attributes Group MUST start with an 'event-
notification-attributes-tag' (see the section "Encodings of notification-attributes-tag' (see the section "Encodings of
Additional Attribute Tags" in [ipp-ntfy]), and end with an 'end-of- Additional Attribute Tags" in [ipp-ntfy]), and end with an 'end-of-
attributes-tag'. In addition, for Event Wait Mode the multi- attributes-tag'. In addition, for Event Wait Mode the multi-
part/related is used to separate each multiple response (in time) to part/related is used to separate each multiple response (in time) to
a single Get-Notifications Request. a single Get-Notifications Request.
The Printer returns Get-Notification Response as follows: The Printer returns Get-Notification Response as follows:
skipping to change at page 27, line 4 skipping to change at page 26, line 36
later wishes to leave Event Wait Mode, the Printer MUST return later wishes to leave Event Wait Mode, the Printer MUST return
the "notify-get-interval" operation attribute (see section the "notify-get-interval" operation attribute (see section
5.2.1). The Printer returns the response as an application/ipp 5.2.1). The Printer returns the response as an application/ipp
part which MUST be inside an multi-part/related type. part which MUST be inside an multi-part/related type.
Note: All of the above is without either the Printer or the Note: All of the above is without either the Printer or the
Notification Recipient closing the connection. In fact, the Notification Recipient closing the connection. In fact, the
connection SHOULD remain open for any subsequent IPP operations. connection SHOULD remain open for any subsequent IPP operations.
However, either the Notification Recipient or the Printer can However, either the Notification Recipient or the Printer can
abnormally terminate by closing the connection. But, if the Printer abnormally terminate by closing the connection. But, if the Printer
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
closes the connection too soon after returning the response, the closes the connection too soon after returning the response, the
client may not receive the response. client may not receive the response.
The Printer MAY chunk the responses, but this has no significance to The Printer MAY chunk the responses, but this has no significance to
the IPP semantics. the IPP semantics.
Note: While HTTP/1.1 allows a proxy to collect chunked responses Note: While HTTP/1.1 allows a proxy to collect chunked responses
over a period of time and return them back as a single un-chunked over a period of time and return them back as a single un-chunked
response (with a Content Length instead). However, in practice no response (with a Content Length instead). However, in practice no
proxy wants to have an infinite buffer. Also no proxy want to hold proxy wants to have an infinite buffer. Also no proxy want to hold
skipping to change at page 27, line 31 skipping to change at page 27, line 13
extension allocated in [ipp-ntfy]: extension allocated in [ipp-ntfy]:
Table 8 - The "event-notification-attributes-tag" value Table 8 - The "event-notification-attributes-tag" value
Tag Value (Hex) Meaning Tag Value (Hex) Meaning
0x07 "event-notification-attributes-tag" 0x07 "event-notification-attributes-tag"
12 Conformance Requirements 12 Conformance Requirements
The 'ippget' Delivery Method is RECOMMEND for Printers to support. This section lists the conformance requirements for clients and
Printers.
12.1 Conformance for IPP Printers 12.1 Conformance for IPP Printers
IPP Printers that conform to this specification: It is OPTIONAL for a Printer to support IPP Notifications as defined
in [ipp-ntfy]. 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:
1. MUST meet the conformance requirements defined in [ipp-ntfy] for 1. MUST meet the conformance requirements defined in [ipp-ntfy] for
a Pull Delivery Method; a Pull Delivery Method;
2. MUST support the Get-Notifications operation defined in section 2. MUST support the Get-Notifications operation defined in section
5, including Event Wait Mode; 5, including Event Wait Mode;
3. MUST support the Subscription Template object attributes as 3. MUST support the Subscription Template object attributes as
defined in section 6; defined in section 6;
4. MUST support the Subscription Description object attributes as 4. MUST support the Subscription Description object attributes as
defined in section 7; defined in section 7;
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
5. MUST support the "ippget-event-life" Printer Description 5. MUST support the "ippget-event-life" Printer Description
attribute defined in section 8.1, including retaining jobs in attribute defined in section 8.1, including retaining jobs in
the Job Retention and/or Job History phases for at least as long the Job Retention and/or Job History phases for at least as long
as the value specified by the Printer's "ippget-event-life"; as the value specified by the Printer's "ippget-event-life";
6. MUST support the additional values for IPP/1.1 Printer 6. MUST support the additional values for IPP/1.1 Printer
Description attributes defined in section 9; Description attributes defined in section 9;
7. MUST support the 'successful-ok-events-complete' status code as 7. MUST support the 'successful-ok-events-complete' status code as
described in section 10.1; described in section 10.1;
skipping to change at page 28, line 20 skipping to change at page 28, line 4
as the value specified by the Printer's "ippget-event-life"; as the value specified by the Printer's "ippget-event-life";
6. MUST support the additional values for IPP/1.1 Printer 6. MUST support the additional values for IPP/1.1 Printer
Description attributes defined in section 9; Description attributes defined in section 9;
7. MUST support the 'successful-ok-events-complete' status code as 7. MUST support the 'successful-ok-events-complete' status code as
described in section 10.1; described in section 10.1;
8. MUST support the "redirection-other-site" status code defined 8. MUST support the "redirection-other-site" status code defined
10.2, if it redirects Get-Notifications operations; 10.2, if it redirects Get-Notifications operations;
9. MUST listen for the IPP Get-Notifications operation requests on 9. MUST listen for the IPP Get-Notifications operation requests on
IANA-assigned well-known port 631, unless explicitly configured IANA-assigned well-known port 631, unless explicitly configured
by system administrators or site policies; by system administrators or site policies;
10. SHOULD NOT listen for IPP Get-Notifications operation requests 10. SHOULD NOT listen for IPP Get-Notifications operation requests
on any other port, unless explicitly configured by system on any other port, unless explicitly configured by system
administrators or site policies. administrators or site policies.
11. MUST meet the conformance requirements as stated in section
15.4.
12.2 Conformance for IPP Clients 12.2 Conformance for IPP Clients
IPP Clients that conform to this specification: It is OPTIONAL for an IPP Client to support IPP Notifications as
defined in [ipp-ntfy]. 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:
1.MUST create Subscription Objects containing the "notify-pull- 1.MUST create Subscription Objects containing the "notify-pull-
method" attribute (as opposed to the "notify-recipient-uri" method" attribute (as opposed to the "notify-recipient-uri"
attribute) using the 'ippget' keyword value; attribute) using the 'ippget' keyword value (see section
17.1.1);
2.MUST send IPP Get-Notifications operation requests via the port 2.MUST send IPP Get-Notifications operation requests (see section
specified in the associated 'ipp' URL (if present) or otherwise 5.1) via the port specified in the associated 'ipp' URL (if
via IANA assigned well-known port 631; present) or otherwise via IANA assigned well-known port 631;
3.MUST convert the associated 'ipp' URLs for use in IPP Get- 3.MUST convert the associated 'ipp' URLs for use in IPP Get-
Notifications operation to their corresponding 'http' URL forms Notifications operation to their corresponding 'http' URL forms
for use in the HTTP layer according to the rules in section 5 for use in the HTTP layer according to the rules in section 5
"IPP URL Scheme" in [RFC2910]. "IPP URL Scheme" in [RFC2910].
13 IANA Considerations 4.MUST meet the conformance requirements as stated in section
15.5.
13 Normative References
[ipp-ntfy]
Herriot, R., and T. Hastings, "Internet Printing Protocol/1.1: IPP
Event Notifications and Subscriptions", <draft-ietf-ipp-not-spec-
09.txt>, June 27, 2002.
[RFC2119]
S. Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119 , March 1997
[RFC2910]
Herriot, R., Butler, S., Moore, P., and R. Tuner, "Internet
Printing Protocol/1.1: Encoding and Transport", RFC 2910, September
2000.
[RFC2911]
deBry, R., Hastings, T., Herriot, R., Isaacson, S., and P. Powell,
"Internet Printing Protocol/1.1: Model and Semantics", RFC 2911,
September 2000.
14 Informative References
[RFC2565]
Herriot, R., Butler, S., Moore, P., and R. Turner, "Internet
Printing Protocol/1.0: Encoding and Transport", RFC 2565, April
1999.
[RFC2566]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, and P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", RFC 2566,
April 1999.
[RFC2567]
Wright, D., "Design Goals for an Internet Printing Protocol", RFC
2567, April 1999.
[RFC2568]
Zilles, S., "Rationale for the Structure and Model and Protocol for
the Internet Printing Protocol", RFC 2568, April 1999.
[RFC2569]
Herriot, R., Hastings, T., Jacobs, N., Martin, J., "Mapping between
LPD and IPP Protocols", RFC 2569, April 1999.
[RFC2616]
R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1",
RFC 2616, June 1999.
[RFC2707]
Bergman, R., Hastings, T., Isaacson, S., and H. Lewis, "Job
Monitoring MIB - V1.0", November 1999.
[RFC3196]
Hastings, T., Manros, C., Zehler, P., Kugler, C., and H. Holst,
"Internet Printing Protocol/1.1: Implementer's Guide", RFC3196,
November 2001.
15 Security Considerations
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.
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.
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.
15.1 Notification Recipient client access rights
The Notification Recipient client MUST have the following access
rights to the Subscription object(s) targeted by the Get-
Notifications operation request:
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) be 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
the attributes returned by the Get-Notifications operation, in a
manner similar to the Get-Job-Attributes operation (see [RFC2911]
end of section 3.3.4.2).
15.2 Printer security threats
Because the Get-Notifications operation is sent in the same direction
as 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).
15.3 Notification Recipient security threats
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 who initiates the Get-
Notifications operation (see section 5). Therefore, there is no
chance of "spam" notifications with this method.
Note: when a client stays connected to a Printer using the Event
Wait Mode (see section 5.1.3) in order to receive Event Notifications
as they occur, such a client can close down the IPP connection at any
time, and so can avoid future unwanted Event Notifications at any
time.
It is true that client has control about whether to ask for Event
Notifications. However, if the client subscribes to an event, and
does a Get-Notifications request, the client gets all events for the
Subscription Object in the sequence number range (see section 5.1.2),
not just the ones the client 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 the ones the client is interested
in. A client can protect itself better by subscribing to his own
jobs using a Per-Job Subscription, rather than creating a Per-Printer
subscription whose Job events apply to all jobs.
15.4 Security requirements for Printers
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.
15.5 Security requirements for clients
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.
16 Internationalization Considerations
The IPP Printer MUST localize the "notify-text" attribute as
specified in section 14 of [ipp-ntfy].
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.
17 IANA Considerations
This section contains the exact information for IANA to add to the This section contains the exact information for IANA to add to the
IPP Registries according to the procedures defined in RFC 2911 IPP Registries according to the procedures defined in RFC 2911
[RFC2911] section 6. [RFC2911] section 6.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
Note to RFC Editors: Replace RFC NNNN below with the RFC number Note to RFC Editors: Replace RFC NNNN below with the RFC number
for this document, so that it accurately reflects the content of for this document, so that it accurately reflects the content of
the information for the IANA Registry. the information for the IANA Registry.
13.1 Additional attribute value registrations for existing attributes 17.1 Additional attribute value registrations for existing attributes
This section lists additional attribute value registrations for use This section lists additional attribute value registrations for use
with existing attributes defined in other documents. with existing attributes defined in other documents.
13.1.1 Additional values for the "notify-pull-method-supported" Printer 17.1.1 Additional values for the "notify-pull-method-supported" Printer
attribute attribute
The following table lists the keyword value defined in this document The following table lists the keyword value defined in this document
as an additional keyword value for use with the "notify-pull-method- as an additional keyword value for use with the "notify-pull-method-
supported" Printer attribute defined in [ipp-ntfy]. This is to be supported" Printer attribute defined in [ipp-ntfy]. This is to be
registered according to the procedures in RFC 2911 [RFC2911] section registered according to the procedures in RFC 2911 [RFC2911] section
6.1. 6.1.
keyword Attribute Values: Ref. Section: keyword Attribute Values: Ref. Section:
ippget RFC NNNN 9.1 ippget RFC NNNN 9.1
skipping to change at page 29, line 27 skipping to change at page 33, line 4
attribute attribute
The following table lists the keyword value defined in this document The following table lists the keyword value defined in this document
as an additional keyword value for use with the "notify-pull-method- as an additional keyword value for use with the "notify-pull-method-
supported" Printer attribute defined in [ipp-ntfy]. This is to be supported" Printer attribute defined in [ipp-ntfy]. This is to be
registered according to the procedures in RFC 2911 [RFC2911] section registered according to the procedures in RFC 2911 [RFC2911] section
6.1. 6.1.
keyword Attribute Values: Ref. Section: keyword Attribute Values: Ref. Section:
ippget RFC NNNN 9.1 ippget RFC NNNN 9.1
The resulting keyword method attribute value registrations will be The resulting keyword method attribute value registrations will be
published in the published in the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute- ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute-
values/notify-pull-method-supported/ values/notify-pull-method-supported/
area. area.
13.1.2 Additional values for the "operations-supported" Printer 17.1.2 Additional values for the "operations-supported" Printer
attribute attribute
The following table lists the enum attribute value defined in this The following table lists the enum attribute value defined in this
document as an additional type2 enum value for use with the document as an additional type2 enum value for use with the
"operations-supported" Printer attribute defined in [RFC2911]. This "operations-supported" Printer attribute defined in [RFC2911]. This
is to be registered according to the procedures in RFC 2911 [RFC2911] is to be registered according to the procedures in RFC 2911 [RFC2911]
section 6.1. section 6.1.
type2 enum Attribute Values: Value Ref. Section: type2 enum Attribute Values: Value Ref. Section:
Get-Notifications 0x001C RFC NNNN 9.2 Get-Notifications 0x001C RFC NNNN 9.2
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
The resulting enum attribute value registration will be published in The resulting enum attribute value registration will be published in
the the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute- ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute-
values/operations-supported/ values/operations-supported/
area. area.
13.2 Operation Registrations 17.2 Operation Registrations
The following table lists the operation defined in this document. The following table lists the operation defined in this document.
This is to be registered according to the procedures in RFC 2911 This is to be registered according to the procedures in RFC 2911
[RFC2911] section 6.4. [RFC2911] section 6.4.
Operations: Ref. Section: Operations: Ref. Section:
Get-Notifications operation RFC NNNN 5 Get-Notifications operation RFC NNNN 5
The resulting operation registration will be published in the The resulting operation registration will be published in the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/operations/ ftp://ftp.iana.org/in-notes/iana/assignments/ipp/operations/
area. area.
13.3 Attribute Registrations 17.3 Attribute Registrations
The following table lists the attribute defined in this document. The following table lists the attribute defined in this document.
This is to be registered according to the procedures in RFC 2911 This is to be registered according to the procedures in RFC 2911
[RFC2911] section 6.2. [RFC2911] section 6.2.
Printer Description attributes: Ref. Section: Printer Description attributes: Ref. Section:
ippget-event-life (integer(15:MAX)) RFC NNNN 8.1 ippget-event-life (integer(15:MAX)) RFC NNNN 8.1
The resulting attribute registration will be published in the The resulting attribute registration will be published in the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attributes/ ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attributes/
area. area.
13.4 Status code Registrations 17.4 Status code Registrations
The following table lists the status code defined in this document. The following table lists the status code defined in this document.
This is to be registered according to the procedures in RFC 2911 This is to be registered according to the procedures in RFC 2911
[RFC2911] section 6.6. [RFC2911] section 6.6.
Status codes: Ref. Section: Status codes: Ref. Section:
successful-ok-events-complete (0x0007) RFC NNNN 10.1 successful-ok-events-complete (0x0007) RFC NNNN 10.1
redirection-other-site (0x0300) RFC NNNN 10.2 redirection-other-site (0x0300) RFC NNNN 10.2
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
The resulting status code registration will be published in the The resulting status code registration will be published in the
ftp://ftp.iana.org/in-notes/iana/assignments/ipp/status-codes/ ftp://ftp.iana.org/in-notes/iana/assignments/ipp/status-codes/
area. area.
14 Internationalization Considerations 18 Contributors
The IPP Printer MUST localize the "notify-text" attribute as
specified in section 14 of [ipp-ntfy].
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.
15 Security Considerations
The IPP Model and Semantics document [RFC2911] discusses high-level
security requirements (Client Authentication, Server Authentication
and Operation Privacy). Client Authentication is the mechanism by
which the client proves its identity to the server in a secure
manner. Server Authentication is the mechanism by which the server
proves its identity to the client in a secure manner. Operation
Privacy is defined as a mechanism for protecting operations from
eavesdropping.
Unlike other Event Notification delivery methods in which the IPP
Printer initiates the Event Notification, with the method defined in
this document, the Notification Recipient is the client who initiates
the Get-Notifications operation. Therefore, there is no chance of
"spam" notifications with this method. Furthermore, such a client
can close down the HTTP channel at any time, and so can avoid future
unwanted Event Notifications at any time.
Because the Get-Notifications operation is sent in the same direction
as Job Creation operations, this Event Notification Delivery Method
poses no additional firewall or port assignment issues.
16 References
[ipp-iig]
Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P.,
"Internet Printing Protocol/1.1: draft-ietf-ipp-implementers-
guide-v11-03.txt, work in progress, July 17, 2001
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
[ipp-ntfy]
R. Herriot, Hastings, T., Isaacson, S., Martin, J., deBry, R.,
Shepherd, M., Bergman, R., "Internet Printing Protocol/1.1: IPP
Event Notifications and Subscriptions", <draft-ietf-ipp-not-spec-
08.txt>, November 19, 2001.
[RFC2026]
S. Bradner, "The Internet Standards Process -- Revision 3", RFC
2026, October 1996.
[RFC2119]
S. Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119 , March 1997
[RFC2565]
Herriot, R., Butler, S., Moore, P., and R. Turner, "Internet
Printing Protocol/1.0: Encoding and Transport", RFC 2565, April
1999.
[RFC2566]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, and P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", RFC 2566,
April 1999.
[RFC2567]
Wright, D., "Design Goals for an Internet Printing Protocol", RFC
2567, April 1999.
[RFC2568]
Zilles, S., "Rationale for the Structure and Model and Protocol for
the Internet Printing Protocol", RFC 2568, April 1999.
[RFC2569]
Herriot, R., Hastings, T., Jacobs, N., Martin, J., "Mapping between
LPD and IPP Protocols", RFC 2569, April 1999.
[RFC2616] Carl Kugler and Harry Lewis contributed the basic idea of in-band
R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. "smart polling" coupled with multiple responses for a single
Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1", operation on the same connection, one response for each event as it
RFC 2616, June 1999. 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.
[RFC2707] Carl Kugler
Bergman, R., Hastings, T., Isaacson, S., and H. Lewis, "Job IBM
Monitoring MIB - V1.0", November 1999. P.O. Box 1900
Boulder, CO 80301-9191
[RFC2910] Phone:
Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing Fax:
Protocol/1.1: Encoding and Transport", RFC 2910, September 2000. e-mail: kugler@us.ibm.com
INTERNET-DRAFT IPP: The 'ippget' Delivery Method Harry Lewis
IBM
P.O. Box 1900
Boulder, CO 80301-9191
[RFC2911] Phone: 303-924-5337
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, FAX:
"Internet Printing Protocol/1.1: Model and Semantics", RFC 2911, e-mail: harryl@us.ibm.com
September 2000.
17 Authors' Addresses 19 Authors' Addresses
Robert Herriot Robert Herriot
706 Colorado Ave. 706 Colorado Ave.
Palo Alto, CA 94303 Palo Alto, CA 94303
Phone: 650-327-4466 Phone: 650-327-4466
Fax: 650-327-4466 Fax: 650-327-4466
email: bob@herriot.com email: bob@herriot.com
Thomas N. Hastings Thomas N. Hastings
Xerox Corporation Xerox Corporation
737 Hawaii St. ESAE 231 737 Hawaii St. ESAE 231
El Segundo CA 90245 El Segundo CA 90245
Phone: 310-333-6413 Phone: 310-333-6413
Fax: 310-333-5514 Fax: 310-333-5514
email: hastings@cp10.es.xerox.com email: hastings@cp10.es.xerox.com
Carl Kugler
IBM
P.O. Box 1900
Boulder, CO 80301-9191
Phone:
Fax:
e-mail: kugler@us.ibm.com
Harry Lewis
IBM
P.O. Box 1900
Boulder, CO 80301-9191
Phone: 303-924-5337
FAX:
e-mail: harryl@us.ibm.com
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
IPP Web Page: http://www.pwg.org/ipp/ IPP Web Page: http://www.pwg.org/ipp/
IPP Mailing List: ipp@pwg.org IPP Mailing List: ipp@pwg.org
To subscribe to the ipp mailing list, send the following email: To subscribe to the ipp mailing list, send the following email:
1) send it to majordomo@pwg.org 1) send it to majordomo@pwg.org
2) leave the subject line blank 2) leave the subject line blank
3) put the following two lines in the message body: 3) put the following two lines in the message body:
subscribe ipp subscribe ipp
end end
Implementers of this specification document are encouraged to join Implementers of this specification document are encouraged to join
the IPP Mailing List in order to participate in any discussions of the IPP Mailing List in order to participate in any discussions of
clarification issues and review of registration proposals for clarification issues and review of registration proposals for
additional attributes and values. In order to reduce spam the additional attributes and values. In order to reduce spam the
mailing list rejects mail from non-subscribers, so you must subscribe 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 to the mailing list in order to send a question or comment to the
mailing list. mailing list.
18 Description of Base IPP documents 20 Description of Base IPP documents
The base set of IPP documents includes: The base set of IPP documents includes:
Design Goals for an Internet Printing Protocol [RFC2567] Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the Internet Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol [RFC2568] Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911] Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910] Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig] Internet Printing Protocol/1.1: Implementer's Guide [[RFC3196]]
Mapping between LPD and IPP Protocols [RFC2569] Mapping between LPD and IPP Protocols [RFC2569]
Internet Printing Protocol (IPP): IPP Event Notifications and
Subscriptions [ipp-ntfy]
The "Design Goals for an Internet Printing Protocol" document takes a The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet. It identifies included in a printing protocol for the Internet. It identifies
requirements for three types of users: end users, operators, and requirements for three types of users: end users, operators, and
administrators. It calls out a subset of end user requirements that administrators. It calls out a subset of end user requirements that
are satisfied in IPP/1.0. A few OPTIONAL operator operations have are satisfied in IPP/1.0. A few OPTIONAL operator operations have
been added to IPP/1.1. been added to IPP/1.1.
The "Rationale for the Structure and Model and Protocol for the The "Rationale for the Structure and Model and Protocol for the
Internet Printing Protocol" document describes IPP from a high level Internet Printing Protocol" document describes IPP from a high level
view, defines a roadmap for the various documents that form the suite view, defines a roadmap for the various documents that form the suite
of IPP specification documents, and gives background and rationale of IPP specification documents, and gives background and rationale
for the IETF working group's major decisions. for the IETF working group's major decisions.
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
The "Internet Printing Protocol/1.1: Model and Semantics" document The "Internet Printing Protocol/1.1: Model and Semantics" document
describes a simplified model with abstract objects, their attributes, describes a simplified model with abstract objects, their attributes,
and their operations that are independent of encoding and transport. and their operations that are independent of encoding and transport.
It introduces a Printer and a Job object. The Job object optionally It introduces a Printer and a Job object. The Job object optionally
supports multiple documents per Job. It also addresses security, supports multiple documents per Job. It also addresses security,
internationalization, and directory issues. internationalization, and directory issues.
The "Internet Printing Protocol/1.1: Encoding and Transport" document The "Internet Printing Protocol/1.1: Encoding and Transport" document
is a formal mapping of the abstract operations and attributes defined is a formal mapping of the abstract operations and attributes defined
in the model document onto HTTP/1.1 [RFC2616]. It defines the in the model document onto HTTP/1.1 [RFC2616]. It defines the
skipping to change at page 35, line 35 skipping to change at page 37, line 5
objects. It is intended to help them understand IPP/1.1 and some of 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 the considerations that may assist them in the design of their client
and/or IPP object implementations. For example, a typical order of and/or IPP object implementations. For example, a typical order of
processing requests is given, including error checking. Motivation processing requests is given, including error checking. Motivation
for some of the specification decisions is also included. for some of the specification decisions is also included.
The "Mapping between LPD and IPP Protocols" document gives some The "Mapping between LPD and IPP Protocols" document gives some
advice to implementers of gateways between IPP and LPD (Line Printer advice to implementers of gateways between IPP and LPD (Line Printer
Daemon) implementations. Daemon) implementations.
The "IPP Event Notifications and Subscriptions" document defines an 21 Full Copyright Statement
extension to IPP/1.0 [RFC2566, RFC2565] and IPP/1.1 [RFC2911,
RFC2910]. This extension allows a client to subscribe to printing
related Events and defines the semantics for delivering asynchronous
Event Notifications to the specified Notification Recipient via a
specified Delivery Method (i.e., protocols) defined in (separate)
Delivery Method documents.
19 Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
INTERNET-DRAFT IPP: The 'ippget' Delivery Method
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
 End of changes. 

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