[Openid-specs-ab] Draft Implementer's Draft vote notice

[Mike Jones]

FYI - this poll has been created at https://openid.net/foundation/members/polls/68.

                                                            -- Mike

From: John Bradley [mailto:ve7jtb at ve7jtb.com]
Sent: Wednesday, July 17, 2013 1:40 PM
To: Mike Jones
Cc: openid-specs-ab at lists.openid.net; Don Thibeau
Subject: Re: [Openid-specs-ab] Draft Implementer's Draft vote notice

looks fine

On 2013-07-17, at 2:59 PM, Mike Jones <Michael.Jones at microsoft.com<mailto:Michael.Jones at microsoft.com>> wrote:


I propose that we use the following wording for the Implementer's Draft vote.  Any suggestions for improvements, or shall I get this sent out as-is?

The vote will start on Tuesday, July 23 (the day after the 45 day review period ends) and end on Tuesday, July 30th.

                                                            -- Mike

Vote to approve second set of OpenID Connect Implementer's Drafts

The OpenID Connect Working Group recommends approval of the following specifications as OpenID Implementer's Drafts:

*        Basic Client Profile - Simple, self-contained profile for a Web-based Relying Parties using the OAuth code flow.
*        Implicit Client Profile - Simple, self-contained profile for a Web-based Relying Parties using the OAuth implicit flow.
*        Messages - Defines the messages that are used by OpenID Connect.
*        Standard - Defines an HTTP binding for the Messages, for both Relying Parties and OpenID Providers.
*        Discovery - Defines how Relying Parties dynamically discover information about OpenID Providers.
*        Dynamic Registration - Defines how Relying Parties dynamically register with OpenID Providers.
*        Session Management - Defines how to manage OpenID Connect sessions, including logout functionality.
*        Multiple Response Type Encoding - Registers OAuth 2.0 "response_type" values used by OpenID Connect.

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-28.html
*        http://openid.net/specs/openid-connect-implicit-1_0-11.html
*        http://openid.net/specs/openid-connect-messages-1_0-20.html
*        http://openid.net/specs/openid-connect-standard-1_0-21.html
*        http://openid.net/specs/openid-connect-discovery-1_0-17.html
*        http://openid.net/specs/openid-connect-registration-1_0-19.html
*        http://openid.net/specs/openid-connect-session-1_0-15.html
*        http://openid.net/specs/oauth-v2-multiple-response-types-1_0-08.html

A description of OpenID Connect can be found at http://openid.net/connect/. The working group page is http://openid.net/wg/connect/.

_______________________________________________
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net<mailto:Openid-specs-ab at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-ab

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20130718/5ef8dc95/attachment.html>