IPP> NOT - Updated: The 'ippget' Delivery Method for Event Notificatio ns

[Hastings, Tom N]

I've down loaded an updated version of "The 'ippget' Delivery Method for
Event Notifications"
spec as agreed on the mailing list.  The change (also reflected in the
updated 
Base IPP Notification Spec) is for 'ippget' (and any other Pull Delivery
Methods)
to use the "notify-pull-method" (type2 keyword) Subscription Template
attribute instead 
of the "notify-recipient-uri" (uri) Subscription Template attribute.

Also as agreed we did not add Event Wait Mode to the Job Creation
operations, so the 
Notification Recipient MUST do a Get-Notifications operation on the same or
different 
channel after receiving the subscription-id in the Job Creation response.

I've submitted the draft-ietf-ipp-notify-get-06.txt to the IETF
Internet-Draft
Editor in time for the IETF dead-line today, so it will be published as an
I-D in the next few days.  Then we need to do an IPP WG Last Call on this
document 
(as well as repeat the IPP WG Last Call on the "IPP Event Notifications and
Subscriptions" 
spec).

ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-011119.pdf
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-011119.doc
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-011119-rev.pdf
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-011119-rev.doc
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get-011119.txt
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-notify-get-06.txt

Please send any comments to the DL.

Thanks,
Tom Hastings