IPP> RESEND: NOT - Notification spec, mailto, and indp down loaded

[Hastings, Tom N]

This mail message seems to have been lost, so I'm resending it.

Tom

> -----Original Message-----
> From:	Hastings, Tom N 
> Sent:	Friday, July 14, 2000 18:56
> To:	'ipp'
> Subject:	NOT - Notification spec, mailto, and indp down loaded
> 
> The updated notification specs are posted: The Notification spec, the
> 'mailto' delivery method, and the 'indp' delivery method (and protocol).
> They have also been sent to the Internet-Drafts editor as well.  These are
> the documents that will be an IPP WG Last Call ending just after the IETF
> meeting in August.  Both Delivery Methods are RECOMMENDED for a Printer to
> support.  Also the beginnings of an Implementer's Guide.
> 
> I have combined all of these files listed below into a single .zip file
> (1M bytes) as well, so you can get all of the files at once:
> 
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-000714.zip
> 
> The Event Notification spec:
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-000713.doc
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-000713.pdf
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-000713-rev.doc
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-000713-rev.pdf
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-000713.txt
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-not-spec-04.txt
> 
> The mailto Delivery Method Document:
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-mailto-000713.doc
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-mailto-000713.pdf
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-mailto-000713-rev.doc
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-mailto-000713-rev.pdf
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-mailto-000713.txt
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-notify-mailto-02.txt
> 
> The indp Delivery Method Document:
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-indp-method-02-000714
> .doc
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-indp-method-02-000714
> .pdf
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-indp-method-02-000714
> -rev.doc
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-indp-method-02-000714
> -rev.pdf
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-indp-method-02.txt
> 
> The following files are the beginnings of an Implementer's Guide for
> notification.
> They contain useful tables for implementers.
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-for-IIG-000714-rev.doc
> ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-for-IIG-000714-rev.pdf
> 
> The change history for the Notification Spec (agreed to at the SFO 7/12/00
> meeting):
> 
> 	Changes to the June 30, 2000 version to create the July 13, 2000
> version
> The following changes were made to the June 30, 2000 version to create the
> July 13, 2000 version based on the agreements reached at the July IPP WG
> meeting:
> 1.	Deleted the "notify-max-job-subscriptions" and
> "notify-max-printer-subscriptions" Printer Description attributes, since
> the maximum cannot be guaranteed.
> 2.	Added the "notify-time-interval (integer(0:MAX)) Subscription
> Template attribute to give Subscribing Client control over moderation of
> 'job-progress' Event Notifications that MUST be implemented if and only if
> the 'job-progress' event is implemented.  There are no default or
> supported Printer attributes.
> 3.	Removed the idea that a Delivery Method MAY allow the Printer to
> moderate certain high frequency events.
> 4.	Clarified that the Printer MUST treat the address part of the
> "notify-recipient-uri" attribute value as opaque.
> 5.	Added the REQUIRED 'printer-stopped' event and the OPTIONAL
> 'job-stopped' event.
> 6.	Deleted the 'job-purged' event.
> 7.	Deleted the "notify-persistence" Subscription Template attribute.
> 8.	Clarified the concept of Compound Event Notifications used by both
> 'mailto' and 'indp'.
> 9.	Clarified that a Printer MUST cancel a Subscription if it gets hard
> errors when sending that will never change.
> 10.	Clarified Figure 3 - Opaque Use of a Notification Service
> Transparent to the Client to indicate that the Printer includes the
> Notification Service.
>