<div>Inline...</div><div><br></div>On Thu, May 20, 2010 at 11:35 AM, Nat Sakimura <span dir="ltr"><<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Dewitt,<br>
<br>
Since I am not a marketing type, I may not have been communicating it properly.<br>
I got a lot of positive criticism around it during IIW X, but the OIDF<br>
chartered WG,<br>
"Artifact Binding" Working Group is producing OAuth2.0-- binding of<br>
OpenID Assertions.<br>
<br>
The spec has gone through 6 draft specs, and you can find it here:<br>
<br>
<a href="https://openid4.us/specs/ab/" target="_blank">https://openid4.us/specs/ab/</a> ("OpenID for us", not ver. 4 :-)<br>
<br>
>From what I see, it is kind of close to what proposed OpenID Connect would do.<br>
It lacks some features like webfinger support (which I expected v.Next<br>
Discovery<br>
WG would sort out), cookie generation, etc., but they can also be<br>
added in, I suppose.<br>
It is kind of unfortunate that though I like those features of the<br>
connect proposal,<br>
I cannot incorporate them because I have read them and these are not<br>
contributed to OIDF yet.<br></blockquote><div><br></div><div>I currently plan to contribute the Connect proposal into an OpenID Foundation Working Group. If that's undesired then I'll remove "OpenID" from the name and continue working on it elsewhere.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Artifact Binding does other things that connect proposal does not: it<br>
supports mobile handsets as well as higher level of assurance.David<br>
might be thinking that these are<br>
redundant features, but they are very useful in commerce etc. setting<br>
and all these public key crypto (actually, any crypto for that matter)<br>
things are optional.<br></blockquote><div><br></div><div>I don't think that they are redundant. Mobile is really important and I'm glad that you held the session on Artifact Binding at IIW so that I could learn more about the limitations within that sort of environment!</div>
<div><br></div><div>It's not said enough, but Nat you've really been the only one making technical progress within the Foundation the past six months and that progress is a good thing.</div><div> </div><div><br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I am planning to freeze the draft latest by the end of May.<br>
<br>
For expediting the process of getting "connect" like features out,<br>
it might be better to utilize this WG as a conduit instead,<br>
and still we can message the market that we are producing a<br>
single version of the OpenID 3.<br>
<br>
Just my 2c.<br>
<font color="#888888"><br>
=nat<br>
</font><br>
P.S. I plan to contribute <a href="http://openid4.us" target="_blank">openid4.us</a> to OIDF. I just needed it to get<br>
SSL cert to demonstrate Artifact Binding at IIW. What would be the process?<br>
<div><div></div><div class="h5"><br>
On Fri, May 21, 2010 at 2:45 AM, DeWitt Clinton <<a href="mailto:dewitt@google.com">dewitt@google.com</a>> wrote:<br>
> From where I'm sitting, I see them as mutually compatible and parallel<br>
> goals, but not now the same technology, and that's okay.<br>
> Connect being "build on what the web is already doing and very much<br>
> wants/needs today", and v.Next being "what could be done given the luxury of<br>
> time to explore."<br>
> The OIDF could make an effort to wait for the latter to build the former,<br>
> but honestly, the former isn't going to wait for the OIDF. Which is why I<br>
> advocate a parallel approach if we hope to see the OIDF involved (and I do).<br>
><br>
> Please correct my understanding of the situation if I got the above wrong,<br>
> as I'm only following the discussions from the edges and I'm (blissfully)<br>
> out of the loop.<br>
> -DeWitt<br>
> On Thu, May 20, 2010 at 10:36 AM, Brian Kissel <<a href="mailto:bkissel@janrain.com">bkissel@janrain.com</a>> wrote:<br>
>><br>
>> +1 to Nat's suggestion. While we know that both David and Joseph are very<br>
>> well qualified to lead this committee, if we do have differing<br>
>> perspectives on the future direction of the next iterations of OpenID, it<br>
>> would be good to have representatives from both perspectives involved in<br>
>> leading the process.<br>
>><br>
>> Cheers,<br>
>><br>
>> Brian<br>
>> ___________<br>
>><br>
>> Brian Kissel<br>
>> CEO - JanRain, Inc.<br>
>> <a href="mailto:bkissel@janrain.com">bkissel@janrain.com</a><br>
>> Mobile: 503.342.2668 | Fax: 503.296.5502<br>
>> 519 SW 3rd Ave. Suite 600 Portland, OR 97204<br>
>><br>
>> Increase registrations, engage users, and grow your brand with RPX. Learn<br>
>> more at <a href="http://www.rpxnow.com" target="_blank">www.rpxnow.com</a><br>
>><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:openid-board-bounces@lists.openid.net">openid-board-bounces@lists.openid.net</a><br>
>> [mailto:<a href="mailto:openid-board-bounces@lists.openid.net">openid-board-bounces@lists.openid.net</a>] On Behalf Of Nat Sakimura<br>
>> Sent: Thursday, May 20, 2010 12:09 AM<br>
>> To: <a href="mailto:openid-board@lists.openid.net">openid-board@lists.openid.net</a><br>
>> Subject: Re: [OpenID board] Technical Committee Chairs<br>
>><br>
>> I have a little concern here. It might be a healthy thing to have<br>
>> discussions, but in the end, I really want v.Next and Connect camp to<br>
>> unite. In that respect, both chair and co-chair coming from Connect<br>
>> camp bothers me.<br>
>><br>
>> You say that Joseph was close to be a co-chair, but the situation<br>
>> surrounding it has changed since then. At the time, there was only<br>
>> v.Next. Now, it looks like there are v.Next and Connect camp.<br>
>><br>
>> Do not you think it is better to first ask v.Next camp people to step up?<br>
>><br>
>> Would not somebody form v.Next camp step up?<br>
>><br>
>> =nat<br>
>><br>
>><br>
>> On Thu, May 20, 2010 at 3:23 PM, David Recordon <<a href="mailto:recordond@gmail.com">recordond@gmail.com</a>><br>
>> wrote:<br>
>> > The committee elects its own chairs. A few months ago we elected Dick as<br>
>> > chair and me as co-chair. Joseph was really close to being co-chair.<br>
>> ><br>
>> > On Wed, May 19, 2010 at 11:22 PM, Nat Sakimura <<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>><br>
>> wrote:<br>
>> >><br>
>> >> So, what is the process that chooses committee chairs?<br>
>> >><br>
>> >> On Thu, May 20, 2010 at 3:01 PM, David Recordon <<a href="mailto:recordond@gmail.com">recordond@gmail.com</a>><br>
>> >> wrote:<br>
>> >> > Today the Board passed a resolution directing the Executive Director,<br>
>> >> > Chair,<br>
>> >> > Technical Committee, and outside council to explore a contracting<br>
>> >> > relationship with Dick Hardt to move the v.Next work forward. Dick<br>
>> >> > brought<br>
>> >> > up how there could be a conflict during this process given that he is<br>
>> >> > the<br>
>> >> > chair of the Technical Committee. So for the time being I'll take on<br>
>> the<br>
>> >> > chair role with Joseph Smarr (who wasn't at the meeting but I spoke<br>
>> to a<br>
>> >> > few<br>
>> >> > hours ago) taking on the co-chair role.<br>
>> >> > Technical Committee, expect a followup email around starting to pull<br>
>> >> > together a set of deliverables and timeline over the next week. The<br>
>> >> > goal, as<br>
>> >> > I understand it, is to either have a contract in place or a<br>
>> >> > determination<br>
>> >> > that it is unfeasible by the end of the this month.<br>
>> >> ><br>
>> >> > Thanks,<br>
>> >> > --David<br>
>> >> > _______________________________________________<br>
>> >> > board mailing list<br>
>> >> > <a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
>> >> > <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
>> >> ><br>
>> >> ><br>
>> >><br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> Nat Sakimura (=nat)<br>
>> >> <a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
>> >> <a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
>> >> _______________________________________________<br>
>> >> board mailing list<br>
>> >> <a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
>> >> <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > board mailing list<br>
>> > <a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
>> > <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
>> ><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Nat Sakimura (=nat)<br>
>> <a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
>> <a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
>> _______________________________________________<br>
>> board mailing list<br>
>> <a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
>> <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
>> _______________________________________________<br>
>> board mailing list<br>
>> <a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
>> <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
><br>
><br>
> _______________________________________________<br>
> board mailing list<br>
> <a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
Nat Sakimura (=nat)<br>
<a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
<a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
</div></div></blockquote></div><br>