attachment
<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Smith,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sorry, my confusion continues. Your new Authorization example may be valid, but it seems odd to me that someone would have an account in a printer but not have authority to print at all. Conditional authority, restricting use to certain times or restricting color, or quantity, etc. would be more realistic, but that is at the IPP level and does not appear to be addressed in this specification. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The title is Authentication Methods, and although I may have missed it, I do not think that it does much with authorization (at least not by the printer), which would occur after successful Authentication. Perhaps the Authorization use case should be put in the out of scope section?</p><p class=MsoNormal>Thanks, Bill W.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:ipp@pwg.org">Rizzo, Christopher via ipp</a><br><b>Sent: </b>Thursday, February 28, 2019 4:12 PM<br><b>To: </b><a href="mailto:smith.kennedy@hp.com">Kennedy, Smith (Wireless & Standards Architect)</a>; <a href="mailto:RYardumian@ciis.canon.com">Rick Yardumian</a><br><b>Cc: </b><a href="mailto:ipp@pwg.org">PWG IPP WG Reflector</a><br><b>Subject: </b>Re: [IPP] WG Last Call: IPP Authentication Methods</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This update looks good to me.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Chris<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>Christopher Rizzo<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>Xerox Corporation<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>GDG/Discovery/Advance Technology<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>26600 SW Parkway Ave.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>Wilsonville, OR 97070-9251<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>Phone: (585) 314-6936<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>Email: Christopher.Rizzo@xerox.com<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'>"The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs."<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'>-Maurice Wilkes, <i>Memoirs of a Computer Pioneer</i></span><o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>"Kennedy, Smith (Wireless & Standards Architect)" <smith.kennedy@hp.com><br><b>Date: </b>Thursday, February 28, 2019 at 12:36 PM<br><b>To: </b>Christopher Rizzo <Christopher.Rizzo@xerox.com>, Rick Yardumian <RYardumian@ciis.canon.com><br><b>Cc: </b>PWG Workgroup <ipp@pwg.org><br><b>Subject: </b>Re: [IPP] WG Last Call: IPP Authentication Methods<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Thanks for the feedback Chris! I also received this feedback from Canon's Rick Yardumian (CC'ed). In my LCRC draft, I've resolved this issue by rewriting 3.3.2 to more meaningfully describe an authorization failure. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Here's the rewrite. Any objections or suggestions?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal>Harry is also visiting Andy's office and wants to print from his laptop. He uses his laptop to discover available printers, and selects one listed. The printer is configured to limit access to only authorized users. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The printer challenges the laptop for authentication, and the laptop presents an authentication dialog to Harry. Harry has an account, and enters the account's username and password. The printer accepts these credentials, but that account is not authorized to access that printer. Harry's laptop shows a notification dialog expressing this to Harry. Harry clicks “OK” and looks for a pencil.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Smith<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Feb 28, 2019, at 12:33 PM, Rizzo, Christopher <<a href="mailto:Christopher.Rizzo@xerox.com">Christopher.Rizzo@xerox.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Just curious, but section 3.3 Exceptions of this document has sections 3.3.1 and 3.3.2 which are pretty much exact duplicates of each other, exception being Lisa vs. Harry. Was this intentional?<br><br>Thanks,<br>Chris<br><br><br>Christopher Rizzo<br>Xerox Corporation<br><br>GDG/Discovery/Advance Technology<br><br>26600 SW Parkway Ave.<br><br>Wilsonville, OR 97070-9251<br><br>Phone: (585) 314-6936<br><br><a href="mailto:Christopher.Rizzo@xerox.com">Email: Christopher.Rizzo@xerox.com</a><br><br>"The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs."<br>-Maurice Wilkes, Memoirs of a Computer Pioneer<br><br>On 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith (Wireless & Standards Architect)" <<a href="mailto:ipp-bounces@pwg.org">ipp-bounces@pwg.org</a> on behalf of <a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>> wrote:<br><br>Greetings,<br><br>This message begins the IPP workgroup Last Call of the IPP Authentication Methods best practice draft, available at:<br><br><a href="https://protect-us.mimecast.com/s/aaIsCmZ6o6hNO9opiQeQvF?domain=ftp.pwg.org">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt</a><br><a href="https://protect-us.mimecast.com/s/xDYACn5XpXTN8kZXiEolxV?domain=ftp.pwg.org">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf</a><br><a href="https://protect-us.mimecast.com/s/erESCo2KqKh3OQVDfWsoRJ?domain=ftp.pwg.org">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf</a><br><br>Please respond with any feedback or comments by doing a "reply all" to this message.<br><br>This last call will end on January 31, 2019 at 10pm PT.<br><br>Cheers,<br>Smith<br><br>/**<br>Smith Kennedy<br>HP Inc.<br>*/<br><br>_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br><a href="https://protect-us.mimecast.com/s/Ym5ZCpYK0Ki3Y709fkMtge?domain=pwg.org">https://www.pwg.org/mailman/listinfo/ipp</a><o:p></o:p></p></div></div></blockquote></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>