<html><head></head><body bgcolor="#FFFFFF"><div>No. That is a vanity string that shows it is a self issued provider. </div><div>It could very well be urn:OpenID:optype:selfissued or something. <br><br>=nat via iPhone</div>
<div><br>On 2012/05/19, at 1:20, Justin Richer <<a href="mailto:jricher@mitre.org">jricher@mitre.org</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
  
  
    <br>
    <span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> </span>
    <blockquote cite="mid:4E1F6AAD24975D4BA5B16804296739436650DBF7@TK5EX14MBXC284.redmond.corp.microsoft.com" type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">Responding
            to Justin’s point about static infrastructure, I believe
            that the way we’re going to specify it will require no
            static infrastructure.  Actually, it make is the protocol *<b>more</b>*
            distributed, as it removes the dependence upon third party
            IdPs.</span></p>
      </div>
    </blockquote>
    Doesn't it require <a href="http://selfissued.me">selfissued.me</a> to be there to answer for all of
    these self-issued pocket IdPs in terms of discovery? That's the
    functionality that I understood from the meeting at Yahoo.<br>
    <br>
     -- Justin<b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"><br>
        <br>
        From:</span></b><br>
    <br>
     <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>
    [<a class="moz-txt-link-freetext" href="mailto:openid-specs-ab-bounces@lists.openid.net">mailto:openid-specs-ab-bounces@lists.openid.net</a>]
    <b>On Behalf Of </b>Justin Richer<br>
    <blockquote cite="mid:4E1F6AAD24975D4BA5B16804296739436650DBF7@TK5EX14MBXC284.redmond.corp.microsoft.com" type="cite">
      <div class="WordSection1">
        <div>
          <div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"><b>Sent:</b>
                Friday, May 18, 2012 8:17 AM<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
                <b>Subject:</b> Re: [Openid-specs-ab] Should we put
                self-issued into the Messages or should we create a
                separate document?</span></p>
          </div>
        </div>
        <p class="MsoNormal"> </p>
        <p class="MsoNormal">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: </p>
        <p class="MsoNormal">We have self-issued OP documented at <a 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>
          . 
          </p>
        <div>
          <p class="MsoNormal">We have built the code that works. </p>
        </div>
        <div>
          <p class="MsoNormal"> </p>
        </div>
        <div>
          <p class="MsoNormal">We decided not to create Userinfo token,
            but decided to include them in the id_token. </p>
        </div>
        <div>
          <p class="MsoNormal">Registration overlay still have not
            reached the consensus. </p>
        </div>
        <div>
          <p class="MsoNormal"> </p>
        </div>
        <div>
          <p class="MsoNormal">Having said that, we should now consider
            where we are going to put these in. </p>
        </div>
        <div>
          <p class="MsoNormal">In Messages? </p>
        </div>
        <div>
          <p class="MsoNormal">Or a separate spec? </p>
        </div>
        <div>
          <p class="MsoNormal"> </p>
        </div>
        <div>
          <p class="MsoNormal">Please discuss. </p>
        </div>
        <div>
          <div>
            <p class="MsoNormal"> </p>
          </div>
          <p class="MsoNormal">-- <br>
            Nat Sakimura (=nat) </p>
          <div>
            <p class="MsoNormal">Chairman, OpenID Foundation<br>
              <a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
              @_nat_en</p>
          </div>
          <p class="MsoNormal"> </p>
        </div>
        <p class="MsoNormal"><br>
          <br>
          <br>
          </p>
        <pre>_______________________________________________</pre>
        <pre>Openid-specs-ab mailing list</pre>
        <pre><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a></pre>
        <pre><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></pre>
        <p class="MsoNormal"> </p>
      </div>
    </blockquote>
    <br>
  

</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Openid-specs-ab mailing list</span><br><span><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a></span><br>
<span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></span><br></div></blockquote></body></html>