<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=us-ascii">
<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">I think board action on this would be premature, as I think first the working group needs to decide what approach makes the most sense.<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">Based upon the discussions at the pre-IETF meeting in London, I think we have two ways to accomplish this. We can create an RFC and use the IANA registry.
This could be a very simple RFC that only establishes the registry or registries. The other way is for us to run our own registry, much like the Information Card foundation did at
<a href="http://wiki.informationcard.net/index.php?title=Claim_Catalog">http://wiki.informationcard.net/index.php?title=Claim_Catalog</a>.<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">Once we decide what we want to do, then we could have the board review it and approve it – probably at the May in-person meeting.<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> Monday, April 07, 2014 9:17 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] Extending OpenID Connect Discovery<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">OK. Can one of the board member propose the motion to establish a registry for this purpose? <o:p></o:p></p>
<div>
<p class="MsoNormal">I suppose cost implication is almost negligible, and we do not need much availability, so it is a low risk thing with a potentially high utility. <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-04-07 23:52 GMT+08:00 John Bradley <<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>>:<o:p></o:p></p>
<p class="MsoNormal">Updating and publishing a new discovery spec is a long process involving an all member vote.<br>
<br>
A registry for new elements is probably more practical and the way most specs deal with extension elements like this.<br>
<br>
UMA is it's own protocol (sort of) so having it's own discovery document for things that are doing UMA is fine.<br>
<br>
I think the question is how to deal with OAuth extensions that may or may not be generally supported.<br>
<br>
I seem to recall from looking at Gluu's Connect discovery document that you were adding extra elements.<br>
<br>
We need to avoid name collision and give people a way to discover what extension elements are.<br>
<br>
In principal private elements should use URI for names to avoid conflict. eg:<br>
"<a href="http://gluu.org/uma-config" target="_blank">http://gluu.org/uma-config</a>": "<a href="http://seed.gluu.org/.well-known/uma-configuration" target="_blank">http://seed.gluu.org/.well-known/uma-configuration</a>"<br>
<br>
So extensions of discovery are possible now but the registry makes them more useful.<br>
<br>
John B.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
On Apr 7, 2014, at 9:05 AM, Michael Schwartz <<a href="mailto:mike@gluu.org">mike@gluu.org</a>> wrote:<br>
<br>
><br>
> Other OAuth2 protocols can define their own Webfinger-style discovery mechanism.<br>
> UMA uses a similar convention: <host>/.well-known/uma-configuration<br>
><br>
> For example, the OX demo server:<br>
> <a href="http://seed.gluu.org/.well-known/uma-configuration" target="_blank">http://seed.gluu.org/.well-known/uma-configuration</a><br>
><br>
> Wouldn't any changes to the OpenID Connect discovery spec just be dealt with in a future version OpenID Connect?<br>
><br>
> thx,<br>
><br>
> Mike<br>
><br>
><br>
> -------------------------------------<br>
> Michael Schwartz<br>
> Gluu<br>
> Founder / CEO<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>
_______________________________________________<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>
</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>