attachment-0001
Hi Glen,<br><br>I understand why you want to lower Printer implementation burden,<br>but your proposal defeats the essence of the "Great Compromise",<br>which is focused on support of IPP Everywhere by OS vendors (to<br>
achieve what the user thinks is "driver-less printing").<br><br>As you say, Printer firmware doesn't change often - but if it once <br>supports the two document formats and two discovery protocols it <br>will reliably interoperate w/ all IPP Everywhere Clients in the future.<br>
<br>Cheers,<br>- Ira<br><br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br>Temporary Cabin *** 2012 only *** 906-494-2523<br><div style="display:inline"></div><div style="display:inline">
</div><div style="display:inline"></div><div></div><div></div><div></div><div></div><br>
<br><br><div class="gmail_quote">On Tue, Aug 21, 2012 at 11:13 AM, Petrie, Glen <span dir="ltr"><<a href="mailto:glen.petrie@eitc.epson.com" target="_blank">glen.petrie@eitc.epson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="blue" style="word-wrap:break-word" lang="EN-US">
<div>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">Mike (all)<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">The change below pushes the burden to
the printer (at an increased cost to the printer) while the Client, a software
entity, has less burden. What is wrong with <u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">1. Discovery:<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"> a. Clients MUST support
DNS-SD and WS-Discovery <u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"> b. Printers MUST support either
DNS-SD or WS-Discovery and RECOMMENED to support both.<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">2. Document Formats:<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal" style="margin-left:27.0pt"><u></u><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><span>a.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman""> </span></font></span></span></font><u></u><font color="blue" face="Cambria"><span style="font-family:Cambria;color:blue">Clients
MUST support both JPEG and PWG Raster <u></u><u></u></span></font></p>
<p class="MsoNormal" style="margin-left:27.0pt"><u></u><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><span>b.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman""> </span></font></span></span></font><u></u><font color="blue" face="Cambria"><span style="font-family:Cambria;color:blue">Printers
MUST support either JPEG or PWG Raster and RECOMMENDED to support both.<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">This change to the printer requirements
could mean a faster time to market since printers are already support one of
the discoveries and documents formats but may not support both discoveries and
document formats. <u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">As was discussed in the meeting, if either
discovery or document format change in the future, the backward compatibility burden
would have to be on the Client to deal with legacy printers. There 'may'
be an issue of Client legacy but I content that is still easier to update
Clients rather than printer firmware. In the event of a Cloud Print
Service or a Print Manager; then, I would assume the "RECOMMEDED"
support of both would be implemented. <u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">Glen<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<div>
<div class="MsoNormal" style="text-align:center" align="center"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">
<hr size="2" width="100%" align="center">
</span></font></div>
<p class="MsoNormal"><b><font face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></font></b><font face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma"> <a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a>
[mailto:<a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a>] <b><span style="font-weight:bold">On Behalf Of </span></b>Michael
Sweet<br>
<b><span style="font-weight:bold">Sent:</span></b> Monday, August 20, 2012 6:42
PM</span></font></p><div class="im"><font face="Tahoma"><br>
<b><span style="font-weight:bold">To:</span></b> <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
<b><span style="font-weight:bold">Subject:</span></b> [IPP] IPP Everywhere and
"The Great Compromise"</font></div><u></u><u></u><p></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">All,<u></u><u></u></span></font></p><div><div class="h5">
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">We discussed the PWG Last Call comments received thus far at today's
IPP WG conference call. Two of the comments concerned the client
requirements to support DNS-SD for discovery and both PWG Raster and JPEG for
document formats. After over an hour of spirited debate, the following
"great compromise" was proposed to resolve the last call comments:<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">1. Discovery:<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"> a. Printers MUST support both DNS-SD and WS-Discovery
(adds WS-Discovery)<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"> b. Clients MUST support at least one of DNS-SD and
WS-Discovery (Clients can choose amongst the two required protocols)<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">2. Document Formats:<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"> a. Printers MUST support both JPEG and PWG Raster (no
change)<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"> b. Clients MUST support at least one of JPEG and PWG
Raster (relaxes conformance - previously a Client had to support both)<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">Please comment on the proposed changes.<u></u><u></u></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<div><span style="border-spacing:0px"><span style="text-align:-webkit-auto;word-spacing:0px">
<div>
<div style="word-wrap:break-word">
<p class="MsoNormal"><font color="black" face="Andale Mono" size="4"><span style="font-size:13.5pt;font-family:"Andale Mono"">_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<u></u><u></u></span></font></p>
</div>
</div>
</span>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</span></div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b><span style="font-weight:bold">MailScanner</span></b></a>, and is <br>
believed to be clean. <u></u><u></u></span></font></p>
</div></div></div><div><div class="h5">
<br>--
<br>This message has been scanned for viruses and
<br>dangerous content by
<a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is
<br>believed to be clean.
</div></div></div>
<br>_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br></blockquote></div><br>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.