IPP Mail Archive: IPP> NOT - Issue for the INDP Protocol doc

IPP> NOT - Issue for the INDP Protocol document

From: Hastings, Tom N (hastings@cp10.es.xerox.com)
Date: Tue Mar 07 2000 - 14:29:28 EST

  • Next message: Hastings, Tom N: "IPP> NOT - Few minor remaining issues in IPP Notification Spec"

    In writing up the IPP Notification Delivery Protocol (INDP) (Action Item
    from February meeting) Hugo and I have the following issue:

    INDP defines some new status codes for the new operations between the
    Printer and the Notification Service.

    Here is the issue:

    1.1 New status codes
    ISSUE 06 - Should we move the status codes into the Notification Model
    document in order to have the same status codes for any other delivery
    method that might be defined?
    The following status codes are defined:
    1.1.1 unknown-notification-recipient. (0xXXX)
    The Notification Recipient returns this status code in order to indicate
    that the intended Ultimate Notification Recipient is not known to the
    Notification Recipient.
    1.1.2 unable-to-delivery-notification-report (0xXXX)
    The Notification Recipient returns this status code in order to indicate
    that it was unable to deliver the event Notification to the intended
    Ultimate Notification Recipient.
    1.1.3 successful-ok-but-cancel-subscription (0xXXXX)
    The Notification Recipient indicates that it no longer wants to receive
    Notifications for this Subscription object. Therefore, the Subscription
    object is canceled. Note: this status code allows the Notification
    Recipient to cancel a Subscription object without having to be the owner of
    the Subscription object. Only the owner of the Subscription object can
    cancel a Subscription object using the Cancel-Subscription operation.
    1.1.4 unknown-registration-id (0xXXX)
    1.1.5 successful-ok-but-error-accessing-persistent-storage (0xXXXX)



    This archive was generated by hypermail 2b29 : Tue Mar 07 2000 - 14:35:36 EST