IPP Mail Archive: RE: IPP> NOT - Updated 'ipp-get' Delivery

IPP Mail Archive: RE: IPP> NOT - Updated 'ipp-get' Delivery

RE: IPP> NOT - Updated 'ipp-get' Delivery Method for Event Notifi cation po sted

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Wed Sep 20 2000 - 17:41:56 EDT

  • Next message: Hastings, Tom N: "RE: IPP> REG - Proposal for "job-recipient-name" Job Template att ribute"

    Hi Carl-Uno and Tom,

    Yes - I support moving the 'ippget:' (in-band IPP
    notifications) proposal forward as a RECOMMENDED
    method.

    I believe, after we have more implementation and
    interop testing experience, we ultimately WILL be
    able to decide on one (or two?) IPP notification
    delivery methods that are REQUIRED for all IPP
    Printers that support notifications. But that
    time is in the future.

    Cheers,
    - Ira McDonald, consulting architect at Xerox and Sharp
      High North Inc

    PS - I've just read this latest draft and will send
    some mostly minor comments at some point on the list.

    -----Original Message-----
    From: Manros, Carl-Uno B [mailto:cmanros@cp10.es.xerox.com]
    Sent: Wednesday, September 20, 2000 11:42 AM
    To: Hastings, Tom N; ipp (E-mail)
    Subject: RE: IPP> NOT - Updated 'ipp-get' Delivery Method for Event
    Notifi cation po sted

    All,

    We have been going backwards and forwards on how many delivery methods we
    want.
    For all those out there who were not attending the PWG meeting I would like
    to
    get a feeling for your reaction to have one more RECOMMENDED delivery method
    and for that matter about having a third delivery method at all.

    It should be said that the people in the meeting all seemed to like the new
    method, which should also be relatively easy to implement.

    In the special meeting on QUALDOCS, now renamed IPP FAX, the 'ippget'
    seemed to be the best fit for that project, if indeed notifications
    will be included, which isn't yet clear from the discussions.

    I would like to hear from more people on the DL about this 3rd delivery
    method, and in particular whether you support this to go out for an IPP WG
    Last Call.

    Carl-Uno

    Carl-Uno Manros
    Principal Engineer - Xerox Architecture Center - Xerox Corporation
    701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
    Phone +1-310-333 8273, Fax +1-310-333 5514
    Email: manros@cp10.es.xerox.com

    -----Original Message-----
    From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com]
    Sent: Wednesday, September 20, 2000 9:37 AM
    To: ipp (E-mail)
    Subject: IPP> NOT - Updated 'ipp-get' Delivery Method for Event
    Notification po sted

    This was renamed from 'ipp-getw' at the meeting last week to 'ipp-get' and
    agreed to be the third RECOMMEND delivery method for IPP Notification. This
    method is a synthesis of Harry's server directed polling method and the
    earlier 'ipp-get' polling method. We also agreed at the meeting that for
    the moment we are not pursuing any additional Event Notification Delivery
    Methods. Send comments to the mailing list and/or discuss at today's
    telecon.

    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
    Time.
    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.

    The -rev is diffed with the old file name ipp-poll which had the older
    'ipp-get' method. The files are available at:

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



    This archive was generated by hypermail 2b29 : Wed Sep 20 2000 - 17:57:04 EDT