Regarding #1:
We gathered a lot of feedback and many people agreed here (
https://github.com/vcstuff/draft-ietf-oauth-status-list/issues/74 ) that
the title seems reasonable. If people do not agree now, I'm happy to
discuss so in Prague.
Regarding #2:
I'm sorry that we forgot to publish
the adopted version, and then make
> changes in a -01 version.
>
>
>
> Huge +1.
>
+1
>
> Best,
>
> Kristina
>
>
>
>
>
> *From:* OAuth *On Behalf Of * Michael Jones
> *Sent:* Monday, October 23, 2023 10:29 PM
> *To:* rifaat.s.ietf ; Aaron Parecki
Jones
Sent: Monday, October 23, 2023 10:29 PM
To: rifaat.s.ietf ; Aaron Parecki
Cc: oauth
Subject: Re: [OAUTH-WG] Call for adoption - JWT and CWT Status List
To Aaron’s naming points, I would be fine changing the title in the draft from
“OAuth Status List” to “OAuth Token Status List”, if there’s w
On Behalf Of Rifaat Shekh-Yusef
Sent: Monday, October 23, 2023 7:48 AM
To: Aaron Parecki
Cc: oauth
Subject: Re: [OAUTH-WG] Call for adoption - JWT and CWT Status List
I also noticed you didn't mark it as replacing the individual draft in
datatracker. You can email supp...@ietf.org<mailto:s
>
> I also noticed you didn't mark it as replacing the individual draft in
> datatracker. You can email supp...@ietf.org and request that they mark it
> as replacing
> https://datatracker.ietf.org/doc/draft-looker-oauth-jwt-cwt-status-list/ so
> that the history tracks better.
>
I fixed that.
Hi Aaron,
Tobias, Paul, Christian,
I just noticed the new working group adopted version of this draft:
https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/
I posted this comment on Github, but I'll repeat it here for others. I
find the new name "OAuth Status List" confusing.
Tobias, Paul, Christian,
I just noticed the new working group adopted version of this draft:
https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/
I posted this comment on Github, but I'll repeat it here for others. I find
the new name "OAuth Status List" confusing. While I understand
All,
Based on the feedback to this call for adoption, we declare this document
adopted as a WG document.
Authors,
Please, submit this as a working group document at your earliest
convenience.
Regards,
Rifaat & Hannes
On Tue, Oct 3, 2023 at 8:51 PM John Bradley wrote:
> +1 for
As one of the authors of this draft, I support the adoption.
Best regards,
Paul
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
+1 for adoption
On Sat, Sep 30, 2023, 9:53 AM Rifaat Shekh-Yusef
wrote:
> All,
>
> This is an official call for adoption for the *JWT and CWT Status List*
> draft:
> https://datatracker.ietf.org/doc/draft-looker-oauth-jwt-cwt-status-list/
>
> Please, reply *on the mailing list *and let us know
+1 for the adoption so we can explore this as a WG document
+1 to Brian's comment to consider the application to tokens in general
(unless the authors have plans for JWT / CWT specific features)
Vladimir Dzhuvinov
On 03/10/2023 00:10, Brian Campbell wrote:
I support adoption.
I do think
It's unfortunate that the spec does not cite previous work, which the
authors and undoubtedly aware of, the same comment was made at the
microphone at the last IETF.
Orie is right that we have to take prior work into account.
I am saying this in response to this call for adoption but it
ate: Tuesday, 3 October 2023 at 2:41 AM
To: Orie Steele , rifaat.s.ietf
Cc: oauth
Subject: Re: [OAUTH-WG] Call for adoption - JWT and CWT Status List
EXTERNAL EMAIL: This email originated outside of our organisation. Do not click
links or open attachments unless you recognise the sender and k
To: rifaat.s.ietf
Cc: oauth
Subject: Re: [OAUTH-WG] Call for adoption - JWT and CWT Status List
I support adoption.
We have implementations of a similar spec and we don't think it would be good
for vendors to have to support both, but that's not under control of OAuth...
we hope
+1
Nat Sakimura
On 2 Oct 2023, 22:11 +0100, Brian Campbell
, wrote:
> I support adoption.
>
> I do think the document would be more appropriately scoped with more focus on
> the status list itself and less so on the JWT/CWT signed representations
> thereof. As such, I'd suggest maybe using a
I am in favor of the adoption, with reservations and observations.
My reservations and observations will be posted in another email under
the following header:
"Reservations and observations about draft JWT and CWT Status List"
The basic idea looks useful for environments where:
-
I support adoption. I have questions about the specifics which I'll try to
write up in the next week or so, but the basic idea seems useful. (The tl;dr of
my thoughts is: have we learned everything we can do from the *many* iterations
of similar mechanisms in the PKI space?)
-- Neil
> On 30
I support adoption.
Joseph
> On 30 Sep 2023, at 13:52, Rifaat Shekh-Yusef wrote:
>
> All,
>
> This is an official call for adoption for the JWT and CWT Status List draft:
> https://datatracker.ietf.org/doc/draft-looker-oauth-jwt-cwt-status-list/
>
> Please, reply on the mailing list and let
I support adoption.
Am 30.09.23 um 14:52 schrieb Rifaat Shekh-Yusef:
All,
This is an official call for adoption for the *JWT and CWT Status
List* draft:
https://datatracker.ietf.org/doc/draft-looker-oauth-jwt-cwt-status-list/
Please, reply *on the mailing list *and let us know if you are in
I support adoption.
From: OAuth on behalf of Amir Sharif
Sent: Saturday, September 30, 2023 7:45:04 AM
To: Rifaat Shekh-Yusef ; oauth
Subject: Re: [OAUTH-WG] Call for adoption - JWT and CWT Status List
I support the adoption.
On Sat, 30 Sep 2023 at 16:41
I support the adoption
Regards
Il sab 30 set 2023, 14:53 Rifaat Shekh-Yusef ha
scritto:
> All,
>
> This is an official call for adoption for the *JWT and CWT Status List*
> draft:
> https://datatracker.ietf.org/doc/draft-looker-oauth-jwt-cwt-status-list/
>
> Please, reply *on the mailing list
I support the adoption.
On Sat, 30 Sep 2023 at 16:41,
wrote:
> +1 for adoption
> Am 30. Sept. 2023, 15:33 +0200 schrieb Aaron Parecki 40parecki@dmarc.ietf.org>:
>
> I support adoption
>
>
> On Sat, Sep 30, 2023 at 5:53 AM Rifaat Shekh-Yusef <
> rifaat.s.i...@gmail.com> wrote:
>
>> All,
>>
+1 for adoption
Am 30. Sept. 2023, 15:33 +0200 schrieb Aaron Parecki
:
> I support adoption
>
>
> > On Sat, Sep 30, 2023 at 5:53 AM Rifaat Shekh-Yusef
> > wrote:
> > > All,
> > >
> > > This is an official call for adoption for the JWT and CWT Status List
> > > draft:
> > >
I support adoption
On Sat, Sep 30, 2023 at 5:53 AM Rifaat Shekh-Yusef
wrote:
> All,
>
> This is an official call for adoption for the *JWT and CWT Status List*
> draft:
> https://datatracker.ietf.org/doc/draft-looker-oauth-jwt-cwt-status-list/
>
> Please, reply *on the mailing list *and let us
I support adoption.
We have implementations of a similar spec and we don't think it would be
good for vendors to have to support both, but that's not under control of
OAuth... we hope there will be significant improvements made, after
adoption to justify a separate spec, aside from CWT being
All,
This is an official call for adoption for the *JWT and CWT Status List*
draft:
https://datatracker.ietf.org/doc/draft-looker-oauth-jwt-cwt-status-list/
Please, reply *on the mailing list *and let us know if you are in *favor *or*
against *adopting this draft as WG document, by *Oct 13th*.
26 matches
Mail list logo
