attachment
<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Smith,<div class=""><br class=""></div><div class="">Quick feedback:</div><div class=""><br class=""></div><div class="">- End initial sentence with "are to:" (add "to")?</div><div class="">- Item 1: "currently defined for IPP" is awkward<br class=""><div class="">- Add "and" at the end of item 1.</div><div class="">- Item 2: "Describe implementation considerations for authentication ..." (identification has already happened, you are describing the items that were identified during the development of the document)</div><div class="">- Item 2: "protocol technical concerns" should read "technical protocol concerns"</div><div class=""><br class=""></div><div class="">That would make it:</div><div class=""><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">3.5 Design Requirements</div></div><div class=""><div class=""><br class=""></div></div><div class=""><div class="">The design requirements for this IPP Authentication Methods Best Practice document are to:</div></div><div class=""><div class=""><br class=""></div></div><div class=""><div class="">1. Illustrate how each authentication method integrates into IPP interaction flows; and</div></div><div class=""><div class="">2. Describe implementation considerations for authentication in general, including factors that influence user experience and technical protocol concerns.</div></div></blockquote><div class=""><div class=""><br class=""><blockquote type="cite" class="">On Jul 1, 2019, at 3:20 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>> wrote:<br class=""><br class="">Greetings,<br class=""><br class="">From our LCRC review of IPP Authentication Methods, it was pointed out in the review that the document was lacking a "Design Requirements" subsection to section 3. We decided to post a draft here on the reflector, and once consensus was reached, to add that to the final draft to be used in the PWG Formal Vote of Approval.<br class=""><br class=""><br class="">3.5 Design Requirements<br class=""><br class="">The design requirements for this IPP Authentication Methods Best Practice document are:<br class=""><br class="">1. Illustrate how each authentication method currently defined for IPP integrates into IPP interaction flows;<br class="">2. Identify and describe points to be considered in implementing Client or Printer support for authentication in general, including factors that influence user experience as well as protocol technical concerns.<br class=""><br class=""><br class="">Thoughts?<br class=""><br class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> HP Inc.<br class="">*/<br class=""><br class="">_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">https://www.pwg.org/mailman/listinfo/ipp<br class=""></blockquote><br class=""><div class="">________________________<br class="">Michael Sweet<br class=""><br class=""><br class=""></div><br class=""></div></div></body></html>