<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:tahoma,new york,times,serif;font-size:10pt;color:#000000;"><div><span class="cgSelectable cgSelectable-over" style="cursor:pointer;" title="View all emails with this subject">Spec call notes 24-May-12<br><br>Nat Sakimura<br>George Fletcher<br>Edmund Jay<br>John Bradley (joined later)<br>Pam Dingle (joined later)<br><br><br><br>Agenda<br> - Open Issues<br><br><br>Open Issues <br> #593: Standard: redirect_uri registration & matching<br> There is still no clear consensus on how to handle the matching of the redirect_uri value.<br> This issue is deferred pending more feedback.<br><br><br> #595: Discovery 2 - No means of discovery
without web server for domain<br> Current discovery mechanism relies on a web server at the domain to host a .well-known file.<br> Virtual domains or email only providers do not have a web server at the domain.<br> Possible solutions :<br> 1) Use DNS to lookup MX record<br> 2) Require a web server at the domain<br> The above solutions may be too optimistic<br> Pam suggested solution # 3 which is performing a GET on the domain first and if that fails then perform a GET<br>
on the result obtained from a discovery of the domain.<br> Solution 3 seems most plausible to the members present.<br> Since WebFinger is still a questionable work item for the OAuth-Apps group, it is suggested a new spec called<br> called Simple Web Finger (or something similar) be written and which profiles a version of WebFingers.<br> This issue is assigned to John in care of Pam.<br><br><br><br><br><br><br></span></div>
</div></body></html>