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="">Smith,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 4, 2019, at 12:22 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</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="">Greetings,<div class=""><br class=""></div><div class="">Thanks to all who provided feedback on the 20190117 draft of IPP Authentication Methods. Since I received valuable non-editorial feedback in addition to editorial feedback on the draft from the PWG Last Call, I have produced a new revision that hopefully resolves all the issues and can be used in a second last call. The new draft is here:</div><div class=""><br class=""></div><div class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt" class="">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt</a> </div><div class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf" class="">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf</a> </div><div class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt" class="">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt</a> </div><div class=""> <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf" class="">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf</a> </div><div class=""><br class=""></div><div class="">I included the contents of my LCRC document in the "Change History" section. If those that submitted comments could review this draft offline and evaluate whether my changes have fixed their issues, I'd appreciate it.</div></div></div></blockquote></div><div class=""><br class=""></div>The -rev version is (as usual) a bit hard to follow, but I like the changes. We normally do the LCRC comments in a separate txt file, but I'm fine with it being in the changes section for now. Process/3.0 doesn't require a particular format or filename, just that all comments and their resolutions be listed for review.</div><div class=""><br class=""></div><div class="">Feedback:</div><div class=""><br class=""></div><div class="">One addition I'd like to see to see for the "requesting-user-name" method is a note that some Clients use a constant identity as a privacy defense (e.g., "mobile" from iOS Clients) when sending requests, so from a Printer's perspective this method is basically useless. In the context of GDPR, this falls under a need for explicit consent - a password challenge or Client UI requesting permission to provide the real user name is required. At Apple we decided to always hide the requesting user on iOS for basic privacy reasons, relying on authentication where such information is genuinely needed.</div><div class=""><br class=""></div><div class="">In the general client recommendations (section 14.2?), you say:</div><div class=""><br class=""></div><div class=""> Client security considerations (section 18.2) should also be followed.</div><div class=""><br class=""></div><div class="">Since we have a lowercase "should" here, perhaps reword this as:</div><div class=""><br class=""></div><div class=""> Also see section 18.2 for Client security considerations and recommendations.<br class=""><div class=""><br class=""></div><div class="">There is a similar statement in the general printer recommendation (section 14.4?), which should probably read "Also see section 18.4 for Printer security considerations and recommendations." (right now it says Client...)</div><div class=""><br class=""></div><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: "Andale Mono"; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal; border-spacing: 0px; -webkit-text-decorations-in-effect: none;"><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; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: 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></body></html>