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 Piotr,<div class="">
<div><br class=""><blockquote type="cite" class=""><div class="">On Oct 9, 2020, at 10:48 AM, Piotr Pawliczek <<a href="mailto:pawliczek@chromium.org" class="">pawliczek@chromium.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class="">Hi Smith,<div class=""><br class=""></div><div class="">Thank you very much for your help!</div><div class="">BTW, have you considered using an HTTP response header (see <a href="https://tools.ietf.org/html/rfc6750#section-3" class="">https://tools.ietf.org/html/rfc6750#section-3</a>) to communicate "server-uri" and "scope" to the client?</div><div class="">In this case, we would not have to expose Get-System-Attributes and Get-Printer-Attributes to everyone.</div></div></div></blockquote><div><br class=""></div><div>(I've attached a PDF rendering of the PlantUML sequence diagram used to produce figure 4.6 "Sequence diagram for the 'oauth' IPP Authentication Method" from page 19 of 5199.10 to this reply.)</div><div><br class=""></div>Hmmm, so you are suggesting that the response in edge 11 could provide the same values that are provided via the IPP "oauth-authorization-server-uri" and "oauth-authorization-scope" Printer Description attributes mentioned in the label for edge 13?</div><div><br class=""></div><div><br class=""></div><div></div></div></body></html>