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; -webkit-line-break: after-white-space;" class=""><div class="">Hi Ira,</div><div class=""><br class=""></div><div class="">My main concerns are that the "job-password" provided will prevent the Job from being stored when it is received, and that once the password is entered at the Printer, that password won't persist. That doesn't seem to match my expectations as to what the user would want. In the use case I'm thinking about, the Job is sent to be stored and is provided with a password, with the user expecting that it will be stored right away, and that each re-print of that saved job will require that job's password to be entered.</div><div class=""><br class=""></div><div class=""><div class="">It seems we could solve this using a combination of "document-password" if the "save-document-format"='application/pdf', or possibly using my pending "IPP Document Encryption" system. I would have thought that this combination would have been considered already since  both "job-password" and "job-save-disposition" are defined in the same PWG candidate standard. Language such as :</div><div class=""><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">If a job creation operation is received that includes both "job-password" and "job-save-disposition" where its "save-disposition" member is 'save-only', in this case the Job will NOT be placed in 'pending-held' state but will proceed to "processing" for becoming a "saved job", and the "job-password" will be expected upon each reprint.</div></div></blockquote><div class=""><br class=""></div><div class=""><div class="">From HP's perspective, the reprinting of saved jobs is not performed via IPP Client operations such as the deprecated Restart-Job or Reprocess-Job operation, but by user interactions at the Printer itself, for instance using a physical printer's control panel or web interface, or a print server's management interface.</div></div><div class=""><br class=""></div><div class=""><div class="">
Smith<br class=""><br class="">/**<br class="">    Smith Kennedy<br class="">    Wireless Architect - Client Software - IPG-PPS<br class="">    Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF<br class="">    Chair, IEEE ISTO Printer Working Group<br class="">    HP Inc.<br class="">*/<br class=""><br class=""><br class="">

</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jun 24, 2017, at 8:14 AM, 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=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Hi Smith,<br class=""><br class=""></div>This is an interesting question.<br class=""><br class=""></div>Since both Restart-Job and Reprocess-Job are <b class=""><i class="">deprecated</i></b>, I note that,<br class=""></div>with Resubmit-Job (which creates a *new* job from the saved/retained<br class=""></div>job), I would assume that an entirely new job-password would be sent.<br class=""><br class=""></div>That is, I don't believe it's appropriate or reasonable for the saved job<br class=""></div>to retain the old one-time-use job-password for the new job created by<br class=""></div><div class="">the Resubmit-Job operation.<br class=""><br class=""></div><div class="">Mike - WDYT?<br class=""><br class=""></div><div class="">Cheers,<br class=""></div><div class="">- Ira<br class=""><br class=""></div></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Ira McDonald (Musician / Software Architect)<br class="">Co-Chair - TCG Trusted Mobility Solutions WG<br 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="http://sites.google.com/site/blueroofmusic" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class=""><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" 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="">Jan-April: 579 Park Place  Saline, MI  48176  734-944-0094<br class="">May-Dec: 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>
<br class=""><div class="gmail_quote">On Fri, Jun 23, 2017 at 6:15 PM, Kennedy, Smith (Wireless Architect) <span dir="ltr" class=""><<a href="mailto:smith.kennedy@hp.com" target="_blank" class="">smith.kennedy@hp.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hi there,<div class=""><br class=""></div><div class="">Consider a scenario where a Printer receives a Create-Job operation with the following attributes:</div><div class=""><br class=""></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px" class=""><div style="font-family:monospace" class="">job-password="12345678"</div><div style="font-family:monospace" class="">job-password-encryption='none'</div><div style="font-family:monospace" class="">job-save-disposition=</div><div style="font-family:monospace" class="">{</div><div style="font-family:monospace" class=""><span class="m_-7466929062766381675Apple-tab-span" style="white-space:pre-wrap">  </span>save-disposition='save-only'</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px" class=""><div style="font-family:monospace" class=""><span class="m_-7466929062766381675Apple-tab-span" style="white-space:pre-wrap">       </span>save-info=</div><div style="font-family:monospace" class=""><span class="m_-7466929062766381675Apple-tab-span" style="white-space:pre-wrap">     </span>{</div><div style="font-family:monospace" class=""><span class="m_-7466929062766381675Apple-tab-span" style="white-space:pre-wrap">              </span>save-location="whatever"</div><div style="font-family:monospace" class=""><span class="m_-7466929062766381675Apple-tab-span" style="white-space:pre-wrap">             </span>save-document-format=<wbr class="">application/pdf</div><div style="font-family:monospace" class=""><span class="m_-7466929062766381675Apple-tab-span" style="white-space:pre-wrap">     </span>}</div><div style="font-family:monospace" class="">}</div></blockquote><div class=""><span class="m_-7466929062766381675Apple-tab-span" style="white-space:pre-wrap">                </span></div><div class="">What would one expect the printer to do:</div><div class=""><br class=""></div><div class="">1. Hold the Job in 'pending-held' state until the matching password was provided, then retain the Job as a Saved Job</div><div class="">2. Process the Job to retain the Job as a Saved Job per the definition in 5100.11 section 2.2, but then whenever it might be reprinted via user selection on the control panel, the user is prompted for the password</div><div class=""><br class=""></div><div class="">If the expectation is #1 then there seems to be no way currently in standard IPP to create a password protected Saved Job, which I believe to be a valid use case that IPP needs to support. This could be supported using my (pending) IPP Document Encryption whitepaper, but wondered if it was already supported.</div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""><div class="">Smith<br class=""><br class="">/**<br class="">    Smith Kennedy<br class="">    Wireless Architect - Client Software - IPG-PPS<br class="">    Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF<br class="">    Chair, IEEE ISTO Printer Working Group<br class="">    HP Inc.<br class="">*/<br class=""><br class=""><br class=""></div><br class=""></div></div><br class="">______________________________<wbr class="">_________________<br class="">
ipp mailing list<br class="">
<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank" class="">https://www.pwg.org/mailman/<wbr class="">listinfo/ipp</a><br class="">
<br class=""></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>