<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
In my opinion, it's too much of a bolt-on bit of functionality to
add it to the core spec. It also presumes a few pieces of static
infrastructure to be in place in order to function, and I'm not
comfortable with a distributed protocol doing that in the first
place.<br>
<br>
-- Justin<br>
<br>
On 05/17/2012 05:29 PM, Nat Sakimura wrote:
<blockquote
cite="mid:CABzCy2BM6cufbEFOv-qX0sCWyPLG9VVz2YsNBbStZ3BG0RifNg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
We have self-issued OP documented at <a moz-do-not-send="true"
href="https://bitbucket.org/openid/connect/issue/566/messages-standard-define-self-issued-op">https://bitbucket.org/openid/connect/issue/566/messages-standard-define-self-issued-op</a>
.
<div>
We have built the code that works. </div>
<div><br>
</div>
<div>We decided not to create Userinfo token, but decided to
include them in the id_token. </div>
<div>Registration overlay still have not reached the consensus. </div>
<div><br>
</div>
<div>Having said that, we should now consider where we are going
to put these in. </div>
<div>In Messages? </div>
<div>Or a separate spec? </div>
<div><br>
</div>
<div>Please discuss. </div>
<div>
<div><br>
</div>
-- <br>
Nat Sakimura (=nat)
<div>Chairman, OpenID Foundation<br>
<a moz-do-not-send="true" href="http://nat.sakimura.org/"
target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<br>
</body>
</html>