I vote for #2.
Hitachi Koki Imaging Solutions
Hugo Parra wrote:
> Excellent advice. Does anybody have any good suggestions? ("Fred's least efficient mechanism for RPC" is a bit long and bitter). Plain "IPP Notification Protocol" would seem to imply that this is the "blessed" notification delivery method for IPP and I don't think we've crossed that bridge. Here are some to start with:
>> 1. IPP's HTTP-Based Notification Protocol
> 2. IPP Notification Protocol Over HTTP (this was suggested by Roy?)
> 3. IPP Notification Extensions (for those who think this is the same protocol as IPP)
> 4. IPP Notification Protocol
>> >>> "Manros, Carl-Uno B" <cmanros at cp10.es.xerox.com> 11/02/99 04:47PM >>>
>> -----Original Message-----
> From: Roy T. Fielding [mailto:fielding at kiwi.ICS.UCI.EDU]
> Sent: Sunday, October 31, 1999 12:57 PM
> To: discuss at apps.ietf.org> Subject: draft-ietf-ipp-not-http-delivery-00
>> I would really appreciate it if future revisions of this draft would not
> refer to itself as the HTTP notification protocol. Call it the IPP
> notification protocol over HTTP, or "Fred's least efficient mechanism
> for RPC', but please do not call it HTTP.
>> >A New Internet-Draft is available from the on-line Internet-Drafts
> >This draft is a work item of the Internet Printing Protocol Working Group
> >of the IETF.
> > Title : Internet Printing Protocol/1.1: HTTP-Based IPP
> > Notification Delivery Protocol
> > Author(s) : H. Parra
> > Filename : draft-ietf-ipp-not-http-delivery-00.txt
> > Pages : 12
> > Date : 26-Oct-99
> >The IPP notification specification [ipp-ntfy] requires the availability
> >of one or more delivery methods for dispatching notification reports to
> >interested parties. This document describes the semantics and syntax of
> >a protocol that a delivery method may use to deliver IPP notifications
> >using HTTP for a transport.
> >A URL for this Internet-Draft is: