[Openid-specs-ab] Proposed text to post at end of 24 hour review period

Salvatore D'Agostino sal at idmachines.com
Sat Dec 21 22:45:57 UTC 2013


No comments apart from great work and way to end year Mike and others.  

 

Sal

 

From: Chuck Mortimore [mailto:cmortimore at salesforce.com] 
Sent: Friday, December 20, 2013 9:11 PM
To: John Bradley
Cc: openid-specs-ab at lists.openid.net
Subject: Re: [Openid-specs-ab] Proposed text to post at end of 24 hour
review period

 

Totally.  Nice work Mike! (and team)

- cmort


On Dec 20, 2013, at 5:38 PM, John Bradley <ve7jtb at ve7jtb.com> wrote:

No Changes

 

Thanks to everyone especially Mike.

 

John B.

 

On Dec 20, 2013, at 6:44 PM, George Fletcher <gffletch at aol.com> wrote:





No changes from me. Just want to say a HUGE THANKS to you Mike for all your
work in getting the specs to this point!

On 12/20/13 4:36 PM, Mike Jones wrote:

Please identify any changes needed.  This will be posted on the openid.net
blog at 10:15pm Pacific Time tonight if no spec issues are identified
beforehand.

 

                                                            Thanks,

                                                            -- Mike

 

Review of Proposed Final OpenID Connect Specifications and Implementer's
Drafts

 

The OpenID Connect Working Group recommends approval of the following
specifications as Final OpenID Specifications:

.         <http://openid.net/specs/openid-connect-core-1_0-17.html> OpenID
Connect Core - Defines the core OpenID Connect functionality: authentication
built on top of OAuth 2.0 and the use of Claims to communicate information
about the End-User.

.         <http://openid.net/specs/openid-connect-discovery-1_0-21.html>
OpenID Connect Discovery - Defines how Relying Parties dynamically discover
information about OpenID Providers.

.         <http://openid.net/specs/openid-connect-registration-1_0-23.html>
OpenID Connect Dynamic Client Registration - Defines how Relying Parties
dynamically register with OpenID Providers.

.
<http://openid.net/specs/oauth-v2-multiple-response-types-1_0-11.html> OAuth
2.0 Multiple Response Type Encoding - Defines several specific new OAuth 2.0
response types.

 

The working group also recommends approval of the following specifications
as OpenID Implementer's Drafts:

.         <http://openid.net/specs/openid-connect-session-1_0-18.html>
OpenID Connect Session Management - Defines how to manage OpenID Connect
sessions, including logout functionality.

.
<http://openid.net/specs/oauth-v2-form-post-response-mode-1_0-02.html> OAuth
2.0 Form Post Response Mode - Defines how to return OAuth 2.0 Authorization
Response parameters (including OpenID Connect Authentication Response
parameters) using HTML form values that are auto-submitted by the User Agent
using HTTP POST.

 

A Final Specification provides intellectual property protections to
implementers of the specification and is not subject to further revision.
An Implementer's Draft is a stable version of a specification also providing
intellectual property protections, but that is subject to further revision.

 

This note starts the 60 day public review period for the specification
drafts in accordance with the OpenID Foundation IPR policies and procedures.
This review period will end on Tuesday, February 18, 2014. Unless issues are
identified during the review that the working group believes must be
addressed by revising the drafts, this review period will be followed by a
seven day voting period during which OpenID Foundation members will vote on
whether to approve these drafts as Final Specifications and Implementer's
Drafts.  For the convenience of members, voting may begin up to two weeks
before Tuesday, February 18th, with the voting period still ending on
Tuesday, February 25, 2014.

A description of OpenID Connect can be found at
<http://openid.net/connect/> http://openid.net/connect/. The working group
page is <http://openid.net/wg/connect/> http://openid.net/wg/connect/.
Information on joining the OpenID Foundation can be found at
<https://openid.net/foundation/members/registration>
https://openid.net/foundation/members/registration. If you're not already a
member, please consider joining to participate in the approval vote.

 

You can send feedback on the specifications in a way that enables the
working group to act upon your feedback by (1) signing the contribution
agreement at  <http://openid.net/intellectual-property/>
http://openid.net/intellectual-property/ to join the working group (please
specify that you are joining the "AB+Connect" working group on your
contribution agreement), (2) joining the working group mailing list at
<http://lists.openid.net/mailman/listinfo/openid-specs-ab>
http://lists.openid.net/mailman/listinfo/openid-specs-ab, and (3) sending
your feedback to the list.

 

Locations for the proposed Final Specifications are:

.         <http://openid.net/specs/openid-connect-core-1_0-17.html>
http://openid.net/specs/openid-connect-core-1_0-17.html

.         <http://openid.net/specs/openid-connect-discovery-1_0-21.html>
http://openid.net/specs/openid-connect-discovery-1_0-21.html

.         <http://openid.net/specs/openid-connect-registration-1_0-23.html>
http://openid.net/specs/openid-connect-registration-1_0-23.html

.
<http://openid.net/specs/oauth-v2-multiple-response-types-1_0-11.html>
http://openid.net/specs/oauth-v2-multiple-response-types-1_0-11.html

 

Locations for the proposed Implementer's Drafts are:

.         <http://openid.net/specs/openid-connect-session-1_0-18.html>
http://openid.net/specs/openid-connect-session-1_0-18.html

.
<http://openid.net/specs/oauth-v2-form-post-response-mode-1_0-02.html>
http://openid.net/specs/oauth-v2-form-post-response-mode-1_0-02.html

 

These informational Implementer's Guides also accompany these
specifications:

.         <http://openid.net/specs/openid-connect-basic-1_0-32.html> OpenID
Connect Basic Client Profile - Simple subset of the Core functionality for a
web-based Relying Party using the OAuth code flow.

.         <http://openid.net/specs/openid-connect-implicit-1_0-14.html>
OpenID Connect Implicit Client Profile - Simple subset of the Core
functionality for a web-based Relying Party using the OAuth implicit flow.

 

Locations for the accompanying Implementer's Guides are:

.         <http://openid.net/specs/openid-connect-basic-1_0-32.html>
http://openid.net/specs/openid-connect-basic-1_0-32.html

.         <http://openid.net/specs/openid-connect-implicit-1_0-14.html>
http://openid.net/specs/openid-connect-implicit-1_0-14.html

 





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

 

-- 
 <http://connect.me/gffletch> <XeC.png>

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

 

_______________________________________________
Openid-specs-ab mailing list
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/20131221/d61b2e11/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6085 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20131221/d61b2e11/attachment-0001.bin>


More information about the Openid-specs-ab mailing list