Hi Harry,
Concensus on more recent IPP Fax telecons this summer has been that
Subscription objects themselves MUST have the same lifetime as
their associated Jobs. And further that BOTH the Subscription and
the Job (with _all_ of its attributes) MUST persist until the
lifetime of the 'job-completed' event (last event) has expired.
So, I suggest that:
If an IPP Printer supports "persistent" Jobs (across power cycles),
then that IPP Printer MUST support "persistent" associated per-job
Subscriptions.
Now, if event lifetimes are long enough, do the actual _events_
"persist" into the next power cycle, if necessary (according to
the event delivery method constraints in 'notify-recipient-uri')?
Cheers,
- Ira McDonald
High North Inc
-----Original Message-----
From: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Tuesday, August 28, 2001 6:51 PM
To: ipp at pwg.org
Subject: IPP> Notification Subscriptions across Power Cycles
Does IPP have a "position" on either per-job (i.e. if job is spooled) or
per-printer subscriptions and whether or not they should be preserved
across power cycles?
Looking at the Notification Spec (draft-ietf-ipp-not-spec-07) the only
related discussion appears to be in Section 5.4.3 (When the Printer powers
up, it MUST set the value of this
(notify-lease-expiration-time) attribute in each persistent Subscription
Object...) which implies per-printer subscriptions may be expected to
persist
across power cycle.
----------------------------------------------
Harry Lewis
IBM Printing Systems
----------------------------------------------