Hi folks, Tuesday (23 July 2002)
Per my action item from today's PSI Telecon, here's some information on
the basic event notification model from IPP. For more info please see:
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-not-spec-09.txt
Cheers,
- Ira McDonald
High North Inc
----------------------------------------
Printer Event Conformance
printer-state-changed REQUIRED
printer-restarted OPTIONAL
printer-shutdown OPTIONAL
printer-stopped REQUIRED
printer-config-changed OPTIONAL
printer-media-changed OPTIONAL
printer-finishings-changed OPTIONAL
printer-order-queue-changed OPTIONAL
----------------------------------------
Job Event Conformance
job-state-changed REQUIRED
job-created REQUIRED
job-completed REQUIRED
job-stopped OPTIONAL
job-config-changed OPTIONAL
job-progress OPTIONAL
----------------------------------------
Table 5 - Attributes in Event Notification Content
Source Value Sends Source Object
notify-subscription-id (integer(1:MAX)) MUST Subscription
notify-printer-uri (uri) MUST Subscription
notify-subscribed-event (type2 keyword) MUST Event
Notification
printer-up-time (integer(MIN:MAX)) MUST Printer
printer-current-time (dateTime) * MUST Printer
notify-sequence-number (integer (0:MAX)) SHOULD Subscription
notify-charset (charset) SHOULD Subscription
notify-natural-language (naturalLanguage) SHOULD Subscription
notify-user-data (octetString(63)) ** SHOULD Subscription
notify-text (text) SHOULD Event
Notification
attributes from the "notify-attributes" MAY Printer
attribute ***
attributes from the "notify-attributes" MAY Job
attribute ***
attributes from the "notify-attributes" MAY Subscription
attribute ***
*A Printer MUST send this value only if and only if it supports the
Printer's "printer-current-time" attribute.
** If the Subscription Object does not contain a "notify-user-data"
attribute and the Delivery Method Document REQUIRES the Printer to
send the "notify-user-data" source value in the Event Notification,
the Printer MUST send an octet-string of length 0.
*** The last three rows represent additional attributes that a client
MAY request via the "notify-attributes" attribute. A Printer MAY
support the "notify-attributes" attribute. The Delivery Method MUST
say that the Printer MUST, SHOULD, MAY, MUST NOT, SHOULD NOT, or NEED
NOT support the "notify-attributes" attribute and specific values of
this attribute. The Delivery Method MAY say that support for the
"notify-attributes" is conditioned on support of the attribute by the
Printer or it MAY say that Printer MUST support the "notify-
attributes" attribute if the Printer supports the Delivery Method.
----------------------------------------
Table 6 - Additional Event Notification Content for Job Events
Source Value Sends Source Object
job-id (integer(1:MAX)) MUST Job
job-state (type1 enum) MUST Job
job-state-reasons (1setOf type2 keyword) MUST Job
job-impressions-completed (integer(0:MAX)) * MUST Job
* The Printer MUST send the "job-impressions-completed" attribute in
an Event Notification only for the combinations of Events and
Subscribed Events shown in Table 7.
----------------------------------------
Table 7 - Combinations of Events and Subscribed Events for
"job-impressions-completed"
Job Event Subscribed Job Event
'job-progress' 'job-progress'
'job-completed' 'job-completed'
'job-completed' 'job-state-changed'
----------------------------------------
Table 8 - Additional Event Notification Content for Printer Events
Source Value Sends Source Object
printer-state (type1 enum) MUST Printer
printer-state-reasons (1setOf type2 keyword) MUST Printer
printer-is-accepting-jobs (boolean) MUST Printer
----------------------------------------
This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 18:58:27 EDT