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 Mike,<div class=""><br class=""></div><div class="">Responding below - feel free to reserve your responses until the session tomorrow.</div><div class=""><br class=""></div><div class="">Smith</div><div class=""><br class="">
<div><br class=""><blockquote type="cite" class=""><div class="">On Feb 6, 2018, at 7:27 AM, Michael Sweet <<a href="mailto:msweet@apple.com" class="">msweet@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Smith,<div class=""><br class=""></div><div class="">Thanks for this, I will update the F2F slide accordingly...</div><div class=""><br class=""></div><div class="">FWIW, the current text still adds the save password to job-save-disposition which has the unfortunate security implication of exposing the password as part of the job ticket.</div></div></div></div></blockquote><div><br class=""></div><div>Details like this are still difficult for me to follow. I'm working on writing an "IPP Attribute Design Principles and Design Patterns" document now (I've said I wanted to do this for a couple of years), to try to organize and grow my understanding in this area, and to document it for posterity because the implications of selecting an attribute's group is unfortunately quite obscure and very nuanced.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""> I also think we still need to better define the use cases and flow of information - not only for definition of the attribute(s) but for the security considerations.</div></div></div></div></blockquote><div><br class=""></div><div>Perhaps those can come out in the discussion, at least a more detailed list of aspects you feel need to be covered but aren't currently.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""> Finally, I think our discussions on encrypted documents may overlap with this one... :/</div></div></div></div></blockquote><div><br class=""></div>I totally agree, and I have an updated draft of that waiting to be posted. I will just post it and if we end up looking at use cases from that tomorrow then I'm fine with that. Originally I was thinking that this might be a stepping stone to IPP Document Encryption, which could likely solve both needs.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Feb 5, 2018, at 7:13 PM, Kennedy, Smith (Wireless & Standards Architec) <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Greetings,<div class=""><br class=""></div><div class="">I have just posted an updated draft of IPP Job Save Password. It is available here:</div><div class=""><br class=""></div><div class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205.pdf" class="">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205.pdf</a> <br class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205.odt" class="">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205.odt</a></div><div class=""><div class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205-rev.pdf" class="">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205-rev.pdf</a> </div><div class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205-rev.odt" class="">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-savepassword-20180205-rev.odt</a> </div></div><div class=""><br class=""></div><div class="">Although I think that the changes I have made to produce this new draft have resolved some of the points of feedback from the last review on Dec. 14, 2017, these changes may still not have resolved these issues. Here are the minutes from the last meeting:</div><div class=""><br class=""></div><div class=""><ul class="MailOutline"><li class="">Comments from IPP mailing list:</li><ul class=""><li class="">Section 1: some mention of job-password being a Job Template attribute, but it is an operation attribute (which is correctly noted in subsequent sections</li><li class="">Section 4.2: Any password attribute needs to be protected, so these should be operation attributes and not Job Template...</li><li class="">Section 6: Will obviously need a lot of discussion of how to protect and handle the passwords.</li><li class="">Overall I'm still not sure about the use case for this, or how it would all work together. Is this an extension of "job-save-disposition", where the password would be used for the saved document? If so,I'd recommend that the attributes be called "job-save-password[-xxx]" to make that clearer, and add some discussion of that.</li><li class="">Also, how does a Client re-print the saved job? Resubmit-Job with "document-password"?</li></ul><li class="">Maybe we need to refactor this: "job-save-accesses (1setOf collection)" attribute to provide credentials for saving to a URI like we do for document-access (INFRA) and destination-accesses (FaxOut).</li><ul class=""><li class="">Don't specify an IPP way to do the "allow another user to reprint the saved content", e.g. Smith saves to network storage and then grants access to Bob through an out-of-band interface</li></ul><li class="">Encryption isn't a requirement, but access control *is*</li><li class="">Two use cases for save + reprint:</li><ul class=""><li class="">Using an IPP client to look at saved jobs and resubmit through IPP</li><li class="">Reprint through printer console (most common scenario for HP)</li><li class="">Reprint user may or may not be the person that submitted the original job</li></ul></ul></div><div class=""><br class=""></div><div class="">Please review the draft and come to discuss this in the session on Wednesday afternoon at the February 2018 vF2F.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""><div class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> Wireless & Standards Architect - 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="">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" class="">https://www.pwg.org/mailman/listinfo/ipp</a><br class=""></div></blockquote></div><br class=""><div class="">
<span class="Apple-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; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-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; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></div></div></div></div></blockquote></div><br class=""></div></body></html>