On those lines, I've been asked to sign up as co-editor for the dynamic client registration document, and I'd be OK with that. There are a lot of little side documents that I'd like to see finalized (XML encoding, instance, UX, dynamic reg, chained auth, MAC). We can discuss details at either IIW or IETF -- but it's something that I'd definitely like to help see through how I can.
-- Justin On Oct 10, 2012, at 4:52 AM, Hannes Tschofenig wrote: > Hi Justin, Hi Torsten, > > We will take care of appropriate time management and agenda topics that have > not seen enough presentation on the list will be postponed. > > In fact, I am concerned about the progress with the use cases document and > the dynamic client registration work. I have notified the authors of my > concerns privately already. > > Ciao > Hannes > > On 10/10/2012 08:09 AM, Torsten Lodderstedt wrote: >> +1 >> >> >> >> "Richer, Justin P." <[email protected]> schrieb: >> >> Good for me, AS LONG AS we make absolutely SURE that we leave plenty of >> time for #8 on the agenda, to the point of cutting off and tabling other >> discussions ahead of time. There are a lot of ancillary documents in various >> states of use/neglect that shouldn't be left aside by the WG, and this is a >> good venue for all of that. >> >> -- Justin >> >> On Oct 7, 2012, at 12:08 PM, Zeltsan, Zachary (Zachary) wrote: >> >> +1 >> >> Zachary >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Phil Hunt >> Sent: Saturday, October 06, 2012 2:54 PM >> To: Torsten Lodderstedt >> Cc: [email protected] WG >> Subject: Re: [OAUTH-WG] Agenda for Atlanta Meeting >> >> +1 >> >> Phil >> >> On 2012-10-06, at 10:07, Torsten Lodderstedt >> <[email protected]> wrote: >> >> fine for me >> >> Am 05.10.2012 10:03, schrieb Hannes Tschofenig: >> >> Hi all, >> >> here is an agenda proposal for the Atlanta IETF meeting: >> (The indicated names are proposals.) >> >> ------ >> Agenda: >> >> 1. Status Update, Agenda Bashing (Chairs) >> 2. Token Revocation (Thorsten) >> 3. Assertions (Brian + Mike) >> 4. OAuth Use Cases (Zachary) >> 5. JWT (Mike) >> 6. Security (Phil) >> 7. Dynamic Client Registration (Thomas) >> 8. Roadmap >> ------ >> >> In the last item we would like to discuss the bigger >> picture of how to get OAuth 2.0 deployment improved. >> There are at least 2 parts to this, namely (a) what >> other specifications do we need to work on, and (b) how >> do we improve interoperability. >> >> Let us know whether you think that this fits your needs. >> >> Ciao >> Hannes & Derek >> >> PS: I am hoping to see daft updates of the WG items soon. >> >> >> ------------------------------------------------------------------------ >> >> OAuth mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/oauth >> >> >> >> ------------------------------------------------------------------------ >> >> OAuth mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/oauth >> >> >> ------------------------------------------------------------------------ >> >> OAuth mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/oauth >> >> ------------------------------------------------------------------------ >> >> OAuth mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/oauth >> >> >> >> >> _______________________________________________ >> OAuth mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/oauth >> > _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
