[IPP] WG Last Call: IPP Authentication Methods

[IPP] WG Last Call: IPP Authentication Methods

Kennedy, Smith (Wireless & Standards Architect) smith.kennedy at hp.com
Thu Feb 28 20:35:23 UTC 2019


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.

Here's the rewrite. Any objections or suggestions?

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.

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.

Smith



> On Feb 28, 2019, at 12:33 PM, Rizzo, Christopher <Christopher.Rizzo at xerox.com> wrote:
> 
> 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?
> 
> Thanks,
> Chris
> 
> 
> Christopher Rizzo
> Xerox Corporation
> 
> GDG/Discovery/Advance Technology
> 
> 26600 SW Parkway Ave.
> 
> Wilsonville, OR 97070-9251
> 
> Phone: (585) 314-6936
> 
> Email: Christopher.Rizzo at xerox.com
> 
> "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."
> -Maurice Wilkes, Memoirs of a Computer Pioneer
> 
> On 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith (Wireless & Standards Architect)" <ipp-bounces at pwg.org on behalf of smith.kennedy at hp.com> wrote:
> 
> Greetings,
> 
> This message begins the IPP workgroup Last Call of the IPP Authentication Methods best practice draft, available at:
> 
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt <https://protect-us.mimecast.com/s/aaIsCmZ6o6hNO9opiQeQvF?domain=ftp.pwg.org>
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf <https://protect-us.mimecast.com/s/xDYACn5XpXTN8kZXiEolxV?domain=ftp.pwg.org>
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf <https://protect-us.mimecast.com/s/erESCo2KqKh3OQVDfWsoRJ?domain=ftp.pwg.org>
> 
> Please respond with any feedback or comments by doing a "reply all" to this message.
> 
> This last call will end on January 31, 2019 at 10pm PT.
> 
> Cheers,
> Smith
> 
> /**
> Smith Kennedy
> HP Inc.
> */
> 
> _______________________________________________
> ipp mailing list
> ipp at pwg.org
> https://www.pwg.org/mailman/listinfo/ipp <https://protect-us.mimecast.com/s/Ym5ZCpYK0Ki3Y709fkMtge?domain=pwg.org>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190228/ebb6cd4c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190228/ebb6cd4c/attachment.sig>


More information about the ipp mailing list