;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20241106T12
DTEND;TZID=America/New_York:20241106T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
Done
On Thu, Oct 31, 2024 at 9:02 AM Rifaat Shekh-Yusef
wrote:
> Sure. I will update the agenda and move your presentation to Thursday.
>
> Regards,
> Rifaat
>
>
> On Thu, Oct 31, 2024 at 7:11 AM Dmitry Telegin
> wrote:
>
>> Rifaat,
>>
>> I have
oley wrote:
>
>> TYVM,
>> Deb
>>
>> On Mon, Oct 28, 2024 at 11:30 AM Rifaat Shekh-Yusef <
>> rifaat.s.i...@gmail.com> wrote:
>>
>>> Deb,
>>>
>>> Done.
>>>
>>>
>>> All,
>>>
>>> I have shu
attend the discussions on SD-JWT and SD-JWT-VC, but these are
> currently on Monday (which is a conflict for me with ipsecme - which meets
> only once). Could these be shifted to Tuesday or Thursday (ideally).
>
> Thanks for the consideration,
>
> Deb Cooley
> Sec AD
>
All,
The following is a draft agenda for the OAuth WG meeting in Dublin:
https://datatracker.ietf.org/doc/agenda-121-oauth/
Please, take a look and let us know if you have any questions or comments.
Regards,
Rifaat
___
OAuth mailing list -- oauth@ietf
Hi Timothée,
This document is the product of the SIPCore WG, not the OAuth WG.
I suggest that you send this feedback to the SIPCore mailing list.
Regards,
Rifaat
On Tue, Oct 15, 2024 at 8:21 AM Timothée Jaussoin wrote:
> Hi,
>
> I'm currently implementing the RFC 8898 and I have a question re
All,
This is a *short second WG Last Call* for the *SD-JWT* document after the
recent update based on the feedback provided during the first WGLC
https://www.ietf.org/archive/id/draft-ietf-oauth-selective-disclosure-jwt-13.txt
Please, review this document and reply on the mailing list if you have
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20241009T12
DTEND;TZID=America/New_York:20241009T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
such scenarios into
> account, but appears to have taken the framework approach, leaving it up to
> developers to complete the definition of the flow for the factors an AS is
> required to use / combine. Is it envisioned for the 1st party flow spec to
> get complemented with profiles
All,
This is a call for topics for the coming IETF121 in Dublin.
Please, let us know *as soon as possible *if you have topics that you
would like to discuss.
Regards,
Rifaat & Hannes
___
OAuth mailing list -- oauth@ietf.org
To unsubscribe send an email
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240925T12
DTEND;TZID=America/New_York:20240925T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
All,
As per the discussion in Vancouver, this is a call for adoption for the *Proof
of Issuer Key Authority (PIKA) *draft:
https://datatracker.ietf.org/doc/draft-barnes-oauth-pika/
Please, reply on the mailing list and let us know if you are in favor or
against adopting this draft as WG document,
All,
As per the discussion in Vancouver, this is a call for adoption for the
First Party Apps draft:
https://datatracker.ietf.org/doc/draft-parecki-oauth-first-party-apps/
Please, reply on the mailing list and let us know if you are in favor or
against adopting this draft as WG document, by *Sep
All,
As per the discussion in Vancouver, this is a WG Last Call for the *SD-JWT *
document.
https://www.ietf.org/archive/id/draft-ietf-oauth-selective-disclosure-jwt-11.html
Please, review this document and reply on the mailing list if you have any
comments or concerns, by *Sep 17th*.
Regards,
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240828T12
DTEND;TZID=America/New_York:20240828T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240814T12
DTEND;TZID=America/New_York:20240814T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
Rifaat Shekh-Yusef has requested publication of
draft-ietf-oauth-resource-metadata-07 as Proposed Standard on behalf of the
OAUTH working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-oauth-resource-met
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240731T12
DTEND;TZID=America/New_York:20240731T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
All,
Here is the shepherd write-up for the OAuth 2.0 Protected Resource Metadata
draft:
https://datatracker.ietf.org/doc/draft-ietf-oauth-resource-metadata/shepherdwriteup/
Please, take a look and let me know if you have any comments.
Regards,
Rifaat
Mike, Phil, Aaron,
As part of the shepherd write-up, all authors of the OAuth 2.0 Protected
Resource Metadata draft must confirm that any and all appropriate *IPR
disclosures* required for full conformance with the provisions of BCP 78
and BCP 79 have been disclosed.
https://datatracker.ietf.org/
All,
As part of the shepherd write-up for the OAuth 2.0 Protected Resource
Metadata document, we are looking for information about implementations of
this draft.
https://www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-06.html
Please, reply on the mailing list with any implementations t
ed in the PR, what specifically would you
> suggest that we say about downgrade possibilities?
>
>
>
> -- Mike
>
>
>
> *From:* Rifaat Shekh-Yusef
> *Sent:* Saturday, July 6, 2024 5:05 AM
> *To:* Michael Jones
> *Cc:* oauth
>
All,
Here is our draft agenda for our 3 OAuth sessions at IETF120:
https://datatracker.ietf.org/doc/agenda-120-oauth/
Please, take a look and let us know what you think.
Regards,
Rifaat & Hannes
___
OAuth mailing list -- oauth@ietf.org
To unsubscribe
Thanks,
>
> -- Mike
>
>
>
> *From:* Rifaat Shekh-Yusef
> *Sent:* Thursday, July 4, 2024 5:30 AM
> *To:* oauth
> *Subject:* [OAUTH-WG] Shepherd Review for OAuth 2.0 Protected Resource
> M
Mike, Phil, Aaron,
The following is my shepherd review for OAuth 2.0 Protected Resource
Metadata
https://www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-05.html
*Comments/Questions*
5.4. Compatibility with other authentication methods
Would this not open the door for potential downg
Sorry, I need to cancel this meeting for today.
Regards,
Rifaat
-- Forwarded message -
From: Rifaat Shekh-Yusef
Date: Wed, Jun 19, 2024 at 11:35 AM
Subject: Webex meeting canceled: OAuth WG Virtual Office Hours
To:
You canceled this Webex meeting.
Wednesday, June 19, 2024
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240619T12
DTEND;TZID=America/New_York:20240619T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
024 at 9:23 AM Michael Richardson
> wrote:
>
>>
>> {does oauth need to remain in the CC?}
>>
>> Rifaat Shekh-Yusef wrote:
>> > The *draft* proposal is talking about a *live* document, with some
>> > ideas borrowed from the IANA registry pro
o have a resource like:
> https://www.ietf.org/obp/ui
>
> Denis
>
> I think we are in agreement here.
> I did not mean for "dynamic" to be interpreted as the term might change
> after it was defined.
> I will try to avoid using the term "dynamic" to a
** living document*.
On Thu, Jun 13, 2024 at 4:22 PM Rifaat Shekh-Yusef
wrote:
> Adding the id-align list to the thread.
>
> The *draft* proposal is talking about a *live* document, with some ideas
> borrowed from the IANA registry process.
> We are sharing this here to get
Adding the id-align list to the thread.
The *draft* proposal is talking about a *live* document, with some ideas
borrowed from the IANA registry process.
We are sharing this here to get the community's thoughts on this, so we
would together come up with a proper process for such a document.
Regar
, Jun 13, 2024 at 12:51 PM Michael Jones
wrote:
> Is this intended to replace https://www.rfc-editor.org/rfc/rfc4949.html?
>
>
>
> *From:* Rifaat Shekh-Yusef
> *Sent:* Thursday, June 13, 2024 9:14 AM
> *To:* oauth
> *Subject:* [OAUTH-WG] Fwd:
C 4949.
>
>
>
> *From:* Rifaat Shekh-Yusef
> *Sent:* Thursday, June 13, 2024 10:34 AM
> *To:* Michael Jones
> *Cc:* oauth ; id-al...@ietf.org
> *Subject:* Re: [OAUTH-WG] Fwd: Internet Terminology Glossary
>
>
>
> That's where we started, but that was deemed problem
wrote:
>
> Rifaat Shekh-Yusef wrote:
> > That's where we started, but that was deemed problematic because that
> > document was produced as an Independent Submission Stream, which is
> > outside of the IETF process. Also, the RFC is a static document,
>
-- Forwarded message -
From: Rifaat Shekh-Yusef
Date: Thu, Jun 13, 2024 at 11:38 AM
Subject: Internet Terminology Glossary
To:
All,
Dick and I put together the following *draft* proposal for an *Internet
Terminology Glossary*:
https://github.com/dickhardt/glossary/blob/main
Please, consider volunteering for 2024 NomCom to help with selecting the
next round of IETF leaders.
Regards,
Rifaat
---
The IETF tools development team identified an error in the interface
between the IETF registration system and the datatracker that mistakenly
marked people as volunte
All,
This is an official call for adoption for the *Proof of Issuer Key
Authority (PIKA)* draft:
https://datatracker.ietf.org/doc/draft-barnes-oauth-pika/
Please, reply *on the mailing list* and let us know if you are in favor or
against adopting this draft as WG document, by *June 24th*.
Regard
-- Forwarded message -
From: Robert Sparks
Date: Tue, May 21, 2024 at 4:26 PM
Subject: [Tools-discuss] Update on ongoing mail delivery issues
To: tools-discuss , Working Chairs <
wgcha...@ietf.org>,
If you have had a message fail to deliver to a list since the mailman3
transitio
Shekh-Yusef wrote:
>
>
> Rifaat Shekh-Yusef canceled this Webex meeting.
>
> Wednesday, May 08, 2024
> 12:00 PM | (UTC-04:00) Eastern Time (US & Canada) | 30 mins
>
> Need help? Go to https://help.webex.com
>
> ___
I have a conflict this week and will not be able to host this meeting.
Regards,
Rifaat
On Tue, May 7, 2024 at 3:36 PM Rifaat Shekh-Yusef wrote:
>
>
> You canceled this Webex meeting.
>
> Wednesday, May 08, 2024
> 12:00 PM | (UTC-04:00) Eastern Time (US & Canada) |
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240508T12
DTEND;TZID=America/New_York:20240508T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
All,
This is a *second* *WG Last Call* for the *OAuth 2.0 Protected Resource
Metadata* document (the previous one was for v03.).
https://www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-05.html
Please, review this document and reply on the mailing list if you have any
comments or concer
e to the status list definition, i.e., just
> return the response relative to the requested time instead of current.
>
>
>
> *From: *Spasm on behalf of "Tschofenig, Hannes"
>
> *Date: *Friday, May 3, 2024 at 3:28 AM
> *To: *"sp...@ietf.org"
> *Cc: *Rifaat
-- Forwarded message -
From: Robert Sparks
Date: Thu, May 9, 2024 at 3:29 PM
Subject: [Tools-discuss] Update on ongoing mail delivery issues and request
to resend failed messages
To: tools-discuss , Working Chairs <
wgcha...@ietf.org>,
If you have had a message fail to deliver t
All,
This is a *WG Last Call* for the *Browser-Based Apps* draft.
https://datatracker.ietf.org/doc/draft-ietf-oauth-browser-based-apps/
Please, review this document and reply on the mailing list if you have any
comments or concerns, by *May 15. *
If you reviewed the document and you do not have a
ORGANIZER;CN=Rifaat Shekh-Yusef:mailto:rifaat.s.i...@gmail.com
UID:5bqme8k6pme30bc7i9r5aap...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Rifaat Shekh-Yusef;X-NUM-GUESTS=0:mailto:rifaat.s.i...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT
ORGANIZER;CN=Rifaat Shekh-Yusef:mailto:rifaat.s.i...@gmail.com
UID:64c4p681gag1afcpspj48b0...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Rifaat Shekh-Yusef;X-NUM-GUESTS=0:mailto:rifaat.s.i...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT
ORGANIZER;CN=Rifaat Shekh-Yusef:mailto:rifaat.s.i...@gmail.com
UID:4m80v6995aubre076s18s6b...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Rifaat Shekh-Yusef;X-NUM-GUESTS=0:mailto:rifaat.s.i...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT
ORGANIZER;CN=Rifaat Shekh-Yusef:mailto:rifaat.s.i...@gmail.com
UID:41beum7datse934jnn861sp...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Rifaat Shekh-Yusef;X-NUM-GUESTS=0:mailto:rifaat.s.i...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT
ORGANIZER;CN=Rifaat Shekh-Yusef:mailto:rifaat.s.i...@gmail.com
UID:0kvpotp8qj0jcqmnmkcra5p...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Rifaat Shekh-Yusef;X-NUM-GUESTS=0:mailto:rifaat.s.i...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT
On Mon, Apr 15, 2024 at 9:32 AM Rifaat Shekh-Yusef
wrote:
> All,
>
> This is a *WG Last Call* for the *Cross-Device Flows BCP *document.
>
> https://www.ietf.org/archive/id/draft-ietf-oauth-cross-device-security-06.html
>
> Please, review this document and reply on the mailing
ource or a reference that describe those "same defenses"?
>3. Section 7.6: The readability of this section may be improved by
>first stating clearly what use cases are supported (as described in
> paragraph 3) and then calling out that all other use cases are not
>
Just to be clear, this is *not* a call for adoption at this time.
So, please focus on discussing the concept described in this individual
draft.
Regards,
Rifaat
On Wed, Apr 17, 2024 at 1:43 PM John Zila wrote:
> On 11 Apr 2024, at 21:15, Neil Madden wrote:
>
> > I'm still digesting this dr
All,
This is a *WG Last Call* for the *Cross-Device Flows BCP *document.
https://www.ietf.org/archive/id/draft-ietf-oauth-cross-device-security-06.html
Please, review this document and reply on the mailing list if you have any
comments or concerns, by *April 29th*.
Regards,
Rifaat & Hannes
___
We cancelled the meeting for this week, because Hannes and I have conflicts.
Regards,
Rifaat
On Mon, Apr 8, 2024 at 3:09 PM Rifaat Shekh-Yusef wrote:
>
>
> Rifaat Shekh-Yusef canceled this Webex meeting.
>
> Wednesday, April 10, 2024
> 12:00 PM | (UTC-04:00) Eastern
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240410T12
DTEND;TZID=America/New_York:20240410T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
All,
This is a *WG Last Call* for the *OAuth 2.0 Protected Resource Metadata*
document.
https://www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-03.html
Please, review this document and reply on the mailing list if you have any
comments or concerns, by *April 12*.
Regards,
Rifaat & H
All,
You can find the final agenda at the following link:
https://datatracker.ietf.org/doc/agenda-119-oauth/
Regards,
Rifaat
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
Presenters,
Please, upload your slides to the following link as soon as possible:
https://datatracker.ietf.org/meeting/119/session/oauth/
Regards,
Rifaat
On Mon, Mar 4, 2024 at 1:31 PM Rifaat Shekh-Yusef
wrote:
> All,
>
> The following is the draft agenda for Brisbane
All,
The following is the draft agenda for Brisbane:
https://datatracker.ietf.org/doc/agenda-119-oauth/
Please, take a look and let us know if you have any questions/comments.
Regards,
Rifaat & Hannes
___
OAuth mailing list
OAuth@ietf.org
https://www.
-- Forwarded message -
From: IETF Agenda
Date: Fri, Feb 23, 2024 at 5:53 PM
Subject: IETF 119 Final Agenda
To: Working Group Chairs
IETF 119
Brisbane, Australia
March 16-22, 2024
Hosted by: Google and Consortium members
Key supporter: Brisbane Economic Development Agency
IETF119
e-metadata.
>
>
>
> Thanks,
>
> -- Mike
>
>
>
> *From:* OAuth *On Behalf Of *Rifaat Shekh-Yusef
> *Sent:* Wednesday, January 24, 2024 6:15 AM
> *To:* oauth
> *Subject:* [OAUTH-WG] IE
All,
This is a call for topics for the coming IETF119 in Brisbane.
Please, let us know *as soon as possible *if you have topics that you
would like to discuss.
This will help us request enough sessions to address the requested topics.
*Note that if we do not get the list before Feb 2nd, we might
All,
Happy new year!
I have cancelled the meeting for this week.
Regards,
Rifaat
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20240103T12
DTEND;TZID=America/New_York:20240103T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
If you are interested in Digital Identity, you might want to consider
subscribing to this new mailing list.
Regards,
Rifaat
-- Forwarded message -
From: IETF Secretariat
Date: Tue, Jan 2, 2024 at 11:17 AM
Subject: New Non-WG Mailing List: id-align (Identity Alignment)
To: IETF
I changed the expiry of the link to one day.
If people want to join after the expiry, ping me back.
Regards,
Rifaat
On Thu, Dec 7, 2023 at 4:22 PM Warren Parad wrote:
> Thanks!
>
> On Thu, Dec 7, 2023 at 10:09 PM Rifaat Shekh-Yusef <
> rifaat.s.i...@gmail.com> wrote:
>
t; Is this the official process:
> https://www.spinics.net/lists/ietf/msg101574.html
>
> On Thu, Dec 7, 2023 at 8:58 PM Rifaat Shekh-Yusef
> wrote:
>
>> I think all you need is a datatracker account.
>>
>> Regards,
>> Rifaat
>>
>>
>> On Thu,
I think all you need is a datatracker account.
Regards,
Rifaat
On Thu, Dec 7, 2023 at 1:16 PM Warren Parad wrote:
> I didn't know there was a Slack Workspace for this. How does one get an
> invite to the workspace?
>
> On Thu, Dec 7, 2023 at 7:04 PM Rifaat Shekh-Yusef
All,
We now have an OAuth channel (#oauth) at the IETF Slack service.
ietf.slack.com
Feel free to join the channel if you use Slack.
Regards,
Rifaat & Hannes
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
.
Regards,
Rifaat & Hannes
On Wed, Nov 22, 2023 at 1:31 PM Steinar Noem wrote:
> I support adoption of the draft for transaction tokens
>
> S
>
> On Tue, Nov 14, 2023 at 7:58 AM Rifaat Shekh-Yusef <
> rifaat.s.i...@gmail.com> wrote:
>
>> All,
>>
>
.
Regards,
Rifaat & Hannes
On Wed, Nov 22, 2023 at 1:25 PM Steinar Noem wrote:
> I support adoption
>
>
> --
> *Fra:* OAuth på vegne av
>
>
> On Tue, Nov 14, 2023 at 4:59 AM Rifaat Shekh-Yusef <
> rifaat.s.i...@gmail.com> wrote:
gt;> Dmitry
>>> Backbase / Keycloak
>>>
>>> On Wed, Nov 15, 2023 at 4:40 PM Pieter Kasselman >> 40microsoft@dmarc.ietf.org> wrote:
>>>
>>>> I support adoption.
>>>>
>>>>
>>>>
>>>> *From:* O
All,
This is an *official* call for adoption for the *Identity Chaining *draft:
https://datatracker.ietf.org/doc/draft-schwenkschuster-oauth-identity-chaining/
Please, reply on the mailing list and let us know if you are in favor or
against adopting this draft as WG document, by *Nov 28th.*
Rega
All,
This is an *official *call for adoption for the *Transaction Tokens *draft:
https://datatracker.ietf.org/doc/draft-tulshibagwale-oauth-transaction-tokens/
Please, reply on the mailing list and let us know if you are in favor or
against adopting this draft as WG document, by *Nov 28th*.
Rega
All,
As discussed during the last IETF meeting in Prague, this is the new
invitation for the OAuth WG Virtual Office Hours meeting.
Please, remove all previous invitations you might still have on
your calendar.
Regards,
Rifaat
On Mon, Nov 13, 2023 at 1:22 PM Rifaat Shekh-Yusef wrote
ATTENDEE;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20231122T12
DTEND;TZID=America/New_York:20231122T123000
LOCATION:https://ietf.webex
Rifaat Shekh-Yusef has requested publication of
draft-ietf-oauth-security-topics-24 as Best Current Practice on behalf of the
OAUTH working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-oauth-security-t
All,
Here is our final agenda for Prague:
https://datatracker.ietf.org/doc/agenda-118-oauth/
Regards,
Rifaat & Hannes
Tuesday (60 min)
-
Chairs update – Rifaat Shekh-Yusef/Hannes Tschofenig (15 min)
-
Charter discussion (30 min)
-
SD-JWT – Kristina Yasuda/Daniel
;CN="oauth@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth@ietf.org
ORGANIZER;CN="Rifaat Shekh-Yusef":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20211006T12
DTEND;TZID=America/New_York:20211006T123000
LOCATION:https://ietf.webex.com/ietf
TRANSP:OPAQUE
Fixed few typos:
https://datatracker.ietf.org/meeting/118/materials/agenda-118-oauth-02
Regards,
Rifaat
On Wed, Oct 25, 2023 at 4:23 PM Rifaat Shekh-Yusef
wrote:
> All,
>
> Here is our *draft* agenda for the meeting in Prague:
> https://datatracker.ietf.org/meeting/118/material
All,
Here is our *draft* agenda for the meeting in Prague:
https://datatracker.ietf.org/meeting/118/materials/agenda-118-oauth-00
Please, let us know if we missed anything.
Regards,
Rifaat & Hannes
___
OAuth mailing list
OAuth@ietf.org
https://www.iet
raft-looker-oauth-jwt-cwt-status-list/
> so that the history tracks better.
>
> I also noticed that there are significant changes to the draft between the
> individual and working group versions. Typically it is better to post a
> verbatim copy of the individual draft as the ado
All,
The *NomCom *is tasked with selecting the *IETF leadership*, like the IESG
and the IAB.
For the NomCom to be able to make an informed decision, they need feedback
from the *wider IETF community*.
Please, consider allocating some time to provide feedback on people that
you interacted with to
+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/
>>
&g
All,
In the world of the Digital Identity community, a brilliant star has dimmed
with the passing of *Vittorio Luigi Bertocci*, a true luminary in the
field. His departure has left a void in the hearts of those who admired and
respected him.
Vittorio left a great legacy with the OAuth Working Gro
All,
As per the preliminary agenda, we have 3 sessions in Prague:
1. *Tuesday *at 15:30-16:30
2. *Wednesday *at 14:30-16:30
3. *Friday *at 13:00-15:00
Please, reply to this email or directly to the chairs if you have topics
that you would like to discuss.
Regards,
Rifaat & Hannes
__
me reality
> would be search and found in a OAuth WG that would show how this would be
> then possible.
>
> I support the adoption and I'm implementing the so called vcstuff drafts
>
> Il ven 29 set 2023, 20:16 Rifaat Shekh-Yusef ha
> scritto:
>
>> There are two r
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*.
R
There are two reasons for not calling for the adoption of this document:
1. The SPICE discussion, which gave the impression that the plan is to
migrate this to a new dedicated WG.
2. Some people questioned whether this is in scope or not.
If the first one is not an issue, and there is no plan to m
h Token Introspection" specification would likely have
> been treated as metadata for the "resource server."
>
> Best Regards,
> Takahiko Kawasaki
>
>
> On Thu, Aug 24, 2023 at 4:02 AM Rifaat Shekh-Yusef <
> rifaat.s.i...@gmail.com> wrote:
>
>&g
-- Forwarded message -
From: NomCom Chair 2023
Date: Wed, Aug 23, 2023 at 1:37 PM
Subject: NomCom 2023 Reminder that Nominations are Open
To: IETF Announcement List
All,
The 2023-2024 nominating committee would like to thank everyone who has
nominated someone for positions and
All,
This is an official call for adoption for the *Protected Resource Metadata*
draft:
https://datatracker.ietf.org/doc/draft-jones-oauth-resource-metadata/
Please, reply on the mailing list and let us know if you are in favor of
adopting this draft as WG document, by *Sep 6th.*
Regards,
Rifaa
All,
Based on the responses to this call for adoption, we declare the
*Attestation-Based
Client Authentication* draft adopted as a WG document.
Authors,
Feel free to submit a WG document at your convenience.
Regards,
Rifaat & Hannes
On Tue, Aug 8, 2023 at 11:51 AM Paul Bastian wrote:
>
All,
Based on the responses to this call for adoption, we declare the *SD-JWT-based
Verifiable Credentials* draft adopted as a WG document.
Authors,
Feel free to submit a WG document at your convenience.
Regards,
Rifaat & Hannes
On Tue, Aug 8, 2023 at 11:51 AM Paul Bastian wrote:
> I
All,
This is a *WG Last Call *for the* Browser-based Apps* draft.
https://www.ietf.org/archive/id/draft-ietf-oauth-browser-based-apps-14.html
Please, review this document and reply on the mailing list if you have any
comments or concerns, by *August 11th*.
Regards,
Rifaat & Hannes
_
All,
This is an official call for adoption for the *Attestation-Based Client
Authentication *draft discussed in SF.
https://datatracker.ietf.org/doc/draft-looker-oauth-attestation-based-client-auth/
Please, reply on the mailing list and let us know if you are in favor of
adopting this draft as WG
All,
This is an official call for adoption for the *SD-JWT-based Verifiable
Credentials *draft discussed in SF.
https://datatracker.ietf.org/doc/draft-terbu-oauth-sd-jwt-vc/
Please, reply on the mailing list and let us know if you are in favor of
adopting this draft as WG document, by *August 11t
All,
There seems to be some confusion about the number of OAuth WG sessions.
We have *THREE* sessions this week.
The session that was initially scheduled on Thursday is now *cancelled*,
and instead we have a new session on *Tuesday*.
In summary, we have sessions on *Tuesday*, *Wednesday*, and *F
All,
The agenda for the OAuth WG has changed.
Our 3 sessions are now on *Tuesday*, *Wednesday* and *Friday* all at
*9:30am*.
Here is a link to the updated agenda:
https://datatracker.ietf.org/meeting/117/materials/agenda-117-oauth-08
Regards,
Rifaat & Hannes
1 - 100 of 517 matches
Mail list logo
