<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Can all this be put into the draft by tomorrow morning’s call (in the Americas) so it can be reviewed then? I think that a note should be included that it’s
not clear whether any XRI providers will become OpenID Connect Providers yet or not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> openid-specs-ab-bounces@lists.openid.net [mailto:openid-specs-ab-bounces@lists.openid.net]
<b>On Behalf Of </b>Nat Sakimura<br>
<b>Sent:</b> Wednesday, September 03, 2014 8:55 AM<br>
<b>To:</b> John Bradley<br>
<b>Cc:</b> Michael Schwartz; openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> Re: [Openid-specs-ab] Ad-hoc conversation about i-names and OpenID Connect Migration 29-Aug-14<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Good point about my solution is that it is completely independent of whatever the XRI providers does, unless they shut down the forwarding service. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">As long as the forwarding service is supported, I can specify
<a href="https://accounts.google.com">https://accounts.google.com</a> as (+openid_iss) and I am done if google allows external canonical ID to be mapped to its OpenID Connect ID. Of course, I can set up
<a href="http://id.sakimura.org">id.sakimura.org</a> and point (+openid_iss) to it as well. <o:p></o:p></p>
<div>
<p class="MsoNormal">If Fullxri decides to support OpenID Connect, then he can create a default map for (+openid_iss) to its users. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Fullxri can make an independent decision on it. This kind of "distributed governance" in fact is very much in-line with the original concept of user centricity :-)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">That's the beauty of this solution. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Nat<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2014-09-04 0:13 GMT+09:00 John Bradley <<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>>:<o:p></o:p></p>
<p class="MsoNormal">Markus indicated that Respect Networks is not planning on doing Connect.<br>
<br>
I don't think we have had input from them directly at this point.<br>
<br>
John B.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Sep 3, 2014, at 9:46 AM, Michael Schwartz <<a href="mailto:mike@gluu.org">mike@gluu.org</a>> wrote:<br>
<br>
> Nat,<br>
><br>
> If Markus is ok with the changes, then I'm ok with it. Does it align with XRI as currently conceived by Respect Networks?<br>
><br>
> - Mike<br>
><br>
><br>
><br>
> -------------------------------------<br>
> Michael Schwartz<br>
> CEO Gluu<br>
><br>
><br>
>> Message: 2<br>
>> Date: Wed, 3 Sep 2014 12:39:23 +0900<br>
>> From: Nat Sakimura <<a href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>><br>
>> To: Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>>, Markus Sabadello<br>
>> <<a href="mailto:markus.sabadello@gmail.com">markus.sabadello@gmail.com</a>><br>
>> Cc: "<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>"<br>
>> <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>><br>
>> Subject: Re: [Openid-specs-ab] Ad-hoc conversation about i-names and<br>
>> OpenID Connect Migration 29-Aug-14<br>
>> Message-ID: <<a href="mailto:20140903123923.24425e3f1a08a945e78af87a@nri.co.jp">20140903123923.24425e3f1a08a945e78af87a@nri.co.jp</a>><br>
>> Content-Type: text/plain; charset=US-ASCII<br>
>> For what is worth,unlike I had hoped for, XRI would need a special casing.<br>
>> Also, whether <a href="http://xri.net" target="_blank">xri.net</a> would support this spec is unclear.<br>
>> Best compromise that I can think of right now is to use the forwarding<br>
>> service of XRI.<br>
>> Forwarding service is a service that XRI providers needs to implement.<br>
>> You can create a node under your XRI to point to another location.<br>
>> For example, I can define<br>
>> =nat/(+contact)<br>
>> to forward it to a contact page of my choice.<br>
>> Similarly, I could create<br>
>> =nat/(+openid_iss)<br>
>> and map it to any page.<br>
>> For example, if my OpenID Connect issuer is <a href="https://example.com/" target="_blank">
https://example.com/</a><br>
>> then I can define =nat/(+openid_iss) to map to <a href="https://example.com/" target="_blank">
https://example.com/</a>.<br>
>> It works this way.<br>
>> 1) The client sends request to <a href="https://xri.net/=nat/(+openid_iss)" target="_blank">
https://xri.net/=nat/(+openid_iss)</a>.<br>
>> 2) The host <a href="http://xri.net" target="_blank">xri.net</a> responds with 302 redirect to for example,<br>
>> <a href="http://forwarding.fullxri.com/forwading/=nat/(+openid_iss)" target="_blank">
http://forwarding.fullxri.com/forwading/=nat/(+openid_iss)</a><br>
>> 3) The client send request to it.<br>
>> 4) The host replies with 302 redirect to<br>
>> <a href="https://example.com/" target="_blank">https://example.com/</a><br>
>> 5) The client requests <a href="https://example.com/" target="_blank">https://example.com/</a>.<br>
>> 6) The page returns 200 OK so the redirection sequence terminates here.<br>
>> 7) Now the client has found that <a href="https://example.com/" target="_blank">
https://example.com/</a> is the<br>
>> authoritative OpenID Connect issuer.<br>
>> 8) Match it to the value of "iss" in the ID Token.<br>
>> This should work with any XRI provider without <a href="http://xri.net" target="_blank">
xri.net</a> doing something.<br>
>> Thoughts?<br>
>> Nat<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><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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><o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)<o:p></o:p></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<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>