+1 apart from the title... It sounds like the spec is implementing OAuth Open Redirector... Something like "preventing OAuth open redirector" or so might be more descriptive.
Nat 2016年1月21日(木) 23:08 John Bradley <ve7...@ve7jtb.com>: > +1 for adoption > > On Jan 21, 2016, at 3:18 AM, William Denniss <wdenn...@google.com> wrote: > > +1 for adoption. > > On Tue, Jan 19, 2016 at 7:47 PM, Hannes Tschofenig < > hannes.tschofe...@gmx.net> wrote: > >> Hi all, >> >> this is the call for adoption of OAuth 2.0 Security: OAuth Open >> Redirector, see >> https://tools.ietf.org/html/draft-bradley-oauth-open-redirector-02 >> >> Please let us know by Feb 2nd whether you accept / object to the >> adoption of this document as a starting point for work in the OAuth >> working group. >> >> Note: At the IETF Yokohama we asked for generic feedback about doing >> security work in the OAuth working group and there was very positive >> feedback. However, for the adoption call we need to ask for individual >> documents. Hence, you need to state your view again. >> >> Ciao >> Hannes & Derek >> >> >> >> >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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
