<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
+1
<div><br>
<div>
<div>On Nov 3, 2013, at 9:48 AM, Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div>+1<br>
<br>
<div class="gmail_quote"><br>
<br>
Brian Campbell <<a href="mailto:bcampbell@pingidentity.com">bcampbell@pingidentity.com</a>> schrieb:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">
<div>Having Connect define and use the term “Authentication Request” provides a nice semantic distinction of what's going on beyond a plain old OAuth "Authorization Request" and, I think, makes it easier to talk about and explain.<br>
<br>
</div>
So yes, Authentication Request is section headers and in content where appropriate is what I'd prefer.<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Oct 30, 2013 at 8:26 PM, n-sakimura <span dir="ltr">
<<a href="mailto:n-sakimura@nri.co.jp" target="_blank">n-sakimura@nri.co.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>My suggestion was affected by one of the earlier reviewer. I thought that was quite reasonable.
<br>
To me, the definition of the each terms are as follows now: <br>
<br>
Authorization Request<br>
OAuth 2.0 Authroization Request<br>
<br>
Authentication Request<br>
Authorization Request used to obtain the Authentication Result through the use of OpenID Connect extension parameters and profiled scopes<br>
<br>
As a section header, I believe Authentication Request is more appropriate. <br>
<br>
Nat
<div>
<div class="h5"><br>
<br>
(2013/10/31 12:01), Mike Jones wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div>
<p class="MsoNormal">We define an Authentication Request as an OAuth 2.0 Authorization Request that requests that the End-User be authenticated by the Authorization Server. And we use the term Authentication Request in a few places. However, we use the term
“Authorization Request” in the section headings, because it’s the OAuth message used.</p>
<div> <br class="webkit-block-placeholder">
</div>
<p class="MsoNormal">More than one reviewer has suggested that we change these section headings from “Authorization Request” to “Authentication Request”. I agree that that’s a better semantic description. We’d just have to be careful to continue to say “Authentication
Request” when referring to the OAuth message.</p>
<div> <br class="webkit-block-placeholder">
</div>
<p class="MsoNormal">What do people prefer?</p>
<div> <br class="webkit-block-placeholder">
</div>
<p class="MsoNormal"> -- Mike</p>
<div> <br class="webkit-block-placeholder">
</div>
</div>
<br>
<fieldset></fieldset> <br>
</div>
</div>
<pre>_______________________________________________
Openid-specs-ab mailing list
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><span class="HOEnZb"><font color="#888888">
</font></span></pre>
<span class="HOEnZb"><font color="#888888"></font></span></blockquote>
<span class="HOEnZb"><font color="#888888"><br>
<br>
</font>
<pre cols="72"><font color="#888888">--
Nat Sakimura (<a href="mailto:n-sakimura@nri.co.jp" target="_blank">n-sakimura@nri.co.jp</a>)
Nomura Research Institute, Ltd.
<a href="tel:+81-3-6274-1412" target="_blank">Tel:+81-3-6274-1412</a> Fax:<a href="tel:%2B81-3-6274-1547" value="+81362741547" target="_blank">+81-3-6274-1547</a>
本メールに含まれる情報は機密情報であり、宛先に記載されている方のみに送信することを意図しております。意図された受取人以外の方によるこれらの情報の開示、複製、再配布や転送など一切の利用が禁止されています。誤って本メールを受信された場合は、申し訳ござӓ
6;|
14;せんが、送信者までお知らせいただき、受信されたメールを削除していただきますようお願い致します。
PLEASE READ:
The information contained in this e-mail is confidential and intended for the named recipient(s) only.
If you are not an intended recipient of this e-mail, you are hereby notified that any review, dissemination, distribution or duplication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete your copy from your system.
</font></pre>
</span></div>
<br>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<div style="margin-top: 2.5em; margin-bottom: 1em; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(0, 0, 0); ">
<br class="webkit-block-placeholder">
</div>
<pre class="k9mail"><hr><br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br></pre>
</blockquote>
</div>
</div>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
http://lists.openid.net/mailman/listinfo/openid-specs-ab<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>