attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Ira,<div class=""><br class=""></div><div class="">I support the move to Job Extensions for the reasons you provided below, and because I think it might be useful in a more general case.</div><div class=""><br class=""><div class="">
Smith<br class=""><br class=""><br class="">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Mar 6, 2019, at 2:50 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class=""><div class="">Hi,</div><div class=""><br class=""></div><div class="">I just read this entire thread carefully.</div><div class=""><br class=""></div><div class="">I agree with all of your joint conclusions (good work Smith and Mike),</div><div class="">*except* for "job-retain-until-xxx".</div><div class=""><br class=""></div><div class="">I consider the lack of "job-retain-until-xxx" an architectural mistake</div><div class="">in IPP/1.1. So I'd like it to be present in Job Extensions, so that</div><div class="">some version lower than IPP/2.2 (Enterprise) can reliably use it.</div><div class="">I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED</div><div class="">in IPP/2.1 and above.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">- Ira</div><div class=""><br class=""></div><div class=""><div class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Ira McDonald (Musician / Software Architect)<br class="">Co-Chair - TCG Trusted Mobility Solutions WG</div><div class="">Co-Chair - TCG Metadata Access Protocol SG<br class=""></div><div dir="ltr" class="">Chair - Linux Foundation Open Printing WG<br class="">Secretary - IEEE-ISTO Printer Working Group<br class="">Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br class="">IETF Designated Expert - IPP & Printer MIB<br class="">Blue Roof Music / High North Inc<br class=""><a style="color:rgb(51,51,255)" href="https://protect-us.mimecast.com/s/gV7KCKrBnBFWnRPJCMjvnA?domain=sites.google.com" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class=""><a style="color:rgb(102,0,204)" href="https://protect-us.mimecast.com/s/Ten6CL9DoDC91zVvSqqkRO?domain=sites.google.com" target="_blank" class="">http://sites.google.com/site/highnorthinc</a><br class="">mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a><br class="">PO Box 221 Grand Marais, MI 49839 906-494-2434<br class=""><br class=""><div style="display:inline" class=""></div><div style="display:inline" class=""></div><div style="display:inline" class=""></div><div class=""></div><div class=""></div><div class=""></div><div class=""></div></div></div></div></div></div></div></div></div></div><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">Smith,<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <<a href="mailto:ipp@pwg.org" target="_blank" class="">ipp@pwg.org</a>> wrote:</div><div class=""><div style="font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none" class="">...<br class=""><blockquote type="cite" style="font-family:Menlo-Regular" class=""><div class=""><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none" class=""> Also, I don't think we want a job-retain-until-time-default, since the value is an absolute dateTime value (unless we make -time an integer and add a -date version for dateTime?)</div></div></blockquote><div style="font-family:Menlo-Regular" class=""><br class=""></div><div style="font-family:Menlo-Regular" class="">Hmmm, how about just having "job-retain-until" (type2 keyword) and "job-retain-until-time" (integer) and not bother with "job-retain-until-date" (dateTime)?</div></div></div></blockquote><br class=""></div><div class="">Let's discuss this at the next concall - I can see a use for both (retain the job for 24 hours, retain the job until the next scheduled update), and a Client can calculate the number of seconds to a specific date/time, but there are still some vagaries due to submission delays and whether the IPP job ticket is used directly and immediately or if it gets "relayed" to the destination output device that is doing the retaining...</div><div class=""><br class=""></div><div class="">
<span class="gmail-m_2584918488612474498Apple-style-span" style="border-collapse: separate; font-family: "Andale Mono"; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; border-spacing: 0px;"><div style="overflow-wrap: break-word;" class=""><span class="gmail-m_2584918488612474498Apple-style-span" style="border-collapse: separate; font-family: "Andale Mono"; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; border-spacing: 0px;"><div style="overflow-wrap: break-word;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></div>_______________________________________________<br class="">
ipp mailing list<br class="">
<a href="mailto:ipp@pwg.org" target="_blank" class="">ipp@pwg.org</a><br class="">
<a href="https://protect-us.mimecast.com/s/rnF_CM8gpgI3ZnDlSJ31k5?domain=pwg.org" rel="noreferrer" target="_blank" class="">https://www.pwg.org/mailman/listinfo/ipp</a><br class="">
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>