This is a repeat of the message announcing this updated version of the
ippget spec. I sent it on November 21, 2000, but it appears not to have
been received by anyone, including me. So here it is again.
It was announced as an Internet-Draft on November 29, 2000 by the
> -----Original Message-----
> From: Hastings, Tom N
> Sent: Tuesday, November 21, 2000 17:21
> To: ipp (E-mail)
> Subject: The 'ippget' Delivery Method for Event Notifications - 01
> The "The 'ippget' Delivery Method for Event Notifications" documents are
> down-loaded. The .txt version is being send to the Internet-Draft editor.
> When it is published as an I-D, Carl-Uno will send it to the IESG. This
> was mainly editorial work: fix the title as noted during the last call and
> to align the presentation with the other Delivery Method documents, plus
> indicate under IANA Considerations:
> The 'ippget' URL scheme for the 'ippget' Delivery Method will be
> registered with IANA according to the procedures of [RFC2717]. According
> to RFC 2717, we have to write a simple RFC in order to register a URL
> The notification extension document [ipp-ntfy] defines operations that a
> client can perform in order to create Subscription Objects in a Printer
> and carry out other operations on them. A Subscription Object represents a
> Subscription abstraction. The Subscription Object specifies that when one
> of the specified Events occurs, the Printer sends an asynchronous Event
> Notification to the specified Notification Recipient via the specified
> Delivery Method (i.e., protocol).
> The notification extension document [ipp-ntfy] specifies that each
> Delivery Method is defined in another document. This document is one such
> document, and it specifies the 'ippget' delivery method.
> The 'ippget' Delivery Method is a 'pull and push' Delivery Method. That
> is, the Printer saves Event Notification for a period of time and expects
> the Notification Recipient to fetch the Event Notifications (the pull
> part). The Printer continues to send Event Notifications to the
> Notification Recipient as Events occur (the push part) if the client has
> selected the option to wait for additional Event Notifications.
> When a Printer supports this Delivery Method, it holds each Event
> Notification for an amount of time, called the Event Notification Lease
> When a Notification Recipient wants to receive Event Notifications, it
> performs an IPP operation called 'Get-Notifications', which this document
> defines. This operation causes the Printer to return all Event
> Notifications held for the Notification Recipient. If the Notification
> Recipient has selected the option to wait for additional Event
> Notifications, the Printer continues sending Event Notifications to the
> Notification Recipient as additional Events occur.
This archive was generated by hypermail 2b29 : Fri Feb 02 2001 - 19:16:17 EST