ginal Message-
>>> From: Justin Richer
>>> Sent: Thursday, September 15, 2022 11:20 AM
>>> To: Roman Danyliw
>>> Cc: oauth@ietf.org
>>> Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
>>>
>>> Hi Roman, som
se address
this feedback concurrently.
> > -Original Message-
> > From: Justin Richer
> > Sent: Thursday, September 15, 2022 11:20 AM
> > To: Roman Danyliw
> > Cc: oauth@ietf.org
> > Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
> >
&
;>
Cc: oauth@ietf.org<mailto:oauth@ietf.org>; Brian Campbell
mailto:bcampb...@pingidentity.com>>;
jric...@mit.edu<mailto:jric...@mit.edu>
Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
Hi Roman,
thanks for you review.
I’m trying to do the next round for the out
>> mailto:bcampb...@pingidentity.com>>;
>> jric...@mit.edu <mailto:jric...@mit.edu>
>> Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
>>
>> Hi Roman,
>>
>> thanks for you review.
>>
>> I’m trying to do the next round fo
Hi Torsten!
Thanks for the response. More inline ...
> -Original Message-
> From: Torsten Lodderstedt
> Sent: Tuesday, October 18, 2022 9:00 AM
> To: Roman Danyliw
> Cc: oauth@ietf.org; Brian Campbell ;
> jric...@mit.edu
> Subject: Re: [OAUTH-WG] AD review of dr
On Fri, Oct 14, 2022 at 10:50 AM Roman Danyliw wrote:
>
> > >
> > > ** Section 11.2
> > >
> > > One option would be to have a mechanism allowing the registration of
> > > extension modules, each of them responsible for rendering the
> > > respective user consent and any transformation neede
Hi Roman,
thanks for you review.
I’m trying to do the next round for the outstanding issues you raised.
> Am 15.09.2022 um 00:30 schrieb Roman Danyliw :
>
> Hi!
>
> I performed an AD review of draft-ietf-oauth-rar-12. Thanks for this
> document. My feedback is as follows:
>
> ** Secti
Hi Justin!
https://github.com/oauthstuff/draft-oauth-rar/pull/88 looks good to me. Thanks.
Roman
From: Justin Richer
Sent: Monday, October 17, 2022 4:35 PM
To: Roman Danyliw
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
Thank you, that’s a much better way to
etf.org>
Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
Hi Roman, some responses inline.
On Sep 14, 2022, at 6:30 PM, Roman Danyliw
mailto:r...@cert.org>> wrote:
[snip]
** Section 2.2.
All data fields are OPTIONAL for use by a given API
definition.
I don't follow
Looks good to me. Thank you Brian!
From: Brian Campbell
Sent: Thursday, September 15, 2022 12:50 PM
To: Justin Richer
Cc: Roman Danyliw ; oauth@ietf.org
Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
Thanks for the review Roman and thanks Justin for the responses.
I took the
Hi Justin!
> -Original Message-
> From: Justin Richer
> Sent: Thursday, September 15, 2022 11:20 AM
> To: Roman Danyliw
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-rar-12
>
> Hi Roman, some responses inline.
>
> > O
Thanks for the review Roman and thanks Justin for the responses.
I took the liberty of going ahead and making some of the more
straightforward changes suggested by the review in the document source
https://github.com/oauthstuff/draft-oauth-rar/commit/575f21bf6369c609f673062ec2083215c797b4c2
so as
Hi Roman, some responses inline.
> On Sep 14, 2022, at 6:30 PM, Roman Danyliw wrote:
>
> Hi!
>
> I performed an AD review of draft-ietf-oauth-rar-12. Thanks for this
> document. My feedback is as follows:
>
> ** Section 2. Editorial
>
> This field MUST be compared using an exact byte ma
13 matches
Mail list logo
