Re: [OAUTH-WG] OAuth2 Client Discovery

2022-12-14 Thread Dmitry Telegin
Hi Tobias, On Wed, Dec 14, 2022 at 2:49 AM Tobias Looker wrote: > > There are certainly things we could explore here, one such option could be > to continue to only return application/json but for the document to include > an element like "@context" in the response if its desired that the metada

[OAUTH-WG] Paul Wouters' Yes on draft-ietf-oauth-rar-19: (with COMMENT)

2022-12-14 Thread Paul Wouters via Datatracker
Paul Wouters has entered the following ballot position for draft-ietf-oauth-rar-19: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.iet

Re: [OAUTH-WG] OAuth2 Client Discovery

2022-12-14 Thread Dick Hardt
1. I see the value of client discovery for registered clients as well as for registering clients. For example, the client may be registered at a number of ASes, and a discovery document lets the client update its information once at its discovery endpoint rather than having to manually update the i

Re: [OAUTH-WG] OAuth2 Client Discovery

2022-12-14 Thread Sam Goto
On Wed, Dec 14, 2022 at 12:04 PM Dick Hardt wrote: > > 1. I see the value of client discovery for registered clients as well as > for registering clients. For example, the client may be registered at a > number of ASes, and a discovery document lets the client update its > information once at its

[OAUTH-WG] Alvaro Retana's No Objection on draft-ietf-oauth-rar-19: (with COMMENT)

2022-12-14 Thread Alvaro Retana via Datatracker
Alvaro Retana has entered the following ballot position for draft-ietf-oauth-rar-19: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https

Re: [OAUTH-WG] OAuth2 Client Discovery

2022-12-14 Thread Tobias Looker
> I see the value of client discovery for registered clients as well as for > registering clients. For example, the client may be registered at a number of > ASes, and a discovery document lets the client update its information once at > its discovery endpoint rather than having to manually upda

Re: [OAUTH-WG] OAuth2 Client Discovery

2022-12-14 Thread Dmitry Telegin
To clarify on JSON-LD - I'm not suggesting we should support it as a *format*; just a bit concerned that we're restricting client metadata response content-type to "application/json", which might be different in the reality. Would it make sense to allow "application/json" as well as its subclasses

Re: [OAUTH-WG] OAuth2 Client Discovery

2022-12-14 Thread Dick Hardt
Responses inline ... On Wed, Dec 14, 2022 at 2:57 PM Tobias Looker wrote: > > I see the value of client discovery for registered clients as well as > for registering clients. For example, the client may be registered at a > number of ASes, and a discovery document lets the client update its > in