Ok then it looks like the name is good as is. :) -- Jim Manico @Manicode Secure Coding Education +1 (808) 652-3805
> On Oct 15, 2015, at 6:52 AM, Nat Sakimura <n-sakim...@nri.co.jp> wrote: > > That’s true, but RFC6749 uses the term Authorization request to mean the > request sent to the authorization endpoint. > > See 4.1.1, 4.2.1, 4.3.1, 4.4.1 of RFC6749. > > Best, > > -- > Nat Sakimura <n-sakim...@nri.co.jp> > Nomura Research Institute, Ltd. > > PLEASE READ: > The information contained in this e-mail is confidential and intended for the > named recipient(s) only. > If you are not an intended recipient of this e-mail, you are hereby notified > that any review, dissemination, distribution or duplication of this message > is strictly prohibited. If you have received this message in error, please > notify the sender immediately and delete your copy from your system. > > From: Jim Manico [mailto:j...@manicode.com] > Sent: Saturday, October 10, 2015 12:28 AM > To: Nat Sakimura <n-sakim...@nri.co.jp> > Cc: oauth <oauth@ietf.org> > Subject: Re: [OAUTH-WG] Better title for OAuth 2.0 JWT Authorization Request > > But its all authorization, even the token request.... > > -- > Jim Manico > @Manicode > Secure Coding Education > +1 (808) 652-3805 > > On Oct 9, 2015, at 5:23 PM, Nat Sakimura <n-sakim...@nri.co.jp> wrote: > > The reason for saying authorization request is that there are two types of > requests in RFC6749; authorization request and token request. This draft > deals with the former and thus named JAR. > > Nat > > 2015年10月9日金曜日、Jim Manico<j...@manicode.com>さんは書きました: > The word authorization is implied by OAuth, consider "OAuth 2.0 JWT Request". > > -- > Jim Manico > @Manicode > (808) 652-3805 > > On Oct 9, 2015, at 3:43 AM, Nat Sakimura <n-sakim...@nri.co.jp> wrote: > > Hi OAuthers: > > One of the to do for https://tools.ietf.org/html/draft-ietf-oauth-jwsreq-05 > is to come up with a better title. > The current title “OAuth 2.0 JWT Authorization Request (JAR)”, is somewhat > better than what it used to be, but if you can suggest a better name, I am > all for it. > > Please let me know if you have an idea. > > Best, > -- > Nat Sakimura <n-sakim...@nri.co.jp> > Nomura Research Institute, Ltd. > > PLEASE READ: > The information contained in this e-mail is confidential and intended for the > named recipient(s) only. > If you are not an intended recipient of this e-mail, you are hereby notified > that any review, dissemination, distribution or duplication of this message > is strictly prohibited. If you have received this message in error, please > notify the sender immediately and delete your copy from your system. > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > > > -- > Nat Sakimura (=nat) > http://www.sakimura.org/en/ > http://twitter.com/_nat_en
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
