[Openid-specs-ab] Spec call notes 16-Apr-15

Mike Jones Michael.Jones at microsoft.com
Thu Apr 16 15:02:24 UTC 2015


Spec call notes 16-Apr-15

John Bradley
Mike Jones
Brian Campbell
Justin Richer
George Fletcher
Edmund Jay

Agenda
               Certification
               Spec Approval Status
               FullXRI is being shut down
               Google is shutting down OpenID 2.0 on April 20th
               Logout Specs
               Passing Software Statements by Reference
               Next Calls

Certification
               All the initial participants are listed at http://openid.net/certification/
                              Certifications to a few more profiles may come in before the launch
               The press releases for the launch are in near-final state
                              Symantec still has to get their quotation in

Spec Approval Status
               OpenID 2.0 to OpenID Connect Migration 1.0 was approved
               OAuth 2.0 Form Post Response Mode still needs 3 more votes
                              The poll closes on April 24th

FullXRI is being shut down
               FullXRI is the i-name provider that most people had been using
               Markus Sabadello is shutting this down
               We have notified people who were using i-names at openid.net to choose another OpenID

Google is shutting down OpenID 2.0 on April 20th
               JanRain Engage is using OpenID Connect at Google now
                              openid.net uses JanRain Engage
               AOL is updating their Google RP code to OpenID Connect today
               Things should continue working for openid.net users after the 20th

Logout Specs
               There are comments on the HTTP logout spec that need to be addressed
                              Mike will look at those after the certification launch
               John still has writing a back-channel logout spec in his queue
                              The session ID would be the same as in the HTTP logout spec

Passing Software Statements by Reference
               The mobile profile working group plans to use software statements
                              They could be very large
               We didn't specify a means of passing software statements by reference
                              They are currently only passed by value
               draft-ietf-oauth-dyn-reg is still in IESG review but we can't add things at this point
               This could be added as a small extension spec
                              John will write a speclet and submit it to OAuth

Next Calls
               We will go back to having the Thursday call only on the first week of the month
               We will continue having the Monday call weekly
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20150416/756ed337/attachment.html>


More information about the Openid-specs-ab mailing list