attachment
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Andale Mono";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you very much for your response, Mike. Please find my comments below with [Soma2].<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Michael Sweet [mailto:msweet@apple.com] <br><b>Sent:</b> Monday, March 17, 2014 10:31 PM<br><b>To:</b> Soma Meiyappan<br><b>Cc:</b> Peter Zehler; IPP@pwg.org<br><b>Subject:</b> Re: [IPP] IPP Scan - Is Push scanning mandatory?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(Apologies for the late reply; I am still working through a backlog of email...)<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Feb 19, 2014, at 4:22 AM, Soma Meiyappan <<a href="mailto:Soma.Meiyappan@conexant.com">Soma.Meiyappan@conexant.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>...</span><span style='color:#1F497D'> </span><o:p></o:p></p><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Soma] When US federal TCPA law talks about fax headers/cover-page for fax machines/senders, should it be interpreted as being applicable for images transmitted through tel: and fax: schemes only and not to mailto:, ipp:, etc…, which inherently involve digital formats with richer meta-data capabilities?</span><o:p></o:p></p></div></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>IANAL, but an application claiming to offer Internet Fax capabilities will likely be subject to the same regulations that traditional fax is subject to. Naturally this will depend on local laws and regulations, and certainly if the destination is an ipp: or ipps: URI then the job ticket/accounting information can be passed out-of-band rather than embedded in the delivered images.<o:p></o:p></p></div><div><p class=MsoNormal><br><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Soma2] Ok. It may be useful to add information related to headers in IPP FaxOut documents. But I can understand if as a standard, IPP does not want to talk about this as it is subject to local laws and regulation.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Document sent using these digital formats can identify the sender through a username that is embedded in the file (be it a PDF, TIFF or JPEG). </span><o:p></o:p></p></div></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Generally speaking, we (the PWG) do not like embedding job ticket/accounting information in the PDL.<o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Soma2] Sure. I was trying to imply that there are digital formats in which the originator’s (sender’s) information can be embedded within it as a meta-data instead of as a fax header as the law’s objective is for the receiver to identify the sender. But if the assumption that all FaxOut schemes will be subject to the same regulations as fax/tel is true, then this does not matter anyways.</span><br><br><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If the IPP FaxOut specification should be interpreted such that the same content (incl the header) should be sent to all destinations (irrespective of the destination scheme), then it makes the case for “push-scan” in IPP Scan stronger. </span><o:p></o:p></p></div></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>I don't think we can require push scan support, as the hardware requirements may preclude support on some printers (think: non-networked MFDs that support IPP USB and the various IPP services...) And more to the point, push scan can be simulated even by embedded/mobile devices that might be used to initiate a scan.<o:p></o:p></p></div><div><p class=MsoNormal><br><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Soma2] I am not implying that “Push scan” should be made mandatory. I agree that push scan can still be simulated by using an external client to “scan and send”. But as a standard, I would expect IPP-Scan to enable the OEMs to differentiate their in-machine’s capabilities with built-in ‘push scan’ functions that can be initiated through a standard client.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>... </span><o:p></o:p></p></div><p class=MsoNormal>*If* there is a use case for discovery of fax services that can deliver using a particular URI scheme, we could add a corresponding "Fax2" TXT key, however nobody has asked for it... (and FWIW, I would argue it would be more useful than the Scan2 key, since at least then you are discovering a delivery capability that cannot be easily reproduced in software...)<o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Soma] If the case for PushScan exists and if a device supports it, then I can see Scan2 (or Fax2) in TXT record being useful especially with the discovery features in Wifi-Direct/P2P and in a kiosk like environment where the IPP client may not have other network connectivity. </span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>WFDS has its own service descriptors and does not use Bonjour. At present, Bonjour is only used for Infrastructure Wi-Fi and wired networking, not P2P.<o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Soma2] Ok.<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span class=apple-style-span><span style='font-family:"Andale Mono","serif";color:black'>_________________________________________________________</span></span><span class=apple-style-span><span style='font-family:"Andale Mono","serif";color:black'><br></span></span><span class=apple-style-span><span style='font-family:"Andale Mono","serif";color:black'>Michael Sweet, Senior Printing System Engineer, PWG Chair</span></span><span class=apple-style-span><span style='font-family:"Andale Mono","serif";color:black'><o:p></o:p></span></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div></div>
<P>Conexant E-mail Firewall (Conexant.Com) made the following annotations<br/>---------------------------------------------------------------------<br/>********************** Legal Disclaimer **************************** <br/><br/>"This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you." <br/><br/>********************************************************************** <br/><br/>---------------------------------------------------------------------<br/>
</P></body></html>