IPP Mail Archive: IPP> RE: IFX> NOT - IPPGET Delivery Met

IPP Mail Archive: IPP> RE: IFX> NOT - IPPGET Delivery Met

IPP> RE: IFX> NOT - IPPGET Delivery Method down-loaded [text version p osted]

From: McDonald, Ira (IMcDonald@crt.xerox.com)
Date: Fri Oct 19 2001 - 18:18:10 EDT

  • Next message: Hastings, Tom N: "IPP> NOT - IPPGET Delivery Method - ISSUE 02 'ippget' URI"


    I just posted the converted '.txt' file to the PWG FTP server at:


    Table 2 has some minor formatting problems in the header lines.
    Tom will fix them in the next draft.

    - Ira McDonald
      High North Inc

    -----Original Message-----
    From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com]
    Sent: Friday, October 19, 2001 6:37 AM
    To: ipp (E-mail); IPP FAX DL (E-mail)
    Subject: IFX> NOT - IPPGET Delivery Method down-loaded - REQUIRED for

    I've posted the updated IPPGET Event Notification Delivery Method that is


    The -rev version show the revisions since the July 17, 2001 version.

    It has all of the agreements reached at the August 1, IPP FAX meeting in
    Toronto and the subsequent 3 telecon, August 11, 14, and 17. See the
    telecon and meeting notes for the list of the changes.

    I'll send a .txt I-D later Friday. Please send any comments to the mailing
    list. We'll also review at the IPPFAX WG meeting, next Wednesday, October
    24 in San Antonio.

    There are two issues:

            ISSUE 01: Although we agreed to extend Job Creation operations to
    support Event Wait Mode, it seems to be an unnecessary complication, since
    the Printer MUST keep events for at least 15 seconds. So OK NOT to add the
    "notify-wait" (boolean) operation attribute to Job Creation operations and
    NOT have to have Job Creation responses return Event Notification Groups (in
    addition to returning Subscription Attribute Groups).

            ISSUE 02: How unique do we need the "notify-recipient-uri" (uri)
    URL now that the Printer doesn't use anything but the scheme in the URL to
    match on?

    Here are the major changes:

    1. Removed the "notify-recipients-uri" operation attribute from
    Get-Notifications, so no URI matching.

    2. Changed "notify-subscription-id" (integer(1:MAX)) to
    "notify-subscription-ids" (1setOf integer(1:MAX)); the client MUST supply
    with at least one value. Printer MUST support multiple-values.

    3. Added "notify-sequence-numbers" (1setOf integer(1:MAX)) to be parallel
    and be a floor to the Event Notifications sequence numbers returned. The
    client SHOULD supply. Printer MUST support multiple-values.

    4. In Event Wait Mode, each response is a full IPP response.

    5. Moved "notify-get-interval" back to the operations attributes group in
    the response.

    6. Added 'successful-ok-events-complete to indicate that there will be no
    more events for this Subscription object.

    7. The Printer MUST support Event Wait Mode.

    8. The client can end Event Wait Mode (without closing the connection) by
    sending "notify-wait" = 'false' any time. The Printer can end Event Wait
    Mode (without closing the connection) by returning "notify-get-internal"
    operation attribute any time (including immediately).

    9. Changed the lower limit for "ippget-event-life" from 1 to 15 seconds and
    recommend 60 seconds to agree with the PWG Job Monitoring MIB (RFC 2707).


    This archive was generated by hypermail 2b29 : Fri Oct 19 2001 - 18:19:32 EDT