Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption?

2020-07-07 Thread Sascha Preibisch
Hello Dick! Unless the two typos that I have mentioned should be updated beforehand , no, I do not. Thank you, Sascha On Tue, 7 Jul 2020 at 16:36, Dick Hardt wrote: > Thanks Sascha and Vladimir for the feedback! > > Sascha: did you have a concern with the document being adopted by the WG? > >

Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption?

2020-07-07 Thread Dick Hardt
Thanks Sascha and Vladimir for the feedback! Sascha: did you have a concern with the document being adopted by the WG? ᐧ On Tue, Jul 7, 2020 at 4:04 PM Sascha Preibisch wrote: > Hi all! > > Here is the rest of my feedback. At the end I also included a list of > typos and the summary of changes

Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption?

2020-07-07 Thread Sascha Preibisch
Hi all! Here is the rest of my feedback. At the end I also included a list of typos and the summary of changes that I have found between RFC 6739 and the current draft. Regards, Sascha Section 2.3. Client Authentication - Draft and current: - both documents contain this

Re: [OAUTH-WG] OAuth 2.1-03 - WG adoption?

2020-07-07 Thread Vladimir Dzhuvinov
I find 03 well structured, well written and it shows that a lot of thought and work has gone into it. If this is a formal call for adoption - I support it. > - defined new client type - credentialed clients - a client that has > credentials, but the AS has not confirmed the identity of the clien

Re: [OAUTH-WG] A few comments on draft-ietf-oauth-rar-01

2020-07-07 Thread Vladimir Dzhuvinov
On 06/07/2020 19:32, Neil Madden wrote: > I’m reading draft-ietf-oauth-rar-01 in a bit more detail now I have > some time, and I have a few comments. > > An assumption in the draft appears to be that the client knows ahead > of time what it wants to gain access to and can describe it in detail. >