attachment
<div dir="ltr"><div><div><div><div><div><div>Hi Mike,<br><br></div>I also want to hear Pete's definition of constrained network clients.<br><br></div>In TCG work on mobile devices, we are careful to accomodate very low-end<br>
</div>"feature phones" (under $100 street price) that dominate the emerging countries<br></div>markets. These devices definitely do *not* have 8GB, high-speed CPUs, or<br></div><div>large batteries.<br></div><div>
<br></div><div>Radio usage controls battery life. Acting as a pull and forward agent for large<br>files is a seriously poor idea for very low-end phones.<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 Tue, Feb 11, 2014 at 11:49 AM, 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>Please provide your definition of a constrained network scan client with minimal local storage.</div><div><div class="h5"><div><br></div><div><br></div><div><div>
<div>On Feb 11, 2014, at 11:38 AM, 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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">All,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The use case of the constrained client with minimal local storage should be accommodated. However the use case important to Xerox is where the client must
have the scanner deliver the scanned documents directly to the destination. (e.g., scanning a contract and delivering is securely to the destination.) The ability to discover scanners that support push without interrogating all the scanners in an enterprise
environment is needed. We eliminated seven of the text records from the discovery message. This leaves 4 mandatory, 2 conditional, and 2 optional. Adding this one should not be an undue burden. I can live with a Boolean but would prefer a list of schemes.
A list fully populated with the defined values would be “http,https,ftp,ftps,smb,ipp,ipps,mailto” which probably comes down to about 45 bytes for the text record.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Pete<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Impact","sans-serif";color:navy">Peter Zehler</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";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="font-size:11.0pt;font-family:"Calibri","sans-serif";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="font-size:11.0pt;font-family:"Calibri","sans-serif";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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">US Mail: Peter Zehler</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Xerox Corp.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">800 Phillips Rd.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">M/S 128-25E</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Webster NY, 14580-9701</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
</span><span style="color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><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""> Ira McDonald [<a href="mailto:blueroofmusic@gmail.com" target="_blank">mailto:blueroofmusic@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, February 11, 2014 10:55 AM<br>
<b>To:</b> Michael Sweet; Ira McDonald<br>
<b>Cc:</b> Zehler, Peter; <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><p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<div><p class="MsoNormal" style="margin-bottom:12.0pt">Hi Mike,<u></u><u></u></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">Crossed wires?<u></u><u></u></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">The mobile client may have very limited local storage and therefore want<br>
the MFD to push a large scan output file directly to a network server. That's<br>
the use case for the boolean in the TXT record (at least I thought that was<br>
what Smith and Pete were concerned about).<u></u><u></u></p>
</div><p class="MsoNormal">Cheers,<u></u><u></u></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">- Ira<u></u><u></u></p>
</div>
<div><p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div><p class="MsoNormal" style="margin-bottom:12.0pt">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 href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style="color:#3333ff">http://sites.google.com/site/blueroofmusic</span></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style="color:#6600cc">http://sites.google.com/site/highnorthinc</span></a><br>
mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 <a href="tel:734-944-0094" value="+17349440094" target="_blank">734-944-0094</a><br>
Summer PO Box 221 Grand Marais, MI 49839 <a href="tel:906-494-2434" value="+19064942434" target="_blank">906-494-2434</a><u></u><u></u></p>
</div>
</div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div><p class="MsoNormal">On Tue, Feb 11, 2014 at 10:13 AM, Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>> wrote:<u></u><u></u></p>
<div><p class="MsoNormal">Ira,<u></u><u></u></p>
<div><p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div><p class="MsoNormal">On Feb 10, 2014, at 5:31 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<div><p class="MsoNormal" style="margin-bottom:12.0pt">Hi Mike and Pete,<u></u><u></u></p>
</div><p class="MsoNormal">What about a simple TXT record discovery attribute for Push capability that's boolean?<u></u><u></u></p>
</div><p class="MsoNormal">Since a bunch of URI schemes are conditionally mandatory anyway, that gets 90% of<br>
the discovery need.<u></u><u></u></p>
</div>
</div>
</div>
</blockquote>
<div><p class="MsoNormal"><u></u> <u></u></p>
</div>
</div><p class="MsoNormal">What would be the use case?<u></u><u></u></p>
</div>
<div><p class="MsoNormal"><u></u> <u></u></p>
</div>
<div><p class="MsoNormal">It's one thing to need to find a color printer - you can't use software to print color on a B&W printers - but for scan if the MFD doesn't support push, the (mobile) client certainly *can* do it...<u></u><u></u></p>
</div>
<div>
<div><p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div><p class="MsoNormal"><span style="font-family:"Andale Mono"">_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<u></u><u></u></span></p>
</div>
</div><p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div><p class="MsoNormal"><u></u> <u></u></p>
</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></blockquote></div><br></div>