The openid.net mailing lists are getting a little confusing too, so I will sort things out here.
The working groups currently planned are listed below and are collectively called v.Next. These were decided on 2010/4/6.
· Core Protocol – Chair: Dick Hardt – Scope: active client, message verification, AX/CX/AB, OAuth, non-browser
· Discovery – Co-chairs: Allen Tom / Mike Jones – Scope: URL, acct: (e-mail address OpenIDs), active client (discovery about OP and RP)
· Attribute Schema – Chair: Joseph Smarr – Scope: How to ask for and get rich, consistent common extensible data attributes (attribute discovery)
· UX Guidelines – Chair: Chris Messina – Scope: Guidelines for how OPs and RPs provide a consistent user experience
· Policy & Certification – Chair: Eric Sachs – Scope: (Define scope)
In addition to these, a WG calling itself OpenID Connect has recently been proposed.
This is being driven by people including David Recordon of FB.
In terms of content, it seems to be Artifact Binding – Magic Signature – various security considerations. With Connect, I wonder whether LoA2 is possible.
The unfortunate thing is that this suddenly appeared while discussions were underway to establish the v.Next WGs.
Personally, if it is intended to look to the future, I would like it to be combined with v.Next; if the goal is to finish it quickly, I think it could simply be put into Artifact Binding. But the Connect people take the position that if their claims are not accepted, they will do it elsewhere. They have even gone so far as to say, “If OpenID is to survive, this is its last chance.” Well, it is FB, after all. It is currently the most powerful, so it can do anything. FB has also been applying pressure to the OpenID Foundation in various other ways, and it feels like, “Ah, once people become powerful, they all turn into bullies.”
When I saw the Connect Strawman before it was made public, I thought, “Why not just put it in the v.Next core?” But watching the way they are going about it has somehow left me disheartened.
It is a shame. FB used to seem like a good company.
Incidentally, Y!’s Allen Tom is among the Connect Proposers, but he is saying, let’s stop calling it Connect and do it as v.Next Core. I feel the same way.
Incidentally, the funny thing is that Connect’s Identity Model and Discovery are precisely the XRI that David so detests, but that is a secret, lol.
Related posts

I Asked Genspark to “Summarize OpenID Connect.”
Genspark.ai has a few points that slightly concern me, but it gives a considerably more in-depth answer than Perplexity. Below, I reproduce the answer exactly as…

Using Plain OAuth 2.0 for Authentication Opens a Security Hole Big Enough to Drive a Car Through
Using the OAuth 2.0 implicit grant flow for authentication opens a security hole big enough to drive a car through, as explained in this excellent article…
OpenID Connect Released—The Internet’s Identity Layer
After a hard-fought 4 and a half years—starting with the formation of the working group—and then 6 hard-fought years, we have finally released OpenID Connect. OpenID…
