specs Digest, Vol 36, Issue 1

[John Bradley]

Chris

I think we are agreeing.  OpenID needs to play to it's strengths.    
Chasing shiny things is tempting.

We need to carefully consider the impact of changes.

That is not to say that openID shouldn't evolve.

There are always tradeoffs.

Remember that a GSA LoA 2 or 3 profile is focused on the Gov accepting  
the assertions for specific uses.

Other people are free to make there own determinations for other use  
cases.

I am interested in finding out if IdP really want to be certified at  
LoA 2 with all of the extra identity proofing,  liability and other  
things that go with that.

A LoA 2 certification for a IdP involves a lot more than just tweaking  
some protocol peaces.

Are there OPs  that want that?

John B.
On 13-Aug-09, at 9:11 AM, Chris Messina wrote:

> On Thu, Aug 13, 2009 at 8:34 AM, John Bradley <jbradley at mac.com>  
> wrote:
> Some may ask if we add artifact binding, signatures and encryption  
> are we not reinventing SAML Web SSO, or something of equal complexity?
>
> I would like to know more about this, but my instinct is always to  
> say "NO" for as long as possible when any new feature will a)  
> introduce complexity and b) stifle or impair potential adoption.
>
> That we've come as far as we have is a feat; maintaining that  
> momentum is critical — and that means making good on the promise of  
> what OpenID offers *today* — and only extending it with real world  
> examples where people are implementing kludges (en masse) to serve a  
> common need.
>
> Chris
>
> -- 
> Chris Messina
> Open Web Advocate
>
> Personal: http://factoryjoe.com
> Follow me on Twitter: http://twitter.com/chrismessina
>
> Citizen Agency: http://citizenagency.com
> Diso Project: http://diso-project.org
> OpenID Foundation: http://openid.net
>
> This email is:   [ ] bloggable    [X] ask first   [ ] private

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20090813/49227c9f/attachment-0001.htm>