attachment

<div dir="ltr"><div><div><div><div><div><div><div>Hi Paul,<br><br></div>As Mike pointed out, using IEEE 1284 Device ID to do PDL-stream tweaks in IPP Everywhere was<br></div>never a legitimate implementation.  Vendors who honored IEEE 1284 Device ID info over the much<br></div>more authoritative IPP Printer status attributes have broken implementations anyway.<br><br></div>I agree with Mike - delete all mention of IEEE 1284 Device ID from IPP Everywhere (with which it<br></div>is incompatible).<br><br></div>Cheers,<br></div>- Ira<br><br><div><div><br></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><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>Jan-April: 579 Park Place  Saline, MI  48176  734-944-0094<br>May-Dec: 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></div></div></div>
<br><div class="gmail_quote">On Tue, Apr 17, 2018 at 8:17 AM, Paul Tykodi <span dir="ltr"><<a href="mailto:ptykodi@tykodi.com" target="_blank">ptykodi@tykodi.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi Ira,<div><br></div><div>My thought is that some vendor developed IPP Everywhere implementations may tweak PDF or JPEG processing on the client (i.e. sender) side for certain 1284 device ID’s.</div><div><br></div><div>If we make retiring them a two step process, we probably would give any developers that have done this time to adjust their code.</div><div><br></div><div>I am Ok with removing them from IPP Everywhere but am just asking about best way to implement change so that developers have time to react.</div><div><br></div><div>Best Regards,</div><div><br></div><div>/Paul<br><br><div id="m_3416474829410571254AppleMailSignature">Sent from my iPhone</div><div><div class="h5"><div><br>On Apr 17, 2018, at 6:35 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div>Hi,<br><br></div>Paul - you can't submit a 1284 Device ID as a command in IPP - it's a declarative<br></div>property only.<br><br></div>Mike and Smith - certainly we should drop 1284 Device ID from IPP Everywhere,<br></div>which is about driverless printing.<br><br></div>Cheers,<br></div>- Ira<br><br></div><div class="gmail_extra"><br clear="all"><div><div class="m_3416474829410571254gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><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/<wbr>blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/<wbr>highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Jan-April: <a href="https://maps.google.com/?q=579+Park+Place+Saline,+MI+48176+734&entry=gmail&source=g">579 Park Place</a>  <a href="https://maps.google.com/?q=579+Park+Place+Saline,+MI+48176+734&entry=gmail&source=g">Saline, MI</a>  <a href="https://maps.google.com/?q=579+Park+Place+Saline,+MI+48176+734&entry=gmail&source=g">48176</a>  <a href="https://maps.google.com/?q=579+Park+Place+Saline,+MI+48176+734&entry=gmail&source=g">734</a>-944-0094<br>May-Dec: 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></div></div></div>
<br><div class="gmail_quote">On Tue, Apr 17, 2018 at 5:14 AM, Paul Tykodi <span dir="ltr"><<a href="mailto:ptykodi@tykodi.com" target="_blank">ptykodi@tykodi.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div class="m_3416474829410571254m_-6503420201089291166WordSection1"><p class="MsoNormal"><span style="color:#203864">Hi Mike,<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#203864"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#203864">Where I believe some vendors use them to send pre and post job processing device specific commands, I don’t believe we should fully retire support for the 1284 device ID’s at this time.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#203864"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#203864">Are you planning to make them an OPTIONAL requirement?<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#203864"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#203864">Thanks.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#203864"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#203864">Best Regards,<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#203864"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#203864">/Paul<u></u><u></u></span></p><div><p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">--</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Paul Tykodi<br>Principal Consultant<br>TCS - Tykodi Consulting Services LLC<br><br>Tel/Fax: 603-343-1820<br>Mobile:  603-866-0712<br>E-mail:  <a href="mailto:ptykodi@tykodi.com" target="_blank">ptykodi@tykodi.com</a></span><span style="font-size:10.0pt;font-family:"Courier New";color:#1f497d"><br></span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">WWW:  </span><span style="font-size:10.0pt;font-family:"Courier New";color:#1f497d"><a href="http://www.tykodi.com/" target="_blank"><span style="font-family:"Arial",sans-serif">http://www.tykodi.com</span></a></span><span style="color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#44546a">This e-mail reply and any attachments are confidential and may be privileged.<u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#44546a">If you are not the intended recipient, please notify Tykodi Consulting Services LLC <u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#44546a">immediately by replying to this message and destroying all copies of this message <u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#44546a">and any attachments. Thank you</span><u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b>From:</b> ipp <<a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a>> <b>On Behalf Of </b>Kennedy, Smith (Wireless & Standards Architec)<br><b>Sent:</b> Monday, April 16, 2018 10:38 PM<br><b>To:</b> Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>><br><b>Cc:</b> PWG IPP WG Reflector <<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a>><br><b>Subject:</b> Re: [IPP] RFC: Drop 1284 device ID requirements from IPP Everywhere 1.1<u></u><u></u></p></div></div><div><div class="m_3416474829410571254h5"><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I approve and second this!<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p><div><div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black">Smith<br><br>/**<br>    Smith Kennedy<br>    Wireless & Standards Architect - IPG-PPS<br>    Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF<br>    Chair, IEEE ISTO Printer Working Group<br>    HP Inc.<br>*/<br><br><u></u><u></u></span></p></div></div></div><div><p class="MsoNormal"><br><br><u></u><u></u></p><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">On Apr 16, 2018, at 7:46 PM, Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>> wrote:<u></u><u></u></p></div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">All,<br><br>As 1284 device IDs are only needed for printer driver selection, I'd like remove all of the 1284 device ID requirements from IPP Everywhere 1.1.<br><br>Thoughts?<br><br>______________________________<wbr>___________________________<br>Michael Sweet, Senior Printing System Engineer<br><br>______________________________<wbr>_________________<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/li<wbr>stinfo/ipp</a><u></u><u></u></p></div></div></blockquote></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div><br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/li<wbr>stinfo/ipp</a><br>
<br></blockquote></div><br></div>
</div></blockquote></div></div></div></div></blockquote></div><br></div>

Comments are owned by the poster. All other material is Copyright © 2001-2024 The Printer Working Group. All rights reserved. IPP Everywhere, the IPP Everywhere logo, and the PWG logo are trademarks of the IEEE-ISTO.
About the PWG · Privacy Policy · PWG Webmaster