attachment-0001
<font size=2 face="sans-serif">Same here - device supports DNS-SD and
WS-Discovery and JPEG and PNG-Raster.</font>
<br>
<br><font size=2 face="sans-serif">-Nancy</font>
<br><font size=2 face="sans-serif">---------------------------------------------------</font>
<br><font size=2 face="sans-serif">Nancy Chen<br>
Principal Engineer<br>
Solutions and Technology<br>
Services & Solution Business - US<br>
Oki Data<br>
2000 Bishops Gate Blvd.<br>
Mt. Laurel, NJ 08054<br>
Phone: +1 (856) 222-7006</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Murdock, Joe"
<jmurdock@sharplabs.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: ipp-bounces@pwg.org</font>
<p><font size=1 face="sans-serif">08/23/2012 06:12 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"ipp@pwg.org" <ipp@pwg.org>,
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [IPP] IPP Everywhere and "The
Great Compromise"</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br><tt><font size=2>I agree with the proposed changes device supports
DNS-SD and WS-Discovery and JPEG and PNG-Raster.<br>
</font></tt>
<br><tt><font size=2>From: ipp-bounces@pwg.org [</font></tt><a href="mailto:ipp-bounces@pwg.org"><tt><font size=2>mailto:ipp-bounces@pwg.org</font></tt></a><tt><font size=2>]
On Behalf Of Michael Sweet<br>
Sent: Thursday, August 23, 2012 7:02 AM<br>
To: ipp@pwg.org<br>
Subject: Re: [IPP] IPP Everywhere and "The Great Compromise"<br>
</font></tt>
<br><tt><font size=2>After letting this sink in over the past couple days,
I have to pull my support for allowing a client to only support JPEG. Aside
from the quality issues, JPEG does not support multiple page content and
so does not satisfy the requirements set forth in the IPP Everywhere spec
and current charter. That leaves us with:<br>
</font></tt>
<br><tt><font size=2>1. Discovery:<br>
a. Printers MUST support both DNS-SD and WS-Discovery (adds WS-Discovery)<br>
b. Clients MUST support DNS-SD and/or WS-Discovery (Clients can choose
amongst the two required protocols)</font></tt>
<br>
<br><tt><font size=2>I humbly suggest that the <1000 lines of code (CUPS'
implementation is 830 lines for both read and write) needed to generate
PWG Raster is not an undue burden on clients to implement support for and
conform to IPP Everywhere.<br>
</font></tt>
<br><tt><font size=2>Please comment, and we will review this at the next
IPP conference call on September 10th.<br>
</font></tt>
<br>
<br><tt><font size=2>On Aug 20, 2012, at 9:42 PM, Michael Sweet <msweet@apple.com<</font></tt><a href=mailto:msweet@apple.com><tt><font size=2>mailto:msweet@apple.com</font></tt></a><tt><font size=2>>>
wrote:<br>
</font></tt>
<br>
<br><tt><font size=2>All,<br>
</font></tt>
<br><tt><font size=2>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:<br>
</font></tt>
<br><tt><font size=2>1. Discovery:<br>
</font></tt>
<br><tt><font size=2>a. Printers MUST support both DNS-SD and WS-Discovery
(adds WS-Discovery)<br>
b. Clients MUST support at least one of DNS-SD and WS-Discovery (Clients
can choose amongst the two required protocols)</font></tt>
<br>
<br><tt><font size=2>2. Document Formats:<br>
</font></tt>
<br><tt><font size=2>a. Printers MUST support both JPEG and PWG Raster
(no change)<br>
b. Clients MUST support at least one of JPEG and PWG Raster (relaxes conformance
- previously a Client had to support both)</font></tt>
<br>
<br><tt><font size=2>Please comment on the proposed changes.<br>
</font></tt>
<br><tt><font size=2>_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
</font></tt>
<br>
<br><tt><font size=2>--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner<</font></tt><a href=http://www.mailscanner.info/><tt><font size=2>http://www.mailscanner.info/</font></tt></a><tt><font size=2>>,
and is<br>
believed to be clean.<br>
_______________________________________________<br>
ipp mailing list<br>
ipp@pwg.org<</font></tt><a href=mailto:ipp@pwg.org><tt><font size=2>mailto:ipp@pwg.org</font></tt></a><tt><font size=2>><br>
</font></tt><a href=https://www.pwg.org/mailman/listinfo/ipp><tt><font size=2>https://www.pwg.org/mailman/listinfo/ipp</font></tt></a><tt><font size=2><br>
</font></tt>
<br><tt><font size=2>_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
</font></tt>
<br>
<br><tt><font size=2>--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner<</font></tt><a href=http://www.mailscanner.info/><tt><font size=2>http://www.mailscanner.info/</font></tt></a><tt><font size=2>>,
and is<br>
believed to be clean.<br>
</font></tt>
<br><tt><font size=2>--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br>
</font></tt>
<br>
<br><tt><font size=2>_______________________________________________<br>
ipp mailing list<br>
ipp@pwg.org<br>
</font></tt><a href=https://www.pwg.org/mailman/listinfo/ipp><tt><font size=2>https://www.pwg.org/mailman/listinfo/ipp</font></tt></a>
<br>
<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.