I would like to clarify that "my" suggestion that Ira cites was echoed by
others, primarily in response to (my understanding of) Mike's indication
that he wanted to proceed with IPP-Everywhere only if there was significant
support from the industry (which is an excellent criterion). Putting it up
for vote both acts to engage more of the membership and "requires" that
negative responses include an explanation of why it is rejected. There
several generally acknowledged needs that IPP-Everywhere intends to address,
but also several different ideas about how they are best addressed.
Looking at the Mike's IPP-Everywhere Wiki page
(http://pwg-wiki.wikispaces.com/IPP+Everywhere), the main points are a
standard document format (or two) which should address much of the driver
issue, and a printer discovery method. These are critical issues, and are
also critical aspects of the Google CloudPrint initiative. But both by name
and by assumption, the solution is linked by many to IPP. And the Charter
makes this link very specific and very tight.
Although I think that there is little question but that IPP represents the
refinement of printing semantics and that these semantics should be
preserved in the next manifestation of printing interface, I do think that
there are differing views on whether this next manifestation should be an
add-on to IPP or a step beyond IPP. In favor of the former, the fact that
IPP is implemented in most networked printers suggests that an
IPP-Everywhere that is an incremental addition to IPP should be well
accepted by the industry as "good bang for the buck". But there is another
viewpoint that might maintain:
a. IPP has not been all that successful in terms of use, is not
supported by current Windows OS's, and is regarded (or perhaps disregarded)
by some business sorts in the industry as a wasted effort. There was even
the suggestion that there is a negative perception of IPP and that the "IPP"
term be replaced in IPP-Everywhere (although no agreement on replaced with
what.)
b. IPP uses a "transition" transport of HTTP over IP, which seemed
reasonable ten years ago, but is something of an anachronism in a world
going with a "web services" approach. And one would expect that the
Discovery, Eventing & Notification aspects that IPP-Everywhere needs will
come out of the Web Services world. Perhaps, when Google indicates that
IPP-Everywhere addresses much of what is needed in CloudPrint but has some
serious things missing, and when they ask for a CloudPrint use case using
IPP-Everywhere, they may be thinking of issues in this area.
So in considering the IPP-Everywhere charter, members must consider not just
whether IPP-Everywhere is a good and needed capability, I don't think that
there is much question about that, but whether the specific approach
specified in the charter is the optimum way to produce the optimum product.
And hopefully members will comment on this one way or the other since the
comments and actual participation in the specification and development of
IPP-Everywhere will be much more significant than an up or down vote.
Bill Wagner
-----Original Message-----
From: ipp-bounces at pwg.org [mailto:ipp-bounces at pwg.org] On Behalf Of Ira
McDonald
Sent: Wednesday, April 28, 2010 1:40 PM
To: Michael Sweet; Ira McDonald
Cc: ipp at pwg.org; George Liu
Subject: Re: [IPP] Stable draft of IPP Everywhere Project Charter (17
April2010)
Hi George,
Thanks for your good feedback.
Apparently, we're going to have to bend the PWG Process
a bit - e.g., to allow a Yes vote with editorial comments.
The PWG does NOT normally *vote* on individual project
charters - only on entire new working group charters.
But Bill Wagner suggested in the PWG Steering Committee
that we make this exception in order to get wider visibility for
the IPP Everywhere project.
Note that IPP/2.0 is simply IPP/1.1 with *correct* handling
of errors and exceptions (as already specified in IPP/1.1),
so I think it's a reasonable basis for IPP Everywhere.
Also, although IPP Everywhere supports the goal of printing
with generic (PDL-based) printer drivers, it's NOT an actual
requirement - I'm not sure about adding this to the charter,
rather than the *future* IPP Everywhere Requirements spec.
Mike - remember that "Yes with comments" should be allowed
in your posted PWG Formal Vote announcement.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
winter:
579 Park Place Saline, MI 48176
734-944-0094
summer:
PO Box 221 Grand Marais, MI 49839
906-494-2434
On Tue, Apr 27, 2010 at 8:39 PM, Michael Sweet <msweet at apple.com> wrote:
> On Apr 27, 2010, at 5:22 PM, George Liu wrote:
>> Michael,
>>>> Thanks for the quick feedback.
>>>> I studied the Charter document. From the problem statement, it seems
>> that the ultimate goal is to develop a comprehensive solution that can
>> eliminate printer drivers.
>>>> If my understanding is correct, I feel the "goal of IPP Everywhere"
>> paragraph is not emphasizing the objective of "eliminating printer
>> drivers" enough.
>> Fair enough, and good feedback that can be applied to the final version of
the charter.
>>> Also I feel setting an objective of " Use IPP/2.0 conformance level as
>> basis of IPP Everywhere." is too strict. No use case has been developed
>> for IPP Everywhere, it might be a bit earlier to decide on the technical
>> details.
>> Given that this will be a project for the IPP working group and that
IPP/2.0 is the current version of IPP approved by the PWG, I don't think it
is a stretch to make IPP/2.0 the basis of "IPP Everywhere".
>> That said, there have also been discussions of mapping any new stuff we
come up with to the PWG semantic model, which will allow it to be used with
other protocol bindings as well.
>>>>> Thanks for your attention.
>> George
>>>>>> -----Original Message-----
>> From: Michael Sweet [mailto:msweet at apple.com]
>> Sent: Tuesday, April 27, 2010 3:46 PM
>> To: George Liu
>> Cc: William Wagner; ipp at pwg.org>> Subject: Re: [IPP] Stable draft of IPP Everywhere Project Charter (17
>> April2010)
>>>> On Apr 27, 2010, at 3:33 PM, George Liu wrote:
>>>> IPP Everywhere (wd-ippeve10-yyyymmdd) - defines ... one IPP
>> Everywhere
>>> conformance level, based on the IPP/2.0 conformance level defined in
>> PWG
>>> IPP Version 2.0 Second Edition
>>>>>> Does it mean a IPP Everywhere complaint software/printer has to be IPP
>>> 2.0 or 2.1 or 2.2 compliant?
>>>> Since we haven't even started the charter vote for IPP Everywhere yet
>> (hoping to get that out today, we'll see...) it is impossible to answer
>> that authoritatively, however I have always pitched IPP Everywhere as
>> IPP/2.0+ (that is, 2.0 or higher).
>>>>>> STD-2 Prototype working draft of IPP Everywhere - Q2 2011
>>> Has any company committed to the development of IPP Everywhere
>>> prototype?
>>>> See above. I have received positive feedback from several vendors
>> already, so I think it is a safe bet that we'll have at least a few
>> prototypes to play with. Also, CUPS already implements everything that
>> has been discussed for IPP Everywhere thus far...
>>>>>>>>>>> Thanks
>>> George
>>>>>> -----Original Message-----
>>> From: ipp-bounces at pwg.org [mailto:ipp-bounces at pwg.org] On Behalf Of
>>> Michael Sweet
>>> Sent: Friday, April 23, 2010 11:26 AM
>>> To: William Wagner
>>> Cc: ipp at pwg.org>>> Subject: Re: [IPP] Stable draft of IPP Everywhere Project Charter (17
>>> April2010)
>>>>>> On Apr 23, 2010, at 10:55 AM, William Wagner wrote:
>>>> Sorry I missed the IPP call and did not bring this up at the Steering
>>>> committee call. What is the status of this charter? Is it going to be
>>> put up
>>>> for PWG vote?
>>>>>> Yes, Ira posted a "final draft" and I am in the process of getting
>> that
>>> email out... If not today, Monday...
>>>>>>>>>>> Thanks,
>>>>>>>> Bill Wagner
>>>>>>>> -----Original Message-----
>>>> From: ipp-bounces at pwg.org [mailto:ipp-bounces at pwg.org] On Behalf Of
>>> Ira
>>>> McDonald
>>>> Sent: Saturday, April 17, 2010 1:37 PM
>>>> To: ipp at pwg.org; Michael R Sweet; Ira McDonald
>>>> Subject: [IPP] Stable draft of IPP Everywhere Project Charter (17
>>> April
>>>> 2010)
>>>>>>>> Hi,
>>>>>>>> [For discussion during IPP WG meeting on Monday 19 April]
>>>>>>>>>>>> In preparation for PWG Formal Vote, I have just posted a Stable draft
>>> of the
>>>> IPP Everywhere Project Charter (4th version) at:
>>>>>>>>>>ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20100417.pdf>>> /
>>>> doc
>>>> - clean copy with line numbers
>>>>>>>>>>>>>ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20100417-rev.p>>> df
>>>> /doc
>>>> - redline copy with line numbers
>>>>>>>> Only changes are status to Stable and corrected several typos.
>>>>>>>> Cheers,
>>>> - Ira (IPP co-editor)
>>>>>>>> Ira McDonald (Musician / Software Architect)
>>>> Chair - Linux Foundation Open Printing WG
>>>> Co-Chair - TCG Hardcopy WG
>>>> IETF Designated Expert - IPP & Printer MIB
>>>> Blue Roof Music/High North Inc
>>>>http://sites.google.com/site/blueroofmusic>>>>http://sites.google.com/site/highnorthinc>>>> mailto:blueroofmusic at gmail.com>>>> winter:
>>>> 579 Park Place Saline, MI 48176
>>>> 734-944-0094
>>>> summer:
>>>> PO Box 221 Grand Marais, MI 49839
>>>> 906-494-2434
>>>>>>>> --
>>>> This message has been scanned for viruses and
>>>> dangerous content by MailScanner, and is
>>>> believed to be clean.
>>>>>>>> _______________________________________________
>>>> ipp mailing list
>>>>ipp at pwg.org>>>>https://www.pwg.org/mailman/listinfo/ipp>>>>>>>>>>>> ________________________________________________________________________
>>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>>>>>>>>>>>>>>> --
>>> This message has been scanned for viruses and
>>> dangerous content by MailScanner, and is
>>> believed to be clean.
>>>>>> _______________________________________________
>>> ipp mailing list
>>>ipp at pwg.org>>>https://www.pwg.org/mailman/listinfo/ipp>>>> ________________________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>>>>>>> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
ipp mailing list
ipp at pwg.orghttps://www.pwg.org/mailman/listinfo/ipp
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.