rian Campbell
> *Sent:* Tuesday, November 29, 2022 11:21 PM
> *To:* Hannes Tschofenig
> *Cc:* oauth
> *Subject:* Re: [OAUTH-WG] draft-ietf-oauth-selective-disclosure-jwt
>
>
>
> Hi Hannes,
>
>
>
> Though I am yet to officially have my name on the document as
Thanks for the response, Brian.
A few remarks below.
From: Brian Campbell
Sent: Tuesday, November 29, 2022 11:21 PM
To: Hannes Tschofenig
Cc: oauth
Subject: Re: [OAUTH-WG] draft-ietf-oauth-selective-disclosure-jwt
Hi Hannes,
Though I am yet to officially have my name on the document as a co
Hi Brian,
My two cents.
1) This draft is about selective-disclosure. The draft should be
balanced between enclosure and disclosure.
The topic of selective-enclosure should also be addressed.
In particular in OAuth, the claims to be incorporated are usually only
selected with a coarse granula
Hi Hannes,
Though I am yet to officially have my name on the document as a co-author,
you did mention me directly :) And so I'll attempt to answer or respond to
your questions/statements below.
On Mon, Nov 28, 2022 at 7:24 AM Hannes Tschofenig
wrote:
> Hi Daniel, Hi Kristina, Hi Brian,
>
> Hi
Hi Daniel, Hi Kristina, Hi Brian,
Hi all,
Reading through draft-ietf-oauth-selective-disclosure-jwt I was wondering why
the document defines new terminology for roles that already exist in OAuth.
For example:
* Issuer = AS
* Holder = Client
* Verifier = RS
I assume that was done
