The OpenID membership has approved the following specifications as OpenID Implementer’s Drafts in the vote held from February 7th to 15th, 2012: • Basic Client Profile – Simple self-contained specification for a web-based Relying Party. (This spec contains a subset of the information in Messages and Standard.) • Discovery – Defines how user and provider endpoints can be dynamically discovered. • Dynamic Registration – Defines how clients can dynamically register with OpenID Providers. • Messages – Defines all the messages that are used in OpenID Connect. (These messages are used by the Standard binding.) • Standard – Complete HTTP binding of the Messages, for both Relying Parties and OpenID Providers. • Multiple Response Type Encoding – Registers OAuth 2.0 response_type values used by OpenID Connect. The voting results were:

• Approve (86 votes)
• Disapprove (1 vote)
• Abstain (2 votes)

Total Votes: 89 (out of 363 members = 25% > 20% quorum requirement) An Implementer’s Draft is a stable version of a specification providing intellectual property protections to implementers of the specification. The specifications are posted at these locations: • http://openid.net/specs/openid-connect-basic-1_0-15.html • http://openid.net/specs/openid-connect-discovery-1_0-07.html • http://openid.net/specs/openid-connect-registration-1_0-08.html • http://openid.net/specs/openid-connect-messages-1_0-07.html • http://openid.net/specs/openid-connect-standard-1_0-07.html • http://openid.net/specs/oauth-v2-multiple-response-types-1_0-03.html A description of OpenID Connect can be found at http://openid.net/connect/. The working group page is http://openid.net/wg/connect/.