attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi there,<div><br></div><div>I agree that Push should be optional.<div><br></div><div>Would we imagine that a client would filter on the Push URI schemes it supported? If so, Pete’s key with a value listing the supported schemes is preferable.</div><div><br></div><div>For advertising Push via DNS-SD, the design decision should come down to balancing the size of the TXT record against the desire to discover or filter this capability using purely the values in the TXT record vs. having to do a follow-up interrogation, which is generally expensive and not desirable.</div><div><br></div><div>Also, should IPP Scan include a way for the MFD to find Push scan destinations?</div><div><br></div><div><div>
<div style="color: rgb(0, 0, 0); font-family: Arial; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Smith<br><br>/**<br> Smith Kennedy<br> ATB Wireless Architect - PPS<br> Hewlett-Packard Co.<br>*/<br><br><br></div>
</div>
<br><div><div>On 2014-02-10, at 3:31 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><div dir="ltr"><div><div><div><div>Hi Mike and Pete,<br><br></div>What about a simple TXT record discovery attribute for Push capability that's boolean?<br></div>Since a bunch of URI schemes are conditionally mandatory anyway, that gets 90% of<br>
the discovery need.<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 Mon, Feb 10, 2014 at 3:29 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Pete,<div><br></div><div>I'm not sure it makes much sense to include the push schemes in the TXT record since you need to load the hardcopy to be scanned on a particular device - probably better to browse for _ipp._tcp,_scan and then do a Get-Printer-Attributes to get the values you are looking for, *if* you really wanted an application that could help a user find a MFD with push scan capabilities.</div>
<div><br></div><div>The more likely use case is that you browse to find the MFD you just loaded the hardcopy in, send an Identify-Printer to confirm, and then send a Get-Printer-Attributes to get the MFD capabilities (which might include whether push scan to an email address is possible, for example). For that you don't need the push schemes in the TXT record...</div>
<div><div class="h5"><div><br></div><div><br><div><div>On Feb 10, 2014, at 3:13 PM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" target="_blank">Peter.Zehler@xerox.com</a>> wrote:</div><br><blockquote type="cite">
<div link="blue" vlink="purple" lang="EN-US">
<div><p class="MsoNormal"><span style="color:#1f497d">Mike,<u></u><u></u></span></p><div><span style="color:#1f497d"> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="color:#1f497d">That works for me and for some internal requests. The additional request for having Push optional would be to include a discovery attribute to locate Scanners with push capability.
<u></u><u></u></span></p><div><span style="color:#1f497d"> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="color:#1f497d">What do you think about a comma separated list of push URL schemes and an empty list indicates a Pull only scanner?<u></u><u></u></span></p><div><span style="color:#1f497d"> </span><br class="webkit-block-placeholder"></div><div><span style="color:#1f497d"> </span><br class="webkit-block-placeholder"></div>
<div><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">Office: <a href="tel:%2B1%20%28585%29%20265-8755" value="+15852658755" target="_blank">+1 (585) 265-8755</a><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Mobile: <a href="tel:%2B1%20%28585%29%20329-9508" value="+15853299508" target="_blank">+1 (585) 329-9508</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:%2B1%20%28585%29%20265-7441" value="+15852657441" target="_blank">+1 (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><span style="color:#1f497d">
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#1f497d"><u></u><u></u></span></p>
</div><div><span style="color:#1f497d"> </span><br class="webkit-block-placeholder"></div>
<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>Michael Sweet<br>
<b>Sent:</b> Monday, February 10, 2014 3:07 PM<br>
<b>To:</b> Zehler, Peter<br>
<b>Cc:</b> <a href="mailto:IPP@pwg.org" target="_blank">IPP@pwg.org</a><br>
<b>Subject:</b> Re: [IPP] IPP Scan - Is Push scanning mandatory?<u></u><u></u></span></p>
</div>
</div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Pete,<u></u><u></u></p>
<div><p class="MsoNormal"><u></u> <u></u></p>
</div>
<div><p class="MsoNormal">I thought we were requiring pull scan and recommending push scan because low-end devices couldn't retry a push automatically. Any push-related attributes would be conditionally required if the service supports push. And any retry-related
attributes would be conditionally required for services that do output spooling.<u></u><u></u></p>
</div>
<div><p class="MsoNormal"><u></u> <u></u></p>
</div>
<div><p class="MsoNormal"><u></u> <u></u></p>
<div>
<div><p class="MsoNormal">On Feb 10, 2014, at 2:59 PM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com" target="_blank">Peter.Zehler@xerox.com</a>> wrote:<u></u><u></u></p>
</div><p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<div><p class="MsoNormal">All,<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">I have conflicting notes. I have some Push scan related attributes marked as conditionally mandatory while Pull and Push scan are listed as required.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">My opinion is that Push and Pull scanning are mandated and therefore the Push related attributes are also mandatory. For Push scanning the “http”, “https”, “ftp” and “ftps URI schemes MUST be supported.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Any objections?<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></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">Office: <a href="tel:%2B1%20%28585%29%20265-8755" value="+15852658755" target="_blank">+1 (585) 265-8755</a></span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Mobile: <a href="tel:%2B1%20%28585%29%20329-9508" value="+15853299508" target="_blank">+1 (585) 329-9508</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:%2B1%20%28585%29%20265-7441" value="+15852657441" target="_blank">+1 (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><span style="color:#1f497d">
</span><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p>
</div><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">_______________________________________________<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><u></u><u></u></span></p>
</div><div><span style="font-size:12.0pt;font-family:"Times New Roman","serif""> </span><br class="webkit-block-placeholder"></div>
<div>
<div><p class="MsoNormal"><span style="font-size:12pt;font-family:'Andale Mono',serif">_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<u></u><u></u></span></p>
</div>
</div><div><span style="font-size:12.0pt;font-family:"Times New Roman","serif""> </span><br class="webkit-block-placeholder"></div>
</div>
</div>
</div>
</blockquote></div><br><div>
<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"><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"><div style="word-wrap:break-word">
_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</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>
_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/ipp<br></blockquote></div><br></div></div></body></html>