When we constructed the current structure in Prague we thought that structure best fit the needs of a implementer, so my preference would be to keep it as it is now but, Torsten / Mark / Phil also may have feedback.
-----Original Message----- From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Eran Hammer-Lahav Sent: Thursday, July 07, 2011 8:18 AM To: oauth@ietf.org; 'Mark Mcgloin (mark.mcgl...@ie.ibm.com)'; 'Torsten Lodderstedt (tors...@lodderstedt.net)'; 'Phil Hunt (phil.h...@oracle.com)' Subject: Re: [OAUTH-WG] security considerations - authorization tokens Looking back at the archives, I didn't find any replies to this proposal. Torsten / Mark / Phil - is this a change you would like me to make? EHL > -----Original Message----- > From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf > Of Brian Eaton > Sent: Sunday, May 22, 2011 8:47 PM > To: oauth@ietf.org > Subject: [OAUTH-WG] security considerations - authorization tokens > > As I said in the other note, after reading through the security > considerations section a couple of times, I think it could benefit > from a different organization. Specifically > > - keep the introduction, it's awesome. > - write new sections for each of the following > 1) Authorization Tokens > 2) Web Application Clients > 3) User-Agent Clients > 4) Installed Application Clients > 5) Authorization Servers > 6) Resource Servers > - merge the current text into the appropriate sections. > > I took a swing at the authorization tokens text. I tried to capture > most of the relevant items from the current draft, but might have missed some. > > Cheers, > Brian _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
