Ira,
I think you are exaggerating the differences between this draft and previous
similar drafts. I don't think that any of the features in this draft are
revolutionary new, you could possibly argue that the exact combination of
features is different, but the individual features have certainly appeared
in previous drafts and should come as no surprise to those who have followed
our discussions over the last year and a half on notifications.
I hope that you only got carried away because we gave this draft a new file
name and started off with -00 again.
I cannot see us winning anything by putting this draft on a shelf for the
next few of weeks, or months, waiting for somebody to possibly raise
something to discuss later. Such discussion can equally well take place
now during the Last Call period.
Carl-Uno
> -----Original Message-----
> From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org]On Behalf Of McDonald,
> Ira
> Sent: Friday, September 22, 2000 12:22 PM
> To: 'Manros, Carl-Uno B'; IETF-IPP
> Cc: Don Fullman
> Subject: RE: IPP> ADM - IETF IPP WG Last Call for "Internet Printing
> Protocol (IPP) : The 'ippget' Event Notifications Delivery Method"
>
>
> Hi Carl-Uno,
>
> I'm in favor of the 'ippget' proposal but...
>
> This is unacceptable IETF working group process.
>
> Two weeks ago you declared both 'ippget' and 'snmpnotify'
> officially dead as IPP work items.
>
> Last week at the PWG meeting, a revised 'ippget' was
> discussed and favored by many for use in IPP Fax (aka
> QualDocs).
>
> In order to ENTER an IETF WG 'last call' the email
> record of the WG MUST show apparent 'rough concensus'.
> That's impossible - this current (significantly changed)
> proposal is new this week as an Internet-Draft.
>
> Please don't break the process without reason. There
> will certainly be very few implementations of 'ippget'
> at the IPP Bakeoff in a few weeks - the other two
> methods WILL be tested for interoperability at the
> IPP Bakeoff - when independent implementations of
> 'ippget' have had at least some testing is plenty
> soon enough to publish 'ippget' as a Proposed Std RFC.
>
> Cheers,
> - Ira McDonald
>
> -----Original Message-----
> From: Manros, Carl-Uno B [mailto:cmanros@cp10.es.xerox.com]
> Sent: Friday, September 22, 2000 11:30 AM
> To: IETF-IPP
> Cc: Don Fullman
> Subject: IPP> ADM - IETF IPP WG Last Call for "Internet Printing
> Protocol (IPP) : The 'ippget' Event Notifications Delivery Method"
>
>
> All,
>
> Although I haven't got a lot of feedback on my previous note about this
> document, I would like to get the IPP WG Last Call started on the
> 'ippget' Notification Delivery Method.
>
> The latest version of this document has been forwarded to the Internet
> Draft directory.
>
> Please note that this document was derived in part from earlier drafts
> on the 'ipp-get' and 'ipp-poll' methods.
>
> It is proposed to publish this as a Proposed Standard RFC, and it is
> proposed to be a RECOMMENDED delivery method, the same level as our
> previous two notification delivery methods.
>
> -----
>
> The Last Call notice follows:
>
> This is a formal request for final comments within the IETF IPP
> working group for one document. The document is:
>
> "Internet Printing Protocol (IPP): The 'ippget' Event Notifications
> Delivery Method"
>
> which is being proposed for forwarding on to the IESG for
> consideration as
> Standards Track document to complement the previous suite of IPP/1.0 and
> IPP/1.1 documents. This is a working group product, which has been
> thoroughly discussed since early 1999.
>
> Note that the "The 'ippget' Event Notifications Delivery Method" document
> is only one of several possible notification delivery documents on which
> the IPP WG has been working.
>
> The purpose of a working group Last Call is in the style of "speak now or
> forever hold your peace" in case there are fundamental objections
> which have
> not gotten previous or adequate discussion, or minor errors which need
> correction.
>
> Last Calls are for a minimum of 2 weeks. We will start the Last
> Call period
> today Friday September 22, 2000 and the period for working group comments
> will close on October 9, 2000 (US Pacific time reference).
>
> The document is:
>
> Title : Internet Printing Protocol (IPP): The 'ippget'
> Event
> Notifications Delivery Method
> Author(s) : R. Herriot, C. Kugler, H. Lewis
> Filename : draft-ietf-ipp-notify-get-00.txt
> Pages : 23
> Date : 19-Sep-00
>
> 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.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipp-notify-get-00.txt
>
> Internet-Drafts are also available by anonymous FTP. Login with
> the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-ietf-ipp-notify-get-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv@ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-ipp-notify-get-00.txt".
>
> ----
>
> Carl-Uno Manros
> Chair of IETF IPP WG
>
> 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
>
This archive was generated by hypermail 2b29 : Fri Sep 22 2000 - 21:32:19 EDT