Thanks Brent, the note is genuinely appreciated. I did take painstaking
efforts to ensure the presentation was factual and somewhat well-reasoned
(if at the cost of brevity) so personally especially appreciate that
acknowledgement.
On Wed, Nov 13, 2024 at 3:40 PM Brent Zundel wrote:
> I want to
+1
shigeya
On Thu, Nov 14, 2024, at 07:39, Brent Zundel wrote:
> I want to express my gratitude to the OAuth WG for the discussion on media
> types during the Thursday session last week.
> The presentation was factual and well-reasoned. and the resulting "Dublin
> Accord" reflects a similarly w
The following errata report has been submitted for RFC7591,
"OAuth 2.0 Dynamic Client Registration Protocol".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8175
--
Type: Editorial
Reported by
I want to express my gratitude to the OAuth WG for the discussion on media
types during the Thursday session last week.
The presentation was factual and well-reasoned. and the resulting "Dublin
Accord" reflects a similarly well-reasoned decision.
___
OAut
FYI - This report has been deleted as junk.
Thank you,
RFC Editor/mc
> On Nov 13, 2024, at 2:45 PM, RFC Errata System
> wrote:
>
> The following errata report has been submitted for RFC7591,
> "OAuth 2.0 Dynamic Client Registration Protocol".
>
> --
> Yo
Hi Daniel,
great work! Looking at [1] and [2] there`s obviously no consensus – which
implies a breach of Sections 1.2, 5 and 9.2 of the IETF Directives on Internet
Standards Process. An assumption is great but not sufficient as in any
standardization body. According to IETF rules the consensus
Hi all,
we are happy to announce version -06 of SD-JWT VC. In this release,
we're updating the media type from application/vc+sd-jwt to
application/dc+sd-jwt (for background, see Brian's excellent summary at
the IETF meeting last week [0]).
This version also removes references to DIDs in the
Internet-Draft draft-ietf-oauth-sd-jwt-vc-06.txt is now available. It is a
work item of the Web Authorization Protocol (OAUTH) WG of the IETF.
Title: SD-JWT-based Verifiable Credentials (SD-JWT VC)
Authors: Oliver Terbu
Daniel Fett
Brian Campbell
Name:draft-i
Thanks Janak for your detailed review and opening the GitHub issues.
On Wed, Nov 13, 2024 at 9:39 AM Janak Amarasena
wrote:
> Hi All,
>
> I created GitHub issues[1] #125 to #131 covering the feedback I provided
> through my previous email.
>
> [1] - https://github.com/oauth-wg/oauth-first-party-
Hi All,
I created GitHub issues[1] #125 to #131 covering the feedback I provided
through my previous email.
[1] - https://github.com/oauth-wg/oauth-first-party-apps/issues
Best Regards,
Janak Amarasena
On Fri, Nov 1, 2024 at 11:43 AM Janak Amarasena
wrote:
> Hi All,
>
> I have gone through th
Am 13.11.24 um 02:04 schrieb Watson Ladd:
I'd appreciate if others would weigh in, particularly if they haven't
followed this debate before.
Happy to - as a co-author of the draft, I think that the current text
addresses this risk sufficiently. Besides that, I'd second what Brian said.
-
Hi,
As the shepherd for this document, I have reviewed the following version of
the Browser-based App draft:
https://www.ietf.org/archive/id/draft-ietf-oauth-browser-based-apps-19.html
I have the following comments/questions:
Section 6.1.1
“This response to the browser will also trigger the relo
12 matches
Mail list logo
