: Freitag, 7. Februar 2025 18:56
An: Steffen Schwalm
Cc: oauth@ietf.org
Betreff: Re: [OAUTH-WG] Re: Status List Feature Request
Caution: This email originated from outside of the organization. Despite an
upstream security check of attachments and links by Microsoft Defender for
Office, a residual risk
list, this increase the effort for QTSP in eiDAS
significantly)
Means statulist would look a bit like a unfinished. But if somebody
else would finish – also fine
*Von:* Brian Campbell
*Gesendet:* Freitag, 7. Februar 2025 16:19
*An:* Christian Bormann
*Cc:* oauth
*Betreff:* [OAUTH-WG] Re: S
Hi Christian,
My opinion has been posted yesterday at:
https://github.com/oauth-wg/draft-ietf-oauth-status-list/issues/243
In a nutshell:
Defining this extension in the current draft would be easier as the
same document would be able to support "Referenced Tokens"
encoded as JWT, CWT
: Brian Campbell
Gesendet: Freitag, 7. Februar 2025 16:19
An: Christian Bormann
Cc: oauth
Betreff: [OAUTH-WG] Re: Status List Feature Request
Caution: This email originated from outside of the organization. Despite an
upstream security check of attachments and links by Microsoft Defender for
That seems well beyond the scope of both the Status List draft and the
OAuth WG in general.
On Fri, Feb 7, 2025 at 2:57 PM Christian Bormann wrote:
> Hi all,
>
>
>
> While going through the feedback and issues on github, there was one
> bigger discussion point that we would like to bring to the
