y 22, 2019 8:37 AM
To: Roman Danyliw mailto:r...@cert.org>>
Cc: oauth@ietf.org<mailto:oauth@ietf.org>
Subject: Re: [OAUTH-WG] AD Review: draft-ietf-oauth-resource-indicators-02
Yes, sorry about that. I realized this yesterday and as tried to write quickly
from from my phone just before my
53 PM Roman Danyliw wrote:
>
> Hi Brian!
>
>
>
> Thanks for the update in -03. The item below is the only thing that
> remains outstanding.
>
>
>
> Thanks,
>
> Roman
>
>
>
>
>
> *From:* Roman Danyliw
> *Sent:* Wednesday, July 17, 2019 6:05 PM
Hi Brian!
From: Brian Campbell [mailto:bcampb...@pingidentity.com]
Sent: Monday, July 22, 2019 8:37 AM
To: Roman Danyliw
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] AD Review: draft-ietf-oauth-resource-indicators-02
Yes, sorry about that. I realized this yesterday and as tried to write quickly
anyliw
> *Sent:* Wednesday, July 17, 2019 6:05 PM
> *To:* Brian Campbell
> *Cc:* oauth@ietf.org
> *Subject:* RE: [OAUTH-WG] AD Review:
> draft-ietf-oauth-resource-indicators-02
>
>
>
>
>
> *From:* Brian Campbell [mailto:bcampb...@pingidentity.com
> ]
> *Sent:* W
Hi Brian!
Thanks for the update in -03. The item below is the only thing that remains
outstanding.
Thanks,
Roman
From: Roman Danyliw
Sent: Wednesday, July 17, 2019 6:05 PM
To: Brian Campbell
Cc: oauth@ietf.org
Subject: RE: [OAUTH-WG] AD Review: draft-ietf-oauth-resource-indicators-02
From
Hi Brian!
From: Brian Campbell [mailto:bcampb...@pingidentity.com]
Sent: Friday, July 19, 2019 2:02 PM
To: Roman Danyliw
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] AD Review: draft-ietf-oauth-resource-indicators-02
Thanks Roman,
I'm attempting to bring this thread and our private exchanges
Error usage location: implicit grant error response, token error
>
> response
>
>o Related protocol extension: resource parameter
>
> o Change controller: IESG
>
> o Specification document(s): [[ this specification ]]
>
>
>
> Roman
>
>
>
>
ngidentity.com]
Sent: Wednesday, July 17, 2019 6:31 PM
To: Roman Danyliw
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] AD Review: draft-ietf-oauth-resource-indicators-02
Yeah, as you surmised, there is some history behind this. Basically
draft-ietf-oauth-token-exchange predates draft-ietf-oauth-resource-i
Yeah, as you surmised, there is some history behind this. Basically
draft-ietf-oauth-token-exchange predates
draft-ietf-oauth-resource-indicators by a good long time (years) and with
the hope and expectation that draft-ietf-oauth-token-exchange would move to
RFC, I've avoided having a reference in
Hi Brian!
From: Brian Campbell [mailto:bcampb...@pingidentity.com]
Sent: Wednesday, July 17, 2019 4:35 PM
To: Roman Danyliw
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] AD Review: draft-ietf-oauth-resource-indicators-02
Thank you, Roman, for the review. Some replies are inline below. I'll aim
Hi!
I forgot one more thing about this draft after re-reading
draft-ietf-oauth-token-exchange.
Per the IANA action in Section 4.1, I need help understanding on the thinking
to resolve this TODO:
o Parameter usage location: authorization request, token request
[[TODO:
Thank you, Roman, for the review. Some replies are inline below. I'll aim
to push out a -03 addressing this stuff sometime not too long after the I-D
submission embargo is lifted next week.
On Tue, Jul 16, 2019 at 5:23 PM Roman Danyliw wrote:
> Hi!
>
> The following is my AD review of
Hi!
The following is my AD review of draft-ietf-oauth-resource-indicators-02. The
document is in good shape.
(1) Section 2. Per "The parameter can carry the location of a protected
resource, typically as an https URL, or a more abstract identifier", is this
"abstract identifier" still an
13 matches
Mail list logo
