<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:tahoma,new york,times,serif;font-size:10pt"><br><div style="font-family:tahoma, new york, times, serif;font-size:10pt"><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family:tahoma, new york, times, serif;font-size:10pt;color:#000000;"><div>Spec call notes 08-Aug-11<br><br>Pam Dingle<br>John Bradley<br>Nat Sakimura<br>Johnny Bufu<br>George Fletcher<br>Edmund Jay<br><br><br><br>John made some changes to the OpenID Lite spec<br> * changed the Introspection endpoint from GET request to POST request due to the fact the <br> the ID Token may be intercepted by referral URLs/Logs, and other methods.<br> Breno said in chat with Nat that GET and JSONP may be needed<br> John to contact Breno
offline for further discussions<br> * made other non-controversial changes from feedback<br><br>John will work on first draft of OpenID 2.0 compatibility/migration spec. Maybe available tomorrow.<br><br>Edmund
will post first draft of OpendID Connect Messages spec to the mailing list.<br><br><br>Discussion of JWT and long header names:<br> * most preferred longer names<br> * most feel that it's too late to make major changes to spec<br> * longer or shorter names can be implemented by defining long constant values by developers vice versa<br> * perhaps better documentation in specs for short names<br><br>Pam has written a OpenID Connect landing page which will be posted to the list for feedback<br><br>WG to setup new support mailing list not encumbered by IPR agreements for general and support questions and feedback.<br><br><br><br> <br><p class="MsoNormal"><a rel="nofollow" target="_blank" href="http://openid.net/specs/openid-connect-framework-1_0.html"><br>
</a></p>
<p class="MsoNormal"> <br></p></div>
</div></div></div>
</div></body></html>