IPP Mail Archive: IPP> NOT - "The 'ippget' Delivery Met

IPP Mail Archive: IPP> NOT - "The 'ippget' Delivery Met

IPP> NOT - "The 'ippget' Delivery Method for Event Notifications" docu ment downloaded

From: Hastings, Tom N (hastings@cp10.es.xerox.com)
Date: Sat Mar 03 2001 - 13:47:40 EST

  • Next message: Hastings, Tom N: "IPP> MIME - List of Printer MIB, UPnP, and Wireless Print Document For mats downloaded"

    I've down loaded the updated "The 'ippget' Delivery Method for Event
    Notifications" document. The versions with revisions are also in the .zip
    file for next week's IPP WG meeting and are on the agenda.

    The major change was to add the necessary material to be able to register
    the 'ippget' scheme with IANA (see section 9). Also added client and
    Printer conformance requirements for using the 'ippget' method (see section

    This document has been in the Area Director's queue since last August, so
    this February 28, 2001 version will replace the November 16, 2000 version
    according to the IETF procedures for this situation.

    The files are at:

    Here is the Abstract:

            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.

    Please send comments to the mailing list.


    This archive was generated by hypermail 2b29 : Sat Mar 03 2001 - 13:48:58 EST