attachment
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Smith/Ira,<div><br></div><div>If we *do* add a ‘ipp-everywhere-1.1’ value, what will it mean? It’s not like the conformance requirements are getting higher...<br><br><div id="AppleMailSignature">Sent from my iPhone</div><div><br>On Aug 24, 2018, at 1:23 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>Hi,</div><div><br></div><div>I agree with all of Smith's recommendations.</div><div><br></div><div>I agree that we should leave out "job-password-repertoire" for now in IPP EW v1.1</div><div>(and probably forever, because I'm not comfortable with its usefulness for Clients).</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div><div><div dir="ltr" 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></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Aug 24, 2018 at 12:59 PM Kennedy, Smith (Wireless & Standards Architect) <<a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><br>
<div><br><blockquote type="cite"><div>On Aug 24, 2018, at 8:06 AM, Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>> wrote:</div><br class="m_-1709307454529954644Apple-interchange-newline"><div>
<div>All,<br>
<br>
I have posted an updated prototype draft of the IPP Everywhere v1.1 specification to:<br>
<br>
<a href="https://protect-us.mimecast.com/s/VXaWCG6xjxhJJxPWSkdlrE?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve11-20180824.docx</a><br>
<a href="https://protect-us.mimecast.com/s/_B6iCJ6AmAh88G2pUOOpmj?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve11-20180824.pdf</a><br>
<a href="https://protect-us.mimecast.com/s/XOcsCKrBnBFqqgY8coF33X?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve11-20180824-rev.pdf</a><br>
<br>
As noted in a prior email, we have a few outstanding issues to discuss:<br>
<br>
- Should we add recommended attributes?</div></div></blockquote><div><br></div>In general, yes.</div><div><br><blockquote type="cite"><div><div> "job-password-repertoire"</div></div></blockquote><div><br></div>I'd vote "No" to this one since we might be revisiting job passwords in JPS2v2.</div><div><br><blockquote type="cite"><div><div>, "jpeg-features-supported", "jpeg-k-octets-supported", "jpeg-x-dimension-supported", "jpeg-y-dimension-supported", "pdf-features-supported", "pdf-k-octets-supported", and "pdf-versions-supported"<br></div></div></blockquote><div><br></div>I'd vote "Yes" to all of these.</div><div><br><blockquote type="cite"><div><div>
- Should we add an 'ipp-everywhere-1.1' value for "ipp-features-supported"?<br></div></div></blockquote><div><br></div>I'd vote "Yes".<br><br><blockquote type="cite"><div><div>
- Should we address/update paid/managed printing (use of Get-User-Printer-Attributes, attributes/values needed for paid/managed printing)<br></div></div></blockquote><div><br></div>I'd vote "Yes" for these updates too.</div><div><br><blockquote type="cite"><div><div>
<br>
_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
<a href="https://protect-us.mimecast.com/s/F72kCL9DoDCPPxgNHKIxl7?domain=pwg.org" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</div>
</div></blockquote></div><br></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" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div>
</div></blockquote></div></body></html>