And given the growing momentum with the new-fangledness (and it's use in other places like OAuth and Portable Contacts and OpenSocial) it would be nice if, by the time an initial draft of the newness is complete, OpenID would be ready with support for it, so that we can simplify and minimize the number of libraries out there (i.e. ONE set of discovery libraries).<div>
<br></div><div>I also appreciate Martin's notes from IIW, since I was unable to attend, and look forward to David's new charter, since I'm very much in favor and supportive of this work!</div><div><br></div><div>
Chris<br><br><div class="gmail_quote">On Wed, Nov 12, 2008 at 6:06 PM, Dick Hardt <span dir="ltr"><<a href="mailto:dick.hardt@gmail.com">dick.hardt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Eran is promising to move the XRD spec forward quickly.<br>
<font color="#888888"><br>
-- Dick<br>
</font><div><div></div><div class="Wj3C7c"><br>
On 12-Nov-08, at 3:01 PM, Joseph A Holsten wrote:<br>
<br>
> Feel free to focus on yadis/xrds errata, but don't worry about XRD<br>
> new fangledness yet. I'd even say don't mention xrds-simple. OpenID<br>
> has been workable with yadis/xrds. But until the xrds-simple/xrd<br>
> stuff gets near final, mentioning it will only confuse people and<br>
> strain their trust.<br>
><br>
> <a href="http://josephholsten.com" target="_blank">http://josephholsten.com</a><br>
><br>
> On Nov 11, 2008, at 2:46 PM, David Recordon wrote:<br>
><br>
>> Yep, thanks! I'll be sending out a new charter shortly.<br>
>><br>
>> On Nov 11, 2008, at 11:24 AM, George Fletcher wrote:<br>
>><br>
>>> Great notes! Thanks!<br>
>>><br>
>>> Martin Atkins wrote:<br>
>>>> Here's the output from today's IIW session on this:<br>
>>>><br>
>>>><br>
>>>> 2.0 has been finalized<br>
>>>> bunch of implementations<br>
>>>> found lots of spec bugs<br>
>>>><br>
>>>> also gone and done oauth and email addresses and other things.<br>
>>>> Can we<br>
>>>> support these in the core spec?<br>
>>>><br>
>>>> - Making the spec more readable and fixing bugs (eratta)<br>
>>>> - Delegation<br>
>>>> - Error handling<br>
>>>> - Adding a security appendix<br>
>>>> - could be a separate document referred to by the spec<br>
>>>> - possibly produced by separate group<br>
>>>> - Who controls this security page?<br>
>>>> - Security committee could look after this.<br>
>>>> - or Allen at Yahoo! will be editing a security document<br>
>>>> - Clarifying XRI<br>
>>>> - Currently there's no firm message about whether RPs MUST support<br>
>>>> XRIs or not.<br>
>>>> - Need to clarify how exactly XRI should be used with OpenID.<br>
>>>> - Similar to the whitelist question.<br>
>>>> - Clarify if RPs can white or blacklist what OPs they accept, and<br>
>>>> vice-versa.<br>
>>>> - Discovery of type of identifiers an RP supports.<br>
>>>> - Clarifying IRI<br>
>>>> - Updating discovery. Possibly including the new-fangled XRD<br>
>>>> discovery.<br>
>>>> - Clarifying whether association over SSL must/can use diffie-<br>
>>>> hellman.<br>
>>>> - Discovery of support of checkid_immediate.<br>
>>>><br>
>>>> Exploratory work:<br>
>>>> - Signature mechanisms. Looking at additionally supporting the<br>
>>>> mechanisms defined in OAuth so that they can be closer together.<br>
>>>> - Possibly deprecating the current signature mechanism.<br>
>>>> - Public keys?<br>
>>>> - Email-shaped identifiers for OpenID<br>
>>>> - Could be a separate working group?<br>
>>>><br>
>>>> There was consensus that email-shaped identifiers would be worked<br>
>>>> on by<br>
>>>> a separate group and possibly rolled into 2.1 if it's done in time.<br>
>>>><br>
>>>> - Smart/rich clients?<br>
>>>> - Could be in this WG unless it ends up being a big change in<br>
>>>> which<br>
>>>> case it could be its own WG.<br>
>>>> - There's another session about this.<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> specs mailing list<br>
>>>> <a href="mailto:specs@openid.net">specs@openid.net</a><br>
>>>> <a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>
>>>><br>
>>>><br>
>>><br>
>>> --<br>
>>> Chief Architect AIM: gffletch<br>
>>> Identity Services Work: <a href="mailto:george.fletcher@corp.aol.com">george.fletcher@corp.aol.com</a><br>
>>> AOL LLC Home: <a href="mailto:gffletch@aol.com">gffletch@aol.com</a><br>
>>> Mobile: +1-703-462-3494<br>
>>> Office: +1-703-265-2544 Blog: http://<br>
>>> <a href="http://practicalid.blogspot.com" target="_blank">practicalid.blogspot.com</a><br>
>>><br>
>>> _______________________________________________<br>
>>> specs mailing list<br>
>>> <a href="mailto:specs@openid.net">specs@openid.net</a><br>
>>> <a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> specs mailing list<br>
>> <a href="mailto:specs@openid.net">specs@openid.net</a><br>
>> <a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>
><br>
><br>
> _______________________________________________<br>
> specs mailing list<br>
> <a href="mailto:specs@openid.net">specs@openid.net</a><br>
> <a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>
<br>
_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@openid.net">specs@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Citizen-Participant &<br> Open Technology Advocate-at-Large<br><a href="http://factoryjoe.com">factoryjoe.com</a> # <a href="http://diso-project.org">diso-project.org</a><br>
<a href="http://citizenagency.com">citizenagency.com</a> # <a href="http://vidoop.com">vidoop.com</a><br>This email is: [ ] bloggable [X] ask first [ ] private<br>
</div>