attachment
<div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>I don't like "destination-uri-ready" at all. It doesn't scale. It doesn't add any<br></div>visible utility. It's actively a bad idea for IPP Everywhere as a pervasive<br>
</div>print protocol.<br><br></div>Cheers,<br></div>- Ira<br><br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<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><br><div style="display:inline">
</div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div>
<br><br><div class="gmail_quote">On Fri, Mar 21, 2014 at 10:52 AM, Soma Meiyappan <span dir="ltr"><<a href="mailto:Soma.Meiyappan@conexant.com" target="_blank">Soma.Meiyappan@conexant.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Hi Mike,<br>
<br>
destination-uri-ready (1 setOf collection) sounds like an useful attribute.<br>
<br>
It may be useful even for IPP and IPPS schemes (both in FaxOut and Scan) and we could add attributes for authentication (incl password digest/token type(s), MFD managed/user provided) as required. For every destination-uri in Job attributes, we could also specify optional fields for authentication (user, password, password-type). If we start dealing with authentication information here, I'd think that we should strongly recommend that only IPPS clients send authentication information.<br>
<br>
One may consider the security aspect of the user providing authentication information for a third party service to the MFD; but we can imagine those third party services generating OTP tokens for use here.<br>
<br>
Regards,<br>
Somasundaram.<div><div class="h5"><br>
<br>
<br>
<br>
-----Original Message-----<br>
<b>From: </b>Michael Sweet [<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>]<br>
<b>Sent: </b>Friday, March 21, 2014 06:40 AM Pacific Standard Time<br>
<b>To: </b>Soma Meiyappan<br>
<b>Cc: </b>Peter Zehler; <a href="mailto:IPP@pwg.org" target="_blank">IPP@pwg.org</a><br>
<b>Subject: </b>Re: [IPP] Prototype version of IPP Scan Service specification available<br>
<br>
Soma,
<div><br>
<div>
<div>On Mar 21, 2014, at 7:14 AM, Soma Meiyappan <<a href="mailto:Soma.Meiyappan@conexant.com" target="_blank">Soma.Meiyappan@conexant.com</a>> wrote:</div>
<blockquote type="cite">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="color:#1f497d">Hi Pete,</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Minor detail on the ‘http’/’https’ scheme for Scan2:</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">http is a transport for a number of application level protocols: One can use that to refer to standard PUT method or a RESTful method to store data on the destination. It would make sense that PUT is implied. Should the specification explicitly exclude RESTful methods from this and define another mechanism for identifying the supported destinations that are RESTful in nature?</span></p>
</div>
</div>
</blockquote>
<div><br></div>
We've never fully-specified how HTTP/HTTPS URIs are used, in SM or IPP.</div>
<div><br></div>
<div>It would be useful to say something here ("http" and "https" refer to destinations that support the HTTP PUT method using only standard HTTP headers), since POST requests will likely have specific header and/or message body requirements we aren't prepared to deal with. Conceptually new "http+post" and "https+post" URI schemes could be defined that allow for HTTP POST usage, although that would be a bit trickier.</div>
<div><br></div>
<div>How about adding a "destination-uri-ready (1setOf uri)" (or 1setOf collection to allow for a description/name along with the URI) attribute to list ready/configured destinations? Conceptually that would support typical workflow scenarios and allow the service to be configured for different HTTP protocol bindings. Specifying a URI that hasn't been pre-configured would revert to HTTP PUT.</div>
<div><br></div>
<div>Thoughts?</div>
<div><br></div>
<div>(FWIW, the same could be done for document-uri's - that would support forms and other predefined content and make print-by-reference more useful)</div>
<div><br></div>
<div><br></div>
<div>
<blockquote type="cite">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Regards,</span></p>
<p class="MsoNormal"><span style="color:#1f497d">Somasundaram.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </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""><a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a> [<a href="mailto:ipp-bounces@pwg.org" target="_blank">mailto:ipp-bounces@pwg.org</a>] <b>On Behalf Of</b> Zehler, Peter<br>
<b>Sent:</b> Monday, March 03, 2014 10:10 PM<br>
<b>To:</b> <a href="mailto:IPP@pwg.org" target="_blank">IPP@pwg.org</a><br>
<b>Subject:</b> [IPP] Prototype version of IPP Scan Service specification available</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">All,</p>
<p class="MsoNormal">I have posted the prototype version of “IPP Scan Service. Send any comments to the IPP mail list. We are looking for companies interested in prototyping this specification</p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.pdf</a> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.pdf" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.pdf</a> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.docx" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.docx</a> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.docx" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227.docx</a> </span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.pdf</a> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.pdf" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.pdf</a></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.docx" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.docx</a> </span> </p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.docx" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140227-rev.docx</a> </span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-family:"Impact","sans-serif";color:navy">Peter Zehler</span><span style="color:#1f497d"><br>
<br></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Xerox Research Center Webster<br></span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Email: <a href="mailto:Peter.Zehler@Xerox.com" target="_blank">Peter.Zehler@Xerox.com</a></span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Voice: <a href="tel:%28585%29%20265-8755" value="+15852658755" target="_blank">(585) 265-8755</a></span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">FAX: <a href="tel:%28585%29%20265-7441" value="+15852657441" target="_blank">(585) 265-7441</a></span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">US Mail: Peter Zehler</span><span style="color:#1f497d"><br></span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Xerox Corp.</span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">800 Phillips Rd.</span><span style="color:#1f497d"><br></span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">M/S 128-25E</span><span style="color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Webster NY, 14580-9701</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
</div>
<p>Conexant E-mail Firewall (<a href="http://Conexant.Com" target="_blank">Conexant.Com</a>) 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>
</div>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org" target="_blank">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></blockquote>
</div>
<br>
<div>
<div style="word-wrap:break-word"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;white-space:normal;font-family:'Andale Mono';word-spacing:0px">_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair</span></div>
</div>
<br></div>
</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></div>